Some programs may have support files like pcdmis forms, basic scripts, bitmaps, external commands, etc.  Very often, the best way to manage a program is to create a folder for it and then allow the program to reside within that folder with all its supporting files in same location.

This is because it is often impractical to have many programs in folders with all their support files intermix.

It would be nice to be able to specify whether to treat a folder as a program container that can be selected for execution.  (On main Measurement routine screen).  Bitmap association to it.

The rule would have to be that a folder name must be identical to the program name.

I know this is a complicated request.  This is how one of our customers that has 50+ CMMs has his custom interface (developed by us Hexagon) configured.

Location of programs is remote (network).

Executing measurement routine is actually a local copy of the folder and its contents.

Hey everyone,

I didn't find anything listed about this so I figured I would put it up. I use 2-3 monitors at a time when using PC-DMIS. I would like the ability to be able to place different parts of PC-DMIS on different monitors when programming and working.

Examples would be:

-Live view on separate monitor

-Report Window on separate monitor

-Edit Window on separate monitor

-CAD View on separate monitor

-Measurement tools in your own locations

-The ability to have that layout,  the size and locations of windows saved for when PC-DMIS is opened next.

Essentially a user could make their PC-DMIS interface setup how they want it when using it whether they use 1,2 or 3 monitors, they could utilize all of them if given the chance.

This sounds like it would be a hard task to change this, but I know it would make a lot of users happy. I think it would be an opportunity to keep some things loaded separately though when loading PC-DMIS and fix certain crashes when too many things are open that are not in use. This would allow users to have only the tools needed for their job open while efficiently switching from task to task and checking their work at the same time without having to find an open window somewhere while utilizing more desktop space for users who like to see more at once.

It would be nice to have PC-DMIS QDAS converter integrated inside PC DMIS, with intuitive K-Fields set-up menu and possibility to export all PC DMIS Dimension functionalities to .DFQ files

If i have to measure 10 same parts, it will be great if there is ability to edit reports from 1 to 10, even if i executed program for each. For now, it's only "View last execute report mode"

Currently PC-DMIS has a square spacer that can be set for auto planes. It would be nice if we could specify the length and width of the spacer

I like to get the actual selected and executed Miniroutine(s) by automation. A function like GetActiveMiniRoutine() on Part level can be a solution.

When measuring with the optics, it should be possible to superimpose an overlay on the live image.

Similar to a wireframe model or a DXF contour, the lines of the nominal geometries should lie over the camera image.

This allows the operator to visually compare the actual and nominal contours, just like with a projector. Furthermore, the customer wishes to carry out manual measurements in the live view between the nominal and actual contour. Such as distances, angles etc.

I'm looking to have an auto calibrate command for all probes/tips within a single routine that have been calibrated outside a specified range. With this, it would also be nice to have a way to see all used probes and tips within the routine without having to go into each probe individually and select mark used. Currently we calibrate probes by opening each probe (F9), selecting mark used and looking at the calibration dates/times. If it has been outside of 24 hours we typically calibrate only the necessary tips. I'd like a way to do this automatically, and to be able to use this command from a form.

Thanks

I think the Comment box could use some help.  I've been using PCDMIS since the 2014 version and its basically untouched in 10 years.  As an offline programmer, the comments are sometimes the only way I can communicate to the inspection operators.  

I have seen some people on here asking for Font Types and Colors, and i think that's a really great idea!

I would also like to see more ALT codes translated correctly to the comment box,   or maybe add more than the four symbols at the bottom of the Comment Text Box.  GD&T uses so many different symbols to communicate there should be a library to choose from when typing out or operator comments. 

Even as I type this out, I'm looking at the options i have to edit my text and I would love to see something similar to this woven into the comment section of PCDMIS. (see below)