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

    Roto Toolboard, no extruder motor motion?

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    4
    21
    369
    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.
    • bug2k22undefined
      bug2k22 @Phaedrux
      last edited by

      @Phaedrux Entering that command to the console at the web interface produces no output.

      07/01/2025, 22:13:36 	M98 P"config.g"
      07/01/2025, 22:12:21 	M98 P"config.g"
      07/01/2025, 20:53:30 	Connection established
      
      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        Do you experience the same issue on 3.5.4 stable release?

        Z-Bot CoreXY Build | Thingiverse Profile

        bug2k22undefined 1 Reply Last reply Reply Quote 0
        • bug2k22undefined
          bug2k22 @Phaedrux
          last edited by

          @Phaedrux I haven't run this configuration with 3.5.4. With the previous setup, upgrading to 3.5.4 broke the setup and the board firmware became corrupt and had to recover with a usb cable. So I upgraded to the latest beta on the board and sbc and all has been working well.

          I presume it's not a simple task to downgrade both boards and all the sbc packages to a previous version?

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

            @bug2k22 you should be able to run the following

            M997 S2 F"stable-3.5"
            M997 S2
            

            and that should downgrade you to 3.5.4

            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

            bug2k22undefined 1 Reply Last reply Reply Quote 0
            • bug2k22undefined
              bug2k22 @jay_s_uk
              last edited by

              @jay_s_uk Does that downgrade the boards and all sbc (pi5) packages too?

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

                @bug2k22 yes, it should do
                If it only downgrades DSF/DWC you can then issue M997 and M997 B20 to flash the firmware to the mainboard and toolboard

                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

                bug2k22undefined 1 Reply Last reply Reply Quote 0
                • bug2k22undefined
                  bug2k22 @jay_s_uk
                  last edited by

                  @jay_s_uk The second M997 S2 command did flash up a notice saying it was upgrading, but nothing seems to have changed, restarting the board shows the 3.6.0-beta.2 firmware on all boards and the sbc packages are still on 3.6.0-beta.2.
                  If I ssh in to the pi, I see that the duet3d.list is now showing "deb https://pkg.duet3d.com/ stable-3.5 armv7" so it is on the stable channel but nothing downgrades.

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

                    @bug2k22 try running M997 S2 V"3.5.4"

                    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

                    bug2k22undefined 1 Reply Last reply Reply Quote 0
                    • bug2k22undefined
                      bug2k22 @jay_s_uk
                      last edited by

                      @jay_s_uk Thanks, that did complete the downgrade on all boards and the pi.

                      Duet 3 MB6HC 	MB6HC 	3.5.4
                      Duet 3 Expansion TOOL1RR
                      TOOL1RR 	3.5.4
                      Duet Software Framework 	DSF 	3.5.4
                      Duet Web Control 	DWC 	3.5.4 
                      

                      This has not changed the behaviour, still no movement on the extruder motor.
                      I have just double checked the cable from the toolboard to the motor and connectivity is fine on all pins.

                      jay_s_ukundefined droftartsundefined 2 Replies Last reply Reply Quote 0
                      • jay_s_ukundefined
                        jay_s_uk @bug2k22
                        last edited by

                        @bug2k22 in that case i'll leave you back with @Phaedrux or @droftarts

                        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

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

                          @bug2k22 Can you try moving your M906 (set motor current) to after the M584, for both the XYZ axes and E? See https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m906-set-motor-currents

                          Order dependency
                          This command must be later in config.g than any M584 command.

                          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

                          bug2k22undefined 1 Reply Last reply Reply Quote 0
                          • bug2k22undefined
                            bug2k22 @droftarts
                            last edited by

                            @droftarts Thanks Ian, it's now working!

                            I didn't look at M906 as it seems to work with the extruder connected directly to the 6HC even with it early in the config. Something to remember for future installs.

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

                              @bug2k22 It would have been reverting the currents to the defaults, I think. I'm not sure what the Roto default is, may be 400mA, as it usually expects a Roto extruder, which uses a lower current motor, so might just not had enough current to turn yours.

                              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

                              1 Reply Last reply Reply Quote 0
                              • Phaedruxundefined Phaedrux marked this topic as a question
                              • Phaedruxundefined Phaedrux has marked this topic as solved
                              • First post
                                Last post
                              Unless otherwise noted, all forum content is licensed under CC-BY-SA