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

Hi vpt.se, your message box is full...

Hey fellas, thank you for your suggestions and for following the thread!

bfire85 - I have read about that too, but it isn't the culprit this time.

JEFMAN - Cleaned, hopefully it will go better next time.

I was told by our local tech that there's now a FDC firmware v11.01... Maybe with a little enhancement from V11 ?

Recap...

While I am one of the first to deal out criticism when stuff doesn't work as expected, I do acknowledge when I have received first class assistance.
None mentioned, none forgotten so I won't name any names, but a sincere and grateful thank you to everyone involved!

After a walkthrough of hardware switch settings, particular cables to particular connectors, software settings, TeamViewer session and whatnot,
the most logical reason for this problem is that a (loose) connection must have been the reason for the error (to the control boxes in the desk).

We got the CMM-VE working and it wasn't PC-DMIS' fault and a firmware up/downgrade wasn't needed.

Thanks for the update vpt.se! I hate it when it's the simple things. All the time/money wasted. Glad to see your service was superior and you are up and running again!

Recap...

While I am one of the first to deal out criticism when stuff doesn't work as expected, I do acknowledge when I have received first class assistance.
None mentioned, none forgotten so I won't name any names, but a sincere and grateful thank you to everyone involved!

After a walkthrough of hardware switch settings, particular cables to particular connectors, software settings, TeamViewer session and whatnot,
the most logical reason for this problem is that a (loose) connection must have been the reason for the error (to the control boxes in the desk).

We got the CMM-VE working and it wasn't PC-DMIS' fault and a firmware up/downgrade wasn't needed.

Is it really that simple?
I had the same problem today and I could not solve it.
The customer is crazy) To date, the CMM configuration is next: DEA Scirocco, b3clc, PH10MQ, SP600,TP200,TP2,CMS106,CMM-VE (Falcon64 4.61),IS1-2,ACR3, SCR200, PC-DMIS 2017R2 64
I came to set up CMS106,CMM-VE, IS1-2, TP200, ACR3, SCR200.
It remains only to solve the problem with calibration CMM-VE.
I used to have a lot of experience with TESA VISIO (200,300, MAN,DCC), Optive 321,322, but did not have such problems.

When trying to calibrate pixel size and focus the error says "*ERROR: ReadPos failed 0/0" . I tryed to sensifocus in live view and i get same error. But! If i press sensifocus on more sharp (clear, big) element I haven't error. I tryed to change focus range, light.
I have the feeling that the optics do not have enough permission to find the focus on the center of sqware of Hexagon slide. Also maybe I have a poor-quality slide.
As for connecting the wires in the table...One of the wires that connects from CMM-Ve to Output Channel IS1-2 really barely keeps. I have the feeling that it is made smaller than the connector.

if you have fresh information about this problem help me, please.
Thank you in advance!

Sorry for not re-visiting this, the actual error still occured even after the TeamViewer session and remote support assistance. But, the error WAS solved during the testing we did at that time. When I dissected the steps taken I found that after choosing "English" as language in PC-DMIS - the focus error disappeared. I tried this the next time the error popped up and lo and behold - the error did not occur when using "English" as language (we usually run swedish language here).

So, if you are facing this problem AND you are running PC-DMIS in a language OTHER than English, change it to English and try again.

We use Russian lang. Tomorrow I'll try your advice. But I think that problem in connecting wires. Today I сonnected CMM-V without IS1-2 and was able to calibrate the optics.

Updated to 2019 R1 SP5 and got hit with this "ReadPos Failed" error again.

This is NOT due to some cables being loose and I don't think it was the reason last time either...

Updated to 2019 R1 SP5 and got hit with this "ReadPos Failed" error again.

This is NOT due to some cables being loose and I don't think it was the reason last time either...

Sorry bud but SP5 works fine on my system. Can you work backwards and try the same scenario in SP4?