@jens55 also moved this to the plugins category and tagging @Sindarius in this as the developer. A potential feature would be to show the gcode being executed.
Thanks, I had a look see at the gcode viewer before I posted my question. I couldn't make much sense out of it - it was not at all intuitive. It did seem clear however that it did not meet my code display requirements so I did not attempt to wrap my mind around it.
I am hoping there might be something available that shows the gcode.
Can it also be used as a filament sensor, detecting jams and such?
Not reliably, I think.
My filament spool at least exhibits quite marked stick-slip, so when printing it doesn't decrement smoothly with print progression. In my setup the spool is on top of the printer and the filament feeds off almost vertically downwards. When printing, as the extruder feeds and filament is used, the weight reading creeps slowly upwards as the filament between spool and extruder is pulled in, then the spool slips and it drops down again before creeping upwards. The graph would be a saw-tooth on a slow downwards trend. I think by the time you could be confident the behaviour was adrift, the print would already be scrap.
While testing I did a lot of swapping spools to and fro, and got a bit slap-dash. I managed to introduce a filament tangle and got almost a kilogram of tension in the filament. The scale was weighing nearly 1000, even though I only had about 50g filament on that spool (hence tangle - it was all loosely looped). I guess you could detect that happening and pause if the weight ever builds up slowly to a much-higher-than-expected value, but that happens so rarely I don't think it's worth it.
It's really just to save the uncertainty of 'is there enough filament' at the start of a print.
@resam ...I simply tried renaming js to dwc and it worked... apparently if uploaded to the controller through DWC, it throws js files into the js directory and CSS into the css directory. Not sure what it does if you use a more complicated structure for some reason...
Thanks everyone for their replies! Currently I found a rather magical way to try things out: I made a sort of VPN with the printer (at another location) with my PC. I used my own SSH port forwarding tool for this (https://github.com/peterwilli/Ghoster) and so far I can open DWC and install plugins as if the printer is in my own home!
@chrishamm At this point I probably should admit that I am not using the DuetPi image - but installed everything from the Duet apt repos into my existing Pi... but the systemd service files are the same - so their Before/After dependencies should be correct as you wrote them.