It would be helpful if PC-DMIS had a Debugging tool for offline programming. This would allow ability to step through programs one command at a time to troubleshoot flow control. It would also be nice to see the values of assigned variables along the way. 

In offline mode, the "Move to point" function automatically moves the probe to the coordinates (x=0, y=0, z=0).

This makes it impossible to use the "Read position" option that was previously very useful when in need to read the position of the probe after having measured an element. 

I hope I've been clear enough, my english skills are not the greatest.

Create two auto featurs  and evaluation  all individual points. The desired result would be the extreme dimensions.

it was randomly generated to some features and in some programs. it make me afraid that at some points i dont trust my measurement at all. 

Save settings as the default settings for different CMMs.

Possibility of calling the default settings at the beginning of the measurement program (One measurement program for different machines)

I'd like to see separate dialog boxes for scanning: one for TTP scanning and one for Analog. The way it is right now, we see all the settings for both in the same dialog: some applicable, some not. This tends to get a bit confusing.

For example, when setting up to do a Freeform scan with an analog head, I can still change density and number of hits in the Execution tab (then press calculate), but this has no affect on the scan since these settings are controlled in the Settings tab. Or, I could set the direction technique to "variable" when it should be set to "nullfiltier" for an analog scan.

Another option could be to gray out non-applicable settings.

I've noticed that the latest training material (2018) on scanning also lumps these two scan types together. It would be nice to have these totally separated in the curriculum since they are two very different animals.

When changing the name of a auto feature PC-DMIS automaticaly pops up asking if you would like make this new name the nominal name for the next featuer. I would like to submit the idea of replicating this when reporting position. If we have 100 diameters of the same ballooned feature it would be great to have the name become nominal so we only have to click on the feature then click create instead of having to retype or feature name every time. Thank you

I want to create a program that I can calibrate multiple probes add in angles and re-prove my probes.

If probes were cleaned or moved for some reason I just want to start a program touch off on my Qualification Tool then watch it go.  

Would it be possible to implement a plausibility check for PC-DMIS?
Controllable, I imagine it that way: You can define the plausibility limit in a program-related setting, e.g. deviation >10% of the tolerance is not plausible.
Ideally, this message can be sent automatically to the internal measuring program Support.

Background:
If the measuring program is started by a user, for example via the operator starter and a faulty measurement takes place, an error message should appear at the end of the measuring program or directly during evaluation that the plausibility limit has been reached.