Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. Tags
    3. touch
    Log in to post
    • All categories
    • CCS86undefined

      Probe Accuracy Test Macro [Issues]

      General Discussion
      • probe probing bltouch touch accuracy offset rrf3 maestro • • CCS86
      6
      0
      Votes
      6
      Posts
      773
      Views

      CCS86undefined

      @dc42 said in Probe Accuracy Test Macro [Issues]:

      @CCS86 said in Probe Accuracy Test Macro [Issues]:

      @dc42: Does it sound like a bug for the probe offset to be applied over and over on repeated G30 P3 X0 Y180 Z-99999 F2000 calls?

      That doesn't sound right. Please post the complete macro file you are running, and your config.g file, and tell us which firmware version you are running.

      I was originally on 3.0, and now on 3.01-RC4

      Unfortunately, I did not save the macro before modifying it. That is my fault.

      I did find one error in my code, in asking it to probe at X0, when my probe has a +12mm offset. I feel like the firmware should catch this more gracefully though. It appears that it ignores the endstop switch and the X0 minimum designation, and tries to aggressively get the probe to X0 anyway, which hard crashes into the machine limit and jumps the belts.

      Also, it appears that I can't probe more than 32 points before I am "out of range"

      f5cb5f29-c4cd-481d-8a66-404810d82659-image.png

    • CR3Dundefined

      Communication timeout with Repetier Server

      Duet Hardware and wiring
      • duet maestro duet wifi communication timeout repetier server touch console buffer reset • • CR3D
      6
      0
      Votes
      6
      Posts
      890
      Views

      dc42undefined

      You have some other problems. Twice there is the sequence:

      es after '''S''', expected 3
      Done!
      Response while disconnected:

      The first line is probably part of an error message from the Duet, but Repetier has chopped off the first part. I've no idea about "Done!" but I think that's from Repetier, not the Duet. After that, Repetier seems to think it shouldn't be connected and is surprised to see a response.