2018 R1, with part CAD:
This might be a rather isolated incident, but I tried making an auto-circle with scanning strategy on.
The feature is a 0.8" radius with only 10° of functional arc segment surface.
I manually overrode scan strategy values to have 20hits per mm, scan speed of 5mm/sec and 50hits, and set the strategy to Fixed Rad, thinking it would help the accuracy of the feature.
I have 4 of these in a pattern. so I used copy/paste with pattern 3x, flipping x or Y respectively. Find Hole turned off, avoidance move turned off. everything else unaltered.
Whenever I executed the routine, after physically scanning each feature, the execution would just stall on each of the four features, with probe still contacting surface at end of scan.
There would be no error messages... Nothing, just blank info in execute drop-downs, like it was waiting for machine to finish the scan.
If I cancelled execution and CTL+U continued, the scans would measure just fine.
I tried re-associating all 4 features to each respective CAD arc segment. no change.
Finally I broke down, and worked around it, by constructing an open-segment scan with the same parameters. I had to manually flip vectors (outer radius instead of CAD generated inner radius) in order for it to work, which might have been a contributor. I then created a circle from the scan segments. No problems whatsoever, ran like a charm, and was super repeatable.
I knew PC-DMIS's scan functionality was rather clunky, but never knew how bad I really was until recent.
/rant
