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

    RRF 3.01-RC11, DWC 2.1.6 and DSF 2.1.3 released

    Scheduled Pinned Locked Moved
    Beta Firmware
    7
    20
    910
    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.
    • dc42undefined
      dc42 administrators @mwolter
      last edited by

      I've put new RRF binaries at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0 to fix the following:

      • Changing baud rate for the PanelDue port didn't work unless the M575 command was repeated. Note that in this version, the M575 command is mandatory when using a PanelDue, even on the Duet WiFi, Ethernet and Maestro.
      • Virtual extruder position was missing from the object model
      • HTTP requests for files with very long names reported a "Filename too long" error and didn't return a response. They now return a 404 response and issue a warning of a possible virus attack from the sending IP address.

      On the Duet WiFi, Ethernet and Maestro it shojud now be possible to use the two I/O pins of the PanelDue port as GPIO, if there is no M575 p1 command in config.g.

      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

      A Former User? botundefined 2 Replies Last reply Reply Quote 0
      • A Former User?
        A Former User @dc42
        last edited by

        @dc42 said in RRF 3.01-RC11, DWC 2.1.6 and DSF 2.1.3 released:

        Note that in this version, the M575 command is mandatory when using a PanelDue, even on the Duet WiFi, Ethernet and Maestro.

        temporary or something that will be part of 3.01?

        dc42undefined 1 Reply Last reply Reply Quote 0
        • dc42undefined
          dc42 administrators @A Former User
          last edited by dc42

          @bearer said in RRF 3.01-RC11, DWC 2.1.6 and DSF 2.1.3 released:

          @dc42 said in RRF 3.01-RC11, DWC 2.1.6 and DSF 2.1.3 released:

          Note that in this version, the M575 command is mandatory when using a PanelDue, even on the Duet WiFi, Ethernet and Maestro.

          temporary or something that will be part of 3.01?

          All of these changes will be included in 3.01 stable.

          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
          • ChrisPundefined
            ChrisP
            last edited by ChrisP

            The "iterations" meta command variable isn't handled correctly when using a D3+SBC setup. This was discovered when attempting to use the example object identification macro posted here. The code example there works as intended when the D3 is used in standalone mode, but returns an error in a D3+SBC setup.

            gtj0undefined 1 Reply Last reply Reply Quote 0
            • ChrisPundefined
              ChrisP
              last edited by

              The identification of objects by parsing the object label comments (PrusaSlicer) and process comments (Simplify3D) for object cancellation features etc. currently works on a D3 in standalone mode but fails if using a D3+SBC setup. Noted here, but first identified here.

              1 Reply Last reply Reply Quote 0
              • gtj0undefined
                gtj0 @ChrisP
                last edited by

                @ChrisP said in RRF 3.01-RC11, DWC 2.1.6 and DSF 2.1.3 released:

                The "iterations" meta command variable isn't handled correctly when using a D3+SBC setup. This was discovered when attempting to use the example object identification macro posted here. The code example there works as intended when the D3 is used in standalone mode, but an error if the a D3+SBC setup.

                @ChrisP said in RRF 3.01-RC11, DWC 2.1.6 and DSF 2.1.3 released:

                The identification of objects by parsing the object label comments (PrusaSlicer) and process comments (Simplify3D) for object cancellation features etc. currently works on a D3 in standalone mode but fails if using a D3+SBC setup. Noted here, but first identified here.

                These will get better attention if you open issues for @chrishamm on GitHub if you can.

                1 Reply Last reply Reply Quote 0
                • botundefined
                  bot @dc42
                  last edited by

                  @dc42 said in RRF 3.01-RC11, DWC 2.1.6 and DSF 2.1.3 released:

                  • HTTP requests for files with very long names reported a "Filename too long" error and didn't return a response. They now return a 404 response and issue a warning of a possible virus attack from the sending IP address.

                  Wat?

                  *not actually a robot

                  dc42undefined 1 Reply Last reply Reply Quote 0
                  • dc42undefined
                    dc42 administrators @bot
                    last edited by

                    @bot said in RRF 3.01-RC11, DWC 2.1.6 and DSF 2.1.3 released:

                    @dc42 said in RRF 3.01-RC11, DWC 2.1.6 and DSF 2.1.3 released:

                    • HTTP requests for files with very long names reported a "Filename too long" error and didn't return a response. They now return a 404 response and issue a warning of a possible virus attack from the sending IP address.

                    Wat?

                    See https://forum.duet3d.com/topic/15346/duetwifi-error-filename-too-long.

                    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 2
                    • ChrisPundefined
                      ChrisP
                      last edited by

                      Perhaps one for @chrishamm ....
                      I had previously reported here that a pause caused by the filament sensor resulted in the printer just halting this was with D3+SBC setup. On trying again in standalone, the pause works as expected and can be resumed. Therefore a DCS issue?

                      dc42undefined 1 Reply Last reply Reply Quote 0
                      • dc42undefined
                        dc42 administrators @ChrisP
                        last edited by

                        @ChrisP said in RRF 3.01-RC11, DWC 2.1.6 and DSF 2.1.3 released:

                        Perhaps one for @chrishamm ....
                        I had previously reported here that a pause caused by the filament sensor resulted in the printer just halting this was with D3+SBC setup. On trying again in standalone, the pause works as expected and can be resumed. Therefore a DCS issue?

                        I believe that issue is already on his list to look into.

                        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