With GeoTol, you cannot change/use other nominals than the ones that were used for the creation of the feature. This is good, but are problematic at times.

For example, I have a part where I am using one alignment to measure the entire thing (using CAD). This is not a problem if all the features on the drawing is dimensioned according to this one alignment, finetuning the nominals (in essence, rounding them off) is not a problem and I can get the dimensions to match the drawing for easy orientation report VS drawing.

Now, for a section of this print, the alignment has rotated 15° and the dimensions are according to this rotated view. In GeoTol, I will not get the drawings dimensions, but the dimensions are recalculated from the previous alignment to this 15° rotated alignment, meaning that I have no way to adjust the nominals to match the print (can't round them off). My only option here is to measure them IN the rotated alignment and adjust (finetune/round off) the nominals when measuring in order to get the correct nominals in GeoTol and subsequently, the report.

Getting my point?

Would it be possible to be able to change the nominals in the GeoTol evaluation (TP in this case) to use in the evaluation - not affecting the features noms (in whatever alignment they were created)? This would help immensely in situations like these, or are there a more elaborate way to use as workaround?

I can't use the 2021.2 version because the programs made in the 2021.2 version of PCDMIS cannot be opened with the innovation that came in the 2021.2 version. I have a lot of prepared CMM programs. Translating them all into the new version will bring a lot of workloads. I don't know why such a feature was introduced, but there is no need to conclude a software maintenance agreement. What does the software team think.?

Now if we want to calculate dimensions, we have to do it in multiple steps. Make a dimension, create variable with functions or operations, create a construction point, and assigned variable to that point, and report the point.

It will be more elegant if you add a checkbox to dimension window to enable and add some functions & operators to the dimension (the expression builder). The expression builder would be integrated into separate tab on all dimensional windows.

When you have the barcode option linked to a COM port, then it always checks if there is an input from the barcode reader. Even if you're not in the input field for Inspect. With the link to a COM port, you are always sure that the routine starts. 

Currently there is a hardware keyboard wege and sends the input from the barcode reader to the keyboard. It would be nicer if there is a software keyboard wedge. A software keyboard wege connects directly to the COM port and not the keyboard. Data from the barcode scanner is sent to the COM port and is rerouted to the keyboard buffer. This way you're sure that Inspect is always reading the input from the barcode scanner even if you're in another input field. 

We run many manifold blocks with many Hydraulic Valve Cavities and O-Ring Ports, it would be nice to have a module either with many of the standard sizes or at least where we could build up the sizes we need and then be able to save and keep these for other parts.

When evaluating the position of a plane, have the ability show the max & min value.

Basically like its done with the surface profile.

It helps to quickly see if the whole plane is offset or if there is a form or angle error. 

When I import the XYZ & feature ID for several hundred points which do not contain IJK values, I would like to automatically update the vector for all of them.  I would like to see an option to automatically update vector points without having to open each individual vector point.  

Ability to change the report dimension colors globally. 

Currently there is only the option change the active program and set the default for new programs. There is no option to globally change all reports for programs that are already created.

Add possibly two modes of error handling whenever a cell part is not fixtured correctly.

1. Advance to next cell and keep all index/counter trace fields sequenced correctly to cell.  This would be best for operator environments.

Allow only the  bad cells to then be rerun after correction maintaining trace field sequence as noted.

As they can currently select cells for execution, the trace field sequence is the the important piece.

Also, if they are running successive fixtures, allow for control of Index/counter trace inputs, stop start or override with specific cell value.

2. Create or use existing notification tools to text programmer, or set stack/message light status to raise awareness.

Allow programmer to reset poorly fixtured part and resume execution from that cell maintaining trace sequence as previously stated.