NEW PROBLEM WITH 1LC CARD

Gianluca · 21 Feb 2024, 21:04

I also did some tests in stand alone mode, and the problem remained, I attach console report.
I made a small print and before finishing it stopped permanently and now the 1LC card no longer responds, it seems broken.
I purchased the card in April 2023 and until yesterday it always worked well.
What can I do?

21/2/2024, 20:54:17: Connected to 192.168.1.220
21/2/2024, 20:55:31: Upload of config.g successful after 0s
21/2/2024, 20:55:34: M98 P"config.g": HTTP is enabled on port 80
21/2/2024, 20:58:36: : Error: CAN response timeout: board 121, req type 6061, RID 146
21/2/2024, 20:58:45: : Warning: Discarded std reply src=121 RID=146 exp=147 ""
21/2/2024, 20:58:50: Connection interrupted, attempting to reconnect...: Operation failed (Reason: Service Unavailable)
21/2/2024, 20:58:50: Connection established
21/2/2024, 20:59:05: : Error: Expansion board 121 stopped sending status
21/2/2024, 20:59:15: : Error: Expansion board 121 reconnected
Error: Expansion board 121 reconnected
Error: Expansion board 121 reconnected
21/2/2024, 20:59:31: Connection interrupted, attempting to reconnect...: HTTP request timed out
21/2/2024, 20:59:31: Connection established
21/2/2024, 21:02:12: Connection interrupted, attempting to reconnect...: Operation failed (Reason: Service Unavailable)
21/2/2024, 21:02:12: Connection established
21/2/2024, 21:06:34: m122 b121: Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-rc.3 (2024-01-24 17:55:14)
Bootloader ID: SAMC21 bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 2912, free system stack 108 words
Tasks: Move(3,nWait 7,0.0%,135) HEAT(2,nWait 6,0.4%,115) CanAsync(5,nWait 4,0.0%,49) CanRecv(3,nWait 1,0.0%,71) CanClock(5,nWait 1,0.0%,59) ACCEL(3,nWait 6,0.0%,53) TMC(2,delaying,3.4%,53) MAIN(1,running,91.2%,315) IDLE(0,ready,0.0%,27) AIN(2,delaying,4.9%,112), total 100.0%
Owned mutexes:
Last reset 00:07:07 ago, cause: power up
Last software reset time unknown, reason: OutOfMemory, available RAM 16088, slot 2
Software reset code 0x01c0 ICSR 0x00000000 SP 0x20002770 Task MAIN Freestk 784 ok
Stack: 00004000 00005e8b 00004000 000041cf a5a5a5a5 00004000 a5a5a5a5 a5a5a5a5 a5a5a5a5 0001d199 a5a5a5a5 0001d1b5 a5a5a5a5 00005a4f a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
Driver 0: pos 0, 745.0 steps/mm, standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 17279, writes 12, 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 0/13, peak Rx sync delay 213, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 29.9, current 30.0, max 30.0
MCU temperature: min 29.4C, current 36.9C, max 36.9C
Last sensors broadcast 0x00000032 found 3 73 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 9278, send timeouts 0, received 4134, lost 0, errs 23472, boc 0, free buffers 18, min 18, error reg ff0000
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, contentions 0, other errors 0
=== Filament sensors ===
Interrupt 4 to 8us, poll 6 to 1176us
Driver 0: pos 2519.65, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
21/2/2024, 21:14:50: Upload of SERBATOIO_SOPRA_PLA.gcode successful after 43s
21/2/2024, 21:17:24: Upload of FERMAFILO 4X.gcode successful after 3s
21/2/2024, 21:20:00: : Resume state saved
21/2/2024, 21:24:22: Upload of config.g successful after 0s
21/2/2024, 21:28:15: : Error: Expansion board 121 stopped sending status
21/2/2024, 21:29:11: m122 b121
21/2/2024, 21:29:11: : Warning: Discarded std reply src=121 RID=348 exp=349 "deri~ "
21/2/2024, 21:29:12: : Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-rc.3 (2024-01-24 17:55:14)
Bootloader ID: SAMC21 bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 968, free system stack 59 words
Tasks: Move(3,nWait 7,0.1%,79) HEAT(2,nWait 6,0.4%,95) CanAsync(5,nWait 4,0.0%,49) CanRecv(3,nWait 1,0.0%,65) CanClock(5,nWait 1,0.0%,59) ACCEL(3,nWait 6,0.0%,53) TMC(2,delaying,3.5%,53) MAIN(1,running,88.4%,315) IDLE(0,ready,2.5%,27) AIN(2,delaying,5.0%,112), total 100.0%
Owned mutexes:
Last reset 00:29:45 ago, cause: power up
Last software reset time unknown, reason: OutOfMemory, available RAM 16088, slot 2
Software reset code 0x01c0 ICSR 0x00000000 SP 0x20002770 Task MAIN Freestk 784 ok
Stack: 00004000 00005e8b 00004000 000041cf a5a5a5a5 00004000 a5a5a5a5 a5a5a5a5 a5a5a5a5 0001d199 a5a5a5a5 0001d1b5 a5a5a5a5 00005a4f a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
Driver 0: pos 0, 745.0 steps/mm, ok, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 22558, writes 2, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 898509
Moves scheduled 7802, completed 7790, in progress 1, hiccups 0, segs 81, step errors 0, maxLate 0 maxPrep 268, maxOverdue 2518269, maxInc 659862, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 1.00
Peak sync jitter 0/13, peak Rx sync delay 222, resyncs 7/0, no timer interrupt scheduled
VIN voltage: min 28.8, current 30.0, max 30.1
MCU temperature: min 29.4C, current 37.6C, max 38.2C
Last sensors broadcast 0x00000032 found 3 40 ticks ago, 0 ordering errs, loop time 2
CAN messages queued 1383423, send timeouts 17, received 19848, lost 0, errs 161384, boc 0, free buffers 18, min 12, error reg ff000f
Last cancelled message type 4527 dest 0
dup 0, oos 32/0/0/20, bm 0, wbm 0, rxMotionDelay 359, adv -2518069/107884
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 0, contentions 0, other errors 0
=== Filament sensors ===
Interrupt 2 to 86us, poll 8 to 3377us
Driver 0: pos 13728.52, errs: frame 147 parity 0 ovrun 5896 pol 16 ovdue 0
21/2/2024, 21:34:45: : Error: Expansion board 121 stopped sending status
21/2/2024, 21:35:04: : Error: Expansion board 121 stopped sending status
21/2/2024, 21:35:07: : Error: CAN response timeout: board 121, req type 6013, RID 367
21/2/2024, 21:35:29: : Warning: Discarded std reply src=121 RID=367 exp=368 "imeo- "
21/2/2024, 21:36:19: : Error: Expansion board 121 reconnected
Error: Expansion board 121 reconnected
21/2/2024, 21:36:38: : Resume state saved
21/2/2024, 21:36:40: : Error: CAN response timeout: board 121, req type 6013, RID 370
21/2/2024, 21:36:41: : CAN response timeout: board 121, req type 6029, RID 371
21/2/2024, 21:36:42: : Error: Expansion board 121 stopped sending status

