Re: re-starting in the middle of a program?
hy jay_dizzle i saw your post yesterday, and i was going to tell you a few things, but only now i have a bit of free time / time is my enemy
on a "dual cnc", at least 2 similar organs exist : at least 2 turrets, or at least 2 spindles ( 2s+t , 2t+s , 2st )
those similar organs :
... may cut free, independtly : single machining state
... may be linked : dual machining state
for example, if you cut a part, on a 2s+t cnc, 1st spindle + transfer + finish it on 2nd spindle, then :
... during transfer, cnc is in "dual machining state" ( both spindles are synced, thus 2 similar organs are linked )
... otherwise, cnc is in "single machining state" ( because similar organs are no longer linked )
program / code is splitted by checkpoints; if the cnc is :
... simple, thus there are no identical organs, then the checkpoints are the common NAT** addresses, that split the code between consecutive sequences ( turret index, etc )
... dual, thus there are identical organs, then the checkpoints should split the code each time a "dual machining state" is changing ( including turned on or off )
from this perspective, a NAT** adreess should be between "single machining states", and a P code should be between "dual machining states"
"dual machining state" = 2 linked "single machining states", so, put a NAT**/NT**/NN** before a P
some programmers are inserting the P codes using excel, so to view the code side-by-side for each organ
some cnc controllers allow this behaviour, thus they can arrange the code side-by-side, accordingly to the existing "dual machining state" codes; this allows the operator to view&edit the code from a different perspective, thus he can oversee the "dual machining state" arhitecture of the program; i don't know if this is possible on osp
okay, so far so good, at least 4 me; i hope that this is useful, or at least there is a bit of sense to it
now, about restart sequences on dual organs : it may be tricky, but the checkpoints have to be created in such a way, that both organs are at clearance position when a restart sequence is performed, otherwise, 1st turret may start approaching, and 2nd turret may crash into the part if there is an id tool ( boring knife, drill, etc )
is easy to create a program for a dual cnc without considering the restart checkpoints
i was told that some programmers, after creating the program, are creating a few copies, and each copy has some custom P codes and NAT**, so to handle a particular failure on a specific tool; it works, but it requires time, and this is a solution for long-term setups, that are not stable ... in other words, those custom programs are about changing the "timing", so to achieve clearance position on both turrets; is kind of a "maintanance" program
if cycle time is short, maybe you can simply trash the part and start all over again
if you enable eco-suite, regardless off "single-block", or "manual-intervention" state, and auto-timer is reduced ( check attached ), you will restart more often in mid-process / kindly
Ladyhawke - My Delirium, https://www.youtube.com/watch?v=X_bFO1SNRZg