Positioning for toolchange - var code for Vetric

I'm working with Vetric Aspire.
I've been bewildered by an issue with locating my spindle in a good place for doing a manual tool change in a PP with ATC.
I have everything working as I would like, but it would be helpful if the spindle went to XH YH ZH to do the tool swap.
I have tried every VAR in the manual, when using the home position that's available to me, and then I trying to load the ngc file, LCNC errors me out with the old:
"Radius to end of arc differs from radius to start". (I really hate that one)

I have the required digits for Imperial (a common cause) so no worries there.

Can anyone give me some guidance on how I can do this?

Thanks for any help

Command a g53 position for your tool change

Or you can find some info here:
linuxcnc.org/docs/2.7/html/config/ini-co....html#_emcio_section

allenwg2005 wrote:

I'm working with Vetric Aspire.
I've been bewildered by an issue with locating my spindle in a good place for doing a manual tool change in a PP with ATC.
I have everything working as I would like, but it would be helpful if the spindle went to XH YH ZH to do the tool swap.
I have tried every VAR in the manual, when using the home position that's available to me, and then I trying to load the ngc file, LCNC errors me out with the old:
"Radius to end of arc differs from radius to start". (I really hate that one)

I have the required digits for Imperial (a common cause) so no worries there.

Can anyone give me some guidance on how I can do this?

Thanks for any help

In your ini file, you can set toolchange_position.

actually in your ini use:

TOOL_CHANGE_QUILL_UP =1 to move the Z axis up
TOOL_CHANGE_POSITION = 0 0 to move x and y

that should move the Z up then X and Y to whatever position you put.

I had forgotten about doing this in the LCNC ini file.
It's been many years past that I tinkered with my ini, (Maybe a decade now).
I have TOOL_CHANGE_POSITION = 1 1 1 in my ini,
I have forgotten a great many things to make this work and I don't have time to read the entire manual (I spent days dealing with the Vetric manual and PP.

Can someone point me to were the manual explains the numbers and how to get it to work.

If I get the same error when loading how will I know if it's the ini or something else? (That error code can be a little difficult to sort).

allenwg2005 wrote:

I had forgotten about doing this in the LCNC ini file.
It's been many years past that I tinkered with my ini, (Maybe a decade now).
I have TOOL_CHANGE_POSITION = 1 1 1 in my ini,
I have forgotten a great many things to make this work and I don't have time to read the entire manual (I spent days dealing with the Vetric manual and PP.

Can someone point me to were the manual explains the numbers and how to get it to work.

If I get the same error when loading how will I know if it's the ini or something else? (That error code can be a little difficult to sort).

What error code?

You want the docs for the ini? => linuxcnc.org/docs/devel/html/config/ini-...html#_emcmot_section
That's devel. Don't know what version your running.

As I expected I would need to spend quite some time to sort this using the manual.

TOOL_CHANGE_POSITION = 0 0 to move x and y

Can I put X & Y home with 0 0?

you can use G30
as it is against the G53 Homing position
see definition
www.linuxcnc.org/docs/html/gcode/g-code.html#gcode:g30-g30.1

As I expected, once I head down this path in no time I'm in the weeds.
I don't know how to code, and there are so many things to look out for, cause and effect, things you need to anticipate, for example:

"G28 Example Line

G28 Z2.5 (rapid to Z2.5 then to Z location specified in #5163)

It is an error if :

Cutter Compensation is turned on"

G30 has the same warning.
I use cutter compensation at times, so how do I deal with that? (A rhetorical question).

I'm sure for many of you out there this is like falling out of bed, stupid simple, that's not the case here.
With the coding knowledge required, you best take the time and read the entire manual or you will spend more time making a mess and cleaning it up than just reading through it in the first place.
I don't have time for this, but, if you want to play you gotta pay.
I'm off to the docs pages, I'm sure I'll need help regardless, I bet I'll be back with lots of questions.

Thanks for the help so far.