-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access PID Autotune from LCD #3135
Comments
Step a) would be to extend M303 with a parameter to actually use the new values instead only displaying them. That's not too complicated. An extra cool feature could be temperature dependent PID tables, using different parameters for different target temperatures |
Also nice would be for PID values to be loaded for the tool in operation instead of using a single set of PID values for all tools. These values could be loaded during tool change, something which you can actually do using most slicers already, but might be nice to have the firmware handle it. Also, if the inactive tool drops out of range while different PID values are in operation for the active tool, that probably shouldn't trigger a halt situation (not sure if that happens right now, I'm a little new to this) |
I am thinking about trying to implement this, but I wonder what extra parameter you think I should use in step A above. U maybe for Use? And also, should it save it to EEPROM or only use it temporarily? |
I would say temporary; it can always be stored with Store Memory. U seems like a sensible choice; intuitive. As long as this isn't used for other, conflicting meanings. Another idea would be perhaps to make it M3031? Elsewhere it seems like alternate numbers are used to distinguish between do and save. |
Temporary is probably right. Another code would probably be the best potion, but can you really have codes higher than 999? I'm not sure since I'm pretty new to this. |
Adds the parameter U to M303. If U1 is included , it will use the PID-values from the auto-tune.
|
Added a menu-element under the Temperature-menu to auto-tune the PID-regulators for the temperatures
This feature has been merged into |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
It would be great if there was an option, perhaps from the "Prepare" menu, to run PID Autotune and read off the results from that on screen. While not absolutely vital to success, having PID tuned for your printer and environment leads to much tighter control of the hot end temperature and more successful first time prints. Once you have these numbers, you can choose to push them into your own firmware build or run them as part of your GCODE starting script. This would be nice to do as part of the commissioning process of a printer, prior to actually hooking up other tools that give you access to a GCODE terminal.
The text was updated successfully, but these errors were encountered: