Issues using G53 or G92.2 in Tool Change Script
Posted: Mon Apr 26, 2021 5:43 pm
Hi everyone,
I've got a Buildbotics controller hooked up to my Taig mill and I'm using a toolsetter probe between tool changes to automate the process of measuring new tools for jobs with multiple tools. The probe sits at a fixed point in machine coordinates (I just bolted it to the table), so I am trying to either use G53 to move in machine coordinates or G92.2 to temporarily disable global offsets so that I can then move to the probe position in machine coordinates. For context, I do have homing switches setup on my mill. The problem I'm running into is that the Buildbotics controller does not respect G53 or G92.2, it's as if it's still trying to move in work offset coordinates. Because of this, when I have the work offset set closer to the upper limits of the axes, the controller will say that the job will move outside some axes bounds (even though it won't, since on the toolchange it will be moving in machine cooridinates), and thus I can't start the job. Has anyone else had this error and possibly know how to fix it? Thanks!
I've got a Buildbotics controller hooked up to my Taig mill and I'm using a toolsetter probe between tool changes to automate the process of measuring new tools for jobs with multiple tools. The probe sits at a fixed point in machine coordinates (I just bolted it to the table), so I am trying to either use G53 to move in machine coordinates or G92.2 to temporarily disable global offsets so that I can then move to the probe position in machine coordinates. For context, I do have homing switches setup on my mill. The problem I'm running into is that the Buildbotics controller does not respect G53 or G92.2, it's as if it's still trying to move in work offset coordinates. Because of this, when I have the work offset set closer to the upper limits of the axes, the controller will say that the job will move outside some axes bounds (even though it won't, since on the toolchange it will be moving in machine cooridinates), and thus I can't start the job. Has anyone else had this error and possibly know how to fix it? Thanks!