oliof · 22 Feb 2024, 10:12

@Gianluca show us some photos of the toolboard, and the wiring connection for CAN (both ends).

jay_s_uk · 22 Feb 2024, 10:14

@Gianluca can you try disabling the filament monitor?

dc42 · 22 Feb 2024, 11:36

@Gianluca also as you are using 3,5rc firmware please try the new firmware binaries at https://www.dropbox.com/scl/fo/p0136wx04h8xf6ejwdnn9/h?rlkey=efrfwyb6o5tqid11gustz3uvy&dl=0.

Gianluca · 24 Feb 2024, 12:53

@dc42 said in NEW PROBLEM WITH 1LC CARD:

@Gianluca also as you are using 3,5rc firmware please try the new firmware binaries at https://www.dropbox.com/scl/fo/p0136wx04h8xf6ejwdnn9/h?rlkey=efrfwyb6o5tqid11gustz3uvy&dl=0.

Last day, I replaced the CAN cable with a new one and the board started working again.
I made a print for 36 hours, but reported the "Expansion board 121 stopped sending status" error about 20 times, still completing the print.
As suggested I installed the R3+ on the 6HC, and everything went fine, then I installed the "Duet3Firmware_TOOL1LC.bin" file on the toolboard and it did not complete the update, blocking the card.
Now the 1LC is no longer seen on the mainboard.
How can I restore the toolboard, since the toolboard is no longer seen by the motherboard?

Phaedrux · 24 Feb 2024, 20:35

Try a factory reset

https://docs.duet3d.com/en/Duet3D_hardware/Duet_3_family/Duet_3_Toolboard_1LC#factory-reset

Gianluca · 25 Feb 2024, 00:31

@Phaedrux said in NEW PROBLEM WITH 1LC CARD:

Try a factory reset

https://docs.duet3d.com/en/Duet3D_hardware/Duet_3_family/Duet_3_Toolboard_1LC#factory-reset

Yes, I already tried, it doesn't work.
Attempting to install RC3+ knocked out the toolboard.
When turned on it flashes 3 quickly and then 5 quickly for 3 times, then the red LED is off.

droftarts · 26 Feb 2024, 12:25

@Gianluca See here for the LED flashes: https://docs.duet3d.com/User_manual/Machine_configuration/CAN_connection#led-behaviour-and-error-codes

Number of flashes:
3 Bad firmware CRC
5 The bootloader requested firmware but the main board reported that it didn't have the correct firmware file

It looks like the firmware upload failed, and the main board can't find a the correct firmware file. Download the 1LC firmware file again, and upload it to your Duet mainboard again, to the /firmware folder. Then reset the 1LC. Hopefully it will find the firmware and update, then.

Ian

Gianluca · 27 Feb 2024, 13:52

@droftarts

Unfortunately what was recommended did not unlock the toolboard.
I tried both in SBC and in stand alone mode.
Would it be possible to send the card to technical assistance for repairs under warranty?
The damage was done following DC42's instruction.
I also purchased a new 1LC toolboard from DHM Compass Project yesterday...

