I'm marking this as solved. We were able to accomplish what we wanted through dsf-python as @chrishamm suggested.

For posterity, see this thread: https://forum.duet3d.com/topic/26090/dsf-python-script-to-monitor-sbc-and-log-results-through-dsf

I second this. I am afraid every time I open up my mobile DWC view. E-stop should be intentional but easily accessible. It should not at all be prone to accidental triggering.

I agree that the button should be moved off to the side, or the bottom of the navigation tray. At the very minimum, it should be inset the width of the hamburger button to prevent accidental double-presses.

I still think it would be really nice to have.

If it existed, it would already be in the start-up gcode of every print i do.

@exerqtor I totally agree with you... That would be very useful

@deckingman said in A single fan appears twice in DWC?:

There is clue in the name (Duet Web Control).

The fans are displayed in the Status page.

😉

@jay_s_uk AMAZING! Thank you so much

@fcwilt @JNB you could use BTN CMD for it i think

@zapta Will do!

@lee7670 Id really like this too. Im having trouble trying to see what is causing my printer to throw a heater fault since its only happening every 20+ hours of operation so the data on the temperature graph is lost.

@sindarius said in 3D GCode Viewer integrated with DWC:

I’ll need to look i believe the code currently uses the machine position and not the tool position which could be the issue.

@sindarius Did you have a chance to look into this?

I was working on someone else's E3D tool-changer today and experienced the same thing, so I wanted to check in.

DWC & Firmware Version: 3.3

@resam A capital -X works better on the wget command line. But it didn't download all the subfolders until I added -l 0.

@phaedrux In that case I sincerely hope I will never ever have to cope with whomever you label as "beginner" 😆

FWIW,
'Emergency stop' means just that. Stop NOW.
What I suggested is a confirmation for a non emergency abort which is a totally different kettle of rabbits.

@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?

@phaedrux said in what if Macros appeared in Console?:

Not a bad idea. Moved to the wishlist.

While we are talking about wishlist in macro-context:
I tested a few things in macros and from time to time I made syntax errors or typos in variable names.
A vague warning popped up in the console about these errors, not naming the macro they happened in.
Was it t#free.g, t#pre.g or t#post.g?
Happy searching...