Probe problems Haas vf1

[Hebrewhammer8]

tech just serviced this 05 vf1 with reinshaw toolsetter and probe.
however for some reason he ran out of time/couldn't get the probe to work.

I tried the calibrate probe xy macro that came with the machine and the probe does not work however when i manually move the stylus the controll will beep so i assume that it is getting trigger info.

tried the toolsetter and the macro for that seems to do all but what its supposed to do.

i get a probe open alarm when i try the probe calibrate xy.

here is the program:

O9802(REN CAL XY OFFSET)
G103P1
#3001= 0
G04 P250
G04 P1
G04 P1
G04 P1
G04 P1
G04 P1
G04 P1
IF [ #3001 LT 200 ] GOTO999
G65P9724
IF[#7NE#0]GOTO1
#3000=91(D INPUT MISSING)
N1
#1=185
WHILE[#1LE199]DO1
#[#1]=#0
#1=#1+1
END1
#10=#5041
#12=#5042
IF[#26EQ#0]GOTO2
IF[#18NE#0]GOTO2
#18=5*#179
N2
G65P9721D#7Q#17R#18Z#26S#[#161]
IF[#199NE0]GOTO3
G0X#177
#[#161+2]=#10-#177
G65P9722D#7Q#17R#18Z#26S#[#161+1]
IF[#199NE0]GOTO3
#[#161+3]=#12-#178
GOTO5
N3
G0X#10Y#12
IF[#199EQ2]GOTO4
#3000=92(PROBE OPEN)
N4
#3000=93(PROBE FAIL)
N5
G0X#10Y#12
N999
G103
M99

not yet up to par reading maco's so can anyone lead me in the right direction why this isn't working?

[cdmurphy]

Are you specifying a diameter? On my Fanuc based machines, you need to call G65P9802DX.XX where X.XX is the nominal diameter of your bored hole. If you are getting a beep on manual activation I think you are good to go, at least up to the renishaw interface. There may still be problems between it and the Haas control though. Try manually calling a G31 move with the probe safely away from anything at a slow feed rate, and manually trip the probe tip. It should immediately stop if everything is hooked up correctly. Do you have the manual for the inspection plus software? I think I have a pdf copy if you need it.

- Cameron

[Hebrewhammer8]

yes i am calling a diameter.
i'm going through the visual quick code menu and outputting to mdi which has the variable for the macro.

i tried the g31 and it did stop so it seems like everything is talking to eachother.

maybe i need to reload the macros.

[cdmurphy]

What does the machine actually do when you run the macro? Does it move at all, or error out immediately?

[Hebrewhammer8]

doesn't move at all.
just alarms out at this line: #3000=92(PROBE OPEN)

[cdmurphy]

I looked back though the macros on my control, and it looks like the error is probably happening in macro O9726, which is the basic measurement function that is called by a lot of the higher level macros. Your O9802 is calling O9721 for an X axis diameter measurement, which in turn is calling O9726 for each of the X axis measurement moves. When it gets to about line 38 of O9726, it calls a G31 move to what it thinks is the target position of your bore. For some reason it is tripping the probe input immediately, and in the following lines seeing that the probe hasn't moved the required minimum distance, and returning a probe open error. The only thing I can think of at this point is to make sure that your probe batteries are fresh, and maybe look into how your probe is turned on. On my M12 probe, you need to issue a special M code to turn the probe on before each use. If not, it will give the same error you are getting. Some probes required spinning on/off. Hope this helps.

- Cameron

[Hebrewhammer8]

i looked at those programs and it looks like they got imported for some reason with a bunch of (parenthases) in the program.
that looks like the error.
need to reload the programs but talked to haas for a split second and they said they have seen this before and if i try to import them again it will happen unless i change a parameter but they didn't tell me which one.
said they would call me right back, but like most techs. no call

thanx for the help. these macro things are fun but pretty complicated.

[PROBE]

Do you switch the probe on before running the G65P9802D..... ?
G65P9832 switches the probe on. G65P9833 switches it off.

[Hebrewhammer8]

so we got the macros loaded on and they look to be correct. i.e. no ()

tried the spindle probe calibrate xy and all i get is an out of range error.
My xyz are all in the middle of the range.

the probe is not orienting and not turning on (green light)

[psychomill]

What probe model are you running?

[Hebrewhammer8]

pretty sure its a reinshaw but i will check tomorrow when i get in to school.

pretty sure the program i posted earlier is different than the one it calls now from the VQC.

I will post the program tomorrow when i get back into school.

i'm glad i'm learning all about this stuff without parts that NEED to be made piling up!

[ARB]

Originally Posted by Hebrewhammer8

i'm glad i'm learning all about this stuff without parts that NEED to be made piling up!

That usually takes a little of the stress out of it.

[psychomill]

Right but... Renishaw makes many models. It's not likely a radio probe so probably something along a OMP40, 400 or 60.

So.....

tech just serviced this 05 vf1 with reinshaw toolsetter and probe.
however for some reason he ran out of time/couldn't get the probe to work.

Here's my question... is he coming back or they just plan on leaving you hanging?

Anyway, with a probe open alarm, also make sure you don't have a "line of sight" problem with the OMI unit (receiver) in the machine.

[Hebrewhammer8]

he kinda left us hangin which sucks!
thought haas was all about service
this makes me want to always be my own tech

i tried the g31 and when i triggered the probe the controll beeped and stopped movement.

I will get model number in the morning.

i reinstalled the macro programs, for some reason the first time they uploaded with a bunch of code in (parenthesis) so that solved some problems but now i get an out of range error.

[psychomill]

You have different errors now but the reason why I asked about 'line of sight' is because most people have the habit of checking the skip signal where the probe is within an easier reach. This may not be the same case as where the probe is during calibration or part cycle.

As for differences in program loading.... Try reloading programs again. Only this time, slow the baud rate way down. You may be shoving data too fast and the control is making mistakes (that is if you're using the serial I/O and not USB or Floppy).

[Hebrewhammer8]

I'm using USB to import.

The probe is a Reinshaw OMP40

here is the calibration program:


%
O09023 (REN EASYSET)
(40120737.0C VQC ADDED)
(HAAS VQC PROBE, English, Inch/MM, V1.8)
(07-11-2005)
G103 P1
#161= 556 (START CALIBRATION VARIABLE)
IF [ #1 EQ #0 ] GOTO17
#27= 10 (DEFAULT Q IN MM)
(#28=1DEFAULT WORK OFFSET)
#29= #[ #161 + 4 ] (PROBE OFFSET #560)
#30= 10 (STAND OFF)
#179= 0.04
IF [ #4006 EQ 20 ] GOTO1
IF [ #4006 EQ 70 ] GOTO1
#179= 1
N1
IF [ #1 EQ 12 ] GOTO40
IF [ #1 EQ 13 ] GOTO50
IF [ #1 EQ 19 ] GOTO60
IF [ #1 EQ 20 ] GOTO70
IF [ #1 EQ 21 ] GOTO80
IF [ #1 EQ 22 ] GOTO85
IF [ #1 EQ 23 ] GOTO90
IF [ #1 EQ 24 ] GOTO95
IF [ #1 EQ 25 ] GOTO81
T#29 M06 <------------------------------(HERE IS WHERE IT ALARMS)
G43 H#29
#30= #30 * #179
(IF[#19NE#0]GOTO2)
(#19=#28)
N2
G65 P9832
G103 P1
IF [ #19 LT 0 ] GOTO17
IF [ #19 GT 155 ] GOTO17
IF [ #19 GE 110 ] GOTO3

IF [ #19 LT 54 ] GOTO200
IF [ #19 GT 59 ] GOTO17
#19= #19 - 53
N200
IF [ #19 LE 6 ] GOTO3
GOTO17
N3
IF [ #17 NE #0 ] GOTO4
#17= #27 * #179 (* XY Q VAL)
IF [ #1 NE 9 ] GOTO4
#17= 4 * #179 (* Z Q VAL)
N4
IF [ #1 EQ 10 ] GOTO20
IF [ #1 EQ 11 ] GOTO30
IF [ #[ #161 ] EQ 0 ] GOTO91 (CHECK CAL)
IF [ #[ #161 ] EQ #0 ] GOTO91
IF [ #1 EQ 1 ] GOTO5
IF [ #1 EQ 2 ] GOTO6
IF [ #1 EQ 3 ] GOTO7
IF [ #1 EQ 4 ] GOTO9
IF [ #1 LE 6 ] GOTO11
IF [ #1 LE 8 ] GOTO13
IF [ #1 EQ 9 ] GOTO16
IF [ #1 EQ 14 ] GOTO130
IF [ #1 EQ 15 ] GOTO140
IF [ #1 EQ 16 ] GOTO150
IF [ #1 EQ 17 ] GOTO160
IF [ #1 EQ 18 ] GOTO170
GOTO17
(program is very long and has been shortened for posing purposes. Looks like there is many calibration routines in this program. If needed i will post the whole thing)


I have marked with <---------------------- where it alarms.

At T#29 M06 it gives me alarm 331 Range error: # too large.

line of sigh is not at issue where the probe is positioned.

[PROBE]

You must first of all load approximate lenght of the probe to variable #560. It seems that the value in this variable is bigger then maximum allowable tool length and this is causing your problem. Do not forget to run length calibration routine.

[SIM]

I don't have an answer about the Probe...

but anything downloaded to the control that looks unfamilar, gets put into ( ).

I have had this when baud rate was too high for control, or downloaded a lathe program by mistake.


If your local HFO does not call back or answer your question to your satisfaction, call the factory directly. They can be quite helpful and have on occasion placed a call to the HFO to find out what is going on.

[Hebrewhammer8]

thanks probe!
that what i just did 5 minutes ago. set up the toolsetter, then the probe lenth, then i did the probe xy calibration.

all was working well, it went thought the xy probe cycle 4 times, i assume/looked like 90deg. intervals to compesate for stylus ball error but then it kept probing untill the 6th set of xy probe moves it then alarms out
with a 531:macro nesting too deep, macros nested more that 9 times deep

so close to getting it working but no cigar yet.

[Hebrewhammer8]

haas called and gave us new updated macro's.
all problems solved.