1
General Mach Discussion / Getting Auto Tool Zero Operation to Work in Mach3
« on: September 05, 2023, 01:19:48 PM »
I've had a difficult day trying to get this operation to work in my Mach3 setup. I have three scripts which I have tried and all work except for not adding the gauge offset when the probe touches. The three scripts all date from around 2010 and all of them access the Gauge Block DRO with the code "GetUserDRO(1151)". When I single step through the scripts, the value from this operation is zero.
The screen I'm using is one supplied by support for Seig KX1/3 machines in the UK and I suspect that the work wasn't quite completes from a remark left in the script area of the Auto Touch button. :-) I wondered if an OEM code wasn't attached to the DRO, or whether a different one had been attached. I've spent the afternoon trying to see if I could get some information using MachScreen to investigate the screen, but absolutely nowhere. It's not often that a bit of software beats me. :-)
I also picked up that OEM codes may have changed over the years and a more recent list of DRO OEM codes I accessed did not have a code 1151 in it.
Any suggestion on how I can find out what's going on.
I also tried Screen4 to investigate the screen but that software just hung up, even in compatability mode.
I'm running Version R3.043.062
Jim.
The screen I'm using is one supplied by support for Seig KX1/3 machines in the UK and I suspect that the work wasn't quite completes from a remark left in the script area of the Auto Touch button. :-) I wondered if an OEM code wasn't attached to the DRO, or whether a different one had been attached. I've spent the afternoon trying to see if I could get some information using MachScreen to investigate the screen, but absolutely nowhere. It's not often that a bit of software beats me. :-)
I also picked up that OEM codes may have changed over the years and a more recent list of DRO OEM codes I accessed did not have a code 1151 in it.
Any suggestion on how I can find out what's going on.
I also tried Screen4 to investigate the screen but that software just hung up, even in compatability mode.
I'm running Version R3.043.062
Jim.