Adaptive circle scan strategy on autocircle stalls after measuring.

[louisd]

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

[JEFMAN]

As usual, I don't use scan strategy in autofetaures, I prefer basic scns.
In your case, I think I would try a classical BF scan (even if it's a autocircle / scan strategy), and after only construct a fixed rad circle...
Not sure it helps, but I woult do it like this...

[vpt.se]

That stall happens on every autocircle (I think it is calculating the circle) here, which may take some time depending on the amount of points. I am sure that this algorithm can be optimized though.

[Jakep379]

I've had similar issues using auto features with lots of scan points. Depending on the points it would pause after the scan for a few before continuing. Reducing the amount of points stopped this. How long did u wait before you cancelled the execution?

[AndersI]

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.

Are you using clearplane? Try turning that off, and insert ordinary MOVE points instead.

[KIRBSTER269]

It won't make you feel any better, but this has happened to me a time or 2, It was like it a had an incurable disease, skipping it, program ran fine. recreating didn't change anything, it would do the same. I start a brand new program start from scratch, with same CAD, same setup same process and it would work. Its like once it gets that hiccup, holding your breath or drinking water won't stop it. I will say the adaptive scans are fantastic, but when they go wrong, they go wrong. Your not alone louisd I had made a topic awhile back about the auto line scan. and what it was doing.

https://www.pcdmisforum.com/forum/pc-dmis-enterprise-metrology-software/pc-dmis-for-cmms/449996-adaptive-scan-lines-2018r1

[Datrax_101]

I have same issue on 2019R2. Adaptive circle scan on auto-circle, max_insc, 29 points combined. After scan is done, probe does the avoidance move and thats it.. Outsmarting this by linear closed scan works OK, but its uncomfortable... For the record - 2017R2 worked fine in this case..