Problem Definition
The required result is to control three existing Mach3 auto tool probing screen functions from a ShuttlePRO v2: -Z, inside, and outside. The available evidence confirms that the operator attempted to use the Mach3 VB editor, but it does not include the working macro, command identifiers, button codes, or remote configuration.
Required Function Mapping
| Remote function | Target Mach3 screen function | Implementation data available |
|---|---|---|
| -Z control | -Z auto tool probe button | Function name only |
| Inside control | Inside probing button | Function name only |
| Outside control | Outside probing button | Function name only |
Do not infer that these three buttons use interchangeable logic. Each remote input must invoke the exact action assigned to its corresponding screen button.
Configuration Decision Path
The evidence states that a solution was found, but it does not document that solution. An exact macro therefore cannot be reconstructed reliably. Before configuring the remote, identify the action currently executed by each on-screen button and determine whether the installed ShuttlePRO-to-Mach3 integration accepts that action directly or requires a VB macro.
- Inspect the existing -Z, inside, and outside screen buttons and record the action associated with each one.
- Determine the input or button assignment generated by each selected ShuttlePRO v2 control.
- Map each remote input to the matching screen action using the integration method already installed.
- If a macro is required, reproduce the recorded screen-button action without substituting guessed command identifiers or VB syntax.
Verification and Missing Data
Verify each mapping independently by comparing the remote-triggered result with the corresponding on-screen button. The implementation is complete only when each remote control invokes its matching function and does not invoke either of the other probing operations.
To produce executable code, the missing evidence must include the existing screen-button actions, the ShuttlePRO button assignments, and the configuration or macro interface exposed by the installed integration. Mach3 version, plugin version, timing, and command identifiers are not provided.
FAQ
How do I assign a ShuttlePRO v2 button to Mach3 auto tool probing?
First identify the exact action used by the existing probing screen button, then assign the selected ShuttlePRO input to that same action through the installed integration. The evidence does not provide the required command identifier or macro syntax.
Can one Mach3 VB macro control the -Z, inside, and outside probe buttons?
The evidence does not establish that the three functions share one macro or command. Treat them as separate mappings until their existing screen-button actions confirm otherwise.
What information is needed to write the ShuttlePRO Mach3 macros?
Record the action behind each -Z, inside, and outside screen button, the remote input assigned to each control, and the interface supported by the installed ShuttlePRO integration. Without those details, executable code would require unsupported guesses.
