Quote Originally Posted by Neale View Post
...

Back to the macro and start reading the code more carefully. I find something I've never seen before - the SetInputData command. Can't find any documentation on it, except for a single comment that it seems to have been introduced in version .066 - the last one released. The comments in the macro code around it give me a clue - it appears to select a specified port and pin for the Probe input. This is probably why I was seeing the probe input definition changing during testing. I keep the TH macros as they are, and modify the probing macros (I'm using the Probe Wizard freeby set for probing) to use the same command but switching to the external "probe" pin before G31 is called. And now, when I run a TH macro, it uses the TH setter on the machine bed, and when I run a probing macro (any of the dozen or so that I had to modify), it uses the probe input. Magic!

...
Hi Neale,

I got exactly the same problem. I tried to user the "SetDataInput(22,12,0) " in a m1s launched thru a Version R3.043.066 FR, but unfortunately i got a "scripter compile error". Can SetDataInput be integrated into a m1s macro file? Is it my french version who do dot support SetDataInput?

FYI, it seems first parameter is Mach3 pin, not ESS pin. If you open the machine definition file (XML), you'll see 22 seems to be the probe input.

I know this is an old thread, but thank you per advance of your answer, and sorry for my poor english :). Fortunately i'm better in French :)..