Currently if you want to use any program while PC DMIS is running you take the chance of sending PC DMIS on it way simply by typing into , say even a e-mail.

Add a toggle switch that would stop PC DMIS from just continuing on without truly knowing that what is being typed is truly intended for PC DMIS.

Or just have PC DMIS recognize that another program in running and not just take keystrokes that are intended for another Program and use them in PC DMIS.

Currently we use the "H" axis as a dummy axis.

If you could add a real dummy axis to work as a place holder.

Most every pint we have has features that must be checked but can not be checked with a CMM.

A dummy axis would create a spot in the Excel out put where such info could be entered.

The best case for this would be that not only would you enter a nominal and Tol. but also letters to define something like "Caliper, Mics, SurfaceFinish...." 

Much like the current ability of reporting Just OOT features.

This would allow you to pick a single axis one you have this you could more effetely see trends/shifts in a single direction.

allow move points to be stored as polar not always x,y

Help files need to make it clear that the working plane and alignment has to match the vector you want the high point to calculate to.   

Either that or change the high point measurement routine to calculate to the entered/ CAD IJK values regardless of working plane or alignment.  This actually seems more intuitive to me.

turkce dilinde Yardım etmek index neden yok

Table Navigation Improvement

When using "Tab" inside a table after entering a value, the program does not navigate horizontally in the table.

When using "Enter"  inside a table after entering a value, the program does not navigate vertically in the table.

Entering values in tables should be seamless, allowing the user to move horizontally and vertically across the table with the "Tab" and "Enter" keys, a feature all users are used to with any traditional table program or web interface.

Example:

1. User opens the "Feature Location" window (Figure 1) in order to add a feature location to an existing feature (PLNA for this example).

2. User clicks PLNA on the left side.

3. On the bottom right of the window, user is given a tabulated selection of the parameters they need to choose to include in the feature location. User desires to change the nominal, +tol and -tol of the "X axis".

4. User would click "Nominal" column in the "X" row and enters a value of "5".

5. User presses "Tab", which moves the input selection to the +tol column. User enters a value of "0.4".

6. User presses "Tab", which moves the input selection to the -tol column. User enters a value of "0.2"

7. User presses "Enter" after entering the last value, which moves the input selection to the "Y" row and "Nominal" column.

8. User enters nominal Y value of "10".

9. User presses "Tab", which moves the input selection to the +tol column of the same row.

This feature would greatly speed up entering tabulated values for users. Everyone defaults to trying to use the "Tab" and "Enter" keys inside a table, however they are slowed down when it does not function correctly in PC-DMIS tables. Currently, pressing tab or enter after inputting a value simply refreshes the table and clears your input selection ability. The user must then re-click another cell in order to enter that value.

Note: This "tab" feature works in command mode for tables, so the implementation is half-way there. Please implement this feature in the GUI for tables, as standard users will likely be using this often.

Figure 1 - Sample picture of table being referenced above:

Long executing programs require operator intervention at time.  Most operators will monitor or look at report window to see issues early enough in a routine.  Some Measurement routines may take hour to run.  If the setup is for operator to stop because something looks odd in the report window, that cannot happen now with Inspect as the only feedback I get is percentage of execution.

For editing complex programs would be a Status window of currently active parameters such as approach path, return path, movement speed and Status Flymodi,  useful