hexagon logo

XSTATS11.tmp

I thought this would be nice for the first thread here. Any PCDMIS part program I have that saves stats I put this at the begining of. It looks for and deletes the xstats11.tmp file when executed. This avoids the way of doing it manually which is usually right after things screw up.

V1 =FILE/EXISTS,C:\PCDMISW\Xstats11.tmp
IF/V1==1
FILE/DELETE,C:\PCDMISW\Xstats11.tmp
END_IF/


Craig
Parents
  • Yes I force an update after every inspection routine. I'd hate the thought of loosing 30+ pieces like you said. Not updating after each routine is like Russian Roulette. You might be fine but I am certainly not going to take a chance on it. I update it without the message box that asks if it is ok to update, again this goes back to my attitude of having the operator do it. My situation is not the same as yours. Here the CMMs are on the shop floor and the machinists load their parts and run them.

    Craig

    Craig
Reply
  • Yes I force an update after every inspection routine. I'd hate the thought of loosing 30+ pieces like you said. Not updating after each routine is like Russian Roulette. You might be fine but I am certainly not going to take a chance on it. I update it without the message box that asks if it is ok to update, again this goes back to my attitude of having the operator do it. My situation is not the same as yours. Here the CMMs are on the shop floor and the machinists load their parts and run them.

    Craig

    Craig
Children
No Data