hexagon logo

Number of hits increasing on their own

We finally got our new Absolute arms, and other than the probe locking lever cutting into the web of my fingers and the beep volume being too low, they are pretty nice.
I'm wondering if anyone else has run into this scenario though:
While executing a program in PC-DMIS PRO, the point count sometimes changes on it's own so that a 4 point circle, for instance, suddenly changes to 30 points. It doesn't matter what type of feature, where the feature is in the program order, or who's running it.
We have another Absolute arm running CAD++ and do not seem to have this issue.
We're running 2010 MR3 on Dell laptops with Windows 7, 64 bit.
Just curious if anyone else has this issue.
Parents
  • We finally got our new Absolute arms, and other than the probe locking lever cutting into the web of my fingers and the beep volume being too low, they are pretty nice.
    I'm wondering if anyone else has run into this scenario though:
    While executing a program in PC-DMIS PRO, the point count sometimes changes on it's own so that a 4 point circle, for instance, suddenly changes to 30 points. It doesn't matter what type of feature, where the feature is in the program order, or who's running it.
    We have another Absolute arm running CAD++ and do not seem to have this issue.
    We're running 2010 MR3 on Dell laptops with Windows 7, 64 bit.
    Just curious if anyone else has this issue.


    I have seen the points for a circle climb when the hit button gets held down to long. It tries to scan and just starts increasing the amount of hits to be taken...ie circle1 take hit 30 of 4. Its always possible the button was sticking.
Reply
  • We finally got our new Absolute arms, and other than the probe locking lever cutting into the web of my fingers and the beep volume being too low, they are pretty nice.
    I'm wondering if anyone else has run into this scenario though:
    While executing a program in PC-DMIS PRO, the point count sometimes changes on it's own so that a 4 point circle, for instance, suddenly changes to 30 points. It doesn't matter what type of feature, where the feature is in the program order, or who's running it.
    We have another Absolute arm running CAD++ and do not seem to have this issue.
    We're running 2010 MR3 on Dell laptops with Windows 7, 64 bit.
    Just curious if anyone else has this issue.


    I have seen the points for a circle climb when the hit button gets held down to long. It tries to scan and just starts increasing the amount of hits to be taken...ie circle1 take hit 30 of 4. Its always possible the button was sticking.
Children
No Data