Gentlemen,
Just my two cents
Backing up the interpreter past a tool change is something I have never
seen and believe would not be useful at all.
OT - I have heard of (but never personally) a shop owner asking the
question of a paper tape as follows - "If I put the tape in backward will I
get mirror image part?".
OK - back to the subject
I think backing up the interpreter should be restricted to only a few lines
and certainly not past the most recent tool change.
Worrying about the state of the feed rate override because you may not get
the exact same path is not something to worry about. The program is the
desired path. I have never seen anyone program an incorrect path just so
they could use the feed rate override to modify the programmed path and cut
the desired (mythical) path.
The last 5 (insert your desired number) lines should be remembered for
backing up through the program. This should not be allowed to go very far
back (maybe not past the immediately previous rapid move). There would be
no need to remember the state of coolant, spindle or anything but the
motion of the tool.
This 'feature' would be useful at times and some operators may use it a lot.
thanks
Stuart
--
dos centavos
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
