Strange errors after update to 3.4

[martin7404]

HI
My corexy was running 3.4 b3 for a few months.
Updated to 3.4 official and some minor errors pop out.
The machine is runing 24/7 for the last few days

1. During start of a new print about 20 minutes in Pause and error that chamber heater fault, reset heater resume print and it finished ok after 20 hours.
2. Today new print everything goest great and when I look in to the console

3/30/2022, 1:34:47 PM	Error: Response timeout: CAN addr 121, req type 6013, RID=227
3/30/2022, 1:34:46 PM	Error: Response timeout: CAN addr 121, req type 6037, RID=226
Error: Failed to enable probe
3/30/2022, 1:32:12 PM	File 0:/gcodes/LoftVersion_FrontLoad_20210311_ForMold (2)-Imported3_0.6n_0.3mm_ABS__14h19m.gcode selected for printing
Error: in GCode file line 17: G10: Invalid tool number
3/30/2022, 1:32:11 PM	M32 "0:/gcodes/LoftVersion_FrontLoad_20210311_ForMold (2)-Imported3_0.6n_0.3mm_ABS__14h19m.gcode"
File 0:/gcodes/LoftVersion_FrontLoad_20210311_ForMold (2)-Imported3_0.6n_0.3mm_ABS__14h19m.gcode selected for printing
Error: in GCode file line 17: G10: Invalid tool number

I usually preheat the chamber and run 3 point traming with G32 before starting a job , so printer is homed and bed level . Then in the gcode I do g29 for mesh bed level. I do not know if the machine used old mesh or did not use any at all
M115 of toolboard gives:

m115 b121
Warning: Discarded std reply src=121 RID=227 exp 228 ""
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0 (2022-03-15 09:00:04)

Everythings works , the print job is ongoing good , no pause only red error in the console
Any advice ?

[Phaedrux]

Can you please share your config.g and the results of M98 P"config.g" as well as M122 and M122 B# where # is the can address of each of your expansion boards?

[martin7404]

@phaedrux

