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
Great plugin - very intuitive and works as needed, bar automation.
In an ideal world, I'd love it if this plugin was capable of turning a relay off upon print completion.
Would be great if the backend of this was ported into a child plugin for PSU control, or alternatively the automation/running detection features from that plugin ported into your plug-in.
Couldn't think of a way to reach out better than GitHub. Feel free to close this issue post-haste if it's beyond your appetite for developing this tool further.
Thanks
The text was updated successfully, but these errors were encountered:
It does indeed sound like a good idea that this would be done, but I think it's probably beyond my abilities (or possibly just beyond what I've got time to do). I don't really have a need for turning a relay off at the end of a print (I just use it to control some lights, which I turn on/off manually when I want to look in on a webcam). I originally used GCODE System Commands to run a command line script to turn stuff on / off, but I wanted to have a button in OctoApp and that meant it needed to be a plugin.
I'll leave this open in case anyone (e.g. you 😊) wants to contribute any code to add this capability; alternatively I'm happy to help talk through porting it into a new plugin if you want to have a go. This was my first (and, so far, last!) ever attempt at a plugin for OctoPrint and it was mostly just a mish-mash of the two projects linked at the bottom of the README. As such it may be easier to base a PSU control child plugin on those source projects rather than basing it on mine.
Hi!
Great plugin - very intuitive and works as needed, bar automation.
In an ideal world, I'd love it if this plugin was capable of turning a relay off upon print completion.
Would be great if the backend of this was ported into a child plugin for PSU control, or alternatively the automation/running detection features from that plugin ported into your plug-in.
Couldn't think of a way to reach out better than GitHub. Feel free to close this issue post-haste if it's beyond your appetite for developing this tool further.
Thanks
The text was updated successfully, but these errors were encountered: