EmotiBit module
The EmotiBit module connects to an EmotiBit wearable biosensor over the
local Wi-Fi network and streams its sensor channels into HEAT Capture. EmotiBit is a third-party,
open-hardware device; the module talks to it using EmotiBit’s own UDP discovery and data protocol
via a native bridge library (EmotibitBridge.dll), not a VRAI-defined interface.
What it captures
EmotiBit reports many physiological and motion channels as separate two-letter “type tags” (EA,
PI, HR, and so on). The module only requests the subset of channels listed in its
sensor whitelist setting; each requested channel is published as
its own reading, named with the device’s raw type tag. See
Data produced by the EmotiBit module for the full list and what each
tag means.
Finding the device
The module does not require a fixed IP address. On startup it can broadcast a discovery request on the local subnet, and/or scan a range of unicast addresses, depending on which of those two methods are enabled. See Configure the EmotiBit module for the discovery settings and a known default that must be changed before this works on a customer network.
Interface Control Document
See Interface control document for bridge configuration and lifecycle, accepted type tags, measurement aggregation, frame publication and known reconnect limits.
Pages
- Configure: discovery, sensor whitelist and network filter settings.
- Data produced: the type tags this module can publish, and how readings are aggregated.
- Troubleshooting: symptoms, causes and fixes.