Duet3/RPi 3.2B3.2: Toolboard Error: Response timeout
-
First time I've run into this. I just received the following error while performing mesh bed leveling on a Duet 3/RPi and toolboard. Hopefully something was caught in the M122 results that will be helpful.
I see a lot of lost messages being reported on the toolboard.. can't say I've seen this before.
Error: Response timeout: CAN addr 20, req type 6037, RID=1349M122:
=== Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2-beta3.2 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode) Board ID: 08DJM-956L2-G43S4-6J1DD-3SJ6S-TB62H Used output buffers: 8 of 40 (18 max) === RTOS === Static ram: 122236 Dynamic ram: 139580 of which 64 recycled Never used RAM 130312, free system stack 128 words Tasks: Linux(ready,67) HEAT(blocked,186) CanReceiv(blocked,869) CanSender(blocked,339) CanClock(blocked,352) TMC(blocked,18) MAIN(running,669) IDLE(ready,19) Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:27:42 ago, cause: software Last software reset at 2020-11-22 09:56, reason: User, GCodes spinning, available RAM 130312, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0xffffffff Task Linu Error status: 0x00 MCU temperature: min 38.9, current 40.6, max 40.8 Supply voltage: min 1.4, current 24.2, max 24.2, under voltage events: 1, over voltage events: 0, power good: yes 12V rail voltage: min 0.2, current 12.1, max 12.2, under voltage events: 0 Driver 0: position 30480, standstill, reads 40419, writes 44 timeouts 0, SG min/max 0/335 Driver 1: position 0, standstill, reads 40442, writes 22 timeouts 0, SG min/max 0/0 Driver 2: position 1000, standstill, reads 40420, writes 44 timeouts 0, SG min/max 0/321 Driver 3: position 0, standstill, reads 40415, writes 50 timeouts 0, SG min/max 0/613 Driver 4: position 0, standstill, reads 40444, writes 22 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 40417, writes 50 timeouts 0, SG min/max 0/801 Date/time: 2020-11-22 10:24:39 Slowest loop: 1250.40ms; fastest: 0.08ms === 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 === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 370, MaxWait: 643231ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 678, completed moves 678, StepErrors 0, LaErrors 0, Underruns [0, 0, 5], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 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 = 2 -1 -1 -1 Heater 0 is on, I-accum = 0.3 Heater 1 is on, I-accum = 0.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 sent 8206, send timeouts 8206, longest wait 2ms for type 6049, free CAN buffers 47 === SBC interface === State: 0, failed transfers: 0 Last transfer: 18ms ago RX/TX seq numbers: 52188/52190 SPI underruns 0, overruns 0 Number of disconnects: 1, IAP RAM available 0x20a30 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.2.0-beta3 Trigger: Finishing macro config.g, started by system > Next stack level Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 31.55M122 B20
Diagnostics for board 20: Duet TOOL1LC firmware version 3.2-beta3.2 (2020-11-13) Bootloader ID: SAMC21 bootloader version 2.1 (2020-11-03b2) Never used RAM 4244, free system stack 72 words HEAT 43 CanAsync 84 CanRecv 82 TMC 53 MAIN 333 AIN 64 Last reset 00:27:33 ago, cause: power up Last software reset data not available Driver 0: position 0, 830.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcount 12, reads 40193, writes 12, timeouts 0, DMA errors 0, failedOp 0xff Moves scheduled 0, completed 0, in progress 0, hiccups 0 No step interrupt scheduled VIN: 24.2V MCU temperature: min 53.3C, current 59.8C, max 61.3C Ticks since heat task active 56, ADC conversions started 1646714, completed 1646712, timed out 0 Last sensors broadcast 0x00000002 found 1 59 ticks ago, loop time 0 Free CAN buffers: 36, messages lost 16494, duplicates 0, oos 0, busOff 0 -
Is that mcu temp on the B20 report represent the temps on the toolboard? I wonder if there’s throttling that comes into play that may cause the issue.
-
I’m surprised to see this, but have never analyzed it before.. this may just be its operating temperature. The toolboard is in a heated chamber, but it was not heated when running the G29. In fact, I had the chamber heated to 70c right after this for a 4 hour print without any issue..
