Release Notes

Core 2.3.2


  • Ported PolySync DDS libraries from Vortex OpenSplice to the open source version: DDS Community.

Fixes and Updates

  • Dynamic library loading
    • Fixed a bug that caused a segfault when polysync libraries were dynamically loaded during runtime.
  • Removed examples from install
    • Prior to this release, examples were shipped and installed with polysync-core and polysync-core-headless apt packages. Documentation directs users to the public examples repos on GitHub.
  • polysync-core-studio
    • Improved column expansion in the parameter views in System Hierarchy plugin. ID column is now expandable, which makes the plugin easier to use.
  • polysync-license-tool
    • Revise --help output to show SDF record and replay directory.
  • polysync-core-cpp-api
    • Fixed a bug in session import/export API. LogSessionImport and LogSessionExport were not properly managing the lifetimes of their _syncHandle member. Depending on use-case, this causes improper ordering of destruction which showed itself when running import/export C++ examples. This fix updates the resource management for these objects to prevent the occasional error message.
    • Fixed Logfile::fillRnRStatusMessage(), the returned message is now publishable.
  • polysync-core-sdf-configurator
    • Improved column expansion in the parameter views. ID column is now expandable, which makes the tool easier to use.
    • Rnr directory path is now visible and editable. While it is recommended that users prefer the default directory, this tool was not functioning properly, and now shows the correct path.

Known Issues

  • Drivers
    • OBD-II driver sometimes fails to locate CAN channel using socketcan libraries when there are multiple channels available on a host running on Ubuntu kernel 4.8.
  • Record and Replay API
    • Some users experience difficulty creating custom nodes with record and replay functionality. An effort is underway to improve the user experience.
  • Tier 2 Platforms
    • No out of box GStreamer support on Tier 2 supported platforms. In order to use your video device it is necessary to apt install the following packages: gstreamer1.0-plugins-bad, gstreamer1.0-plugins-ugly, gstreamer1.0-plugins-base, libgstreamer1.0-dev, libgstreamermm-1.0-dev, libgstreamer-plugins-base1.0-dev, libavc1394-dev, libaa1-dev, libshout3-dev, libtag1-dev, libdv4-dev, libavfilter-ffmpeg5, libiec61883-dev.
    • Raspberry Pi 2 is not supported by the license server. Please request a license from
  • Studio
    • Occasionally Studio Console reports a “Failed to wait for clock tick condition.” Usually this does not affect the replay session, however if there is abnormal replay behavior:
      • Recovery steps: Restart the runtime environment by clicking the ‘Standby’ button ensuring it goes to green, then select the desired logfile session for playback.
    • Distributed systems issues when using replay
      • Logged error/warn/info/debug messages are not visible from remote machines
      • Studio is able to visualize data from log sessions started on a different machine, but does not correctly visualize the session data or interact with the session. For example, seek-to-time will not work on the remote session.
    • The record module does not detect dynamic driver nodes in ‘Hardware’ state that are started manually on the command line, preventing you from recording a logfile session Recovery steps: Use Studio to start nodes in the ‘Hardware’ state to work around this issue
    • Trace does not always show all values in an array. Sometimes it only presents the last value.