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

    3.3b2: Unsupported type code 13 running G32

    Scheduled Pinned Locked Moved
    Beta Firmware
    3
    9
    299
    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.
    • oliofundefined
      oliof
      last edited by

      I run 3.3b2 on a 6HC board with a 1LC toolboard in SBC mode.

      here is my bed.g:

      M290 R0 S0    ;  clear baby stepping
      M561          ;  reset all bed adjustments
      M400          ;  flush move queue
      
      if !move.axes[0].homed or !move.axes[1].homed or !move.axes[2].homed
        echo "not all axes homed, homing axes first"
        G28
      
      
      while true
        if iterations = 4
          abort "Auto calibration repeated attempts ended, final deviation", move.calibration.final.deviation ^ "mm"
        G30 P0 X-130 Y-120 Z-99999 ; probe near a leadscrew
        if result != 0
          continue
        G30 P1 X0    Y110  Z-99999 ; probe near a leadscrew
        if result != 0
          continue
        G30 P2 X95  Y-120 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors
        if result != 0
          continue
        if move.calibration.initial.deviation <= 0.02
          break
        echo "Repeating calibration because deviation is too high (" ^ move.calibration.initial.deviation ^ "mm)"
      ; end loop
      echo "Auto calibration successful, deviation", move.calibration.final.deviation ^ "mm"
      G0 X0 Y0 Z10 F7200
      ; rehome Z as the absolute height of the z plane may have shifted
      G28 Z
      
      

      It completes it's run but in between the macro output I get error messages:

      	G32
      unsupported type code 13
      Leadscrew adjustments made: 0.721 0.320 0.301, points used 3, (mean, deviation) before (0.458, 0.147) after (-0.000, 0.000)
      unsupported type code 13
      Leadscrew adjustments made: -0.016 -0.029 -0.002, points used 3, (mean, deviation) before (-0.017, 0.008) after (0.000, 0.000)
      unsupported type code 13 unsupported type code 13
      

      Here is my homeall.g which is called:

      M400                    ; wait til stuff stops
      M913 X30 Y30            ; drop motor currents to 30% 
      M201 X1000 Y1000        ; reduce acceleration on X/Y to stop false triggers
      M915 P0:1 S2 R0 F0 H400 ; both motors because corexy; Sensitivity 2, don’t take action, don’t filter, 400steps/sec
      G91                     ; set relative
      G1 Z5 F600 H2           ; clear the bed
      G1 H1 X-400 F4000       ; move left 400mm, stopping at the endstop
      G1 X120 F1200           ; move away from end
      G1 H1 Y400 F4000       ; move 400mm, stopping at the endstop
      G0 Y20 F1200            ; move away from end
      G90                     ; back to absolute positioning
      M400                    ; wait again
      M913 X100 Y100          ; motor currents back to 100%
      G0 X0 Y0 F3600          ; move to center of bed
      G1 H2 X30 Y0 F1200      ; go to first probe point
      G30                     ; home Z by probing the bed
      M201 X3000 Y3000        ; reset acceleration on X/Y
      
      
      ; Uncomment the following lines to lift Z after probing
      G91                    ; relative positioning
      G1 Z5 F480             ; lift Z relative to current position
      G90                    ; absolute positioning
      

      I only added the conditional code to bed.g recently, but before updating to 3.3b2. Running 3.3b1 I did not get the unsupported type code 13 message.

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

      1 Reply Last reply Reply Quote 0
      • oliofundefined
        oliof
        last edited by

        I am also getting this error when running G32 while the machine is homed.

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

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

          Please post your config.g file too.

          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

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

            After investigation, I can see what has happened. We will fix this in the next RRF 3.3 beta.

            PS - I think it's this line that is causing the problem:

            abort "Auto calibration repeated attempts ended, final deviation", move.calibration.final.deviation ^ "mm"
            

            because the result of the ^ operator is now represented in a different way.

            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

            oliofundefined 1 Reply Last reply Reply Quote 1
            • oliofundefined
              oliof @dc42
              last edited by

              @dc42 Interesting, since that line is never reached. So macros are completely parsed before being executed?

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

              OwenDundefined 1 Reply Last reply Reply Quote 0
              • OwenDundefined
                OwenD @oliof
                last edited by OwenD

                @oliof
                May not be related but...
                You have

                successful, deviation", move.calibration.final.deviation ^ "mm"
                

                Should be

                successful, deviation,"  ^ move.calibration.final.deviation ^ "mm"
                
                1 Reply Last reply Reply Quote 1
                • oliofundefined
                  oliof
                  last edited by

                  then the second-to-last line in the script https://duet3d.dozuki.com/Wiki/GCode_Meta_Commands#Section_Examples_of_use is wrong, because that's what I cribbed from ...

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

                  1 Reply Last reply Reply Quote 0
                  • OwenDundefined
                    OwenD
                    last edited by

                    Well as someone who can't type teh word teh, I tend not to throw stones.
                    Syntax is the bane of my existence 😂

                    1 Reply Last reply Reply Quote 0
                    • oliofundefined
                      oliof
                      last edited by

                      I am not saying you're wrong. I just don't feel qualified to say I am right either.

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

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