ARK OK signal

jbfabweld

jbfabweld
Does the M3 ( torch on) initiate the dwell till the ARK OK signal is received at MASSO, then allows OK to MOVE motion in G01? My machine uses a pneumatic actuator for Z height control, M8 ( torch down) prior to M3 (torch on) and M5 (torch off) prior to M9 (torch up). Is M667/M666 needed in the Gcode for the ARK OK signal to work?

Sample gcode:

G0 x1

M8

M3

G4 p1000

G01 x10

M5

M9



Thanks
 

breezy

Moderator
Jim,

You need to set torch height control to option 2

attachment



When MASSO reads the M3 it turns on the torch control output then waits 15 seconds for the Arc-OK signal, if the signal doesn't arrive in that time frame it throws an alarm and stops else it continues with the program.

So with your program

G0 x1 Moves to x1

M8 Turns on actuator

M3 Turns on plasma waits Arc-OK

G4 p1000 Waits 1 sec

G01 x10 Moves to x10

M5 Turns off plasma

M9 Turns off actuator

As you are using option 2 there is no need for M667/666 in your Gcode.
 

lilow

Lilow
jbfabweld

Try this.

G00 ( go to first start for cutting )

G38.2 Z-75 ( torch touch / distance to trigger limit plus return up to piece height to set the G92 )

G92 Z0.0 ( temp zero the height set in F1 screen / THC torch touch offset)

M667 F50 ( intigates Masso in THC mode, with Z axis speed )

M3 ( fires Plasma )

M8 G4 P800 ( instigates the THC board with a delay for arc stabilization )

G1 ( cut part )

M666 ( switch off THC in Masso / reverts to normal Masso control )

M5 ( Switch of Plasma )

M9 ( Switch off THC board )

G0 Z60 ( Go to safe height )

G0 X0 Y0 ( back to work origin )

This works every day here.

Is M667/M666 needed in the G code for the ARK OK signal to work?

( I do not use the Arc Ok from the THC board, set Arc Ok to a high (Red) in F1 screen. )

Cheers.
 
Top