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

unstable movement in X/Y with latest beta

Scheduled Pinned Locked Moved
Beta Firmware
4
20
951
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
    last edited by 28 Dec 2019, 21:49

    Bear in mind that in CNC mode, the firmware attempts to execute G0 moves at the maximum feedrates permitted, as configured using M203. Also that when drawing circles expressed as G0 moves, the actual maximum possible may be limited by the maximum XY jerk speeds configured using M566, because jerk is needed when transitioning from one segment of the approximated circle to the next.

    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 28 Dec 2019, 22:21 Reply Quote 0
    • undefined
      daavery
      last edited by 28 Dec 2019, 21:57

      looks like its a DWC problem - running direct from SD on DUET3 and panel due the motion is flawless

      undefined 1 Reply Last reply 28 Dec 2019, 22:05 Reply Quote 0
      • undefined
        dc42 administrators @daavery
        last edited by 28 Dec 2019, 22:05

        @daavery said in unstable movement in X/Y with latest beta:

        looks like its a DWC problem - running direct from SD on DUET3 and panel due the motion is flawless

        As you are using Duet 3, have you tried this using RRF 3.0RC1 and Duet Software Framework 1.2.1.0?

        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 2 Replies Last reply 28 Dec 2019, 22:25 Reply Quote 0
        • undefined
          daavery @dc42
          last edited by 28 Dec 2019, 22:21

          @dc42 the gcode looks fine - posted from fusion360 via reprapfw post

          slot caused by skipped g0z8

          slot again

          1 Reply Last reply Reply Quote 0
          • undefined
            daavery @dc42
            last edited by 28 Dec 2019, 22:25

            @dc42 yep that's where i started - then reverted to b12 - then disconnected the pi ribbon cable and connected a paneldue and made up an SD card to run on. that combo is working flawlessly

            undefined 1 Reply Last reply 28 Dec 2019, 22:29 Reply Quote 0
            • undefined
              dc42 administrators @daavery
              last edited by 28 Dec 2019, 22:29

              @daavery said in unstable movement in X/Y with latest beta:

              @dc42 yep that's where i started - then reverted to b12 - then disconnected the pi ribbon cable and connected a paneldue and made up an SD card to run on. that combo is working flawlessly

              Thanks, I'll alert @chrishamm to this as it looks like the issue may be in DSF.

              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
              • undefined
                daavery @dc42
                last edited by 28 Dec 2019, 22:29

                @dc42 waiting on 55min job to finish a test pass then i will do a full panel with router on

                1 Reply Last reply Reply Quote 0
                • undefined
                  daavery
                  last edited by daavery 28 Dec 2019, 22:31

                  @dc42 any debugging info I can get for you guys?

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    daavery
                    last edited by 29 Dec 2019, 00:41

                    1 panel - 450 bored holes - 55 min - no glitches - looks like i'm running without the pi for now

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      daavery
                      last edited by 29 Dec 2019, 02:26

                      more detail - ran TEST.gcode 2 times from DWC - capturing M111 P3 S1 via duet3 micro usb port

                      there are obvious differences - random gcode lines are out of order

                      compare report

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        daavery
                        last edited by 29 Dec 2019, 02:35

                        duet config

                        Board: Duet 3 MB6HC (MB6HC)
                        DSF Version: 1.2.1.0
                        Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.0beta12 (2019-11-02b1)

                        pi config

                        Start-Date: 2019-12-26 09:07:20
                        Commandline: apt-get upgrade
                        Upgrade:
                        duettools:armhf (1.1.0.5, 1.2.1.0),
                        reprapfirmware:armhf (1.1.0.5-1, 1.2.1.0-1),
                        duetwebserver:armhf (1.1.2.1, 1.2.1.0),
                        duetcontrolserver:armhf (1.1.0.5, 1.2.1.0),
                        duetruntime:armhf (1.1.0.5, 1.2.1.0),
                        duetsoftwareframework:armhf (1.1.0.5, 1.2.1.0),
                        duetsd:armhf (1.0.4, 1.0.5)
                        End-Date: 2019-12-26 09:08:06

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          daavery
                          last edited by 29 Dec 2019, 23:59

                          @dc42 @chrishamm did you see the compare i did - doing a M111 P3 S1 and logging the duet3 usb port while running TEST.gcode ( see above) I see random lines of gcode being swapped in order. the 2 runs in the compare were done by just restarting the running job

                          i'm somewhat suprised others are not seeing the same issue.

                          1 Reply Last reply Reply Quote 0
                          • undefined
                            chrishamm administrators
                            last edited by 2 Jan 2020, 20:45

                            There was an issue in DSF > 1.1.0.5 and < 1.2.2.0 that could sometimes cause out-of-order execution of G-codes from a file print - sorry for that. It's fixed in DSF 1.2.2.0.

                            Duet software engineer

                            1 Reply Last reply Reply Quote 0
                            • undefined
                              daavery
                              last edited by 3 Jan 2020, 03:01

                              @chrishamm Tested here - looks good - thanks

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