Help with transfer - Macturn250W OSP200

I am having trouble with my code on a Macturn 250W OSP 200.

My program runs fine with optional stop on, however if switch off optional stop I get an alarm that I do not understand relating to my W axis while attempting to run a transfer with cutoff.

The alarm is 2273-01 ALARM-B Data Word "W" A side 3 , which apparently means that my commanded W position is out of range.

Attached is the alarm and the program. All I know is that its a timing thing and a P code thing. My okuma knowledge is best described as shallow. The output is from CAM, as
the jobs we are doing do not lend themselves very well to IGF so I need to a solid grip on what is happening and why.

Thanks
hocuspocus357


N45 P50
N50 P60
N55 ( W AXIS CONTROL - A TURRET )
N60 G140
N65 P61
N70 G122 P62
N75 P63
N80 P65
N85 M42
N90 G0 X1000. Z1000. W5000.

( OPERATION PART-OFF-TRANSFER )
( TOOL NUMBER 20 )
( TOOL DATA TAG N3C / TGAQ D82-3-4Z-JHP / TGTBY R32-D82R-JHP / HSK A63WH TBK 32R )
( POST TT_TURNING_POST )
G140
G20 HP=4
MT=02001
M321
MT=01601 ( PRESELECT )
G20 HP=4
(BT FORMAT)
N95 TL=020020 BT=1 M603
N100 G90 G0 X100. Z25.
M175
Z-34.468
X42.798
G138
G0 Y-21.399 Z-34.468
X0.0 ( CENTRELINE )
N105 M05 P66
M247
M249
M89 M289
M151
G0 W30.000 (APPROACH) <------------- Here is where I get stuck!

I wold say it's not related to the W axis range. More likely it's trust monitoring.

Quote:

---

Originally Posted by Algirdas

I wold say it's not related to the W axis range. More likely it's trust monitoring.

---

Thanks for the suggestion, can I temporarily disable thrust monitoring with an M code? Better yet, what is wrong with my code?

check the programming manual or special functions manual. You will find out what is the command to start trust monitoring and cancel trust monitoring.
On the other hand, here in this forum sure are at least a couple of workpiece transfer examples with detailed explanations.

You've got a timing issue of when the W move is occurring. Depending on parameter settings, your G140 and M01's can work like P-codes, so with the M01 it may not be reading ahead as much as with it off. Check the timing in your program with single block on to see more closely when the alarm happens. I think you'll see that it's reading different areas of the program timing wise with M01 on vs off. You don't show enough code for both turrets for us to properly evaluate.

On the LT-300 (very similar) I also was using the G145 command to switch to W-positioning mode before doing the transfer and G144 to turn it back off.

Best regards,

Quote:

---

Originally Posted by OkumaWiz

You've got a timing issue of when the W move is occurring. Depending on parameter settings, your G140 and M01's can work like P-codes, so with the M01 it may not be reading ahead as much as with it off. Check the timing in your program with single block on to see more closely when the alarm happens. I think you'll see that it's reading different areas of the program timing wise with M01 on vs off. You don't show enough code for both turrets for us to properly evaluate.

On the LT-300 (very similar) I also was using the G145 command to switch to W-positioning mode before doing the transfer and G144 to turn it back off.

Best regards,

---

Hi OkumaWiz
Thanks for the reply, I know its a timing issue, and I don't understand timing, how do I time things? That may sound deliberately ignorant and its because I am. I know enough about this machine to get myself into trouble, but not out of it! The manuals don't mention anything about it so its been quite frustrating. Lucky for me CNCZone and G145 is my knight in shining armour. However, I am still in the dark about all of this so I would much prefer to have to solutions to this problem, solution one, understand timing, solution two use G145.

Attached is a working code sample that I based my code on, my broken code and the actual g code in full.

This might be too big a topic for an explanation here, but nevertheless, any insight is appreciated.

Attached is a zip file with the attachments from the post above in case they get scaled down and lose legibility.