hexagon logo
Register Sign in
  • Replies 20 replies
  • Subscribers 15 subscribers
  • Views 598 views
  • Users 0 members are here
Options
Related

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:


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
  • i had this problem i changed my windows and for it


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


  • 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.
  • 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!





  • 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!







    This is fantastic, thank you very much and no worries about the delay, we all have to work Slight smile. I'll let you know how we get on once we get access to the directory or have reverted to the back up to retrieve them.
  • Well more fun and games with our external IT company, they want confirmation from Hexagon that these are the files that are missing..... before they do anything.

    Is it just in the C:\Windows folder? or is there any other file path they could be located in?

    They have said that they have looked in the windows.old directory and cannot find any of the files mentioned by sealevel, so they want to see "the email from hexagon stating these files are missing" which of course I cannot do nor can I confirm the files are missing as this was only an attempt to fix the issue.

    They're a bit of a joke company, will ring hexagon support on Monday and just go from there I suppose.
  • Each of the different vision system machines are different. Is this a 321? I Just updated a 321 where the CNC board wasn't compatible with W10.
  • It's an Optiv Classic 443, I'm currently out of work now for the weekend, same for the boss man haha. Won't be touching any of this until monday now, IT company being painfully difficult with us as well which doesn't help matters.
  • Okay the 443 doesn't have a CNC board it's an embedded controller. But yea you should have at least 3 of the 4 ini files if not all 4 of the ones that SeaLevel listed and they should be in C:\Windows.
  • Well more fun and games with our external IT company, they want confirmation from Hexagon that these are the files that are missing..... before they do anything........
    ......They're a bit of a joke company, will ring hexagon support on Monday and just go from there I suppose.

    I feel your pain.
    Vendor IT 'departments' and even most INTERNAL IT departments love to ride herd over anything and everything. We all understand they must keep the network secure.
    But..... they know next to nothing of what the Demon (Calypso as well) needs as far as admin rights, access, settings...etc.....kinda like they just don't want you coming into their cockpit....Rolling eyes

    Keep trying Jack!
    Obviously Peter knows his Optiv ****!!! Another one who knows is Doug Sjogren up in Rhode Island. Doug spent 3 days & many hours on remote access via teamview trouble shooting our Optiv.
    I can't say enough glorious words about him as a tech guru and really nice guy too.

    The Optiv is a real tease. It promises to do wonders in the world of metrology. I think ours is just not there yet, but we keep trying.
    Optiv is best described as a very mysterious machine from the Black Forest of Germany..... Sunglasses


© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement