Release Notes

Core 2.0.9

Name change: the PolySync platform is now called PolySync Core.


  • Support for Ubuntu 16.04

    • To take advantage of the features below, upgrade to the new Ubuntu distribution
    • Coming Soon: PolySync Core support for Ubuntu 14.04
  • Support for the QNX® Neutrino® RTOS

  • ROS Bridge

    • PolySync Core <> ROS bridge is now bidirectional, allowing data to flow between Core and ROS buses in real-time
    • How to use the ROS Bridge
  • PolySync Core <> MATLAB integration (beta) provides a workflow to export data from Core to .CSV, and then import into MATLAB

    • Coming Soon:  fully-supported bridge developed in collaboration with MathWorks to provide PolySync Core <> MATLAB class / Simulink block streaming interface
  • Support for the Renesas R-Car H3 autonomous driving platform, running the QNX® Neutrino® RTOS

  • Support for the NVIDIA DRIVE PX2 autonomous driving platform

  • Support for 32 sensors and actuation systems popular in the autonomous driving environment

  • PolySync Transcoder

    • Open source interface for accessing and converting stored logfiles (plogs)
    • Ability to introspect all Core logfiles regardless of the data model
    • Ability to decode specific sensor data through sensor descriptors, starting with the Ibeo family of LiDAR sensors
    • Coming soon: a Python binding to the PolySync logfile encoder and decoder; plugins to convert Core logfiles to hdf5 and rosbag; more sensor descriptors to decode sensor data
    • Learn more about the Transcoder, then learn how to build and install the Transcoder

Change Log

Technical changes from 2.0.8 to 2.0.9, that a developer would need/want to know before upgrading applications written on the older version.


  • The installation method has been simplified, and now conforms to the Debian package manager conventions

    • The GUI installer has been replaced by the Debian package installation method
    • Installation is performed using the Ubuntu Software Center, or on the command line with dpkg ─ you can see the step by step installation guide from our Help Center
  • Support for the Quanergy family of LiDAR sensors with Quanergy API version 4, and the Rev-C hardware

  • The polysync-generate node creates a node scaffolding and is capable of generating a supported sensor interface for CAN based sensors with  a DBC file

  • Studio provides an open plugin framework to create custom visualization tools for data on the PolySync bus

  • Huge repo’s full of examples, tutorials and tools geared towards learning the PolySync C and C++ APIs

    • Be sure to check out the README in each example for a description, list of dependencies and instructions on how to build and run the example or tool
  • PolySync Studio has an interface to manage logfile sessions, and coordinate record and replay operations across entire PolySync systems

  • New File Sync API which is used to export/import logfile data

    • Bitrate auto adjusts to network capabilities
    • Use TCP instead of custom protocol
    • Local file copy if the source and destination targets are on same machine
    • Checks for insufficient disk space before creating a new file
    • File progress provided via messages instead of callbacks


  • Fixed a bug where certain sensors reported the “now time” during replay mode, when they should have used “replay time”

    • Affected drivers were:
      • Delphi ESR 2.5
      • Ibeo Lux
      • Ibeo Fusion ECU
      • Velodyne HDL-32E
      • Velodyne VLP-16
  • Fixed a bug in Studio’s system observer which caused it to incorrectly report an error state when a host entered the hardware mode, but didn’t have any nodes defined in its SDF

  • Fixed a bug in the C and C++ APIs that manifested when an application unsubscribed from a message type while the subscription was in use, causing issues with an invalidated iterator and a thread that could lock since it was lacking recursive mutex support

    • The bug fix adds support for recursive locking and resolves the iterator invalidation issue
  • Added a configurable replay module grace-period timeout to fix a bug causing larger logfile sessions to fail while trying to replay within Studio

  • Fixed a bug in the dynamic driver which caused it to incorrectly skip over parameters while updating an SDF with the -u command

  • Fixed the MobilEye invalid heading angle bug

  • Fixed a bug in Studio’s Trace plugin which blocked you from selecting a destination for the CSV export file


  • PolySync Core Manager is now controlled as a system service, and accepts the commands:

    • sudo service polysync-core-manager start | stop | restart
  • The PTP service which synchronizes distributed hosts is now controlled as a system service and is started by default when the machine boots

  • Supported sensors support a message-publish toggle, to enable and disable publishing of each sensors supported messages

  • The Dataspeed drive-by-wire interface records all control commands

  • The pdm-gen tool has been updated to allow simultaneous pdm-gen data model generation processes on a single machine

    • Previously the pdm-gen tool made assumptions about where build files lived and where generated files were supposed to be installed
  • The C and C++ API documentation points out thread-safety use-cases

  • Added a loading/busy indicator to the SDF Configurator to indicate when background operations are in-progress