Deleting config.g file
-
So I thought the problem was fixed. Did several prints some lasting 20+ hrs. Powered off yesterday due the hotend thermistor reading -273 degrees. Turned it on today to heat up block to remove themistor tube that is stuck due to plastic stuck on hotend from failed bed adheasion several prints ago. When fired up panel due stuck in connecting status. tried to connect to WBC and nothing there. Removed sd card and plugged into printer and again the config.g file missing. Why is my duet 3 mini wifi doing this. The only other post of this happening was my prior post a month ago. Started new thread because forum software said I needed to cause other post was old.
-
-
I have no idea what you are asking.
-
My config.g file keeps getting deleted.
-
Why?
There's no reason that it will get deleted unless you delete it.
SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300
-
@alankilian yea I aint deleting it it is getting deleted on its own and why. Thats why I am here asking for help
-
Hi,
I wish I had a answer for you.
I've been using a Mini 5 for several months now without losing any files.
I started with firmware v3.1.1 - then 3.2.0 - and now 3.2.2.
Frederick
-
Yea I am now having wifi dropping again. each time I boot I run the risk of the system no reconnecting to wifi. I have tried new sd cards and I am just getting tired of it. I updated firmware the last time and it worked fine for just over a month. I wish I could get it figured out.
-
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.2 running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: UWSLD-U296U-D65J0-40KMS-1H03Z-7UQUB
Used output buffers: 3 of 40 (15 max)
=== RTOS ===
Static ram: 98732
Dynamic ram: 108252 of which 40 recycled
Never used RAM 38192, free system stack 200 words
Tasks: NETWORK(ready,190) HEAT(blocked,316) CanReceiv(blocked,947) CanSender(blocked,372) CanClock(blocked,363) TMC(blocked,104) MAIN(running,444) IDLE(ready,20) AIN(blocked,267)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:33 ago, cause: software
Last software reset at 2021-02-17 22:00, reason: User, GCodes spinning, available RAM 38192, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Supply voltage: min 0.0, current 24.5, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 85, reads 4809, writes 9, timeouts 0, DMA errors 0
Driver 1: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 85, reads 4809, writes 9, timeouts 0, DMA errors 0
Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 85, reads 4809, writes 9, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 79, reads 4809, writes 9, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 79, reads 4809, writes 9, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-02-17 22:00:54
Cache data hit count 70097951
Slowest loop: 5.00ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 1.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, 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 = 0 -1, chamberHeaters = -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.
=== Network ===
Slowest loop: 12.07ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.25
WiFi MAC address f4:cf:a2:6f:bd:71
WiFi Vcc 3.34, reset reason Power up
WiFi flash size 2097152, free heap 26176
WiFi IP address 192.168.1.55
WiFi signal strength -53dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages queued 303, send timeouts 301, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16
- WiFi -
-
I can't think of any good reason why config.g would be deleted except for perhaps a damaged SD card and/or file system. Try running a file system check when the SD card is plugged into a PC.
If you are not planning on changing it again soon, you can right-click config.g on Windows, go to Properties and check the "Read-only" attribute. That way RRF and/or DWC cannot delete or modify it.
Duet software engineer
-
chrishamm said in Deleting config.g file:
If you are not planning on changing it again soon, you can right-click config.g on Windows, go to Properties and check the "Read-only" attribute. That way RRF and/or DWC cannot delete or modify it.
@Phaedrux This is my new thing I've learnt for today. This might be good to detail somewhere. Especially for people who use a duet machine in a schools environment and want a way to stop people messing with the settings
-
I will lock the file. It is frustrating to have it happen the first several times it was bad cause I didnt have back up. now I have backup but I have made changes and have to figure out. I now have a rolling backup I manually do.
-
@idaho-creator when the file gets deleted, is the config.bak still there?
Duet Hardware Designer
www.duet3d.com -
@T3P3Tony no it doesnt. The picture in the second post is what is left in the folder. I am also having to fight the board connecting to the wifi. It occurs now every other reset making me have to reset by pressing the stop button on the duet mini.
-
The files being deleted is very odd.
We have a macro for renamin and deleting files at the end of the board testing. is there any chance that that file could be being run. whats in your /macros directory?
Duet Hardware Designer
www.duet3d.com -
@T3P3Tony if you are referencing 2_tests_completed macro yes I have that macro but I dont use macros. I will delete it.
-
If it happens again please let us know, and if it does I think we should replace the board in case it's an issue with the card slot.
When and where did you purchase it?
-
@idaho-creator yes feel free to delete that macro
It would also be good to see if the problem re-occurs with a different SD card.
Duet Hardware Designer
www.duet3d.com -
@Phaedrux I purchased through filastruder. I am still having wifi issues were it wont connect to wifi either about every other reset. sometimes it connects but sometimes I have to reset board 2 or 3 times.
-
@T3P3Tony I had used different sd card and problem still occurred but that macro was still in macro folder. It has been deleted.
-
@Phaedrux So its been a bit but It occured again jsut a moment ago. The system only deleted config.g in the system file. it left the config.g.bak so I was able to correct. This occured when I was saving the config.g after editing it with the web server editing feature and this is on a 3rd sd card that is new and high end fast read and write speed. It still has issue with locking on to wifi when reset with the router is 10 feet away in the next room.
-
Have you used a WiFi Analyzer to take a look at your WiFi environment.
WiFi can be problematic if it is not configured optimally and quite often it is not.
Frederick
Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1
-
@fcwilt Yea my network is channels is not near any other channel nearby. wifi signal strength is really good and the duet 3 connects but after a reset it might not connect until reset again. some times its several attempts sometimes its just once.
-
@idaho-creator said in Deleting config.g file:
@fcwilt Yea my network is channels is not near any other channel nearby. wifi signal strength is really good and the duet 3 connects but after a reset it might not connect until reset again. some times its several attempts sometimes its just once.
Hmm...
All I can say is I have 4 printers - one with a Duet 3 Mini 5, two with Duet 2 WiFi/Duex 5 and one with Duet 3 MB6HC.
I had to install a nearby WiFi Access Point to get reliable connections but once I did that I never have any problems with connection on power up or after a reset.
Frederick
Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1
-
It has now deleted everything in the config.g file but left the empty file. This is getting annoying I have not used it in a week because of this still occurring.
