Problem with ssb/lib file

[Shotout]

MA500 OSP200 control

Was wondering if some one could help me with a problem I'm having. I use a sub program call to change tools at work to avoid wrong tool command errors when restarting etc. My normal tool change is CALL OCHG1 TOOL=nn where the sub OCHG1 is:

OCHG1
M5 G30 P1
IF[VTLCN EQ TOOL] NTLOK
IF[VNTOL EQ TOOL] NCH
IF[VNTOL EQ 0] NTC
M64
NTC T=TOOL
NCH M6
NTLOK
RTS

I also have it in a lib file where TOOL=60 registered as G115 so that my operators can clear the presenter and spindle to check tools at the end of shift.

What happened
I was firing up the machines the other morning, running the 1st piece to put the machine into cycle and it never changed tools. It started running the program with the current tool, T60, in the spindle but it called up the tool length offset for the 1st tool in the program, H07, was making the first rapid move and had called up work offset H11, spindle and coolant on. Also the program display screen wasn't displaying the program. It showed the correct program name in the title bar, but nothing was displayed in the window. I dialed rapid down to 0% and hit Quick Edit. The active line was the CALL OCHG1 TOOL=07 line. Aside from the unexpected results I find it odd that it would show the active block as the tool change line but be processing the block 4 lines past that. Program structure is:
O5001
(COMMENT LINES)
RP=1M289
G119 (Lib program that clears the work offset, Z axis to "home", then X and Y to tool change position then B0.)
G0G90G94G20G80
M1
N1007 (*TOOL 7* 2IN ISCAR FACE MILL *LONG*)
CALL OCHG1 TOOL=7
G15 H11
M08
M120
G0 G90 X-18.5 Y3.5S1145M03
G56 H07 Z12.
Z8.2389
G1 X-17.2

Same exact results in MDI when entering CALL OCHG1 TOOL=1. It started to run the program for the current pallet, blank program window, and called the offset for the 1st tool (T7) in the program etc. G115 after an MDI tool change using the M06 command did the same.

After talking with a friend he suggested that perhaps someone had went into the parameters and disabled the interlock that prevents a tool change to an empty pot. His suggestion was to create a main program with the T variable in it. Load that program, power down completely and back up then run the main program so I did after commanding an M6 tool change in MDI. As a main program it works. Tried calling up the main program for the part again and running, same strange result. I thought it might have to do with a 7in face mill I had installed in the machine the night before for another setup, the interlock for the tool change, so I cleared it and the two dummy tools from the tool registry so the 3 pots showed NONE. No luck.

Checked the keystroke log to see if I could find any entries where someone had gone into the parameters but is didn't show anything. The operator stated that it ran fine the day before, obviously since it didn't crash, and that he had not been on the control except to pallet change when OP1 came out with a slag hole inside a drilled boss and left him with no part for the OP2 fixture. Which is one of the reasons I use the sub call to start with.

Does anyone have any idea what might be causing this? I'd appreciate any help, ideas etc.
Thanks
Scott

[Superman]

Can you put up what these variables represent ?
VTLCN
VNTOL
VNTOL

I think
VTLCN is current tool
VNTOL is next tool

Have you single blocked thru the code and checked the variables after each block ?

Could an additional block be inserted that would error if conditions are not meet ? ie IF [ VTLCN NEQ TOOL ] err "TOOL NOT LOADED" after the M6 line

We have ours set to replace the M6 code with a G-code
works a similar way, no T/C if the tool is in the spindle but goes to P1, if T/C required , it goes to P1 and T/Cs

ie

N1999 M1
()
N2000 G116 T3 ( Tool 3, H3, D3, dia=25mm)
N2001 T4
()
N2002 G15 H1

let me know if you want a look at the G116 file

Have a look at this thread-post #6
OKUMA MA40 HA variables

extra ideas ?? maybe

[Shotout]

You are correct about the variables.
VTLCN= Actual tool number in the spindle
VNTOL= Tool number in the presenter
VNTOL EQ 0: If next tool=Zero then stage the tool number that the program making the call has set as the variable for TOOL.

I'd like to see your routine it if you don't mind posting it.

I didn't think of the single block and check so no I haven't I'm afraid. I got focused on what was suggested about the interlock. The person who I was talking to set the machines up when he was our tooling and apps eng before going to work for an Okuma dealer. It was a problem that had occured on other machines he had dealt with and he had a ready culprit and fix in mind so... Considering despite 5 weeks notice he was not treated well when he left I try not to bother him too much for stuff like this, although he is the kind of guy that would drop in on his way through town just to help out.

As to the other thread. I printed it yesterday to read over the weekend but haven't gotten farther than "Cool more info". I use a main program that is essentially sets my XYZ work offsets used in the program for each pallet, then checks the current pallet with a goto line to call the appropriate sub file for that pallet. It was set up this way so we could later add the robot and pallet loading system we want to the Okumas and run several part sets (LH and RH) together. Different way to skin the same cat as a schedule program.
Snipped from A500.MIN
IF[VPLNO EQ 1]N010
IF[VPLNO EQ 2]N020
MSG(PALLET NO NG)
GOTO NEND
N010 CALL O5001(.SSB)
N011 GOTO N001
N020 CALL O5002(.SSB)
N021 GOTO N001

Can you put up what these variables represent ?
VTLCN
VNTOL
VNTOL

I think
VTLCN is current tool
VNTOL is next tool

Have you single blocked thru the code and checked the variables after each block ?

Could an additional block be inserted that would error if conditions are not meet ? ie IF [ VTLCN NEQ TOOL ] err "TOOL NOT LOADED" after the M6 line

We have ours set to replace the M6 code with a G-code
works a similar way, no T/C if the tool is in the spindle but goes to P1, if T/C required , it goes to P1 and T/Cs

ie

N1999 M1
()
N2000 G116 T3 ( Tool 3, H3, D3, dia=25mm)
N2001 T4
()
N2002 G15 H1

let me know if you want a look at the G116 file

Have a look at this thread-post #6
OKUMA MA40 HA variables

extra ideas ?? maybe

[Superman]

Here you go

changed .LIB to .TXT for attaching