What's new
What's new

Brother speedio variables

civicske2

Aluminum
Joined
Nov 29, 2015
Hello,
i am quiet a time spending on a macro on the speedioX700 where i want to read a on/off signal from #1000 into a local variable.
if i do it in mdi, signals coming in as it should be. When runnin in auto mode it never does.
signal comming in on 1 when the #=OFF

I put a G4 after every ...#=...# as i tought it was the look ahead that was reading to early but also that doesnt work.

can anyone help? the goal is to detect tool breakage with the switch conneted to #1000
 

gkoenig

Titanium
Joined
Mar 31, 2013
Location
Portland, OR
M159 is a single-shot code that prohibits read ahed until the line just after it.
Once that line is processed, read ahed is turned back on.
 

BROTHERFRANK

Stainless
Joined
Dec 20, 2013
Location
SoCal
Do you have a tool setter probe installed like a Blum Znano or equivalent? We use that for tool breakage detection as well as tool length setting. If you connect a sensor or switch to the Touch Sensor input on the IO board, you just need to command a M120 when the tool is in position to activate the sensor or switch. M120 will automatically set feed hold and give a Tool Broken Error alarm if the Touch Sensor input is not made. If the signal is there, the machine will continue operation.
 

couch

Cast Iron
Joined
Jun 10, 2009
Location
Anaheim, California
M120 and M121 are Skip Signal detections. M120 alarms when not no signal is detected, M121 alarms when signal is detected. Here’s the Breakage Program I wrote and use.

(TOOL BREAKAGE SUB)
(03/04/2022 KS)

(USER INPUTS)
#1=.010 (PULL OUT SENSITIVITY)
#2=.010 (BREAKAGE SENSITIVITY)
(END USER INPUTS)

G100 T#3700 G0 G90 G54.1 P48 X.03 Y.03 M19 (POSITION OVER TOOL SETTER XY)
G43 H#3700 Z.3937 (ACTIVATE TOOL OFFSET IN SPINDLE - POSITION FOR INITIAL PULL OUT DETECTION)
M121 (TOUCH SIGNAL CHECK - ERROR WHEN ON)
G1 Z#1 F150. (POSITION FOR FINE PULL OUT DETECTION)
M121 (TOUCH SIGNAL CHECK - ERROR WHEN ON)
G1 Z-#2 F150. (TRIGGER TOOL SETTER - BREAKAGE DETECTION)
M120 (TOUCH SIGNAL CHECK - ERROR WHEN OFF)
G100 T#3700 (SEND SPINDLE HOME)
M99 (RETURN TO MAIN PROGRAM)

(NOTES)
(MATCH G54.1 P48 Z WCS TO USER PARAMETER SWITCH 1 #7 OR 8028 Z VALUE - TRIGGER HEIGHT)
(INITIAL Z POSITION SET FOR OVER TRAVEL PREVENTION ON BLUM Z NANO)
(XY POSITION IN G100 LINE CAN BE ADJUSTED - THIS SHIFT REDUCES WEAR ON TOUCH-OFF LOCATION)
 

civicske2

Aluminum
Joined
Nov 29, 2015
i fixed the earlyer problem by putting an m159 between the lines of reading variables. can you tell me more about it? do i have to do it always at each line when i m reading variables?


Im trying to get a macro working witch loops al day but past 16.00.00 houres when counter (#666) is reached it has to sent to M30 to switch off machine.

N100
(LOAD/UNLOAD 1PROG)
#666=[#666+1]
M400
M402(LOAD1)
M404(UNLOAD1)
M460(W8)
M403(SIGNL OFF)
M405(SIGNL OFF)
M400
M98P1531 (***PROG NR HIER AANPASSEN***)
IF[#666LT#667]GOTO100
M159???
IF[#3012GT160000]GOTO999
M159???
GOTO100
N999
M30
 

gkoenig

Titanium
Joined
Mar 31, 2013
Location
Portland, OR
i fixed the earlyer problem by putting an m159 between the lines of reading variables. can you tell me more about it? do i have to do it always at each line when i m reading variables?


Im trying to get a macro working witch loops al day but past 16.00.00 houres when counter (#666) is reached it has to sent to M30 to switch off machine.

N100
(LOAD/UNLOAD 1PROG)
#666=[#666+1]
M400
M402(LOAD1)
M404(UNLOAD1)
M460(W8)
M403(SIGNL OFF)
M405(SIGNL OFF)
M400
M98P1531 (***PROG NR HIER AANPASSEN***)
IF[#666LT#667]GOTO100
M159???
IF[#3012GT160000]GOTO999
M159???
GOTO100
N999
M30

What exactly are you trying to do?
Putting M159s all over the place (outside of actual program code) won't hurt anything. I would lower the counter and change the end time to test it all out though.
 








 
Top