Posts made by Serbitar

undefined

In SBC mode, thanks for looking at it!

undefined

When you run abort in either a macro or just directly in DWC you get the error

abort
Error: expected an expression

The documentation defines abort as

Abort command

abort <opt-expression>

This causes all nested macros and the current print file (if any) to be terminated. The expression (if present) is converted to a string, which is included in the message presented to the user and written to the log file.

So the expression should be optional. I have not seen any mention of this being changed in the changelog.

Is this a planned change or a bug?

undefined

@jay_s_uk No worries! Do you have a thread or somewhere else to discuss the code?

My question regarding recovery from failed changes is still not resolved.
I changed the error code to

M25
abort

And this still results in the firmware getting stuck when attempting manual recovery.

undefined

@jay_s_uk Oh thats a nice approach, thanks!

undefined

Hi

Not sure this is specific to 3.6.0-rc1 but that's the version I am currently running.

I am trying to set up a auto filament changing system like a box turtle.
In my testing occasionally the filament fails to properly swap for whatever reason.
I have switches at several points along the filament path so detecting a failed swap is easily possible.

The swaps are being done in tool change macros tfree and tpost. When an unexpected state is found, currently the macros call

T-1 P0
M25

This correctly deselects the tool and pauses the printer.
However when trying to recover the state manually in DWC by selecting a tool with T3 or just resuming the print with the resume button on the status page the UI just spins forever.

Hardware is a Duet3 mini in SBC mode with a MB6HC 1.0 as fd-can expansion (yeah I know this sounds backwards but its how the machine evolved).

I couldn't find any examples of aborting a tool change and allowing manual recovery. Am I doing something silly or is there something that needs improving in the firmware?

Thanks

=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.6.0-rc.1 (2025-02-28 14:59:42) running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: W4ZW4-V296U-D65J0-40KM0-LR03Z-H6928
Used output buffers: 1 of 40 (19 max)
=== RTOS ===
Static ram: 94764
Dynamic ram: 89564 of which 228 recycled
Never used RAM 44864, free system stack 132 words
Tasks: SBC(2,nWait 7,2.2%,700) HEAT(3,nWait 6,0.0%,325) Move(4,nWait 6,0.1%,247) TMC(4,nWait 6,1.5%,65) CanReceiv(6,nWait 1,0.0%,814) CanSender(5,nWait 7,0.0%,335) CanClock(7,delaying,0.0%,348) MAIN(1,running,94.9%,683) IDLE(0,ready,0.4%,29) USBD(3,blocked,0.0%,147) AIN(4,delaying,0.8%,261), total 100.0%
Owned mutexes: Aux(MAIN)
=== Platform ===
Last reset 00:40:28 ago, cause: software
Last software reset at 2025-03-20 21:01, reason: User, Platform spinning, available RAM 56288, slot 2
Software reset code 0x2000 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a
=== 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 ===
Segments created 502, maxWait 113293ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00/0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 1217.00/1216/1.00 -11501.00/-11500/-1.00 -1215.00/-1216/1.00
No step interrupt scheduled
Driver 0: standstill, SG min 0, r/w errs 0/2, ifcnt 19, reads/writes 23470/34, timeouts 0, DMA errs 0, CC errs 0
Driver 1: standstill, SG min 0, r/w errs 0/2, ifcnt 19, reads/writes 23470/34, timeouts 0, DMA errs 0, CC errs 0
Driver 2: standstill, SG min 0, r/w errs 0/2, ifcnt 21, reads/writes 23466/36, timeouts 0, DMA errs 0, CC errs 0
Driver 3: standstill, SG min 0, r/w errs 0/2, ifcnt 15, reads/writes 23474/28, timeouts 0, DMA errs 0, CC errs 0
Driver 4: standstill, SG min 0, r/w errs 0/2, ifcnt 11, reads/writes 23484/20, timeouts 0, DMA errs 0, CC errs 0
Driver 5: standstill, SG min 0, r/w errs 0/2, ifcnt 11, reads/writes 23482/20, timeouts 0, DMA errs 0, CC errs 0
Driver 6: standstill, SG min 0, r/w errs 0/2, ifcnt 11, reads/writes 23482/20, timeouts 0, DMA errs 0, CC errs 0
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.2
=== GCodes ===
Movement locks held by File, null
HTTP* is doing "T1 P0" in state(s) 0
Telnet is idle in state(s) 0
File* is idle in state(s) 0 0 0 7, running macro
USB is idle in state(s) 0
Aux* is doing "M122" 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
=== CAN ===
Messages queued 25380, received 19462, lost 0, ignored 0, errs 1, boc 0
Longest wait 1ms for reply type 6042, peak Tx sync delay 375, free buffers 26 (min 25), ts 11509/11508/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 27248/27248
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x14878
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server version 3.6.0-rc.1 (2025-03-03 12:11:46, 32-bit)
HTTP+ProcessInternally:
> Executing M24
Aux+Executed:
> Executing M122
File 0:/gcodes/2color_treefrog_small_hollow_0.2mm_PLA__3h32m.gcode is selected, paused
HTTP:
Buffered code: T1 P0
Buffered codes: 32 bytes total
> Number of flush requests: 1
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 38.30, max time between full transfers: 78.0ms, max pin wait times: 58.1ms/3.4ms
Codes per second: 2.40
Maximum length of RX/TX data transfers: 6624/1052

M122 b100
Diagnostics for board 100:
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.6.0-rc.1 (2025-02-28 15:00:13) running on Duet 3 MB6HC v1.0 or earlier (expansion mode)
Board ID: 08DJM-956L2-G43S8-6J9D8-3S86J-9B36F
Used output buffers: 0 of 40 (1 max)
=== RTOS ===
Static ram: 137420
Dynamic ram: 125272 of which 0 recycled
Never used RAM 81820, free system stack 148 words
Tasks: NETWORK(1,ready,11.1%,545) HEAT(3,nWait 6,0.0%,343) Move(4,nWait 6,0.0%,333) TMC(4,nWait 6,3.0%,343) CanReceiv(6,running,0.0%,594) CanSender(5,nWait 7,0.0%,334) MAIN(1,ready,85.8%,500) IDLE(0,ready,0.0%,29) USBD(3,blocked,0.0%,149), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:41:02 ago, cause: software
Last software reset at 2025-03-20 21:01, reason: User, none spinning, available RAM 84148, slot 2
Software reset code 0x0013 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 0.4ms, write time 0.0ms, max retries 0
=== Move ===
Segments created 100, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00/0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 0.00/0/0.00 42401.83/42402/-0.13 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00
Peak sync jitter -12/1, peak Rx sync delay 186, resyncs 0/0
Next step interrupt due in 119 ticks, disabled
Driver 0: standstill, SG min 0, mspos 8, reads 61369, writes 154 timeouts 13
Driver 1: standstill, SG min 0, mspos 552, reads 61359, writes 164 timeouts 13
Driver 2: standstill, SG min 0, mspos 8, reads 61362, writes 161 timeouts 13
Driver 3: standstill, SG min 0, mspos 8, reads 61362, writes 161 timeouts 13
Driver 4: standstill, SG min 0, mspos 8, reads 61376, writes 154 timeouts 13
Driver 5: standstill, SG min 0, mspos 8, reads 61369, writes 161 timeouts 13
Phase step loop runtime (us): min=0, max=60, frequency (Hz): min=0, max=11718
=== Heat ===
Bed heaters -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1 -1 -1 -1 -1, ordering errs 0
=== CAN ===
Messages queued 19783, received 25696, lost 0, ignored 0, errs 842, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 1/0/0
Tx timeouts 0,0,0,0,0,0
Motion dup 0, oos 0/0/0/0

undefined

@fcwilt Thanks, for pointing that out. I should have read that doc more thoroughly.

I have also found a proper solution which is to specify M558 A2 (or higher) which causes all the G30 S-2 to probe slowly on the second (and third) probes.

I'm still surprised by the difference in behaviour between G30 and G30 S-2 in my previous configuration.

undefined

For extra fun, it seems M558 resets the X and Y values (but not Z) of the probe offset set in G31.

4/1/2022, 7:36:56 PM	G31
Z probe 0: current reading 0, threshold 500, trigger height 0.700, offsets X0.0 Y0.0 U0.0
4/1/2022, 7:36:38 PM	M558 P9 C"^io1.in" B1 H5 F60 T6000
4/1/2022, 7:36:25 PM	M558
Z Probe 0: type 9, input pin io1.in, output pin nil, dive height 5.0mm, probe speeds 60,60mm/min, travel speed 6000mm/min, recovery time 0.00 sec, heaters suspended, max taps 1, max diff 0.03
4/1/2022, 7:36:13 PM	G31
Z probe 0: current reading 0, threshold 500, trigger height 0.700, offsets X56.0 Y16.0 U0.0
4/1/2022, 7:36:10 PM	g31 x56 y16

undefined

I hvae a bltouch configured and working with

M558 P9 C"^io1.in" B1 H5 F600:60 T6000

When homing Z i use G30 and as expected the probing is done once quickly and then more slowly in the second pass.

With my calibration macros i use G30 S-2 to set the probe z offset with this it only probes with the faster speed.

I am working around the problem by reconfiguring the probing speeds to F60 in the calibration macros.

Is this behaviour expected or a bug?

RepRapFirmware for Duet 3 Mini 5+ version 3.4.0 (2022-03-15 18:59:15) running on Duet 3 Mini5plus WiFi (SBC mode)

undefined

If your misbehaving servo is using io1.out on the mini5+ you should try the firmware build in the thread for my issue.

undefined

bltouch back on io1 with your updated build works. fantastic! thanks!

undefined

Works great on io3 thanks again.

undefined

Ah! I will sacrifice one of the runout sensors to put it on io3 and give it a go, thanks.

undefined

With 3.4b6
Reset the board by pressing the reset button

Measured 0% duty

Sent M280 P0 S90

Measured 7.35% duty at 50Hz

Sent M280 P0 S180

measured 12% duty at 50Hz

Send M280 P0 S270

measured 12% duty at 50Hz

Sent M280 P0 S90

Measured 7.35% duty at 50Hz

So updating servo positions multiple times in 3.4b6 works

undefined

Further debug...

I replaced my bltouch with a multimeter set to measure frequency and duty cycle.

Reset the board by pressing the reset button

Measured 0% duty

Sent M280 P0 S90

Measured 7.35% duty at 50Hz

Send M280 P0 S180

no change in measurement

sent m280 P0 s270

no change in measurement.

reset board.

sent m280 p0 s270

measured 12% duty at 50Hz

sent m280 p0 s90

no change in measurement

Thus i think my issue is the same as this thread:

https://forum.duet3d.com/topic/27139/rrf-3-4-0beta7-5-sbc-servo-only-responding-once-after-reset

undefined

In 3.4rc1 the probe now deploys but doesn't retract after probing.

Machine was completely powered off after the update.

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.0rc1 (2022-02-09 10:27:22) running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: W4ZW4-V296U-D65J0-40KM0-LR03Z-H6928
Used output buffers: 1 of 40 (14 max)
=== RTOS ===
Static ram: 103652
Dynamic ram: 102128 of which 0 recycled
Never used RAM 35788, free system stack 134 words
Tasks: SBC(ready,3.9%,504) HEAT(notifyWait,0.0%,356) Move(notifyWait,0.0%,292) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,356) CanClock(delaying,0.0%,339) TMC(notifyWait,1.1%,114) MAIN(running,93.8%,558) IDLE(ready,0.4%,29) AIN(delaying,0.8%,264), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:08:35 ago, cause: software
Last software reset at 2022-02-09 18:36, reason: User, GCodes spinning, available RAM 36076, slot 0
Software reset code 0x0003 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 515901, completed 515899, timed out 0, errs 0
Step timer max interval 1489
MCU temperature: min 27.5, current 37.5, max 37.8
Supply voltage: min 0.5, current 24.3, max 24.3, under voltage events: 1, 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: pos 3760, standstill, SG min 0, read errors 0, write errors 2, ifcnt 13, reads 44146, writes 25, timeouts 0, DMA errors 0, CC errors 0
Driver 1: pos -1280, standstill, SG min 0, read errors 0, write errors 2, ifcnt 10, reads 44148, writes 23, timeouts 0, DMA errors 0, CC errors 0
Driver 2: pos 3560, standstill, SG min 0, read errors 0, write errors 2, ifcnt 10, reads 44147, writes 23, timeouts 0, DMA errors 0, CC errors 0
Driver 3: pos 17104, standstill, SG min 0, read errors 0, write errors 2, ifcnt 15, reads 44140, writes 29, timeouts 0, DMA errors 0, CC errors 0
Driver 4: pos 0, standstill, SG min 0, read errors 0, write errors 2, ifcnt 15, reads 44142, writes 29, timeouts 0, DMA errors 0, CC errors 0
Driver 5: pos 0, standstill, SG min 0, read errors 0, write errors 2, ifcnt 15, reads 44142, writes 29, timeouts 0, DMA errors 0, CC errors 0
Driver 6: pos 0, standstill, SG min 0, read errors 0, write errors 2, ifcnt 15, reads 44140, writes 29, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2022-02-09 18:46:07
Cache data hit count 1160425780
Slowest loop: 60.47ms; fastest: 0.08ms
=== 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 6, maxWait 48307ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 39, completed 39, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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, chamber heaters -1 -1 -1 -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
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages queued 4633, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 2578/0/0
Tx timeouts 0,0,2577,0,0,2054 last cancelled message type 4514 dest 127
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 20857/20857
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x0f624
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4-rc1
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 40.50, max time between full transfers: 47.1ms, max pin wait times: 46.5ms/6.9ms
Codes per second: 0.45
Maximum length of RX/TX data transfers: 3592/1136

