Hello everyone,

I just upgraded my highly appreciated Mach3 / parallel port driven mill to a PoKeys57CNC device. 

Unfortunately, although probing seemed to work fine on a first sight (probe connection works, G31 command is executed nice - machine stops as soon as probe is triggered) I've got a strange problem: the #2000 to #2005 variables, which should contain the probe trigger coordinates, are all "0" after execution of G31 command.   

TriggerPointX = GetVar(2000)
TriggerPointY = GetVar(2001)
TriggerPointZ = GetVar(2002)

--> To get machine running again, as I had to get some work done on it, I changed the relevant probing script to do the probing veeery slooow and polled the according X, Y and Z DROs, which is suitable as a temporary solution.

So, my question is:
- Who exerienced similar probing trouble with a PoKeys57CNC board.
- Maybe, PoKeys plugin has an own place to put the trigger coordinates to, which I don't know.
- Did I misconfigure Mach3 or PoKeys plugin, so probing basically work, but the plugin isn't able to write the trigger coordinates to the according variables

I'm happy about any help or Information.

regards, Konrad

Update:
PoKeys published an updated plugin an hour ago, which should improve the reporting of probing results to the Mach3 system variables. 
Wow, they're fast... 

I will not be able to test this before the weekend, as I am not at my workshop at the moment.


Have a nice evening,
Konrad

Update again - Testing is done:

It works! PoKeys fixed the trouble with their plugin Version 3.12, after which the probing Trigger coordinates are properly written into the according Mach #2000 to #2005 -variables...


3.12 - 5.10.2017
- probing reporting to Mach3 improved

3.11 - 5.10.2017
- PoKeys device does not switch to STOPPED mode before doing the axis homing


And: The PoKeys guys are really fast. - My appreciation!  :-)