BMS Connectors¶

The BMS Application uses a modular connector architecture to integrate with various real-time data sources. Each connector implements a common interface for receiving position updates, video feeds, geofences, and bullseye references.

Connector Architecture¶

Available Connectors¶

SPX RADAR Connector¶

The SPX connector receives track reports from Cambridge Pixel RADAR systems over UDP multicast.

Protocol Details¶

• Magic Number: 0x4342 (Cambridge Pixel)
• Default Multicast: 239.192.50.79:5079
• Encoding: Big-endian binary

Message Types¶

Track Status Values¶

Configuration¶

{
    "connectorId": "spx",
    "enabled": true,
    "settings": {
        "multicastAddress": "239.192.50.79",
        "port": 5079,
        "interface": "",
        "staleTimeoutSec": 30,
        "calculateLatLon": true
    }
}

SAPIENT Connector¶

The SAPIENT connector implements BSI Flex 335 v2.0 for autonomous sensor integration, receiving detection reports from AI sensors and RADAR systems.

Protocol Details¶

• Standard: BSI Flex 335 v2.0
• Encoding: Protocol Buffers
• Transport: TCP with 4-byte length prefix

Message Types¶

• Registration / RegistrationAck - Sensor registration
• DetectionReport - Object detections with classifications
• StatusReport - Sensor health and status
• Task / TaskAck - Sensor tasking commands

Detection Classifications¶

SAPIENT provides AI-based object classification with confidence levels:

• Vehicle (car, truck, tank, APC)
• Person (individual, group)
• Aircraft (fixed-wing, rotary)
• Maritime (boat, ship)

Configuration¶

{
    "connectorId": "sapient",
    "enabled": true,
    "settings": {
        "mode": "client",
        "host": "192.168.1.100",
        "port": 8080,
        "nodeId": "bms-node-001",
        "defaultAffiliation": "unknown",
        "staleTimeoutSec": 300
    }
}

Cursor on Target (CoT) Connector¶

The CoT connector integrates with the TAK ecosystem (ATAK, WinTAK, TAK Server) using the Cursor on Target XML protocol.

Protocol Details¶

• Format: XML over TCP or UDP Multicast
• SA Multicast: 239.2.3.1:6969
• Chat Multicast: 224.10.10.1:17012

CoT Event Types¶

Configuration¶

{
    "connectorId": "cot",
    "enabled": true,
    "settings": {
        "mode": "multicast",
        "multicastAddress": "239.2.3.1",
        "port": 6969,
        "interface": ""
    }
}

Data Flow¶

Connector Manager¶

The Connector Manager handles:

• Registration: Built-in and plugin connectors
• Lifecycle: Start, stop, configure connectors
• Routing: Forward updates to map and track displays
• Status: Monitor connector health and statistics

Loading Connectors¶

// Get connector manager instance
auto* manager = ConnectorManager::instance();

// Create and configure a connector
auto* spx = manager->createInstance("spx", "radar-1");
spx->configure({
    {"multicastAddress", "239.192.50.79"},
    {"port", 5079}
});

// Connect signals
connect(spx, &ConnectorInterface::positionUpdated,
        this, &BmsWindow::onPositionUpdate);

// Start receiving data
spx->start();

Symbol Mapping¶

Connectors convert source-specific data to APP-6D military symbols (SIDC):

Adding Custom Connectors¶

Implement the ConnectorInterface to create custom connectors:

class MyConnector : public ConnectorInterface
{
    Q_OBJECT
public:
    QString connectorId() const override { return "my-connector"; }
    QString displayName() const override { return "My Custom Connector"; }

    bool configure(const QVariantMap& settings) override;
    bool start() override;
    void stop() override;

    // Emit positionUpdated() when data arrives
};

See ConnectorInterface.h for the full interface definition.