Machine fails to initialize

[Jacknm2]

Hi guys,

Newbie to the forum and relatively new to PC Dmis as well, I've been trained for use and programming on the Pioneer CMM but we also have an Optiv classic in our inspection that has been a paper weight until me and my Quality manager decided to have a play around with it.

We've had some limited success until recently when our IT management company wanted to update our windows 7 machines to windows 10, which is understandable since its at end of life.

However, since that update PC dmis fails to get the machine to initialize throwing up this error:

PCDMIS ERROR.jpgPCDMIS VERSION.jpg
I'm relatively new it at this and even my manager who has been doing PC DMIS for years is stumped. I thought I'd ask for some help / advice on here before we ring up Hexagon for support as it seems like a relatively easy fix in my eyes if I knew where this machine.config file is and what I need to point it at in terms of file paths.

Clicking ok pops up another window saying HSI.DLL failed to load, that is in the program file directory so its not missing.

Checking device manager I can confirm we have Com ports 1 - 5 but no com6.

I got the machine to work, move and has a green light by using a the joytest application so the machine and controller do function but there is some error between the machine and computer in regards to these config files which has me stumped.

We are running on windows 10 pro 1903 build and PC Dmis Pro 2017 R1 (see above). No idea why its still on 2017 myself since the Hexagon engineer that came to do our calibration did the pioneer machine but not this one so its technically our of cal as well.

Any help on this would be appreciated.

Jack

[vpt.se]

Are you running a 64-bit Windows 10? I know some capture cards are using 64-bit drivers... and if you are running 32-bit...

[Jacknm2]

Are you running a 64-bit Windows 10? I know some capture cards are using 64-bit drivers... and if you are running 32-bit...

We are running 64 bit windows, this was one of things I was unsure about when the IT guy came to upgrade asking if that mattered to which I googled/checked the website whether the software we were using supported 64 bit windows. The short answer was yes, but I wasn't sure if that included everything the setup required, software wise.

We were running a 64 bit version of windows 7 before the update and it was working fine then.

[Peter Fuller]

Vision systems have files that are stored in the Windows Directory used to initialize the controller. Probably lost during migration and are sitting in the windows.old folder now. You'd need to contact Tech Support to get it going again.

[Jacknm2]

Vision systems have files that are stored in the Windows Directory used to initialize the controller. Probably lost during migration and are sitting in the windows.old folder now. You'd need to contact Tech Support to get it going again.

I had a feeling I would have to resort to doing this. It was worth a shot seeing if any one had an answer. Near the end of the working day here in the UK so will give them a ring tomorrow and post back with a fix if there is one once we are sorted out .

I would go digging around in the Windows.old file but well our IT admin company is 3rd party and paranoid about security, so we don't have access to that, or they removed it. We don't even have any on site admins :/

Thanks any way guys, finally got around to making a username for the site as I've been reading it quite a lot as I've been learning.

[Peter Fuller]

Lets hope they didn't remove it.

[Matthew D. Hoedeman]

gotta ask, did you run as ADMIN the first time you executed Pcdmis after the new install?

[sealevel]

Jack,
the techs will come and calibrate, but as far as the release of Demon you got? They do not upgrade you.
As far as the Optiv problem, I know your conundrum.
One PITA is framegrabber card drivers like vpt said.. It's VERY fussy. (eagle or falcon, they both bark!) They want their favorite ones, and we had to try a few installs to finally make it happy.
Pete said it correctly (we didn't upgrade the O/S, just put in a new 'puter - same win7). those several files he mentions are critical. For our Otpiv performance 443 they were four .ini files that Optiv HAD to have. (they're named very bizarre names) tomorrow at work I'll try to post them for you....
good luck!

[Jacknm2]

Jack,
the techs will come and calibrate, but as far as the release of Demon you got? They do not upgrade you.
As far as the Optiv problem, I know your conundrum.
One PITA is framegrabber card drivers like vpt said.. It's VERY fussy. (eagle or falcon, they both bark!) They want their favorite ones, and we had to try a few installs to finally make it happy.
Pete said it correctly (we didn't upgrade the O/S, just put in a new 'puter - same win7). those several files he mentions are critical. For our Otpiv performance 443 they were four .ini files that Optiv HAD to have. (they're named very bizarre names) tomorrow at work I'll try to post them for you....
good luck!

Thanks very much for the insight guys, at least I know its not a devastatingly bad issue. I did make the techs take an image of the PC before they did their upgrade so we can revert to the back up if all else fails, I've been starting to think I know more about PC's than him as I'm always telling him what to do haha.

I did run the program as Admin after the fresh upgrade. The admin is a separate company and doesn't really know the ins and outs of PCDMIS, he wanted us, bizarrely, to log in as a server user on the machine connected to the optiv, from there the server will talk to the local PC we are logged in on which will then talk to the Optiv, I told him it wouldn't work as the machine needs to talk to the PC locally, at which point he said well we won't have server access without that. They are extremely paranoid as given the right permissions as a user I could connect to the server just fine. **Shrug**

I'll get back onto the admins today, get them on remote access to give me access to the windows.old folder and if they did remove it they will have to revert it so I can get those .ini files back if sealevel is able to find them if not maybe tech support might be able to help in that regard.

I understand now why the calibration guy only worked on upgrading the Pioneer, we paid for that one haha. We have started actually using this optiv now so I've stated, whilst costly, it might be worth getting that paid for and have them out to calibrate and upgrade the software, at least then they can trouble shoot any issues like this in the future.

I'll be honest as well im still quite relatively new at this, I've been on the pioneer for about a year now but not had any formal training as of yet, only some of the free online teaching sources, a point in the right direction from my manager and the rest is having a play and using my knowledge from programming CNC milling machines, I've got the pioneer down now, been writing programs for months on it but this optiv feels like a whole different animal haha. I know PC hardware as well building my own but the proprietary PCIe cards for the optiv are a unfamiliar to me, same goes for the drivers, but you work with what you got and this forum has been a treasure trove of information for me!

[JEFMAN]

from ftp, if it can help... :
FALCON_46105_64.zip
What is it?
Very similar to 46102, but has some bugfixes for Windows 10 support.
Supports 64 bit Windows 7, Windows 8, and Windows 10.
How to use?
Standard Install. Run FALCON_46105_64.exe
Uploaded By? Bryan Seltzer For? General Use.

ftp://ftp.wilcoxassoc.com/Hardware/V...meGrabber/IDS/

[Jacknm2]

from ftp, if it can help... :
FALCON_46105_64.zip
What is it?
Very similar to 46102, but has some bugfixes for Windows 10 support.
Supports 64 bit Windows 7, Windows 8, and Windows 10.
How to use?
Standard Install. Run FALCON_46105_64.exe
Uploaded By? Bryan Seltzer For? General Use.

ftp://ftp.wilcoxassoc.com/Hardware/V...meGrabber/IDS/

I downloaded and ran the .exe which updated fine. But this hasn't solved the error unfortunately, but thank you for the link regardless.

I'm wondering if its worth doing a fresh install of PCDMIS as a whole? Drivers as well. We don't have any programs of use at the moment so there is not much for us to lose by doing it, but I haven't actually done that before with the software. I'm not familiar how the activation works whether it be by a normal type in key or via a key installed onto the PC, is there a way to do this via downloading the correct version from the website?

[vahid32]

i had this problem i changed my windows and for it

[Peter Fuller]

I downloaded and ran the .exe which updated fine. But this hasn't solved the error unfortunately, but thank you for the link regardless.

I'm wondering if its worth doing a fresh install of PCDMIS as a whole? Drivers as well. We don't have any programs of use at the moment so there is not much for us to lose by doing it, but I haven't actually done that before with the software. I'm not familiar how the activation works whether it be by a normal type in key or via a key installed onto the PC, is there a way to do this via downloading the correct version from the website?

Reinstalling won't replace the CNC configuration files that were deleted when the operating system was upgraded. These files are specific to that machine.

[Jacknm2]

Reinstalling won't replace the CNC configuration files that were deleted when the operating system was upgraded. These files are specific to that machine.

Fair enough and thank you for the responses. So is this a case of ringing hexagon tech support then and having them link/send us the config files or sending someone out to replace them? I think the latter is more likely of course but just wanted to double check. I take it these files are some what proprietary and only installed to the PC when the machine is bought/setup?

We are actually holding off ringing them at the minute since one of the air compressors has gone down so we can't get the CMM's running any how (noticed yesterday after writing this that the optiv doesn't need it, bit of a durh moment). I think we are going to ring our tech guys first, we will just revert to the back up image until we know what .dll / .ini files are a must for the optiv, so we can create a back up of them for the future. Then contact hexagon regarding our upgrading issues. I will post the file names here as well if and when we get that done for any one else suffering this problem in the future.

Is this likely to happen to the Pioneer as well? That machine is also on windows 7 and due for them to upgrade it to Win 10, we've told them to hang fire at the minute of course as we use that pretty much 24/7.

[sealevel]

Hey Jack, sorry for the delay. Here are the file names that were CRITICAL to getting our Optive running again after replacing our old Win 7 computer with a new one w/same O/S.
It should be noted that ours is a Performance 443 Dual Z with CWS (white light sensor)
Here they are:

kmess.ini
PwrBoard.ini
ZOOM.INI
CWS.INI (if you have chromatic white light sensor)

VPU.INI
cnc.ini

the ones bold/in red am sure that those are critical. The others may or may not be there.
All files should be found in the C:\Windows directory.
Good luck!