Originally Posted by
broby
Code:
N1006 G0 Z800 G97 S1102 M63 (Rapid to tool change position on Z axis only, Setting up spindle speed for next operation)
N1007 X52 Z800 T020202 M65 M66 (move to next start point on X axis, KEEPING tool firmly on Z axis home position to ensure safety, use M66 to specify free turret indexing when not home and M65 to not confirm tool change has done)
N1008 X52 Z52 T020202 (IMPORTANT!... Confirm tool index by re-specifying the same tool number)
You MUST confirm that the selected tool is in position prior to moving in to the start point for machining as you can imagine the crash occurring if the turret is still rotating when positioned near the part/chuck!
hy broby i know that text that i quoted is from 2016bc, but there is a case when confirming T can be done "at the start point ( clearance position )", instead of " prior to moving in to the start point "
for example, if there is a single long drill, and all other tools are normal face knifes, i can use next code without worries :
Code:
home position
G00 X0 Z2.5 T=drill M65
T confirm ( only confirmation, no linear movement occurs )
// in this case, at this position, i can rotate the turret for a full revolution without worries
it is only a particular case, and, even if it works, it does not occur frequently, so maybe it does not sound reasonable to be used in reality
ok, now, please, let's consider another example : there are 2 identical face knifes ( T1_rough & T2_finish ), and all other tools are long drills; only when i index from T1 to T2, i can use this code :
Code:
cutting with T1
home position
G00 X0 Z2.5 T2 M65
T2 confirm ( only confirmation, no linear movement occurs )
// in this case, at this position, i can rotate the turret for a 360/12 degress, thus only for a single index
again, it is only a particular case, and, even if it works, it does not occur frequently, so maybe it does not sound reasonable to be used in reality
so, even if there are cases that allow confirming T at clearance position, instead of " prior to moving to clearance position", their probability of occurrence is questionable; main answer is "better be safe than sorry", so, looking from this perspective, your approach, your code, seems ok
the dynamic indexing code, that i developed, is a "live?" code, that adapts even after small offset changes, like 0.001 ( uses system variables ), and "decides" where to send the turret for next index sequence, and also checks if it can perform an on-the-fly index, by using M65; in other words, it raises the probability of occurence ... and onestly, i don't know where it will index precisely, and this "unpredictible" side is what i like about it ( there are safe boundaries, that are always changing )
Originally Posted by
OkumaWiz
Repeating the T command only slows things down
yup, this is true, there is a downtime created by repeating the T command
since how i can confirm the T at clearance position, and not before approaching it ( i can approach+M65 without broken vector), i simply reduce the downtime by repeating the T command inside a block that contains a feed movement
Code:
home position
G00 clearance position T M65
G01 T=confirm
even if a code is using M65 and it is collision-free, there are some things that need to be considered, so to speed up the cycle time, but this is a story for another time / kindly