Message of moved pallet system

[[Ka...]]

Dear Experts,

CALYPSO 7.0.20 / 7.4.04

Sometimes we need to change the protocol head parameters of a pallet. To do that we call via context menu of the pallet icon the pallet parameter menu. Then we open the protocol head parameter and change the "actual part ident" number as an example. Next step is to adopt (1) the changes and click OK (2) . Now we are back in the palet parameter menu and we click OK (3) to make the change active.

Surprisingly, a message appears that the pallet system and the workpiece system differs now 😮

I don't understand what this is about or is this a great feature that I don't know about?

Best Regards
Karsten

3.PNG2.PNG1.PNG

[[Ma...]]

Hi Karsten,

first of all - this message tells you, that your pallet alignment has changed from previous declaration ( meaning after opening this first window ).

Best what you can do is not using this first window - you can access parameter window from context menu in better way.

Use: context menu -> Define Measurement Plan Parameters

This will skip window with alignments, so no changes to that.

BUT YOU SHOULD SOLVE THAT! You should have one program for pallet system and run it when you replace your fixture.
Don't use actual measuring program to do measuring and pallet position at same time - this will lead to these types of warnings.

[[No...]]

Very important: If you use the same Autorun file and programs on multiple machines, be careful when and where you edit in that first window. Because the difference between the alignments is stored inside the Autorun file, based on the situation on the particular machine where it was last edited. If next time you edit it on another machine, Calypso compares the stored values with what is stored on the other machine and may change the values accordingly. This is especially dangerous if you also have an offline seat where the alignments are not "real". You may end up with wrong offsets and possibly a crash during the next measurment.

[[Ka...]]

Hi Martin, Hi Norbert

Thank you so much for your input!

So this means, we need for every CMM it´s local autorun.arn file and therefore a local configuration task if we need to change something as long as we define a pallet inside 😕
Do we need a local autorun.arn file too if we simply calling programs with autorun?

We use a network drive to save/open the CALYPSO programmes. All CMMs therefore open the same programme and so does Autorun. The actual data are local of course. This works very well but I am now afraid that this no longer works with Autorun?

Best Regards
Karsten

[[No...]]

Please sign in to view this quote.

We use exactly the same setup - WITH Autorun. What we don't do is run the same program on different machines at the same time. Not because this would be a bad idea (I don't know for sure if it is), but just because we have only one fixture per part.
But we run the same programs on all machines and we do it with Autorun. This shouldn't pose a problem even with multiple fixtures as long as they are identical. Small offset deviations between machines usually do no harm. Only be careful in case you're editing the *.arn on an offline seat.

[[Ka...]]

Hi Norbert,

That calms down immensely 😃

Unfortunately we need to run the same programm ( and therefore parts ) at the same time on different CMM´s in different locations. The reason is that production and QA run simultaneously. This means that the protocol header data will be overwritten and need to be corrected at start time of the program.

Since we do not have a PiWeb Sbs/enterprise/cloud available all measurement data are local and can´t be merged to a single db-File 😭 So we copy once a night all changed db-files to our file server in seperate directories. One for each CMM. To open these files using PiWeb plus you need to copy the db-file(s) again to a local machine. Well this is a big hack... bit it works so far 😕

Best Regards
Karsten