CAN board not responding
-
Hi all,
One of my 1HCl boards is acting up. It's status LED is flashing in sync with the one on the 6HC, but after a firmware reset it is not responding at the default address. I wrote a small script that also checks all other addresses, but no luck either. It's also not the wiring, if I unplug the board, the led starts flashing rapidly, indicating a loss of CAN communication. I also tested another 1HCL board with the same wiring and it works fine.
I also retested on a Mini5plus, here the faulty board flashes rapidly while the other board works fine. Reseting the faulty board while connectd to the Mini makes it flash 4 times in a row, this stops when I take off the reset jumper, it will flash rapidly afterwards.
-
Can you share an M122 and M122 B# from the Duet and 1HCL in question?
-
@Phaedrux
M122 of the Mini:=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.1 (2023-08-31 16:16:56) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: 1YQL7-SR6KL-K65J0-409NU-12W1Z-RJPQ9 Used output buffers: 1 of 40 (18 max) Error in macro line 28 while starting up: Response timeout: CAN addr 21, req type 6041, RID=0 === RTOS === Static ram: 102836 Dynamic ram: 121052 of which 0 recycled Never used RAM 14672, free system stack 206 words Tasks: NETWORK(1,ready,33.0%,249) HEAT(3,nWait,0.0%,355) Move(4,nWait,0.0%,358) CanReceiv(6,nWait,0.0%,939) CanSender(5,nWait,0.0%,337) CanClock(7,delaying,0.0%,342) TMC(4,nWait,0.6%,116) MAIN(1,running,57.4%,704) IDLE(0,ready,8.1%,29) AIN(4,delaying,0.8%,272), total 100.0% Owned mutexes: === Platform === Last reset 00:03:26 ago, cause: power up Last software reset at 2023-09-06 09:52, reason: User, Gcodes spinning, available RAM 17804, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00487000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 MCU revision 3, ADC conversions started 206952, completed 206951, timed out 0, errs 0 MCU temperature: min 20.0, current 30.3, max 30.5 Supply voltage: min 24.2, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/64/0, gc cycles 0 Events: 1 queued, 1 completed Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 10848, writes 12, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 10848, writes 12, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 10848, writes 12, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 10849, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 10850, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-09-22 10:17:37 Cache data hit count 324275953 Slowest loop: 13.55ms; fastest: 0.16ms === Storage === Free file entries: 19 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 3.8ms, write time 5.1ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, 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, 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 0x000080f Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 1802, received 0, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 26 (min 25), ts 1034/0/0 Tx timeouts 0,0,1033,13,0,753 last cancelled message type 30 dest 127 === Network === Slowest loop: 18.81ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 1.26 MAC address e8:68:e7:e5:b5:01 Module reset reason: Power up, Vcc 3.43, flash size 2097152, free heap 25888 WiFi IP address 172.16.1.38 Signal strength -83dBm, channel 0, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0M122 of the borad:
Error: M122: Response timeout: CAN addr 21, req type 6024, RID=14 -
@nikscha said in CAN board not responding:
M122 of the borad:
Does it ever respond correctly to an M122?
When and where was the board purchased?
-
@Phaedrux It used to work fine and respond to M122. I aquired the board through E3D about a month ago.
It's the same board I had this issue with: https://forum.duet3d.com/topic/33559/3-5-0-rc-1-1hcl-expansionboard-needs-resetting/3?_=1695630650041
-
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
-
@Phaedrux Will do, thank you ^^
