@mintytrebor Works perfectly, thanks a lot!

@mfs12 When I try to collect accelerometer data for my Y-Axis my Duet3 6HC crashes and reboots after doing the first two Y-Axis moves. Strangely, it works flawlessly on the X-Axis.

EDIT: After power cycling, it works again on both axis. I will keep an eye on this. 😁

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0beta5 (2021-10-12 13:53:56) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J1F8-3S86J-9B3LF
Used output buffers: 1 of 40 (17 max)
=== RTOS ===
Static ram: 151104
Dynamic ram: 69036 of which 0 recycled
Never used RAM 130460, free system stack 200 words
Tasks: ACCEL(notifyWait,0.0%,348) SBC(resourceWait:,0.8%,508) HEAT(notifyWait,0.0%,327) Move(notifyWait,0.0%,276) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,351) TMC(notifyWait,7.9%,92) MAIN(running,87.6%,921) IDLE(ready,3.6%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:07 ago, cause: software
Last software reset at 2021-10-15 18:50, reason: HeatTaskStuck, GCodes spinning, available RAM 130416, slot 1
Software reset code 0x4143 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0040080f BFAR 0x00000000 SP 0x20435b44 Task ACCE Freestk 348 ok
Stack: 00449c51 00449c46 61000000 20435488 20435488 00000006 ffffffe8 0049c018 204240b8 00000003 00477329 204354aa 20435488 00000007 000003e8 0000000a 004773b5 00000007 20419130 000003e8 00476805 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
Error status: 0x00
Step timer max interval 129
MCU temperature: min 54.3, current 55.0, max 55.1
Supply voltage: min 4.5, current 23.9, max 24.0, under voltage events: 1, over voltage events: 0, power good: yes
12V rail voltage: min 3.9, current 12.0, max 12.6, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: pos 0, standstill, SG min/max 0/0, reads 38481, writes 27 timeouts 0
Driver 1: pos 0, standstill, SG min/max 0/0, reads 38482, writes 27 timeouts 0
Driver 2: pos 0, standstill, SG min/max 0/0, reads 38482, writes 27 timeouts 0
Driver 3: pos 0, standstill, SG min/max 0/0, reads 38482, writes 27 timeouts 0
Driver 4: pos 0, standstill, SG min/max 0/0, reads 38484, writes 25 timeouts 0
Driver 5: pos 0, standstill, SG min/max 0/0, reads 38484, writes 25 timeouts 0
Date/time: 2021-10-15 18:51:26
Slowest loop: 1.84ms; fastest: 0.04ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 3, maxWait 4428ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 2, completed 2, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon* is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 80, received 335, lost 0, longest wait 1ms for reply type 6018, peak Tx sync delay 5, free buffers 49 (min 48), ts 36/35/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
State: 4, failed transfers: 0, checksum errors: 0
Last transfer: 2ms ago
RX/TX seq numbers: 25316/305
SPI underruns 0, overruns 0
Disconnects: 0, timeouts: 0, IAP RAM available 0x2b7dc
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.4-b5
Code buffer space: 4096
Configured SPI speed: 8000000Hz
Full transfers per second: 36.35, max wait times: 48.2ms/24.3ms
Codes per second: 1.19
Maximum length of RX/TX data transfers: 6564/1320

@t3p3tony said in Gcode viewer:

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

ACC from duet

20211008_124901.jpg

IS Plugin

20211008_124942.jpg

Sorry for the Bad Picture Quality

@zapta said in Another weighing filament holder:

Very nice!

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...

@peirof also BtnCmd https://forum.duet3d.com/topic/22776/btncmd-dwc-plugin-create-custom-layouts-action-buttons?_=1629783324948

@jay_s_uk Thanks, now updated: https://github.com/Duet3D/DSF-Plugins/releases/tag/v3.4-b2

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.

@chrishamm will have to take a look at your question when he gets a chance.