Deleting config.g file
-
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?
-
@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.
-
@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
-
@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, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
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.
-
@fcwilt My wifi router for this section of the house is just on the other side of the wall. It has no issues connecting when it does but there are times it just wont connect.
-
@idaho-creator said in Deleting config.g file:
@fcwilt My wifi router for this section of the house is just on the other side of the wall. It has no issues connecting when it does but there are times it just wont connect.
Odd.
I have no idea why that might be.
Frederick
-
Contact your vendor and initiate a warranty exchange. Include a link to this thread as authorization. There may be a problem with the SD card slot.
-
@Phaedrux Ok I will contact filastruder. Thanks
-
@t3p3tony This was very helpfull. I accidentily pressed this macro and all files are gone. I will delete it. As a newbie you try everything....
-
3 years later, and I've recently encountered the same issue on my Duet3D 6HC mainboard. Config.g and config.bak are deleted, yet there is the a new config.g file dating back to when we first started the mainboard last year - has the generic 5-6 lines of code.
All other files for homing the axes and all gcode files of previous jobs are still on the card. We've even printed sth about 4h prior to the deletion of the config files.
We also had that 2_test_macro preinstalled at from when we bought the Duet3D. -
@lromberg said in Deleting config.g file:
3 years later, and I've recently encountered the same issue on my Duet3D 6HC mainboard. Config.g and config.bak are deleted, yet there is the a new config.g file dating back to when we first started the mainboard last year - has the generic 5-6 lines of code.
All other files for homing the axes and all gcode files of previous jobs are still on the card. We've even printed sth about 4h prior to the deletion of the config files.
We also had that 2_test_macro preinstalled at from when we bought the Duet3D.Exactly today, when starting my printer (6XD+3HC, 3.5.rc2)... it would not start, so I checked every bit of SDcard, including formating it. After some file checking, I realised that my config.g was missing.
Yesterday I tried to print some stuff. I printed a little, but being ugly I stopped the printing, and then reload the file, resliced. I do not remember if exactly then, or after I used EMERGENCY STOP in DWC for some reason, I kept receiving some connecting errors. They would seem to pass, if I restarted the printer and DWC, but while reloading that file, at some point I got connection errors again.
Sometime later I gave up and started to change the nozzle. At this was for some reason complicated, I turned off the printer and gone to other stuff.
Today, starting the printer, it would not connect, neither to Panel Due, or DWC. I found config.g missing, and also config.bak.
The rest of the files were there, in good order.Regarding the SDcard, formatted it, and it seemed to not have any errors. Also, yesterday, while the printer was still working, I did not messed up with the file system, at all.
The coincidence, two DUET3 filesystems loosing minds on 13-14.02.2024, seems to me, very doubtful.
I can understand a SDCard slot being faulty, but not simultaneously (basicly) on 2 (very similar) boards. And not resulting in the same file being f....d up. As I not familiar with RRF or DWC, I cant say in what condition exactly config.g would be erased, giben the fact that I was not working with the files, I mean editing or such.While the file sent to the printer is large, It was just a Cura gcode file, and cant be sure if that iteration had something to do with the event. I can anyway submit it if needed, I did not parsed it, for now.
I am almost sure that this is a bug. Costing more than a month of work, because of my lazyness in doing backup lately.
L.E. What is (somewhat) funny, is that from the first occurence of this ...event, passed almost exactly 3years, 18.02.2021, so... RRF virus? Maybe the date of that system was 14.02... Valentine's day Duet bug. VDDB.
L.L.E. I recovered some part of my config.g from a forum post, at least my frustration is halved now...
-
@lromberg @soare0 @jameswookyz
Please confirm the firmwareand hardware versions you are running
-
@T3P3Tony Is there a possibility for that macro, 2_test_macro, to run, other than manually? The file was there, I left it undeleted being ”from Duet” (good file, hehe...), but almost 99.999% I did not touched it when that happened, as I was simply trying to upload a new file for printing.
I will inspect the Cura file to search for a M30. but I would say this is a long shot.
Meantime, I deleted that macro file, just for revenge...Duet 3 MB6XD MB6XD 3.5.0-rc.2
Duet 3 Expansion EXP3HC EXP3HC 3.5.0-rc.2
Duet Web Control DWC 3.5.0-rc.2RepRapFirmware for Duet 3 MB6XD version 3.5.0-rc.2 (2023-12-14 10:33:00) running on Duet 3 MB6XD v1.01 or later (standalone mode)
Board ID: 0JD2M-999AL-D25S0-7JTDD-3S46L-1N1B1
