Posts made by kcorbedsellig

@dc42

Unfortunately pressing the reset button and powering on does not work on any of the unresponsive 23CLs. They don't give any sign of life. Both with and without a CAN cable connected while running the process.

For the recalibration of the one with address 80.0. I disconnected all other CAN devices and have run a single cable to a t-splitter of which one end is 120ohm resistors and the other is the 23CL. It does not want to calibrate and says it has no encoder configured.

M569.6 P80.0 V2
Error: M569.6: no encoder configured
25/04/2024, 11:12:08	M17
25/04/2024, 11:11:53	M115 B80
Duet M23CL firmware version 3.5.1 (2024-04-19 14:42:52)
25/04/2024, 11:07:55	Error: Expansion board 80 stopped sending status
25/04/2024, 11:07:14	M569.6 P80.0 V2
Error: M569.6: no encoder configured
25/04/2024, 11:06:59	M17
25/04/2024, 11:04:49	M115 B80
Duet M23CL firmware version 3.5.1 (2024-04-19 14:42:52)
25/04/2024, 11:04:00	M122 B80
Diagnostics for board 80:
Duet M23CL firmware version 3.5.1 (2024-04-19 14:42:52)
Bootloader ID: SAME5x bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 75108, free system stack 184 words
Tasks: Move(3,nWait 7,0.0%,175) CLSend(3,nWait 6,0.0%,148) HEAT(2,nWait 6,0.0%,131) CanAsync(5,nWait 4,0.0%,67) CanRecv(3,nWait 1,0.0%,80) CanClock(5,nWait 1,0.0%,65) TMC(2,nWait 6,23.5%,350) MAIN(1,running,73.9%,394) IDLE(0,ready,0.0%,40) AIN(2,nWait 2,2.5%,255), total 100.0%
Owned mutexes:
Last reset 00:07:03 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 80.0 steps/mm, standstill, SG min 0, mspos 8, reads 48187, writes 13 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, segs 0, step errors 0, maxLate 0 maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00
Peak sync jitter -8/5, peak Rx sync delay 184, resyncs 0/0, next timer interrupt due in 31 ticks, enabled, next step interrupt due in 3977492161 ticks, disabled
VIN voltage: min 48.1, current 48.1, max 48.2
V12 voltage: min 12.1, current 12.1, max 12.1
MCU temperature: min 17.3C, current 21.8C, max 21.8C
Last sensors broadcast 0x00000000 found 0 54 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 3410, send timeouts 0, received 2128, lost 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Closed loop driver 0 mode: open loop, pre-error threshold: 2.00, error threshold: 4.00, encoder type none

For the possibly broken fuses on the unresponsive 23CLs. I've opened one and found what I believe must be the fuse. It's labeled F1 and can be found directly next to the power input. I've measured continuity on this fuse and it appears to not be broken.

@dc42 I'll run through these step first thing tomorrow morning. I have a multimeter, where might I find this fuse to check it?

@dc42 That's strange, I only ever ran the calibration without load. Is it required to rerun the calibration after a firmware upgrade? I'll recalibrate and report the results.

I'll get in touch with info@duet3d.com. Does that mean these 23CLs are bricked?

@dc42

"M112 B80" for the 23CL that's showing most errors

M122 B80
Diagnostics for board 80:
Duet M23CL firmware version 3.5.1 (2024-04-19 14:42:52)
Bootloader ID: SAME5x bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 45192, free system stack 186 words
Tasks: EncCal(1,nWait 6,0.0%,470) Move(3,nWait 7,0.0%,166) CLSend(3,nWait 6,0.0%,148) HEAT(2,nWait 6,0.1%,106) CanAsync(5,nWait 4,0.0%,67) CanRecv(3,nWait 1,0.0%,80) CanClock(5,nWait 1,0.0%,65) TMC(4,nWait 6,68.9%,326) MAIN(1,running,26.8%,248) IDLE(0,ready,0.0%,30) AIN(2,nWait 2,4.2%,255), total 100.0%
Owned mutexes:
Last reset 00:00:57 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 80.0 steps/mm, ok, SG min 0, mspos 8, reads 20377, writes 10329 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, segs 0, step errors 0, maxLate 0 maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00
Peak sync jitter -8/3, peak Rx sync delay 16912, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 48.1, current 48.2, max 48.2
V12 voltage: min 12.1, current 12.1, max 12.1
MCU temperature: min 20.3C, current 22.4C, max 22.4C
Last sensors broadcast 0x00000000 found 0 154 ticks ago, 0 ordering errs, loop time 1
CAN messages queued 484, send timeouts 0, received 300, lost 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Closed loop driver 0 mode: closed loop, pre-error threshold: 2.00, error threshold: 4.00, encoder type rotaryAS5047, position 826
Encoder reverse polarity: no, full rotations 0, last angle 825, minCorrection=-31.7, maxCorrection=35.1, agc 72, mag 4705, no error
Tuning mode: 0, tuning error: 0, collecting data: no
Control loop runtime (us): min=2, max=66, frequency (Hz): min=9259, max=14423

"M112 B73" for a 23CL that seems to work fine

M122 B73
Diagnostics for board 73:
Duet M23CL firmware version 3.5.1 (2024-04-19 14:42:52)
Bootloader ID: SAME5x bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 45192, free system stack 186 words
Tasks: EncCal(1,nWait 6,0.0%,470) Move(3,nWait 7,0.0%,166) CLSend(3,nWait 6,0.0%,148) HEAT(2,nWait 6,0.1%,106) CanAsync(5,nWait 4,0.0%,67) CanRecv(3,nWait 1,0.0%,66) CanClock(5,nWait 1,0.0%,65) TMC(4,nWait 6,70.4%,326) MAIN(1,running,25.1%,273) IDLE(0,ready,0.0%,30) AIN(2,nWait 2,4.4%,255), total 100.0%
Owned mutexes:
Last reset 00:02:10 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 80.0 steps/mm, ok, SG min 0, mspos 8, reads 57763, writes 12606 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, segs 0, step errors 0, maxLate 0 maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00
Peak sync jitter -8/2, peak Rx sync delay 189, resyncs 0/0, next timer interrupt due in 2 ticks, enabled, next step interrupt due in 4196851010 ticks, disabled
VIN voltage: min 48.2, current 48.2, max 48.3
V12 voltage: min 12.0, current 12.0, max 12.0
MCU temperature: min 22.5C, current 25.4C, max 25.4C
Last sensors broadcast 0x00000000 found 0 84 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 1073, send timeouts 0, received 668, lost 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Closed loop driver 0 mode: closed loop, pre-error threshold: 2.00, error threshold: 4.00, encoder type rotaryAS5047, position -620
Encoder reverse polarity: no, full rotations -1, last angle 15764, minCorrection=-16.9, maxCorrection=20.9, agc 71, mag 4778, no error
Tuning mode: 0, tuning error: 0, collecting data: no
Control loop runtime (us): min=2, max=69, frequency (Hz): min=9036, max=14423

The ones that don't respond anymore don't show any LED's from power up to power down and don't respond to any console call.

Below the M115 response on a nonresponsive and a responsive 23CL. You get the same with a M122 for 23CL 72.0.

24/04/2024, 17:29:37	M115 B72
CAN response timeout: board 72, req type 6024, RID 77
24/04/2024, 17:29:29	M115 B80
Duet M23CL firmware version 3.5.1 (2024-04-19 14:42:52)

I've been doing some more testing and ran into more issues.

Each 23CL is connected to its own Meanwell 48V 2.5A power supply with a common ground and each 23CL faces the same load as they are all copies of each other.

For some reason, the 23CL with address 80 has been reporting shorts more than the others. I thought this had to do with tuning but that did not change much to the situation. I then noticed when measuring the voltage on the power supply of this 23CL that it was drawing 78V. I then took this supply out and tested it on my bench and found nothing wrong with it.

I also tested the other 23CLs in the system and they all worked fine when used individually including the one with address 80. However, upon using them as a single tool 80 started to report errors again and two others immediately stopped responding as well. I now have 3 23CLs out of 13 that don't show a blinking light anymore upon connecting. I haven't found a way to get these back to life as I can't connect them to reflash firmware or reset them. These for example also don't show as connected in the machine-specific information tab.

I have no clue what to test next and what could be the issue here. Any help would be greatly apreciated.

Since moving my project from my bench to a first prototype setup I'm running into errors and unresponsive 23CL's. As soon as I started running the 23CLs under load the first issues came up.

I started seeing errors in the console related to "short to vin". I remembered seeing this in the tuning manual and figured it would have something to do with tuning in the closed-loop plugin. The first issue I ran into here is that the 23CLs are configured as extruders and the plugin only allows tuning in axis. Since all 12 I have are under the exact same load I changed one to an unused axis and then autotuned it under load. I then took the PID and V and A values and added them to all my extruder drives like so:

M569.1 P82.0 T3 E2:4 R20 I2000 D0 A0 V1000 

This did not fully resolve the issue but I seem to get the error less at this point.

I'm also seeing various CAN errors that I can't seem to find anything about in the documentation.

23/04/2024, 12:33:09	CAN response timeout: board 80, req type 6042, RID 58
23/04/2024, 12:33:08	CAN response timeout: board 80, req type 6043, RID 45
23/04/2024, 12:33:07	CAN response timeout: board 80, req type 6042, RID 34
23/04/2024, 12:33:06	CAN response timeout: board 80, req type 6018, RID 21

Besides that I also had one 23CL that is now completely unresponsive. I've replaced this one with my only spare. The replaced one does not work either but does stay responsive.
It could be a coincidence but could also be related that 23CL that is unresponsive was 81 and 80 gives errors, when placing 70 in the place of 80 the errors stay the same. Changing the order in the config does not change which 23cl has the error.

I've tried to take the load of the 23CL's and go back to the settings I had on my bench but that did not solve anything.

My setup is on the latest version of everything.

config:

; executed by the firmware on start-up
G4 S2                           ;wait for expansion boards to start

; General preferences
G91                             ; rel pos
M83                             ; ...but relative extruder moves
M550 P"conveyor"                ; set printer name
M669 K0                         ; printer mode

; Axis Limits
M208 X0 Y0 Z0 S1                                ; set axis minima
M208 X1000 Y99999 Z99999 S0        

; for pumps tuned settings
;M569.1 P71.0 T3 E2:4 R20 I2000 D0 A0 V1000 ; Configure the M23CL at CAN address 71
;M569.1 P72.0 T3 E2:4 R20 I2000 D0 A0 V1000 ; Configure the M23CL at CAN address 72
;M569.1 P73.0 T3 E2:4 R20 I2000 D0 A0 V1000 ; Configure the M23CL at CAN address 73
;M569.1 P74.0 T3 E2:4 R20 I2000 D0 A0 V1000 ; Configure the M23CL at CAN address 73
;M569.1 P75.0 T3 E2:4 R20 I2000 D0 A0 V1000 ; Configure the M23CL at CAN address 73
;M569.1 P76.0 T3 E2:4 R20 I2000 D0 A0 V1000 ; Configure the M23CL at CAN address 73
;M569.1 P77.0 T3 E2:4 R20 I2000 D0 A0 V1000 ; Configure the M23CL at CAN address 73
;M569.1 P78.0 T3 E2:4 R20 I2000 D0 A0 V1000 ; Configure the M23CL at CAN address 73
;M569.1 P79.0 T3 E2:4 R20 I2000 D0 A0 V1000 ; Configure the M23CL at CAN address 73
;M569.1 P80.0 T3 E2:4 R20 I2000 D0 A0 V1000 ; Configure the M23CL at CAN address 73
;M569.1 P70.0 T3 E2:4 R20 I2000 D0 A0 V1000 ; Configure the M23CL at CAN address 73
;M569.1 P82.0 T3 E2:4 R20 I2000 D0 A0 V1000 ; Configure the M23CL at CAN address 73

; for pumps untuned settings
M569.1 P71.0 T3 E2:4 R100 I0 D0  ; Configure the M23CL at CAN address 71
M569.1 P72.0 T3 E2:4 R100 I0 D0  ; Configure the M23CL at CAN address 72
M569.1 P73.0 T3 E2:4 R100 I0 D0  ; Configure the M23CL at CAN address 73
M569.1 P74.0 T3 E2:4 R100 I0 D0  ; Configure the M23CL at CAN address 73
M569.1 P75.0 T3 E2:4 R100 I0 D0  ; Configure the M23CL at CAN address 73
M569.1 P76.0 T3 E2:4 R100 I0 D0  ; Configure the M23CL at CAN address 73
M569.1 P77.0 T3 E2:4 R100 I0 D0  ; Configure the M23CL at CAN address 73
M569.1 P78.0 T3 E2:4 R100 I0 D0  ; Configure the M23CL at CAN address 73
M569.1 P79.0 T3 E2:4 R100 I0 D0  ; Configure the M23CL at CAN address 73
M569.1 P80.0 T3 E2:4 R100 I0 D0  ; Configure the M23CL at CAN address 73
M569.1 P70.0 T3 E2:4 R100 I0 D0  ; Configure the M23CL at CAN address 73
M569.1 P82.0 T3 E2:4 R100 I0 D0  ; Configure the M23CL at CAN address 73

M569 P71.0 D4 S0 ; Set into closed-loop drive mode (D4) and reversed (S0)
M569 P72.0 D4 S0 ; Set into closed-loop drive mode (D4) and reversed (S0)
M569 P73.0 D4 S0 ; Set into closed-loop drive mode (D4) and reversed (S0)
M569 P74.0 D4 S0 ; Set into closed-loop drive mode (D4) and reversed (S0)
M569 P75.0 D4 S0 ; Set into closed-loop drive mode (D4) and reversed (S0)
M569 P76.0 D4 S0 ; Set into closed-loop drive mode (D4) and reversed (S0)
M569 P77.0 D4 S0 ; Set into closed-loop drive mode (D4) and reversed (S0)
M569 P78.0 D4 S0 ; Set into closed-loop drive mode (D4) and reversed (S0)
M569 P79.0 D4 S0 ; Set into closed-loop drive mode (D4) and reversed (S0)
M569 P80.0 D4 S0 ; Set into closed-loop drive mode (D4) and reversed (S0)
M569 P70.0 D4 S0 ; Set into closed-loop drive mode (D4) and reversed (S0)
M569 P82.0 D4 S0 ; Set into closed-loop drive mode (D4) and reversed (S0)

; for conveyors
M569 P0.0 S1                                          ; physical drive 0.0 goes forwards
M569 P0.1 S1                                          ; physical drive 0.1 goes forwards
M350 X16
M566 X900 Y1300 E1300                                 ; set maximum instantaneous speed changes (mm/min)
M203 X90000.00 Y5000.00 E5000.00                      ; set maximum speeds (mm/min)
M201 X2000.00 Y1000.00 E1000.00                       ; set accelerations (mm/s^2)
M84 S30                                               ; Set idle timeout

M584 X0.0:0.1 E71.0:72.0:73.0:74.0:75.0:76.0:77.0:78.0:79.0:80.0:70.0:82.0
M906 X2000 Y2500 E2500:2500:2500:2500:2500:2500:2500:2500:2500:2500:2500:2500

M92 X100.00 Y80.00 E80:80:80:80:80:80:80:80:80:80:80:80 ; steps/mm

; extruder setup
M563 P0 D0:1:2:3:4:5:6:7:8:9:10:11 F0           
;M563 P0 D0:2:4:6:8:10:1:3:5:7:9:11 F0           
G10 P0 X0 Y0 Z0                                       ; set tool 0 axis offsets
G10 P0 R0 S0                                          ; set initial tool 0 active and standby temperatures to 0C
M568 P0 S1                                            ; enable mixing for tool 0
M567 P0 E1:1:1:1:1:1:1:1:1:1:1:1                      ; set mixing ratios for tool 0
T0

;sensors
M574 X1 S1 P"!io0.in"
M950 J1 C"!io1.in"                                     ; Input 4 uses io1.in pin, inverted
M581 P1 S0 T4 R0                                       ; Disable Steppers - trigger4.g

;no homing required to start
M564 H0

