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

    Error: G30: Z probe point index out of range

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    4
    300
    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.
    • devleonundefined
      devleon
      last edited by devleon

      Hey everyone!

      I'm trying to test the accuracy between two of my z-probes for choosing the better one, and I'm trying the script from here: https://forum.duet3d.com/topic/1291/testing-resolution-accuracy-your-results-wanted-z-probe-results

      Since the thread is locked and I don't want to dig up that thread, I'm making a new one for an issue I'm having.

      When running the 36 probes 1 point script, in which I have just modified the X and Y position (see at the end), I get the following output when the script is finished:

      11/29/2019, 1:36:15 PM	M98 P"0:/macros/Testing/Z-Probe Accuracy"
      Error: G30: Z probe point index out of range
      Error: G30: Z probe point index out of range
      Error: G30: Z probe point index out of range
      Error: G30: Z probe point index out of range
      

      Any idea what's going on? I searched for the error message here and via google, but I found nothing. Is there another way to test z-probe accuracy?

      Info: RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later

      Thanks!

      Code for the script:

      ;prob testing single point. 
      G30 P0  X178.5 Y145.5 Z-99999 F2000 
      G30 P1  X178.5 Y145.5 Z-99999 F2000 
      G30 P2  X178.5 Y145.5 Z-99999 F2000 
      G30 P3  X178.5 Y145.5 Z-99999 F2000 
      G30 P4  X178.5 Y145.5 Z-99999 F2000
      G30 P5  X178.5 Y145.5 Z-99999 F2000 
      G30 P6  X178.5 Y145.5 Z-99999 F2000 
      G30 P7  X178.5 Y145.5 Z-99999 F2000 
      G30 P8  X178.5 Y145.5 Z-99999 F2000 
      G30 P9  X178.5 Y145.5 Z-99999 F2000
      G30 P10 X178.5 Y145.5 Z-99999 F2000 
      G30 P11 X178.5 Y145.5 Z-99999 F2000 
      G30 P12 X178.5 Y145.5 Z-99999 F2000 
      G30 P13 X178.5 Y145.5 Z-99999 F2000 
      G30 P14 X178.5 Y145.5 Z-99999 F2000
      G30 P15 X178.5 Y145.5 Z-99999 F2000 
      G30 P16 X178.5 Y145.5 Z-99999 F2000 
      G30 P17 X178.5 Y145.5 Z-99999 F2000 
      G30 P18 X178.5 Y145.5 Z-99999 F2000 
      G30 P19 X178.5 Y145.5 Z-99999 F2000
      G30 P20 X178.5 Y145.5 Z-99999 F2000 
      G30 P21 X178.5 Y145.5 Z-99999 F2000 
      G30 P22 X178.5 Y145.5 Z-99999 F2000 
      G30 P23 X178.5 Y145.5 Z-99999 F2000 
      G30 P24 X178.5 Y145.5 Z-99999 F2000
      G30 P25 X178.5 Y145.5 Z-99999 F2000 
      G30 P26 X178.5 Y145.5 Z-99999 F2000 
      G30 P27 X178.5 Y145.5 Z-99999 F2000 
      G30 P28 X178.5 Y145.5 Z-99999 F2000 
      G30 P29 X178.5 Y145.5 Z-99999 F2000
      G30 P30 X178.5 Y145.5 Z-99999 F2000 
      G30 P31 X178.5 Y145.5 Z-99999 F2000 
      G30 P32 X178.5 Y145.5 Z-99999 F2000 
      G30 P33 X178.5 Y145.5 Z-99999 F2000 
      G30 P34 X178.5 Y145.5 Z-99999 F2000
      G30 P35 X178.5 Y145.5 Z-99999 F2000 S-1
      
      1 Reply Last reply Reply Quote 0
      • oliofundefined
        oliof
        last edited by

        It could be that a single coordinate can only be probed 32 times. So Remove runs 32 to 35 and try again (you will then get 0 to 31 which probably is more than enough. I tried with 3, 7, 15 points and didn't get a different result between the latter).

        <>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 1
        • dc42undefined
          dc42 administrators
          last edited by dc42

          The maximum number of G30 numbered probe points supported is 32 (P values 0 to 31).

          BTW it's useful to run tests separately with the probe points approached from the +X, -X, +Y and -Y directions, to check for certain types of backlash in the positioning system.

          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
          • devleonundefined
            devleon
            last edited by

            Thanks very much for the feedback!

            I found another script on the linked github repo: https://github.com/T3P3/GcodeMacros/blob/master/Calibration and Tuning/Diagnostics/Probe_Repeatability_test

            Works fine now, got a mean deviation of around 0.00759 mm, seems good to me!

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