• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login

Upgrading Firmware from 2.02RC3 to 3.2

Scheduled Pinned Locked Moved
Firmware installation
4
17
743
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • undefined
    dc42 administrators @sinnedwrong
    last edited by 24 Mar 2021, 17:56

    @sinnedwrong said in Upgrading Firmware from 2.02RC3 to 2.05.1:

    @dc42
    response after uploading 3.2 and power cycling machine

    M98 P"config.g"
    HTTP is enabled on port 80
    FTP is disabled
    TELNET is disabled
    Warning: M308 command is not supported
    Warning: M950 command is not supported
    Warning: M308 command is not supported
    Warning: M950 command is not supported
    Warning: M950 command is not supported

    comments at start of config.g

    ; Configuration file for Duet Maestro (firmware version 3)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 23 2021 17:45:18 GMT+0000 (Greenwich Mean Time)

    Those warnings indicate that you are not running RRF3.2, you are running RRF version 2.x.

    Duet WiFi hardware designer and firmware engineer
    Please do not ask me for Duet support via PM or email, use the forum
    http://www.escher3d.com, https://miscsolutions.wordpress.com

    undefined 1 Reply Last reply 24 Mar 2021, 18:06 Reply Quote 0
    • undefined
      sinnedwrong @dc42
      last edited by 24 Mar 2021, 18:06

      @dc42
      I have just recreated firmware and specificallty ensured in the config tool to select V3.0 or later.
      It provides in the zip file DuetMaestroFirmware.bin 470kb compressed size 470kb 5% ratio with a CRC 2144DF1C

      undefined 1 Reply Last reply 24 Mar 2021, 18:16 Reply Quote 0
      • undefined
        sinnedwrong @sinnedwrong
        last edited by 24 Mar 2021, 18:16

        @sinnedwrong and to confirm
        M115
        FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2020-02-09b1

        What's the way forward?

        undefined 1 Reply Last reply 24 Mar 2021, 18:21 Reply Quote 0
        • undefined
          sinnedwrong @sinnedwrong
          last edited by 24 Mar 2021, 18:21

          @sinnedwrong and just discovered this which could be the problem as I hadn't done this. Could be tomorrows challenge EXCEPT how easy is it to go from 3.x back to 2.05?

          **Updating from RRF 2.x to 3.x
          Upgrading ANY Duet 2 from 2.x to 3.0 or later requires installing 3.0 first.

          The version 3.01 and later binaries are too large to be installed by the IAP program supported by version 1.x and 2.x firmware. Therefore you cannot upgrade directly from version 1.x or 2.x firmware to 3.01 or later firmware. This is the procedure:

          Download file Duet2and3Firmware-3.0.zip from https://github.com/Duet3D/RepRapFirmware...
          Upload and install that file on the Duet through Duet Web Control
          Send M115 and check the response to confirm that you are running version 3.0 firmware
          You can then upgrade to version 3.01 or later firmware.
          Important! When upgrading from 1.x or 2.x firmware to 3.x you will need to make substantial changes to your config.g file. See RepRapFirmware 3 overview.**

          1 Reply Last reply Reply Quote 0
          • undefined
            Phaedrux Moderator
            last edited by 24 Mar 2021, 19:19

            If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them. Reboot after each. Use M115 to verify the firmware has been applied.
            https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
            https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
            https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip
            That will get your firmware and DWC up to date.

            You can see the change logs here:
            https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x

            For your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
            https://configtool.reprapfirmware.org/Start

            Backup your existing config files in the sys folder in case you want to switch back to RRF3. IT’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.

            These documents will come in handy during the conversion.
            https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
            https://duet3d.dozuki.com/Wiki/Gcode

            Z-Bot CoreXY Build | Thingiverse Profile

            undefined 1 Reply Last reply 11 Apr 2021, 12:47 Reply Quote 0
            • undefined
              sinnedwrong @Phaedrux
              last edited by 11 Apr 2021, 12:47

              @phaedrux I finally got brave enough to attempt the firmware upgrade which was straightforward as I guess you are not surprised. I now have an issue in my config files. The bed which was working perfectly under 2.05 so isn't a wiring fault is coming up with the message "Heater fault rising more slowly than expected 1.8C/sec"
              Settings in the RRF config tool:
              tick for heated bed, bang bang,
              values 120, 100, 10000,3988, 0
              which are the defaults after specifying an Ormerod 2 in the initial screen. M115 gives Firmware 3.2.2 X&Y axes zero OK. That's as far as I've tested.
              Ideas?

              undefined 1 Reply Last reply 11 Apr 2021, 15:52 Reply Quote 0
              • undefined
                dc42 administrators @sinnedwrong
                last edited by 11 Apr 2021, 15:52

                @sinnedwrong, I suggest you run heater tuning on the bed header. This will fix the fault message, also running the bed heater in bang-bang mode may cause Z banding.

                Duet WiFi hardware designer and firmware engineer
                Please do not ask me for Duet support via PM or email, use the forum
                http://www.escher3d.com, https://miscsolutions.wordpress.com

                undefined 1 Reply Last reply 11 Apr 2021, 17:24 Reply Quote 0
                • undefined
                  sinnedwrong @dc42
                  last edited by 11 Apr 2021, 17:24

                  @dc42 Clearly more reading and research to do however the RRF config tool was what specified bang/bang and I went with the default recommendation. Clearly I will now have to read https://duet3d.dozuki.com/Wiki/Tuning_the_heater_temperature_control and discover how to use heater tuning. Out of interest what is Z banding and should the config tool be updated?

                  Thanks

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    Phaedrux Moderator
                    last edited by 11 Apr 2021, 18:24

                    Well the config tool can't do the tuning for you, so even if you didn't select bang-bang there it wouldn't have any tuned PID values to use until you did a tuning cycle.

                    Z-Bot CoreXY Build | Thingiverse Profile

                    undefined 1 Reply Last reply 14 Apr 2021, 13:49 Reply Quote 0
                    • undefined
                      sinnedwrong @Phaedrux
                      last edited by 14 Apr 2021, 13:49

                      @phaedrux Just a quick reply to thank everybody, the TOY is now working successfully on 3.2.

                      A couple of points:
                      I didn't find in the change log for version 3.2 that BANG-BANG wouldn't work only that there was a new heating algorithm.
                      Removing the BANG-BANG option in the configuration tool might be a good idea to avoid confusion
                      Also for completeness it might be a good idea to change the title of this thread by adding the phrase "to 3.2". I don't think I'm allowed to do this, I suspect an admin or moderator needs to do this.

                      Thanks again for all the help

                      Dennis

                      undefined 1 Reply Last reply 14 Apr 2021, 18:03 Reply Quote 0
                      • undefined
                        dc42 administrators @sinnedwrong
                        last edited by 14 Apr 2021, 18:03

                        @sinnedwrong said in Upgrading Firmware from 2.02RC3 to 3.2:

                        I didn't find in the change log for version 3.2 that BANG-BANG wouldn't work only that there was a new heating algorithm.

                        Bang-bang can still be used. However, if you don't run heater tuning, then RRF knows nothing about your heater; so its heating rate may be lower than RRF expects, leading to a heater fault being raised.

                        Duet WiFi hardware designer and firmware engineer
                        Please do not ask me for Duet support via PM or email, use the forum
                        http://www.escher3d.com, https://miscsolutions.wordpress.com

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA