Often there are tools in auto features that are quite useful.  Often enough I spend time manually converting the coordinates of a measured feature into an autofeature to get the benefits it prescribes.

We can control the angles of the hits for the circle, it would be nice to independently control the angle of the sample hits

The all new Updater should be able to list all versions of Pc-Dmis that is installed on that particular computer not just the newest version

I've seen competing software that has no problem with edges I have problems with in PC°DMIS.

Whenever I'm on a vision project, I always struggle to get edge parameters correct until lots of trial.

Nearest Nominal and Matching Edge are sometimes very amazing and work quite well, but often there are program parameters and changes that are not feasible with those tools (at least not with out lots of work, meaning if I quote for the struggle I lose the work anyway).

Can we develop a plan for implementing better algorithms?  I can, and possibly the rest of the community, can submit difficult tasks to measure and submit them for review.

Change the ICON of a program in the explorer window depending on the version it is saved in.

Example:

-2018 R1 & 2 Icon would be the number 18

-2017 R1 & 2 icon would be the number 17

etc..

We have multiple customers that require different versions of PCDMIS - before we send the program we have to verify that it is in the correct format.  This would be a quick visual to verify that it has been saved correctly.

PC°Dmis has a group command.

It would be nice if it were possible to check conditions inside of the group command and then the group command would output a conditional variable.

Example:

I place all of my critical feature dimensions inside of a group command.  I then set the conditional statement for:

-any out of tolerance condition inside group = to 1

-any % of tolerance condition inside group = to -1

This condition is written to an external record (comma separated)

I can now program an external system to fetch these results and use it to control process signals i.e. stop production/quality alert (Andon Signaling) etc. 

Unfortunately, metrology software in general is riff with bugs.  - It happens -

Often, we are stuck to find them on our own with only our own attempts of validation before calling the help line.

It would be very nice and awesome if the following could happen.

-Allow users to sign a confidentiality agreement (not to expose flaws exorbitantly)

-Allow those users access to the list of known/confirmed bugs

-Open a forum to the discussion and troubleshooting of bugs and workarounds to help save time and potentially inaccuracies.

I'd like the ability to change the contents of a probe file without having to reconstruct the entire probe build. We have 15 production machines and are trying to simplify the process of changing a broken stylus. An under trained person won't know that a 4 x 67mm custom stylus is ITP part number STHM504011069.

If I could just edit the stylus names in the existing probe files in a text file format it would be much easier than having to create all new probe files.

Hi,

Many user change the open GL tesselation value to 1 -> 0,1.

It would be great some possibilities that the Probe ball and shaft tesselation also can to improve...

Thanks in advance!

Like the title.

I use measured features a lot (placing hits with mouse/joystick) especially on surfaces/planes.

I have found it quite cumbersome to delete a certain hit from the feature, as you first need to

"find" the hit - either in the command or by using the "hits" dialog for measured features:

After that, you will need to find the actual hit in the command and remove it.

Then, repeat the procedure until all the hits you want to remove are gone.

I would like to have the possibility to multi-select the points I want to remove

through the dialog shown in the image.