Automatic parametric programs

[[Mi...]]

Before I try this... I'm curious if Calypso is going to get mad at me, has anybody tried this....

I want to make 1 program that can be used to sort parts that goes through many machining steps. But for simplicity sake we'll talk about holes.

Part has a pattern of bore holes. These holes are 15mm at the rough operation, and 21+mm at the finish operation.

At some point in the program prior to measuring said holes properly, I have the idea to probe it with points and enough clearance/retrace/search distance to measure either diameter.... then using pcm that says "if diameter is in range X set nominal diameter variable to 15mm, if it's in range Y set nominal diameter variable to 21mm"

Is Calypso going to play nice with a parameter changing nominal values AFTER the program starts?

Normally I would ask a question at the start of a program, set all variables based on what the operator answers for the parametric program... but I want to try and make the CMM smart enough to set them on it's own, I have never seen anybody talk about doing that.

[[No...]]

I never tried anthything like this, but I suppose Calypso shouldn't mind - technically. If you CAN put a formula on something, then there should be no technical reason why you shouldn't be allowed to do so and modify it to your liking with PCM.

Of course there may arise a LOGICAL problem. My expectation is Calypso will use whatever nominal value is there when it evaluates a feature or characteristic. But since there is more than one occasion when that is happening (e.g. "live" red/green marking during a run by chracteristic order, report generation at the end of a run vs. default protocol running in the background, red/green marking at the end of an Autorun program etc.) there may be inconsistencies if you change a nominal between two of these events.
And if you base another variable or formula on the value of a parametrized nominal, which may possibly control the travel path of the machine directly or indirectly, you could of course run into bad troubles if you change it at the wrong time.

[[Ka...]]

I used something like that multiple times. Works without any problems even in patterns (next nominal in relation to previous actual)

[[Kh...]]

Should be doable. Put PCM code on Post setting on feature side to determine what is your nominal value, after that put parameterize to nominal field on Characteristic side. it should work.

[[Ri...]]

Calypso will do what you want and most likely a lot more.

I inherited a set of programs for several families of parts, these use Excel for variable definitions, dimensions, patterns, etc and para files that are developed on the fly reading in from the Excel file.

Many years ago, a company made an interface (parameter.exe) to launch programs. This needed to be updated for new methods, so I re-wrote it in VB.net with a very similar interface. It's now named slightly different, the company I am at now owns the code so it can be updated anytime.

There are 5 parametric programs that handle approximately 50 plus parts in all. At the start of the CMM run, all dimensions in features and characteristics are fully updated.