Mentalista module

Unlike most capture modules, the Mentalista module does not connect out to a device - it hosts a WebSocket listener and waits for a client to connect in. Once connected, it optionally sends a connect command to start the device, then receives prediction events and publishes them as biometric readings.

The client on the other end of that WebSocket is not the EEG headset itself. In this deployment, it is Mentalista’s own web application, running in an automated Chrome session (driven via ChromeDriver) that is logged into Mentalista’s cloud backend. The headset talks to that web application (over Bluetooth, or synthetically for testing); the backend performs the actual prediction inference; the browser session relays the result down over the WebSocket this module listens on. This module never talks to the headset or Mentalista’s backend directly - see Interface Control Document Section 2.

What you need

An automated Chrome browser session running Mentalista’s web application, logged into Mentalista’s cloud backend, reachable to open a WebSocket connection to the workstation running HEAT Capture on the configured host and port. Setting this browser session up is outside this module - it only hosts the listener the browser connects to.
The listener is only open while a capture session is active - see Configure. A client attempting to connect before a session starts, or after it ends, will find nothing listening.

Network exposure

This module declares the network.listen capability for tcp/5555, HEAT Capture’s default port for it. That declaration is what HEAT Capture’s host firewall scoping is built from; see Configure for what changing Port away from 5555 actually does, and Interface Control Document Section 9 for the full security picture, including that the connection is unauthenticated and unencrypted.

Mentalista module

What you need

Network exposure

Pages