invalid reading of the measured point

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • invalid reading of the measured point

    this is the error i am getting. what does it mean and how do i fix it?

  • #2
    It's normally when you've manually loaded a styli onto an analogue (scanning) probe but haven't performed a weight balance. Can also happen after a collision. To manually perform a weight balance, press the probe enable button twice (once to disable, once to enable again). An automatic weight balance will be performed whenever you index the wrist or do a tool change from a probe rack.
    Neil Challinor
    PC-DMIS Product Owner

    T: +44 870 446 2667 (Hexagon UK office)
    E: [email protected]

    Comment


    • Kp61dude!
      Kp61dude! commented
      Editing a comment
      So that's what it is called. Now I know.

  • #3
    I tried this and it didn't fix anything. how about any other tricks?

    Comment


    • neil.challinor
      neil.challinor commented
      Editing a comment
      What's your prehit/retract value and your touchspeed? For analogue probes the touchspeed should be 2mm/sec. You also need to make sure that you calibrated with that touchspeed - the touchspeed value within the probe utilities dialogue should always be the same as the value in your programs.

    • neil.challinor
      neil.challinor commented
      Editing a comment
      For prehit and retract, make sure the probe isn't hitting the surface too soon. If your prehit is set too small and the part has a large amount of deviation the tip may already be in contact with the surface when it enters it's probing cycle. Increase the prehit & retract if that is the case.

  • #4
    .06 for the pre/hit and retract and 2mm/sec for the touchspeed.

    Comment


    • neil.challinor
      neil.challinor commented
      Editing a comment
      Try increasing your prehit - as a test, set it to a large value like 0.25 if you can (I assume you're working in inches - if not then it's definitely too small - I'd make it at least a few mm)

  • #5
    it doesn't seem like anything is working.

    Comment


    • neil.challinor
      neil.challinor commented
      Editing a comment
      Sorry to hear that. I suggest contacting your local Hexagon support.

  • #6
    Is this a scanning probe or TTP? If scanning check you optional probe parameters and be sure to have an optional probe command before the 1st load probe command in the routine.

    Comment

    Related Topics

    Collapse

    Working...
    X