Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Indusctive z probe error

    General Discussion
    3
    8
    71
    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.
    • Tinchus
      Tinchus last edited by

      Hi. Im having this issue after upgrading to 3.4.1 stable . Duet 3 SBC

      I have a mesh levelling routing, nothing on that start gcode has changed. As aI said the error appears sometimes in version 3.4.1 (previous version used was 3.3)

      Error: Probe was not triggered during probing move

      And also sometimes I get the error:

      Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.

      If I let the print continues, the prints Z offset is OK, perfect.

      Any ideas of what can be happening?

      My start gcode is this :

      G21
      M83
      M561 ; clear any bed transform
      G28
      T0
      G32
      G1 X5 Y5 F2000
      M400
      M141 S90
      G10 S<MAIN1 - 70>
      M116 P0 S5
      G1 X175 Y175 F2000
      G30; Home z again with probe for Z DATUM
      G29; mesh levelling
      G10 S<TEMP>
      M116 P0
      <MATL>

      Thanks in advance

      Tinchus 1 Reply Last reply Reply Quote 0
      • Tinchus
        Tinchus @Tinchus last edited by

        I have more data. The probing error happens when running bed.g

        In that file I do a side by side calibration (both Z motors are independent).

        bed.g:

        M561 ; clear any bed transform
        G28 ; home
        G1 X182 Y204 F2000
        G30
        G30 P0 X10 Y204 Z-99999 ; probe near left leadscrew
        G30 P1 X345 Y204 Z-99999 S2 ; probe near right leadscrew and calibrate 2 motors
        M400

        With version 3.3 this error was not happening. I have read documentation and I cant find anything related to a change on probing

        Stephen6309 fcwilt 2 Replies Last reply Reply Quote 0
        • Stephen6309
          Stephen6309 @Tinchus last edited by

          @tinchus Make sure you home Z before leveling, that should get rid of the warning about the Z offset.

          Here's my bed.g:

          ; bed.g
          ; called to perform automatic bed compensation via G32
          M561						; clear any bed transform
          while iterations < #move.axes & move.axes[iterations].visible
          	if !move.axes[iterations].homed
          		G28
          		break
          G28 Z						; home Z for Z0
          M290 R0 S0					;  clear baby stepping
          G30 P0 X10 Y150 Z-99999		; probe near a leadscrew, half way along Y axis
          G30 P1 X275 Y150 Z-99999 S2	; probe near a leadscrew and calibrate 2 motors
          
          
          Tinchus 1 Reply Last reply Reply Quote 0
          • fcwilt
            fcwilt @Tinchus last edited by

            @tinchus said in Indusctive z probe error:

            I have more data. The probing error happens when running bed.g

            In that file I do a side by side calibration (both Z motors are independent).

            bed.g:

            M561 ; clear any bed transform
            G28 ; home
            G1 X182 Y204 F2000
            G30
            G30 P0 X10 Y204 Z-99999 ; probe near left leadscrew
            G30 P1 X345 Y204 Z-99999 S2 ; probe near right leadscrew and calibrate 2 motors
            M400

            With version 3.3 this error was not happening. I have read documentation and I cant find anything related to a change on probing

            A couple of things.

            You should not need that M400.

            And after leveling the bed you should reset the Z=0 Datum with a single G30 at whatever location you normally use.

            Frederick

            Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1

            Tinchus 1 Reply Last reply Reply Quote 0
            • Tinchus
              Tinchus @Stephen6309 last edited by

              @stephen6309 Thank you for this. Can you explain me what these lines are for?

              while iterations < #move.axes & move.axes[iterations].visible

              if !move.axes[iterations].homed
              
              	G28
              
              	break
              

              Also, lets supose the z probe is not triggered an d I get an error, can that error be detected and add some code lines to repeat the probing?

              fcwilt Stephen6309 2 Replies Last reply Reply Quote 0
              • Tinchus
                Tinchus @fcwilt last edited by

                @fcwilt Thank you for the tip, will do it

                1 Reply Last reply Reply Quote 0
                • fcwilt
                  fcwilt @Tinchus last edited by

                  @tinchus said in Indusctive z probe error:

                  while iterations < #move.axes & move.axes[iterations].visible

                  if !move.axes[iterations].homed

                    G28
                  
                    break
                  

                  That code scans for any un-homed axis and if it finds one it does a "home all".

                  I myself don't use such code because I don't won't homing to occur as a side effect. Probing, other than homing with a probe, should not be happening unless all axes are already homed.

                  But that's just me.

                  Frederick

                  Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1

                  1 Reply Last reply Reply Quote 0
                  • Stephen6309
                    Stephen6309 @Tinchus last edited by

                    @tinchus To make sure the printer is homed. I also have this in start.g, so it shouldn't run in G32 during a print, but the G28 Z is in there, since the bed is heated up before running G32 and G29/mesh.g for a print. It also allows testing of the G32 without additional steps.

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