Data produced by the EmotiBit module
Reading names
Each reading is published under its raw two-letter EmotiBit type tag (EA, HR, AX, and so on)
as a BiometricReading - the module does not translate the tag
into a descriptive name. Only tags listed in the
sensor whitelist setting are ever requested from the device.
Type tags
| Type tag | Signal | Sensor | Sampling rate |
|---|---|---|---|
EA | EDA - Electrodermal Activity | ADS1114 | 15 Hz |
EL | EDL - Electrodermal Level | ADS1114 | 15 Hz |
ER | EDR - Electrodermal Response | ADS1114 | 15 Hz |
PI | PPG Infrared | MAX30101 | 25 Hz (100 Hz with special firmware) |
PR | PPG Red | MAX30101 | 25 Hz (100 Hz with special firmware) |
PG | PPG Green | MAX30101 | 25 Hz (100 Hz with special firmware) |
TH | Temperature via medical-grade thermopile (EmotiBit MD only) | MLX90632 | 7.5 Hz |
AX, AY, AZ | Accelerometer, X/Y/Z axes | BMI160 | 25 Hz |
GX, GY, GZ | Gyroscope, X/Y/Z axes | BMI160 | 25 Hz |
MX, MY, MZ | Magnetometer, X/Y/Z axes | BMI150 | 25 Hz |
HR | Heart rate | Derived from PPG | Event-based |
BI | Heart inter-beat interval | Derived from PPG | Event-based |
SA | Skin conductance response amplitude | Derived from EDA | Event-based |
SF | Skin conductance response frequency | Derived from EDA | Event-based |
Sensor ICs and sampling rates are for the stock EmotiBit firmware, from EmotiBit’s own
data format reference ;
verify against the connected device’s firmware and hardware revision. HR, BI, SA and SF
readings arrive only when the device detects the corresponding event, not on a fixed schedule.
Aggregation
All readings received since the previous capture tick are collected under a single entity (fixed
ID 1234) and published together in one SimulationFrame. If a channel produced several samples
in that window - the device can batch multiple points into one packet - every sample is published
as a separate reading with the same type tag name; none are dropped or averaged. If nothing was
received in a tick, no frame is produced for this entity.
The capture timestamp on the published frame is HEAT Capture’s own wall-clock time at the moment the tick is processed, not the device’s own onboard timestamp carried in the EmotiBit packet header; that header timestamp is read by the bridge library but not forwarded into the recorded data.
Limits
The module tracks exactly one EmotiBit under a single fixed entity ID. It has no way to distinguish or capture from two EmotiBit devices at once.