Doosan Puma 3100LY

[JeremyV]

Let me first say how much of a PITA these Doosans can be....

(TOOL - 7 OFFSET - 7)
(3.0"X .0625 SLIT SAW)
(SLITSAW PART)
N1030 G54
N1040 T0707
N1050 G19 G98
N1060 M35
N1070 M90
N1080 G0 C90.
N1090 M89
N1100 G0 X10. Y-1.899 Z.8795 M08
N1110 G97 S100 M03 P12
N1120 X.2
N1130 G1 X-.0626 F10.
N1140 G41 Y-.499 F1.8
N1150 Y.499
N1160 G40 Y1.899
N1170 G0 X10.
N1180 M09
N1190 M90
N1200 G30 U0. V0.
N1210 G30 W0. H0.
N1220 M05 P12
N1230 M01

The code above is how mastercam + post processor posts for the Doosan.   What happens here is the machine alarms on N1100 saying X overtravel, but we have 2.5" of travel on Y axis.  However... from what i've been told by the place that sold the machine to us.... the further out in X, the less the Y axis travels.

 

So with that knowledge, I had to manually add code to make it work:

(TOOL - 7 OFFSET - 7)
(3.0"X .0625 SLIT SAW)
(SLITSAW PART)
N1030 G54
N1040 T0707
N1050 G19 G98
N1060 M35
N1070 M90
N1080 G0 C90.
N1090 M89
N1091 G0 X10. Y0. Z1.7
N1092 X.2
N1093 Y-1.899
N1100 Z.8795 M08
N1110 G97 S100 M03 P12
N1130 G1 X-.0626 F10.
N1140 G41 Y-.499 F1.8
N1150 Y.499
N1160 G40 Y1.899
N1161 G0 Z1.7
N1162 Y0.
N1170 G0 X10.
N1180 M09
N1190 M90
N1200 G30 U0. V0.
N1210 G30 W0. H0.
N1220 M05 P12
N1230 M01

The above is what I had added to the program to make it work without alarming out.

 

This might seem far fetched, but is there anything in the control definition that could be made to do this or is this a post processor thing?

[crazy^millman]

To my knowledge neither will work to solve your issues out of the box. This is the issue with Dual Axis Y travel machines. Single Axis Y travel machines where Y has the full travel at all places in the X travel of the machine don't have these limits, but all Slant style machines trying to achieve Y axis travel using 2 Axis have this limit. Might could write some math logic in the post where if y_abs is above this amount then make this output a certain value for Y and output the code differently. Should not effect the post since the post is not kinematic aware and in this dumb. By it not being kinematic aware I think you will need to build a buffer and scan the toolpath section to see if the travel does fall outside of the range to then output the value you need. I would pass this to a professional post writer and have them do it for me.

 

Another thing to try would be a ref point in the operation where it forces the operation to start and end at Y0 absolute and see if that tricks your operation into working on the machine.

[SlaveCam]

Never mind... (obviously I can't even read)