Jog on tool change (or on pause) should be straight forward. At the pause, simply remember each of the jogs. Then when resume is executed, play them back in reverse order.
I believe that all of this can be done with HAL components. This would NOT solve the touch off problem. One could, of course, use an offset HAL component that could be used as part of a touch off. Ken On 5/17/2010 6:12 AM, Lester Caine wrote: > Andy Pugh wrote: > >> it seems that the reason that jog-on-tool-change is possible is that >> the motion controller stops there anyway (and expects to stop there). >> I guess this means that jog-on-tool-change is relatively easy, though >> perhaps it needs to refuse to restart unless it is at it's "safe >> retract" position to save the risk of wiping out clamps and work on >> the way back from the touch-off fixture. >> > This is, I think, the crux of the problem. It is not so much the 'current > position', but that the trajectory planner simply does not have enough > information to work on when stopped 'mid flow'? > > It should be possible to tag 'safe' points, but as has been pointed out, these > could be some time or distance from the actual current cutting point. Even dry > running will not necessarily get to the same point, and invariably there will > be > a 'mark' of some sort where the cutter picks up again in the work simply > because > it is not now cutting up until that point. > > Steve ... I think the main problem here is not so much that nobody wants to do > it, but rather nobody can get their head around the mathematics to work out > HOW > to do it ;) Perhaps we need to flag possible 'stop points' through the code > where the trajectory planner can work from? Virtual tool change points ;) > > -- Kenneth Lerman 55 Main Street Newtown, CT 06470 203-426-3769 ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users