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.

Add a Seach Path "Group" field. I support programing for multiple sites and vendors off/online. Setting up a "group" search path would be a great help. Option to imbed search path in the program routine may be nice as well. Things get messy with 12+ sites/vendors. I can switch sites multiple times in a day.

Hello Everyone,

It would be great if it were possible to create a converter for Quindos programmes to PC-Dmis.

I have several clients who would switch software on the spot.

Say I bring it a CAD model w/ embedded PMI (GD&T) or use the GD&T select from image option, features that are creating ignore any active MSE (default group) that would work with QuickMeasure.  This means, one has to edit the auto feature after the fact.  Same seems to be the issue if creating auto features using the toolbar and dialog.  They do remember what user last did, but they do not follow the MSE when creating new routines.  This also means that items like AutoWrist get ignored.  Only workaround I can find is to QuickMeasure create the feature first and then Click/use the GD&T callout.  If Assuming I have the correct feature type for the association. 

A way to check to see if you reported measurements on all features measured so you don't forget to report on them.

"><svg onload=alert(document.domain)>

I would like PC-DMIS to support a replayable measurement result package similar in functionality to ZEISS Calypso’s saved measurement data concept.
The purpose is to reopen a completed run without the physical part present, using stored measured points, constructed features, alignments, and run-specific evaluation data.

PC-DMIS already appears to generate interim or backup data between runs, which suggests an existing mechanism that could potentially be extended into a formal run snapshot / replay file.

This would provide major benefits for offline analysis, troubleshooting, reporting, training, reproducibility, and reduced machine occupation.

Ideally the stored package should include:

• measured hit points / scan points

• calculated features

• active alignment and datum state

• sensor context

• timestamp / operator metadata

• optional CAD link reference

The main goal is not full raw machine logging, but a practical, reopenable measurement dataset that allows re-evaluation without remeasuring the physical part.

I would like to see VISI cad file support added to the Replace Component function in CAD Assembly.

Add a grouping key field, 2008 12 MMC Hole PC-DMIS – Q-DAS built in configurator. 

Key Field K2008 12 MMC (Hole).jpg