sensor did not carry out measurement with expected force...

[[Pa...]]

I understand this message is a heads up that the measured feature was not physically where Calypso was expecting to find it, but is still within the measurement envelope. It is an indication, I guess, that you may have an out-of-tolerance condition. Is the distance from nominal that triggers this message adjustable?
Paul

[[No...]]

This message appears when the passive XXT head detects a measuring force that is out of the acceptable range (too low or too high). Since this is a passive head, which means it can't actively follow a deviating geometry (like a VAST or VAST XT), all the tracking has to be done with the machine axes. But if scanning speed is too high, the axes can't follow fast enough and the measuring force may slip out of tolerance. Solution: Lower the scanning speed until the message goes away.

[[To...]]

When you qualify a passive stylus system, the "standard" setting means the stylus is qualified using .15mm or .006" deflection on the stylus. So, if you go into a circle and start scanning and the stylus cannot maintain the given deflection, usually due to bad form or location, Calypso gives you this error. On new versions of Calypso, the circle will be automatically be re-measured at a slower speed.

[[Me...]]

Tom,
Thanks for tha info about it remeasuring the feature. Does this only do it for diameters or will it also do it for free form profiles and all other features as well? When you say it will do it automatically that means that there is no PCM code or loop that needs to be added? I thouught that I have seen this in action recently with some of our programs that we are machining at different operations and have been getting questions about why the feature is being taken again and there is not a loop in them.

[[To...]]

RIght now, I'm sure it automatically does circles and I think it does cylinders however, I don't think it works on anything else. No PCM function required for the above.

[[No...]]

Note that remeasuring only happens automatically in new programs. In old programs you first have to activate it in the compatibility settings.

[[Me...]]

What do you mean by compatibility settings?

[[No...]]

That's how the menu item is called in the German version. Currently no Calypso anywhere near me. It's the dialog where you select if the behavior of certain software features is like in an older version or not.

[[To...]]

You can find Compatibility Settings under Resources. I believe the category is call Scanning Optimization

[[Lo...]]

You have to be careful. We have this option turned on and have broken probes due to us having a flip in a part program. When we add a flip we put a position point and programmable stop stating to flip the part to the last feature we want measured before the flip. The problem is with Calypso 6.2.12 if the feature needs to be re-scanned due to "sensor not carry out measurement with expected force", we get the note saying to flip the part before it goes and re-scans. This has happened 2 different times resulting in broken styli.

Does anyone know if this was addressed in 6.4 or or fixed in a patch for 6.2?

We verified this by watching the top left corner while the program is running. It tells you what is being measured. It measured "circle5", probe goes to the position point, Then tells us to flip the part, but then says something like "re measure optimization "circle 5" after you hit enter. Wouldn't be a problem if we didn't flip the part already. If the feature doesn't need to be re-scanned the program works great.

[[To...]]

If you don't want to rely on the scanning optimization, you could actually measure pre-measure the circle with points, which would adjust the location of the scanning path based on the 4 points.

Open the Circle feature, click the None button under Projection. Click "Meas. Ref" tab. Tick "Own Geometry".

When the circle gets measured, it will start by probing 4 points at the 90 deg quadrants, then go back into the hole and scan it at it's newly found location.

See attached below.

[[Te...]]

Yes you have to be careful of that. I but the stop at the beginning of the next feature because I had the same issue and also broke the stylus. So any time I but a stop in a program on the XXT I do it on the next feature.

[[No...]]

Please sign in to view this quote.

I think this is due to Calypso's object oriented nature. A feature gets evaluated only after all its strategy elements have been executed. So if your programmable stop is in the feature to be remeasured, it prompts you before it becomes aware of the problem.
So always put the stop in the next feature likeTed said.