The approach vector when auto scanning cones is incorrect. The approach should be at a tangent to the cone angle this results in the incorrect contact point when the probe touches the cone, the error is equal to the sine of the angle of the cone multiplied by the probe radius

Hi,

It would be great if the Construct (point,line etc) windows work just like the auto feature windows.

Idea1

In case of auto Feature you can hide or show the measurement properties .

Personaly I like to see everything in auto feature but the ">>" button is good idea.

It would be great if the "<<" button appear in "construct ..." window too and the users can be hide the red area:

Idea2

If you work too many elements maybe helpfully if you see not just 7elements. 

In auto feature window you can modify the size of window if you can drag the left bottom corner.

It would be great if it works in the Construct ... windows and increases the size of the window to more elements than 7.

When use quick features and with the Flexible Measurement Strategy (FMS) Wizard opened, add the ability that , the user can drag the hits pathline mannually to a position to define where PC-DMIS takes the hits.

At this moment there is a possibility that you forget you checked the 'Don't as me again' checkbox, and leave a collegae (or yourself) with the possibility to make unwanted recalculations without noticing.

When you make that it only applies for this session (until the program closes) you can make the chance of this error/mistake a bit smaller.

I would like to see parameter sets added as a parameter of the PROBEDATA function. I currently use a log file (.csv) to track the calibration of parameter sets of probe tips for different programs. 

Currently, one can use the date and time data in a probe file for a particular tip to get information on the last calibration date/time, but there is nothing like that for parameter sets.

As of version 2019, the legacy Optimize Path tool has been removed, and the new Optimize Path (formerly "Preview" as opposed to "Legacy") chokes on MOVE/CLEARPLANE commands. Since clearplane moves can be controlled in the Edit window they are much more versatile than the clearance cube, and for flat parts they are much more efficient than Auto Insert Moves. It should not be hard to make the Optimize Path tool work with clearance planes - please do so!

When measuring a cylinder from the outside, a pin, with avoidance on, the probe approaches the center of the cylinder before moving to the first measure point on the outside of the cylinder. This is not a problem unless the center of the cylinder is outside the part and the probe attempts to plunge through the part wall. Please consider changing the routine to apply the avoidance to above the first measured point or add a toggle to allow the user to turn on that option. 

For example, in vision, you save lighting settings to percentages you want. I would like to have a setting where I can pick a lighting that I want on with a preset variable. Like Bottom Light = V999. Then the programmer can assign the variable at the top of the program.

So instead of it saying    "Bottom Light=<off, 100, on>" it would say "Bottom Light=<off,V999, on>"

Instead of having to manually type this for every feature, it will hold the value as a variable rather than a number. This could potentially solve all lighting issues going forward and make it super easy for a programmer to update/change programs if needed. And if possible

Ad a drop down menu in the construct feature window to select what kind of feature you want to construct. 

This makes constructing different feature's easier, and faster.

The function i'm looking for is already in place with the auto feature window, here you could start with a vector point, and then select the drop down menu to change to cylinder.