Bluetooth BLE keyboard emulation settings
A list of all valid configuration settings for the config.txt file which relate to sending pass information over a BLE keyboard emulation interface, when the VTAP PRO is in Local mode.
Note: Bluetooth is only available on VTAP100-PRO-BW hardware.
BTKeyboardMode enables/disables the BLE keyboard emulation. When enabled, you can pair and connect the VTAP reader with a Bluetooth host device (such as a tablet or laptop), and start receiving the pass or card data on the text editor or other application that expects to receive a keyboard input. Like USB keyboard emulation, you need to ensure your cursor is at the right place (in an appropriate app) to receive the input.
When scanning for pairing or connecting, the VTAP PRO name will match its 'VTAP label' (check boot.txt or label on the bottom or the case for this serial number). By default no PIN is set, so the host device can automatically pair and connect to the VTAP PRO. Should you need to change the Bluetooth name for your VTAP PRO, use BTKeyboardName. If you want to add a PIN for pairing set BTKeyboardPIN.
BTKeyboardSource determines whether BLE keyboard mode responds to only mobile pass reads, or card/tag reads too. You might need a BTKeyboardDelayMS value to insert a delay between key presses, to suit your receiving application
BTKeyboardPrefix and BTKeyboardPostfix can be optionally used to add extra characters before or after a pass read, to suit your application.
When BTKeyboardPassMode=1, a character delimited section of the pass payload will be extracted. The delimiting character defaults to | but this can be changed to another character using BTKeyboardPassSeparator. The payload is then considered as comprising a number of sections, any of which can be selected using BTKeyboardPassSection. By identifying a BTKeyboardContentSeparator this process can be repeated at a lower level, within a section. This follows the same approach as over a USB keyboard emulation, for which there is a simple example in
Settings below: BTKeyboardDelayMS | BTKeyboardMode | BTKeyboardName | BTKeyboardPassContentMode | BTKeyboardPassContentSection | BTKeyboardPassContentSeparator | BTKeyboardPassLength | BTKeyboardPassMode | BTKeyboardPassSection | BTKeyboardPassSeparator | BTKeyboardPassStart | BTKeyboardPIN | BTKeyboardPostfix | BTKeyboardPrefix | BTKeyboardSource
Inserts a number of milliseconds delay between key down and key up in the BLE keyboard output.
Turns BLE keyboard emulation on or off.
This is the name that the VTAP BLE keyboard will advertise for discovery by a host device.
Turns on a subdivision of a data section into smaller content sections.
Identifies the content section of interest, by finding BTKeyboardPassContentSeparator characters. The first content section, before the first separator, is numbered 0.
Identifies the content separator character in the data which bounds content sections.
Number of characters of data to extract, starting from the position defined by BTKeyboardPassStart.
Sets whether to extract parts of the data from the mobile NFC pass.
Identifies the section of interest, based on finding BTKeyboardPassSeparator characters. The first section, before the first separator, is numbered 0.
Identifies the separator character in the data which bounds sections.
Number of characters into pass data to start reading, where first character is 0.
Optional PIN for pairing the VTAP PRO reader with host device such as PC or tablet.
Adds special characters after BLE keyboard data, if needed.
Use standard ASCII hex characters to describe the keystrokes to append.
%0D in the example adds a carriage return after the data,
%0A adds a new line after every pass or tag entry.
$t would include the pass type.
$$t would append '$t' to the output.
$t$n will follow the pass type character with a digit for VAS merchant ID/ST collector ID index (1 to 6) and a digit for keyslot used (1 to 6).
$u adds the UID as 8, 14 or 16 hex ASCII digits.
(For
Pass type explainer - click here
Adds special characters before BLE keyboard data, if needed.
Use standard ASCII hex characters to describe the keystrokes to append.
%0A in the example adds a new line linefeed before the data.
$t would include the pass type .
$$t would prefix the output with '$t'.
$t$n will follow the pass type character with a digit for VAS merchant ID/ST collector ID index (1 to 6) and a digit for keyslot used (1 to 6).
$u adds the UID as 8, 14 or 16 hex ASCII digits.
(ForPass type explainer - click here
Controls which types of event data (pass reads, card/tag reads, serial commands) are sent as a BLE keyboard entries.
=80 (hex) will send only mobile NFC pass data
=A1 to send data from NFC passes and NFC cards/tags and card emulation
=83 to send passes, cards/tags and serial commands