M122:

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.5.1 (2024-04-22 13:55:46) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-9P63L-DJ3T8-6JTDG-3SN6S-1V7RB
Used output buffers: 1 of 40 (27 max)
=== RTOS ===
Static ram: 155200
Dynamic ram: 86972 of which 0 recycled
Never used RAM 100964, free system stack 202 words
Tasks: SBC(2,ready,0.9%,372) HEAT(3,nWait 6,0.0%,357) Move(4,nWait 6,0.0%,336) CanReceiv(6,nWait 1,0.1%,797) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,350) TMC(4,nWait 6,9.8%,56) MAIN(2,running,83.1%,101) IDLE(0,ready,6.0%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:01:36 ago, cause: software
Last software reset at 2024-04-23 11:57, reason: User, FilamentSensors spinning, available RAM 100964, slot 0
Software reset code 0x600d HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
MCU temperature: min 31.0, current 31.1, max 33.1
Supply voltage: min 23.8, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 99/7, heap memory allocated/used/recyclable 2048/100/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min 0, mspos 0, reads 5161, writes 14 timeouts 0
Driver 1: ok, SG min 0, mspos 0, reads 5162, writes 13 timeouts 0
Driver 2: ok, SG min 0, mspos 0, reads 5164, writes 11 timeouts 0
Driver 3: ok, SG min 9, mspos 9, reads 5164, writes 11 timeouts 0
Driver 4: ok, SG min 9, mspos 9, reads 5164, writes 11 timeouts 0
Driver 5: ok, SG min 9, mspos 9, reads 5164, writes 11 timeouts 0
Date/time: 2024-04-23 11:59:17
Slowest loop: 2.88ms; fastest: 0.07ms
=== Storage ===
Free file entries: 20
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 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -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 0xfff00003
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 554, received 8547, lost 0, errs 0, boc 0
Longest wait 56ms for reply type 6041, peak Tx sync delay 64, free buffers 50 (min 49), ts 483/482/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 3472/3472
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x253c8
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server version 3.5.1 (2024-04-19 16:30:56, 32-bit)
HTTP+Executed:
> Executing M122
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 38.49, max time between full transfers: 50.2ms, max pin wait times: 41.6ms/0.2ms
Codes per second: 0.73
Maximum length of RX/TX data transfers: 8184/1216

Any help is much appreciated as always.

I've got the custom firmware working.

The issue was that CrcAppender needed '.NET runtime' to work. After installing that separately and confirming in the terminal CrcAppender worked without errors the rebuild firmware worked. It took some time to figure this out because Eclipse reported no error for it.

Thanks for all the help.

@jay_s_uk thanks, I've quickly tried to get this going but can't get a serial connection with the boards, and can't get Bossa to run on my Mac either, will have to do this some other time and dust off the old PC I must have around here somewhere.

Unfortunately, this does put me in a situation in which I can't seem to get the firmware changed myself but I also can't proceed with only 10 extruders. If I understand @dc42 correctly the next firmware update could allow for 12 extruders but I imagine that could take a while to become available.

Any chance anybody who feels comfortable altering the firmware could build a version for me that has the 12 extruders per tool allowed? I'm on my last development board now so I can't risk uploading a faulty version created by myself again.

I've just tried to upload my .bin file through the DWC and it failed. Just for sanity, I tried it on a second board but without success again. I now can't connect to either of the boards. In both cases, the DWC still loads but fails to connect and shows the following error:

My .bin file is called "Duet3Firmware_MB6HC.bin" and found in "RepRapFirmware/Duet3_MB6HC/". It's 792KB which seems to match the ones found online. The only thing I changed is the variable discussed above.

On one of the boards, the diag led flashes 3 times followed by 2 sec of no flash.
On the other which is a newer one the diag led does not flash at all.

I've tried connecting through SSH to go back to an older version but can't seem to get it to work. It keeps telling me everything is up to date.

I now have two boards that don't respond and can't seem to find out how to flash stable firmware back on them. What's the right way to get these back to life? I have a third one I can try but I'd rather not.

@droftarts Thanks, I'm sure I can make that work.

You can see works from a similar machine here.

@deckingman It's not a 3d printer that I'm building but a machine that extrudes paint. The 12 drives are configured as one tool but that tool has 6 nozzles that extrude at the same time with 2 extruders on each. I use machines like these to create artworks.

@chrishamm Thank you for your reply and advice.

I believe I've successfully built a .bin file with the variable changed as required.

I'm running an MB6HC with a SBC and I'm not sure how to upload the firmware as I have no experience with these processes.

• Should I drag the .bin file into the system folder the same way as I upgrade my M23CLs?
• Should I somehow upload it via SSH?

I'm building a printer in which I use 12 drives for one tool. Unfortunately, I'm running into an issue where it seems the maximum amount of drives configured to one tool appears to be 10. I'm wondering if there is any reason behind this limitation and if it can be increased and if so If I can do it myself or if this is configured deep in the firmware.

My whole system is in version 3.5.0-rc.3.

To config the tool:

M563 P0 D0:1:2:3:4:5:6:7:8:9:10:11 F0   

The error:

Error in start-up file config.g line 54: in file macro line 54: M563: array too long, max length = 10

Additionally, I'm open to finding a way around this but I haven't been able to find one myself so far. In my use case, I need the 12 drives to work simultanously. The gcode is generated through software I create myself so I'm happy to alter it to work differently but I'm not sure if there is any other way to do this. I could for example add the 12 drives as different axis but as far as I can tell only 6 are supported of which I need one for movement.

Any help is much appreciated as always.

I've finally gotten everything to work.

The issue all along must have been the star-shaped configuration of cables I had for the Can signal. The system had one distribution block and 2m cables to the steppers. As soon as I changed this to one 2m cable followed by t splitters, 30cm cables and a 120-ohm resistor at the end everything started working as expected.

Thanks for all the help and sorry for wasting your time.

@dc42 Hey David, thank you for your reply.

I'm working on a test setup, there is no load on any of the steppers and the config file is empty except for the bare minimum and whatever it told me to add in the documentation.

I've just added 70.0 with an almost empty config as you described and when I run "M564 H0" I can indeed move the stepper which is a first. However when I try to run the M569.6 command it still gives me an error. I'm aware I only have to run it once but can't seem to get it working.

08/04/2024, 14:43:52	M569.6 P70.0 V2
Error: M569.6: no encoder configured
08/04/2024, 14:43:16	M17 U
08/04/2024, 14:43:04	M584 U70.0
08/04/2024, 14:42:40	Connection established

I then shut down and connected 70.0 and 71.0 and ran the config settings as in the documentation.

Config:

G4 S2                           ;wait for expansion boards to start

; General preferences
G90                             ; send absolute coordinates...
M83                             ; ...but relative extruder moves
M550 P"conveyor"                ; set printer name
M669 K0                         ; printer mode

 
M569.1 P70.0 T3 E2:4 R100 I0 D0 ; Configure the M23CL at CAN address 70
M569.1 P71.0 T3 E2:4 R100 I0 D0 ; Configure the M23CL at CAN address 71
M569 P70.0 D4 S1 ; Set into closed-loop drive mode (D4) and not reversed (S1)
M569 P71.0 D4 S1 ; Set into closed-loop drive mode (D4) and not reversed (S1)
M584 X70.0 Y71.0 ; set X and Y drivers

M350 X32 Y32 ; set steps/mm to 32 for open loop mode operation
M92 X160 Y160 ; steps/mm for a 20 tooth gt2 pulley for open loop operation

And I get new errors on both.
console:

08/04/2024, 15:41:18	Warning: Driver 71.0 warning: failed to maintain position, tuning/calibration failed
08/04/2024, 15:41:18	M569.6 P71.0 V2
Error: M569.6: Driver 71.0 calibration failed, the measured motion was less than expected, measured counts/step is about 0.0
08/04/2024, 15:40:40	Warning: Driver 70.0 warning: tuning/calibration failed
08/04/2024, 15:40:40	M569.6 P70.0 V2
Error: M569.6: Driver 70.0 calibration failed, the measured motion was less than expected, measured counts/step is about 0.0
08/04/2024, 15:40:11	M17
08/04/2024, 15:39:01	Connection established

With these config settings, I can no longer get the steppers to move either.

Another strange thing is also that I get an error as a popup for 71.0 but not for 70.0 even though they have the same settings upon startup.

Event notification
Driver 71.0 error: failed to maintain position```
code_text

Currently, 70.0 is one I ordered earlier and 71.0 is from a later batch that shipped directly from China. The older serial starts with 2311 and the newer ones start with 2403.

Could this have something to do with how I wired them or would they not respond well to M115 in that case either?

@droftarts Thank you for your reply.

Here is the full reply on "M122 B73" before attempting to update through the bin file you linked to.

M122 B73
Diagnostics for board 73:
Duet M23CL firmware version 3.5.0-rc.1+ (2023-10-26 09:24:34)
Bootloader ID: SAME5x bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 75428, free system stack 186 words
Tasks: Move(3,nWait,0.0%,182) CLSend(3,nWait,0.0%,150) HEAT(2,nWait,0.0%,120) CanAsync(5,nWait,0.0%,67) CanRecv(3,nWait,0.0%,80) CanClock(5,nWait,0.0%,70) TMC(2,nWait,20.2%,359) MAIN(1,running,77.5%,399) IDLE(0,ready,0.0%,40) AIN(2,nWait,2.2%,265), total 100.0%
Last reset 00:05:14 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 80.0 steps/mm, standstill, SG min 0, mspos 8, reads 63748, writes 12 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, segs 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00
Peak sync jitter -7/3, peak Rx sync delay 184, resyncs 0/0, next timer interrupt due in 12 ticks, enabled, next step interrupt due in 4059135798 ticks, disabled
VIN voltage: min 48.2, current 48.2, max 48.2
V12 voltage: min 12.0, current 12.0, max 12.0
MCU temperature: min 20.1C, current 23.6C, max 23.6C
Last sensors broadcast 0x00000000 found 0 197 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 2535, send timeouts 0, received 1581, lost 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Closed loop driver 0 mode: open loop, pre-error threshold: 2.00, error threshold: 4.00, encoder type none

I downloaded the M23CL bin file and uploaded it in the system files which prompted an update on the M23CL that was connected at that time. It seems succesfull and displays in the machine specific info:

Electronics
 Diagnostics
Product	Short Name	Version
Duet 3 MB6HC	MB6HC	3.5.0-rc.3
Duet 3 Expansion M23CL	M23CL	3.5.0-rc.3
Duet Software Framework	DSF	3.5.0-rc.3
Duet Web Control	DWC	3.5.0-rc.3

For M23CL with CAN 73.0 which is not configured at all in the config file it still reads:

M569.6 P73.0 V2
Error: M569.6: no encoder configured

After reconnecting and updating 71.0 and 72.0 and running them with the same config file as before which was taken from the example in the documentation. I get popups in the DWC that say:
"Event notification
Driver 71.0 error: failed to maintain position"
And the same for 72.0

Upon trying to initiate the config for the M23CL I still get the same error:

M569.6 P71.0 V2
Error: M569.6: Driver is not enabled

Here is the full reply on M112 B71.0 after updating.

M122 B71.0
Diagnostics for board 71:
Duet M23CL firmware version 3.5.0-rc.3 (2024-01-24 17:54:18)
Bootloader ID: SAME5x bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 45192, free system stack 186 words
Tasks: EncCal(1,nWait 6,0.0%,470) Move(3,nWait 7,0.0%,166) CLSend(3,nWait 6,0.0%,148) HEAT(2,nWait 6,0.1%,108) CanAsync(5,nWait 4,0.0%,67) CanRecv(3,nWait 1,0.0%,66) CanClock(5,nWait 1,0.0%,65) TMC(4,nWait 6,70.0%,326) MAIN(1,running,25.2%,266) IDLE(0,ready,0.0%,30) AIN(2,nWait 2,4.7%,255), total 100.0%
Owned mutexes:
Last reset 00:04:19 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 160.0 steps/mm, failed to maintain position, SG min n/a, mspos 4, reads 14047, writes 31123 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, segs 0, step errors 0, maxLate 0 maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00
Peak sync jitter -6/3, peak Rx sync delay 190, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 48.0, current 48.0, max 48.0
V12 voltage: min 12.0, current 12.0, max 12.0
MCU temperature: min 20.2C, current 21.1C, max 21.1C
Last sensors broadcast 0x00000000 found 0 177 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 2100, send timeouts 0, received 1311, lost 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Closed loop driver 0 mode: closed loop, pre-error threshold: 2.00, error threshold: 4.00, encoder type rotaryAS5047, position 1955
Encoder reverse polarity: no, full rotations 0, last angle 1957, minCorrection=-12.6, maxCorrection=18.3, agc 62, mag 4757, no error
Tuning mode: 0, tuning error: 0, collecting data: no
Control loop runtime (us): min=4, max=66, frequency (Hz): min=8928, max=14150

Since as in the example they are configured as X and Y it tried sending:

M564 H0

In order to move them without homing from the DWC. This allows me to move X and Y from the dashboard. When I do this I can see their location update in the status as well as it going from "idle" to "busy" but no movement in the steppers.

The whole system seems to be running the latest versions of firmware but the errors have not changed. I've followed all the steps from the documentation as far as I can tell but no success.

Not sure how to proceed from here, any help as always would be greatly appreciated. I'm most likely making a stupid mistake somewhere but the big question is where.

@Phaedrux @jay_s_uk
I believe I've successfully upgraded the firmware:

Product	Short Name	Version
Duet 3 MB6HC	MB6HC	3.5.0-rc.3
Duet 3 Expansion M23CL	M23CL	3.5.0-rc.1+
Duet 3 Expansion M23CL	M23CL	3.5.0-rc.1+
Duet 3 Expansion M23CL	M23CL	3.5.0-rc.1+
Duet 3 Expansion M23CL	M23CL	3.5.0-rc.1+
Duet Software Framework	DSF	3.5.0-rc.3
Duet Web Control	DWC	3.5.0-rc.3

However, I'm getting the same results as before. I've added one fresh from the box under a new address to verify and it also gives the same errors.

When I run the following config:

; executed by the firmware on start-up

G4 S2                           ;wait for expansion boards to start

; General preferences
G90                             ; send absolute coordinates...
M83                             ; ...but relative extruder moves
M550 P"conveyor"                ; set printer name
M669 K0                         ; printer mode

M569.1 P71.0 T3 E2:4 R100 I0 D0 ; Configure the M23CL at CAN address 70
M569.1 P72.0 T3 E2:4 R100 I0 D0 ; Configure the M23CL at CAN address 71
M569 P71.0 D4 S1 ; Set into closed-loop drive mode (D4) and not reversed (S1)
M569 P72.0 D4 S1 ; Set into closed-loop drive mode (D4) and not reversed (S1)
M584 X71.0 Y72.0 ; set X and Y drivers

M350 X32 Y32 ; set steps/mm to 32 for open loop mode operation
M92 X160 Y160 ; steps/mm for a 20 tooth gt2 pulley for open loop operation

The error is:

M569.6 P71.0 V2
Error: M569.6: Driver is not enabled

And without any config for the M23CL's.
config:

; executed by the firmware on start-up

G4 S2                           ;wait for expansion boards to start

; General preferences
G90                             ; send absolute coordinates...
M83                             ; ...but relative extruder moves
M550 P"conveyor"                ; set printer name
M669 K0                         ; printer mode

Error:

M569.6 P73.0 V2
Error: M569.6: no encoder configured

For as far as I can tell the M23CL's can't be updated to run RC.3 based on the following feedback from terminal.

pi@conveyor:~ $ sudo rm -f /etc/apt/sources.list.d/duet3d.list
pi@conveyor:~ $ sudo bash -c "echo 'deb https://pkg.duet3d.com/ unstable armv7' > /etc/apt/sources.list.d/duet3d-unstable.list"
pi@conveyor:~ $ sudo apt update
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease         
Hit:3 https://pkg.duet3d.com unstable InRelease                         
Reading package lists... Done                     
Building dependency tree       
Reading state information... Done
All packages are up to date.
pi@conveyor:~ $ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
pi@conveyor:~ $ 

Any help would be greatly appreciated.

@Phaedrux Thanks, I'm sure this will do the trick.

@jay_s_uk Thanks for your response. I was under the impression that I was running the latest after updating using these steps.
https://docs.duet3d.com/User_manual/Machine_configuration/DSF_RPi#software-installation

I'll run this again to see if it makes a difference.

I couldn't find much on this subject yet on this forum (or elsewhere online). I purchased some M23CL steppers without breaks but can't seem to get them configured.

I'm following the following instructions:
https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Motor_23CL

Innitial connection and change of adress went fine without issues. However I'm having issues getting them callibrated or moving at all after.

I'm supplying 48V to them both from a seperate power supply with common ground connected between all supplies in use. (one for each M23CL and one for the main board)

When calling the M23CL with:

M115 B71

I get the following reply:

M115 B71
Duet M23CL firmware version 3.5.0-rc.1+ (2023-10-26 09:24:34)

And the same for the other M23CL with the adres 72.

When trying to callibrate with:

M569.6 P71.0 V2

I get the following error:

Error: M569.6: Driver is not enabled

And with:

M569.6 P71.0 V3

I get the same error.

I've tried to run this without having anything in the config file related to them but it does not seem to make a difference. When I try to add a third one and configure it under the adress 73 everything responds the same.

When I restart my board I get the following error for both M23CL's

Warning: Driver 71.0 stall

Config file:

; executed by the firmware on start-up

G4 S2                           ;wait for expansion boards to start

; General preferences
G90                             ; send absolute coordinates...
M83                             ; ...but relative extruder moves
M550 P"conveyor"                ; set printer name
M669 K0                         ; printer mode



M569.1 P71.0 T3 E2:4 R100 I0 D0 ; Configure the M23CL at CAN address 71
M569.1 P72.0 T3 E2:4 R100 I0 D0 ; Configure the M23CL at CAN address 72
M569 P71.0 D4 S1 ; Set into closed-loop drive mode (D4) and not reversed (S1)
M569 P72.0 D4 S1 ; Set into closed-loop drive mode (D4) and not reversed (S1)
M584 X71.0 Y72.0 ; set X and Y drivers

M350 X32 Y32 ; set steps/mm to 32 for open loop mode operation
M92 X160 Y160 ; steps/mm for a 20 tooth gt2 pulley for open loop operation

M112:

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.1 (2022-06-01 21:09:01) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TJ-6J9D4-3S46N-KB8AS
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 64316 of which 0 recycled
Never used RAM 135356, free system stack 200 words
Tasks: SBC(resourceWait:,0.5%,496) HEAT(notifyWait,0.0%,371) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.5%,92) MAIN(running,91.9%,923) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:07:59 ago, cause: software
Last software reset at 2024-04-01 14:08, reason: User, none spinning, available RAM 135356, slot 1
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 153
MCU temperature: min 32.1, current 32.2, max 32.7
Supply voltage: min 32.0, current 32.0, max 32.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.9, current 11.9, max 12.0, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 2 queued, 2 completed
Driver 0: standstill, SG min 0, mspos 8, reads 605, writes 11 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 605, writes 11 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 605, writes 11 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 605, writes 11 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 605, writes 11 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 606, writes 11 timeouts 0
Date/time: 2024-04-01 14:16:02
Slowest loop: 1.26ms; 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 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -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
=== CAN ===
Messages queued 2410, received 7673, lost 0, boc 0
Longest wait 56ms for reply type 6041, peak Tx sync delay 6, free buffers 50 (min 49), ts 2397/2396/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 18722/18722
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2b880
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server version 3.5.0-rc.3 (2024-01-26 12:34:19)
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 39.59, max time between full transfers: 40.5ms, max pin wait times: 38.0ms/1.2ms
Codes per second: 0.03
Maximum length of RX/TX data transfers: 3136/484

For as far as I know my system is on the highest version of everything installed through SSH:

Duet 3 MB6HC	                MB6HC	3.4.1
Duet 3 Expansion M23CL	M23CL	3.5.0-rc.1+
Duet 3 Expansion M23CL	M23CL	3.5.0-rc.1+
Duet Software Framework	DSF	        3.5.0-rc.3
Duet Web Control	        DWC	3.5.0-rc.3

Any help would be greatly apreciated.

Best, Gilles