Suggestion from HxGN Live  Idea Center Session

"With a Hexagon wide user account system, an award/achievement system could be added tracking usage of Hexagon software, and/or for attending HxGN Live,  or completing training courses.

Unlock achievements by trying learning new capabilities in the software, or through long usage of the same capabilities (1miilionth feature created).

Your ranking position among your peers can be shown on a worldwide leader board, and the top placed users win prizes (t-shirts, iPads, HxGN Live tickets (travel included))."

When using executing program parts by CTRL + E, PCDMIS automatically swings to the last programmed probe position from the program.

Unfortunately alsothis position is skipped by an IF / GO command.

 Here would be a safety requestion befor the swivel useful.

Hey guys,

I was thinking this morning how nice it would be to be able to specify with your jog box or even form the machine directly set move distances while programming directly online.

Example: I program a lot of thinks that are almost 2 dimensional so it is hard to fixture so we simply just change parts run a quick manual alignment however sometimes it can be tedious to go take and find those manual points but still get it close.

So if you are programming without CAD and not offline and you want the machine to move what you know to be 10mm you can have an options to move in Z+ Z- X+ X- ect. that exact amount instead of feathering the stick to where you want it given the option to change desired distant in seconds. Usually we know where we want to go in each direction we just don't know how far but we know roughly and we know which direction we want. This can make manually take points slightly more uniform as well short of going back through your code and just adjusting your coordinates.

I am not sure if this is possible with current jog boxes or windows in pc-dmis but our machine has an older style j box with no screen or anything. So a window for quick input directions in pc-dmis and or on the jog box would be awesome.

A constructed mid-point cannot be used for best-fit vector alignments because the vector is wrong, I normally get around it by constructing a generic point and calculate the average vector of the 2 points...

PNT_MID    =GENERIC/POINT,DEPENDENT,CARTESIAN,$
            NOM/XYZ,<(PNT_1.TX+PNT_2.TX)/2,(PNT_1.TY+PNT_2.TY)/2,(PNT_1.TZ+PNT_2.TZ)/2>,$
            MEAS/XYZ,<(PNT_1.X+PNT_2.X)/2,(PNT_1.Y+PNT_2.Y)/2,(PNT_1.Z+PNT_2.Z)/2>,$
            NOM/IJK,<(PNT_1.TI+PNT_2.TI)/2,(PNT_1.TJ+PNT_2.TJ)/2,(PNT_1.TK+PNT_2.TK)/2>,$
            MEAS/IJK,<(PNT_1.I+PNT_2.I)/2,(PNT_1.J+PNT_2.J)/2,(PNT_1.K+PNT_2.K)/2>

Would be useful if the mid-point worked in the same way as my genetic point.

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