[rcs60]

fanuc controllers have a geometry and a wear offset this is why there are 2 system variables
You need them before the G43 tool length call as on the same line the tool is going to make a Z axis movement to the pc. it makes no sense to check after the crash
you should also have it after the tool call (M6Txx) as a tool offset can be made while the program is running
This keeps the operator from making a large change to the tool geometry and wear offsets during the running of the program
You could put it at the beginning of the program and that is where the check will be done which bring us back to the previous sentence
all this is is a check during the program that will stop the machine if the operator did a offset larger than the check allows.
if a geometry/wear offset exceeded the amount set in the program in the example above #10001+#11001 -8.8 can be no greater than .100 in either direction of 8.800".(8.900-8.700 in length)
this usually slows the crash down to the feed rate of going into the cut (instead of 1200-1400 ipm "G0" the feed is usually in the 50 ipm range here is where you could if the option was purchased (DRDOS mentioned load detection) might be able to stop the crash

[deadlykitten]

hy rcs

how many offsets are there ? 30, 100 ?

#10001 and 11001 are system variables for offset 1 and wear 1 ? thus, considereing that there are only 30 inputs, their range is up to #10030 and #11030 ?

same questions for #13001 and #12001

M6Txx

i suppose that you are talking about a mill

You need them before the G43 tool length call as on the same line the tool is going to make a Z axis movement

so, for example, if i use T10M6, G43 H10, then tool will move on z when executing G43 H10 ?


please, have you used load monitor on fanuc ? kindly

[rcs60]

hy rcs

how many offsets are there ? 30, 100 ?

#10001 and 11001 are system variables for offset 1 and wear 1 ? thus, considereing that there are only 30 inputs, their range is up to #10030 and #11030 ?

same questions for #13001 and #12001



i suppose that you are talking about a mill



so, for example, if i use T10M6, G43 H10, then tool will move on z when executing G43 H10 ?


please, have you used load monitor on fanuc ? kindly

there are 100 tool offset #10001-#11000 then #11001-#12000 ect.
the example is for a mill -- most programmer will put on the same line as the g43 Hxx a z axis movement to set the offset
it could be modified to a lathe with the geometry and wear offsets to keep the offsets being made while running the lathe so as not to crash when the offset was to large
on the lathe i would put it before any axis moves
the load monitor that i have used is for an OKUMA osp200 (simple load monitoring it works ok on larger tools I have not used fanucs load monitoring

[deadlykitten]

there are 100 tool offset #10001-#11000 then #11001-#12000 ect.

hello rcs please, i don't understand how to fit 100 values between 10001 and 11000

also, is it possible to save the offset values to a file ? is it possible to read that file later ?

It is a Fanuc paid option and it's called Abnormal Load Detection, or Abnormal Torque Detection. Here is the write up on it. I am surprised Fanuc didn't tell you about it.

hello drdos please, have you used those ? is it possible to do this :
... turret @ home position
... index
... rpm, coolant
... approach
... [ monitoring on : z25% x10%]
... cut until z-50 feed=0.12mm/rot
... [ monitoring on : z20% x10% ]
... cut until z-60 feed=0.08mm/rot
... rapid to clearance position
... [ monitoring off ]
... turret at home position

or please, can you provide a code that uses load monitoring ?

also, considering that this is an option, is it possible to check if that option is installed ? kindly