Tweet
Have always heard of corrupt probe files causing way more trouble than you'd think they can... finally had my experience with that last week...
Started my machine with the wrist in the A0B0 position... last part ran the previous day runs entirely in A0B0 so it was left in that position, had the right stylus loaded already too.
Put a part on the table and loaded a well proven program that uses nothing but the same A0B0 position, only changes star tips in A0B0
When I executed this program I got the standard prompt asking if it is ok to change to T1A0B0 and being in that position already it should not even disengage the wrist just activate T1 calibration offset.
Not this time, when I hit ok on that prompt it indexed the wrist to A10B0 while pcdmis still showed me that A0B0 was active, and execution began until I hit the stop.
I tried a few shut downs and start ups and got nowhere with that... started to suspect hardware or a crash I never heard about.
Had never seen it myself but from stories about corrupt probe files I decided to delete them, rebulid the probe files and re-calibrate.
Problem was gone from that point on, no sign of recurrance and no other issues whatsoever after replacing probe files and recal. I reloaded the exact same program file that acted up and it ran as usual with no issues so the program is not the cause.
Only one guy operates that machine other than me, and I do believe him that he did not see a crash or have any sort of strange power down event or anything... can probe files really give this much trouble?
Started my machine with the wrist in the A0B0 position... last part ran the previous day runs entirely in A0B0 so it was left in that position, had the right stylus loaded already too.
Put a part on the table and loaded a well proven program that uses nothing but the same A0B0 position, only changes star tips in A0B0
When I executed this program I got the standard prompt asking if it is ok to change to T1A0B0 and being in that position already it should not even disengage the wrist just activate T1 calibration offset.
Not this time, when I hit ok on that prompt it indexed the wrist to A10B0 while pcdmis still showed me that A0B0 was active, and execution began until I hit the stop.
I tried a few shut downs and start ups and got nowhere with that... started to suspect hardware or a crash I never heard about.
Had never seen it myself but from stories about corrupt probe files I decided to delete them, rebulid the probe files and re-calibrate.
Problem was gone from that point on, no sign of recurrance and no other issues whatsoever after replacing probe files and recal. I reloaded the exact same program file that acted up and it ran as usual with no issues so the program is not the cause.
Only one guy operates that machine other than me, and I do believe him that he did not see a crash or have any sort of strange power down event or anything... can probe files really give this much trouble?
Comment