Report from partial run

[[Mi...]]

I've had an interesting request. A part is being machined on a combination Mill/Lathe, Milled features (pattern of holes) is critical, the rest are not.

With AutoRun, can I have a program run, display and print the size and position of the holes and then with no user interaction continue on to complete the rest of the program? Ideally without going back through a base alignment.

Sounds like it would be something like Mini-plans and a sequence in the autorun interface... but that's not something I'm familiar with

I could measure the holes in under 3 minutes, but the rest of the part takes almost 10. Operators could be reacting to the hole results before the program has even finished if there is a way to do this.

[[Ju...]]

Is measuring "Current Selection" available in AutoRun?

[[Ün...]]

My personal opinion is that calypso should be able to show the results here as long as you measure under the "feature" feature. It would be great if the results could be followed instantly on the screen. maybe in a bottom row, maybe in a drop-down box. Here you should see not only the green/red color but also the measurement result.

The same possibility applies to AutoRun.

[[No...]]

It would indeed be great to have such a feature, but as of now Calypso is designed to generate reports only once at the end of a run.

You can place two icons of the same measurement plan on the Autorun desk, each with different mini plans selected. But this would still mean to measure the base alignment twice, because Autorun always resets old results. To run as a sequence, just multi-select the icons in the correct order with CTRL+LMB and click Start. Or if you want to save the sequence, click the sequence button on the lower right, change the order if needed, then click the save button. When you're done, don't forget to also resave the whole Autorun desk.
To start a saved sequence, click the sequence button, load the desired sequence, click OK, then click Start.

Note that sequences are tied to the layer they're defined on and can not be defined across layers (the latter is a big drawback in my eyes).

As an alternative, if you have PCM and don't need a shiny report, you could write the results of the characteristics in question to a text file, maybe with some Excel (CSV) formatting.

[[Da...]]

Please sign in to view this quote.

Not quite true. The standard report (the one that's usually banished into the background as soon as the operator installs the software for the first time - at least I did, because it always popped up and drove me craaazy), always runs in the background. It reports characteristics as soon as all needed features for those characteristics are measured.

It's somewhat bulky, though, so not easy readable.

[[No...]]

Please sign in to view this quote.

You're right, but somehow my brain disregarded that report completely - probably for the reasons you mentioned.
I've always questioned the benefit of it since we got Calypso. It's ok for "debugging" tasks, but it would drive me nuts if I had to use it for real reporting. And doesn't it keep scrolling as long as the program's still running? I just don't like it 😜

[[Mi...]]

Please sign in to view this quote.

Hmm... a PCM controlled Excel based report. That just might be an acceptable alternative - although that would mean forcing Calypso to calculate the BFBP in the middle of the run. If nothing else it's an excuse to learn to do new things with PCM.

[[Da...]]

Please sign in to view this quote.

You underestimate the sentimental value of letting a live report print out on a very annoyingly loud matrix printer like the pros did in the Seventies. 👩‍🏫

[[No...]]

Please sign in to view this quote.

Sometimes I imagine that the guys in the programming department are just that: pros from the seventies 🤣 🤣 🤣