dc42 · 27 Feb 2024, 14:20

@Gianluca said in NEW PROBLEM WITH 1LC CARD:

When turned on it flashes 3 quickly and then 5 quickly for 3 times, then the red LED is off.

3 times is normal after telling the board to update, it just means that board doesn't have any valid firmware on it. 5 times means the Duet main board reported that it didn't have the requested firmware. So as Ian says, download the file from Github and upload it to the Duet again.

Gianluca · 27 Feb 2024, 17:30

@dc42 said in NEW PROBLEM WITH 1LC CARD:

@Gianluca said in NEW PROBLEM WITH 1LC CARD:

When turned on it flashes 3 quickly and then 5 quickly for 3 times, then the red LED is off.

3 times is normal after telling the board to update, it just means that board doesn't have any valid firmware on it. 5 times means the Duet main board reported that it didn't have the requested firmware. So as Ian says, download the file from Github and upload it to the Duet again.

Yes, that's exactly what I did last night, both in stand alone mode and in SBC, but the firmware doesn't load.
List of tests step by step:

downloaded the file Duet3Firmware_TOOL1LC.bin ver. 3.5.0 RC3 from Gitub
copied the file into the firmware directory
turned off the printer
turned on the printer by holding down both buttons on the 1LC board for 5sec, then released. (I also tried 1 second and also keeping them pressed all the time)

Result: no firmware loaded, 1LC card always unusable.

If you give me a detailed procedure, I can try again...

Gianluca · 29 Feb 2024, 17:38

Sorry for insisting, but I have a 1LC board that is stuck after trying to install a firmware provided by the Duet team.
Unfortunately factory reset using the two buttons doesn't work.
Should I throw the card in the trash? Is there anything else I can try? Is there a warranty for this type of problem?
Thank you

Phaedrux · 1 Mar 2024, 15:05

Alternating 3 and 5 flashes then the main board should put a message in the DWC console saying that a firmware file was requested but not found. Check the DWC console while the 1LC is trying to load firmware and giving those flashes to see what it's requesting as missing.

Gianluca · 1 Mar 2024, 15:18

@Phaedrux said in NEW PROBLEM WITH 1LC CARD:

Alternating 3 and 5 flashes then the main board should put a message in the DWC console saying that a firmware file was requested but not found. Check the DWC console while the 1LC is trying to load firmware and giving those flashes to see what it's requesting as missing.

Thank,you, this weekend I'll make further attempts and check the messages in the DWC console.
I will try again in both, SBC and stand alone mode.
In SBC mode, is it recommended to power up the toolboard after the system is already running? (in SBC mode, the boot is very long...)

Phaedrux · 1 Mar 2024, 15:46

I'd say it would be best to test with as minimal a setup as possible, so try standalone.

Gianluca · 10 Apr 2024, 08:38

SECOND 1LC CARD BRICKED AFTER UPDATE
This morning I updated the printer firmware to go from 3.5 RC3 to RC4 and also the second 1LC card is now unusable.
The update process stopped at 96% (see photos). After 30 min i have reboot the printer and now M122 B121 gives no response.
Can I get warranty assistance for at least (second) toolboard? I don't want to buy a third one!!
All attempts made to unlock the first toolboard did not work.
Thank you

Phaedrux · 12 Apr 2024, 05:50

Is this the same can cable as before?

dc42 · 12 Apr 2024, 06:16

@Gianluca what happens if you connect just one of the non-functioning tool boards to the CAN bus and hold both buttons down while powering up? What sequence of LED flashes do you see on the tool board?

Gianluca · 16 Apr 2024, 07:57

@Phaedrux said in NEW PROBLEM WITH 1LC CARD:

Is this the same can cable as before?

No, I have tried various canbus cables. I'm sure this isn't the problem.

Gianluca · 16 Apr 2024, 08:45

@dc42 said in NEW PROBLEM WITH 1LC CARD:

@Gianluca what happens if you connect just one of the non-functioning tool boards to the CAN bus and hold both buttons down while powering up? What sequence of LED flashes do you see on the tool board?

I answer the questions by attaching videos.

VIDEO_1: startup in stand alone mode.
The beep at the end indicates boot completion.
link text

VIDEO_2: startup in stand alone mode with reset 1LC.
The beep at the end indicates boot completion.
link text

VIDEO_3: startup in SBC mode.
The beep at the end indicates boot completion.
link text

VIDEO_4: startup in SBC mode with reset 1LC.
The beep at the end indicates boot completion.
link text

The file "Duet3Firmware_TOOL1LC.bin" is present in both the firemware and SYS folders, both in the SD card (st. alone mode) and in the raspberry (SBC mode).

Unfortunately the toolboard reset procedure did not work with any attempts.

Before the toolboards were blocked, they worked fine, except for the "Can't turn heater 1 on while in fault state" error, that perhaps arose with the RC3 version.

Is it not possible to send the cards to load the firmware in your laboratory?

Thanks for the help, I really need it to get a usable printer again.