Long story short. Hard drive died and all data was lost. My only real issue is probe files. Does anyone know if there is a way to extract all the probe angles, names etc. from our previously existing programs?
The programs are all saved on our server, but the probe profiles were not backed up. I'm looking at having to rebuild every probe manually so any tips would be appreciated. Now running Version 2023 on a global green 7.10.07
Not sure what the issue is now but after getting a random error calibrating a probe, I am back to getting a failed to connect=0 error message upon restarting. Fixed this connect error once already and now it comes back after multiple calibrations and running several routines without issues. Anyone else have this issue with Version 2023?
First things first - check the connectivity with the controller
Assuming this is a machine with an FDC controller, open a web browser and type 100.0.0.1 and you should be taken to the FDC interface page (if it doesn't load then the issue is likely to do with the network settings on your PC, i.e. an incorrect IP address).
If it does load then check the interfac file.
We have numerous .dll files to allow PC-Dmis to work with different controllers.
In the install directory (i.e. C:\Program Files\Hexagon\PC-DMIS 2023.1 64-bit) look for a file called interfac.dll - if you can't find this then (again, assuming it's an FDC controller) find the FDC.dll file and copy it, rename the copy interfac.dll.
First things first - check the connectivity with the controller
Assuming this is a machine with an FDC controller, open a web browser and type 100.0.0.1 and you should be taken to the FDC interface page (if it doesn't load then the issue is likely to do with the network settings on your PC, i.e. an incorrect IP address).
If it does load then check the interfac file.
We have numerous .dll files to allow PC-Dmis to work with different controllers.
In the install directory (i.e. C:\Program Files\Hexagon\PC-DMIS 2023.1 64-bit) look for a file called interfac.dll - if you can't find this then (again, assuming it's an FDC controller) find the FDC.dll file and copy it, rename the copy interfac.dll.
