Hardinge HXL Tool Turret
- microsprintbuilder
- Offline
- Elite Member
- Posts: 163
- Thank you received: 4
Please Log in or Create an account to join the conversation.
JT
Please Log in or Create an account to join the conversation.
- microsprintbuilder
- Offline
- Elite Member
- Posts: 163
- Thank you received: 4
Please Log in or Create an account to join the conversation.
JT
Please Log in or Create an account to join the conversation.
- microsprintbuilder
- Offline
- Elite Member
- Posts: 163
- Thank you received: 4
Please Log in or Create an account to join the conversation.
When you first start up LinuxCNC it does not know what tool is loaded physically. So you will have to issue a Tn M6 G43 at startup.
There is almost certainly a way of doing this automatically.
Arguably it should be built-in. The way that tools are handled in LinuxCNC is open to some improvement, and we are working on it.
Please Log in or Create an account to join the conversation.
BigJohnT wrote:
When you first start up LinuxCNC it does not know what tool is loaded physically. So you will have to issue a Tn M6 G43 at startup.
Andy Pugh wrote:
There is almost certainly a way of doing this automatically.
What I have done with 3 different toolchanger components that start in an unknown state, is to change iocontrol.
I added a pin to receive the current tool number and a bit flag to trigger an update.
This triggers iocontrol to issue a tool change instruction for the given toolnumber.
Because the tool change component knows that tool is already current, it just returns a toolchanged signal and the toolnumber is automatically updated.
I don't know anything about classic ladder, these were realtime components.
If classic ladder can set HAL pins, the same could be used.
regards
Please Log in or Create an account to join the conversation.
What I have done with 3 different toolchanger components that start in an unknown state, is to change iocontrol.
Which is a pretty strong argument for why toolchanger behaviour does not belong hardcoded into iocontrol (and that is on the list of things to change)
Please Log in or Create an account to join the conversation.
Any idea why I would have to do it twice? It like it's not updating. When I get home tonight I'm going to print out your files I have and compare them to mine again.
My WAG is your logic is not correct in the ladder. Watch iocontrol.0.tool-changed in a watch window as you change tools. Axis should update as soon as it goes true. Actually put all the iocontrol tool bits in the watch window as you change a tool.
JT
Please Log in or Create an account to join the conversation.
- microsprintbuilder
- Offline
- Elite Member
- Posts: 163
- Thank you received: 4
Please Log in or Create an account to join the conversation.