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

    Content of bed.g?

    Scheduled Pinned Locked Moved
    IR Height Sensor
    4
    8
    3.0k
    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.
    • peirofundefined
      peirof
      last edited by

      Hi,

      i have installed Mini Ir Height Sensor… think all works, but calibration at the half, send a error message, and stops.

      This message:

      [[language]]
         "Error: Z probe already triggered before probing move startedMacro file IN Up.g not found."
      
      

      Maybe the problem, is the content of bed.g, i have the same, when i have instaled BlTouch….

      Someone can post his bed.g file for compare?

      In this moment, i am using this:

      [[language]]
      ; bed.g
      ; called to perform automatic delta calibration via G32
      ;
      ; generated by RepRapFirmware Configuration Tool on Mon May 22 2017 22:56:20 GMT-0400 (Eastern Daylight Time)
      G28
      
      ; Clear any bed transform
      M561
      
      ; Probe the bed at 6 peripheral and 0 halfway points, and perform 3-factor auto compensation
      ; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
      G28 ; home all
      G91 ; relative mode
      G1 Z15 F200 ; move Z 4mm for clearance
      G90 ;absolute mode
      
      M98 BLT PIN Down.g
      ; M401 _ In lieu of macro - call GCode for deploy probe
      
      G29 ; run auto bed mesh levl
      
      M98 BLT PIN Up.g
      ;M402 _In lieu of macro - call GCode to retract probe
      
      G1 X10 Y10 F5000
      
      

      Thanks

      1 Reply Last reply Reply Quote 0
      • fulgundefined
        fulg
        last edited by

        Don't use spaces in your macro filenames… I believe this is the problem.

        Cheers,
        Ben.

        VORON V2 CoreXY + Duet3 Mini5+ Ethernet v1.0 with Mini2+ expansion, VORON V0 CoreXY + Duet2 Maestro

        1 Reply Last reply Reply Quote 0
        • fulgundefined
          fulg
          last edited by

          Also, these macros are usually called deploy.g and retract.g, and are already automatically called by M401 and M402. Since Firmware 1.19, you no longer need to call M401/M402 explicitly for G29 or G32 to work.

          VORON V2 CoreXY + Duet3 Mini5+ Ethernet v1.0 with Mini2+ expansion, VORON V0 CoreXY + Duet2 Maestro

          1 Reply Last reply Reply Quote 0
          • fulgundefined
            fulg
            last edited by

            Lastly, here is my entire bed.g:

            [c]
            M561 ; clear any existing bed transform
            G1 F500

            ; bed points are in probe space…
            G30 P0 X20 Y70 Z-99999 ; define 4 points in a clockwise direction around the bed, starting near (0,0)
            G30 P1 X20 Y280 Z-99999
            G30 P2 X280 Y280 Z-99999
            G30 P3 X280 Y70 Z-99999
            G30 P4 X150 Y150 Z-99999 S0 ; finally probe bed centre, and calculate compensation
            ;G1 X0 Y0 F5000 ; move the head to the corner (optional)
            [/c]

            (next time I should think more before pressing Submit, sorry for the multiple sequential answers!)

            VORON V2 CoreXY + Duet3 Mini5+ Ethernet v1.0 with Mini2+ expansion, VORON V0 CoreXY + Duet2 Maestro

            1 Reply Last reply Reply Quote 0
            • peirofundefined
              peirof
              last edited by

              ok,

              later try… but my probe don't need to be deployed, these lines are in bed.g, when i have instaled a BlTouch. In this moment i have a Mini IR Sensor.

              Thanks

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

                Looks like 2 different errors:

                1. Probe triggered at start of move. Perhaps the G31 P parameter is wrong, or the dive height is too low.

                2. Trying to execute a macro file that it can't find.

                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
                • Dougal1957undefined
                  Dougal1957
                  last edited by

                  and I don't see any Probe points defined.

                  1 Reply Last reply Reply Quote 0
                  • peirofundefined
                    peirof
                    last edited by

                    @dc42:

                    Looks like 2 different errors:

                    1. Probe triggered at start of move. Perhaps the, G31 P parameter is wrong, or the dive height is too low.

                    2. Trying to execute a macro file that it can't find.

                    Now works….

                    I have raised the dive height...

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