Probe_basic Toolchanger

Hello I have set the Varibales in my var. so got it work. but i have other problems right now...

The changer does not always switch to the correct tool, especially when the direction is changed.

Which toolchange.ngc is the current one? I was surprised that I had two different ones...

Are there any other changes to the associated sub-programs?

Then another question, is there a script that allows the machine to record a tool at a specific XY coordinate if it is not in the changer?

e.g. T9 is in the spindle

T3 Should be fetched but T3 is not in the changer.

So he should bring tool 9 back into the changer and then move to XY0 and request a tool change.

Of course the same goes the other way around.

Request tool change because tool 3 was not in the changer XY0 and then go to the changer and get T3 again

github.com/dpslwk/starmill-linuxcnc/raw/...tines/toolchange.ngc
that should be a good version, I suggest comparing it to the one you are running for changes before just overwriting it

unfortunately there are multiple copies of the routines in PB's github, something I'm working to clean up and condense.


Probe Basic's current M6 remap `toolchange.ngc` only supports tools in the ATC
you would need to adapt it yourself to handle mixed atc and manual changes

ok thanks got the normal toolchange.ngc work...

so i will try my luck for mixed atc manual toolchange code

by the way. why can i not set my pockets manual for the tools in the tooltable???

can set pocket 1 for tool 3 in tooltable but at store tool in changer the changer stores tool 3 in pocket 5

PB's included ATC routines do not use the pocket entries in the lcnc tool table at all, they use the numbers parameters to store that information, which is one huge hurdle implementing a mixed ATC/manual tool change routine
I have opened an issue to track this as a new feature / improvement request github.com/kcjengr/probe_basic/issues/95

current routines use the following numbers parameters
; Parameter #5171 is used to track if the carousel is homed (M13) (volatile)
; Parameter #5170 is used to track the current tool pocket (persistently)
; Parameter #5231 is used to track the current tool loaded it in the spindle (persistently)
; Parameters #5191 to #5202 are used to track which tool is in which pocket (persistently)
; Parameter #5190 is not populated just used in the maths to calculate the above numbers


how ever I have an open PR that will move them to
; Parameter #3989 is used to track if the carousel is homed (M13) (volatile)
; Parameter #3990 is used to track the current tool pocket (persistently)
; Parameter #3991 is used to track the current tool loaded it in the spindle (persistently)
; Parameters #4001 to #4024 are used to track which tool is in which pocket (persistently)
; Parameter #4000 is not populated just used in the maths to calculate the above numbers

Re-doing the PB tool table connection is a really nice idea.  Being able to use carousel.comp would be great, and untangling the atc macros took me forever.

Thank you.

Work in progress readme for the ATC routines here
github.com/dpslwk/probe_basic/tree/subro...iles/probe_basic/atc