You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since upgrading octodash to V2.2.0, activating the filament change, with config options set to M600, used to allow for a post change extrusion of any length as deemed by the operator. This amount was entered into the touch screen at the point immediately AFTER loading the new filament.
Since upgrading to v2.2.0, immediately after loading the new filament, the screen momentarily shows some kind of progress bar and instead of displaying a screen and asking for user input as to how much filament should be extruded before the hot end is cooled, it now just flashes and immediately starts to cool down.
Raspberry Pi 3B+
octoprint 1.6.1
Octodash 2.2.0
7” touchscreen
The text was updated successfully, but these errors were encountered:
Yes this screen was removed from the M600 option since M600 has a purge option on it's own. The general gist was that people, that are using M600 want as little intervention from OctoDash as possible, thus this screen was removed.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Since upgrading octodash to V2.2.0, activating the filament change, with config options set to M600, used to allow for a post change extrusion of any length as deemed by the operator. This amount was entered into the touch screen at the point immediately AFTER loading the new filament.
Since upgrading to v2.2.0, immediately after loading the new filament, the screen momentarily shows some kind of progress bar and instead of displaying a screen and asking for user input as to how much filament should be extruded before the hot end is cooled, it now just flashes and immediately starts to cool down.
Raspberry Pi 3B+
octoprint 1.6.1
Octodash 2.2.0
7” touchscreen
The text was updated successfully, but these errors were encountered: