Off-line scanning speed calcs vs On-line

[[Ja...]]

When I write a program on my off-line station, it calculates the scanning speed for any given feature substantially lower than what the actual CMM calculates it at. Once the program is written and I put in the CMM to run, I have to go into every single feature and have it re-calculate the scanning speed. The actual CMM will scan approx. 80% faster than what the off-line station thinks it’s capable of scanning at. Obviously it’s worth taking the time to do that, but it would also save a lot of time if I didn’t have to do it all. I have the Off-line station set-up identical to the actual CMM so is there a way to get it to calculate the scanning speeds correctly?

[[Ro...]]

If you setup and load default strategies for features in your program, you can specify all that stuff as a default and edit it if it's not what you want. I never let the machine calculate scanning speeds, point density, etc. I set all that as defaults based on experience, the Zeiss cookbook, as well as other information like material type, etc. The calculated scanning speeds are almost always too fast for the accuracy I'm looking for, but that may be different for you.

[[Ja...]]

I do it that way in a similar fashion but I have rather large variances in part size (IE: small parts the size of a thumb to parts similar to large engine blocks and require a hoist to get on the CMM) so most every feature I’m changing in some way, and thus need the speeds recalced. Having to go back in after loading the program on the CMM and re-opening sometimes upwards of 300 hundred features is a real pain and eats up CMM time.

I agree with you that most of the time scanning speeds are too fast so I change the point density to force Calypso to run slower. That way I get more data and slow it down at the same time.

If you’ve got more ideas, I’m all ears.

[[Ro...]]

My suggestion would be to either have multiple different defaults you can load depending on your part sizes and tolerances or create multiple program templates with all the settings you need for different situations. I prefer the latter myself, as I can create as many templates as I want with different units, tolerances, defaults, etc. and load it all in one shot. That combined with using the paste function to copy strategies to similar features saves me a lot of time.

[[Ja...]]

Multiple templates is a good idea. I’ll have to experiment with that. I’ve started experimenting with the variable strategies thing that showed up in the last version of Calypso. That holds some promise also.