undefined

I downgraded to 3.4b6 to get a print done but here is config.g

; General preferences
G90                                                ; send absolute coordinates...
M83                                                ; ...but relative extruder moves
M550 P"Ender 3"                                    ; set printer name
M918 P1 E4 F2000000                                ; configure direct-connect display
M929 P"log.txt" S1                                 ; Enable logging
;M552 S1                                            ; Enable network

; Drives
M569 P0.0 S1 D3 V0 F4                              ; physical drive 0.0 goes backwards, stealthchop enabled
M569 P0.1 S0 D3 V0 F4                              ; physical drive 0.1 goes backwards, stealthchop enabled
M569 P0.2 S1 D3 V0 F4                              ; physical drive 0.2 goes backwards, stealthchop enabled
M569 P0.3 S0 D3 V0 F4                              ; physical drive 0.3 goes forwards,  stealthchop enabled 
M569 P0.4 S0 D3 V0 F4                              ; physical drive 0.4 goes forwards,  stealthchop enabled 
M569 P0.5 S1 D3 V0 F4                              ; physical drive 0.5 goes backwards, stealthchop enabled 
M569 P0.6 S1 D3 V0 F4                              ; physical drive 0.6 goes backwards, stealthchop enabled 
M584 U0.0 X0.3 Y0.4 Z0.5:0.6 E0.1:0.2              ; set drive mapping
M350 U16 X16 Y16 Z16 E16:16 I1                        ; configure microstepping with interpolation
M92 U80.00 X80.00 Y80.00 Z400.00 E413.4:413.4      ; set steps per mm
M566 U450 X450 Y450 Z60.00 E120.00                 ; set maximum instantaneous speed changes (mm/min)
M203 U9000.00 X9000.00 Y9000.00 Z480.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
M201 U2500.00 X2500.00 Y2500.00 Z20.00 E500.00:500.00  ; set accelerations (mm/s^2)
M906 U1000 X1000 Y1000 Z1000 E1200:1200 I50          ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; Set idle timeout
M915 X Y S5 F1 R0 H150                             ; Stall detection XY log on stall
M915 Z   S3 F1 R2 H200                             ; Stall detection Z pause on stall
M915 P0.1:0.2 S5 F1 R0                             ; Stall detection E0,E1 do nothing


; Axis Limits
M208 U-80.8 X-212 Y-150.6 Z0 S1                     ; set axis minima
M208 U213.8 X95 Y100 Z230 S0                        ; set axis maxima

; Endstops
M574 U2 S1 P"io0.in"                               ; configure active-high endstop for high end on Y via pin io0.in
M574 X1 S1 P"io5.in"                               ; configure active-high endstop for low end on X via pin io6.in
M574 Y1 S1 P"io6.in"                               ; configure active-high endstop for low end on Y via pin io5.in
M574 Z1 S2                                         ; configure Z-probe endstop for low end on Z

; Filament runout sensors
M591 D0 P1 C"^io3.in" S0                           ; Left extruder runout
;M591 D1 P1 C"^io2.in" S0                           ; Right extruder runout

; Z-Probe
M950 S0 C"io1.out"                                 ; create servo pin 0 for BLTouch
M558 P9 C"^io1.in" B1 H5 F480 T6000                ; set Z probe type to bltouch and the dive height + speeds disable heaters when probing
G31 P500 X66 Y12 Z1.8
M557 X-110:110 Y-110:110 S20                       ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950       ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                                 ; create bed heater output on out0 and map it to sensor 0
M140 H0                                            ; map heated bed to heater 0
M143 H0 S120                                       ; set temperature limit for heater 0 to 120C

M308 S1 P"temp1" Y"pt1000"                         ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1                                 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00                                   ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S300                                       ; set temperature limit for heater 1 to 280C

M308 S2 P"temp2" Y"pt1000"                         ; configure sensor 2 as thermistor on pin temp2
M950 H2 C"out2" T2                                 ; create nozzle heater output on out2 and map it to sensor 2
M307 H2 B0 S1.00                                   ; disable bang-bang mode for heater  and set PWM limit
M143 H2 S300                                       ; set temperature limit for heater 2 to 280C

; Fans
M950 F0 C"out5" Q1000                              ; create fan 0 on pin out5 and set its frequency
M106 P0 C"Part Coling T0" S0 H-1                   ; set fan 0 name and value. Thermostatic control is turned on
M950 F1 C"!out3+out3.tach" Q1000
M106 P1 C"Hotend Fan T0" S64 X64 H1 T45

