Do you want to measure it now?

[[Ni...]]

Hello,

I have a problem that has been happening randomly in the past 2 months. It is not frequent, 4 times in past 2 months, but it is a big slap when it does happen.

Sometimes after calypso finishes running a program, we get this message. If we click yes, it goes back to the first feature and scans it. then the message pops back up for the next feature, we click yes then it goes to scan it and it will keep asking for every single feature until it finishes scanning the program again.
If we click no, the program stops and there is no data even though it just finished running the whole program.

Weird thing is that it happens randomly. We could be running the same program 20 times without any problems but then on the 22nd time it will run normally and at the end we get this message. So there is no way of knowing if we are going to get it or not.

Has anyone encountered this and know why it happens?

Thank You,

Capture8.PNG

[[Jo...]]

If you use a Result element , feature, or formula reference for a calculation it won't prompt you until it needs it.

[[Ja...]]

I have seen that before. We save our programs to a network. We can run a single program on two different machine. I was getting that message because we were not saving something locally. I think it was measured points but I don't remember. I have already shut down or I would figure out exactly what it was that I had to change. That might be the direction you need to look into.

[[Ni...]]

Please sign in to view this quote.

I do reference a few features to scan other features. But why does it run perfectly fine for a week and then it decides to give me that message at the end of the run? without anything changing?

[[Ni...]]

Please sign in to view this quote.

All programs are saved locally in the computer that the CMM is hooked up to. I am sharing that folder through the network though to be able to access it from laptop in the office.
What do you mean measured points were not saved locally? I am not sure how to change their default saving path.

Also, I did make a change to that program on the laptop in the office while it was open in the CMM. Could that have been the culprit? Did it glitch out because something changed while it was open? I fixed it by shutting off the computer and turning it back on. But I am sure it will happen randomly again in the future.

[[Da...]]

We also save to a network and if someone opens the program while its running it will give us the same alarm. I don't know how to prevent this from happening though.

[[Ja...]]

If you are running from a network , you want to go to extras - settings - environments - paths, and set it to "fixed directory for actual values". Set the location to the computer and not the network. My location is set to C:users-public-public documents-Zeiss-Calypso-workarea-results.

[[Am...]]

Please sign in to view this quote.

I run programs off the network and will have the same open on 2 machines and a third on my offline seat. It doesn't cause any issues to make changes while its open else where, the only thing that has caused is the changes i made end up getting overwritten by the unchanged program if someone saves it obviously to prevent that I don't allow saving without master login and that way i can save the 1 I want. If you need to run the updated program you have to close it and re-open on the ones that were open while changes were made.

[[Za...]]

If you ever get an answer from Zeiss as to why this happens can you please post. This happens to us about once a week and it has never happened to the same program twice in a row. Sometimes I just re-run the program vs. hitting enter every time.

[[Ni...]]

Just to update everyone. The programs or "Inspection" folder is saved locally in the computer. That folder is shared through the network so I can have access to it from my laptop in the office using Offline Seat.

The culprit seems to be when I have the same program opened on my office laptop and its being used on the CMM on the floor. If I make a change and save it, that message will pop up on the CMM.

Please sign in to view this quote.

This seems like a possible fix but I have yet to try.

Hope this helps anyone in the future.

[[Ri...]]

Please sign in to view this quote.

Yes - this is something that should be covered sooner with people, but the way that Calypso behaves normally is that it is reading/writing to you measurement plan as it runs. If you plan to run from a network please make a change to the default paths as listed above. This will at least allow you to run the same measurement plan across multiple machines. Still, you should not be trying to modify a measurement plan if it is open and running on a machine.

[[Ne...]]

Please sign in to view this quote.

Zeiss? I could use an answer and solution as well. It coincidentally likes to happen at the end of the day after a long program and I either have to just start the program over again or tell the operator that I'll run it the next day, which never goes over well.

[[Ch...]]

I believe Jason and Richard already posted a solution to this question.

[[No...]]

Recently I received a program from a supplier that showed this message every time. This is what caused it:
* The supplier used a looped RPS alignment that was only needed for one single characteristic (distance)
* The features used in the RPS were needed for nothing else.
* I was running it by feature list (the message did not show up when running by characteristic list)

I think this is what happened:
When the program was running by features, the elements of the RPS were not measured, because no characteristic had a direct (!) reference to them (it seems the alignment itself doesn't count as a charcteristic here). Then, after everything seemed to be complete, Calypso began to calculate the chracteristics. When it arrived at the distance, it realized it needed the RPS, which was not calculated yet because of the missing features. That was when it displayed that message - and I was clicking OK for the next 5 minutes....
I think the essential point is that the features of the RPS alignment were only indirectly referenced by the distance. Maybe Calypso only checks the nearest item in the dependency tree and doesn't detect indirect references until it really needs them?

@Nixon U: Are there any conditional loops in the program where you got this message? That might explain why it only happened from time to time.

[[Da...]]

I have seen that screen a few times as well. In my instances, the program did run everything, including the feature in question. However, it still wanted to think it needed to so it again. As I recall, I think what I came to find was that Calypso was not able to get a result on that feature for some reason. In one instance, it was a cone with a rather large angle, and very short height. Think of a round flat part with a 5° chamfer on the perimeter being measured as a cone. In that case, I had to modify my probe strategy. My system is standalone, and I only back up my file to the network, so no issues there. As mentioned, this program ran fine several times before the error started coming up. However, once I changed the strategy a little (offset the probe points from one ring to the other) the problem has never occurred since.

[[Za...]]

We have stopped pulling up programs on our offline seats (usually to get modular fixture info) before or while program is running on CMM's and we never get the alarm anymore.