User Stories

Astrium Creates World’s First Two-Way Laser Optical Link Between an Aircraft and a Communication Satellite


Develop controls to ensure the precision of a laser optical link between an aircraft and a communication satellite


Use MathWorks tools to model control algorithms and pointing hardware, conduct hardware-in-the-loop tests, and deploy a real-time system for flight tests


  • First-of-its-kind optical link demonstrated
  • Design iterations reduced from days to hours
  • Overall development time reduced by six months

"Using MathWorks tools for Model-Based Design, we simulated not only our control algorithms but also the physical hardware. By automatically generating code for the control software and the test bench, we reduced development time and implemented changes quickly. We visualized simulation and test results, which gave us confidence in the design that we ultimately deployed."

David Gendre, Astrium
LOLA telescope assembly, as fitted to aircraft in Artemis laser link trials.

Until recently, laser optical links for high-bandwidth satellite transmissions were limited to satellite-to-satellite communication. To establish such a link with an aircraft, engineers had to contend with the distortion and attenuation of the signal by the atmosphere and by the movement and vibrations of the aircraft.

Astrium, a wholly owned subsidiary of EADS, developed LOLA, a two-way laser optical link between an airborne aircraft and the Artemis geostationary satellite capable of 50 megabits-per-second transmission with an error rate of less than one error bit per billion.

Astrium reduced control development and validation time by using MathWorks tools for Model-Based Design, an approach that was already well-established within the organization.

"We use Model-Based Design regularly for timed simulations and modeling spacecraft dynamics," explains David Gendre, pointing development engineer at Astrium. "On this project, we used Simulink, Simulink Coder, and Simulink Real-Time to develop a control system model and a physical model of the pointing hardware. We used these models for continuous functional verification and to generate code for hardware-in-the-loop tests and the real-time demonstration system used in flight tests."


Astrium’s system had to control and dampen the aircraft’s high-frequency vibrations as well as its roll, pitch, and yaw. It also had to track the laser beam despite the disturbances and distortion caused by the atmosphere.

Based on input from an inertial measurement unit, an active pixel sensor, and a GPS receiver, the control system used actuators to adjust the azimuth and elevation of the telescope for larger-scale control and to adjust a pointing mirror along two axes for fine-grain control.

When Astrium carried out the first tests with real hardware, only the fine-tuning components were available. As a result, for verification they needed to model, simulate, and generate code for a large portion of the physical system in addition to the control system.


Astrium engineers used MathWorks tools for Model-Based Design to model, simulate, and verify the control algorithms and telescope pointing hardware; conduct hardware-in-the-loop (HIL) tests; and deploy a fully operational, real-time system for flight tests.

Astrium conducted flight tests to measure vibration in the aircraft and pitch, roll, and yaw angle variations. MATLAB® and Optimization Toolbox™ were used to process the measurement data as input to the control system model.

They divided the project into two parallel efforts, with one group using Simulink® to design and model the control system and a second using Simulink to model the mechanics of the telescope pointing hardware and the behavior of the active pixel sensor. The Simulink models enabled the teams to communicate design decisions throughout development.

Using Simulink, engineers developed components for each control-system operating mode, including pointing, acquisition, and tracking. They used Control System Toolbox™ to develop linear time-invariant models and reused functional blocks from their Simulink library, including blocks for orbit models and geometric analysis using quaternion computations.

After running time- and frequency-domain simulations in Simulink to verify the functionality and stability of the control system, the engineers used Simulink Coder™ to generate code for the control software and the physical model. They then conducted a second, avionic validation phase using HIL tests, with the control system operating on a combination of actual hardware (for the fine-control pointing) and simulated hardware (for the larger-scale pointing).

Throughout development, MathWorks tools facilitated concurrent engineering, with software engineers in charge of managing the real-time constraints of the control system as well as developing functions such as image processing and specific hardware drivers. “These functions were easily embedded into S-functions in the Simulink model,” explains Gendre.

The engineers used Simulink Real-Time™ to deploy a fully functional, real-time version of the system on a PC designed for flight tests.


  • First-of-its-kind optical link demonstrated. The telescope pointing control system enabled Astrium to demonstrate the world’s first two-way laser optical link between an airborne aircraft and a communications satellite.

  • Design iterations reduced from days to hours. “During HIL tests we have many other teams involved, including the people that handle the test bench and the optics. It is important to be able to react quickly and resolve problems,” says Gendre. “With Simulink we can make the necessary modification, re-generate the software using Simulink Coder, and start the test again in a half-day. Similar changes used to take us almost a week.”

  • Overall development time reduced by six months. “Using MathWorks tools for Model-Based Design enabled us to shorten our development effort by about six months,” says Gendre. “A big part of that time savings was due to automatic generation of the code for the control system and the test bench. On the test bench alone, we increased our development speed by a factor of four.”