hexagon logo

Clipping data points

I am very new to using Quindos, and there was definitely a steep learning curve. I am currently running an old Leitz PMM 544 that upgraded back in 2006 to include the B4 Controller, and has an LSP-S1 Probe head.

My issue that I am encountering is that at a certain angular acceleration, i am seeing data points starting to be clipped. I initially thought it could be and issue with the speed I was running the machine at, and it not being able to keep up with the data points, however that was proven to be false because I am able to run it at higher speeds using larger diameter parts. I thought that perhaps the issues was due to the centripetal force counteracting the probing force, decreasing the deflection of the stylus enough to no longer accept it as a valid point. However after watching the display, there is almost an equal or greater deflection.

Has anyone encountered this issue before, and does anyone know how to solve it?

I am also trying to find out how to export the deflection data during the scan, so that I can compare the deflection of the stylus at various speeds. So far all that I have figured out how to export is the coordinatees of the scan in X, Y, Z or Rho, Theta, Z depending on the type of coordinate system.

Lastly, I am also trying to find a setting that will allow my to change force settings or deflection settings for scanning. I have found the object that changes the actives parameters for the lower, trigger, upper, and max force settings, but to my knowledge those are for point by point probing rather than scanning.
  • please clarify further as to what version of Quindos you are using (Q6 or Q7), and commands you are using to perform the scan. I don't believe it is an 'angular acceleration issue'. Please explain what you mean by 'clipping' and how do you 'see' this? If you slow the scan down are the points still 'clipped'?

    If using Q7, the probe deflection values are automatically being sent back to Quindos, a registry setting activates DVM values out. During the measure command, you'd have to turn off the calculation to avoid the calculated vector from overwriting the DVM values. The DVM values will be stored in the U,V,W fields of the APT's.

    For Q6, you'd have to use PTODEV command to send the 'ENABLE DVMOUT' command to the controller. Again, turn off calculate in the measure to see the DVM values in the U,V,W fields of the APTs.

    The B4 has parameter sets in the INIFILE which allow one to activate different parameter sets that have different force settings. In Q7 use the command UseContrlrParSet to activate a different parameter set.


    Feel free to contact us at Hexagon for help
    Steven Wojciechowski
    401-886-2715