Probe_basic Toolchanger

More
20 Nov 2023 19:15 #286085 by dpslwk
Replied by dpslwk on topic Probe_basic Toolchanger
are you referencing your changer first, as that routine not only homes the carousel but repopulates the UI

the bundled subroutines store which pocket holds which tool in the variables
5191>5202
The following user(s) said Thank You: CNC_ANDI

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

More
20 Nov 2023 23:13 #286112 by CNCaddict.1970
Please share your var file and your current toolchange.ngc. let's see if you have the correct variables set so it saves the tools.

As a recent coming change is happening for the parameters used in toolchange.ngc, we need to see which toolchange.ngc you are using. Based on that you will have to add some variables to linuxcnc.var file. So it has a place to store your tools.

It's actually really not difficult. It's the understanding what needs to be set to work that can be hard :)
The following user(s) said Thank You: CNC_ANDI

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

More
21 Nov 2023 16:33 #286181 by CNC_ANDI
Replied by CNC_ANDI on topic 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

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

More
21 Nov 2023 17:19 #286184 by dpslwk
Replied by dpslwk on topic Probe_basic Toolchanger
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
The following user(s) said Thank You: CNC_ANDI

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

More
21 Nov 2023 19:10 - 21 Nov 2023 19:12 #286187 by CNC_ANDI
Replied by CNC_ANDI on topic Probe_basic Toolchanger
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
Last edit: 21 Nov 2023 19:12 by CNC_ANDI.

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

More
21 Nov 2023 20:08 #286189 by dpslwk
Replied by dpslwk on topic Probe_basic Toolchanger
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
The following user(s) said Thank You: spumco, nwallace

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

More
21 Nov 2023 20:24 #286191 by spumco
Replied by spumco on topic Probe_basic Toolchanger
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.

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

More
21 Nov 2023 21:03 #286195 by dpslwk
Replied by dpslwk on topic Probe_basic Toolchanger
Work in progress readme for the ATC routines here
github.com/dpslwk/probe_basic/tree/subro...iles/probe_basic/atc

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

More
23 Nov 2023 06:21 - 23 Nov 2023 15:31 #286305 by CNC_ANDI
Replied by CNC_ANDI on topic Probe_basic Toolchanger
Yeah good idea.

By the way i have replaced the hardcode too.

I hate this to open 25021 files for change one thing.

Changed every hardcode to <#_ini[ATC]XXXX> params

So i can do all changes for coordinates, speed, pins in the ini

youtube.com/shorts/aSQBl6aripY?si=c-Hw2SXOMTkKsj0-
Last edit: 23 Nov 2023 15:31 by CNC_ANDI.

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

Moderators: KCJLcvette
Time to create page: 0.134 seconds
Powered by Kunena Forum