M950 F2 C"out6" Q1000                              ; create fan 2 on pin out6 and set its frequency
M106 P2 C"Part Cooling T1" S0 H-1                  ; set fan 2 name and value. Thermostatic control is turned off
M950 F3 C"!out4+out4.tach" Q1000
M106 P3 C"Hotend Fan T1" S64 X64 H2 T45


; Tools
M563 P0 S"Left Tool" D0 H1 F0                      ; define tool 0
G10 P0 X0 Y0 Z0                                    ; set tool 0 axis offsets
G10 P0 R0 S0                                       ; set initial tool 0 active and standby temperatures to 0C

M563 P1 S"Right Tool" D1 H2 F2 X3                  ; define tool 1 using U axes for X
G10 P1 X0 Y2 Z0                                    ; set tool 1 axis offsets
G10 P1 R0 S0                                       ; set initial tool 1 active and standby temperatures to 0C

; Custom settings are not defined
M307 H0 R0.281 C428.8 D4.28 S1.00 V23.9
 
; Miscellaneous
;M911 S21 R23 P"M913 X0 Y0 G10 P0 R0 S0 G91 M83 G1 Z3 E-5 F10000" ; set voltage thresholds and actions to run on power loss
M572 D0 S0.05                                    ; Guestimate pressure advance setting
M207 S0.5   F2400                                  ; Retraction 0.5mm @40mm/s
M671 X-145:145 Y0:0 S3 F1                          ; leadscrew co-ordinates
M81 C"ps_on"                                       ; Turn off power supply (makes power switch show in webui)

; Load from config-override.g
M501

deployprobe.g:

M280 P0 S10 ; deploy BLTouch

undefined

Since update from 3.4b6 to 3.4b7 (and eventually b7+5 and b7+7) on my Mini5+, bltouch pin does not deploy for homing.

M98 P"config.g" does not present any errors in any of the tested firmware versions.

Setting servo values directly with M280 correctly controls the probe in b6 but doesn't in later versions. Looks like a PWM issue to me. I haven't checked duty cycle with my meter or scope yet, let me know if that would be useful.

undefined

My usual workflow for prints is to slice them in prusa-slicer and send the job to a printer for immediate start. In 3.4b5 this was working fine, in 3.4b6 this no longer works. The job gets uploaded correctly and is listed in the jobs list but doesn't start.

I'm running a MB6HC is SBC mode.

undefined

I am trying to modify the duet3 mb6hc design to suit my specific requirements.

I was unable to find the PCB footprint library used in this project, for example:

footprint “complib:MCCQ-122-minibladefuseholder” not found

I found "complib" from the duet2 project but that doesn't have this footprint or many others needed for the duet3 mb6hc

Could some please point me in the right direction to find these.

Thanks!

undefined

Hi!

With 3.4b1 installed on my MB6HC + raspi changing fillament appears to be imposible. Indeed M702 causes DCS to crash and has to be manually restarted.

	m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0beta1 (2021-07-10 16:20:28) running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J9D8-3S86J-9B36F
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 64380 of which 36 recycled
Never used RAM 138872, free system stack 219 words
Tasks: ACCEL(notifyWait,0.0%,348) SBC(resourceWait:,0.3%,308) HEAT(delaying,0.1%,325) Move(notifyWait,0.0%,300) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,333) TMC(notifyWait,6.6%,93) MAIN(running,92.7%,967) IDLE(ready,0.3%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:03:02 ago, cause: software
Last software reset at 2021-07-13 16:56, reason: User, GCodes spinning, available RAM 135800, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 740
MCU temperature: min 45.6, current 45.8, max 46.9
Supply voltage: min 0.2, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 0.1, current 12.2, max 12.8, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 36701, writes 11 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 36701, writes 11 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 36701, writes 11 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 36701, writes 11 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 36702, writes 11 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 36702, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-07-13 16:59:57
Slowest loop: 26.60ms; 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, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 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.
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages queued 1625, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 913/0/0
Tx timeouts 0,0,912,0,0,711 last cancelled message type 4514 dest 127

=== SBC interface ===
State: 4, failed transfers: 0, checksum errors: 0
Last transfer: 2ms ago
RX/TX seq numbers: 793/793
SPI underruns 0, overruns 0
Disconnects: 1, timeouts: 1, IAP RAM available 0x2c7a4
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.4-b1
Code buffer space: 4096
Configured SPI speed: 8000000Hz
Full transfers per second: 37.82, max wait times: 56.8ms/0.0ms
Codes per second: 0.05
Maximum length of RX/TX data transfers: 3096/40

Systemd log

log.txt