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
Is your feature request related to a problem? Please describe.
I'm using Octoprint at work to make our printers available to everyone using them over the network, which is a great improvement over the printer firmware's own quirks and also eliminates the SD card handling completely.
Sometimes the nozzle size is changed but not everyone's aware of the printers currently mounted nozzle, leading to failed prints and confusion.
Describe the solution you'd like
Octoprint has a property for nozzle size in the printer profiles. A widget displaying the nozzle size, pulling the data from the printer profile will allow me to always keep my colleagues up to date without asking questions back and forth.
Describe alternatives you've considered
At the moment I'm circumventing this issue by including the nozzle size in the printer name.
Thank you for considering implementing this feature.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm using Octoprint at work to make our printers available to everyone using them over the network, which is a great improvement over the printer firmware's own quirks and also eliminates the SD card handling completely.
Sometimes the nozzle size is changed but not everyone's aware of the printers currently mounted nozzle, leading to failed prints and confusion.
Describe the solution you'd like
Octoprint has a property for nozzle size in the printer profiles. A widget displaying the nozzle size, pulling the data from the printer profile will allow me to always keep my colleagues up to date without asking questions back and forth.
Describe alternatives you've considered
At the moment I'm circumventing this issue by including the nozzle size in the printer name.
Thank you for considering implementing this feature.
The text was updated successfully, but these errors were encountered: