Licensing, Support & Training FAQs 11 questions
Email [email protected] to request a copy of Cambridge Pixel's licence terms, end user agreement or general terms of use.
Yes. SPx runtime licences are supplied on USB dongles or as licence files tied to a host MAC address. One dongle or licence file can hold licences for different applications and for several instances of the same application, or the licences can be split across several dongles or files.
No, with one or two exceptions: most Cambridge Pixel products are not subject to UK export control. However, Cambridge Pixel may be unable to supply products to countries that are subject to UK Government sanctions or other special measures.
No. SPx Server and SPx Fusion Server are manufactured in the UK and are not subject to export control, including ITAR.
Request the manual for your product with the Request Manual form on the product's page. Existing customers can also email [email protected].
Yes. Cambridge Pixel can provide training for any of its products. Email [email protected] with your company name, your country and the product you would like training on.
Cambridge Pixel's pricing is flexible and depends on the customer and the project, so we quote for each enquiry. Use Request a Quote on the product page, or email [email protected] with details of your project; where appropriate, your enquiry may be passed to your local distributor.
Yes. Depending on the product, Cambridge Pixel may be able to offer a walk-through demonstration, a trial licence or an equipment loan on request. Use the Book a Demo or Request a Demo button on the product page, or email [email protected].
Every Cambridge Pixel product comes with 12 months of support as standard, including access to software updates. Support gives direct access to Cambridge Pixel's engineers by phone, email or web chat (phone and web chat in normal UK office hours).
When you buy SPx software you choose how to receive it: as download links in the Cambridge Pixel customer portal, or on USB or DVD. Installation instructions are in the product manual, which you can request from the product's page; existing customers who need help can email [email protected].
Yes. SPx Radar Trainer is a computer-based training package for marine radar operators, run by course instructors for their students. SPx Radar Simulator generates realistic radar video, tracks, AIS and navigation data in real time, for training operators on radar display systems.
Platforms & Compatibility FAQs 9 questions
Yes. SPx Server, SPx Fusion Server and RadarWatch all run on Windows 11 and can be installed together on one workstation.
Cambridge Pixel's web-enabled clients support up-to-date versions of modern desktop and mobile browsers, including Chrome, Edge, Firefox and Safari.
Yes. SPx software supports most common virtual machines and containers, such as Docker.
Yes, provided the airborne radar can supply ASTERIX plot reports (ideally CAT-48 with CAT-34 status messages, or CAT-1 with CAT-2), has an ICD that lets Cambridge Pixel convert its proprietary format to ASTERIX, or outputs analogue or digital radar video that SPx Server can turn into ASTERIX plot reports.
RadarView (as an option), RadarWatch and the Maritime Display Framework (MDF) can display S-57 electronic navigation charts (ENCs). MDF also supports S-63 charts.
Yes, in most cases. Cambridge Pixel supports more than 80 radar models and can interface to radars that output analogue video, trigger and azimuth signals, network radar video, or plots and tracks in ASTERIX or another documented format. See Supported Radars for specific makes and models.
Cambridge Pixel software runs on Windows and Linux. Server and processing applications, such as SPx Server, SPx Fusion Server and SPx Track Manager, are available for both; most ready-to-run display applications, such as RadarView, RadarWatch, ASD-100 and VSD, run on Windows. For other operating systems, consult Cambridge Pixel.
No. No Cambridge Pixel product runs natively on macOS; Cambridge Pixel software is supplied for Windows and Linux. To view radar on a Mac, tablet or phone, use SPx Radar Web Server, which serves radar video and tracks to standard web browsers, including Safari.
Choose by application: RadarView for general radar display, set-up and testing; VSD-C2 for security, military C2 and counter-UAS; RadarWatch for coastal surveillance and port security; ASD-100 for air situation displays.
Radar Standards & Concepts FAQs 15 questions
ASTERIX is a family of Eurocontrol standards for exchanging surveillance data such as radar plots, tracks and video. Each type of data has its own category (CAT), for example CAT-48 for radar plots and tracks, and CAT-240 for radar video.
CAT-240 is the ASTERIX category for sending radar video across a network. Plots and tracks use other categories, such as CAT-48.
CAT-48 is the ASTERIX category for monoradar target reports: plots and tracks from a single primary or secondary radar, usually sent across a network. CAT-48 is normally used with CAT-34, the category for the radar's service (status) messages.
An A-Scan (or A-Scope) display shows radar signal amplitude against range for each radar return, as an oscilloscope connected to the radar video would. An A-Scan is useful for checking radar video signal levels to verify that the radar is correctly configured.
A B-Scan (or B-Scope) display shows radar video with azimuth along the horizontal axis and range along the vertical axis. B-Scan displays are commonly used with fire control radars, including in naval fire control.
An RHI (Range Height Indicator) display shows range along the horizontal (X) axis and altitude on the vertical (Y) axis. In RadarView, unlike its other displays, the RHI shows tracks only, not radar video.
RPM stands for Revolutions Per Minute. Typically it is used to describe how fast a radar rotates, i.e. how many times it sweeps through 360 degrees in 60 seconds. It is inversely related to the Period.
Period is the number of seconds that an event takes to repeat. It is often used to describe how long a radar takes to sweep through 360 degrees. For example, a 2 second period means a radar rotates completely every 2 seconds, which is the equivalent of a 30RPM rotation rate.
PIM is an acronym for Polar Interface Module. This is one of the classes (SPxPIM) within Cambridge Pixel’s SPx Development Library and is used for the storage of radar video data for processing and display.
Several do. SPx Alarm Server, RadarWatch and the Maritime Display Framework calculate CPA (Closest Point of Approach) and TCPA (Time to CPA) and can raise alarms on them, and SPx Server's proximity detection supports collision avoidance.
Radar scan conversion transforms radar video from polar format (range and azimuth) into Cartesian form for display on a computer screen, for example as a PPI. Scan conversion must represent targets accurately and introduce no gaps in the video.
Plot extraction (also called target detection) finds blobs of radar video that meet set size and strength criteria. Each plot may be a real target or noise, and has no speed or course. Tracking correlates plots over time to reject false targets, producing tracks with position, speed and course.
A multi-hypothesis tracker considers several possible interpretations of the radar measurements at the same time, rather than committing to one, which significantly improves performance over simpler single-hypothesis trackers. SPx Server uses multi-hypothesis association in its radar tracker.
Sector blanking forces radar video to zero over a chosen sequence of azimuths, so that a sector of the radar picture is blanked.
SAPIENT FAQs 8 questions
SAPIENT is an open standard that lets different devices, called edge nodes, connect through plug-and-play interfaces to a single endpoint, called a fusion node. The current version is BSI Flex 335 v2.0. SAPIENT is used mainly in counter-UAS systems, but nothing technical limits it to them.
The plug-and-play nature of SAPIENT means no prior knowledge of the specific devices serving as edge nodes is needed, and the mechanism for control and information gathering is the same across device types, enabling faster, easier system setup.
No. NATO STANREC 4869 is built on the current version of SAPIENT but adds recommendations on how to implement the standard, making it more specific. A system compliant with STANREC 4869 is compliant with SAPIENT, but a SAPIENT-compliant system may not be fully compliant with STANREC 4869.
A SAPIENT edge node can be any device that acts as a sensor, an effector or both, including:
A SAPIENT fusion node is the endpoint of a SAPIENT system. The fusion node processes the information received from the edge nodes connected to it, sends tasking to those nodes, and normally either feeds a display application directly or is integrated into one.
Yes. A SAPIENT fusion node can act as a child of another fusion node, connecting to it as an edge node would. This lets a larger system be built as a hierarchy, with several fusion nodes feeding a higher-level fusion node.
SPx Server, SPx Fusion Server, SPx Track Manager, SPx Camera Manager and VSD-C2 support SAPIENT, as does the SPx Server embedded in the HPx-700. All of them use BSI Flex 335, the formal name for SAPIENT version 2.
Use Cambridge Pixel software to translate. SPx Server can process the radar's video into tracks and output them in SAPIENT format, so the radar joins the SAPIENT system as a full edge node, and SPx Track Manager can convert any of its input formats into SAPIENT. Analogue radars connect to SPx Server through HPx radar interface hardware.
HPx Radar Interface Hardware FAQs 18 questions
Choose by the job and the host. The HPx-346 and HPx-700 are standalone units that put analogue radar onto a network; the HPx-410 (PCIe) and HPx-450 (XMC) are input cards for a host computer; the HPx-310 outputs analogue radar signals; the HPx-180 and HPx-550 convert synchro/resolver azimuth.
HPx input hardware takes three signals from the radar: analogue video, a trigger (synchronisation) signal, and antenna azimuth, normally as ACP/ARP pulses. Depending on the product, azimuth can also be parallel or serial data, and synchro/resolver azimuth is converted with an HPx-180 or HPx-550.
Almost always, yes. Cambridge Pixel supports more than 80 radar models: analogue radars connect through HPx radar interface hardware, and radars with a network output connect over Ethernet using SPx software, which reads ASTERIX CAT-240 and formats from Terma, Simrad, Navtech, Furuno, Raymarine, Garmin and others.
Yes. Cambridge Pixel’s HPx radar interface hardware can connect to the “sub display” output of Furuno FAR-2xx8 series radars.
Use an HPx-346, connected either to the Sperry radar’s transceiver or to its DCU. The transceiver’s signals are directly compatible with the HPx-346 using cable P/N 346-800; the DCU’s signals need some conditioning and a different radar input cable.
Yes. The HPx-346 connects to a radar’s analogue video, trigger and ACP/ARP outputs, digitises the video and streams it over Ethernet as ASTERIX CAT-240 or other formats. The HPx-346 is a small standalone unit, configured through a built-in web interface.
Yes. The HPx-700 runs an embedded version of SPx Server on its onboard 64-bit ARM processor, so the HPx-700 can digitise analogue radar, distribute radar video, extract plots and track targets with no host PC. The HPx-700 comes in Distribution, Detection and Tracking versions.
Yes. The HPx-346 can send radar video onto the network as a multicast stream, normally in ASTERIX CAT-240 format.
Yes. The HPx-346D is the dual-redundant network version of the HPx-346. The HPx-346D has two independent Ethernet interfaces and sends network radar video onto two networks simultaneously.
Yes. The HPx-310 radar signal output card, driven by SPx software, converts network radar video back into analogue video, trigger and ACP/ARP signals, for example to feed legacy equipment that has an analogue radar interface.
Yes. The dual-stream versions of the HPx-410 (PCIe) and HPx-450 (XMC) have two independent sets of radar inputs, so one card can capture two separate radars at the same time. To track targets from both radars, you need two instances of SPx Server.
“Highest-wins” means that when an HPx radar input card combines consecutive range samples to reduce the data rate, the combined sample takes the highest of the original values, so returns from small targets are not lost.
Yes. Cambridge Pixel supplies pre-built radar interface cables for HPx hardware, including generic signal breakout cables and radar-specific cables for radars from Consilium, Furuno, JRC, Kelvin Hughes, Koden, Sperry Marine, STN Atlas and Terma.
From Cambridge Pixel support. The latest HPx drivers for Windows and Linux are free of charge within your warranty period; contact support to request them.
Request the manual from the HPx product’s page on this website: use the Request Manual button and complete the short form. For legacy HPx models, contact support to request a manual.
SPx Server FAQs 33 questions
Choose by the processing you need. The Distribution version digitises radar and streams video over the network; Detection adds plot extraction and proximity detection; Tracking adds complete multi-hypothesis primary radar tracking. Each version includes everything in the one before.
SPx Server outputs track reports in SPx format, ASTERIX CAT-48 or CAT-10, NMEA-0183 TTM, TAK and SAPIENT. Radar video is distributed in ASTERIX CAT-240 or SPx format.
Yes, provided you have licences for both. SPx Server has a single processing chain, so set that processing up for tracking rather than display; video processed for display, for example thresholded to reduce bandwidth, cannot share the chain the tracker uses.
SPx Server finds spans of processed video above a threshold on each return, joins them across returns into connected two-dimensional shapes, and records each shape as a plot with its weighted centre of gravity, bounding box, total weight and timestamp. Size limits reject small noise, large clutter and land.
SPx Server's track filter computes a dynamic filter gain from estimated system noise and measurement noise models, so the gains change continually: they rise when the target manoeuvres or uncertainty increases, and fall in steady-state tracking. A simpler fixed-gain mode is also available.
A hypothesis is one possible interpretation of how new plots associate with existing tracks. SPx Server’s multi-hypothesis tracker holds several hypotheses at once and reports the one with the highest confidence, so the correct interpretation can be chosen as soon as new data resolves it.
Model Based Tracking (MBT) is an SPx Server extension that runs several sets of tightly coupled tracking parameters, called models, on the same radar video. MBT lets small, low-observable targets such as drones be detected and tracked alongside conventional targets, much like running multiple trackers with different parameters.
Yes, but only to a limited degree. SPx Server tracks in 2D and is designed for rotating radars; SPx Server can tag height information into its track reports. For true 3D tracking, or radars with non-rotating or variable updates such as electronically scanned radars, use SPx Tracker-3D.
Yes. SPx Server extracts and tracks targets from secondary surveillance radar (SSR/IFF) transponder video as well as primary radar, decoding interleaved Mode 1, 2, 3/A and C codes in software. The codes are embedded in each plot and used to strengthen track association.
SPx Server has programmable minimum and maximum target speeds, for initiation and tracking, from 0 to 1000 m/s. High-speed targets can be tracked with appropriate configuration; the practical limit depends on how far the target moves within the radar data store, which depends on the radar’s maximum range.
Yes, provided SPx Server is configured correctly. Dynamic (CFAR) thresholding automatically adjusts the detection threshold as clutter levels change, and other track-processing parameters adapt automatically to conditions. There are limits to how far this adaptation goes.
Yes. SPx Server masks radar video with user-defined polygons, fixed to the world or to the platform, including holes, on static or moving platforms, so a sector or any other area can be blanked. Land can be masked automatically using the built-in world shoreline database.
Yes, to a limited degree. SPx Server has built-in AIS association: SPx Server can associate a radar track with an AIS track and include the AIS ID in the track report. For more flexible fusion of radar, AIS, ADS-B and IFF tracks, use SPx Fusion Server.
Yes. SPx Server has been verified by simulation against the standardised test scenarios in IEC 62388 section 10.3.14 (target motion and tracking accuracy).
SPx Server has a user interface to help you configure, tune and analyse the processing, with live views of radar video, plots and tracks that show the effect of each change. Once deployed, SPx Server can run headless, without the user interface, controlled through its network API.
Use the SPx Server web interface: connect a standard web browser to SPx Server to monitor and control it remotely. Alternatively, view the native user interface on a remote computer with remote desktop. For health monitoring across several systems, use SPx Monitor.
In automatic track initiation (ATI), SPx Server creates tracks itself by looking for target-like returns in the radar video. In manual acquisition, something outside SPx Server, such as an operator clicking a target on a display, tells SPx Server where to create a track; SPx Server then maintains it.
SPx Server’s track acquisition time is programmable. In low clutter, a new track can be established after as few as 2 detections (2 scans); where the plot extractor reports false detections, the provisional stage can be extended. Shorter times detect targets faster; longer times reduce false tracks.
Yes. SPx Server can record radar video, together with NMEA and AIS data, for trials and offline analysis. Recording is a licensed option; without the licence only short recordings are permitted. To enable recording, set the ProRecord.Available parameter to 1.
No. SPx Server’s recording is designed for capturing recordings during trials, for offline analysis and configuration, not for continuous recording. SPx Server cannot manage a recording session to keep, for example, the last N days. For continuous recording with managed storage, use RDR Data Recorder.
Yes. You can upgrade SPx Server to the latest version for one year after initial delivery. After that, you need a support contract in place; contact our sales team for details.
Ask Cambridge Pixel engineers: they often supply a customised configuration file as a starting point, with suggested parameters to adjust. The best SPx Server settings depend on the radar, the targets and your priorities, such as fast acquisition or fewer false alarms, so no single procedure fits every system.
Create named area objects, such as polygons or segments, then give tracking parameters different values inside those areas. SPx Server uses the area value where one applies and the global value everywhere else, so you can solve a local problem without changing tracking elsewhere.
A provisional track is a new track that SPx Server has not yet confirmed. SPx Server creates a provisional track when a plot does not associate with any existing track, and promotes the track to established once confidence has built up over a number of detections.
A cluster is a group of one or more tracks that are close enough together for SPx Server to process them as a group. Processing close tracks together ensures that all possible associations of plots and tracks are considered. A sufficiently isolated track forms a cluster on its own.
Use SPx Server’s built-in lossless compression, zlib or ORC (Open Radar Coding), and if needed simplify the video before compression, for example by thresholding it to a single bit and removing low-level background noise. Simplifying the video improves compression but loses some video content.
Your SPx Server licence probably does not include tracking. SPx Server enables its radar processing functions according to the licence: the Distribution version, for example, distributes radar video but does not enable plot extraction or target tracking. Tracking needs the Tracking version.
Reduce the number of plots first, then check tracking parameters. SPx Server falls behind when processing, plot extraction or tracking is configured incorrectly. SPx Server tries to self-correct by switching to simplified processing, such as single-hypothesis tracking, but this may not be enough or may not be what you want.
Radar position measurements always contain some error, and a track’s estimated speed and heading partly reflect that error. In SPx Server, lower steady-state filter gains apply more filtering, so speed and heading settle as the noise is filtered out; gains rise automatically during a manoeuvre and fall again afterwards.
SPx Server allocates track IDs from 1 to 4095 on a least-recently-used basis. When a track is deleted, its ID is not reused until all the other IDs have been used.
The missing IDs were used by provisional tracks that never became established. SPx Server allocates a track ID when it creates a provisional track; if the provisional track is deleted before it is established, that ID never appears in a track report.
Usually because the radar video has a small range bias. SPx Server can correct this with one of our standard plugins, which applies a fixed range offset and a range multiplier. Contact support for details.
SPx Server’s built-in screen recorder captures images of the PPI window at regular intervals and saves them to a directory. Use the screen recorder when analysing problem cases, to capture images showing detailed on-screen information.
SPx Fusion Server FAQs 8 questions
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.
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.
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.
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.
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.
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.
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.
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 FAQs 7 questions
Yes. SPx Track Manager treats each ASTERIX source as an independent input, even when several radars send to the same network address and port, provided each radar has its own SAC/SIC codes. Each input can be filtered, converted to another format and sent to one or more outputs.
SPx Track Manager supports standard formats including ASTERIX, GeoJSON, NMEA TTC, NMEA TTM, SAPIENT (BSI Flex 335), SEIWG ICD-100, SGF 1.1 and SPx, plus many proprietary radar formats such as Echodyne EchoShield, Robin Radar and Leonardo DRS RADA, and converts between them.
Contact Cambridge Pixel. SPx Track Manager is designed to be extended to new track formats quickly. If you can share the format documentation (under NDA if necessary), Cambridge Pixel can provide a fixed-price quote quickly; there may be a small NRE charge.
Yes. In SPx Track Manager, set up two filter areas: an inner zone where the false tracks start, and an outer zone enclosing the area where they usually die out. Then set the filter to exclude tracks that are in the outer zone and started in the inner zone.
Slant range correction converts the range a radar measures to an airborne target (the slant range) into ground range, so the track appears at its true position over the ground on a PPI display. SPx Track Manager can correct a track's latitude/longitude when it was based on slant range.
Yes. SPx Track Manager supports dual-redundant track streams: it enables one stream and switches automatically to the second if the first is lost.
SPx Track Manager is application software for standard Intel PC or single-board computer (SBC) hardware. The suggested minimum is an Intel Core i5 or better CPU, 8 GB or more of RAM, and Windows 11 or a mainstream Linux distribution less than two years old.
SPx Radar Simulator FAQs 14 questions
SPx Radar Simulator generates primary, secondary (IFF) and MTI radar video for each simulated radar, plus target tracks, AIS, ADS-B and platform navigation data, all as separate network outputs. Radar video is output as ASTERIX CAT-240, or as analogue signals through an HPx-310 card.
In SPx Radar Simulator, each target can be configured to generate any combination of AIS, primary or secondary radar video, and track reports. For example, a target can be AIS only, or can generate AIS and primary radar, both as video and as a track.
Use SPx Radar Simulator with an HPx-310 radar signal output card. SPx Radar Simulator generates realistic radar scenarios with returns from terrain and moving targets, and the HPx-310 outputs them as analogue radar video in standard four-wire format: video, trigger, ACP and ARP.
SPx Radar Simulator can take real radar video as an auxiliary input and add simulated targets to it. The auxiliary source can be a Cambridge Pixel recording (CPR) file, a network input in SPx or ASTERIX CAT-240 format, or live video from an HPx radar input card.
Yes. SPx Radar Simulator has a built-in scenario generator, but you do not have to use it. SPx Radar Simulator can instead convert target positions from your existing scenario generator into radar video, tracks or AIS, provided the scenario generator reports changes in target positions at regular intervals.
Yes. SPx Radar Simulator has an API for remote control, so a separate application can control it as a server.
No. SPx Radar Simulator does not model the RF characteristics of real radars. Instead, SPx Radar Simulator provides a controllable source of realistic-looking radar video, with high-level settings such as beamwidth and pulse length that you adjust until the video picture looks as wanted.
Load better terrain data. SPx Radar Simulator uses NASA SRTM terrain elevation data by default, covering most of the world's landmass at 3 arc-second resolution, but you can use your own DTED data instead, configured in the terrain configuration dialog.
SPx Radar Simulator can simulate background noise and near noise in the generated radar video, plus noise in detected target positions, detected target size, and measured platform position, course, heading and speed. Sea clutter can also be simulated.
Open the visibility status dialog from the target configuration dialog in SPx Radar Simulator. If a target is not visible, one of its indicators will be red, and a tooltip explains how to resolve the issue. When several radars are simulated, each radar has its own visibility indicators.
No. SPx Radar Simulator is currently available for Windows only.
Yes. SPx Radar Simulator works on air platforms as well as moving land and sea platforms: the radar origin can follow a user-defined motion path or be driven by external navigation data, and the simulation takes altitude, pitch and roll into account.
Yes. SPx Radar Simulator uses terrain elevation data to calculate radar returns from land for the platform position, and can include line of sight along each azimuth, so land or targets obscured by terrain at shorter ranges are not displayed. Buildings also contribute to the returns.
Request the SPx Radar Simulator user manual through the form on the SPx Radar Simulator product page.
RDR Data Recorder FAQs 8 questions
RDR Data Recorder captures radar video, primary and secondary radar tracks, AIS, ADS-B, navigation data, camera video, audio, screen video and arbitrary network packets. Data from all channels is synchronised in a common recording file, so all channels stay synchronised on replay.
RDR Data Recorder has no intrinsic limit on recording length; it is limited by available disk space. For continuous recording, RDR Data Recorder supports rolling recording, where data older than, for example, 30 days is deleted automatically.
Yes, provided your sensor or system outputs its data on a network. RDR Data Recorder can record generic network packets on an open channel without interpreting them, and replays them like any other channel, synchronised with the radar data.
Use SPx Open Access, which reads and decodes the radar video in Cambridge Pixel Recording (CPR) files made by RDR Data Recorder. Your own C++, .NET or MATLAB code can then analyse the video on Windows or Linux, for a selected time range and channel of the recording.
RDR Data Recorder writes track messages to an SQL database while recording. You can filter the results with SQL queries and export them to a .csv file for analysis in Microsoft Excel or other packages.
Both. RDR Data Recorder is available as software for Windows, or as a turnkey PC system supplied with the appropriate radar input/output cards. For system integrators and OEM developers, the software and radar input/output cards are also available as components for a custom system.
RDR Data Recorder replays a recording through user-defined output channels, routing each channel's data to a suitable physical output with all channels kept synchronised. For example, AIS data can be replayed on the host's serial port or Ethernet port, whichever one it was recorded from.
Yes. RDR Data Recorder has a socket-based control interface, so recording and replay can be managed remotely over the network as well as from the local user interface.
SPx Radar Web Server FAQs 7 questions
Use SPx Radar Web Server. SPx Radar Web Server receives ASTERIX CAT-240 radar video, converts it into scan-converted images and serves them to web browsers, which request images for a defined geographical area through a REST interface and display them with maps, tracks and other layers.
Use SPx Radar Web Server. SPx Radar Web Server receives ASTERIX CAT-240 radar video, scan-converts it on a server and serves the images to a standard web browser, including browsers on iOS and Android phones and tablets, provided the device has a network connection to the server.
SPx Radar Web Server runs on Windows or Linux servers. Clients need only a standard web browser, so radar video can be viewed on Windows, Linux, macOS, iOS and Android devices.
SPx Radar Web Server serves track reports to browsers in an extended GeoJSON format. This covers primary radar tracks, fused tracks, AIS and ADS-B, which the browser renders with the radar video and map.
SPx Radar Web Server is licensed by the maximum number of clients, with standard options for 2, 5, 10, 25 or 100 clients. More clients can be supported if the host has sufficient resources, or several servers can share the radar data and each serve fewer clients.
Yes. In a cloud-based system, a lightweight radar server or an HPx-346 unit receives the radar video and distributes it to a cloud-based server running SPx Radar Web Server. Client browsers then make HTTP requests for the specific areas of radar data they need.
Yes. SPx Radar Web Server is fully controllable at runtime through a client-side JavaScript API, so display applications can be built on web mapping tools such as Google Maps and Bing Maps. A built-in web client display is also provided.
VSD-C2 FAQs 13 questions
VSD comes in four ready-to-run versions. VSD-Camera Standard and Advanced display and control cameras. VSD-C2 Standard adds one type of C2 sensor or effector, such as a radar or jammer. VSD-C2 Advanced supports up to four types, plus 3D and panorama windows.
VSD supports 2D and 3D ground-based radars from APS, Blighter, Echodyne, Hensoldt, Leonardo DRS RADA, Robin Radar Systems, Teledyne FLIR and Weibel, plus radars that output ASTERIX CAT-048 or CAT-062 or use the SAPIENT protocol. Radar is a C2 sensor type, so it needs a VSD-C2 version.
VSD supports PTZ cameras that use ONVIF (Profile S) or Pelco-D, SAPIENT protocol cameras, and named EO/IR cameras from Hensoldt, OpenWorks Engineering and Teledyne FLIR. Video can be received over ONVIF, MPEG-TS, RTP or RTSP, encoded as H.264 or H.265.
Yes, provided you use a VSD-C2 version, which adds radar support. Once a target is acquired on radar, VSD moves a camera to the reported position and updates the camera position from each radar detection. This is called slew-to-cue.
VSD-Camera Advanced and both VSD-C2 versions support third-party video tracking systems and AI-based classifier modules, including Chess Dynamics Vision4ce (CHARM and DART), OpenWorks Engineering SkyAI, Vizgard FortifAI, Walaris AirScout and SAPIENT protocol devices. VSD-Camera Standard does not include video tracker support.
Yes. VSD-C2 Advanced controls cameras plus up to four types of C2 sensor or effector, such as radars, radio direction finders and RF jammers, from one display. VSD-C2 Standard supports cameras plus a single C2 sensor or effector type.
Yes, provided the reports are first converted with SPx Track Manager. VSD receives track reports and can use them to trigger alarms and control cameras and laser rangefinders. Where required, an SPx Track Manager licence for radar format conversion is included with VSD-C2.
Yes. VSD shows a georeferenced map with the positions of radars, cameras and targets of interest. Maps are downloaded automatically from an internet connection, can be cached for use without one, or custom maps can be loaded.
Yes. Many VSD capabilities can be customised, including the display presentation, window layout and controls. For more specialised needs, Cambridge Pixel offers a customisation and rapid prototyping service covering interface changes, branding and support for new devices.
Choose VSD for smaller mobile or single-operator systems, camera-only systems, or systems that integrate video trackers, laser rangefinders or radio direction finders. Choose RadarWatch for larger systems with multiple operators, multiple long-range radars, more complex alarm handling or electronic chart (ENC) support.
Besides radar, VSD-C2 supports acoustic direction finders, laser rangefinders and radio direction finders as C2 sensors, and acoustic hailing devices, laser dazzlers and RF inhibitors or jammers as C2 effectors. VSD-C2 Standard supports one type from these lists; VSD-C2 Advanced supports up to four.
VSD supports ASTERIX, SAPIENT (BSI Flex 335 V2.0 and NATO STANREC/AEDP-4869), TAK Cursor-on-Target (CoT), MIL-STD-2525D symbology, SEIWG ICD-0101 XML, NMEA-0183 GNSS/INS navigation data, AIS and ADS-B. VSD-C2 can output tracks in ASTERIX, SPx and TAK CoT formats.
VSD is used in ground mobile as well as ground fixed systems, but full on-the-move (OTM) operation is listed as a planned future release. At present, GNSS/INS navigation data is used only to orient and position a stationary vehicle platform automatically.
RadarWatch FAQs 8 questions
RadarWatch is radar and camera display software for coastal surveillance, port and harbour security, simple vessel traffic monitoring and search and rescue. It displays radar video, tracks, AIS, ADS-B and camera video in multiple windows across multiple screens, with flexible automated alarms.
Yes, for ports, harbours and simple vessel traffic monitoring. RadarWatch displays radar tracks and AIS targets, calculates CPA/TCPA between targets and reference points, and raises alarms when vessels enter areas, cross gates or exceed a set speed.
RadarWatch takes all its inputs from the network in open formats: ASTERIX CAT-48 radar tracks, ASTERIX CAT-240 radar video, NMEA-0183 platform data, NMEA-0183 AIS data and ASTERIX CAT-21 ADS-B data, plus camera video.
RadarWatch supports up to four radar inputs and up to 16 camera inputs. Its windows include two radar PPI windows, two camera video windows, a video multiview window, a track table and an active alarms window.
No, provided your sensors already output open formats such as ASTERIX and NMEA-0183: RadarWatch can then be used as a ready-made display for that data. RadarWatch is also designed to work closely with other Cambridge Pixel software when you need more capability.
RadarWatch generates alarms under user-defined conditions: targets entering defined areas, gate crossings, proximity, speed, and CPA/TCPA between target pairs or between targets and reference points. Alarms can be visual and audible, and RadarWatch can send network messages to external equipment.
Yes. RadarWatch supports slew-to-cue and manual camera control, and shows camera video with target information from radar, AIS and ADS-B. It supports up to 16 camera inputs, with two camera video windows and a video multiview window.
RadarWatch displays radar video and symbology over S-57 electronic charts, tiled maps or a world vector shoreline map. It can also show a radar coverage map.
ASD-100 & ASD-View FAQs 10 questions
Buy a SkyVector subscription directly from SkyVector, then enter the SkyVector licence key in ASD-100 through the setup dialogue or by editing the config file. Setup is described in the 'Tiled Map Display' section (3.24) of the ASD-100 user manual.
Cambridge Pixel software accepts weather radar data in ASTERIX CAT-8 format. ASD-100, RadarView and the SPx Development Library can receive and display CAT-8 weather data.
ASD-100 accepts ASTERIX data over the network: four channels of CAT-240 radar video, four channels of CAT-48 plots or tracks, CAT-21 ADS-B, CAT-4 safety alerts and CAT-8 weather data.
Yes. ASD-100 receives safety alerts in ASTERIX CAT-4 format, including Short Term Conflict Alerts (STCA), Area Proximity Warnings (APW) and Minimum Safe Altitude Warnings (MSAW). It shows a visual warning and a graphical representation of each conflict while it persists.
Yes. ASD-100 provides an affordable way to upgrade existing air defence C2 systems. Combined with other Cambridge Pixel software, the upgrade is predominantly software-based, so existing front-end radar hardware can be retained, and standard ASTERIX data keeps compatibility with other systems.
Yes. Source code licensing is available for ASD-100, allowing developers to extend and localise the application and ensure long-term support. Alternatively, Cambridge Pixel's in-house team can customise ASD-100, for example with custom branding and user interfaces.
RadarView FAQs 9 questions
No. RadarView is a Windows application and is Windows 11 compatible. For radar display on Linux, Cambridge Pixel offers other options, including the SPx Development Library, SPx Radar Web Server and SPx Viewer-3D.
RadarView does not create tracks; it only displays tracks that it receives as input. To create tracks from radar video, you need SPx Server, which can send them to RadarView over the network.
RadarView supports tiled maps, raster images, a world vector shoreline map and, with an extra licence, S-57 electronic (ENC) charts. Overlay graphics include range rings, a compass ring, a range scale indicator and user maps, and RadarView can calculate and display a radar coverage map.
Yes. RadarView can display up to two camera video windows, from an RTSP network stream or a DirectShow-compatible video capture device. It can also control up to two Pelco-D compatible PTZ cameras.
AIS symbology can take tens of seconds to appear in RadarView because it depends on how often AIS messages are sent. Some AIS messages, including those that define a target's size and details, are sent less frequently than others.
Yes. RadarView-240 is a free application that receives ASTERIX CAT-240 radar video on a configurable IP address and port and displays it as a scan-converted PPI. Fill in the form on the RadarView-240 page to receive a download link and user manual.
RadarView accepts network radar video in ASTERIX CAT-240, SPx format (for example from SPx Server) and a number of proprietary formats. With an HPx radar input card, it can also take radar video, trigger, ACP and ARP signals directly from a wide range of radar types.
Yes. RadarView offers PPI, RHI, B-Scan and A-Scan presentations. It has a main PPI plus up to four pop-up PPIs, all fully resizable and positionable, and can spread the radar picture across multiple screens.
Yes. RadarView has built-in radar video record and replay, so you can display and record radar video at the same time. This is useful when configuring a new installation or testing a radar, and lets you analyse the data off-line.
Maritime Display Framework FAQs 10 questions
Yes. The Maritime Display Framework (MDF) is a C# .NET source code package for developing customised ARPA, ECDIS and integrated bridge displays. It is a good starting point for this kind of application.
Both. MDF is available as a turnkey application and, with the SPx Development Library, as a source-code framework for developers to modify and extend. MDF's default configuration provides a functional maritime display without any development.
MDF gives you a working maritime display, with source code for the application layer, as the starting point for your own development. It is generally much easier to modify and extend an application that already implements the core functionality than to start from scratch.
MDF is a framework that a system developer can use as the starting point for an ARPA, ECDIS or integrated bridge system display. It already includes typical ARPA features and electronic chart support, which you then adapt and extend for your product.
MDF usually needs an NMEA-0183 navigation data input, ASTERIX CAT-240 radar video, and radar tracks in ASTERIX CAT-48, SPx or NMEA TTM format. AIS input and H.264 camera video via RTSP are also supported.
MDF works with most maritime radars through SPx Server, which converts radar video to ASTERIX CAT-240 and generates tracks for MDF. Radar control from MDF is currently available for models from Furuno, Hensoldt, JRC, Raymarine, Simrad, Sperry and Terma.
MDF handles CPA/TCPA (Closest Point of Approach and Time to CPA) values and related alarms natively, using the SPx .NET library. MDF also generates predictive vectors and warns if there is a danger of collision with other ships.
Yes. MDF includes S-57 / S-63 electronic chart support, so radar video, tracks and AIS targets can be displayed over electronic navigation charts.
MDF supports up to four radars, each with radar video and tracks, and up to 350 radar and/or AIS targets. It supports display resolutions up to 8K UHD (7680x4320) and Windows touch screens.
MDF is designed for single-screen, moving-platform systems on board ships and vessels. The Surveillance Display Framework (SDF) supports multi-screen systems that are shore-based, ground-based or on any stationary platform. Both are C# .NET frameworks that can be supplied with source code.
SPx Development Library FAQs 8 questions
Yes. The SPx Development Library is Cambridge Pixel's open-standards SDK for building or enhancing applications that need radar processing and display. It provides a library of C++ and .NET classes, with example applications, documentation and engineering support.
The SPx Development Library provides C++ and .NET classes, with Windows and Linux/X11 options. It runs on standard, low-cost processing hardware and uses multi-core processors and graphics processors for high performance with low CPU usage.
The SPx Development Library includes radar processing modules for scan conversion, compression, video and clutter processing, plot extraction, target display, network distribution and recording, plus supporting modules for graphics, GUI widgets and data receivers. Example applications and documentation are included.
The SPx Development Library is available with single developer, dual developer and project licensing options, each with Windows or Linux/X11 options. Engineer-to-engineer support is provided by phone or email.
SPx Server is a ready-made application that acquires, processes and distributes radar video, plots and tracks. The SPx Development Library is the toolkit for building radar processing and display into your own code. You can use either, or both together.
The SPx Development Library is supplied with documentation and example applications that demonstrate key features. If you have a licence but cannot find them, contact Cambridge Pixel support.
Yes. The scan conversion module of the SPx Development Library adds PPI, A-Scan or B-Scan radar displays to an existing Windows or Linux application. Its Radar Insertion technology inserts the radar image into your application with minimal changes to your code.
Yes, with SPx Open Access. It is a set of tools and libraries for reading and decoding radar video in Cambridge Pixel Recording (CPR) files from SPx Server, RadarView or RDR, so you can analyse recordings or develop new algorithms in C++, .NET or MATLAB.
Tools & Utilities FAQs 8 questions
The Radar Coverage Tool is a free Windows application from Cambridge Pixel that shows where a radar at a chosen location and height can see targets, and where terrain creates blind spots. The Radar Coverage Tool uses SRTM terrain data, line-of-sight calculations and the curvature of the earth.
Cambridge Pixel offers five free downloads: the Radar Coverage Tool for visualising radar coverage, the Navigation Data Monitor, AIS Data Monitor and ADS-B Data Monitor for inspecting data feeds, and RadarView-240 for displaying ASTERIX CAT-240 radar video.
Yes, with Radar Coverage Tool Pro or Radar Coverage Tool Geo, which export the coverage map as a KML file for GIS tools such as Google Earth. The free Radar Coverage Tool can only save a screenshot of the current view as an image file.
Two standalone utilities in the Cambridge Pixel toolkit do this. spxserialtonet converts between serial and UDP and between TCP and UDP; it is often used to convert serial AIS or GPS feeds into UDP messages. spxnetrepeat converts between unicast and multicast packets.
Use the free Radar Coverage Tool to try different radar positions, heights, end ranges and beam angles; the coverage map updates quickly as you change them. The tool shows where targets at chosen heights are line-of-sight visible and where terrain blocks the view, helping you identify optimum radar positions.
The free Radar Coverage Tool calculates coverage for one radar using approximately 90 m SRTM terrain data. Radar Coverage Tool Pro is a licensed version that calculates coverage for up to 10 radar sites at once, exports coverage to KML, and uses approximately 30 m SRTM1 terrain data or DTED.
SPx Camera Manager is Windows or Linux server software that shares control of PTZ video cameras between multiple users by priority, and automatically points cameras at targets (slew-to-cue) using AIS, radar or fused track reports. SPx Camera Manager supports ONVIF, Pelco-D and FLIR Nexus camera control protocols.
SPx Alarm Server is Windows or Linux server software that monitors radar, fused, AIS and ADS-B track streams and raises alarms when tracks meet user-defined conditions against zones, gates, points or other tracks, such as entering a restricted area or coming too close to another track.
No questions match yet.
Try a shorter or different word, or ask our support engineers — we add new questions from what people ask us.