UTC
--:--:--
GPS
--:--:--
LORAN
--:--:--
TAI
--:--:--
LOCAL
--:--:--

We design time reference systems.

When the Test Bench Has to Travel

Test and simulation systems for satellite ground segments, avionics and ground-based defense, from the laboratory to the field

By Gian Luca Pizzocolo, IPSES · Oct 27, 2026

The same SDR (software-defined radio) core, three form factors: a rack in the laboratory, a rugged case on the flight line, a compact unit that goes below deck on a ship.

That continuity matters because the equipment a test system verifies rarely stays in one place. A satellite unit is checked in the cleanroom during Assembly, Integration and Testing (AIT). A radar is tested at the factory, again on a test range and again at every maintenance cycle. A vessel can spend months at sea, and its radars, radios and navigation receivers still need regular checks while the nearest laboratory is an ocean away.

On the flight line or below deck, a maintenance technician needs one answer in minutes: is the system ready, and if it is not, where is the fault?

For twenty years IPSES has built test systems for Aerospace & Defense. This article looks at how test and simulation work across three domains (satellite ground segments, avionics and ground-based defense) and at what changes when the test bench has to leave the lab.

WHY SIMULATION COMES FIRST

Some conditions cannot be produced on demand. A hostile emitter will not fly a test pattern for you. A satellite cannot be launched to check its telemetry link. A radar cannot wait for a real target to approach at the right speed and angle.

Simulation brings those conditions into the lab:

  • Radar target generator: receives the radar pulse and returns a synthetic echo with the delay, Doppler shift and amplitude of a target at a chosen range and speed
  • Electronic threat simulator: reproduces the emissions a receiver is designed to detect
  • GNSS (Global Navigation Satellite System) simulator: generates the constellation as a receiver would see it from a given position and time
  • TT&C (Telemetry, Tracking and Command) link simulator: plays the role of the spacecraft or of the ground station

The value lies in repeatability. The same scenario can run a hundred times with one parameter changed at each run, and every result can be traced back to its conditions. A field trial gives one sample; a simulated campaign gives a data set.

THREE DOMAINS, ONE DISCIPLINE

SATELLITE GROUND SEGMENT
During AIT, every unit of a spacecraft is verified by a SCOE (Special Check-Out Equipment): a test system built around a single unit under test, such as power, communication, data handling or payload electronics. On the RF side this means stimulating and measuring TT&C transponders, feeding GNSS signals to on-board receivers and checking that every link behaves as specified. Once the spacecraft is in orbit, nothing can be fixed by hand.

AVIONICS
Avionics equipment is tested at the bench, during integration on the aircraft and at each maintenance step. Communication radios, navigation receivers and radars all need stimuli that reproduce flight conditions while the aircraft stays on the ground.

GROUND-BASED DEFENSE
Systems that protect against aerial and satellite threats depend on sensors that must be trusted before deployment and after every upgrade. Spectrum monitoring receivers for Electronic Support Measures (ESM) have to detect and classify emitters correctly. C-UAS (Counter-Unmanned Aircraft Systems) sensors have to pick out the radio links of drones among everything else on the air. Communication protection systems have to keep a link alive under interference.

Each of these is tested against simulated scenarios: a crowded spectrum, a drone control link, a jamming signal. A sensor that has only met a quiet spectrum in the lab has not really been tested.

FROM THE LAB TO THE FIELD

A laboratory bench has space, stable power, air conditioning and a test engineer next to it. None of these can be taken for granted on board a ship, in a hangar, inside a vehicle or at the edge of a test range. A transportable system has to deal with:

  • Space: narrow passages and little room around the equipment
  • Power: whatever the platform provides
  • Environment: vibration, humidity, salt atmosphere, temperature swings
  • Setup time: operational in minutes
  • Operator: often maintenance staff, guided step by step to a clear result

At sea, the test system goes to the equipment. Radars, communication systems and navigation receivers are checked where they are installed, during the mission or in port, without removing them.

On aircraft and vehicles, the test set travels on board or stays installed for the length of a campaign. On test ranges, radar target generators and threat simulators move with the trials, so the scenarios built in the lab can be reproduced in the field.

ONE ARCHITECTURE, FROM RACK TO CASE

Software-defined radio is what makes this continuity possible. In an SDR the RF front end is general-purpose, while the function lives in software and in the FPGA. The same hardware can act as a radar target generator in the morning and as a TT&C link simulator in the afternoon, with a different FPGA image and a different test sequence.

IPSES builds on NI platforms:

  • USRP and PXI with Vector Signal Transceivers (VST): the RF chain
  • CompactRIO (cRIO): compact and rugged deployments
  • NI TestStand: test sequence management

Test sequences are developed once and run on both the laboratory bench and the transportable unit. A measurement taken at sea can then be compared directly with one taken in the lab.

Behind the architecture is a team of ten NI-certified engineers, including four LabVIEW Architects and two TestStand Architects.

The bench that once filled a laboratory now fits in a case. For a ship at sea, that means its radar can face the same scenario it met in the factory, without coming back to port.