Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
M code return failure
#1
I have UMAC with Adv900, TPMAC2, ACC24E2A 4x, ACC65E. A pretty straightforward retrofit of an Eagle mill. The program code uses M98 with three different file calls, one to setup and start coolant, one to perform repetitive drilling cycles, and one to end the cycle. Here is a code snippet:

N1 M98(c:\cnc\startnc.nc)L1
N2 X-0.3177 Y-8.0255
N3 M98(c:\cnc\drillnc.nc)L1
N4 X-0.3177 Y-6.0255
N5 M98(c:\cnc\drillnc.nc)L1
N6 X-0.3177 Y-4.0255

The program loads the first called program startnc.nc, that looks like this:

N05 G90 G17 G20
N10 M8
N15 M3 S100
N20 G0 G53 Z-0.5
N21 G0 G54 X0 Y0
N23 G0 Z.500
N25 M8
N30 M1
N35 M99

The program hangs with the yellow highlight at the top line. The M8 coolant on executes (turns on). NC shows N10000 as current line. The Buff is Open, in Auto, and CS Status shows Program running, federate at 50%. G90 G17 G20 show active If I load Startnc.nc directly, the same thing happens.

With drillnc.nc the program looks like this:

/M8
M3 S1500
G0 Z0.250
G1 Z-2.120 F3.0
G0 Z0.250
M99

This progam, if loaded directly, does the same thing. If M8 is starting line it executes coolant on and hangs. If M8 is deleted, M3, S1500 line runs (spindle comes to speed) and the program hangs, top line yellow highlighted, as described above.

If the M3 S1500 line is deleted. The G code motion lines executed completely to the end.

The really odd thing is that there are two machines at this site, one machine will run these exactly copied programs without problem. The one I am working on does not seem able to return from the Prog1001 Mcode call.

Any ideas?

Tim Lockert
Reply
#2
(07-01-2014, 03:58 PM)timlockert Wrote: I have UMAC with Adv900, TPMAC2, ACC24E2A 4x, ACC65E. A pretty straightforward retrofit of an Eagle mill. The program code uses M98 with three different file calls, one to setup and start coolant, one to perform repetitive drilling cycles, and one to end the cycle. Here is a code snippet:

N1 M98(c:\cnc\startnc.nc)L1
N2 X-0.3177 Y-8.0255
N3 M98(c:\cnc\drillnc.nc)L1
N4 X-0.3177 Y-6.0255
N5 M98(c:\cnc\drillnc.nc)L1
N6 X-0.3177 Y-4.0255

The program loads the first called program startnc.nc, that looks like this:

N05 G90 G17 G20
N10 M8
N15 M3 S100
N20 G0 G53 Z-0.5
N21 G0 G54 X0 Y0
N23 G0 Z.500
N25 M8
N30 M1
N35 M99

The program hangs with the yellow highlight at the top line. The M8 coolant on executes (turns on). NC shows N10000 as current line. The Buff is Open, in Auto, and CS Status shows Program running, federate at 50%. G90 G17 G20 show active If I load Startnc.nc directly, the same thing happens.

With drillnc.nc the program looks like this:

/M8
M3 S1500
G0 Z0.250
G1 Z-2.120 F3.0
G0 Z0.250
M99

This progam, if loaded directly, does the same thing. If M8 is starting line it executes coolant on and hangs. If M8 is deleted, M3, S1500 line runs (spindle comes to speed) and the program hangs, top line yellow highlighted, as described above.

If the M3 S1500 line is deleted. The G code motion lines executed completely to the end.

The really odd thing is that there are two machines at this site, one machine will run these exactly copied programs without problem. The one I am working on does not seem able to return from the Prog1001 Mcode call.

Any ideas?

Tim Lockert
Reply
#3
After intensive trouble shooting it is determined that the hang up is associated only with M3, spindle on, and the spindle at speed signal.

It's hot in southern Louisiana in July!

Tim Lockert

(07-01-2014, 03:58 PM)timlockert Wrote: I have UMAC with Adv900, TPMAC2, ACC24E2A 4x, ACC65E. A pretty straightforward retrofit of an Eagle mill. The program code uses M98 with three different file calls, one to setup and start coolant, one to perform repetitive drilling cycles, and one to end the cycle. Here is a code snippet:

