The Gerber format is a standard ASCII format file structure and uses X, Y, Z and I, J, K information that enables data exchange between CAD (development) and CAM (production). It is primarily used in electronic CAD programs (EDA – Electronic Design Automation) to output layout data for printed circuit boards.

We are frequently confronted with this format and here we have a competitive disadvantage compared to providers who can read this format into their measurement software without further external conversion.

It would therefore be desirable to integrate a corresponding import interface into PC-DMIS.

Many times we have 25 to 100 x's size and location callouts for pattern of holes. It would be nice to have PC-DMIS be able to output Min/Max GeoTol values without hard coded variable arrays.

As a PC-DMIS User I would like to have the possibility to enlarge the size of Annotation Points created out of Surface colormaps or Pointcloud colormaps. Sometimes it is very hard to read the value inside of Annotation Points, because they are just too small. Sometimes it is hard to read because you do not have a nice contrast between the Type and the background color. In this case it would be nice if I could change the color of the type.

While in Graphic Window the Annotations are good to read, it may be  more difficult in Reports, etc.

Sometimes TED from drawing not fit with model.

It was easy to edit this if necessary on Xact / Geometric Tolerance field.

Unfortunately strange decision to disable this feature in 2020R2....

When using loops, anything inside (such as features, dimensions, etc.) must be explicitly typed and named with the array number of the loop iteration, as shown in this example:

I would like to be able to select the looped features, similar to how the Auto Cylinder Concentric Scan has individual circles that can be selected. This could be based on the loop number parameters, or perhaps the loop would need to be executed to create those looped features?

Change the "Close" menu option to "Save and Quit".

This would be much more clear in what is happening.

Idea spawned from the user forum, recently from this discussion:

https://www.pcdmisforum.com/forum/pc-dmis-enterprise-metrology-software/pc-dmis-for-cmms/449143-how-to-check-all-around

The longing for a function like this has been around for a long while. Basically what it should do is to create a second vectorpoint based on the vector from the first auto vectorpoint and place that second vectorpoint on the CAD surface that the first vectorpoints vector will intersect/hit. If you don't have CAD, the possibility to control the distance between the points must exist for it to be useful without CAD.

Example of using the function when measuring a groove:

(1) The function should use a "simple" auto vectorpoint as start where we place the vectorpoint at our intended position

(2) The vector of this vectorpoint is used to find the closest CAD surface along the points vector

(3) The new - or "mirrored" - vectorpoint is created on the CAD surface using the vector from the CAD surface

(4) This way we can create "perfectly" opposite points along the groove

This is not just applicable for grooves, but also for opposite planes where we want to create a plane out of the midpoints of the opposite planes - for this we need to be able to place the hits for the planes opposite each other. It is doable today, but very tedious and a function like this would ease the process.

Lets say we have a measured cad model with a load of points taken on it. These points are coloured black on the model.
For eg.
I need to create a plane using some existing points.
From the construction toolbox I choose the plane option and I select the relevant points I need to create the plane.
After selection of these points they still remain coloured black.
Is there a way to make the selected points a different colour, so as to make identification easier, that I have selected the correct points off the model?

Be able to use Increment Moves with Virtual Machine when executing paths and for collision detection.