NEW PROBLEM WITH 1LC CARD
-
Excellent suggestion the LEDs.
I actually have 126 RGB LEDs on the top of the chassis, and 3 RGBW LEDs on the stealtburner, but unfortunately they are both connected to the 6HC motherboard (LED port + io.8) not in 1LC.
The 126 LEDs have always been there, while the LEDs on the extruder have only recently been using the following management macro: https://github.com/Exerqtor/Voron/tree/main/Firmware/rrf-macros/sb_leds.
This evening I will try to remove the configuration of all the LEDs and start the print again.
I attach config.g and daemon.gconfig.g
; Voron 2.4 355x355mm Duet3 6MBHC - Toolboard 1LC - SBC with RASPBERRY PI-4 4GB and SD 64GB ; Data di aggiornamento: 10/02/2024 ; ; ---------- GENERAL PREFERENCES --------- G90 ; absolute coordinates... M83 ; relative extruder moves M669 K1 ; Select CoreXY mode M564 S1 H1 ; Forbid axis movements when not homed M575 P1 S1 B57600 ; enable support for Paneldue display M290 R0 S0 ; reset babystepping ; ; ---------- DRIVES MAPPINGS ---------- ; ; Rear ; | Z1 | Z2 | ; -----+----- ; | Z0 | Z3 | ; -----+----- ; Front ; M584 X4 Y5 Z0:1:2:3 E121.0 ; set drive mapping M569 P0 S1 ; Z0 motor FL goes forwards M569 P1 S0 ; Z1 motor RL goes backwards M569 P2 S1 ; Z2 motor RR goes forwards M569 P3 S0 ; Z3 motor FR goes backwards M569 P4 S1 ; A motor goes forwards M569 P5 S1 ; B motor goes forwards M569 P121.0 S0 ; E1 motor Extruder goes backwards (scheda 1LC porta 121) M671 X-67.5:-67.85:422.5:422.5 Y-10:443.8:443.8:-10 S15 ; Define Z belts locations (Z0=Front_Left Z1, Z2, Z3...ecc) S15=mm di correzione massima ; ; ---------- DRIVES GENERAL PARAMETERS ---------- M350 X32 Y32 Z32 E16 I1 ; configure microstepping with interpolation M92 X158.5 Y158.5 Z800 E745 ; set steps per mm (417 afterburner, 745 stealthburner) M84 S20 ; riduzione potenza motori dopo 20sec ; ; ---------- DRIVES SPEED PARAMETERS ---------- M566 X800 Y800 Z100 E1000 ; JERK (mm/min) M203 X24000 Y24000 Z6000 E1000 ; MAX SPEED (400mm/min) M201 X7000 Y7000 Z500 E3000 ; ACCELERAZIONE (mm/s^2) M906 X2000 Y2000 Z2000 E850 I30 ; set motor currents (mA) and motor idle factor 30% ; ; ---------- AXIS LIMITS ---------- M208 X0 Y0 Z-0.15 S1 ; set axis minima (S1) M208 X350 Y350 Z320 S0 ; set axis maxima (S0) Portato ad H=320mm per presenza barra LED ; ; ---------- ENDSTOP --------- M574 Y2 S1 P"!io1.in" ; Configure enstop Y(2) posizione alta dello switch e pin !io1.in invertito M574 X2 S1 P"!io2.in" ; Configure enstop x(2) posizione alta dello switch e pin !io2.in invertito ; ; ---------- SENSORE MAGNETICO FILAMENTO --------- M591 D0 P3 C"121.io0.in" R10:190 L24.5 E10.0 S1 ; Rotating magnet sensor for extruder drive 0 is connected to 121.io0.in on Toolboard 1LC, ; ; ---------- Z-PROBE ---------- M558 P8 C"!121.io1.in" H10 F600 T5000 ; set Z probe type inductive (P8), altezza tastatura (H10), velocità tastatura mm/min (F600), velocità di spostamento mm/min (T6000) su scheda espansione 1LC porta 121 G31 P500 X0 Y24 Z1.52 ; set Z probe trigger value, PIU' ALTO E' Z PIU' SI AVVICINA AL LETTO M557 X40:315 Y40:315 S55 ; define mesh grid (GRIGLIA maglia 6 x 6 con 55mm di spazio) EVITA I MAGNETI (ALZATO DI 0.03mm IL 5-9-23) ; ; ----------- HO - HEATERS BED ---------- M308 S0 P"temp0" Y"thermistor" T100000 B4138 A"LETTO" ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out1" T0 ; create bed heater output on out1 and map it to sensor 0 M307 H0 R0.856 K0.199:0.000 D4.53 E1.35 S1.00 B0 ; DOPO AUTOTARATURA LETTO CON (M303 H0 P1 S100) il 03/12/2023 (R=Velocità di riscaldamento °C/sec) M140 H0 ; map heated bed to heater 0 ; ; ----------- H1 - HEATERS NOZZLE ---------- M308 S1 P"121.temp0" Y"thermistor" T100000 B4138 A"ESTRUSORE" ; Configure sensor 1 as thermistor on pin temp0/121 M950 H1 C"121.out0" T1 ; Create nozzle heater output on out0 su scheda espansione 1LC porta 121 and map it to sensor 1 M307 H1 S0.8 B0 M143 H1 S275 ; set temperature limit for heater 1 to 275C ; ; ---------- TOOLS ---------- M563 P0 S"TOOLS-0" D0.5 H1 F0 ; DEFINE TOOL 0 => P0=Tool 0, S"..."=Tool name, D0.5=drive 0.5, H1=heather 1, F0=fan 0. G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; ; ---------- FAN 0 VENTOLA RAFFR. STAMPA PWM (out4) 24v ---------- M950 F0 C"121.out2" Q500 ; Fan 0 su 121.out2, use PWM, using 121.out2 M106 P0 C"VENTOLA FILO" S0.0 H-1 ; set FAN_0 name and value. ; ; ---------- FAN 1 VENTOLA HOTEND (out8) 24v ---------- M950 F1 C"121.out1" Q500 ; Fan 0 su 121.out2, use PWM, using 121.out2 M106 P1 C"HOTEND" H1 L0.35 X0.6 B0.3 T60:250 ; PARAMETRICA Termostatica ( da L=35% a X=60% con temp. da 60°C a 250°C ) ; ; ---------- FAN 2 VENTOLA MCU PWM (out5) 24v --------- M308 S2 Y"mcu-temp" A"MCU 6HC" ; configure sensor 2 (S2) as thermistor for MCU M950 F2 C"!out5+out5.tach" ; Fan 2 su out5, use PWM (needs ! inverted), using out5.tach M106 P2 C"VENTOLA MCU" L0.1 X0.8 B0.1 T26:35 H3 ; set FAN_2 value T26:32°C velocità ventola L-10% X-80% ; ; ---------- FAN 3 VENTOLA PWM RASPBERRY (out4) 12v --------- M308 S3 P"temp2" Y"thermistor" T100000 B4138 A"RASPBERRY" ; Configura il sensore 3 (S3) come riscaldatore sul pin temp2 con nome RASPBERRY M950 F3 C"!out4+out4.tach" ; Fan 3 su out6, use PWM (needs ! inverted), using out4.tach M106 P3 C"VENTOLA RASPBERRY" L0.1 X1.0 B0.5 T20:48 H4 ; set FAN_3 value T20:42°C velocità ventola L-10% X-100% B=blip time ; ; ---------- FAN 4 VENTOLA 1LC (out7) 24v ---------- M308 S4 Y"mcu-temp" P"121.dummy" A"MCU 1LC" ; configure sensor 4 (S4) Temp MCU 1LC M950 F4 C"out7" Q1000 ; create FAN_4 on pin ou7 Toolboard and set its frequency at 1000hz M106 P4 C"FAN 1LC MCU" H1 L0.2 X0.7 B0.3 T38:55 ; H1=Termostatic L=Min.Spd. X=Max.Spd. B=Blips Time T=Temp Range 30-50°C ; M106 P4 S0.65 ; PER ACCENDERE LA VENTOLA ; M106 P4 S0.0 ; PER SPEGNERE LA VENTOLA ; ; ---------- FAN 5 VENTOLA CHASSIS (out8) 24v ---------- M950 F5 C"out8" Q1500 ; create FAN_5 on pin ou8 VENTOLE LATERALI DX ASPIRANTI M106 P5 S0.00 C"CHASSIS_SX" B1 ; ACCENDE LA VENTOLA AL 30% ; ; ---------- FAN 6 VENTOLA CHASSIS (out9) 24v ---------- M950 F6 C"out9" Q1500 ; create FAN_6 on pin ou9 VENTOLE LATERALI SX SOFFIANTI M106 P6 S0.00 C"CHASSIS_DX" B1 ; ACCENDE LA VENTOLA AL 30% ; ; ---------- TEMPERATURA E0 NEMA 14 SU TOOLBOARD 1LC ---------- M308 S5 P"121.temp1" Y"thermistor" T100000 B4138 A"NEMA14" ; Configure sensor 5 (S5) as thermistor on pin temp1/121 ; ; ---------- PORT 1 RELE' ACCENSIONE (io4.out) IO PORT PWM ---------- M950 P1 C"io4.out" Q500 ; allocate GPIO PORT.1 to io4.out at 500Hz ; ; ---------- ACCELEROMETRO ---------- M955 P121.0 I10 ; ACCELEROMETRO SU SCHEDA 1LC (I10 = orientamento scheda) M593 P"EI3" F40 ; INPUT SHAPING: Configura i parametri di riduzione risonanza ; ; ---------- TASTI FISICI SU 1LC ---------- M950 J5 C"121.button0" ; Crea pin 5 su porta 121.button0 della scheda 1LC M581 P5 T2 S1 R0 ; P5=pin 5 creato con M950 (J5), T2=Trigger logico a cui associare gli ingressi, S1=funziona da inattivo ad attivo, R0=attivo in ogni momento ; Qualsiasi numero di trigger # maggiore di 1 provoca l'esecuzione del file della macro sys/trigger2.g (T2) M950 J6 C"121.button1" ; Crea trigger n°6 su porta "121.button0" M581 P6 T3 S1 R0 ; Crea pin 6 su porta 121.button1 della scheda 1LC ; ; ---------- NEOLED "1" RGBW - STEALTHBURNER (PORTA IO8 OUT SU 6HC) ---------- M950 E1 C"io8.out" T2 ; Crea PIN "io8.out" striscia LED E1 T1=RGB T2=RGBW M98 P"/sys/lib/init.g" ; Avvia il controllo automatico dei LED sullo Stealtburner (in /sys/lib...) set global.sb_leds = "ready" ; ; ---------- NEOLED "0" 4 BARRE LED RGB SUPERIORI (PORTA DEDICATA DOTSTAR SU 6HC) ---------- M950 E0 C"led" T1 U160 Q3000000 ; Crea PIN "led" striscia LED E0 T1=RGB U160=160LED disponibili M98 P"0:/macros/5-NEOLED ITALIA.g" ; Tutti i led superiori accesi al 10% (41+41+32+41=155 LED RGB) ; ; ---------- IMPOSTA L'AUTOSALVATAGGIO IN CASO DI MANCATA ALIMENTAZIONE ---------- M911 S29.2 R29.4 P"M913 X0 Y0 G91 M83 G1 Z3 E-2 F500" ; Autosalvataggio stampa per mancanza di corrente, sospende a 29.2v e riparte a 29.4v ; ; ---------- MISCELLANEUS ---------- M912 P0 S-1 ; parametro per tarare la temperatura della MCU (-1°C) M300 S2500 P3000 ; Emette suono a S=2500Hz per P=3 secondi T0 ; select first tool ACTIVE ;daemon.g
;Check sb_leds status var SB_LEDS = true ; Turn on(true) / off(false) the Stealthburner led "system" if var.SB_LEDS if fileexists("/sys/lib/led/sb_leds-state.g") M98 P"/sys/lib/led/sb_leds-state.g" ; Check if global.sb_leds has changed since last run/loop -
@Gianluca if the LEDs are on the 6HC, they won’t be causing the out of memory problem on the 1LC.
I’ll ask @dc42 to look at the M122 report.
Ian
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
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 -
@Gianluca show us some photos of the toolboard, and the wiring connection for CAN (both ends).
-
@Gianluca can you try disabling the filament monitor?
-
@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.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@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 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. -
@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 fileIt 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
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
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... -
@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.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@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...
-
undefined Phaedrux marked this topic as a question
-
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 -
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.
-
@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...) -
I'd say it would be best to test with as minimal a setup as possible, so try standalone.
-
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
-
Is this the same can cable as before?
-
@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?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com
