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

Configuration Duet3 Mainbord 6HC motor mapping

Scheduled Pinned Locked Moved
Firmware installation
4
20
443
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
    silverpoint
    last edited by silverpoint 3 Jul 2024, 13:45 7 Mar 2024, 13:44

    Hello everyone,

    I hope this is the right place to ask a question about the firmware and a warning I get when setting the config.g file.

    I am setting up a configuration on on the mainbord 6HC using Duet3 MB6HC DSF version 3.4.6 and reprapfirmware 3.4.6.
    In the config file I am setting all of my axis and mapping according to the manual(https://docs.duet3d.com/User_manual/Connecting_hardware/Motors_configuring). However could it be possible that there is a bug in the code, whenever I use the small letter g as a motor axis mapping in config.g using command M584 g5 and accordingly set the steps per mm and micro-stepping using commands M92 g16 and M350 g80.00 for example I get the following warning in the console. Warning: G80.0: Command is not supported and Warning: G16: Command is not supported. I do not understand why I get a warning as I am only setting the config file and not using any real g code here. Could this be a bug or is this already solved? I would like to know if it is a problem to use this small letter g in my motor mapping.

    undefined undefined 2 Replies Last reply 7 Mar 2024, 14:07 Reply Quote 0
    • undefined
      oliof @silverpoint
      last edited by oliof 3 Jul 2024, 14:08 7 Mar 2024, 14:07

      @silverpoint does it work when you put a tick in front of the g like M350 'g80.00 ?

      <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

      undefined 1 Reply Last reply 7 Mar 2024, 15:20 Reply Quote 0
      • undefined
        silverpoint @oliof
        last edited by 7 Mar 2024, 15:20

        @oliof No, that does not make a difference.

        1 Reply Last reply Reply Quote 0
        • undefined
          T3P3Tony administrators @silverpoint
          last edited by T3P3Tony 3 Jul 2024, 20:20 7 Mar 2024, 20:09

          @silverpoint did you see this point form the documentation:

          https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m584-set-drive-mapping

          Because GCode is normally case insensitive, axes that are represented by lowercase letters must be prefixed with a single quote character in GCode commands. For example, M584 'A1.2 would assign axis 'a' to driver 1.2, and G1 'A10 would move the 'a' axis to the 10mm or 10 degree position (or by 10mm or 10 degrees if in relative mode)

          So please ensure your M584 command has:

          M584 'g0.5

          Note the single quote before the lower case "g"

          And you will need to use a single quote whenever you refer to this axis.

          To that end its easier to use upper case letter if your can.

          www.duet3d.com

          1 Reply Last reply Reply Quote 0
          • undefined
            silverpoint
            last edited by 7 Mar 2024, 21:10

            @T3P3Tony Thank you for mentioning the case senitivity, but I already took this into account and did use lowercase in all of my config file.

            undefined 1 Reply Last reply 7 Mar 2024, 21:31 Reply Quote 0
            • undefined
              T3P3Tony administrators @silverpoint
              last edited by 7 Mar 2024, 21:31

              @silverpoint may I ask why?

              Please Send M584 from the console and paste what is returned here

              www.duet3d.com

              undefined 1 Reply Last reply 7 Mar 2024, 21:52 Reply Quote 0
              • undefined
                silverpoint @T3P3Tony
                last edited by silverpoint 3 Jul 2024, 22:25 7 Mar 2024, 21:52

                For the why question. I am using multiple 6HC boards (connected to mainboard via CANbus) and need to map all motors to a separate axis, because they are all different motors. I did see the useage of lowercase in the description in the configuration manual(https://docs.duet3d.com/User_manual/Connecting_hardware/Motors_configuring). So therefore I already followed that example and used lowercase letters for the mapping.

                @T3P3Tony The reply from command M584:
                Driver assignments: X12.1 Y12.2 Z12.3 a0.1 b0.0 c0.2 d0.3 e0.5 f0.4 (r)(c)A11.0 (r)(c)B11.1 (r)(c)C11.2 (r)(c)D11.3 U11.4 V11.5, 15 axes visible

                undefined 1 Reply Last reply 7 Mar 2024, 23:32 Reply Quote 0
                • undefined
                  T3P3Tony administrators @silverpoint
                  last edited by 7 Mar 2024, 23:32

                  @silverpoint said in Configuration Duet3 Mainbord 6HC motor mapping:

                  15 axes visible

                  I guess the reason "g" is not showing is that you have reached the maximum axes configurable in RRF 3.4.6 of 15.

                  https://docs.duet3d.com/User_manual/RepRapFirmware/RepRapFirmware_overview#firmware-configuration-limits

                  You will have 30 available from 3.5 onwards so you can try 3.5rc3
                  Gett the version for github:
                  https://github.com/Duet3D/RepRapFirmware/releases/tag/3.5.0-rc.3

                  then after you have upgraded to RC3, upgrade the firmware to 3.5rc3+ from here:
                  https://www.dropbox.com/scl/fo/p0136wx04h8xf6ejwdnn9/h?rlkey=efrfwyb6o5tqid11gustz3uvy&e=1&dl=0

                  as the drop box version has some bug fixes in it.

                  www.duet3d.com

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    silverpoint
                    last edited by silverpoint 3 Aug 2024, 09:43 8 Mar 2024, 09:35

                    @T3P3Tony I am performing the updates, however after updating I cannot connect anymore via the webpage to the mainboard. The mainboard has an SBC connected, so no SD cart. I still can login to the SBC via ssh. The other 6HC who are used as extension boards seem to work fine. Some 1XD extension boards I also could not update.
                    8efba32a-25a6-4bf0-a402-0d9a924d565c-Schermafbeelding 2024-03-08 102531.png
                    I am not sure if I caused the network connection problem myself because after updating there was an error that my machine name was invalid due to the use of _ in the name. So that is the only thing I have changed.

                    1f09dfff-dfef-459c-be19-743295595858-afbeelding.png

                    undefined undefined 2 Replies Last reply 8 Mar 2024, 10:40 Reply Quote 0
                    • undefined
                      T3P3Tony administrators @silverpoint
                      last edited by 8 Mar 2024, 10:40

                      @chrishamm please can you have a look at this. Not sure why its failing to find and load the 1XD firmware.

                      www.duet3d.com

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        chrishamm administrators @silverpoint
                        last edited by 8 Mar 2024, 12:10

                        @silverpoint It looks very much as if you're still on DSF/DWC 3.3.0 or older. Did you update the SBC using apt update / apt upgrade as described in the upgrade guide? It is very likely that there are some incompatibilites between RRF 3.5 and DSF/DWC 3.3. See https://docs.duet3d.com/en/User_manual/Machine_configuration/SBC_setup#shutdown-or-reboot-sbc

                        Unless you experience known bugs that are fixed by one of our dev firmware builds, it is discouraged to install firmware builds that are not provided by apt packages in SBC mode.

                        Duet software engineer

                        undefined 1 Reply Last reply 8 Mar 2024, 12:55 Reply Quote 0
                        • undefined
                          silverpoint @chrishamm
                          last edited by silverpoint 3 Aug 2024, 13:55 8 Mar 2024, 12:55

                          @chrishamm I managed to replicate the same error on a single test board I still have. It looks like I can install the version 3.5.0 rc3 but not the rc3+ versions @T3P3Tony provided earlier. So I get to the point where the version 3.5.0 rc3 is fully installed, however afterwards during the startup of the DSF/DWC in the webpage there comes a moment where the connection is lost.

                          Step 1. Start with a fresh Duet3 image 3.4.6 on the SBC
                          Step 2. Upgrade using the the commands on https://docs.duet3d.com/User_manual/Machine_configuration/DSF_Other for the unstable installation (version 3.5.0).
                          Step 3. The installation is completed and version 3.5.0 rc3 is installed.
                          Step 4. Initially I get a connection to the board however after +-1 minute the connection fails and cannot be restored. It gives the error message: "Connection lost, attempting to reconnect". Whenever the connection is lost, it is never restored.

                          @chrishamm I manage to resolve the network connection issue, by totally emptying my config.g and return only the bare minimum commands.

                          undefined 2 Replies Last reply 8 Mar 2024, 15:32 Reply Quote 0
                          • undefined
                            chrishamm administrators @silverpoint
                            last edited by 8 Mar 2024, 15:32

                            @silverpoint Please share the full config.g that lets you reproduce the problem. I suspect you're hitting a buffer limit.

                            Duet software engineer

                            undefined 1 Reply Last reply 8 Mar 2024, 16:54 Reply Quote 0
                            • undefined
                              silverpoint @chrishamm
                              last edited by 8 Mar 2024, 16:54

                              @chrishamm I reinstalled everything again for the production board (not the testboard). Now the network seems to be working again properly, don't ask me why. However I stil have the same error as before when using the command for the motor with name "g" / 'g . It gives the errors at startup: Warning: G500.0: Command is not supported and Warning: G6000.0: Command is not supported, etc. So basically every time the motor mapping 'g is used it looks like it it not processing the commands.

                              @T3P3Tony Now using the command M584 on version 3.5.0 rc3+ I get the following output.
                              M584
                              Driver assignments: X12.1 Y12.2 Z12.3 a0.1 b0.0 c0.2 d0.3 e0.5 f0.4 (r)(c)A11.0 (r)(c)B11.1 (r)(c)C11.2 (r)(c)D11.3 U11.4 V11.5 W12.0, 21 axes visible.

                              I should get 22 axes visible. So I suppose this means the 'g axes is not configured?
                              @T3P3Tony You mentioned 30 axes in v3.5.0. At the moment I use ABCDUVWXYZabcdefghijkl for the mapping. Which letters are still available?

                              undefined 1 Reply Last reply 8 Mar 2024, 17:21 Reply Quote 0
                              • undefined
                                T3P3Tony administrators @silverpoint
                                last edited by 8 Mar 2024, 17:21

                                @silverpoint from the docs:

                                U, V, W, A, B, Cnnn Driver number(s) for additional axes U, V, W, A, B and C (UVW available in RepRapFirmware 1.16 and later; UVWABC available in RepRapFirmware 1.19 and later; UVWABCD available in RepRapFirmware 3.0 and later; UVWABCDabcdefghijkl available in RepRapFirmware 3.3 and later; additionally mnopqrstuvwxyz are available in RepRapFirmware 3.5 and later on Duet 3 MB6HC and MB6XD only).

                                so i would try skipping g and using n

                                www.duet3d.com

                                undefined 1 Reply Last reply 8 Mar 2024, 17:25 Reply Quote 0
                                • undefined
                                  T3P3Tony administrators @T3P3Tony
                                  last edited by 8 Mar 2024, 17:25

                                  @silverpoint also. i just tested various m commands with a "'g" axis and they worked. which commands are failing for you?

                                  08/03/2024, 17:24:55 M201 'g8000
                                  08/03/2024, 17:24:48 M92 'g80
                                  08/03/2024, 17:24:40 M350 'g16

                                  www.duet3d.com

                                  undefined 1 Reply Last reply 8 Mar 2024, 17:35 Reply Quote 0
                                  • undefined
                                    T3P3Tony administrators @T3P3Tony
                                    last edited by 8 Mar 2024, 17:35

                                    I should add i tested this in stand alone mode. I will now test in SBC mode

                                    www.duet3d.com

                                    undefined 1 Reply Last reply 8 Mar 2024, 17:38 Reply Quote 0
                                    • undefined
                                      T3P3Tony administrators @T3P3Tony
                                      last edited by 8 Mar 2024, 17:38

                                      @chrishamm i can confirm this is an issue in SBC mode:

                                      baf46fc2-263d-45e1-8d1b-b0be0b512079-image.png

                                      www.duet3d.com

                                      undefined 1 Reply Last reply 8 Mar 2024, 17:50 Reply Quote 0
                                      • undefined
                                        T3P3Tony administrators @T3P3Tony
                                        last edited by 8 Mar 2024, 17:50

                                        @silverpoint Ok this has been confirmed as an issue with SBC mode and we will fix it as soon as possible next week and post back here once that's done.

                                        www.duet3d.com

                                        1 Reply Last reply Reply Quote 0
                                        • undefined
                                          chrishamm administrators @silverpoint
                                          last edited by 8 Mar 2024, 17:56

                                          @silverpoint In the meantime please share your config.g because I don't think DCS should fail to connect to RRF even if DSF cannot handle certain axis letters yet. You can email it to christian@duet3d.com as well if you don't want to make it public.

                                          Duet software engineer

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