Problems updating to RRF 3.3 + LC1 DWC reconnects
-
@Frederik Can you please share the output of M122 without parameters? It looks like the new RRF build resets shortly after it establishes a connection to DSF.
Duet software engineer
-
@chrishamm i will try
with all the reconnects its quite a challenging task 
i try it with a vnc connection, perhaps that is a bit more stable -
@Frederik Thanks, I suppose the best way to get an M122 dump would be to leave the Pi or DCS service disabled and to run M122 from a USB connection
-
-
i think i managed it , to get the mainboard + LC1 back in sync, but now i got this message when i try a m997
Error: M997: Failed to find IAP file /opt/dsf/sd/sys/Duet3_SBCiap32_MB6HC.bin
-
@Frederik That file is part of the reprapfirmware package but I guess your last update attempt prevented that package from being updated. See my previous post for further information on how to resolve this. Note that it may restore RRF 3.2 after the installation.
Duet software engineer
-
@chrishamm ok, the reconnects are gone at the moment, but i cannot update to 3.3
-
-
-- Logs begin at Tue 2021-01-26 12:16:45 UTC, end at Tue 2021-01-26 12:22:18 UTC. -- Jan 26 12:16:49 vcore systemd[1]: Starting Duet Control Server... Jan 26 12:16:53 vcore DuetControlServer[357]: Duet Control Server v3.2.0 Jan 26 12:16:53 vcore DuetControlServer[357]: Written by Christian Hammacher for Duet3D Jan 26 12:16:53 vcore DuetControlServer[357]: Licensed under the terms of the GNU Public License Version 3 Jan 26 12:16:55 vcore DuetControlServer[357]: [info] Settings loaded Jan 26 12:16:56 vcore DuetControlServer[357]: [info] Environment initialized Jan 26 12:16:56 vcore DuetControlServer[357]: [info] Connection to Duet established Jan 26 12:16:56 vcore DuetControlServer[357]: [info] IPC socket created at /var/run/dsf/dcs.sock Jan 26 12:16:56 vcore systemd[1]: Started Duet Control Server. Jan 26 12:16:56 vcore DuetControlServer[357]: [info] Starting macro file config.g on channel Trigger Jan 26 12:16:58 vcore DuetControlServer[357]: [warn] Lost connection to Duet (Board is not available (no header)) Jan 26 12:16:58 vcore DuetControlServer[357]: [info] Connection to Duet established Jan 26 12:16:58 vcore DuetControlServer[357]: [warn] Trigger: Aborting orphaned macro file config.g Jan 26 12:16:58 vcore DuetControlServer[357]: [info] Aborted macro file config.g Jan 26 12:16:58 vcore DuetControlServer[357]: [warn] Controller has been reset Jan 26 12:16:59 vcore DuetControlServer[357]: [info] Starting macro file config.g on channel Trigger Jan 26 12:16:59 vcore DuetControlServer[357]: [warn] Lost connection to Duet (Board is not available (no header)) Jan 26 12:16:59 vcore DuetControlServer[357]: [info] Connection to Duet established Jan 26 12:16:59 vcore DuetControlServer[357]: [warn] Trigger: Aborting orphaned macro file config.g Jan 26 12:16:59 vcore DuetControlServer[357]: [info] Aborted macro file config.g Jan 26 12:16:59 vcore DuetControlServer[357]: [warn] Controller has been reset Jan 26 12:16:59 vcore DuetControlServer[357]: [info] Starting macro file config.g on channel Trigger Jan 26 12:17:00 vcore DuetControlServer[357]: [warn] Lost connection to Duet (Board is not available (no header)) Jan 26 12:17:01 vcore DuetControlServer[357]: [info] Connection to Duet established Jan 26 12:17:01 vcore DuetControlServer[357]: [warn] Trigger: Aborting orphaned macro file config.g Jan 26 12:17:01 vcore DuetControlServer[357]: [info] Aborted macro file config.g Jan 26 12:17:01 vcore DuetControlServer[357]: [warn] Controller has been reset Jan 26 12:17:01 vcore DuetControlServer[357]: [warn] Failed to find query for object model response Jan 26 12:17:01 vcore DuetControlServer[357]: [info] Starting macro file config.g on channel Trigger Jan 26 12:17:01 vcore DuetControlServer[357]: [warn] Bad data CRC32 (expected 0x35fc057a, got 0x9ac38e3d) Jan 26 12:17:02 vcore DuetControlServer[357]: [warn] Note: RepRapFirmware didn't receive valid data either (code 0x0004005f) Jan 26 12:17:02 vcore DuetControlServer[357]: [warn] Bad data CRC32 (expected 0x35fc057a, got 0x01acbff6) Jan 26 12:17:02 vcore DuetControlServer[357]: [warn] Note: RepRapFirmware didn't receive valid data either (code 0x0004005f) Jan 26 12:17:02 vcore DuetControlServer[357]: [warn] Bad data CRC32 (expected 0x35fc057a, got 0x01acbff6) Jan 26 12:17:02 vcore DuetControlServer[357]: [warn] Note: RepRapFirmware didn't receive valid data either (code 0x0004005f) Jan 26 12:17:02 vcore DuetControlServer[357]: [warn] Restarting transfer because the number of maximum retries has been exceeded Jan 26 12:17:02 vcore DuetControlServer[357]: [warn] Trigger: Aborting orphaned macro file config.g Jan 26 12:17:02 vcore DuetControlServer[357]: [info] Aborted macro file config.g Jan 26 12:17:02 vcore DuetControlServer[357]: [warn] Controller has been reset Jan 26 12:17:02 vcore DuetControlServer[357]: [info] Starting macro file config.g on channel Trigger Jan 26 12:17:02 vcore DuetControlServer[357]: [warn] Lost connection to Duet (Board is not available (no header)) Jan 26 12:17:02 vcore DuetControlServer[357]: [info] Connection to Duet established Jan 26 12:17:02 vcore DuetControlServer[357]: [warn] Trigger: Aborting orphaned macro file config.g Jan 26 12:17:02 vcore DuetControlServer[357]: [info] Aborted macro file config.g Jan 26 12:17:02 vcore DuetControlServer[357]: [warn] Controller has been reset Jan 26 12:17:02 vcore DuetControlServer[357]: [info] Starting macro file config.g on channel Trigger Jan 26 12:17:03 vcore DuetControlServer[357]: [warn] Lost connection to Duet (Board is not available (no header)) Jan 26 12:17:03 vcore DuetControlServer[357]: [info] Connection to Duet established lines 1-49 -
Good morning,
yesterday evening, I flashed a new DuetPI (Desktop) Image with RRF 3.2 Stable. After checking the correct Function I downloaded the 3.3Beta Files again and try to Update the Firmware on Mainboard & LC1.
At the beginning , the same error occured as befor and the machine state switched twice a second from idle to off and the controller is constantly resetting + unable to . I let the Printer run over night and in the morning the update was finished. but now another Error Occured:
Failed to enable enstops
-
Today i flashed a new Duet Pi Image with RRF 3.2 Stable and flashed a new duet 6 mainboard firmaware via USB and Bossa. Everything fine without errors, but when i try to copy my last config.g and sys files , the controller starts the reconnects again, exactly like before in RRF3.3beta.
when i try to home the machine , i get the error : failed to enable endstops
What can i do to restore the function of my printer ?
m122 confirmed that RRF3.2 stable is on mainboard and toolboard.
Toolboard bootlader 2.2Warning: Controller has been reset 27.1.2021, 21:12:02 Connection to Duet established 27.1.2021, 21:12:02 Warning: Lost connection to Duet (Board is not available (no header)) 27.1.2021, 21:12:00 Warning: Controller has been reset 27.1.2021, 21:11:59 Warning: Controller has been reset 27.1.2021, 21:11:59 Connection to Duet established 27.1.2021, 21:11:58 Warning: Lost connection to Duet (Board is not available (no header)) 27.1.2021, 21:11:57 m122 b121 Diagnostics for board 121: Duet TOOL1LC firmware version 3.2 (2021-01-05) Bootloader ID: SAMC21 bootloader version 2.2 (2021-01-16b1) Never used RAM 4412, free system stack 96 words HEAT 90 CanAsync 89 CanRecv 83 TMC 54 MAIN 268 AIN 64 Last reset 03:53:10 ago, cause: power up Last software reset time unknown, reason: OutOfMemory, available RAM 15632, slot 2 Software reset code 0x01c0 ICSR 0x00000000 SP 0x20003578 Task MAIN Freestk 747 ok Stack: 20000d10 00011ceb 20000d10 0001df61 00000000 00004008 20000d10 0001ded5 20000d0c 00004000 a5a5a5a5 a5a5a5a5 00000000 0001dd9d 00004000 00018b21 a5a5a5a5 00018b3d a5a5a5a5 00011b39 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 Driver 0: position 0, 859.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 252, reads 19330, writes 833, timeouts 0, DMA errors 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0 No step interrupt scheduled VIN: 24.1V MCU temperature: min 38.8C, current 41.5C, max 41.7C Ticks since heat task active 231, ADC conversions started 13990474, completed 13990473, timed out 0 Last sensors broadcast 0x00000000 found 0 235 ticks ago, loop time 0 CAN messages queued 1687, send timeouts 0, received 3760, lost 0, free buffers 36 Connection to Duet established 27.1.2021, 21:12:48 Warning: Lost connection to Duet (Board is not available (no header)) 27.1.2021, 21:12:46 Warning: Controller has been reset 27.1.2021, 21:12:46 Connection to Duet established 27.1.2021, 21:12:46 Warning: Lost connection to Duet (Board is not available (no data response)) 27.1.2021, 21:12:45 Warning: Controller has been reset 27.1.2021, 21:12:49 Warning: Lost connection to Duet (Board is not available (no header)) 27.1.2021, 21:12:48 Warning: Controller has been reset 27.1.2021, 21:12:48 Connection to Duet established 27.1.2021, 21:12:48 Warning: Lost connection to Duet (Board is not available (no header)) 27.1.2021, 21:12:46 Warning: Controller has been reset 27.1.2021, 21:12:46 Connection to Duet established 27.1.2021, 21:12:46 Warning: Lost connection to Duet (Board is not available (no data response)) 27.1.2021, 21:12:45 Warning: Controller has been reset 27.1.2021, 21:12:45 Connection to Duet established 27.1.2021, 21:12:45 Warning: Lost connection to Duet (Board is not available (no header)) 27.1.2021, 21:12:43 m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-956BA-NA3TN-6J9DL-3S46S-99AUT Used output buffers: 1 of 40 (2 max) === RTOS === Static ram: 149788 Dynamic ram: 61196 of which 0 recycled Never used RAM 147848, free system stack 214 words Tasks: Linux(ready,407) HEAT(blocked,365) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,360) TMC(blocked,59) MAIN(running,1283) IDLE(ready,19) Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:00:00 ago, cause: software Last software reset at 2021-01-27 21:12, reason: TerminateCalled, GCodes spinning, available RAM 146820, slot 2 Software reset code 0x4183 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x2041f560 Task MAIN Freestk 1254 ok Stack: 0000002b 00471bc3 00000000 2042f108 2041f8c0 00471f2b 00000000 004718b1 2041f5b0 00456d61 2041f600 00000000 2042f108 00000000 2041f7fc 00000001 00000000 0047581b 2041f600 00000000 2042f108 0047581b 00000000 2042f108 00456d5f 2041f7fc 2041f7fc Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 MCU temperature: min 42.8, current 42.8, max 42.8 Supply voltage: min 24.1, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0 Driver 0: position 0, standstill, reads 994, writes 11 timeouts 0, SG min/max 0/0 Driver 1: position 0, standstill, reads 994, writes 11 timeouts 0, SG min/max 0/0 Driver 2: position 0, standstill, reads 995, writes 11 timeouts 0, SG min/max 0/0 Driver 3: position 0, standstill, reads 995, writes 11 timeouts 0, SG min/max 0/0 Driver 4: position 0, standstill, reads 995, writes 11 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 995, writes 11 timeouts 0, SG min/max 0/0 Date/time: 1970-01-01 00:00:00 Slowest loop: 0.15ms; fastest: 0.00ms === 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 === DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === 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 0, running macro 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 0, send timeouts 0, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48 === SBC interface === State: 1, failed transfers: 0 Last transfer: 1ms ago RX/TX seq numbers: 22007/5 SPI underruns 0, overruns 0 Number of disconnects: 0, IAP RAM available 0x2c8a8 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.2.0 Trigger: Buffered code: M550 P"vcore" Buffered code: M905 P"2021-01-27" S"21:12:43" Buffered code: M291 P"Please go to this page for further instructions on how to set it up." R"Welcome to your new Duet 3!" S1 T0 Buffered code: G90 ; send absolute coordinates... Buffered code: M83 ;Set extruder to relative mode ==> 364 bytes Executing macro config.g, started by system Number of flush requests: 1 > Next stack level Code buffer space: 3732 Configured SPI speed: 8000000 Hz Full transfers per second: 42.63 Maximum length of RX/TX data transfers: 3320/548 -
Post your current config.g and the results of M98 P"config.g"
-
; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"vcore" ; set printer name M669 K1 ; select CoreXY mode ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.3 S1 M569 P0.4 S1 M569 P0.5 S1 M569 P121.0 S0 ; physical drive 121.0 goes forwards M584 X0.0 Y0.1 Z0.2:0.3:0.4 E121.0:0.5 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X159.50 Y159.50 Z1600.00 E859.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X1500 Y1500 Z1200 E800 I100 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X380 Y380 Z380 S0 ; set axis maxima ; Endstops M574 X1 S1 P"121.io2.in" ; configure active-high endstop for low end on X via pin 121.io2.in M574 Y1 S1 P"io0.in" ; configure active-high endstop for low end on Y via pin io0.in M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; Position of Leadscrews M671 X-30:450:235 Y200:200:450 S6 ;Position of Leadscrews ; Bed Compensation Taper M376 H0 ; BMG Pressure Advance M572 D0:1 S0.000 ;---------------------------------------------------------------------- ; FW Retraction Mosquito (S)-Retraction Dist. (F) Speed , (Z) ZHopHeight M207 S0.5 F4000 Z0.0 ;---------------------------------------------------------------------- ; Volumetric Extrusion Filament Diameter (D) M200 D1.75:1.75 ;---------------------------------------------------------------------- ; Extrusion Override Factor to 83 % M221 S100 D0:1 ;---------------------------------------------------------------------- ;--Ringing Frequenz ;M593 F40.5 ; Ringing Frequency DirectDrive ;---------------------------------------------------------------------- ;--Print Monitor - Filament (N) and Nozzle diameter (D) M404 N1.75 D0.4 ;---------------------------------------------------------------------- ;--Duet Laser Filament Monitor ;M591 D0 P5 C"121.io1.in" R30:130 E3.0 S0 ; Extruder0 Tolerance 30 to 130%, 3mm comparison length, diabled ; Z-Probe M950 S0 C"121.io0.out" ; create servo pin 0 for BLTouch M558 P9 C"^121.io0.in" H5 F120 T9000 ; set Z probe type to bltouch and the dive height + speeds M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved G31 P500 X-28 Y-22 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X15:380 Y15:380 S40 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out7" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S160 ; set temperature limit for heater 0 to 160C M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out8" T1 ; create chamber heater output on out1 and map it to sensor 1 M307 H1 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit M141 H1 ; map chamber to heater 1 M143 H1 S120 ; set temperature limit for heater 1 to 120C M308 S2 P"121.temp0" Y"thermistor" T500000 B4723 C1.19622e-7 ; configure sensor 2 as thermistor on pin 121.temp0 M950 H2 C"121.out0" T2 ; create nozzle heater output on 121.out0 and map it to sensor 2 M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H2 S525 ; set temperature limit for heater 2 to 525C ; Fans M950 F0 C"121.out2" Q500 ; create fan 0 on pin 121.out2 and set its frequency M106 P0 C"Mosquito" S0.6 H1:2 T45 ; set fan 0 name and value. Thermostatic control is turned on M950 F1 C"121.out1" Q500 ; create fan 1 on pin 121.out1 and set its frequency M106 P1 C"Bauteil" S0 H-1 ; set fan 1 name and value. Thermostatic control is turned off ;Air Pump Control on SSR_3 M950 F2 C"out9" Q255 ; create fan 1 on pin 121.out1 and set its frequency M106 P2 C"AirCompressor" S0 H-1 ; set fan 1 name and value. Thermostatic control is turned off ; ;Led Beleuchtung ; Zone 1 ;---------------------------------------------------------------------- M950 F3 C"out2" Q500 ; create a output for led zone1 on out3 M106 P3 S1 ; set output default to on ; ; Zone 2 ;---------------------------------------------------------------------- M950 F4 C"out3" Q500 ; create a fan output for led zone2 on out4 M106 P4 S1 ; set output default to on ;---------------------------------------------------------------------- ; ; Toolboard Buttons ;---------------------------------------------------------------------- ;button0 LC1.121 M950 J4 C"121.button0" ; Input 4 uses io4 pin, inverted M581 P4 S1 T2 R0 ; configure button for LED ON ;---------------------------------------------------------------------- ; button1 LC1.121 M950 J5 C"121.button1" ; Input 5 uses io5 pin, inverted M581 P5 S1 T3 R0 ; configure push button for LED OFF ; ; Tools M563 P0 S"Mosquito" D0 F0:1 ; define tool 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 ; Custom settings are not defined ; Miscellaneous M501 ; load saved parameters from non-volatile memory M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss T0 ; select first tool ´ M98 config.g: 27.1.2021, 21:44:19 M98 P"0:/macros/config check" Warning: Board 121 does not have input handle 2400 Warning: Board 121 does not have input handle 2500 Tool 0 offsets: X0.00 Y0.00 Z0.00 Warning: Macro file config-override.g not found 27.1.2021, 21:44:18 Warning: Board 121 does not have input handle 3000 27.1.2021, 21:44:18 Warning: Board 121 does not have input handle 1000 27.1.2021, 21:51:04 Warning: Controller has been reset 27.1.2021, 21:51:04 Connection to Duet established 27.1.2021, 21:50:48 Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin) 27.1.2021, 21:49:59 Warning: M307: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C 27.1.2021, 21:49:59 Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C 27.1.2021, 21:49:58 Tool 0 offsets: X0.00 Y0.00 Z0.00 27.1.2021, 21:49:57 Connection established 27.1.2021, 21:49:50 Connection interrupted, attempting to reconnect... DCS has been stopped 27.1.2021, 21:49:48 Upload of config.g successful after 0s 27.1.2021, 21:44:56 M98 P"0:/macros/config check" Tool 0 offsets: X0.00 Y0.00 Z0.00 Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C Warning: M307: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C 27.1.2021, 21:44:32 m500
