Hi @GregValiant
You hit the spot, found the mistake, and it is working again.
I did not know that it was editable in Machine Settings!
Thanks, that makes it easy, but i think it is also gone after update.
Kind regards,
Tom
Hi @GregValiant
You hit the spot, found the mistake, and it is working again.
I did not know that it was editable in Machine Settings!
Thanks, that makes it easy, but i think it is also gone after update.
Kind regards,
Tom
If you alter the stock "Machine Settings" it gets noted in a .cfg file in the "app data\cura\5.3\definition changes" folder. When you update Cura that will get used when the printer moves to the new version.
Recommended Posts
GregValiant 1,409
It's a json file and coded much like Python. You must have the punctuation exactly correct (a tab character is not the same as a space character) and a correct new-line character between commands.
If you open the cura.log file you should find the exact error described.
If you alter the definition file - if/when you update Cura to the next version, you will lose your changes. The easy thing to do is just edit the StartUp and Ending gcode in the Machine Settings in Cura.
Link to post
Share on other sites