Wallboard keyboard emulator

Requirements

• Android 4.0.6 application version
• Windows 4.0.210 application version

Sensor configuration

{
	"uid": "",
	"type": "KEYBOARD_EMULATOR",
	"settings": {
		"rules": [
			{
				"type": "KEYBOARD|JOYSTICK|IR",
				"timeout": 50,
				"eol": "\n",
				"format": "message|sensor",
				"target": "displayer|device|both",
				"defaultId": "",
				"defaultEvent": "",
				"pattern": "(\\w\\d{3}\\w)\\[(TR|TD)=UID:([A-Za-z0-9]*)]\r\n",
				"idGroupIndex": 1,
				"eventGroupIndex": 2,
				"valueGroupIndex": 3
			}
		]
	}
}

Setup

In order to utilize the Keyboard emulators, it is necessary to apply a configuration to your device. You have to configure the settings through the right-click menu on the device:

Device Properties >> Set >> Set sensor configuration

Parameters

• type is used to tell the device what kind of keyboard emulator is connected, usually if for example a barcode or NFC reader is used then the type has to be KEYBOARD
• The timeout sets the maximum amount of time the device will wait for a new key press, if the timeout expires the received message will be sent to the target
• The format tells the device what kind of format it should use to send the message to the target, if the format is message then only the message itself will be sent to the target, if the format is sensor then the message will be wrapped in our sensor message format
• target tells the device to where to send the message, if it is set to displayer then the message will be sent to the displayer where it can be handled in a content, if it is set to device then the received message will be sent to the underlying display operating system.

info

The target should always be set to displayer to prevent an IR remote for example from controlling the display

• The defaultId and defaultEvent are used when the format is set to sensor, in this case these will added as an ID and as an Event to the sensor message
• The pattern is used similarly to our Generic sensor the pattern given here will be applied to the received message, and the idGroupIndex eventGroupIndex valueGroupIndex will be used to get the values captured by the pattern