N1 M98(c:\cnc\startnc.nc)L1
N2 X-0.3177 Y-8.0255
N3 M98(c:\cnc\drillnc.nc)L1
N4 X-0.3177 Y-6.0255
N5 M98(c:\cnc\drillnc.nc)L1
N6 X-0.3177 Y-4.0255

The program loads the first called program startnc.nc, that looks like this:

N05 G90 G17 G20
N10 M8
N15 M3 S100
N20 G0 G53 Z-0.5
N21 G0 G54 X0 Y0
N23 G0 Z.500
N25 M8
N30 M1
N35 M99

The program hangs with the yellow highlight at the top line. The M8 coolant on executes (turns on). NC shows N10000 as current line. The Buff is Open, in Auto, and CS Status shows Program running, federate at 50%. G90 G17 G20 show active If I load Startnc.nc directly, the same thing happens.

With drillnc.nc the program looks like this:

/M8
M3 S1500
G0 Z0.250
G1 Z-2.120 F3.0
G0 Z0.250
M99

This progam, if loaded directly, does the same thing. If M8 is starting line it executes coolant on and hangs. If M8 is deleted, M3, S1500 line runs (spindle comes to speed) and the program hangs, top line yellow highlighted, as described above.

If the M3 S1500 line is deleted. The G code motion lines executed completely to the end.

The really odd thing is that there are two machines at this site, one machine will run these exactly copied programs without problem. The one I am working on does not seem able to return from the Prog1001 Mcode call.

Any ideas?

Tim Lockert
Reply
#4
That would have been my first thought is Spindle At Speed. You can also use G25/26 for testing this type of thing. Spindle Speed Detect ON & OFF. I have run into this more time than I can count. Does this machine use encoder feedback to determine speed or the analog feedback? Also note that the yellow bar sometimes gets out of sink especially while mcodes are executing & McodeAtFront registry settings also play a part.

(07-02-2014, 07:09 AM)timlockert Wrote: After intensive trouble shooting it is determined that the hang up is associated only with M3, spindle on, and the spindle at speed signal.

It's hot in southern Louisiana in July!

Tim Lockert

(07-01-2014, 03:58 PM)timlockert Wrote: I have UMAC with Adv900, TPMAC2, ACC24E2A 4x, ACC65E. A pretty straightforward retrofit of an Eagle mill. The program code uses M98 with three different file calls, one to setup and start coolant, one to perform repetitive drilling cycles, and one to end the cycle. Here is a code snippet:

N1 M98(c:\cnc\startnc.nc)L1
N2 X-0.3177 Y-8.0255
N3 M98(c:\cnc\drillnc.nc)L1
N4 X-0.3177 Y-6.0255
N5 M98(c:\cnc\drillnc.nc)L1
N6 X-0.3177 Y-4.0255

The program loads the first called program startnc.nc, that looks like this:

N05 G90 G17 G20
N10 M8
N15 M3 S100
N20 G0 G53 Z-0.5
N21 G0 G54 X0 Y0
N23 G0 Z.500
N25 M8
N30 M1
N35 M99

The program hangs with the yellow highlight at the top line. The M8 coolant on executes (turns on). NC shows N10000 as current line. The Buff is Open, in Auto, and CS Status shows Program running, federate at 50%. G90 G17 G20 show active If I load Startnc.nc directly, the same thing happens.

With drillnc.nc the program looks like this:

/M8
M3 S1500
G0 Z0.250
G1 Z-2.120 F3.0
G0 Z0.250
M99

This progam, if loaded directly, does the same thing. If M8 is starting line it executes coolant on and hangs. If M8 is deleted, M3, S1500 line runs (spindle comes to speed) and the program hangs, top line yellow highlighted, as described above.

If the M3 S1500 line is deleted. The G code motion lines executed completely to the end.

The really odd thing is that there are two machines at this site, one machine will run these exactly copied programs without problem. The one I am working on does not seem able to return from the Prog1001 Mcode call.

Any ideas?

Tim Lockert
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)