Configure the SonoMarc module
Settings are edited in HEAT Capture’s module settings UI, under Sonomarc Module.
Connection and session
| Setting | Type | Default | What it controls |
|---|---|---|---|
Host | string | localhost | Hostname or IP of the SonoMarc Core server. |
Port | integer | 80 | HTTP port of the SonoMarc REST API. |
SessionName | string | empty | The SonoMarc session to capture. Left empty, this module picks the first session it finds in the Running state - not necessarily a predictable one if more than one is running. |
SessionPollRetryMs | integer (ms) | 5000 | How often this module checks for a matching running session. It keeps checking indefinitely - there is no give-up point, so a capture session that starts before SonoMarc does waits. |
Capture mode
| Setting | Type | Default | What it controls |
|---|---|---|---|
CaptureMode | WholeSession | PerSeat | WholeSession | WholeSession: capture every seat on every platform - intended for one centralized capture node. PerSeat: capture only the seat bound to this workstation - intended for a per-operator HEAT Capture deployment. |
SeatBinding | string | empty (local hostname) | Only used in PerSeat mode. The seat binding this workstation should match. A seat matches if its own binding string contains this value, not only on an exact match - see Troubleshooting for why that can pick up more than one seat. |
SSE
| Setting | Type | Default | What it controls |
|---|---|---|---|
SseReconnectDelayMs | integer (ms) | 3000 | Delay before reconnecting a dropped event stream. Retries indefinitely. |
This module also exposes the generic settings every HEAT Capture module has (Enabled,
Interval, OverrideNodeId/NodeId, Timeout) - see
Manage capture modules. Interval matters
more than its name suggests here: seat and asset state (including malfunction detection) is only
re-polled, and fault-transition events only computed, when this module’s own capture call runs -
left at the SDK default of 1000 ms, a fault that clears within that window can be missed
entirely, the same risk documented for the game controller input module.
Activity events (transmit, receive, push-to-talk) are not affected - those arrive over the
separate SSE stream in real time, independent of Interval.