[deadlykitten]

hy i simplified your program; before testing, be sure that turret is at X+ limit, and index to T2

G50 S500 ( or maybe 500.0 ) (*1)
G0 X22.0 Z22.0
T0202 ( G0 had been removed )
G96 S200 M3 M41 ( or maybe S200.0 ) (*1)
G0 X3.0  Z0.05
G1 X0.0        F0.005 G95
         Z0.1
G0 X22.0 Z22.0
M30 ( or M2 )

( i guess you should remove spaces and comments )
(*1 it may not be a must to use "." for G50S* and G96S*, since those may only handle integer numbers )

if there are 2 turrets, then put G13 at the begining / kindly

[machinehop5]

so i tried without the M41
but nothing again. i don't know about the cycle start interlock? how do we check that?

quick way to test if Workpiece clamping is the cause....just try running the program with nothing in the chuck with jaws open using foot switch...aka I.D. clamped

It looks like a parameter setting for "Workpiece clamped" Interlock. Not sure if this is your manual but, look in your manual for the Parameter
Okuma OSP7000L Model U LFS15-2SP Instruction Manual pdf - CNC Manual

Attachment 447038

[deadlykitten]

hy machinehop that is a good idea, to help him run the trials faster ... but i'm afraid that there is always needed something in the chuck, regardless of od/id clamping status, because there are safeties, that involve proximity senzors and pressure senzors

in order to run " hollow ", is needed to use the " grasp interlock cancel " spec, but this special function is costly, and was not designed for testing programs

the simpler way arround is to lock the machine, by pressing [ I-L ] + another button, like shown in attached, in order to put the machine in simulation mode; like this, real machine won't move, but display will work, even if there is nothing inside the chuck : this helps, for example, to test a future program, even if current machine setup is running a different program; sorry for all these explanations, i mostly wrote them for okuma1984 / kindly

[okuma1984]

hy machinehop that is a good idea, to help him run the trials faster ... but i'm afraid that there is always needed something in the chuck, regardless of od/id clmaping status, because there are safeties, that involve proximity senzors and pressure senzors

in order to run " hollow ", is needed to use the " grasp interlock cancel " spec, but this special function is costly, and was not designed for testing programs

the simpler way arround is to lock the machine, by pressing [ I-L ] + another button, like shown in attached, in order to put the machine in simulation mode; like this, real machine won't move, but display will work, even if there is nothing inside the chuck : this helps, for example, to test a future program, even if current machine setup is running a different program; sorry for all these explanations, i mostly wrote them for okuma1984 / kindly

don't worry. you're addressing a professional machine operator here. i have a very extensive knowledge of G code programming and fanuc. i have pushed buttons for 10 years!!!!!
lol my only problem is with the mechanics of this machine or trying to find out what's wrong with it. i will give it a shot with the modified program. it could very well be a G13

[deadlykitten]

ok, just give it a go

facing

G50S500
G13
G0X22.0Z22.0
T0202
G96S200M3M41
G0X3.0Z0.05
G1X0.0F0.005G95
Z0.1
G0X22.0Z22.0
M30(orM2)

only rpm

G50S500
G0X22.0Z22.0
T0202
G97S180M3M41
M30(orM2)

i hope that mechanics are fine do you have 2 turrets ? 2 spindles ? automatic doors ?

[OkumaWiz]

Ok your code looks good. Can you take a picture of the serial number plate? I see by the control pics you are on the U100 control and not the 7000.

Please try code with G13 at the top.

Is machine actually LB 15?

[okuma1984]

Ok your code looks good. Can you take a picture of the serial number plate? I see by the control pics you are on the U100 control and not the 7000.

Please try code with G13 at the top.

Is machine actually LB 15?

no it's Lu15! two turrets.
i added the G13 so now it is reading the program however it stops right away to give me a
1215-01 alarm

so, remove the G97S... line (spindle warm up if you will)
once it gets to my " G96 S200 M3 M41 " line
it projects this alarm

[okuma1984]

and you're correct about the control however there are no manuals with it but i got a lot of OSP700 manuals with the machine

[OkumaWiz]

Ok, since you have two turrets, they have to agree on what the spindle is doing. This requires you to use P codes for timing and you will need some code for the B turret to accomplish this:

