new to PCM in Calypso

[[An...]]

I'm trying to have two different tolerances for the same feature based on the operation the part is currently at. Say I want a +/- .005 tolerance at operation 50 and a +/- .001 tolerance at operation 100. At the beginning of the program I would like the operator to be required to enter the operation number and this will dictate which tolerance is used. I'm thinking I would assign a variable to the prompt of which operation then use an IF statement to have the correct tolerance used. Just not sure whats needed to do that.

Thanks

[[Jo...]]

You don't need PCM to accomplish this. You can make mini plans for each operation. I have parts with different nominals and tolerances before and after heat treat and only have one program.

[[An...]]

The operators that are running the program don't really know anything about CMM's and honestly aren't that computer literate, as bad as that sounds. They're just there to put the part in the fixture and press play. The prompt in the beginning of the program will be answered by them using a bar code scanner to scan their work router for the operation. If we make it any more complicated than that I suspect some issues. That being said can I use miniplans to accomplish the same thing? i.e. use a bar code scanner to determine which tolerance to use

[[Jo...]]

Please sign in to view this quote.

I don't know about the bar code thing. Are you using the autorun interface ?

[[An...]]

no autorun

[[Jo...]]

Please sign in to view this quote.

Calling Roberto Flores ..??

I think he has some experience on autorun. I would recommend it for a caveman interface. You can create families of parts with pics. It pretty much locks out any editing or accidental tampering as well. I would like to hear from someone on the barcode thing. I haven't used it. Does it require PCM ?

[[Ro...]]

Program Presettings

itemSelected = inquireList("Is this part","Op50","Op100")

if itemSelected=="Op50" then
TOL=0.005
OPERATION="Op50"
endif
if itemSelected=="Op100" then
TOL=0.001
OPERATION="Op100""
endif

Then, in the tolerance field of the diameter in question, right click on the tolerance window and select formula, then just type "TOL" in the plus tolerance, and "TOL*-1.0" for the minus

THEN...............................

Create a text box (resources>Utilities>textelement) and name it "Operation Selected" and right click in the body and select formula and put "OPERATION" in the box, then in your report a line will be created so everybody knows which operation was scanned.
You may need to "formatL(OPERATION)" in the text box if its being finicky.

skskdjdhfghfg.JPG

[[An...]]

Please sign in to view this quote.

Right now we have a couple programs that use a barcode in the beginning to select which specific family is being run, for example we have one program where the bore is the same and there is 8 different options for locations of keyways within that bore. The program is set up so you open the main program then when you play it there is three prompts in the beginning; the operator uses a barcode scanner to answer these prompts. The first one is the operator badge number, they simply scan their badge, the second is the workorder from the router, and the third is the part number from the router. The first two are simply used for SPC records and it is also recorded on the report, the last prompt is what controls which orientation of that specific part is being measured.

[[An...]]

Please sign in to view this quote.

Thanks Roberto, I will give this a shot

[[An...]]

Roberto, thanks for your help. I got most of it working, the comments from the text boxes are not showing on the report though. Still trying to work through that. When I click OK on the formula box its giving me a caution question: The data type of the result does not match the data type desired "Text" Do you still want to continue?"

[[An...]]

Please sign in to view this quote.

So as I said before I was having issues getting this info on the report, looking at the forums it looks like the TextElement does not communicate with PiWeb and you cannot directly have this info on the report. Do you have a workaround?

[[Ro...]]

I don't use Pi Web, i use text reports that feed directly into WnSPC.
It's a 10+ year old system but we keep feeding it the same stuff we know it likes.

[[Ro...]]

But yes, hold on i have a workaround
You're gonna use your comment field in characteristics.
Open a dim
click on comment
Right click in the comment field & select Formula
"Operation Selected "+OPERATION+cr()+"Tolerance "+TOL
then hit compute and see if it works.

fgjkhfgdjhfgdj.JPGfdjfdjfgdjhkfgdj.JPG

[[Ro...]]

Please sign in to view this quote.

This is where the formatL() comes in to play.
Calypso wants text, and youre giving it numbers.
So to convert numbers to text you have to add a step in the process.
Instead of doing TOL, you do formatL(TOL)
so if this persists in my last reply change it to
"Operation Selected "+OPERATION+cr()+"Tolerance "+formatL(TOL)

[[Er...]]

That's actually not entierly correct.

formatL() is supposed to be used to shift a comma/point separator for a float value of a fixed lenght. Where it will be justified to the left. Thats what the L in the syntax is is indication. The same thing can be done to the right, with formatR().
The object will be converted to a "string with digits".

To convert a number to text (or actually a string value), use format().

Not saying this isn't achiveing the task. It's just not converting to text.

This will demonstrate the intended use pretty well i guess. You don't have to fill you code up with millions of space character to align outputs.

display("column 1	column2")
display("no1"+formatR(1.1123,25,3))

[[An...]]

Thanks Roberto, I have got what I need on PiWeb now. I'm now trying to figure out how I can get text elements, or I guess just the same information onto our Excel file that populates at the end of the run.