Displaying variable values onscreen?

[facegarden]

Hello,

I needed to use my probe to measure a few parts today, and I know that variable #188 holds the diameter of a part probed with the renishaw probe bore cycle (#188 technically holds the "size" measured for any feature with the macros). I wanted to print it onscreen for the user to see, but HAAS tells me this is impossible with anything but the absolute latest in pendant code (my machine is only 1 yr old).

Do you guys know otherwise?

I know I can set a pause with a message using variable #3006, or an alarm with #3000 (or #3001?), but neither of those will display a variable's value with anything I have tried.

I have a serial printer hooked up right now, but we use it elsewhere in the shop and I don't want to have to always use it.

I also know I could have an IF statement and determine if the part is in spec automatically and print that, but I would still like to be able to just display a value onscreen for times where that is more appropriate.

And ideas?
Thanks!
-Taylor

[vlmarshall]

How about setting #3006=#188, and pausing with that?

Interesting problem, I'm gonna think about this one for a bit more.

[vlmarshall]

Wait, isn't there a page under Current Commands that displays the variables?

[facegarden]

Originally Posted by vlmarshall How about setting #3006=#188, and pausing with that? Interesting problem, I'm gonna think about this one for a bit more.

#3006=#188 causes an error, as #188 is a decimal value.

You can set #3006 equal to any number from 1 to i believe 99 or something, which can be used as a code along with the message. Since my value is a decimal it causes an error.

#3006=1(This text is displayed)

Is the format, but I have tried

#3006=1(#188)
and that doesn't work, it just displays the pound sign and 188, not the variable's value.

I have also tried
#3006=1(#188[24])

because DPRNT seems to like that [24] and i thought it would help, but no, it just displayed that too.

The guy at HAAS was kinda lame - he said "It doesn't do it because no one needs it." Which was rediculous because:

A) I need it.

B) Just because he hasn't heard any complaints doesn't mean people don't need it. Hell, I've found that many users of our products don't "need" new features until we add them, and then they appreciate and use them.

It is also just weird because you can display custom messages, and you can send variables out the serial port, but you can't put variables in custom messages. If people might need a custom message, and they might need to have data sent out the serial port to a serial printer or computer, who decided they wouldn't also get some use out of putting variables in the custom message displayed onscreen?

Lame.

I still think it might be possible.
-Taylor

[vlmarshall]

Yeah, that IS lame. I'm going to play with this tommorrow at work. I think it's possible too.

[facegarden]

Originally Posted by vlmarshall Wait, isn't there a page under Current Commands that displays the variables?

Yes, but then my operator has to go to that page and find the variable each time.

I did just realize that if you have just been there, it remembers where you were, so it's not too bad to just go look there again because you don't have to hit page down again, but it still seems like a basic functionality that would be more useful than navigating to that page each time. My operator often forgets things like which variable number is the correct one, for example. It would be easier if my code could just tell him the number he needs.
-Taylor

[Matt@RFR]

For the time being, could you go:

M0
(CRNT CMDS, PAGE DOWN, RECORD #188)

Or something to that effect? I know it's not what you want, but it would atleast leave no room for excuses for the operator.

Also, out of curiosity, why are you not automatically updating the offset page after probing? That would avoid the operators' involvment entirely.

[facegarden]

Originally Posted by Matt@RFR For the time being, could you go: M0 (CRNT CMDS, PAGE DOWN, RECORD #188) Or something to that effect? I know it's not what you want, but it would atleast leave no room for excuses for the operator.

I mostly just want to give him some nice code to make him happy. Part of my job is learning new things to make the shop better, not just getting jobs done.

Originally Posted by Matt@RFR Also, out of curiosity, why are you not automatically updating the offset page after probing? That would avoid the operators' involvement entirely.

We aren't zeroing the parts, we are measuring them. After you probe a bore or a boss, #188 holds the measurement.
-Taylor

[Matt@RFR]

I understood that. You can update the tool offset page (wear) with the probing macros as well as the work offsets.

[facegarden]

Originally Posted by Matt@RFR I understood that. You can update the tool offset page (wear) with the probing macros as well as the work offsets.

I don't need to update anything, we are just taking final measurements for inspection. All i need is the diameter of the bore.
-Taylor

[dougtyler]

I understand your pain.

I've been trying to do the same thing on a Fanuc 31I control, ever since we've gotten them about 2 years ago, with no luck.

[stevo1]

I am not very familiar with Haas but I do a lot with Fanucs which I know are pretty similar. Here are a few thoughts on the topic as I have thought about it as well.

1) If it is easier for the operators to reach say the tool offset page or the work offset page then you could write the value to say a tool offset value that you never use like 99 or something. If you have that many tool offsets. If it is just a matter of having to page to the actual number then you could have it set to a local variable like #1 that way when they press the key to the variables it’s the first one displayed.

2) Does the machine display the feed rate set with “F” and then clear with the reset button? What you could do is at the end of the program just do a F#188 then the feed on the front screen will be set to the diameter.

3) Depending on how long you have to display the value of #188 or how large the number is you could do a dwell of G4X#188 and then while it dwells the value of #188 it will be displayed as the executed block showing the value of #188 on the screen.

4) I don’t know if you want to record the actual value or just check to see if it is in spec. You could write your program to alarm out or message to display if the data in #188 exceeds the tolerance of say 3.015+/-.005.
IF[#188GT3.02]TH#3006=1(DIAMETER TO BIG)
IF[#188LT3.01]TH#3006=1(DIAMETER TO SMALL)

Stevo