hexagon logo
Register Sign in
  • Replies 41 replies
  • Subscribers 221 subscribers
  • Views 936 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?

  • Shouldn't this be in the "PC-DMIS Vision" section? Anyway, I've always had focus problems with versions 2013, 2014 and 2015 when using "Full" as the focus type. Changing it to "Auto" works fine.
  • It says HP-C-VE on the can, but even if I change it to "CMM-VE" in the probefile, it can't focus (not tested in a calibration, only focus on part).



    Hi VPT !
    Did you calibrate the focus camera ?
    I believe you can't use it without a complete calibration (light, focus, offsets).
    For it, you should ave a little glass with circles and squares. The total calibration is long, but you have to do it only one or twice a year.
  • - Yup, I have that artifact and it was with that artifact the tech tried to calibrate to but it couldn't achieve focus... I think the probe in the probefile listed as "CMM-V", not "CMM-Ve" (if there is any difference between the two, probefile-wise).

    I have not tried it myself - yet.
  • - Yup, I have that artifact and it was with that artifact the tech tried to calibrate to but it couldn't achieve focus... I think the probe in the probefile listed as "CMM-V", not "CMM-Ve" (if there is any difference between the two, probefile-wise).

    I have not tried it myself - yet.

    I had both CMMV, then CMMVe, ther's a difference of size and of distance of work (not sure for this point) and a difference of image quality.
    I don't think Hexagon still sale the first one.
    One of my old posts on the vision forum was about the star stylus which is used to calibrate angles : why is it the same stylus while the cmmv are different ????????

    There are some utilities to check some parameters without pc-dmis, some wires to check, options with framegrabber, compatibility with 64bits..... (for example, falcon board can work in 64, not the matrox).
    Did you look at the ftp : ftp://ftp.wilcoxassoc.com/Hardware/Vision/ (I'm unable to add the link as a link, it adds http before ftp !!!!! Disappointed (but it seems to work after posting Slight smile
    There are some (old) informations, but always usefull !!!!!
  • Any luck with your calibration? I had Hexagon in here calibrating my Optiv 321GLtp with no problems. Running 2016.0 SP4.
  • Any luck with your calibration? I had Hexagon in here calibrating my Optiv 321GLtp with no problems. Running 2016.0 SP4.

    Haven't been able to try it out yet. Still waiting for confirmation of how to reset the controller. Will try to calibrate using the glass artifact as soon as work allows. If it doesn't work, then I'm out of ideas.


  • Haven't been able to try it out yet. Still waiting for confirmation of how to reset the controller. Will try to calibrate using the glass artifact as soon as work allows. If it doesn't work, then I'm out of ideas.

    Can someone confirm or not the ability of cmmv (e) with 64 bits versions ???????
    And did you re-installed pc-dmis after adding vision on your licence ?
  • The camera was working just fine after installation of 2016.0 SP4 (to fix the autofocus issue). Both me and my colleagues have been using the CMM-VE in 2016.0 SP4, but after the tech was finished servicing and calibrating the machine and was gonna run the probe/sensors calibration - the camera did not work (it couldn't autofocus).

    The only thing that is different is that the MANRETRACT is active in the controller and the controller has an updated firmware. Hopefully, I will be able to perform some tests (someday).
  • Didn't somebody in another thread have an issue with MANRETRACT, that when turned off, the probe worked fine?
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement