G54 G55 G53 Problem

Are you use Gmoccapy?

He's using the ProbeBasic GUI

Did you sort this out?

for atc work the position needs to be hardcoded in the subroutine or an ini setting created and added for the toolchange position.  linuxcnc does not allow pulling in ui parameters during remap unfortunately, i suspect this is what you are dealing with.  your atc parameters need to be hardcoded in the subs and done in G53 and your toolchange macro need to be using G53 anytime your doing toolchange functions.  work offsets should only be used for program offsets.

Chris

yes i´m sure i have set my g53 coordinates for the toolchange hardcoded but as variable in the ini.

i don´t have any problems when i only have a g54 offset...

my programm was running fine with g54 and g55 but at the resart of my machine and after homing the toolchange position was incorrect.

CNC_ANDI post=291970 userid=33414yes i´m sure i have set my g53 coordinates for the toolchange hardcoded but as variable in the ini.

i don´t have any problems when i only have a g54 offset...

my programm was running fine with g54 and g55 but at the resart of my machine and after homing the toolchange position was incorrect.

your subroutine on page one where you set G53 coordinates doesn't seem right, the only time you should be calling those coordinates are when you need G53 moves for atc positioning. and you should never be "setting" g53 after homing.  

but with out the rest of the routine its hard to see where you are creating the error.  the sim works as expected, my machine works as expected, so it is probably something pretty simple in your subroutine.  also remember that the parameters in the ui are useless in your scenario since you need the hardcoded parameters.  be sure to uncheck that option and clear those registers so they don't add to the troubleshooting issue.

ok please tell me which files do you need and i will post them.

check you ini file to see if you are commanding a goto move on toolchange there. may be in conflict with the subroutines. just check through all of your files and try and find the offending commands.