Troubleshooting the SmartEye module
No data ever arrives, with nothing in the log
Cause. Either SmartEye’s software is not configured to send its UDP output to this workstation and port, or it is sending a packet type other than its gaze packet (type 4). This module drops any other packet type silently - no warning, no error.
Fix. Confirm SmartEye’s software is configured to broadcast to the correct host and
UdpPort, and that its output includes the gaze packet, not only a head-tracking-only or
diagnostic packet type.
Some fields are always missing from the gaze or pupillometry data
Cause. SmartEye only includes a field in its packet when it actually has a value for it that frame - a lost eye, an unconfigured analysis feature, or a SmartEye software version that doesn’t compute that particular field will omit it. This module publishes whatever arrived and nothing for what didn’t; it does not synthesize a placeholder value.
Fix. Check SmartEye’s own software configuration and licensed feature set for the fields you expect; this is not something to adjust in this module’s own settings.
The head pose looks static even though the head is moving
Cause. If SmartEye stops sending head position or both rotation representations (quaternion and Rodrigues vector), this module still publishes a pose using an identity orientation rather than omitting the field - see Data produced.
Fix. Confirm SmartEye’s head-tracking output is actually enabled and being received; a flat orientation with no other symptoms is more likely a missing upstream field than a real head position.
DominantEmotion values don’t make sense as a probability or magnitude
Cause. DominantEmotion is SmartEye’s own enumerated code for which emotion it classified as
dominant, not a score. This module passes the raw code through without decoding it.
Fix. Interpret it against SmartEye’s own documentation for that field; there is nothing to configure here.