Jump to content

Machine alarms out at certain location on table


---
 Share

Recommended Posts

After upgrading and older machine with hardware fit, and new tower to the latest version of calypso my cmm alarms out at certain points of travel.

It will redlight at whenever it travels in a +X direction at about 320mm and does the same thing when traveling -Y at about 120mm from home position. I can greenlight it back then continue, but whenever it crosses those points from that direction it will stop again.

It gives a status alarm message of: "349 Machine position outside CAA data field"

After the hardware upgrade we still used the old computer with older calypso5.6 for a few days with no problems but now with the new computer with fresh software this is happening, so I assume it is a cmm setting I need to set right. Oddly, I have one other cmm that I did the identical process, but that one turned out just fine.
Link to comment
Share on other sites

I'm not certain about that error, but in the past when I've had a machine behave like that it's because of a dirty scale (most likely a fingerprint).

Call hardware support, and they can walk you through checking each scale, and proper cleaning procedures.

Hopefully that's all your of you issue.
Link to comment
Share on other sites

Please sign in to view this quote.

You can clean the scales, but there is care to take when doing it. Like the type of cleaning solution you do, and how aggressive you are with the cleaning.

The scales are glued on, so there's not much holding it.
Link to comment
Share on other sites

Please sign in to view this quote.

Did you transfer all of the old data when setting up the new PC hardware?
I'm not entirely certain about this, as answers from other techs vary, but I once asked a tech who was doing the annual maintenance, where the corrected CAA data goes. To me the most logical place would be the controller, which is basically true. But that tech told me that there are also CAA files stored in the Calypso config. So if you should have forgotten to copy that data over, it might explain the error.
If that's not the problem, my first guess would have also been the scales or some lag in the drives. There are also some PCB boards in the controller (possibly A/D converters), one for each axis. Some time back when our retrofitted MC550 had problems with the drives switching off sporadically, they exchanged these boards. I can't tell whether this was helpful (at least it was to Zeiss in a monetary way 😃 ) because it happens so infrequently.
Link to comment
Share on other sites

Please sign in to view this quote.

Old machines store the CAA files on the local PC, but "newer" machines all store the CAA files on the controller.
Link to comment
Share on other sites

Please sign in to view this quote.

Thank you.

None of the setting were copied over from the previous computer. I decided to start over with a "clean slate" during the setup, but it was explained that we should be able to do a simple swap of the tower and be good to go. I don't know which files exactly we should have copied over for the config if we did.

I hadn't tried swapping out the controller for the new one that zeiss provided since we already had the same model, BP26 controller on the cmm (albeit it was an older version), but since you said the newer ones stored the CAA on the controller, I did the exchange. Unfortunately it still has the same issue.
Link to comment
Share on other sites

By controller, we mean the one either on the back of the machine, or off to the side. You are referring to the joystick box - that can be swapped out with no issues.
Link to comment
Share on other sites

The attached pdf file was sent to us by Zeiss to assist in moving critical machine information when upgrading or swapping out computers. Hope it helps you. 333_2aee7de86da131aac448cd3fe13c8063.pdf
Greg K.
Link to comment
Share on other sites

 Share

×
×
  • Create New...