Troubleshooting the SonoMarc module
The module never starts capturing
Cause. This module waits for a SonoMarc session matching SessionName (or, if that’s empty,
the first one it finds) to be in the Running state before it does anything else, retrying every
SessionPollRetryMs indefinitely. If no matching session ever starts running, this module
never gets past that wait.
Fix. Confirm the expected SonoMarc session exists and is actually running, not only created.
If SessionName is set, confirm it matches exactly (case-insensitive, but not a partial match).
A PerSeat deployment captures more (or a different) seat than expected
Cause. The seat-binding match in PerSeat mode is a substring check, not an exact match:
this module matches any seat whose own binding string contains SeatBinding (or the local
hostname if that’s empty). A workstation whose hostname is a prefix or substring of another
seat’s binding can match a seat that was not intended for it.
Fix. Set SeatBinding explicitly to the exact binding string SonoMarc uses for the intended
seat, rather than relying on hostname auto-detection, if hostnames on your network share common
prefixes.
The selected radio is always reported as not selected
Cause. This is a real gap in this version, not a configuration issue - RadioComponent.selected
is always published false regardless of which radio the operator actually has selected. See
Data produced.
Fix. There is nothing to configure for this; the selected radio is not available from this module’s output today.
Cannot tell whether a radio was selected or its squelch was toggled
Cause. Both produce the identical INTERCOM_STATE_CHANGED tracking event, with nothing in
the event distinguishing which one happened. The same is true for secure mode turning on versus
off - both produce the identical TRANSMITTER_STATE_CHANGED event.
Fix. This is a real ambiguity in this version’s event stream, not something a setting resolves. If you need to tell them apart, you cannot from this module’s events alone.
A platform’s position never appears
Cause. This module only understands a platform’s position when SonoMarc reports it as
"geographic" (latitude/longitude/altitude). A platform whose position source is "geocentric"
publishes no position at all in this version.
Fix. Check how the platform’s position source is configured in SonoMarc; there is nothing in this module’s own settings that changes this.