How do I map a physical key to a function key or macro?
You tap Menu -> Settings -> Keyboard setup -> KEYBOARD MAPPING
​
Then press the physical key or button you want to map to a function or a macro, for example the "Volume up" button. Confirm that this is the key you want to map.
Once a key is pressed, a new row is added. Tap the Map button to map the key to a function or macro. Select the function or "Macro" and tap SAVE.
If you want to map the physical key to a macro, tap the Macro button to define the actual macro. When you are done, tap OK. See below how to define a macro string.
Tap Menu -> Modify to modify a keyboard mapping or Menu -> Remove to remove a keyboard mapping.
Macro string
​
When entering a macro string, in addition to plain text, there are several conven-tions, all of which are signaled using the caret (^). If you wish to enter a 'real' caret, then you must type it twice (^^).
​
Control characters may be entered using the normal convention with a letter follow-ing the caret symbol. For example, a return is ^M and a line feed is ^J.
​
You may also send specific ASCII codes in hexadecimal, decimal, or octal form by following the caret with a $, #, or & character, and the desired code:
^#ddd decimal specification
^&ooo octal specification
^$hh hexadecimal specification
Note that decimal and octal codes must be 3 digits and prefixed with 0 if it is 2-digit codes.
​
Transmitting the string you have defined on a macro can be awkward if you are working in multiple environments where you sometimes need a CR terminator and sometimes need an ETX or EOT. To do this transparently, use the conventional form ^! (caret + exclamation mark). The correct line terminator will be sent depend-ing on the mode in which the emulator is operating. Note that if a macro contains multiple transmits then the macro execution will be suspended on each transmit and resumed when the host has responded. This functionality is only reliable for host connections with a 'turn' mechanism that signals when the host response is finished (DSA, Ggate and TNVIP).
​
Function codes (for those using synchronous interfaces) may be sent using the form '^=x', where 'x' is the function code you wish to be sent with the next message to be transmitted.
​
If the last character in the macro string typed in is '^', it will be ignored. This can in fact be useful: in that trailing spaces are deleted from the input you type; you can use an appropriately placed '^' at the end of the string to ensure that required trailing spaces are actually included. For example, entering 'ABC ^' will provide a trailing space after the 'ABC'.
​
