hexagon logo
Register Sign in
  • State Not Answered
  • Replies 3 replies
  • Subscribers 19 subscribers
  • Views 1675 views
  • Users 0 members are here
Options
Related

Rotary Table issue

Anders_C

Trying to measure a cylinder using the rotary table and to create elements with the function CadGenCylCirs and scanning.
The machine behaves funny both the rotary table and the X and Y axes move at the same time.
The probe is at the same position on the part while the rotary table moves, following the rotary table around.

I have found a solution to the problem and that is to change the "Tolerances for Scanning types" in the point NCI in the NPT list from 1 to lower than 1,
then it works as it should, the rotary table rotates and the X and Y axes are still.

Is there somewhere where the parameter default value for "Tolerances for Scanning types" for CadGenCylCirs is stored, so I can put it in LDB or in GDB and avoid having to change the value every time I create new elements.
If you forget to mask the CadGenCylCirs lines in the program, the value changes back to 1 and the machine crashes

In the IPPSimulator it works even if the value is 1 on "Tolerances for Scanning types" so it's only a problem in the CMM.

Regards Anders C

Parents
  • 0

    Hello Anders, first off, please let me clarify the meaning of the "Tolerances for Scanning types" you mentioned, as randomly selecting a value is not really a good way forward. Here is an extract from the I++DME specification : 

    ScanOnCircleHint (Displacement, Form) Parameters :

    Displacement defines the maximum expected distance between the nominal circle center and the actual circle center.

    Form defines the maximum expected form deviation calculated by Gauss of the circle.

    The form is defined by the radial distance of the innermost and outermost point related to the calculated circle.

    Using the above and other information (f.I. radius, point distance…) the server can and must reduce the scanning speed to guarantee measurement accuracy if necessary.

    In the case of Quindos, the scan type (OLS / CLS) is also determined using these inputs.

    Regarding the collision etc., I will append a response in the morning.

Reply
  • 0

    Hello Anders, first off, please let me clarify the meaning of the "Tolerances for Scanning types" you mentioned, as randomly selecting a value is not really a good way forward. Here is an extract from the I++DME specification : 

    ScanOnCircleHint (Displacement, Form) Parameters :

    Displacement defines the maximum expected distance between the nominal circle center and the actual circle center.

    Form defines the maximum expected form deviation calculated by Gauss of the circle.

    The form is defined by the radial distance of the innermost and outermost point related to the calculated circle.

    Using the above and other information (f.I. radius, point distance…) the server can and must reduce the scanning speed to guarantee measurement accuracy if necessary.

    In the case of Quindos, the scan type (OLS / CLS) is also determined using these inputs.

    Regarding the collision etc., I will append a response in the morning.

Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement