Re: Deleting config.g file
I've read some of the previous posts on this, as I've recently had the same problem when upgrading my Z probe.
The first time config.g deleted completely and the second, this evening, left an empty config.g, in both cases config.bak was available and renamed to config.g to resolve the problem, but this is a pain and a waste of time.
From my experience and what I've read on the forum, this has been an ongoing issue for some time now.
Has anyone come up with an explanation and/or a solution
Hi, sorry to hear that. It is something we are currently investigating. Would you be able to tell us which Duet board and what firmware you have running?
o_lampe last edited by o_lampe
My gutt feeling tells me it's also time to ask for the purchase date or serial-number. Just because it's still unclear if it's a bad batch of card readers or firmware or something else (soldering process).
And for the reputation of Duet3d it would be a good idea to actively search for customers with related problems. (*)
*) edit/// @droftarts has beaten me with this, but a real polling thread would be better
Just my 2 Cent
@phaedrux https:Thanks for your reply, The following is the data you require:
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.2 (2021-01-05)
Duet WiFi Server Version: 1.25
I understand that these type of problems can be extremely difficult to resolve, or indeed, replicate,
so please don't take my post as a crib, I'd just like to know what is causing it and in particular, is it due to something I've done inadvertently? Overall the board produces great prints and is streets ahead of the original 8 bit Chinese board
Did it seem like you were having any connectivity issues at the time?
@phaedrux No problems with connectivity until the second incident that left the empty config.g file .
The IP address changed from 192.168.1.11 to 192.168.1.9.