SPx Fusion Server FAQs

SPx Fusion Server is application software from Cambridge Pixel that combines track reports from multiple sensors, such as radars, IFF, ADS-B and AIS, into a single output stream of correlated tracks with consistent track labels. SPx Fusion Server runs on Windows or Linux on Intel PC workstations or servers.

• For co-located sensors covering the same area, SPx Fusion Server produces one track report per target with the most reliable information from each sensor, plus anything one sensor reports that another does not.
• For sensors with overlapping coverage, SPx Fusion Server keeps a single global track ID as a target moves from one sensor's coverage into the next.
• Priority and score settings for each sensor decide which sensor's data is trusted.
• A single instance supports 2 to 32 sensor inputs, depending on the licence.

Fused tracks are output on the network for displays and systems such as RadarWatch, ASD-100, VSD and TEWA. See SPx Fusion Server.

Link to this answer

No, apart from the licence. SPx Fusion Server has no intrinsic limit on the number of sensors; each instance supports the number of sensor inputs its licence allows, with standard licences for up to 2, 4, 6, 8, 16, 25 or 32 sensor inputs.

If you need more than 32 sensor inputs, contact Cambridge Pixel. See the SPx Fusion Server page for licence details.

Link to this answer

Yes. SPx Fusion Server uses the 3D position in each track report (latitude, longitude and height) during correlation, so tracks from the radars and other sensors in a drone detection system can be fused into a single track stream.

Each sensor is assigned a relative priority and score, which determines the number of sensor observations needed before a fused track is reported. Recent releases added support for SAPIENT sensor sources, bearing-only observations and enhanced track and sensor height references.

See SPx Fusion Server and Cambridge Pixel's counter-UAS applications.

Link to this answer

Yes. SPx Fusion Server normally sends fused track reports as multicast UDP messages, so multiple applications on the network can subscribe to the same track stream.

Every subscriber receives the same consistent track IDs, so displays such as RadarWatch and ASD-100 show matching track labels. See SPx Fusion Server.

Link to this answer

SPx Fusion Server combines track reports from radars, IFF, ADS-B and AIS, in ASTERIX, SPx and other georeferenced track report formats. Any sensor that produces georeferenced reports can be interfaced, including perimeter intrusion detection systems (PIDS), unattended ground sensors (UGS) and SAPIENT sensor sources.

Through PIDS and UGS systems, SPx Fusion Server can take in reports from acoustic, electro-optic, magnetic, passive infrared and seismic sensors. Bearing-only observations are also supported.

Primary radars are usually connected via an ASTERIX network data stream. Non-standard data streams can first be converted to SPx format by SPx Server (2D radars), SPx Tracker-3D (3D radars) or SPx Track Manager. Older primary radars without an Ethernet output can be connected through HPx radar input cards.

Link to this answer

SPx Fusion Server uses a priority and a score set for each sensor. When overlapping sensors observe the same target, data from the sensor with the highest priority is used. If sensors share the same priority, the choice is based on the target's proximity to each sensor.

Scores control when a fused track is reported. SPx Fusion Server only outputs a track when the combined score of the sensors observing it reaches the threshold of 1.0. For example, if each sensor's score is 0.5, a target must be seen by at least two sensors before it is reported.

Setting a higher priority for sensors you believe are more accurate means their information is given greater credence than that from less accurate sensors. See SPx Fusion Server.

Link to this answer

Yes. SPx Fusion Server gives each target a single global track ID across the combined coverage area, so the track label does not change as a target moves from one sensor's coverage into the next, and operators do not see two or more tracks for the same target.

This is a common requirement in VTS, coastal surveillance and land border security systems. In redundant SPx Server installations, SPx Fusion Server also keeps track IDs consistent across a failover, so client systems see no discontinuity.

SPx Fusion Server can also issue alert reports when tracks are merged, split or changed. See SPx Fusion Server.

Link to this answer

To connect an Echodyne EchoShield radar to SPx Fusion Server, first convert its track output with SPx Track Manager, which supports EchoShield, EchoGuard and many other proprietary track formats. SPx Track Manager then outputs the tracks in a format SPx Fusion Server accepts, such as SPx or ASTERIX.

SPx Track Manager's EchoShield support includes third-generation EchoShield radars.

1. Check that your radar is listed on the supported radars pages (for example Echodyne).
2. Configure SPx Track Manager to receive the radar's track reports and convert them to SPx or ASTERIX format.
3. Add the converted stream as a sensor input to SPx Fusion Server and set its priority and score.

If your radar's format is not supported yet, contact Cambridge Pixel.

Link to this answer