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

    How to upgrade from 2.05.1 to 3.1.1?

    Scheduled Pinned Locked Moved Solved
    Firmware installation
    4
    42
    2.5k
    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.
    • A Former User?
      A Former User @zapta
      last edited by

      @zapta said in How to upgrade from 2.05.1 to 3.1.1?:

      Can you explain?

      sorry, just a bad joke - there was a buttload of people posting something like "oh my god my paneldue stopped working" after upgrading to 3.1.1 ... figured one of them could test estop on the duet3 ... so most recent posts containing M575 would be one of those.

      Anyways, back on topic - is there an signal we can analyze to indicate the actual reset? curious if the bad command comes before or after the duet being reset.

      PanelDue             Duet
      
      N162 M112 ;ð␏*192 >
                         < {"seq":3,"resp":"Emergency Stop! Reset the controller to continue.\n"}
                         < {"seq":4,"resp":"Error: Bad command: 192\n"}
      N163 M999*46       >
      N164 M408 S0 R2*47 >
      N165 M408 S0 R4*40 >
                         < {"seq":1,"resp":"WiFi module started\n"}
      

      looks like it might be before, or it gets reset again by M999?

      zaptaundefined 1 Reply Last reply Reply Quote 0
      • zaptaundefined
        zapta @A Former User
        last edited by zapta

        @bearer said in How to upgrade from 2.05.1 to 3.1.1?:

        is there an signal we can analyze to indicate the actual reset?

        Maybe one of the outputs that are turned off on reset? Heaters, PS_ON, etc? I don't know thought what is the delay added by the power mosfets so maybe the signal before the mosfet driver.

        BTW, what logic analyzer are you using? I am using an 8 bit saleae which is good enough for the rare occasions I need it but its software is not great.

        A Former User? 1 Reply Last reply Reply Quote 0
        • A Former User?
          A Former User @zapta
          last edited by

          Maybe one of the outputs that are turned off on reset?

          I tried a few different ones, was just surprised by the spread; but it definitely looks like its the code that was supposed to clear the buffer that isn't doing it and the firmware has time to process the rest triggering a "Bad command" error before reset occurs.

          BTW, what logic analyzer are you using?

          I got a Pro8 from Saleae; and v1 software is junk but I'm quite happy with the v2 beta that they just did a survey asking if v2 was mature enough to replace v1. I said 95%, they're pretty good at bugfixing, but not quite superhero level like dc42.

          If you haven't tried the beta, then I'd give that a go, I've only seen two bugs that are just visual representation and as far as I can tell they were hunted down a while back.

          If you were wondering about the side by side serial representation then I did that by hand, but its quite easy with the Pro8 as it has the data terminal, I just added some spacing.
          da406af5-ecd3-4c3c-8ff5-0f7ca59c25fe-image.png

          Anyways, all the planets aligned and the mail man just dropped off my Hemera, and seconds later the UPS guy came with the power supply and 3-wire fans so stuff to do:)))

          zaptaundefined 1 Reply Last reply Reply Quote 0
          • zaptaundefined
            zapta @A Former User
            last edited by

            @bearer said in How to upgrade from 2.05.1 to 3.1.1?:

            I'm quite happy with the v2 beta...

            Thanks, I will give it a try. The serial analyzer dump of V2 seems to be easier to to understand.

            A Former User? 1 Reply Last reply Reply Quote 0
            • A Former User?
              A Former User @zapta
              last edited by

              @zapta said in How to upgrade from 2.05.1 to 3.1.1?:

              The serial analyzer dump of V2 seems to be easier to to understand.

              The "data terminal" shown is for some unkown reason reserved for the Pro8 and Pro16, but everything is easier to read and use in v2 imho.

              zaptaundefined 1 Reply Last reply Reply Quote 0
              • zaptaundefined
                zapta @A Former User
                last edited by zapta

                @bearer, V2 looks nicer indeed and I was able to see the terminal widget even though the icon had a red 'pro' marking. Possibly they will cripple it once the stable version will be release. I could also see footprint for Analog functionality even though I don't have any.

                af918e9c-3d11-4526-badb-886c7cc8be73-image.png

                BTW, finding the problematic section in the graph is very easy. It's the only place where the duet sends a responds before the paneldue transmition completes.

                1 Reply Last reply Reply Quote 0
                • A Former User?
                  A Former User
                  last edited by A Former User

                  Interesting, i'd squirrel away the installer in case they cripple it in a future version, seems odd to limit features like that. Big 👎 for Saleae if they do.

                  Anyways, yes, can see where the Duet reacts with bad command (although i don't think mine overlapped like that it did when zoomed in), but whats not clear is when the reset occurs. I think reset occurs after the bad command

                  Btw, right click the decoded bars above and you can choose just ascii to aid readability with non-binary protocols.

                  1 Reply Last reply Reply Quote 0
                  • zaptaundefined
                    zapta
                    last edited by

                    Since this thread is about a wider topic, I moved the STOP issue to a new thread https://forum.duet3d.com/topic/17990/rrf3-paneldue-stop-function-results-in-a-false-error-message

                    1 Reply Last reply Reply Quote 1
                    • zaptaundefined
                      zapta @A Former User
                      last edited by

                      @bearer said in How to upgrade from 2.05.1 to 3.1.1?:

                      its odd that duet3 people have been using paneldue since the first rrf3 with no similar reports

                      Is checksum enabled by default?

                      A Former User? 1 Reply Last reply Reply Quote 0
                      • A Former User?
                        A Former User @zapta
                        last edited by A Former User

                        @zapta said in How to upgrade from 2.05.1 to 3.1.1?:

                        Is checksum enabled by default?

                        afaik its always on and not configurable in the PanelDue, and checksums was default enabled in RRF until the PanelDue port was not enabled at all by default anymore as of 3.1-ish

                        @dc42 seems to back in business so hopefully he'll take a look at why this is treated differently in RRF3. Its pretty clear the issue is RRF2 clears the RX buffer after receiving M112 or 0xf0 0x0f, while RRF3 does not clear the RX buffer.

                        edit: ah, new thread might be cleaner. But I'd suggest replacing the pictures with one where the bad command matches the checksum on the logic analyzer - or maybe just annotating the difference.

                        1 Reply Last reply Reply Quote 1
                        • zaptaundefined
                          zapta
                          last edited by

                          My printer now run on RRF3 and everything looks good. Thanks everybody for the help.

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