Release Notes

Core 2.0.7-pr.7

Note: Do not install PolySync as root. Simply follow the installation guide. The installer will request root-level password as needed.

PR7 is recommended for all PolySync users.

New API Docs:

New Support Center coming soon


  • A Host Wizard was added to the SDF Configurator to help with network setup, and to warn of mismatched network settings
    • Use the SDF Configurator to select the host configuration and IP address that matches your machine/ECU
  • The C++ Logfile API was added, along with examples on how to record, replay, iterate and connect to a logfile queue
  • A Vehicle OBD-II interface was added to the list of supported sensors
    • 99 common CAN ID’s supported, which can be queried on a vehicle-by-vehicle basis
    • Publishes the ps_platform_obd_msg message
  • The Neobotix USBoard Ultrasonics sensor interface was added to the list of supported sensors
    • Connect up to 16 Ultrasonic sensors to the USBoard and access zone message data from the PolySync bus
  • The Video plugin has a toggle for object message overlay
    • For objects without a 3D size, such as the MobilEye 560 which only provides width, the object is represented with a line rather than a 2D rectangle:
    • <——–>
  • 3D View can visualize zone messages, which are commonly output by Ultrasonic sensors
  • New message support for the OxTS RT3000 interface
    • Now supporting Batch 2 and Batch 3 channel data


  • Fixed the GUI installers premature file-copy bug
  • Squashed a bug causing the license tool Host ID field to change, when a new network device was connected
  • Resolved a bug that was causing the license tool Host ID field to change, when a new network device was connected
    • A persistent Host ID can be set in the polysync/utils/<arch>/etc/config/ospl.xml file
  • Fixed a bug within Studio causing the application to hang on startup when the license was invalid
  • Fixed a threading issue within Studio causing a crash when closing plugins
  • Fixed a bug with the MobilEye driver, which caused the lane model to have an inverse curvature value
  • Fixed the Velodyne LiDAR points message timestamping mismatch in the replay queue
    • The replay message->header.timestamp value is now preserved from the recorded data (ps_byte_array_msg)
    • This allows a custom application to access the native timestamp data, before the data is published to the PolySync bus
  • Fixed the Video plugin bug so that the aspect ratio is maintained during decoding
  • Fixed the C++ CANChannel object constructor bug following the changes in PR6


  • The default PolySync IP address was changed from AUTO, to
    • Multicast must be enabled for PolySync’s DDS communication layer to work on the loopback interface
    • It’s recommended to use the loopback (lo, for single machine PolySync systems
    • The IP address can be changed with the command polysync-manager -s
    • The script persistently enables multicast across reboots for the loopback interface
  • The Logfile API has a new ‘Readying’ state which has been added to the state machine to handle the intermediate management between activation and ready
    • The Asynchronous Record & Replay log session management previously blocked during activation and deactivation
    • The blocking state was moved to the synchronous version of Record & Replay
  • The license tool indicates directly whether a license is valid or not
    • Call polysync-license-tool to check your license status
  • The C++ Application Node was updated
    • Previously the Application Node was calling std::future::get() when the method had already finished giving undefined behaviour
  • The Node destructor will wait for release state to finish before destructing
    • The Application Node destructor does not call disconnectFromPolySync, as this was already happening on the Node destructor
  • Studio Trace prints double types with full precision
  • The C++ System API now has appropriate const usage throughout the get routines
  • Xsens debug flag added to print position, orientation and acceleration data to stdout for testing
  • Supported sensor links from the SDF Configurator updated to point to the new URL
  • Optimized Studio’s shared-data module behaviour to decrease system load on the System Hierarchy rendering process
    • This affected systems with 15+ nodes being spawned at the same time