PID Tuning on the Mini?
Hi folks,
I want to run some tests on my Mini, and PID tuning is part of my plan.
Was originally planning to hook the Mini up to my PC and just run Pronterface to get a decent tuning profile and send a M500 to save it. But However, we can't save gcode to the EEPROM on the Mini - does that mean PID tuning is impossible?
Kind regards,
Dennis
PID values on Mini
You can add the PID values into your Start gcode, so it's automatically added to your Gcode when you slice models
regards joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
PID can be saved I guess
Hi Joan,
Thanks for your reply. I actually found this post just now: https://forum.prusa3d.com/forum/general-discussion-announcements-and-releases/4-0-5-firmware-for-original-prusa-mini-2/ and it states:
Any specific adjustment of those values should be part of the G-code. The only variables from Marlin allowed to be stored in the EEPROM are the Live Adjust Z and PID calibration.
So I think just sending an M500 through Pronterface will actually work!
have fun!
Best of luck,
As I don't have a Mini, I can't try it.
regards joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
I'm 99% certain M500 doesn't work on the Mini. So I have my PID values in the startup gcode for the mini.
Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...
The only variables from Marlin allowed to be stored in the EEPROM are the Live Adjust Z and PID calibration.
-I think this needs clarification. M500 doesn't work for Mini -that's a fact.
For example, if you do First layer calibration, then new Z-offset is saved into EEPROM, right? Because it's saved by Prusa firmware. Same is true for PID: if you execute PID tuning, then new values will be stored the same way -of course only until you execute "Reset to factory defaults".
However you can't store PID (or any other parameter) into EEPROM directly, because Mini's original firmware skips M500 code that's coming from outside (via terminal/Pronterface).
[Mini+] [MK3S+BEAR]
Automatically stored vs can be stored with M500
[...] So I think just sending an M500 through Pronterface will actually work!
I haven't gone through the Mini firmware source code, but I suspect it's more of a case that "Live Z adjustment and PID tuning results are automatically stored". My understanding is that M500 is not implemented. In this case, it's not needed to save either of those settings. Unfortunately, I can't test to confirm.
and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan
RE: PID Tuning on the Mini?
Can anyone please show where exactly to add the codes in PrusaSlicer? Thank you very much.
RE: PID Tuning on the Mini?
Note the section 'Thermal regulation for custom extruders' in the release notes for firmware 4.3.3: https://github.com/prusa3d/Prusa-Firmware-Buddy/releases/tag/v4.3.3.
Long story short; PID tuning is unnecessary for the Mini.
RE: PID Tuning on the Mini?
Thank you!