Fookin last friday, I did an alignment on a fixture and ran a master part multiple of times, but I didnt like one of the move points, so I inserted a new move point. Somehow the CMM went retarded and drove the probe right into the dam table. Bent the **** out of my 3mm probe and busted the module because it was in A0B0. Has anyone else have had this happen to them? Not even a year old global s green and running 2018R2. 2nd time in a month.
There's also the resource leak effect - when (no IF involved!) PC-DMIS or any other Windows program has been running 'long enough', small resource leaks (tiny programming errors) have accumulated enough to make Windows say NO instead of returning the new memory area, file handle, window handle, whatever, that the program is asking for. What happens next depends on the code's ability to handle unexpected errors like that. Most software contains parts of code where the programmer thought "that can never happen, so no test is needed".
The result is unexpected, non-repeatable behavior, crashes, etc.
The only remedy is to regularly restart the program in question - my recommendation, both for PC-DMIS and Microsoft Word (for example) is to start each working shift with a newly started software (no need to reboot the whole computer if you're running Windows Vista or later).
There's also the resource leak effect - when (no IF involved!) PC-DMIS or any other Windows program has been running 'long enough', small resource leaks (tiny programming errors) have accumulated enough to make Windows say NO instead of returning the new memory area, file handle, window handle, whatever, that the program is asking for. What happens next depends on the code's ability to handle unexpected errors like that. Most software contains parts of code where the programmer thought "that can never happen, so no test is needed".
The result is unexpected, non-repeatable behavior, crashes, etc.
The only remedy is to regularly restart the program in question - my recommendation, both for PC-DMIS and Microsoft Word (for example) is to start each working shift with a newly started software (no need to reboot the whole computer if you're running Windows Vista or later).
