Do you use an auto-calibration procedure that could be missing a tip angle after resetting the probe tips?
Does a special project take place at 1 of the 2 locations?
Is someone manually switching probing due to lack of rack slots?
Is there a user who has the ability to add move/points inadvertently which is resulting in a 'crash'?
ive seen this happen before. 1) running program from a server 2) recalling an alignment from autocal and defined alignment being skipped 3) try re establishing the alignment first to repopulate the alignments ie. re lvl plane, line, point to there features again.
after a crash are you running the path lines/collision detection to see what is happening?
are you able to correct the problem and then save the correction as the new master for that particular machine?
Are both machines running the same version of the software? I ask because I had a machine running 2011 MR1 in a lights out cell. Had a program that had run fine for years. We upgraded to 2022 and migrated the program. Then the problems started. It would run 24 parts without issue and then just crash. (Probe ram into part). Nothing in the code to explain what was happening and it was every 24 parts like clockwork. Also it was always in the same spot in the routine. At the point of the crash an incremental move was being executed. I deleted the incremental moved and utilized a move point and haven't had a problem since.
Same controllers?
Does it happen at a move point, move incremental? What's it supposed to be doing. Is it in random areas of the program, or the same spot?
