Can Linux CNC control twin turrets?

More
14 years 6 months ago #19075 by robh
on superlsant, i have X and Z
then bottom is W

so both turrets have there own offsets etc


sounds very nice machine u can get your self there.. im sure there is afew ways to go about this depends how much time you have etc..
might want to put this out on the mailing list also to see what ideas you can get back

rob

Please Log in or Create an account to join the conversation.

More
6 years 5 months ago #168695 by nkp
If we need alternate work.
Is it possible to apply such a scheme?
Switch mux-demux allowed only if turret1 and turret2 in zero position.
(tool_change_position_turret1 = tool_change_position_turret2 = home_pos = (0,0))

Please Log in or Create an account to join the conversation.

More
6 years 5 months ago #168699 by cmorley
Once about a time there was an experimental branch of linuxcnc that could have two instances of linuxcnc on one machine.

The developer that did that started Machinekit, so maybe that capability got into machinekit. Then it would be a case of synchronization.

Please Log in or Create an account to join the conversation.

More
6 years 5 months ago #168700 by nkp
Synchronous operation is not of interest at the moment, only separate.

Please Log in or Create an account to join the conversation.

More
6 years 5 months ago #168775 by andypugh
It is possible to run more than one instance of the "carousel" component, to control different tool turrets for changing the tools.
If you are content to run one tool slide as XZ and the other as UW then LinuxCNC can also move both tools.

What that scheme doesn't allow you to do is to start a long turning pass in W while at the same time threading in Z (for example). G-code lines all run in strict sequence and all axes arrive at the end point at the same time.

For special purposes I can imagine running some axes outside of the interpreter using simple_tp but that is not really an answer for general machining.


Using multiple instances of "carousel" would be simplified if the component could be configured to ignore tool numbers outside its range. This is a simple fix. I think that an extra pin "base number" would do all that is needed. Then the component would quietly ignore any input number < base or > base + pockets. (rather than rely on hal wiring to achieve the same thing)
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
6 years 5 months ago #168780 by nkp
My idea: use only 2 axes(XZ), and switch depending on the tool number.
Do you think it will work?

Please Log in or Create an account to join the conversation.

Time to create page: 0.213 seconds
Powered by Kunena Forum