fixing M61 to actually make sense I came across the following issue:
- let's assume a tool is in the spindle
- there IS an automatic toolchanger - either random or non-random
- an M61 Qx is executed
This looks fine for manual toolchange - no pockets used here.
With automatic toolchangers it's not so nice:
Q: where does the tool-in-spindle go?
a) it is removed from the changer entirely, hence cannot be loaded anymore (!)
b) it is put into an empty pocket - which one?
c) it is swapped with some other tool - the x chosen with Qx?
Looks like c) is the best option in the current setup - or b) with an
additional parameter like so:
M61 Q<new tool> P<pocket to unload spindle tool into>
meaning:
<new tool> is loaded into spindle
if there was a tool in the spindle, it is assigned the pocket of the P
word
--
What I would like add
- permit 'unloaded tools' in the tool table (like having pocket=-1)
- define a 'G10Lx' command which enables setting a pocket for a tool
with that in place, an M61 Qx could follow either a) or c), and the
tool-in-spindle
loaded into any pocket like so
(example: tool 5 goes into spindle, tool-in-spindle goes to pocket 10)
#<t> = #5400
M61 Q5
o100 if [[#<t>] NE -1]
G10 L3 T#<t> P10
o100 endif
This would permit defining a 'loading' (set of tools in given changer pockets)
all from G-code, without fiddling the tool table; plus retaining tools which
arent currently loaded - including geometry, comments and all
Opinions on those ideas?
-Michael
ps: I have already removed the current data dependency in the tool table -
which requires each tool to have a current pocket (0...MAX_POCKETS) so
permitting a pocket value of -1 in the tool table is not an issue
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
