Keyboard/barcode reader emulation settings
A list of all valid configuration settings which relate to sending pass information over a keyboard/barcode reader emulation interface for the config.txt file.
If KBLogMode=1 and KBSource is set, you can open an application on the computer connected to the VTAP reader, and pass or card data that is read will be typed to the screen. KBSource determines whether keyboard wedge/barcode mode is triggered only by mobile pass reads, or cards/tag reads too. You might need a KBDelayMS value to insert an additional delay between key presses, to suit your receiving application.
KBPrefix and KBPostfix can be optionally used to add extra characters before or after a pass read, to suit your application. These include adding pass type, as explained below:
Pass type is a single character to describe the source of a received pass payload, which may be an Apple VAS pass or Google ST pass, a particular type of NFC card, or other source such as a barcode scanner. The values that returned are:
A - Apple VAS pass
G - Google ST pass
0 - MIFARE card/tag
2 - NFC type 2 card/tag
4 - NFC type 4 card/tag
6 - NFC type 5 card/tag
E - Card emulation
Q - Scanner input
X - Apple Wallet Access iPhone
W - Apple Wallet Access Watch
When KBPassMode=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 KBPassSeparator. The payload is then considered as comprising a number of sections, any of which can be selected using KBPassSection. By identifying a KBContentSeparator this process can be repeated at a lower level, within a section. There is a simple example in
KBMap optionally points to a separate file, where a list of key codes corresponding to particular characters, can be used to translate between the VTAP default US keyboard emulation and the keyboard language setting used by the host computer.
KBEnable=0 allows you to disable the keyboard device function of a VTAP reader, which can be helpful if you are working with Android devices using the USB COMPort, to avoid a clash with the on‑screen keyboard.
Settings below:
KBDelayMS
Inserts a number of milliseconds delay between key down and key up and between consecutive key presses in the keyboard output.
Option to disable the USB keyboard device function of a VTAP reader. This can be useful in Android USB serial integrations, where the presence of a USB keyboard device can disable the on-screen keyboard, which would then need to be overridden in settings.
Points to a keyboard map file and/or section of that file, which lists key codes corresponding to particular characters, in order to translate to a keyboard language setting used by the host computer. (Without this setting the VTAP keyboard emulation uses a US English keyboard mapping.)
Turns on a subdivision of a data section into smaller content sections.
Identifies the content section of interest, by finding KBPassContentSeparator 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 KBPassStart.
Sets whether to extract parts of the data from the mobile NFC pass.
Identifies the section of interest, based on finding KBPassSeparator 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.
Adds special characters after 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 the 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 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
