When using trace fields to collect operator input in the beginning of routines I feel like we are missing some functionality.

I would like the option to reset trace field values when a routine is started. Today trace fields will remember the last entered value and display it when running a program. This gives operators the option to start the program without updating input values.

For example: I have a part with serial number requirements. When running the first part the operator will enter “S/N 1”. When running the second part the trace field will remember and display this value. If the operator isn’t paying attention they have the ability to start the program without updating the value.

Having the option to reset trace field values and using the “mandatory” setting would stop this mistake from happening and force operators to update values on every run.

That said having trace fields remember the last entered value is also important so I would like the option to choose if values are remembered or not.

M-Cosmos/Geopak (Mitutoyo) can measure a point on a circular path. This is useful in certain situations when rough aligning a round part or when the rotation of a radial feature is not necessarily clocked to other features on the part.

See this forum post for more details/examples...

PC-DMIS forum "How to search for point radially or using circular moves"

Here is the example from M-Cosmos/Geopak help file...

During programming, it is convenient to hide the elements using the 'Hide all elements' function.

Then, when creating dimensions, you can select the elements to be measured by choosing “Show all elements”.

However, it would be useful to have the option to prevent certain elements, such as manual or automatic alignment elements, from appearing again.

The Geometric Tolerance windows are able to self-filter as you type in feature names, which I appreciate because it speeds up the dimensioning process.

Though the Location, Angle, and Distance commands - they still behave like legacy, although they are also still widely used.

The search function on these is cumbersome - why not update it to behave like the Geometric Tolerance search list?

Like title.

I would really like to have the toolbar/user configuration files (toolbar.dat, gbarstate.dat, et al.) to something user readable.

Like XML or JSON. When we "move" the old configuration files between versions/upgrades sometimes they end up with duplicate menu items, sometimes missing a menu item...

Today, there isn't a possibility for the user to add/edit the .dat files. This is possible with XML/JSON so the user can "see" if there is a menu item missing/duplicate. The only thing left to do is to delete the files and start over with setting up the GUI in PC-DMIS, which I find quite cumbersome.

When using multi monitor ALL windows within the PCDMIS software should respect available desktop work space and not be allowed to appear off screen, also there is a bug in 2025.1.112.0 where defining the "main display" causes Auto feature window to appear off screen depending on the display chosen.

ability to send tip data (name & date/time they were calibrated) to the report

It would be good to be able to measure hits along the flats of a round-ended slot, instead of being restricted to the radii on the ends of the slot.