[netboss]

If I understand correctly, the array persist.UserData[] is used to pass data to KMotion about Mach3. Amoung the data is button presses, or at least the HOME buttons.

Again, if I understand correctly persist.UserData[5] contains data about the press of the HOME buttons, with bit 0 representing the X axis, bit 1 representing the Y axis and bit 2 representing tne Z axis.

I have a couple of questions about this process.

1. Is there a list of all bits/bytes in persist.UserData[] that represent data from Maxh3, the list showing the bit/byte location and the meaning.

2. How is a bit within persist.UserData[] reset. IOWs, if byte 5, bit 0 is set to indicate that the X Home button has been presed, how is it reset?

[TomKerekes]

Hi netboss,

The persist.UserData[5] variable isn't directly related to key presses. Whenever Mach3 decides homing should be performed for whatever reason it sends a message to the plugin which includes what it calls a "flags" variable which it sets to specify which axis or axes should be homed. Our plugin then places the "flags" value into any KFLOP persist.UserData[] variable of your choice and invokes any C Program of your choice into any KFLOP Thread of your choice. The C Program should read the variable to decide which axes it should home. You may specify the Variable, Program, and Thread to be used when homing in the Mach3-Dynomotion Plugin Configuration Screen.

The persist.UserData[] variables are actually 32-bit integers not bytes.

There isn't any need to reset the variables. They will be overwritten with new data for any future purpose.

HTH
Regards