G31 doesn't work anymore, why? :(
-
Are you running the nozzle to the bed until it holds a piece of paper and then G92 Z0 first before G30 S-1?
I have gone as far as copying G31 from config.g to override and bed.g files and it seemed to fix my pre-print bed probing.
-
Are you running the nozzle to the bed until it holds a piece of paper and then G92 Z0 first before G30 S-1?
I have gone as far as copying G31 from config.g to override and bed.g files and it seemed to fix my pre-print bed probing.
Yes, but with Z-10 in G31 I should be able to put my finger between the bed and the nozzle at Z0 after calibration
-
Ok, just ran a test. The only way I could get m665 to report 10mm lower was to have the -10 in the bed.g folder.
That is -10 + the 3.336 real offset.
-
If modifying the G31 command in config.g has no effect then it is probably being overridden by the one in config-override.g. So instead of editing config.g, send the new G31 command from the console. Then run M665 or whatever you need to test the new value. When you are happy with the new G31 values, send M500 to save it to config-override.g.
-
I can't test right know (work :)). But first of all your right there are G31 lines in configuration override! I don't know exactly why
I'll clean these 3 lines and do G31 by console and M500.
Is there any command that could have add these G31 in config-override? The point of my question is to know if its just bad input I've made in the past, that stacked until today.
Once cleaned up could I just rely on config.g or should I put G31 X0 Y0 Z-0.15 in bed.g and manage first layer tuning from there (bed.g)?
[[language]] ; Z probe parameters G31 T1 P500 X0.0 Y0.0 Z-0.10 G31 T3 P500 X0.0 Y0.0 Z0.70 G31 T4 P500 X0.0 Y0.0 Z0.00 ```; Z probe parameters in config-override.g -
Any time you use M500 it will write the current settings for G31, M307, M665 and a few other parameters to config-override.g.
Whether you want to use config-override.g is up to you. If you don't, then remove the M501 line from config.g.
-
Any time you use M500 it will write the current settings for G31, M307, M665 and a few other parameters to config-override.g.
Whether you want to use config-override.g is up to you. If you don't, then remove the M501 line from config.g.
OK I'll keep on with config-override, I'll manage G31 in bed.g I think it'll do the trick. I'll give my feedback here once tested.
EDIT : changed the title of the thread for search purpose in the future
-
Well after putting my G31 in bed.g, and tune the value from here, every is fine
Note : don't forget M501 in config.g and using M500 after bed leveling or directly put M500 at the end of beg.g
-
Using M500 / M501 to write to config-override.g (like older firmware used to write certain settings to EEPROM) is personal taste. Originally i did not like the idea as I prefered to edit config.g with the new settings. Recently I have started to use it a lot as its just so easy to type M500 after I have done delta calibration.
-
Using M500 / M501 to write to config-override.g (like older firmware used to write certain settings to EEPROM) is personal taste. Originally i did not like the idea as I prefered to edit config.g with the new settings. Recently I have started to use it a lot as its just so easy to type M500 after I have done delta calibration.
Same here, I think m500/501 is a good feature when you change often of nozzle, in my case I swap to Volcano or tungsten nozzle often, it's more convenient to work without rebooting the board after modifying config.g. But it's personnal taste.
