hexagon logo
Register Sign in
  • Replies 41 replies
  • Subscribers 221 subscribers
  • Views 1055 views
  • Users 0 members are here
Options
Related

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

vpt.se
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?

Parents
  • .............. I saw this in an earlier build in Technical Preview (there is a thread on it) and it has come back.

    Let's sprinkle this with the fact that reported this very same error during the 2016 TP. .


    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


    Update: Build #866 works with calibration on my end. At the time of error, Hexagon tested calibration with build #854 and it worked.


    It was not a case of the issue getting fixed and then breaking again. It is just not one of those that is not easy to pinpoint. We do test for this sort of issue, but as already reported, it is not always evident. Regardless, we are focused (no pun intended) on this now. Once we understand the logic behind it, we will work to make sure it does not re-appear.


Reply
  • .............. I saw this in an earlier build in Technical Preview (there is a thread on it) and it has come back.

    Let's sprinkle this with the fact that reported this very same error during the 2016 TP. .


    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


    Update: Build #866 works with calibration on my end. At the time of error, Hexagon tested calibration with build #854 and it worked.


    It was not a case of the issue getting fixed and then breaking again. It is just not one of those that is not easy to pinpoint. We do test for this sort of issue, but as already reported, it is not always evident. Regardless, we are focused (no pun intended) on this now. Once we understand the logic behind it, we will work to make sure it does not re-appear.


Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement