The way I’ve handled this in the past is to create a VC4 visualization that’s just used to map the buttons (keys). You can create a key for each button, and use those keys to set datapoints (process variables). This will run in the background even though you’re actually using mappView for the display.
There might be a different method available in AS6, but that is how I’ve usually mapped the push buttons on the AP5000 panels, and I believe the same method can apply to the mobile panels.
In such usecase, please note it is imperative to implement a reset mechanism for the keys in case the communication between the mobile panel and the mappView server is lost, thereby preventing an infinite axis jog. This can be achieved by monitoring a variable such as clientInfo.isValidSystem Variables.
Please note that not all keys are functional by default. Modifying the KCM file Key Configuration may allow for additional key assignments, though I have not yet had the opportunity to test this myself (yet).