Two CMMs, programs interchangeable?

[Underspec]

Hey guys,

I am getting another CMM which is going to be identical to our current one. All our programs are fully DCC automatic and do not require the operator to do any manual alignments. We use a 1" grid surface plate where we secure fixtures in certain coordinates. Anyway, since I am getting two identical CMMs with the same grid surface plates, I am thinking that the programs can be interchangeable and that I don't have to reprogram everything on the other CMM. What do you think?

[Mike N.]

The only thing I can think of that might be different on the "identical" machines are the bolt hole patterns in the granite. If you have time I would map out where they are on the existing machine from home position without any alignment. Then do the same when your new machine comes in. You might be surprised to find they are quite a bit off from each other.

This most likely will require some thought as to how you will orientate the existing fixures on the new table due to the slight offset.

We purchased a Rayco plate to cover the entire working area of our 9128 Global and I had to send Rayco a map of the hole locations before they would build the plate to ensure it would line up square with the machine axis.

[BSchwark]

If there are some differences or offset required between the two machines? You could create a generic comment and goto statement (Machine #1 or Machine #2) to read or not read the offset, and run the programs on either machine.

BS

[Couleer]

Save external alignments of the grid plate (same name) I bet you did that already. Recall it and all should be good to go

[tking]

Save external alignments of the grid plate (same name) I bet you did that already. Recall it and all should be good to go

Agreed!

TK

[VONDY]

We have 7 different CMM's now, when we started out with 1, all of our programs were DCC, after getting the second CMM we found the CMM's home positions were different, thus we ended up coping a program and placing it into that CMM's folder, doing a machine offset at the start of the program which was in all three axises. Well it got to be messy. Now any program is written with a manual 3-2-1 ( or adequate ) alignment and then we go DCC to check the rest of the program. This way we can use one program on all 7 CMM's. Note: There are travel limit issues and maybe a few other obstacles if the machine sizes are different but it does run fairly smooth.
I like the saving of the grid plate alignment, I'm just not sure that it could apply to all setups all the time, and doesn't the CMM change it's zero point every time the machine is started and homed out?

[T Miller]

Another place I worked we did it with a read point. Place probe here on that order hit enter

[Underspec]

Wow 7 CMMs?? I think I will have to adjust each program's alignment when I run it on the new machine.

[Mike N.]

I like the saving of the grid plate alignment, I'm just not sure that it could apply to all setups all the time, and doesn't the CMM change it's zero point every time the machine is started and homed out?

I prog/run a global image and I don't find any significant change in homing the machine that amounts to an error when running any of our programs

[VONDY]

Underspec - Check your private messages

[Simon_Fuller]

We have 5 CMM's all different sizes and the way we got around this problem was to create a fixture alignment. (All our fixtures sit on a rack system). All we have to do is align one fixture that is against a hard stop and them the prog recalls that alignment.
Works a treat!!

[Paul Barriage]

It is mentioned above, somewhat briefly, to do a separate, but identically named plate alignment.This is the key.

Regardless of the differences in the machines, doing a program to align both machines to a common location on your plate, (i.e. A certain bolt hole in the table or plate) While it may be X500,Y-300 one one, and X400,Y100 on another, as long as you bring them to common in their own 'tablealign' alignment, the common origin locks it in for recall in any program.