Contract/Offline programming.

[[Cl...]]

I'd like to ask a few questions about this subject. What I currently do (my process for writing Calypso programs off-line).

I simply create the measurement plan off-line, transfer it to the live machine, assign the correct stylus there and off we go.

Then run it slowly feature by feature to check for collisions. working out the kinks. This works fine for me. I'd like to know

how other do this. Do you go through the entire process creating styli from scratch, running it in simulation with crash detection on, etc.

[[Ri...]]

I use crash detection all the time. You have to get used to setting the speed down to a low range. (See image Planner Speed Setting).

If it's too high, it misses too much.

I strictly use SSC files, and these are always the build to be used on the live CMM.

Basically, I create turn-key programs, which almost always need some tweaking when you go live.

Fixturing, Probe builds, Program, setup instructions, etc.

Once live, I run MSA's which is where I typically find out what needs fine-tuned.

The MSR 2.0 build is typical of a full turn-key system I recently completed. The very upper rack is for XXT probes, it's a custom design.

MSR 2.0-600_12.pdf

Edited January 3

[[Cl...]]

Thanks Rick. Like I said, I'm curious as to how other programmers do this. By MSA, do you mean just a type-1? Thats our minimum internal requirement. Some customers require a full type-2. We have on out three Conturas, three O-inspects just about every conceivable stylus configuration that would be needed. So, I really don't need to create new styli.

[[Ri...]]

MSA in general, depends on what the customer wants.

[[Ma...]]

I build the whole process and bring it into the customer. If I do collision detection then I know I’m 95% there. Just adjust for the fixture setup if they have a dedicated fixture. If I can design the fixture I do that in Solidworks. So my customers get: a program, a stylus build sheet (and what to order if they don’t have it), and a fixture build sheet.

[[Ro...]]

For my last 2 jobs I sit at all offline seat and program. I would go to the CMM computer and export every stylus system to a network drive and import them into my offline seat, then I have an exact copy of whatever they have.

For crash detection, well I just trust my programming method for that. I had a certain way I went around a part that in my mind made sense, and minimized crashes, as long as I didn't skip any steps in my "final audit".

If you're dealing with a customer, ask them for their probe files. 

[[Ma...]]

There are some considerations when programming for a customer, which I was prompted with Roberto’s reply. One, is you have written your program to run in Feature List, and man you worked hard on getting optimization and zero crashes. Then the customer, which you told to run in Feature List runs in Characteristic List. That in itself is no big deal but when they tell you your 20 minute program took 50 minutes to run, because of stylus system changes 🙄
 

I always put the Characteristic report in a certain manner for multiple print pages. I create groups for the page # and sub groups for the main view, section views, etc… This helps in 2 ways: (unless the print is bubbled)

1) makes sure I measured every feature even if I can’t or shouldn’t measure it with the CMM it puts eyes on the entire drawing and if the customer wants information I can speak to that.

2) helps the customer find everything easily 

 

[[Cl...]]

Thanks for all the helpful information, guys.

[[Ma...]]

Clarke, you need anything just let me know. I'd be glad to help.