3/31/2022, 10:18:15 AM	m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-9P63L-DJMSS-6JKDA-3S86L-1BDB9
Used output buffers: 1 of 40 (27 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 96356 of which 252 recycled
Never used RAM 99320, free system stack 112 words
Tasks: NETWORK(ready,37.0%,173) ETHERNET(notifyWait,1.3%,161) HEAT(notifyWait,0.3%,316) Move(notifyWait,23.7%,241) CanReceiv(notifyWait,0.4%,772) CanSender(notifyWait,0.3%,346) CanClock(delaying,0.1%,333) TMC(notifyWait,19.1%,58) MAIN(running,17.8%,925) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 138:12:40 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 103268, 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
Step timer max interval 190
MCU temperature: min 20.4, current 21.7, max 28.1
Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/252/252, gc cycles 0
Events: 1 queued, 1 completed
Driver 0: standstill, SG min 25, mspos 452, reads 56265, writes 2 timeouts 0
Driver 1: standstill, SG min 25, mspos 948, reads 56265, writes 2 timeouts 0
Driver 2: standstill, SG min n/a, mspos 8, reads 56267, writes 0 timeouts 0
Driver 3: standstill, SG min 0, mspos 312, reads 56261, writes 6 timeouts 0
Driver 4: standstill, SG min 0, mspos 760, reads 56262, writes 6 timeouts 0
Driver 5: standstill, SG min 0, mspos 200, reads 56261, writes 6 timeouts 0
Date/time: 2022-03-31 09:18:12
Slowest loop: 999.75ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.9ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 37, maxWait 1595536ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 816469, completed 816469, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 47, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters 2 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.2
=== GCodes ===
Segments left: 0
Movement lock held by 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
Code queue is empty
=== CAN ===
Messages queued 1453344, received 1456822, lost 0, boc 44
Longest wait 850ms for reply type 6029, peak Tx sync delay 65518, free buffers 50 (min 19), ts 364147/360650/0
Tx timeouts 4482,0,3475,0,0,1837 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 18.12ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0
3/31/2022, 9:01:32 AM	Finished printing file 0:/gcodes/LoftVersion_FrontLoad_20210311_ForMold (2)-Imported3_0.6n_0.3mm_ABS__14h19m.gcode, print time was 19h 29m

m122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0 (2022-03-15 09:00:04)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2624, free system stack 35 words
Tasks: Move(notifyWait,38.4%,91) HEAT(notifyWait,26.4%,95) CanAsync(notifyWait,0.0%,51) CanRecv(notifyWait,6.8%,74) CanClock(notifyWait,1.8%,65) ACCEL(notifyWait,0.0%,61) TMC(delaying,70.2%,57) MAIN(running,34.2%,351) IDLE(ready,0.0%,26) AIN(delaying,33.7%,142), total 211.5%
Last reset 138:13:45 ago, cause: power up
Last software reset data not available
Driver 0: pos 294435424, 395.7 steps/mm,standstill, SG min 0, read errors 106, write errors 0, ifcnt 24, reads 39131, writes 24, timeouts 176, DMA errors 0, CC errors 0, failedOp 0x71, steps req 302704478 done 302704478
Moves scheduled 4564537, completed 4564537, in progress 0, hiccups 0, step errors 0, maxPrep 566, maxOverdue 8739366, maxInc 4528284, mcErrs 0, gcmErrs 0
Peak sync jitter -2/23, peak Rx sync delay 231, resyncs 191/16, no step interrupt scheduled
VIN voltage: min 23.9, current 24.2, max 24.3
MCU temperature: min 28.9C, current 47.0C, max 82.9C
Last sensors broadcast 0x00000002 found 1 220 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 9957429, send timeouts 364, received 9037591, lost 0, free buffers 37, min 8, error reg ff0000
Last cancelled message type 4514 dest 127
dup 117, oos 1992/33/1008/209, bm 0, wbm 0, rxMotionDelay 1120, adv -4534913/205706
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0

[martin7404]

@phaedrux said in Strange errors after update to 3.4:

M98 P"config.g"

3/31/2022, 10:21:24 AM	Accelerometer 121:0 type LIS3DH with orientation 5 samples at 1344Hz with 10-bit resolution
Warning: Heater 0 predicted maximum temperature at full power is 224°C
Warning: Heater 1 predicted maximum temperature at full power is 547°C
Error: bad model parameters
3/31/2022, 10:21:22 AM	M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

[dc42]

@martin7404 the "Response timeout" messages suggest that the CAN connection may be intermittent, perhaps due to a bad connection.

You could also check that the CAN bus is properly terminated. With power off, if you use a multimeter to measure between CANH and CANL anywhere on the bus, the reading should be close to 60 ohms. If it's 120 ohms instead then either there is no termination or there is a break in the wire between where you are measuring from and the termination.

[martin7404]

@dc42 Thank you
After careful review, the printed plate on which the tool board had a broken strain relief. During commissioning It was put as a test part, to be exchanged for ALu machined part, and left there for almost 6 months
I will also re crimp the CAN cable at the tool board

[martin7404]

@dc42 So strain fixed everything ok 3 point traming , bed leveling and when it is finished in gcode I awitch the heater from standbay to active together with fast position XY AND HERE IT IS

m122 b121
Warning: Discarded std reply src=121 RID=303 exp 304 "Accen�"
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0 (2022-03-15 09:00:04)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2624, free system stack 45 words
Tasks: Move(notifyWait,1.8%,91) HEAT(notifyWait,62.8%,97) CanAsync(notifyWait,0.0%,59) CanRecv(notifyWait,4.0%,74) CanClock(notifyWait,5.9%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,945.6%,57) MAIN(running,5372.1%,351) IDLE(ready,0.0%,26) AIN(delaying,1542.0%,142), total 7934.4%
Last reset 06:22:59 ago, cause: software
Last software reset data not available
Driver 0: pos 104828, 395.7 steps/mm,ok, SG min 0, read errors 0, write errors 1, ifcnt 24, reads 20359, writes 12, timeouts 5, DMA errors 0, CC errors 0, failedOp 0x6a, steps req 113850 done 113830
Moves scheduled 2089, completed 2088, in progress 1, hiccups 0, step errors 0, maxPrep 502, maxOverdue 2719617, maxInc 2367052, mcErrs 0, gcmErrs 0
Peak sync jitter -1/4, peak Rx sync delay 216, resyncs 2/0, next step interrupt due in 100 ticks, enabled
VIN voltage: min 24.1, current 24.3, max 24.3
MCU temperature: min 29.3C, current 66.3C, max 66.3C
Last sensors broadcast 0x00000002 found 1 154 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 460079, send timeouts 22, received 208997, lost 0, free buffers 37, min 37, error reg 810086
Last cancelled message type 4511 dest 0
dup 0, oos 1/0/1/1, bm 0, wbm 0, rxMotionDelay 416, adv -2429537/74646
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0
4/1/2022, 12:19:26 AM	Error: Response timeout: CAN addr 121, req type 6013, RID=303
4/1/2022, 12:19:24 AM	M140 P0 S110
Error: Response timeout: CAN addr 121, req type 6037, RID=302
Error: Failed to enable probe

May be I should replacw the data CAN cable

[Phaedrux]

@martin7404 said in Strange errors after update to 3.4:

May be I should replacw the data CAN cable

Worth a shot.

[martin7404]

So yesterday I did reset the board (emergency on DWS) and started the print again 8 hours in everything OK including G32 and G29 in the begining.
Here is M122 B121

m122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0 (2022-03-15 09:00:04)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2624, free system stack 45 words
Tasks: Move(notifyWait,5.0%,91) HEAT(notifyWait,2.5%,95) CanAsync(notifyWait,0.0%,57) CanRecv(notifyWait,0.8%,74) CanClock(notifyWait,0.2%,65) ACCEL(notifyWait,0.0%,61) TMC(delaying,28.5%,57) MAIN(running,16.4%,351) IDLE(ready,0.0%,26) AIN(delaying,46.6%,142), total 100.0%
Last reset 10:40:48 ago, cause: software
Last software reset data not available
Driver 0: pos 26193656, 395.7 steps/mm,ok, SG min 0, read errors 4, write errors 1, ifcnt 40, reads 5300, writes 13, timeouts 9, DMA errors 0, CC errors 0, failedOp 0x01, steps req 26816192 done 26816164
Moves scheduled 462622, completed 462619, in progress 1, hiccups 0, step errors 0, maxPrep 525, maxOverdue 919192, maxInc 759560, mcErrs 0, gcmErrs 0
Peak sync jitter -1/4, peak Rx sync delay 231, resyncs 3/0, next step interrupt due in 225 ticks, enabled
VIN voltage: min 24.1, current 24.3, max 24.3
MCU temperature: min 47.6C, current 80.4C, max 80.6C
Last sensors broadcast 0x00000002 found 1 223 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 770264, send timeouts 44, received 808792, lost 0, free buffers 37, min 36, error reg 870000
Last cancelled message type 4519 dest 0
dup 0, oos 0/0/0/3, bm 0, wbm 0, rxMotionDelay 474, adv -918856/74660
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0

I see that My tool board sitting on top of the carriage is about 80 degC, bed 110 degC , chamber 50 deg C. Should I worry about 80 deg C on the toolboard

[Phaedrux]

@martin7404 said in Strange errors after update to 3.4:

Should I worry about 80 deg C on the toolboard

That's probably at the high end of acceptable.

[martin7404]

@phaedrux also I am not sure how acutaye it is.
I might consider some cooler there