"Failed to detect a focus position for feature <featurename>"

What can cause this?

Tried
- new probe files
- different Z-heights
- different lightning
- different backgrounds
- different surfaces

I can visually "see" that it does focus very well, during the autofocus phase - however, it does not seem to "lock" or "detect" this...
CMM-V (HP-C-VE) in 2016.0 SP1.

Ideas?

NeilRyan

Parents

bfire85 over 8 years ago

It is true that it was reported in the technical preview. We were not able to repeat it at the time, and apparently neither was Bfire85 apparently, based on this post in the T/P forum

I was unable to repeat it in a later build than what I had at the time it showed up. I would like to assume that all builds are archived so if when we saw this arise in Build #851, Hexagon can try replicating in that build. But they didn't try that build, they tried to problem solve the issue in a later build, which the problem didn't show up in that one. If all previous builds are scrapped once a new one is released, maybe the revision process needs to be reformated to archive previous builds.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

bfire85 over 8 years ago

It is true that it was reported in the technical preview. We were not able to repeat it at the time, and apparently neither was Bfire85 apparently, based on this post in the T/P forum

I was unable to repeat it in a later build than what I had at the time it showed up. I would like to assume that all builds are archived so if when we saw this arise in Build #851, Hexagon can try replicating in that build. But they didn't try that build, they tried to problem solve the issue in a later build, which the problem didn't show up in that one. If all previous builds are scrapped once a new one is released, maybe the revision process needs to be reformated to archive previous builds.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

No Data