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. |
multiple constructions using same input features
Our engineers always want 3 circle algorithms, Least Squares, Max Inscribed, Min Circumscribed. I'd like to be able to choose all 3 of these at one time, using the same set of input scans. Maybe change the selection option from a drop down list to radio buttons enabling multiple circle creations in on step.
Promt operator BEFORE changing tip angles within program
I program offline for different machines and all of the machines do not have the same probe head, so the tip rotation angles are not the same. When an operotor mistakenly opens a program on the machine that is equiped with the PROBEPH10M probe head instead of the HH-AS8-T2.5, PC-DMIS automatically switches the tip angles that are available while using the PH10M. This is a problem because even if they don't run the program, simply closing the program will save the new tip angles. File, Quit will not save it but sometimes it doesn't go down like that.
Deeper automated feature naming convention
When programming offline I would like the naming conventions to more customizable. Example...If I select to measure a diameter that is .750 then I would like PC-DMIS to automatically assign that circle to be named CIR_750_1 and the next time (whenever that may be) a circle is selected with that same nominal diameter it would come up as CIR_750_2. Since I try to program with the least amount of movements in between features (path optimization) I don't always measure all of the Ø.750's at once. Just an example...Usually I would measure the Ø.750, then the Ø.129, then the second Ø.750. So I would like PC-DMIS to automatically assign (with the help of ID Setup) the circles as CIR_750_1, CIR_129_1 and then CIR_750_2. Hope this makes sense...
cad model transparent
Hi guys
it would be nice to be able to make certain regions transparent. For example: fixture model transparent, workpiece visible
have a nice day
Add a simple PASS or FAIL Inspection Summary At The End of the Report to indicate if a part is non-conforming
In a lot of instances an operator or Inspector wants a simple classification if a part is either good or Bad. Currently we can add the code to test for any out of tolerance features and display a report label programatically but this can be complex to a user. In most cases they wish to know of the part is any good or not, by having a PASS/FAIL label the inspector / operator does not have to review the report in all its detail. For Example
Graceful default handling of Find Hole Failure
Would like to see a graceful default way to handle Find Hole failures.
For example the operator puts the probe in the approximate middle of the feature and lets PC DMIS try again and/or quick minimal manual feature measurement to temporarily reset the theoriticals. Probably would have to have a surface touch as part of the solution in case the surface isn't quite where it's expected.
Find Hole search area in the Auto Features Dialog
Add another parameter to appropriate Auto Features that sets the size of the Find Hole search area. I know it can be done other ways but having your commonly used tools right at hand makes for a good work flow.
Allow measured feature coordinates to convert to auto features
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.
Add Angle for sample hit rotation (circle)
We can control the angles of the hits for the circle, it would be nice to independently control the angle of the sample hits
More Vision Algorithms
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.
Kundesupport af UserEcho