Overview
Sensors may be co-located but of different types (e.g. primary and secondary radar) in which case the fusion server generates a single set of output reports without duplicates. Alternatively, sensors may be geographically separated but with overlapping areas, in which case the server provides handover support as targets move from each sensor to the next, preserving a single global target ID across the combined coverage area. A combination of the two modes is also supported.
The sensor data supplied to SPx Fusion may be derived from primary radar video (using SPx Server) or from secondary sources, such as AIS, IFF (SSR), or ADS-B. Track messages generated by processing primary radar video, using Cambridge Pixel's SPx Tracking Server application, may be input directly into the SPx Fusion Server software. Tracks from multiple, separate instances of SPx Tracking Server may be input, allowing for fusion of tracks from multiple primary radars.
Equally, SPx Fusion Server will accept a combination of SPx Tracking Server tracks and secondary tracks. For example, SPx Fusion Server could be used to combine the primary target tracks extracted from a VTS radar with the AIS messages being received from an AIS base station. Alternatively, the software could combine primary target tracks from an air surveillance radar with the decoded IFF or ADS-B transponder replies from aircraft.
Feature
■ Multiple sensor inputs
■ Any combination of primary and secondary sensor input
■ Accepts up to 25 sensor sources (additional sources may be supported upon request)
■ Support for AIS, ADS-B and IFF secondary sensors
■ Configurable sensor weighting and priority
■ Configuration file support
■ Moving platform support
■ Remote control over network socket
■ Standalone server application
■ Client interface using standard SPx library software
■ Available for Windows and Linux
■ Network output of fused tracks
■ Support for ASTERIX CAT 019, 020, 021, 034 and 048 input
