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

    M98 not working as described or user error

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    6
    260
    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.
    • jsinicroundefined
      jsinicro
      last edited by

      Hi,

      Continuing on my learning, I've decided to use the concept of splitting and rejoining axis during homing I've customized my homingall.g to use the M98 command and call each individual axis to be homed nothing different on the X, and U axis these use endstops. However the Z axis seem to work a bit different with the bltouches. I have 2 tools one on the X axis and one on the U axis each tool has an associated bltouch. This is the original M584 cmd.

      M584 R0 S0 X1.0 U3.0 Y0.2:0.3 Z0.0:0.5:1:0.4 E1.1:3.1 P4
      

      this is the home all file:

      ; homeall.g
      ; called to home all axes
      ;
       M98 P"homex.g"
       M98 P"homey.g"
       M98 P"homeu.g"
       M98 P"homez.g"
       M98 P"homev.g"
       
      M18 Z                           ; disable Z motors before reassigning them
      M584 Z0.0:0.5:0.1:0.4 ; join both Z together
      M350 Z16 I1                     ; Z reassign microstepping
      M906 Z800 I30                   ; Z reassing currents (mA) and motor idle factor in per cent
      
      G90
      

      Homex, homey, homeu, homez and homev they all do as commanded, however after homingv it repeats homingz and never comes back to rejoing the Z motor mappings as defined in the homeall file. Not sure why this doesn't work.

      this is the homingv file:

      ; homev.g
      ; called to home the Z axis
      ;
      G91
      M18 Z                           ; disable Z motors before reassigning them
      M584 Z0.1:0.4                   ; Split the 2 Z towers for independent control. this will move right tower only
      M350 Z16 I1                     ; Z reassign microstepping
      M906 Z800 I30                   ; Z reassing currents (mA) and motor idle factor in per cent
      ;T0 P0                        ; Select Tool 1 and run tfree0 only to park T0
      G1 H1 X250 Y250 Z5 F6000    ; lift Z relative to current position
      G30 K0                       ; this will home and probe the left Z tower
      
      
      

      and this is the homingz file:

      ; homez.g
      ; called to home the Z axis
      ;
      ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Apr 18 2021 23:08:10 GMT-0400 (Eastern Daylight Time)
      
      ; Back to absolute positioning
      M18 Z   ; disable Z motors before reassigning them
      G91
      ;G92 Z0 ; Momentarily set Z to 0 position so tool change can be executed
      
      M584 Z0.0:0.5               ; Split the 2 Z towers for independent control. this will move left tower only
      M350 Z16 I1                 ; Z reassign microstepping
      M906 Z800 I30               ; Z reassing currents (mA) and motor idle factor in per cent
      ;T1 P1                       ; Select Tool 0 without running tfree tpre tpost
      G1 H1 U250 Y250 Z5 F6000    ; lift Z relative to current position
      G30 K1                      ; this will home and probe the left Z tower
      
      G90
      
      

      Why does it call homingz twice, because I think the homeall gets executed completely, but the second call to homez leaves the Z axis unjoined.

      jsinicroundefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
      • jsinicroundefined
        jsinicro @jsinicro
        last edited by

        @jsinicro Wow, It helped me type this, the error is in the config.g file in the

        M584 R0 S0 X1.0 U3.0 Y0.2:0.3 Z0.0:0.5:1:0.4 E1.1:3.1 P4
        

        the Z part should be Z0.0:0.5:0.1:0.4 , however the above should work as Z1:0.4 is the same as Z0.1:0.4 so I guess this is not it, but I will fix it and see if it makes any difference.

        dc42undefined 1 Reply Last reply Reply Quote 0
        • Phaedruxundefined
          Phaedrux Moderator @jsinicro
          last edited by

          @jsinicro said in M98 not working as described or user error:

                                                                                                                                                                                  M18 Z                           ; disable Z motors before reassigning them
          

          As soon as you disable a motor, it becomes unhomed. In homeall.z if it reaches the end of the file and an axis isn't yet homed it will call the associated homeing files for that axis. So you home everything, disable the Z motors and unhome Z, so it then tries to homez again for you.

          There's no need to disable the motors with M18.

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • dc42undefined
            dc42 administrators @jsinicro
            last edited by

            @jsinicro which RRF version are you using, and what are you trying to achieve splitting the Z axis?

            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

            jsinicroundefined 1 Reply Last reply Reply Quote 0
            • jsinicroundefined
              jsinicro @dc42
              last edited by

              @dc42 OK, I saw this in the Zidex config or homing files. as a way to switch axis and probably it would be used to print with 2 different filament on 2 separate axis. Yes what Phaedrux said makes sense that's probably why it calls the homez twice. Basically doing this it gets both Z towers homed using the bltouch on each tool carriage, thus switching Z axis from tower 1 to tower 2. I've been trying to use the 38.2 command to run homing on the second Z axis called V however even if the bltouch deploys and retracts once it hits the workpeace and the axis stops moving I still get an error message of homing failed. I've upgraded everything including the touch screen and boards to RRF3.3RC2 I have not tried doing any prints yet as I am still waiting for the heated bed silicon to arrive, however both extruders work filament flows pretty good, just have to tweak the flow rates motors steps and the next thing to work on is the bed leveling, one for each tool thus I should be able to switch between the two towers.

              1 Reply Last reply Reply Quote 0
              • Phaedruxundefined
                Phaedrux Moderator
                last edited by

                Could you show some photos of the printer to show how it's laid out? It's a little confusing to understand.

                Z-Bot CoreXY Build | Thingiverse Profile

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