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

Motor brake not working on expansion board

Scheduled Pinned Locked Moved Solved
Duet Hardware and wiring
6
33
1.1k
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
    mike_b
    last edited by mike_b 24 Aug 2024, 21:19

    Hi everyone. I have two Mini5+ boards controlling 8 stepper motors. When I try to set the motor break for any motor on the main board like this:

    M569.7 P0.0 C"out5" S25
    

    everything works correctly and as expected. However, when I try to setup a break for a motor on the second board that is being used as an expansion board, like this:

     M569.7 P40.0 C"40.out5" S25
    

    I get this error:

    24/08/2024, 15.16.00 	Error in start-up file config.g line 76: M569.7:
    24/08/2024, 15.16.00 	Error: M569.7: 
    

    Any help would be sincerely appreciated! Thanks in advance

    undefined 1 Reply Last reply 24 Aug 2024, 21:21 Reply Quote 0
    • undefined
      dc42 administrators @mike_b
      last edited by 24 Aug 2024, 21:21

      @mike_b this is a known issue, fixed in 3.6.0-alpha and in the forthcoming 3.5.3 release.

      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 24 Aug 2024, 21:22 Reply Quote 0
      • undefined
        mike_b @dc42
        last edited by 24 Aug 2024, 21:22

        @dc42 wow, thank you for the prompt reply! Very much appreciated!

        1 Reply Last reply Reply Quote 0
        • undefined
          mike_b @dc42
          last edited by 24 Aug 2024, 21:29

          @dc42 quick question: do you recommend testing 3.6.0-alpha at this point? Or just waiting for the 3.5.3?

          undefined 1 Reply Last reply 2 Sept 2024, 10:03 Reply Quote 0
          • undefined
            dc42 administrators @mike_b
            last edited by 2 Sept 2024, 10:03

            @mike_b we recently released 3.5.3-rc.1 so I suggest you try that.

            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 undefined 3 Replies Last reply 3 Sept 2024, 02:24 Reply Quote 0
            • undefined
              mike_b @dc42
              last edited by 3 Sept 2024, 02:24

              @dc42 Thank you! This is fantastic. I'll try it out tomorrow and report any bugs in the beta channel. Thanks again!

              1 Reply Last reply Reply Quote 0
              • undefined
                mike_b @dc42
                last edited by 3 Sept 2024, 14:46

                @dc42 apologies up front if I'm missing something obvious here. However, in your dropbox, I don't see the Duet3_SBCiap32_Mini5plus.bin file which, I assume, I would a 3.5.3-rc.1 version off to test if this bug has been resolved? Or, is it safe to test with Duet 3 Expansion Mini5plus running at 3.5.2?

                undefined 1 Reply Last reply 3 Sept 2024, 14:59 Reply Quote 0
                • undefined
                  jay_s_uk @mike_b
                  last edited by 3 Sept 2024, 14:59

                  @mike_b https://github.com/Duet3D/RepRapFirmware/releases/tag/3.5.3-rc.1

                  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

                  undefined 1 Reply Last reply 3 Sept 2024, 15:03 Reply Quote 0
                  • undefined
                    mike_b @jay_s_uk
                    last edited by 3 Sept 2024, 15:03

                    Hi @jay_s_uk, unfortunately I don't see Duet3_CANiap32_Mini5plus.bin in the link provided. Am I missing something?

                    undefined 1 Reply Last reply 3 Sept 2024, 15:05 Reply Quote 0
                    • undefined
                      jay_s_uk @mike_b
                      last edited by 3 Sept 2024, 15:05

                      @mike_b DSF should handle the SBC IAP file, they aren't part of a normal release

                      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

                      undefined 1 Reply Last reply 3 Sept 2024, 15:09 Reply Quote 0
                      • undefined
                        mike_b @jay_s_uk
                        last edited by mike_b 9 Mar 2024, 15:11 3 Sept 2024, 15:09

                        @jay_s_uk When you say "DSF should handle the SBC IAP file" do you mean that I'll be able to find the .bin file in the DSF git repo?

                        undefined 1 Reply Last reply 3 Sept 2024, 15:11 Reply Quote 0
                        • undefined
                          jay_s_uk @mike_b
                          last edited by 3 Sept 2024, 15:11

                          @mike_b when you sudo apt update/upgrade, everything gets pulled down and automatically updated. so I suppose I should say the DSF repository (not git)

                          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

                          undefined 1 Reply Last reply 3 Sept 2024, 15:17 Reply Quote 0
                          • undefined
                            mike_b @jay_s_uk
                            last edited by 3 Sept 2024, 15:17

                            @jay_s_uk ah, Ok, got it, thank you! So I guess that mean I'll have to figure out my second issue https://forum.duet3d.com/post/344169, for some reason, despite switching to the unsteady deb repo (i.e deb https://pkg.duet3d.com/ unstable-3.5 armv7 in my sources, running apt update/upgrade doesn't get me 3.5.3-rc

                            1 Reply Last reply Reply Quote 0
                            • undefined
                              p8blr @dc42
                              last edited by 3 Sept 2024, 19:11

                              @dc42 How do we update to this if we're running in SBC mode? The M997 commands don't work.

                              undefined 1 Reply Last reply 3 Sept 2024, 19:12 Reply Quote 0
                              • undefined
                                jay_s_uk @p8blr
                                last edited by 3 Sept 2024, 19:12

                                @p8blr you can't at the moment

                                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

                                undefined 1 Reply Last reply 3 Sept 2024, 21:14 Reply Quote 0
                                • undefined
                                  mike_b @jay_s_uk
                                  last edited by mike_b 9 Mar 2024, 21:14 3 Sept 2024, 21:14

                                  Hey @jay_s_uk when you say "you can't at the moment" do you mean you can't at the moment because of a bug? Or do you mean you can't update to an -rc release in SBC in general? I ask because there does seem to be a version 3.5.3-rc1 in the repo here so I'm not really sure what the issue is. Could you help me understand?

                                  undefined 1 Reply Last reply 3 Sept 2024, 22:54 Reply Quote 1
                                  • undefined
                                    jay_s_uk @mike_b
                                    last edited by 3 Sept 2024, 22:54

                                    @mike_b just wait for @chrishamm to respond. You can usually upgrade to RC versions but it's obviously not working so be patient

                                    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

                                    undefined 1 Reply Last reply 4 Sept 2024, 20:05 Reply Quote 0
                                    • undefined
                                      mike_b @jay_s_uk
                                      last edited by 4 Sept 2024, 20:05

                                      Hey @jay_s_uk Thanks for your feedback! I truly appreciate everyone’s input and am happy to wait for a response 😊 Thanks again!

                                      chrishammundefined 1 Reply Last reply 5 Sept 2024, 19:28 Reply Quote 0
                                      • chrishammundefined
                                        chrishamm administrators @mike_b
                                        last edited by 5 Sept 2024, 19:28

                                        @mike_b It's now available via the package feeds, apologies for the delay.

                                        Duet software engineer

                                        undefined 1 Reply Last reply 5 Sept 2024, 20:06 Reply Quote 1
                                        • undefined
                                          mike_b @chrishamm
                                          last edited by mike_b 9 May 2024, 20:23 5 Sept 2024, 20:06

                                          Thanks @chrishamm, my entire system is now running 3.5.3-rc.1 as shown here

                                          Unfortunately @dc42 I'm getting the same bug as before:

                                          05/09/2024, 14.02.03 -Error in start-up file config.g line 156: M569.7:
                                          05/09/2024, 14.02.03 -Error: M569.7:
                                          

                                          Interestingly, I don't see these errors after power cycling the board and the SBC. That error only shows up when I do an emergency stop or chose "restart mainboard" or "run config file" after editing the config file. Although I guess I'm not getting those messages after a power cycle because DWC starts up only after the error, so doesn't show up in the console?

                                          @dc42 also, I just realized that my particular issue was never mirrored on github - or mentioned in the release notes - so now I'm wondering if this issue got confused with this one?

                                          Looking through the changelogs of previous releases, I see this limitation mentioned for 3.4.0RC1 but it's never mentioned again:
                                          M569.7 (configure driver brake port) is supported, initially on the main board only

                                          undefined 1 Reply Last reply 6 Sept 2024, 16:21 Reply Quote 0
                                          • First post
                                            Last post
                                          Unless otherwise noted, all forum content is licensed under CC-BY-SA