Name X

IR6 had a bug where the scanning profiles only worked in mm.

Nice workaround!

Some of the sketch functions in IMEdit should be able to accomplish what you're looking for.

The Manual Alignment dialog will move anything that is selected in the tree, including Reference Objects.

I run into that quite often. I've always chalked it up to sloppy designers. Odds are that the Y planeisn't actually zero, but 0.00052589612511", or something like that. IMINspect is rounding up to display 0.001"

I usually just turn on more decimal places in the annotations, and manually align the cad to the coordinate grid.

You need to verify which COM port the FAROArm is actually installed on via the device manager. It probably isn't COM40.

IMMerge can handle much larger datasets, and IMAlign will help clean up your cloud before meshing.  IMInspect doesn't offer as many parameters to create a nice mesh.

The real-time meshing is awesome, but you still need additional licenses just as before.

Now that I know where you're working, and have a pretty good idea of what you're working on...

We were touch probing most of those features with the FARO Sensor Probe, rather than scanning.

I would guess that either:
The cylinder is too far out of location;
or that there aren't enough data points to extract the measured value.

Are you able to manually fit a plane to the cloud?

Step by step wouldn't really work, as it's not a one-size-fits-all alignment.

However, the basic scenario would be to:
Create nominal features
Define measured features
Create Reference Points for said features
Set properties of each reference point
Perform Alignment

You can also add tolerance templates to save you additional time.

Are you trying to calculate trim edge deviations on a sheet metal part? Ifo so, comparison points would be a better option.

I understand what you want, and I've been requesting that feature fora LONG time. Currently, it doesn't work like that though.

There is a TON of reasons why a feature wouldn't extract. I'd need to see the project to effectively troubleshoot it.

That's a fine way of doing it, but there are a dozen or more reasons why a particular cmp pt wouldn't solve. Can you offer any more info about the ones that won't solve? Or perhaps upload the project somewhere? Even screenshots could help diagnose this.