Creality CR-10 upgrade
-
Do you use G29 S1 anywhere in your print start code to load the mesh grid compensation height map? You can add it to your config as well if you want it to be active always starting at power up.
Can you post the image of the height map results?
-
@agniusm said in Creality CR-10 upgrade:
Is there a list of changes done to 1.21 as i just wasted a spool of filament.
The GitHub page for every release refers to https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md. Always read the upgrade notes for the release you are upgrading to and for any releases you have skipped.
-
@phaedrux I use G29 alone so it probes before each print.
I will get the map posted as my printer is away -
Can someone explane how to call macro file in start gcode? Asked this and still have no answer.
I am slicing with slic3r.
Putting:
M98 Pgantry_leveling.g
does not work. -
@agniusm You need to use the full path.
M98 P/macros/gantry_leveling.g -
Thank you. And its not this path:
M98 P/sys/gantry_leveling.g ? -
It depends on which folder you put the macro in. If you put it in /sys then you should not need to use the full path.
-
Had a chance to film my first layer.
Using Prusa 5V induction probe on precision aluminium plate.
Cant remember exact deviation on mesh map but its 0.07 max.
I am using gantry leveling as well.
I always get front right quarter of the bed too high. I am lost as dont know why it would not compensate. Those induction probes as per Tom's YT channel are ones of the most acurate ones.
If anyone could chime in and point my error? -
Is there any other metalwork near the front right corner that might be affecting the inductive sensor?
-
There is none. Its uniform. It has y carriage on 4 rail blocks. Bed is 8mm thick on 10mm standoffs from y carriage. Those induction probes are less sensitive to aluminium and my z offset is at ~0.2mm.
I know it should be far better than this.
I have enders with those uneven chinese heated beds running pinda's and they do work very good. Layers are smooth like butter.I have a script where it parks hotend 60mm abobe the bed, blows part cooling fan full whack and heats the bed to print temp, then goes for mesh mapping.
-
@agniusm said in Creality CR-10 upgrade:
Those induction probes are less sensitive to aluminium and my z offset is at ~0.2mm.
True; but they are much more sensitive to magnetic materials, such as non-stainless steel screws. They are also somewhat sensitive to temperature and supply voltage.
-
There is no fluctuation from psu, unless dwc readouts are inacurate. I have no protruding bolts and all of my fittings are stainless exept for the frame but they are far away.
I know that probes are sensitive to heat and thats why i have a script to move it out of the way while heating.
Here is my bed and whats underneath: -
So i have checked and rechecked and M98 does not work.
My macro file gantry_leveling.g is located in /Macros catalog and i place:
M98 P/macros/gantry_leveling.g
It reports that file is not found. Was this function tested and confirmed working?
Maybe there is syntax errors and rules that must be followed like space between P and path or CAP sensitive? -
M98 is known to work but it is Case sensistive!
did you try
M98 Pgantry_leveling.g
? -
Do you have any other characters on that line after the final ".g" ?
Are you certain that when you created the file, you didn't add an extra space after or before the filename?
You can also try:
M98 P"/macros/gantry_leveling.g"
or:
M98 P"gantry_leveling.g"
-
@dc42 : maybe update the wiki to reflect the fact that quotes are allowed for M98?
-
OK, will try your suggestions. I guess my error will be with Case.
I am sure i have no space after .gBTW, i think i have pinpointed my leveling issue.
I have printed holders for Z motors and my right motor was getting hotter than left one to the point it melted plastic. I have ordered longer motors and some 50x50x5 aluminium angle to fabricate some brackets.
I think it was just turning motor slightly so compensation was canceling out on melted saggy plastic.
Wow, that took me some time to notice. -
@whosrdaddy In addition to knowing quotes are allowed it would be nice to know when they are required.
Maybe I'm old school, but I always contain paths and strings in quotation marks. Especially if there is white space in it.
-
@phaedrux It would be good to have these notes. A lot of useres are beginners as myself and are not familiar with machine code and finding a refference and solution might be overwhelming sometimes.
-
It doesn't explicitly say where they can be used but there is a section covering quoted strings - https://duet3d.dozuki.com/Wiki/GCode#Section_Quoted_strings