GregValiant 1,110
Thanks for that. You actually the first person to get back to me on whether there were any problems running it on other machines.
I have a question in regards to where that error occurs...Does your printer use "Jerk" or "Junction Deviation"?
Recommended Posts
GregValiant 1,110
M201 is MAX Accel. M205 is Jerk. There is no "Max" for Jerk.
If you enable Acceleration control in Cura and if you enter 5000 for X and 5000 for Y within Printer Settings you would be allowed to enter up to 5000 for any acceleration setting in Cura without the box turning red. Cura would use those Accel numbers in its calculations and it is what Cura would put in the gcode file in an M204 line.
But when your printer sees the M204 P5000 T5000 line it would say "Whoa...No Way" because internally M201 says Max X and Y acceleration is 750 and that is what the printer would use in IT'S calculations and the Cura estimate goes out the window. That's usually where the time discrepancy comes from.
With Pronterface you can send
M201 X5000 Y5000
M500
The Max acceleration of the printer would become 5000 for X and Y and would be saved as the new default. If your printer is a "bed slinger" like my Ender 3Pro then 5000 is much too high for the Y but if you were to do that and set the accel in Cura to 1000 then the Cura estimate would be closer to reality as the printer would use 1000 because it would be below the new Max. Both Cura and the printer would be using the same numbers (although maybe somewhat differently). I ain't saying this is perfect.
And then there is Jerk. Jerk units are mm/sec and if you think about it as minimum speed around a corner it's easier to get your head around it.
This post processor was written by someone else. It was never submitted to Ultimaker for inclusion into Cura. I use it and I like it because it has a "Fudge Factor" to adjust the Cura estimate to what the printer is actually doing.
ShowProgress.zip
Unzip the file and copy "ShowProgress.py" to "C:\Program Files\Ultimaker Cura 5.1.0\share\cura\plugins\PostProcessingPlugin\scripts". It will be available for you to load as a Post Processor.
The fudge factor is "[Cura estimate]/[actual print time]". Figure it out and enter it in the proper box. A much closer estimate of time remaining should appear on the LCD via an M117 line added to the gcode. Mine looks like: 1/180 | ET 30M. I also added an M118 line so if you use it and have Pronterface running it bounces the same line back to Pronterface.
Next, if you are running Windows I wrote this little app as a test for Accel and Jerk. It's interesting and may give you some insight into what your printer can actually handle. You have to be careful and start slow. It is possible to unlock the MAX values and to put in numbers that are high enough to hurt your printer. Some printers can handle much higher accelerations than others.
Here is the download link to the aptly named
Greg's Accel and Jerk Tool which is for Windows only and for Marlin type firmware.
you can use it instead of Pronterface (it has a textbox for printer responses) and to print from the SD card IF the app works correctly for you.
Link to post
Share on other sites
stuart264 1
Thank you, I plugged in some of those settings, and they look about right. That utility is a handy bit of software. Though unfortunately I cannot get the Accel and Jerk options to work as every time I try to load I get an error message below about Length must be greater than or equal to zero. But the Accel and Jerk tool in "Movement and Levelling" works fine.
Link to post
Share on other sites