Excuse my ignorance. The G Code selects a tool by #. The operator has placed
the tools into the numbered positions for the tool changer.
Now here I guess it gets interesting. Most efficient would be if the G-Code
Parser read ahead and signaled the tool changer object that it will need tool
I've seen some that have each tool holder coded and read the holders in the
chain or carousel as it moves. The system has no idea where any of the tools
are but it does know the difference between an empty spot and one with a tool.
So when a tool is requested it just runs the carousel or chain
On 01/06/2019 10:54 AM, Kenneth Lerman wrote:
To clarify the question:
With this type of tool changer, one could speed up the tool change delay:
1. when loading a tool
1. unload the previous tool into one side of the arm
2. move the chain so that the new tool is ready to be
To clarify the question:
With this type of tool changer, one could speed up the tool change delay:
1. when loading a tool
1. unload the previous tool into one side of the arm
2. move the chain so that the new tool is ready to be loaded (if not
already there)
3. grab the
