Framegrabber BS

That's a good call, vpt.se - BUT as it ends up? there were probably TOO MANY entries in the cofig/ini recipe!
So, we luckily got Doug S. (senior Optiv guru/test pilot/rocket scientist etc.. ) in on this issue. And if he could have came into the cockpit with TeamViewer, hours of troubleshooting might have been reduced to minutes.

The history of the issue -(pre-Doug) IDS camera manager got into the act, and didn't like the camera manager release and firmware/drivers. OK. So we updated - I think it was from 4.90.xxx to 4.96.xxx. As the starting firmware got to installing at 96%, it crapped out. *error* Oh ok. Back to square one. Framegrabber initialization error.

Doug had us change an .ini file from 5420M.ini to camera_5420M.ini, and place it the demon root folder, then tried it in program data, and... other places!
Didn't help. Then, Doug sent us an older IDS SDK zip file. So we uninstalled the whole IDS enchilada, and installed the older package. No dice!

We then changed the file names in the C:\Windows\System32\drivers folder - two files: something like uEYE_64.SYS and uEYE_64.DLL - we changed the VERSION under properties and took off the last xxx.xx..23.0 (the .0) and xxx.xx..18.0 OK.... I'm just guessing! But... that didn't fix it either. Doug was kind of running out of ideas... not sure who mentioned it, but in the IDS camera manager, we clicked the " automatic ETH configuration" button (it became available again) see the image up at start of this thread.....and..... VIOLA! Camera back online!!!!

Obviously, Doug sending us the (new) OLDER release of the IDS SDK camera package worked. He said PC-DMIS doesn't like listening to the IDS regarding UPDATES. And? I think our employer forces new win 10 updates that satisfy themselves, but the Demon and IDS do not like! But that is out of an Optiv user's control. Strange error to start this story - but Doug is always the wiz who conjures up the solution!
THANK YOU DOUG! Hope this thread might help anyone else using an Optiv.

and P.S. if your boss will listen.... get a DUAL Z 443 Optiv - the standard Performance 443 model blows chunks for clearance in your routines.

That's a good call, vpt.se - BUT as it ends up? there were probably TOO MANY entries in the cofig/ini recipe!
So, we luckily got Doug S. (senior Optiv guru/test pilot/rocket scientist etc.. ) in on this issue. And if he could have came into the cockpit with TeamViewer, hours of troubleshooting might have been reduced to minutes.

The history of the issue -(pre-Doug) IDS camera manager got into the act, and didn't like the camera manager release and firmware/drivers. OK. So we updated - I think it was from 4.90.xxx to 4.96.xxx. As the starting firmware got to installing at 96%, it crapped out. *error* Oh ok. Back to square one. Framegrabber initialization error.

Doug had us change an .ini file from 5420M.ini to camera_5420M.ini, and place it the demon root folder, then tried it in program data, and... other places!
Didn't help. Then, Doug sent us an older IDS SDK zip file. So we uninstalled the whole IDS enchilada, and installed the older package. No dice!

We then changed the file names in the C:\Windows\System32\drivers folder - two files: something like uEYE_64.SYS and uEYE_64.DLL - we changed the VERSION under properties and took off the last xxx.xx..23.0 (the .0) and xxx.xx..18.0 OK.... I'm just guessing! But... that didn't fix it either. Doug was kind of running out of ideas... not sure who mentioned it, but in the IDS camera manager, we clicked the " automatic ETH configuration" button (it became available again) see the image up at start of this thread.....and..... VIOLA! Camera back online!!!!

Obviously, Doug sending us the (new) OLDER release of the IDS SDK camera package worked. He said PC-DMIS doesn't like listening to the IDS regarding UPDATES. And? I think our employer forces new win 10 updates that satisfy themselves, but the Demon and IDS do not like! But that is out of an Optiv user's control. Strange error to start this story - but Doug is always the wiz who conjures up the solution!
THANK YOU DOUG! Hope this thread might help anyone else using an Optiv.

and P.S. if your boss will listen.... get a DUAL Z 443 Optiv - the standard Performance 443 model blows chunks for clearance in your routines.