PrestoDecom is a portable extraction tool for telemetry parameters from binary archives, coming with a graphical user interface to navigate the Satellite DataBase.

It was developed in 2003 for the Proteus spacecraft platform, and was adopted by more than twenty different projects and platforms in and outside CNES (Pléiades, Calipso, Corot, Jason, Smos, Elisa, Parasol, Picard, Galileo, IASI, Doris, SpaceBus 4000, Iridium, Sentinel-3, Exomars to name only the most well-known).

PrestoDecom can extract physical telemetry parameter values into either human-readable ASCII files, or export them towards Microsoft Excel® or PrestoPlot®.

Among its greatest strengths are its ease of use and user-friendliness, gained through years of experience and feedback from its user community. Moreover, its inclusion in the control centres for the Proteus, Myriade, Pléiades and Galileo platforms and its use during IVQ for spacecrafts based on the Proteus platform are a pledge to its maturity.

Current version

The current version is PrestoDecom 18.12.

Next version

The next version of PrestoDecom is not yet planned.


Here is a list of some PrestoDecom features

  • Offline telemetry archive extraction

    PrestoDecom offers highly optimized extraction of parameters from standalone telemetry archives, supporting a wealth of platforms and telemetry formats.

    Its user-friendly graphical interface lets the user navigate the Satellite DataBase (SDB) packets and all their parameters to select only those that need be extracted.

    PrestoDecom also retrieves from the SDB and handles transfer functions, computation of ground-computed parameters, significant condition, and alarms.

  • Multiple extraction formats

    PrestoDecom allows extraction of telemetry parameters for analysis directly towards Microsoft Excel®, PrestoPlot®, or in raw text format. Analysis can begin straight away as PrestoDecom handles both extracting the data and opening the preferred viewer afterwards.

  • Fully extensible

    PrestoDecom can be extended through plugins. Plugins may add handling of new archive formats, special processing for specific APIDs, support for new extraction formats, and much more.

  • Accessible documentation

    PrestoDecom includes a comprehensive user manual that is directly accessible from the software interface.

  • Commutation capabilities

    PrestoDecom comes with libraries allowing encoding features like encoding telecommands.

  • ...

Frequently Asked Questions

Which operating systems does PrestoDecom run on ?

PrestoDecom targets the following operating systems:

  • Windows XP, Windows Seven
  • RedHat 3.9, RedHat 5, RedHat 6
  • CentOS 3.9, CentOS 5, CentOS 6

PrestoDecom should also run fine on other Windows and Linux versions.

Why does PrestoDecom fail to start on my 64bits Linux machine ?

PrestoDecom is a 32-bits binary and thus requires 32-bits libraries to run. Such libraries are generally available as compatibility libraries for Linux 64-bits systems. In order to install them, please contact your system administrator.

The list of required compatibility libraries can be found by running ldd <binary-name.lnx> from the command line.

Why can't I run PrestoDecom on a headless Linux machine if I'm only using batch mode ?

Since PrestoDecom uses Tk, it requires the X11 libraries to run, and a working X11 display. This is still the case even in batch mode.

On a headless machine, you may use Xvfb to provide PrestoDecom with a virtual X11 display. This can be done as follows:

 # Start the virtual X server
 Xvfb :1 &
 # Keep the process ID
 # Run PrestoDecom on the new virtual display
 ./<binary-name.lnx> -display :1 -commandfile <your-command-file> -noshow -exit
 # Stop the virtual display
 kill $XPID

To install Xvfb on your system if it is not already available, please contact your system administrator.

Error “/tmp/tclXXXXXX: failed to map segment from shared object: Operation not permitted”

Upon start, PrestoDecom unpacks and loads some internal libraries into $TMPDIR (/tmp by default). If $TMPDIR is mounted with the noexec option (execution of binaries is forbidden), those libraries will fail to load.

To circumvent this, $TMPDIR must be set to a directory where execution of binaries is allowed. This can be done follows:

 # Create a user-specific temporary directory
 mkdir -p ~/.tmp
 # Run PrestoDecom using the new temporary directory
 TMPDIR=~/.tmp <binary-name.lnx> -commandfile <your-command-file> -exit
 # Remove the temporary directory
 rm -rf ~/.tmp