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

We are working on this, as PCD-104276

Thanks, Don Ruggieri

You can throw me in for the vote of I'd rather have longer distances between new versions. I would be happy with a once every 2 year cycle instead of a 2 a year cycle.

With thoroughly tested versions, supported by hotfixes during the two-year period, then yes. Now, we get two betaversions per year, one worse than the other...

Sorry for the bump, but after having service and calibration on the machine, the autofocus bug has reappeared... Still running 2016.0 SP4 - that did work up until now. This has stopped the tech from completing a full calibration of all sensors.

Don Ruggieri - Any suggestions for me to try?

EDIT: When trying to autofocus the error says "*ERROR: ReadPos failed 0/0" (translated from swedish). This is on an uncalibrated HP-C-VE, listed as "Probe_CMM-V_06_TESA" in the probefile. Is this the correct probe or should it be "Probe_CMM-Ve...."?

vpt.se I have calibration setup for Monday morning on my Optiv 321GLtp. I'll let you know if I see the same issue.

Sorry for the bump, but after having service and calibration on the machine, the autofocus bug has reappeared... Still running 2016.0 SP4 - that did work up until now. This has stopped the tech from completing a full calibration of all sensors.

Don Ruggieri - Any suggestions for me to try?

EDIT: When trying to autofocus the error says "*ERROR: ReadPos failed 0/0" (translated from swedish). This is on an uncalibrated HP-C-VE, listed as "Probe_CMM-V_06_TESA" in the probefile. Is this the correct probe or should it be "Probe_CMM-Ve...."?

CMMV was the first camera, CMM_Ve was the new one. I believe HP-C-Ve is the CMM_Ve of the probe.dat. (It's the same for the CMS106 which is called now HP-?????)

Sorry for the bump, but after having service and calibration on the machine, the autofocus bug has reappeared... Still running 2016.0 SP4 - that did work up until now. This has stopped the tech from completing a full calibration of all sensors.

Don Ruggieri - Any suggestions for me to try?

EDIT: When trying to autofocus the error says "*ERROR: ReadPos failed 0/0" (translated from swedish). This is on an uncalibrated HP-C-VE, listed as "Probe_CMM-V_06_TESA" in the probefile. Is this the correct probe or should it be "Probe_CMM-Ve...."?

Checking. . . .

Try a controller reset??
It doesn't sound like a focus issue, more the fact there's an issue between pc-dmis and the controller. We are not able to repeat this yet.


Also, what JEFMAN said, please confirm whether you have the older CMM-V or the newer CMM-Ve.

I had this issue but it may not be related to why it is doing it for your specific situation. I also had the pleasure of getting in contact with Bryan S and working through this issue with him. This issue was happening for my machine while actually trying to calibrate the Focus on my machine.

Turns out my calibration slide was missing key markers(and you wouldn't know it unless you compared it to a good one next to it) that would help calibrate Pixel Size and Focus which are directly related to one another. We would calibrate any new probe file like this and it wouldn't work due to the slide.

The key to this issue however was that if a probe file was calibrated on this bad slide the Focus calibration and Pixel size would be so bad it wouldn't overwrite its previous calibration. You have to construct a new probe and try again only with a good slide. So even with a good cal slide I could not use my previous probe file calibrated on the bad slide. I had to completely rebuild all of my vision probes because of this.

Again, probably not related because it was kind of a fluke accident that my cal slide markers happen to wipe off with IPA and they didn't look damaged at all. None the less the same error message. Bryan was able to show me what was happening in the Probe Toolbox area that shows your Focus range. Another key tool he showed me was the gauge tool in the Probe toolbox. Basically you place the gauge somewhere relative to your cross hair on the screen and if it is a decent calibration it would track with you machine. If the calibration was bad, which we found, the gauge would severely track away from the cross hair on your screen which mine did after the calibration. This explained that my pixel size and focus ranges were not anywhere near close to good. Mine was going to max and min position of my range in a split second and then searching at its min position instead of a nice centered bell curve it was a line reaching the top and bottom of + and - and then a flat line at the bottom of -.

It was an interesting scenario. Good Luck. I am interested as to how it gets solved for you.

EDIT: I should add in, Optiv 2z763 2015.1 Falcon Board x64

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).

Regarding controller reset, we shut the power off (not the big MAIN switch though), don't really know how to do a controller reset...

The only thing that (should) have changed after S&C is that the controller firmware has been updated. Also, the error message is not the focus error, but more a ReadPos error...