Macro B question; Displaying a variable as an operator message.

[danielm]

I'd like to use the number in a variable as information to the machine operator. Ex: Lets say that I just ran a macro that set variable #141=.065. I now want to display that number and incorporate it into an operator message...something like: (Part is not located within .065. Inspect part loading).


Thanks for any help!!
DM

[BenK]

I would use an alarm for that. 

 

#141=.065

IF [#141GT.065] GOTO9999 

 

 

N9999 #3000=1 (Part is not located within .065. Inspect part loading)

[crazy^millman]

That is what the #3000 is for. Are you using a WHILE [DO] or just a basic math formula process?

 

Simple one:

#21 = .065

IF[#141 GT #21] GOTO9101

N9101 #3000=101 (DIFFERENCE GREATER THAN .065)

 

I recommend Peter Smid Fanuc CNC Custom Macro's book. Not very expensive and has some good examples.

 

HTH

[danielm]

I'm starting with a Renishaw probe macro for a 4-axis measurement and adjustment (O9817). #144 is the angle error that's written after the macro. The macro will error out on its own if the set tolerance is exceeded but it wont automatically report by how much and what direction.  Its this info that I want to put up for the operator.

[danielm]

BTW...thanks for the tip about the Smid book.

[specv]

What he is saying is that he wants the message to have the value of the variable (whatever that value is), Which as far as i know you cannot do. I would look into what Ben or Ron posted, those are some options. If its just informative to the operator then you could use #3006 which is a program stop with a message to check the value of variable #141  

[djstedman]

I haven't ever tried it, but would the following work? or is there some internal prohibition that only allows non variable types in the alarm? (I am kind of assuming there must be since otherwise why wouldn't this be the norm)

 

#3000=1 (Part is not located within .065. Actual value is #144)

 

Also, just an FYI, if you do any other probing before your error checking #144 will be overwritten on the next probing cycle, so if you do other probing at the same time, its a good idea to stash it into a non-volatile macro variable (anything that's not in use over #500) that way it wont get overwritten on the next probing cycle.

 

I program this way so I can probe multiple features without stopping, then when I do the error checking, I just check the values of the 500 series variables I have set, this way I can check multiple features and not have to have probing stop after the first thing it finds bad.

[Guyinthedesert]

you could stick the value in an unused work offset, like G54P10, ie #7181 = #141

[crazy^millman]

I'm starting with a Renishaw probe macro for a 4-axis measurement and adjustment (O9817). #144 is the angle error that's written after the macro. The macro will error out on its own if the set tolerance is exceeded but it wont automatically report by how much and what direction.  Its this info that I want to put up for the operator.

 

Well that is a totally different question. I think you have been pointed in the right direction.

[danielm]

I haven't ever tried it, but would the following work? or is there some internal prohibition that only allows non variable types in the alarm? (I am kind of assuming there must be since otherwise why wouldn't this be the norm)

 

#3000=1 (Part is not located within .065. Actual value is #144)

 

Also, just an FYI, if you do any other probing before your error checking #144 will be overwritten on the next probing cycle, so if you do other probing at the same time, its a good idea to stash it into a non-volatile macro variable (anything that's not in use over #500) that way it wont get overwritten on the next probing cycle.

 

I program this way so I can probe multiple features without stopping, then when I do the error checking, I just check the values of the 500 series variables I have set, this way I can check multiple features and not have to have probing stop after the first thing it finds bad.

 

 

I'll try that but I'm thinking that it won't work and will just be processed as a comment.  Maybe if it had brackets around #144....[#144]  ?   If it works I'll put it up.     Also...I'm getting used to storing variables in a safe area...#600's. 

 

Thanks for the feedback!!

DM

[Guest]

 

Also, just an FYI, if you do any other probing before your error checking #144 will be overwritten on the next probing cycle, so if you do other probing at the same time, its a good idea to stash it into a non-volatile macro variable (anything that's not in use over #150) that way it wont get overwritten on the next probing cycle.

 

Free fiss. :

 

I use variables between #150 and #199 for that stuff. Freeing mup my #500's for important stuff that I need to keep track of even after the power has turned off.

 

To OP; AFAIK you CANNOT insert data into an alarm message. You can do as follows;

#3001=143(MEAS. VAL. IS OUT OF TOL. SEE #143)

 

That would be the closest you could get to what you want.