All All SD card data lost after web estop
-
@mikeabuilder what board?
When and where did you buy it? -
The board is a Duet2 - clone. Purchased recently from Amazon. I understand that clone is synonymous with "Good Luck". The SD card is also a low cost off-brand card. Another good luck product. Just thought this might be something of interest to Due team, despite the supplier.
-
@mikeabuilder said in All All SD card data lost after web estop:
The probe had deployed and before we crashed, I clicked the Emergency Stop button on the web interface.
I wonder if the deployed probe acted like a ignition coil and sent a spark all over the board when you hit the Estop?
-
@mikeabuilder said in All All SD card data lost after web estop:
Running Duet2, RRF 3.3, Web interface that came with 3.3.
After AC cycling to restart (I think this is the right recovery action),
Just FYI, after clicking on the Emergency Stop button the printer should re-boot on it's own and return you to the Duet Web Control interface.
You should not have to cycle power.
Frederick
-
@fcwilt - I was not aware the board should reboot on it's own. This was one of my first estop trials. The board seemed to be off and I AC cycled. Possibly I interrupted the boot sequence during a risky window of time. But I'm at a loss for a period of time during boot that an AC loss would result in the loss of the file system on an SD card. The power would need to go out just when the SDcard file allocation table was being written. Seems like a very small window of opportunity.
Reminds me of when I worked making PC and server motherboards. We had an AC cycle test with a remote AC cycler (arduino or equivalent). It would apply AC, wait a random (but recorded) amount of time, then turn AC on again and wait for the verified completion of a full boot cycle. That was a single test run. We'd let the thing run for thousands of boots looking for random timing issues.
-
I enable FTP on my Duets which allows me to easily access all the files on the SD card and keep backups.
Frederick
-
@fcwilt, we've been keeping our code in a github repo. But we got sloppy a week ago and will need to recreate a few recent changes. This event also taught me that we need to put more than just the gcode directories in our repo. All the fw files and web interface needs to be included too.
-
@mikeabuilder said in All All SD card data lost after web estop:
@fcwilt, we've been keeping our code in a github repo. But we got sloppy a week ago and will need to recreate a few recent changes. This event also taught me that we need to put more than just the gcode directories in our repo. All the fw files and web interface needs to be included too.
All of those files are accessible via FTP if desired.
Frederick
-
@fcwilt - Am I correct in understanding that none of the files on the SD card are ever changed by the fw (other than during an migration to a new version, and log files)? I've been operating on this idea and so would only need to make a backup copy of those files once, after a fw update.
All the other files (primarily in the sys, macros, gcode, and filaments directories) are files I'm responsible for and my process for those has been to edit on a networked computer and download to the Duet board. I try to be disciplined and "never" edit a file via the Duet web interface to avoid the possibility of losing changes (like I just did).
I guess I'm asking if it's important to periodically make backups of the files I'm not responsible for because they might have changed?
-
@mikeabuilder said in All All SD card data lost after web estop:
none of the files on the SD card are ever changed by the fw
there are some files which are changed:
config-override.g <- every time you send M500
heighmap.csv <- every time you probe the bed and save the height map
*.json within the /sys directory <- various DWC and plugin settings that can changeThe firmware binaries and other /sys macros are not changed by the printer. and in the case of the /www directory and firmware binaries, those are on github to download again.
