cant upload new changes to config.g all of a sudden
-
hello everyone. i've suddenly just experienced this issue where if I make a change to the config file and try to save changes, the config file just disappears and cant connect to the ethernet.
I have DUET3 on RRF 3.3. I don't think I entered a bad command or anything on the config file. all I was doing was changing the extruder speed and then when I tried to upload the config file just went blank and wont reconnect.
Ive gone through yat and manually edited the IP address again so I can reaccess DWC, and then I notice the blank config file.
Any help on this would be appreciated. Let me know if any other info is needed thanks.
-
heres the config file. its nothing out of the ordinary. Im working with a hangprinter btw.
; Enable network M552 P129.100.228.115 S1 M550 P"hangprinter" ; change the name from the IP address of 192.168.50.2 ;General Machine Settings/Conventions G21 ;work in mm G90 ;absolute coordinates M83 ;relative extruder moves G4 S2 ; wait for expansion boards to start ;Heaters and Temp Sensor ;bandheater M140 H-1 ; disable heated bed (overrides default heater mapping) M308 S1 P"temp1" Y"pt1000" A"Extruder Sensor"; configure sensor 1 as PT1000 on pin temp1 M950 H1 C"out1" Q10 T1 ; create nozzle heater output on out1 and map it to sensor 1, limit pwm frequency to 10Hz ;M307 H1 B0 R0.050 C1800 D36.57 S1.00 V12.1 ; FAILED AUTOTUNE RESULTS ; disable bang-bang mode for heater and set PWM limit M307 H1 B0 R0.319 C1028.9 D36.57 S1.00 V12.1 ; AUTOTUNE RESULTS FROM 2022-03-26 M143 H1 S300 ; set temperature limit for heater 0 to 240C ;second temp sensor ;M308 S2 P"temp0" Y"pt1000" A"Barrel Sensor"; configure sensor 2 as PT1000 on pin temp2 ;Fans ;Heatsink Fans 1 and 2 M950 F1 C"!out4+out4.tach" Q25000 ; Fan 1 uses out4, but we are using a PWM fan so the output needs to be inverted, and using out4.tach as a tacho input M106 P1 H-1 M950 F2 C"!out5+out5.tach" Q25000 ; Fan 2 uses out5, but we are using a PWM fan so the output needs to be inverted, and using out5.tach as a tacho input M106 P2 H-1 ;Kinematics and Drives ;Drives: x4 NEMA23's for Hangprinter Axis and x1 NEMA17 for extruder M18 ;disable default driver assignments; M569 P0 S0 ; drive 0 for extruder axis M569 P1 S0 ; drive 1 for D axis, goes forwards; need to create another "U" axis for D motor M569 P2 S1 ; drive 2 (Z motor output aka C) goes forwards M569 P3 S1 ; drive 3 (Y motor output aka B) goes forwards M569 P4 S1 ; drive 4 (X motor output aka A) goes forwards M584 X4 Y3 Z2 E0 U1 ;assign drives to axes and create U axis for D motor ;Step settings M350 X32 Y32 Z32 U32 E16 I1 ; configure microstepping with interpolation ;M92 X192 Y192 Z192 U192 ; set steps/mm for each spool M92 E5850 ; set steps/mm for extruder ;Speed and Accelerations M566 X250.00 Y250.00 Z250.00 U250.0 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z6000.00 U6000.00 E350.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z500.00 U250.00 E120.00 ; set accelerations (mm/s^2) ;Set Currents M906 X2500 Y2500 Z2500 E1500 U2500 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ;Kinematics M669 K6 ; Configures the Duet 3 to identify as Hangprinter Kinematics ;set anchor distances M669 K6 A0.0:-792.0:-232.0 B730.0:413.0:-232.0 C-711.0:413.0:-232.0 D0.0:0.0:2298.0 ; set Hangprinter kinematics parameters M669 P900.0 ; Hangprinter printable radius (unused for now) M669 S100 T0.5 ; Segments per second and min segment length M666 Q0.0033333 ; buildup compensation factor for ABCD M666 R75.0:75.0:75.0:75.0 ; ABCD radii M666 U2:2:2:4 ; Mechanical advantages on ABCD spools - 2 stands for doubled lines M666 O2:2:2:2 ; Number of lines per spool or "coil mode" (each line has it's own coil). 1 = coil style M666 L20:20:20:20 ; Motor gear teeth of ABCD axes M666 H254:254:254:254 ; Spool gear teeth of ABCD axes M666 J200:200:200:200 ; Full steps per ABCD motor revolution M208 S0 Z1200 ; maximum height 1750mm or some distance below D anchor M208 S1 Z-2 ; minimum height -5mm ; Uncomment M564 S0 if you don't want G0/G1 moves to be limited to a software defined volume ; M564 S0 ; Tool Definitions M563 P0 S"Pellet Extruder" D0 H1 F1:2 ;assign extruder(T1), drive(E1),Heater(h1) to tool1 G10 P0 R200 S220
-
Were you using the DWC editor to change the config.g?
Is there a config.bak file present?
Has this happened before, or only once? Does it happen every time?
Can you send M122 and post the results here?
Do you have a new SD card to move to?
When and where did you purchase your Duet 3?
-
@phaedrux
Were you using the DWC editor to change the config.g? Yes I was.Is there a config.bak file present? Yes there is.
Has this happened before, or only once? Does it happen every time?
Today is a very first time this has happened. What I did after this was go into YAT an manually change IP again so I can access DWC. It was there I noticed that the config.g file was 0KB so I took the contents of the backup config and pasted it into config.g. I uploaded the changes and at first I thought it still failed but it just took a really long time to reconnect to DWC. I was about to go into YAT again to manually change the IP address but it suddenly connected again. I powered off the duet3 and turned it on again, it took about 2-3 mins to connect. This has never happened before. Since we bought it, it has been working very good. I'm guessing if i do this again, it will take long to connect
Do you have a new SD card to move to? No, at the moment I don't have a new SD card to move to.
When and where did you purchase your Duet 3? I don't remember exact date but it was somewhere between DEC2021-JAN2022. We purchased it through DigitMakers(Canadian Reseller)
I currently have nothing connected to the DUET besides USB power and ethernet. Here is the M122 report:
m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (standalone mode) Board ID: 08DJM-9P63L-DJMSS-6JKDL-3SD6M-1SDZ9 Used output buffers: 13 of 40 (13 max) === RTOS === Static ram: 150904 Dynamic ram: 89656 of which 212 recycled Never used RAM 113420, free system stack 208 words Tasks: NETWORK(ready,17.6%,212) ETHERNET(notifyWait,0.0%,126) HEAT(delaying,0.0%,367) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,342) TMC(notifyWait,0.0%,105) MAIN(running,82.3%,1096) IDLE(ready,0.0%,29), total 100.0% Owned mutexes: === Platform === Last reset 00:05:33 ago, cause: software Last software reset at 2022-06-14 14:40, reason: User, GCodes spinning, available RAM 113420, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 643 MCU temperature: min 31.8, current 33.6, max 33.8 Supply voltage: min 0.1, current 0.2, max 0.2, under voltage events: 0, over voltage events: 0, power good: no 12V rail voltage: min 0.1, current 0.2, max 0.3, under voltage events: 0 Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0 Driver 1: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0 Driver 2: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0 Driver 3: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0 Driver 4: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0 Driver 5: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0 Date/time: 2022-06-14 14:46:34 Slowest loop: 7.48ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 2.3ms, 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 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 Code queue is empty. === CAN === Messages queued 2995, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 1669/0/0 Tx timeouts 0,0,1668,0,0,1325 last cancelled message type 4514 dest 127 === Network === Slowest loop: 12.68ms; fastest: 0.02ms Responder states: HTTP(2) HTTP(2) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions HTTP sessions: 1 of 8 - Ethernet - State: active Error counts: 0 0 0 0 0 Socket states: 5 3 2 2 2 0 0 0
-
Thanks for the details.
What browser were you using at the time?
We have had sporadic reports of the config file being lost of save like this. But haven't been able to narrow down a cause.
The only thing I can recommend at the moment is to replace the SD card with a good quality option, and to update your firmware/DWC to 3.4.1.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.1/Duet2and3Firmware-3.4.1.zip
Also a good time to make a full backup of the SD card just in case.
-
@phaedrux Ok thank you. We have been using chrome ever since we got the board.
I tried resetting the board (emergency stop in DWC) for the third time to recreate the problem and still got the same result (2-3 mins to reconnect)
Last time I madeany changes to the config while was a week ago and back then the upload happened within seconds.
I will try to upload to 3.4. Can you provide any link or procedure for backing up SD and using a new one?
Thanks
-
@ravs99 said in cant upload new changes to config.g all of a sudden:
Can you provide any link or procedure for backing up SD and using a new one?
It's as simple as taking the SD card out of the Duet and using a computer to copy the file contents over. You can omit the gcodes folder if you don't want to backup your print files as well.
-
This post is deleted! -
@phaedrux Ok thank you.
its been 20 mins later and now that issue has gone. I have backed up the sd card and will by a replacement when I get a chance. Gonna have to hold off on upgrading to 3.4 because of that MAC address change. Im connected to the school network so I will have to get that cleared with IT.
Just to clarify, when I do upgrade to RRF3.4, I can look up the MAC address on YAT correct?
-
If you want to keep the old MAC address you can make a note of it now and then manually set it in config.g
https://docs.duet3d.com/User_manual/Reference/Gcodes#m540-set-mac-address
-
@phaedrux oh right. i forgot about that. haha. Thank you for the help