We would like to be able to pattern around a specified feature as oppose to having to move the datum to that location, as pattern only operates around the datum.

One filter that I really wish was available for a laser-scan COP is a one that just removes all laser points within x distance of a seam in a solid model.  Trying to get a surface profile measurement of a scanned part is inevitably thrown off because the physical part has had the edges smoothed per drawing requirements, but the model had sharp edges so it shows up as an out-of-tolerance condition.

I'd love to have a filter were I can specify a distance, and then either select individual seam lines or just pick "all seams" to filter out these edge points from the COP.

A .015"/.005" break edge requirement means on a .010-profile surface all of the edges will be out of spec, and the measurement will not be an accurate representation of the part.

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.

It would be a good idea to configure PC-DMIS so that each measurement program is automatically saved in its designated folder. This improves traceability and makes it easier to retrieve previous measurement sessions for review or verification. For example, if I need to revisit a measurement I performed a few days ago, I can quickly locate the corresponding program and results.

Technically, this can be achieved by setting a default save path in PC-DMIS, either through the software preferences or by using a startup script. This ensures that all programs are stored in a structured and consistent way, reducing the risk of file misplacement or overwriting. It also supports better version control and simplifies data management, especially in multi-user environments.

This kind of functionality already exists in PolyWorks, where the software automatically organizes measurement projects into predefined folders, making it easier to manage and access historical data. Implementing a similar approach in PC-DMIS would bring significant benefits to workflow efficiency and data integrity.

add ability to AUTO CYLINDER to generate TO CIRCLES similar to TO POINTS

Is it possible to have the program list the angles that are outside the volume during collision check? Something like 

Movement T1A90B90 --> T1A0B90 [ Out on X, Ok on Y, Out on Z ] ?

I know you can have the program automatically calibrate angles for you, but I have had situations where ramming into the checking sphere with the head then rotating to an already calibrated angle was the programs way of avoiding collisions ... did it twice. Anyway, due to that, I have been manually picking the angles. The problem is I have 18 angles. I put them in an order that should theoretically have no problem with transitioning from one angle to the next but when I hit collision check, I am met with this generic message that could be more helpful. 

I would also like for it to stop marking all my angles as uncalibrated and removing my order only because collision check failed... but that's a topic for another day.

Having the ability to see the report window while the report is running or even the edit screen while the program is running in Inspect would help us determine where in the program a fault occurred.  All we can see currently (In 5.1) is the CAD, %, and pass/fail screens

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...