Incompatible software versions error, but same firmware in use

Duncan

Hello,

I had a problem with my toolboard 1LC that some connectors broke and I put a new one... I use M997 to update 1LC firmware but now I have this error of different software versions in my screen... but I have the same firmware on both... what can I do?

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.5.1 (2024-04-19 14:30:55) running on Duet 3 MB6HC v1.01 (standalone mode)
Board ID: 08DJM-9P63L-DJ3S0-7JTD4-3S86P-9AJM9
Used output buffers: 6 of 40 (33 max)
=== RTOS ===
Static ram: 155208
Dynamic ram: 120652 of which 0 recycled
Never used RAM 70132, free system stack 200 words
Tasks: NETWORK(1,ready,40.6%,183) ETHERNET(5,nWait 7,0.1%,317) HEAT(3,nWait 6,0.0%,323) Move(4,nWait 6,0.0%,336) CanReceiv(6,nWait 1,0.1%,550) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,339) TMC(4,nWait 6,9.2%,54) MAIN(1,running,50.1%,105) IDLE(0,ready,0.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:06:15 ago, cause: power up
Last software reset at 2025-06-06 20:53, reason: User, Gcodes spinning, available RAM 67392, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 48.2, current 48.7, max 48.8
Supply voltage: min 24.1, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
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 n/a, mspos 4, reads 61381, writes 0 timeouts 0
Driver 1: standstill, SG min n/a, mspos 4, reads 61380, writes 0 timeouts 0
Driver 2: standstill, SG min n/a, mspos 4, reads 61380, writes 0 timeouts 0
Driver 3: standstill, SG min n/a, mspos 4, reads 61380, writes 0 timeouts 0
Driver 4: standstill, SG min n/a, mspos 4, reads 61380, writes 0 timeouts 0
Driver 5: standstill, SG min n/a, mspos 4, reads 61381, writes 0 timeouts 0
Date/time: 2025-06-06 21:07:02
Slowest loop: 28.52ms; fastest: 0.07ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 0.5ms, 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 0 -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 idle 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 0x80000003
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== Filament sensors ===
check 0 clear 0
Extruder 0 sensor: no filament
=== CAN ===
Messages queued 4775, received 4822, lost 0, errs 12635, boc 0
Longest wait 4ms for reply type 6024, peak Tx sync delay 63076, free buffers 50 (min 49), ts 1240/1228/0
Tx timeouts 0,0,12,0,0,7 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 5.26ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
Interface state: active
Error counts: 0 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

M122 B20
Diagnostics for board 20:
Duet TOOL1LC rev 1.0 or earlier firmware version 3.5.1 (2024-04-19 14:42:41)
Bootloader ID: SAMC21 bootloader version 2.11 (2024-08-09)
All averaging filters OK
Never used RAM 5544, free system stack 136 words
Tasks: Move(3,nWait 7,0.0%,135) HEAT(2,nWait 6,0.1%,131) CanAsync(5,nWait 4,0.0%,55) CanRecv(3,nWait 1,0.0%,71) CanClock(5,nWait 1,0.0%,59) TMC(2,nWait 6,3.4%,53) MAIN(1,running,92.1%,431) IDLE(0,ready,0.0%,41) AIN(2,delaying,4.4%,112), total 100.0%
Owned mutexes:
Last reset 00:02:05 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 80.0 steps/mm, standstill, SG min 0, read errors 0, write errors 1, ifcnt 23, reads 62744, writes 9, timeouts 0, DMA errors 0, CC errors 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/10, peak Rx sync delay 203, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 24.3, current 24.3, max 24.3
MCU temperature: min 41.3C, current 41.9C, max 42.0C
Last sensors broadcast 0x00000000 found 0 32 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 1024, send timeouts 0, received 1141, lost 0, errs 0, boc 0, free buffers 18, min 18, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: none
I2C bus errors 4565, naks 4565, contentions 4565, other errors 4565

UDPATE:

Anyway, I've noticed something that concerns me. When I replaced the 1LC, it was because the hotend wasn't receiving 24V when connected, and I thought the connector was broken... but the thing is, it's not working with this new one either, and now I'm starting to doubt that it's due to incompatible software, since I didn't have that issue before...

Therefore, I'm still having the same problem as before (no voltage at the hotend when activated), and now there's a new one: a software incompatibility.

And I also don't understand the hotend failure, because it was working fine and suddenly started to fail... it would reach lower and lower temperatures until it gave an error, and now it doesn’t work at all.

And the red light on the left side of the board is blinking normally, and the other two lights (red and blue) are on.

jay_s_uk

@Duncan it could also be the version of DWC you have installed that could be different

Duncan

@jay_s_uk said in Incompatible software versions error, but same firmware in use:

DWC

But the only thing I changed was the 1LC board, and before I had no problems with that.

Anyway, I've noticed something that concerns me. When I replaced the 1LC, it was because the hotend wasn't receiving 24V when connected, and I thought the connector was broken... but the thing is, it's not working with this new one either, and now I'm starting to doubt that it's due to incompatible software, since I didn't have that issue before...

Therefore, I'm still having the same problem as before (no voltage at the hotend when activated), and now there's a new one: a software incompatibility.

And I also don't understand the hotend failure, because it was working fine and suddenly started to fail... it would reach lower and lower temperatures until it gave an error, and now it doesn’t work at all.

And the red light on the left side of the board is blinking normally, and the other two lights (red and blue) are on.

jay_s_uk

@Duncan software incompatibility wouldn't stop the hotend working.
I suggest you get a multimeter on the hotend. Sounds like it has failed and not the toolboard

Duncan

@jay_s_uk
I put a new heater cartridge and the problem persists... If I put the multimeter and turn the heater on I don't get 24V on the output, and that's why I change the 1LC first place... but I don't know why it's failing.

Phaedrux

Can you share a diagram or photo of your wiring?

How have you updated the firmware previously? I suggest you upload th complete zip file again and allow it to update everything again.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.5.1/Duet2and3Firmware-3.5.1.zip

Also, 3.5.1 is quite old at this point. Once you have everything worked out I suggest you update to 3.6.

It wouldn't hurt to share your config.g file as well.

Duncan

@Phaedrux
Hello,
I updated the firmware to 3.6.. the software error dissapear, but problem with hotend heater persists...

This is the wiring

This is the config

; General
G90 ; absolute coordinates
M83 ; relative extruder moves
M550 P"BIGC3D" ; set hostname

; Accessories
M575 P1 S0 B57600 ; configure PanelDue support

; Network
M552 P0.0.0.0 S1 ; configure Ethernet adapter
M586 P0 S1 ; configure HTTP

; Wait a moment for the CAN expansion boards to become available
G4 S2

; Smart Drivers
M569 P0.0 S0 D2 ; driver 0.0 goes backwards (Y axis)
M569 P0.1 S0 D2 ; driver 0.1 goes backwards (Z axis)
M569 P0.2 S0 D2 ; driver 0.2 goes backwards (Z axis)
M569 P0.3 S0 D2 ; driver 0.3 goes backwards (X axis)
M569 P0.4 S0 D2 ; driver 0.4 goes backwards (Z axis)
M569 P0.5 S0 D2 ; driver 0.5 goes backwards (Z axis)
M569 P20.0 S1 D2 ; driver 121.0 goes forwards (extruder 0)

; Motor Idle Current Reduction
M906 I30 ; set motor current idle factor
M84 S30 ; set motor current idle timeout

; Axes
M584 X0.3 Y0.0 Z0.1:0.2:0.4:0.5 ; set axis mapping
M350 X32 Y32 Z32 I1 ; configure microstepping with interpolation
M906 X2800 Y4000 Z2800 ; set axis driver currents
M92 X213.883 Y213.883 Z1280 ; configure steps per mm
M208 X0:1100 Y0:1100 Z0:1000 ; set minimum and maximum axis limits
M566 X900 Y900 Z12 ; set maximum instantaneous speed changes (mm/min)
M203 X20000 Y20000 Z1000 ; set maximum speeds (mm/min)
M201 X1000 Y1000 Z200 ; set accelerations (mm/s^2)

; Extruders
M584 E20.0 ; set extruder mapping
M350 E16 I1 ; configure microstepping with interpolation
M906 E800 ; set extruder driver currents
M92 E561.6 ; configure steps per mm
M566 E120 ; set maximum instantaneous speed changes (mm/min)
M203 E1200 ; set maximum speeds (mm/min)
M201 E250 ; set accelerations (mm/s^2)

; Kinematics
M669 K0 ; configure Cartesian kinematics
M671 X1115:1115:-15:-15 Y1360:-260:-260:1360 S0.5	; J- configuramos la posición de los husillos respecto el origen (0,0) de la cama (no de los finales de carrera)

; Probes
M558 K0 P9 C"20.io0.in" H5 F480 T10000 ; configure BLTouch probe via slot #0
G31 P500 X-20 Y40 Z0.23 ; set Z probe trigger value, offset and trigger height
M950 S0 C"20.io0.out" ; create servo #0 for BLtouch

; Endstops
M574 X1 P"io2.in" S1 ; configure X axis endstop
M574 Y1 P"io1.in" S1 ; configure Y axis endstop
M574 Z1 P"io3.in+io4.in+io5.in+io6.in" S1 ; configure Z axis endstop

; Mesh Bed Compensation
M557 X50:1050 Y50:1050 S50:50 ; define grid for mesh bed compensation

; Sensors
M308 S0 P"temp3" Y"thermistor" T100000 B4725 ;C7.06e-8 ; configure sensor #0
M308 S1 P"20.temp0" Y"pt1000" ; configure sensor #1

; Heaters
M950 H0 C"out0" T0 ; create heater #0
M143 H0 P0 T0 C0 S120 A0 ; configure heater monitor #0 for heater #0
;M307 H0 R2.43 D5.5 E1.35 K0.56 B1 ; configure model of heater #0
M307 H0 A340 C2745.9 D25 S1.00 B0                               ; enable bang-bang mode for the bed heater and set PWM limit - OLD FIRMWARE 3.4.3
M950 H1 C"20.out0" T1 ; create heater #1
M143 H1 P0 T1 C0 S290 A0 ; configure heater monitor #0 for heater #1
;M307 H1 R2.43 D5.5 E1.35 K0.56 B0 S100 ; configure model of heater #1
M307 H1 R4.221 K0.860:0.000 D1.42 E1.35 S1.00 B0 V22.7 ;after PID configuration tool calibration

; Heated beds
M140 P0 H0 ; configure heated bed #0

; Fans
M950 F0 C"20.out2" ; create fan #0
M106 P0 S0 B0.1 H1 T50 ; configure fan #0
M950 F1 C"20.out1" ; create fan #1
M106 P1 S0 L0 X1 B0.1 ; configure fan #1

; Tools
M563 P0 S"toolzero" D0 H1 F0 ; create tool #0
;M568 P0 X0 Y0 Z0 ; set custom offsets for tool #0
;M568 P0 R0 S0 ; set initial tool #0 active and standby temperatures to 0C
G10 P0 X0 Y0 Z0                                         ; set tool 0 axis offsets
G10 P0 R0 S0                                            ; set initial tool 0 active and standby temperatures to 0C
M591 D0 P1 C"20.io1.in" S1							; filament monitor connected to E0_stop - old firmware 3.4.3
M591 D0

; Miscellaneous
M564 H0
M302 P1
T0 ;activamos la herramienta T0

m122 b20
Diagnostics for board 20:
Duet TOOL1LC rev 1.0 or earlier firmware version 3.6.0 (2025-05-25 08:04:05)
Bootloader ID: SAMC21 bootloader version 2.11 (2024-08-09)
All averaging filters OK
Never used RAM 8464, free system stack 138 words
Tasks: Move(3,nWait 7,0.0%,140) TMC(2,delaying,3.7%,52) HEAT(2,nWait 6,0.1%,84) CanAsync(5,nWait 4,0.0%,58) CanRecv(3,nWait 1,0.0%,70) CanClock(5,nWait 1,0.0%,60) MAIN(1,running,91.4%,318) IDLE(0,ready,0.0%,40) AIN(2,delaying,4.7%,112), total 100.0%
Owned mutexes:
Last reset 00:00:45 ago, cause: software
Last software reset data not available
Moves scheduled 0, hiccups 0 (0.00/0.00ms), segs 0, step errors 0 (types 0x0), maxLate 0 maxPrep 0, ebfmin 0.00 max 0.00
Sync err accum 586, peak jitter -3/29, peak Rx delay 204, resyncs 0/0, no timer interrupt scheduled, next step interrupt due in 4260831815 ticks, disabled
VIN voltage: min 24.3, current 24.3, max 24.4
MCU temperature: min 37.6C, current 38.3C, max 38.4C
Driver 0: pos 0, 561.6 steps/mm, standstill, SG min 0, read errors 0, write errors 1, ifcnt 36, reads 22736, writes 12, timeouts 0, DMA errors 0, CC errors 0
Last sensors broadcast 0x00000002 found 1 163 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 806, send timeouts 5, received 354, lost 0, ignored 0, errs 32904, boc 0, free buffers 18, min 18, error reg 110000
Last cancelled message type 4519 dest 0
dup 0, oos 0/0/0/0, rxMotionDelay 0
Accelerometer: none
I2C bus errors 4565, naks 4565, contentions 4565, other errors 4565
=== Filament sensors ===
Interrupt 5726621 to 0us, poll 4 to 536us
Driver 0: ok

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.6.0 (2025-05-25 08:05:42) running on Duet 3 MB6HC v1.01 (standalone mode)
Board ID: 08DJM-9P63L-DJ3S0-7JTD4-3S86P-9AJM9
Used output buffers: 3 of 40 (18 max)
=== RTOS ===
Static ram: 137420
Dynamic ram: 127528 of which 0 recycled
Never used RAM 79108, free system stack 202 words
Tasks: NETWORK(1,ready,31.9%,180) ETHERNET(5,nWait 7,0.4%,562) HEAT(3,nWait 6,0.0%,350) Move(4,nWait 6,0.0%,329) TMC(4,nWait 6,2.9%,377) CanReceiv(6,nWait 1,0.0%,794) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,353) MAIN(1,running,64.3%,103) IDLE(0,ready,0.4%,29) USBD(3,blocked,0.0%,149), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:33 ago, cause: software
Last software reset at 2025-06-06 21:12, reason: User, Gcodes spinning, available RAM 69668, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043c000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 42.2, current 44.0, max 44.5
Supply voltage: min 24.1, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/12/0, gc cycles 0
Events: 2 queued, 2 completed
Date/time: 2025-06-08 11:14:39
Slowest loop: 7.19ms; fastest: 0.07ms
=== Storage ===
Free file entries: 20
SD card 0 detected, requested/actual speed: 25.0/25.0MBytes/sec
SD card longest read time 0.6ms, write time 0.0ms, max retries 0
=== Move ===
Segments created 0, 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 0.00/0/0.00 0.00/0/0.00
Next step interrupt due in 44 ticks, disabled
Driver 0: standstill, SG min n/a, mspos 4, reads 666, writes 17 timeouts 0
Driver 1: standstill, SG min n/a, mspos 4, reads 666, writes 17 timeouts 0
Driver 2: standstill, SG min n/a, mspos 4, reads 667, writes 17 timeouts 0
Driver 3: standstill, SG min n/a, mspos 4, reads 667, writes 17 timeouts 0
Driver 4: standstill, SG min n/a, mspos 4, reads 667, writes 17 timeouts 0
Driver 5: standstill, SG min n/a, mspos 4, reads 667, writes 17 timeouts 0
Phase step loop runtime (us): min=0, max=122, frequency (Hz): min=1685, max=2459
=== DDARing 0 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x80000003, drives owned 0x80000003
Code queue is empty
=== DDARing 1 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000
Code queue is empty
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1 -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, null
HTTP is idle 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
=== Filament sensors ===
Driver 31: no filament
=== CAN ===
Messages queued 310, received 693, lost 0, ignored 0, errs 1, boc 0
Longest wait 2ms for reply type 6053, peak Tx sync delay 407, free buffers 50 (min 49), ts 158/157/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 4.09ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0
= Ethernet =
Interface state: active
Error counts: 0 0 0 1 0 0
Socket states: 6 2 2 2 2 0 0 0 0

droftarts

@Duncan Do you have a multimeter? Check for 24V between VIN pin on out0 and GND. This should always be 24V, as the heater is switched on the GND side. If it's not turning on, it's possible the MOSFET that controls the GND switching has failed. Also check the resistance of the heater, it's possible your replacement is faulty.

Your diagram says 'PT100'; I assume that's an error, and it's a PT1000, which is configured in the config.g? Do you get sensible temperatures shown in DWC?

To check versions, look in DWC > Settings > Machine-Specific > Electronics. Board and DWC versions should match.

Ian

Duncan

@droftarts you're right... the replacement is faulty... I can't believe it...

At least now I'm running 3.6... something good...

Thank you very much

droftarts

@Duncan said in Incompatible software versions error, but same firmware in use:

the replacement is faulty

Do you mean the heater cartridge or 1LC? If it's the 1LC, it should be covered by the warranty. See https://www.duet3d.com/page/warranty-policy

Ian