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
Once you get the probe built (as far as components, etc) you can add all of the angles your programs use by clicking the Global Used button. Be warned, this can take a while if you have hundreds of programs.
seach for "listfiles", on this forum. it's a macro-enabled excel file that will search all your prg routines for loadprobe and tip commands, reporting each probe used on each routine, and each angle as well.
you need to rename the file suffix and will need to link the macro to a pcdmis directory for library terms. the post should have all you need detailed on it.
I know it doesn't help now, but I always keep copies of the probe files on our server. That way, if something happens, I can retrieve the server copies, calibrate them, and not lose too much time.
It was way better than building everything from scratch.
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.
So I wouldn't call it a fix but I installed the 2023.1 update and after a restart the connection error hasn't popped up again...yet. I did have a TCP/IP connect error this morning when trying to execute a routine it just froze at 0%. That too went away with a restart. My first check was to check the controller plugs and reset the controller. I verified the correct port settings and ensured that I'm plugged into the motherboard and not the network card. I also have backed up all my probe files onto the server so I should never have to rebuild the prob files again. I'll post up again if I find any other issues.
On a side note when calibrating my master tip last night, I noticed the probe selection tab was scrolling through all the tips I have in the directory when the calibration was ending. I didn't find anything effected by this, but I've never seen that in V2019
I would stick to "Mark Used", global used will open every program it has access to and if you have large programs with a lot of angles this can tie your PC up for several hours.
