Sd card disk Image



  • Hi, I have a duetWifi with firmware 1.21, I just broke my SD card and I'm trying to re-install. Upon succeeding I just want to comment that it's complicated for no reason. Could you please provide a disk-image version for each release version of the firmware.

    Etcher is a free multi-platform tool that can be use for the task...



  • Basically the SD Card contains the following:

    • "gcodes" - folder that contains all the gcode files that you upload as jobs. By default this folder is empty.
    • "macros" - folder that will contain macros you define yourself. While a few macros come as stock, they are dummy and factory test macros used to verify that the board is working correctly. If you would like these, I can supply them to you, but frankly it is not useful for actual use.
    • "sys" - the default contents of this folder is once again tests values, which produce errors when running. You get your own files from the configuration tool, and it is a very good idea to regularly backup these files (in case of corrupted SD card). The contents of your config.g file can be adapted quite a lot and regularly as you need (solving issues and making sure it works better than before and remains updated with new firmware).
    • "www" - folder containing the relevant version of Duet Web Control. The correct version can be downloaded from the firmware releases page: https://github.com/dc42/RepRapFirmware/releases

    As you can see, it is not very useful to supply the sd card contents, and with the details above, it is simple to re-create the folder structure, and with the sys folder backups, you should easily be able to get back on your feet.



  • Every time I make a change to a config file I download all the files in /sys as a zip to my PC and archive it away. I also give each version a number - I'm currently on V17.
    Spot the ex-developer/DBA ☺



  • @jacotheron
    Yes easy if you done it once, but easy to forget something for example in your last link on the last candidate version 2.02 RC2 where is the iap4e.bin file oups? Ok maybe in the last real release 2.0.1 not there ok it's 2.0 release. Having a complete package and version stamped packet is less prone to error .

    The process is not complex but not user friendly, took me 30 minutes instead of 5.



  • @tekkydave
    Thanks Yes I've many backup of my config file, just arguing that a 3 steps process Download image, burn image, replace config files is simpler that a 10 steps one...





  • Actually, I agree that a complete image for each MAJOR release would be a wonderful thing for the community. I'm never 101% confident that I have the right things on an SD, because tidbits of information, like which iap... or the exact name of the firmware file, or similar are spread all over the place. The forum, the wiki, release notes, maybe other places.

    An image would solve all of that.

    Along with that, I'd like to see a /sys and /usr (user) directory, separate. Names should make it self-evident what goes where.

    This would require a very small change to RepRap firmware, and a somewhat larger change to DWC. In fact, it would be nice if DWC had a "file browser", instead of hard-coded assumptions about what uploads where, what can/can't be edited, etc. This might make many things simpler in the long run.

    Installing a new release could become:

    1. Download/burn new physical SD with release that you want.

    2. Click the button in DWC that says "Copy /usr to new SD"

    3. Move the SD from computer to printer, boot printer, and look! The DWC copy operation put a "one time".g file somewhere on the SD that contains the "load firmware" M-Codes. From a user perspective that boot takes a little longer... and "just works".

    Very, very simple for a printer user/operator. A few changes to RepRap and DWC that only have to be done once, and a small effort to produce the image each time (that could easily be scripted).



  • @danal I kinda wish that the DWC had an auto updater function like octoprint. It should notify the user that a new version is available, and auto download the needed files when the user says update. It could give a warning about what is changing and then proceed to update. It could even create a backup first and have a function to revert.

    Or perhaps have a single zip file package that contains all the latest versions and installs whatever is out of date.

    The image is good idea, but wouldn't it depend on what version of the firmware is currently installed on the board?



  • @phaedrux said in Sd card disk Image:

    The image is good idea, but wouldn't it depend on what version of the firmware is currently installed on the board?

    Given the sequence: "build entirely new", "overlay user files like config.g, override, macros", "boot and update flash-on-card", then no, it really should not depend on what was there before... any /sys file incompatibilities would be auto-resolved by the fact it is a "complete, new, image".

    With one caveat: Any necessary release-to-release config incompatibilities.

    Release to release config changes will always be a thing... not really any (reasonable) way around that.



  • @danal said in Sd card disk Image:

    Actually, I agree that a complete image for each MAJOR release would be a wonderful thing for the community. I'm never 101% confident that I have the right things on an SD, because tidbits of information, like which iap... or the exact name of the firmware file, or similar are spread all over the place. The forum, the wiki, release notes, maybe other places.

    Thanks you totally get my point...

    @danal said in Sd card disk Image:

    With one caveat: Any necessary release-to-release config incompatibilities.

    Yes that's life, if you upgrade from a much lower version you must be willing to put the effort.


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.