Hexagon Measurement SystemsNo matter what Hexagon measurement equipment or software you use, we want to hear your ideas and suggestions on how we can improve.
Thanks for your assistance in helping us shape the future. |

elements / grouping easy to fade out
We use this program for big first samples with many elements that is reason we work with groupings. But when we will some measurements we don´t need all elements and we fade out some elements. But currently we must select a single element and than we most go in the options to fade this out.
Please make this process simple.

Implement a database with variables and tracefields which are used at all routines to get a better change management.
A lot of companies have different measurement routines which are using the same variables and tracefields. If they have for example 100 measurement routines and wants to add a additional tracefield, the have to open all 100 measurement routines and have to add the additional tracefield. This is a lot of work and needs a lot of time. It should be nice if we can simplify this process.
There are already two possibilities:
1. Export variables and tracefields as basic script and recall in measurement routine:
This option works without problems and we can use it. But the problem is here, that we have to do manual adjustments after we create the basic script. Here we have to delete some things. If you do this not very often, it is not very easy to know which parts you have to delete.
One possibility can be, if we mark the commands out of the measurement routine and generate a basic script only with the commands which are marked.
2. Recall a subroutine which includes the variables and tracefields:
Here is the problem, that we have to declare all variables and tracefields in the main routine for first.
If we do not do this, we can’t use them in the main routine.
Here could be a possibility to set a command, that the variables and tracefields of the subroutine(s) can be used in the main routine without any declaration before.
For sure a third possibility can be, that we implement a complete new function, which we can use to do this. I think this is a really good function which is useful for a lot of customer.

Print Yes/NO
hello
hello i would like the function i want a print yes or no
and that you can tell that you only get the mistakes a report with mitutoyo this is easy

turn off hits on all in edit window
To my understanding, if you want to "clean up" your edit window, you have to turn off "parameters" and "show hits" individually on every feature.
Can there be an option (Probably under the View menu) to toggle parameters and show-hits ON or OFF for all features?

Dimension the width between circles
Add the ability in the distance dimensioning to be able to report the width of an O ring groove between two circles.

Auto Surface Feature
I know I am way out there this time but please hear me out. Please add a surface type auto feature. No matter the surface I want to be able to create an adaptive scan similar to an auto plane adaptive scan feature, such as perimeter, free form, or teach path. For example, (bad example but here it is) I don't necessarily want to create a cylinder on a radius surface I want to create an auto surface feature but I don't want it to be constrained to the cylinder parameters I want it to be able to be treated the same as I would create a plane adaptive scan. Another example would be irregular surface geometry. The reasoning is I want to be able to go through a part and create auto features instead of generic scan features to report the profile of each surface. I think it could be a valuable tool. Thank you!

Pull data from auto feture sample hits
Have the ability to pull data from sample hit for constructed features.

CAD model Export
I have a program with a CAD model in it, but I do not have a model in any other CAD format (stp, igs, prt...) only .cad from PC-DMIS. I need a function to export CAD model from PC-DMIS to other formats like stp and igs.
Situation is: I have only a PC-DMIS program and I need a model because we can not find that model anywhere.

Separate Clearance Cubes = More efficient probe travel times.
When I import my 1-2-3 blocks for fixturing or whatever I bring in, I would like each of them to be able to have their own clearance cube instead of having to have a large cube encompassing the whole set up. Sometimes with larger fixtures it would definitely speed things up if the probe didn't think it had to move so far away from my part just because the constraints of the CC are limited to the overall size of my imported fixturing. And why stop there, also make it where if I don't have a fixture model I can manually set up a cube just for that single fixture piece as well.

more information in the calibration results window
Add more information to the calibration results window like: touch speed, scan speed, move speed, prehit/retract distance and so on. It would help to decide if the calibration has to be done again because of differences in these settings.
Here's an example:
Customer support service by UserEcho