G13 (A-TURRET)
G0X20Z20
G50 S800
G0T0202 G96 S100 M41 M3 P-1
X3. Z.1
Z0.
G1 X0. F.005
G0 Z.1
X3.
G0X20Z20M5 P2
G14 (B-TURRET)
G0X20Z20
G96 S100 M41 M3 P-1
G0X20Z20M5 P2
M2

When the control sees the G14, it will put the code on the B-turret side. The negative P code will reset the P counter and every time you change spindle commands, you will need to command the same on the opposite turret. You have up to 9999 codes available and they can be reset as needed so you are basically unlimited for timing codes. P codes will also work for things such as pinch turning. Just put a p code in your lap cycles on each line and they will match right down to .0001". The B turret is following 1/2 rev behind the A turret, so things like feeding at 2x the norm is possible when pinch turning.

Best regards,

PS> Turn on single block and feedrate down to keep rapid from occuring!

[okuma1984]

PS> Turn on single block and feedrate down to keep rapid from occuring!
G0T0202 G96 S100 M41 M3 P-1

i still get a Asynchoronous command B side 3 alarm right on the P line

that's a minus right?

[OkumaWiz]

LOL! yeah, we finally got them to change it so that you can switch a parameter bit and have the feedrate controlled all the time by the override switch instead of only with single block. It's available on the E100 and newer controls. Helps reduce the pucker factor! ;-)

[okuma1984]

LOL! yeah, we finally got them to change it so that you can switch a parameter bit and have the feedrate controlled all the time by the override switch instead of only with single block. It's available on the E100 and newer controls. Helps reduce the pucker factor! ;-)

i thought you could always add that Rapid option for a $1000?
i never needed it.

[OkumaWiz]

i still get a Asynchoronous command B side 3 alarm right on the P line

that's a minus right?

Yes it’s a minus. I think you may need a G110 since you are using G96 so that it knows which turret is being used to calculate surface footage.

[okuma1984]

Yes it’s a minus. I think you may need a G110 since you are using G96 so that it knows which turret is being used to calculate surface footage.

ok

nothing. it gives the same alarm. i go to the Turret B and try to run the program it does the same thing.

[okuma1984]

MAJOR BREAKTHROUGH

this worked, but only for the Turret A




what are "P"s ? ? ?

[machinehop5]

what are "P"s ? ? ?

Great its alive...

Attachment 447106

[deadlykitten]

what are "P"s ?

hello, let's supose that you wish for a program like this :
... face cut with turret 1 ( 10 seconds )
... c axis operation with turret 1 ( 30 seconds )
... roughing with both turrets ( 60 seconds )

if code is not " timed " right, then 2nd turret will start roughing when 1st turret will cut the face ... P helps with timing/handshake; for above example, is required to have a "handshake" after c axis operation finished / kindly

[OkumaWiz]

The code you posted is quite a bit different than mine. The G80, P22, P25, T100 are not needed. I would guess that having the M42 on a separate line caused you issues. That IS a spindle command, so try to keep the commands on the same line and less P codes are needed. If you did, the P9 would go away as well.

Another trick is to try running the code with individual A on and Individual B off. It will only look at A side code and then will not need to match B commands since it is not running. Only good until both need to run though and then your sync alarms will show back up.

Best regards,

[okuma1984]

The code you posted is quite a bit different than mine. The G80, P22, P25, T100 are not needed. I would guess that having the M42 on a separate line caused you issues. That IS a spindle command, so try to keep the commands on the same line and less P codes are needed. If you did, the P9 would go away as well.

Another trick is to try running the code with individual A on and Individual B off. It will only look at A side code and then will not need to match B commands since it is not running. Only good until both need to run though and then your sync alarms will show back up.

Best regards,

no i know i stole that from a guy who had a longer program so maybe that's why the G80 showed up. same with T100
but without the Peeees it doesn't work. we had similar coding in Fanuc where P was TIME eg dwelling. so "G4 P10" or X for the dwell. is it the same thing?

[okuma1984]

if you wish for a program ....
to TAKE AS MUCH AS 10 seconds ? or is that WAIT 10 seconds before you start the next MOVE?