Posts made by jltx

Ok I did the following which unblocks me for macros. Let me know if it is wrong.
chown -R dsf:dsf /opt/dsf/sd/*

What do I need to change to start DWC automatically?

here is the M122 from the new system:

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.4 (2024-11-24 10:44:24) running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: RNXYU-8296U-D65J0-40KMW-2503Z-ZP7HW
Used output buffers: 1 of 40 (17 max)
=== RTOS ===
Static ram: 103496
Dynamic ram: 117260 of which 0 recycled
Never used RAM 18068, free system stack 135 words
Tasks: SBC(2,ready,1.7%,813) HEAT(3,nWait 1,0.1%,323) Move(4,nWait 6,0.0%,285) CanReceiv(6,nWait 1,0.0%,939) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,334) TMC(4,nWait 6,1.5%,81) MAIN(2,running,95.9%,757) IDLE(0,ready,0.0%,29) AIN(4,delaying,0.8%,264), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 04:23:49 ago, cause: power up
Last software reset at 2025-02-04 08:05, reason: User, Platform spinning, available RAM 22812, slot 2
Software reset code 0x6000 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 11872475, completed 11872474, timed out 0, errs 0
MCU temperature: min 16.2, current 23.7, max 26.4
Supply voltage: min 0.2, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/8/8, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 62715, writes 12, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 19, reads 62708, writes 19, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 19, reads 62708, writes 19, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 19, reads 62708, writes 19, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 62717, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 19, reads 62708, writes 19, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 19, reads 62708, writes 19, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2025-02-04 17:01:41
Cache data hit count 4294967295
Slowest loop: 233.24ms; fastest: 0.11ms
=== Storage ===
Free file entries: 20
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 3604118ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 14, completed 14, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
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, chamber heaters 3 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, 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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000803
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 142282, received 0, lost 0, errs 74830674, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 26 (min 26), ts 79150/0/0
Tx timeouts 0,0,79149,0,0,63131 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 28567/36292
SPI underruns 0, overruns 0
State: 5, disconnects: 2, timeouts: 2 total, 2 by SBC, IAP RAM available 0x0cd20
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server version 3.5.4 (2024-11-25 17:32:26, 64-bit)
HTTP+Executed:

Executing M122
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 2
Full transfers per second: 22.43, max time between full transfers: 9506.9ms, max pin wait times: 4331.9ms/12.7ms
Codes per second: 0.10
Maximum length of RX/TX data transfers: 4436/936

@chrishamm I attempted to do that on the lite version. I used the RPI imager and entered all the credentials. Something did not go right because the first boot hung. I pulled the SD card and, thinking it never connected to network because I could not reach it via ssh, I added the wpa_supplicant file. It worked on the next boot. I read that wpa file doesn't work on bookworm so not sure what changed for the next boot. One thing that did work is it copied the backup *.g files over from the boot partition and the printer started up. See next.

My full install also has issues. It booted to the Duet splash screen for a while doing things and eventually dumped me into some linux desktop environment. The printer never started nor DWC. Investigating I found that none of the *.g files were copied over from the boot partition. So I sftp'd them over and got the printer going. I have to start the DWC manually on every boot, it never starts on its own. Also, I cannot access some of the *.g files through DWC because it says I don't have permission. I used -P to preserve attributes but something went awry. Not sure what the proper chown or chmod to use to fix it.

I can install some plug-ins in this new setup but not all. For example the btn_mgr and release_manager fail prerequisite check, but say I need the version I have. Input shaping says the manifest is bad. So still stuck at an incomplete state.

BTW, in both cases, the lite and full, the img I downloaded from the document page is inconsistent in that it installs a mix of 3.5.4 and 3.5.3 sw. I have to immediately apt update/upgrade to get things aligned.

this was a headless configuration. I set up a new SD card with the full install for an attached display. This one let me install the plug-in even though it is labeled 3.5.1 and I'm on 3.5.4. So maybe something is missing from the headless bundle.

This is a mini 5+ board with SBC. I'm on 3.5.4 for all.

M98 P"config.g" produced no output

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.4 (2024-11-24 10:44:24) running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: RNXYU-8296U-D65J0-40KMW-2503Z-ZP7HW
Used output buffers: 1 of 40 (17 max)
=== RTOS ===
Static ram: 103496
Dynamic ram: 116664 of which 0 recycled
Never used RAM 21588, free system stack 208 words
Tasks: SBC(2,rWait:,1.3%,801) HEAT(3,nWait 1,0.1%,323) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.0%,939) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,334) TMC(4,nWait 6,1.5%,110) MAIN(2,running,92.4%,757) IDLE(0,ready,4.0%,29) AIN(4,delaying,0.8%,264), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:02:05 ago, cause: power up
Last software reset at 2025-02-02 15:07, reason: User, Platform spinning, available RAM 21564, slot 0
Software reset code 0x6000 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 94373, completed 94373, timed out 0, errs 0
MCU temperature: min 19.9, current 20.3, max 28.6
Supply voltage: min 1.0, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 11358, writes 12, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 11356, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 11356, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 11356, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 11360, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 11356, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 11356, writes 13, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2025-02-03 09:58:17
Cache data hit count 272063535
Slowest loop: 5.59ms; fastest: 0.13ms
=== Storage ===
Free file entries: 20
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
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, chamber heaters 3 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, 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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000803
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 995, received 0, lost 0, errs 593551, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 26 (min 26), ts 629/0/0
Tx timeouts 0,0,628,0,0,365 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 4026/4026
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x0cd20
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server version 3.5.4 (2024-11-25 17:32:26, 64-bit)
HTTP+Executed:

Executing M122
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 0.09, max time between full transfers: 57.9ms, max pin wait times: 45.3ms/4.2ms
Codes per second: 0.00
Maximum length of RX/TX data transfers: 4440/932

I either get blocked from installing by version discrepancy, e.g. 3.5.2 vs 3.5.4 or it loads and disappears into the void with zero feedback. Not a single plugin works. Everything else in DWC appears to work including internal plugins. What am I doing wrong?

Does the tool board come with uncrimped pins or do I need to source those myself? e3d told me the leads on the Roto extruder are 1m long so I would need to remove 90% of the wire and reposition the connectors to use this tool board mounted locally.

Does the roto toolboard come with scanning z probe coils? I don’t see where to get those separately.

@sebkritikel Awesome news! Thank you.

I read that reprapfw input shaping does not support mixing steppers between main board and stepper remote on can bus. The tool boards that control an extruder are on can bus. I need input shaping to control axis and extruder steppers together. So how does this work? Did I read that wrong (I hope)?

@dc42 I did check the console and it had no errors reported. But I’m not clear that it captures anything when my laptop is asleep. I feel like it skips over anything incoming while asleep.

Is there a mode I can set the treats M0 like M1? I can’t ever think when I’d use M0. I never have before. More likely I think is your theory on SD read error (though I don’t know what that would happen either, just more likely). But wouldn’t that get captured in M122? Also the failure mode there should be a pause by firmware to allow for restart, e.g don’t turn off bed heater or motors and send warning. I was lucky that I happened to catch it. I was about to go to bed and it would have been ruined the next morning.

@dc42 no errors in console. I have a 12864 display. If an errant M0 were somehow emitted would that status screen show 100% complete?

@jltx @dc42 is this a known failure mode? can firmware detect and report? I'm hesitant to start any long prints now.

@bot I don’t know how to read that log either. Driver 5 is also only one with a timeout, so may be a real issue.

Driver 4 is unused which might explain the read error there.

I forgot I took a screenshot at failure. Notice it thinks it is 100% complete, though Z is 25 when final should be 66 for this print. The heaters are off but have active temps. I have not seen that before.

I noticed my printer was awfully quiet and when I checked I found it had just stopped with the head parked in the middle of doing some infill. The heaters had shut off and were cooling. The 12864 had some conflicting info where it showed the heaters still on but they were not, but otherwise showed printer was in a non-printing state. I checked DWC and found no errors. The status page said job completed but clearly it was not. I dumped a M122 shown below.

Luckily I was able to use M114 and G92 in a hacked gcode to recover the last 7 hours of the print. But I’m disturbed that it just ended early without errors. I just simulated the original file and it completed without error. The line it stopped on during the print was in a stretch of uninteresting G1 commands. Any other areas to investigate?

1/3/2022, 11:13:36 PM: M122: === Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.0beta7 (2021-12-16 12:22:56) running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: RNXYU-8296U-D65J0-40KMW-2503Z-ZP7HW
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 103460
Dynamic ram: 104412 of which 0 recycled
Never used RAM 30144, free system stack 118 words
Tasks: SBC(ready,138.9%,480) HEAT(notifyWait,1.3%,342) Move(notifyWait,87.1%,273) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,358) CanClock(delaying,0.4%,331) TMC(notifyWait,37.6%,105) MAIN(running,121.3%,484) IDLE(ready,0.2%,29) AIN(delaying,25.3%,264), total 412.1%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 29:39:08 ago, cause: software
Last software reset at 2022-01-02 23:34, reason: User, none spinning, available RAM 30824, slot 2
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00487000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 106756829, completed 106756829, timed out 0, errs 0
Step timer max interval 1479
MCU temperature: min 20.8, current 22.1, max 32.2
Supply voltage: min 23.7, current 23.9, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/84/84, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: pos 31583, standstill, SG min 0, read errors 0, write errors 1, ifcnt 105, reads 2294, writes 14, timeouts 0, DMA errors 0, CC errors 0
Driver 1: pos 10279, standstill, SG min 0, read errors 0, write errors 1, ifcnt 188, reads 2287, writes 21, timeouts 0, DMA errors 0, CC errors 0
Driver 2: pos 20360, standstill, SG min 0, read errors 0, write errors 1, ifcnt 188, reads 2287, writes 21, timeouts 0, DMA errors 0, CC errors 0
Driver 3: pos 0, standstill, SG min 0, read errors 0, write errors 1, ifcnt 188, reads 2286, writes 21, timeouts 0, DMA errors 0, CC errors 0
Driver 4: pos 0, standstill, SG min 0, read errors 1, write errors 1, ifcnt 59, reads 2298, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 5: pos 0, standstill, SG min 0, read errors 0, write errors 1, ifcnt 188, reads 2286, writes 21, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6c
Driver 6: pos 0, standstill, SG min 0, read errors 0, write errors 1, ifcnt 188, reads 2286, writes 21, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2022-01-04 05:13:35
Cache data hit count 4294967295
Slowest loop: 1057.14ms; fastest: 0.09ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 35, maxWait 31364ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 5538039, completed 5538039, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], 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, chamber heaters 3 -1, ordering errs 0
=== 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 960761, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 533744/0/0
Tx timeouts 0,29,533743,0,0,426986 last cancelled message type 4514 dest 127
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 31931/31931
SPI underruns 0, overruns 0
State: 5, disconnects: 1, timeouts: 1, IAP RAM available 0x0f918
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.4-b7
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 41.80, max time between full transfers: 48.2ms, max pin wait times: 32.3ms/10.7ms
Codes per second: 0.00
Maximum length of RX/TX data transfers: 3528/132

@fcwilt
That's clever. I'll have a think about that.

@phaedrux said in mesh results inconsistent with leveling:

Does that mean the probing is done cold?

No, you can probe whenever you want. I really don't know why that designed it that way.

@zapta I looked at klicky but I don’t think I have enough room. Unless the magnetic sled can discriminate only a few mm for pick up I will lose part of my rear bed trying to avoid accidental mounting.

@phaedrux i believe they use a hybrid setup because the inductive probes are very sensitive to temperature. If I were to ignore the endstop and try to just use the probe I would have no way to actually set Z=0, at least no confidence that I was anywhere close at a given temp. The endstop can move a little too with thermal expansion but it seems pretty small by comparison.

@gloomyandy @fcwilt I’m still not clear on the purpose of the Z=0. Maybe the confusion is I have a Voron with a mechanical Z end stop that is used to set the tool Z relative to bed. The inductive probe is only used to level the bed and probe a mesh for bed correction. All of that is relative. Do I need this extra step of Z=0? What exact command would that be? Since I’m not currently doing that, what bad things might happen? I appreciate the help.