Today I got this error message..... cannot find framegrabber (or something like that... I KNOW!! should have written down the exact error) Anyway, figured I'd reboot everything and it would go away. Well, it didn't.
Now, none of the PC-DMIS installs will open. Bam! immediate crash and almost as annoying??... the send error to hexagon/crash window pops up around 10-15 times in intervals of a few seconds. Never seen anything like it.
Oh, and after the first reboot the first try to open the Demon .... I got a TCP/IP error. I called in the IT guy, but that got me nowhere. I'd swear this machine is possessed!
The computer had Falcon/Eagle IDS driver installed (was showing in add/remove programs) Thought I would re-install it, but wanted your guys advice first. It's a Win 7 64bit box, and 2015.1(sp10), 2016(sp9) 2017M1(sp6) and 2017R2(sp2). I've looked through all our documentation that previous guy left and all I can figure is that it's a 10x zoom camera with settings (in live view) of .65x to 6.5x.
Any help is most appreciated!
Thanks for the reply Barry.... so here's what I got:
Installed the Falcon driver --- old one was v4.61.1.0 --- new one is v4.61.2 (from Wilcox FTP site) Quadro K620 old driver (1|10|17) is now latest from Nvidia site (9|16|17)
Was able to at least get 2017R1 sp6 to open... but of course with an error:
Framegrabber initialization error - File not found so the Demon opens, but no initialize, no live view... nada.
Also, when I close out the Demon I get:
Check the network cable that connects the PC to the Optiv. I used to get the framegrabber error along with a few others and it would shut down pcdmis on my optiv. It turns out the the clip on the cable was broken and it wasn't seated all the way in the PC. I just got another cable from IT and everything worked.
On my way to check right now.....
well, all cables were OK. But then a very Demon moment!... on about the 5th try to install the Falcon driver.... voila!! the card was recognized. Go figure. (i
was also getting 'falcon_64.dll' not found) Maybe time for a new SSD or memory upgrade. At any rate, it's now running the calibration routines, so hopefully problem solved.
Thx guys for your assistance!