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

    Multiple motion system

    Scheduled Pinned Locked Moved Solved
    General Discussion
    8
    69
    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.
    • Alvaundefined
      Alva @Alva
      last edited by

      3723076a-3e13-4b97-8ac7-195a87a4f8c8-image.png

      droftartsundefined 1 Reply Last reply Reply Quote 0
      • droftartsundefined
        droftarts administrators @Alva
        last edited by

        @Alva We're going to release 3.6.0-beta.3 in a couple of days, please retest when we release that.

        Ian

        Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

        Alvaundefined 1 Reply Last reply Reply Quote 0
        • Alvaundefined
          Alva @droftarts
          last edited by

          @droftarts Sure will do. Thank you.

          T3P3Tonyundefined 1 Reply Last reply Reply Quote -1
          • T3P3Tonyundefined
            T3P3Tony administrators @Alva
            last edited by

            @Alva it's released:

            https://forum.duet3d.com/topic/37289/software-version-3-6-0-beta-3-now-available

            Testing is appreciated 🙏

            www.duet3d.com

            Alvaundefined 1 Reply Last reply Reply Quote 0
            • o_lampeundefined
              o_lampe
              last edited by

              My understanding of the dual gcode stream is: you can open two gcode files at the same time and have a daemon.g running in the background?
              At the same time you'd have to split the config.g into two portions.
              Maybe put the U-axis specific lines in the startcode of the second stream?

              Alvaundefined 1 Reply Last reply Reply Quote 0
              • Alvaundefined
                Alva @T3P3Tony
                last edited by

                @T3P3Tony Tested the above mentioned testing procedure and got the same error as 3.6.0.beta2 + 5.

                1 Reply Last reply Reply Quote 0
                • Alvaundefined
                  Alva @o_lampe
                  last edited by Alva

                  @o_lampe My requirement is to utilize the unused axes during printing, with their movement controlled via daemon.g and triggered by a flag. My understanding of multiple motion systems is that the unused axes should be accessible to the other motion system. However, the error I am encountering indicates that the unused axes are still being treated as part of the motion system responsible for the print job.

                  Alvaundefined 1 Reply Last reply Reply Quote 0
                  • Alvaundefined
                    Alva @Alva
                    last edited by

                    Any updates about this topic? My observation is 3.6.0-beta2+3 worked , but after that it is broken. Thank you

                    droftartsundefined 1 Reply Last reply Reply Quote 0
                    • droftartsundefined
                      droftarts administrators @Alva
                      last edited by

                      @Alva I've asked @dc42 to have a look at the issue.

                      Ian

                      Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                      Alvaundefined 1 Reply Last reply Reply Quote 0
                      • Alvaundefined
                        Alva @droftarts
                        last edited by

                        @droftarts Okay , 🙏 thank you.

                        Alvaundefined 1 Reply Last reply Reply Quote 0
                        • Alvaundefined
                          Alva @Alva
                          last edited by Alva

                          @Alva @dc42 sorry for writing again, but will there be fix regarding this topic in the next version?

                          dwuk3dundefined 1 Reply Last reply Reply Quote 0
                          • T3P3Tonyundefined T3P3Tony referenced this topic
                          • dwuk3dundefined
                            dwuk3d @Alva
                            last edited by

                            @Alva I think I am getting the same issue as you - in 3.5.4 I can access my U axis in Motion system 1 ok - but not in any of the 3.6.0 beta versions I have tried.

                            The problems I am getting though the 3.5.4 is that the synchronisation isn't working - with either M598 and M400 don't seem to work. Plus also I can't seem to extend the length of the queue with M595 beyond 5 entries.

                            dwuk3dundefined 1 Reply Last reply Reply Quote 0
                            • dwuk3dundefined
                              dwuk3d @dwuk3d
                              last edited by dwuk3d

                              @Alva Update - Just managed to get it working in 3.6.0b4 - by surrounding all references to the U axis in M596 P1 - including in the homing macro's

                              M598 still not working for me though -

                              plus in my case I am finding a connected Mini5+ board runs slow in 3.6.0b vs 3.5.4 - so I have left that board at 3.5.4

                              jay_s_ukundefined gloomyandyundefined 2 Replies Last reply Reply Quote 0
                              • jay_s_ukundefined
                                jay_s_uk @dwuk3d
                                last edited by

                                @dwuk mixing 3.5.4 and 3.6b4 based boards, with the amount of changes that have happened between the two, is a really bad idea

                                Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                                dwuk3dundefined 1 Reply Last reply Reply Quote 0
                                • gloomyandyundefined
                                  gloomyandy @dwuk3d
                                  last edited by

                                  @dwuk said in Multiple motion system:

                                  plus in my case I am finding a connected Mini5+ board runs slow in 3.6.0b vs 3.5.4

                                  Can you provide more details on that? What exactly is slow?

                                  dwuk3dundefined 1 Reply Last reply Reply Quote 0
                                  • dwuk3dundefined
                                    dwuk3d @gloomyandy
                                    last edited by

                                    @gloomyandy The U&V axis don't react instantly when you press the +1/+10 etc. button - there seems to be a small delay.

                                    Also when homing the U Axis - it is a two pass process - normally the first hit happens, the tool head immediately moves back, and then has its' second attempt, but with 3.6.0 again there is a slight delay.

                                    The the Mini5+ board is on 3.5.4 there is no noticeable delay.

                                    If there isn't any obvious answer I will make a short video at some point to demonstrate the difference.

                                    dwuk3dundefined jay_s_ukundefined 2 Replies Last reply Reply Quote 0
                                    • dwuk3dundefined
                                      dwuk3d @jay_s_uk
                                      last edited by

                                      @jay_s_uk Yes I am sure you are right. I am not really seeing any advantage in 3.6.0b4 over 3.5.4 at the moment - so will probably revert the whole lot back to 3.5.4 - as all 3.6.0 is unusable for me.

                                      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                                      • dwuk3dundefined
                                        dwuk3d @dwuk3d
                                        last edited by dwuk3d

                                        @gloomyandy Just realised this is @Alva's thread - if you look at my one you will see a lot more detail of the 'slowness' problem

                                        1 Reply Last reply Reply Quote 0
                                        • jay_s_ukundefined
                                          jay_s_uk @dwuk3d
                                          last edited by

                                          @dwuk if you're doing any remapping of axes after movement in 3.5.4 that's unusable too.
                                          You'll notice a difference when you come to print something as the movement code is way better in 3.6, especially pressure advance and input shaping

                                          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                                          dwuk3dundefined 1 Reply Last reply Reply Quote 0
                                          • jay_s_ukundefined
                                            jay_s_uk @dwuk3d
                                            last edited by

                                            @dwuk the out of sync/delay issues with a mainboard in expansion mode has been fixed internally. Don't know if a build has been made available

                                            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

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