Tweaked Probe Basic UI fails to launch
27 Oct 2022 23:30 #255258
by andypugh
Replied by andypugh on topic Tweaked Probe Basic UI fails to launch
I have been playing about with it trying to answer another forum post, and the answer seems to be "yes, but"
A T-command does populate #<_selected_tool> and #<_selected_pocket> correctly.
But if you _remap_ T then you don't get these parameters passed in to the T remap. Which is rather a pain for a lathe tool remap.
It's not the end of the world, as a Python prolog can be used to get the info. (And maybe I am missing something)
A T-command does populate #<_selected_tool> and #<_selected_pocket> correctly.
But if you _remap_ T then you don't get these parameters passed in to the T remap. Which is rather a pain for a lathe tool remap.
It's not the end of the world, as a Python prolog can be used to get the info. (And maybe I am missing something)
Please Log in or Create an account to join the conversation.
27 Oct 2022 23:44 #255260
by andypugh
Replied by andypugh on topic Tweaked Probe Basic UI fails to launch
By the way, "carousel" gets the pocket number from a HAL pin, not a G-code parameter. It should just work with iocontrol.0.tool-prep-pocket connected to carousel.0.pocket-numberThat would simplify things greatly if it works like that. Carousel could be given the value of #<_selected_pocket> and it just goes there with no fussing or macro gymnastics.
Please Log in or Create an account to join the conversation.
28 Oct 2022 01:16 #255266
by spumco
So based on the above, a tool change .ngc file could be even simpler - just the various head/slide/drawbar movements, safety checks, and the carousel enable signal(s).
I'll have to try this one out and see if my existing sequence can be vastly simplified.
Last question for this tangent: what updates the tool table pocket number when a tool is installed in the spindle then put away in the carousel?
Replied by spumco on topic Tweaked Probe Basic UI fails to launch
As usual, I mimremembered the connection scheme and phrased it inexpertly.
That would simplify things greatly if it works like that. Carousel could be given the value of #<_selected_pocket> and it just goes there with no fussing or macro gymnastics.
By the way, "carousel" gets the pocket number from a HAL pin, not a G-code parameter. It should just work with iocontrol.0.tool-prep-pocket connected to carousel.0.pocket-number
So based on the above, a tool change .ngc file could be even simpler - just the various head/slide/drawbar movements, safety checks, and the carousel enable signal(s).
I'll have to try this one out and see if my existing sequence can be vastly simplified.
Last question for this tangent: what updates the tool table pocket number when a tool is installed in the spindle then put away in the carousel?
Please Log in or Create an account to join the conversation.
29 Oct 2022 22:20 #255411
by andypugh
Replied by andypugh on topic Tweaked Probe Basic UI fails to launch
I think it is iocontrol that shuffles the internal database. I am not sure when that get written out to the tool file.
Last question for this tangent: what updates the tool table pocket number when a tool is installed in the spindle then put away in the carousel?
The following user(s) said Thank You: spumco
Please Log in or Create an account to join the conversation.
30 Oct 2022 02:21 #255418
by spumco
Replied by spumco on topic Tweaked Probe Basic UI fails to launch
Thanks. When I get the screen sorted out and back on finalizing the ATC, I'll continue in my other mega-thread and report back.
Please Log in or Create an account to join the conversation.
Time to create page: 0.119 seconds