Show M950 J-inputs
-
Using M950 one can setup various J-inputs. This could for example be used for tool detection (are all tools docked). These J-inputs can then later be used as source for M581 triggers.
For debugging purposes, and for general overview (such as on a toolchanger), it would be nice if DWC would show the current state of these J-inputs.
This could be designed as an extra line in the status-box (below "speeds" and "sensors") where it shows J0, J1, J2, ... (as configured) together with there state. As an alternative it could be added in the tools-box under the "extra" part. This first (inside the status-box) would be preferred to have it always visible.
-
@khenderick, you can see the current state if you go to the Object Model browser in DWC and navigate to sensors.gpIn.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 This is indeed interesting for debugging, nice
.For a more general overview, another solution could be to implement something more generic where certain entries of the object model could be persisted on the dashboard (either with manual refresh or some kind of automatic refresh (e.g. every second, every 5 seconds, ...)).
-
Sounds like a candidate for a DWC plugin.
-
@khenderick said in Show M950 J-inputs:
For a more general overview, another solution could be to implement something more generic where certain entries of the object model could be persisted on the dashboard
I believe, you could poll the sensors in question with M582 in daemon.g and send an echo to your screen with the result?
