Gcode files sorting, backup system
-
Agreed about a backup zip file download feature. For all the user modified config files.
The whole thing about backups is that they're a pain to do and they need to be as easy as possible if there's going to be a chance anyone will do them.
If I lost my config today… I'd cry.
-
Maybe an auto backup reminder, every 10 startups "do you want to backup sys" then it downloads a zip or whatever. Could be opted out of for those who don't like it.
-
I just do it back to front. That is to say, I keep and maintain the contents of the SD card on my PC, backed up as one would normally (to a NAS and cloud storage), and only copy files in one direction - from the PC to the sd card. I've had one too many sd card failures to trust them.
However, I don't use any bed compensation so I'd guess you have to use some other method to backup the height map?
-
Definitely backup to zip for system files
-
Just going to repeat myself.
The gcode files build up.
Deleting them one by one is not going to happen so they just build up and build up.
I've never connected to my Duet with anything other the web interface and taking the SD card out is unthinkable.
So am REALLY waiting for a way to do multiple deletes from the Web Interface. Or even a "Delete All"!
-
You can select more than one file, right click, delete on DWC 1.19
-
Meanwhile, you could always put the SD card in a PC and do a bulk delete.
-
I don't know when the update happened, but now you can delete all the files in one clic.
Select all, right clic, delete.I'm here to second requests to be able to arrange the gcode files list by date.
For now, I name all my g-codes starting with the date and then the title. That way, when sorting by name they are actually sorted by date. -
You can already arrange the gcode files by date if you upgrade DWC to 1.19.3. The same version also provides easy access to simulating a print to find out how long it will take. You can finds it in chrishamms's github repository, and also at https://github.com/dc42/RepRapFirmware/tree/dev/Release/Duet-WiFi/Edge.
My thanks to chrishamm for implementing these features.
-
Nice, thanks David.
-
…................................ The same version also provides easy access to simulating a print to find out how long it will take. ..............................
So does this work? I've upgraded to 1.19.3. If I right click on a file I see "Simulate File" and if I click on that I get the following:-
M37 P"5colourParts/5colorDiamond mount.gcode"
Simulation mode: off, move time: 0.0 sec, other time: 0.0 secI'm obviously missing a step somewhere.
-
Looks like you are running a version of RRF older than 1.19.
-
Looks like you are running a version of RRF older than 1.19.
Copy and paste from DWC
Firmware Version: 1.19 (2017-08-14)I can of course upgrade to a later version but I'm currently evaluating something so I don't want to make any changes until I've finished that evaluation.
-
My mistake, you need RRF 1.19.2 or 1.20beta1 to use that feature.
-
-
Can sorting by date also be implemented into PanelDue ? I normally upload my gcode straight from Cura (DuetRRF plugin) and if for some reason I need to stop the print, it becomes very difficult to find the right file on Paneldue to restart the print. So I have to either reupload (can take a while for big prints) or go to my computer and start from it.
Thanks
-
@randomfactoid said in Gcode files sorting, backup system:
Can sorting by date also be implemented into PanelDue ? I normally upload my gcode straight from Cura (DuetRRF plugin) and if for some reason I need to stop the print, it becomes very difficult to find the right file on Paneldue to restart the print. So I have to either reupload (can take a while for big prints) or go to my computer and start from it.
Thanks
I've added it to the wish list, but it's unlikely to happen soon.
-
@RandomFactoid maybe I can implement something that will help you:
In the DuetRRF plugin, before actually uploading the new file, I could check if a file with the same name already exists. If yes, you could select "Overwrite" or "Restart print with this file". This assumes you have Cura still running with you current model & build plate.Would this be of help to you?
