Release Notes

Core 2.0.6-pr.6

Known Issues:

We’re aware of an issue where the GUI installer will fail to properly update or install a new instance of PolySync. The issue was caused by an compression extraction bug in the installer provided by a vendor. Good news is that we have a fix ready for the next PolySync release (pr.7). In the meantime, please use the tarball (tar.gz) package provided and command line interface to install PolySync. Instructions can be found here. Thank you for your patience and understanding while we fix this issue.


  • Scrolling interface for the SDF Configurator parameter table
  • We have added a File Transfer API, which will facilitate the new logfile management features and also allow you to pass data around, anywhere!


  • Fixed a bug in the C++ polysync::Node empty constructor, causing undefined behaviour in unused event methods
  • Fixed the issue causing Studio to lock up, when the polysync.log file contained 5k+ entries

    • The zlog configuration file is configurable to limit the size, or rotate the log to save all data
    • Studio Console limits the number of entries it will load on startup to prevent similar issues
  • Fixed the Trace plugin when one or more column of data would stop updating

  • Fixed the Replay control module usage for node synchronization

  • Found a bug within the Video plugin image decoder, where the output resolution was a constant 640x480

    • Now the displayed aspect ratio will always match the published aspect ratio
  • Fixed the missing SDF IO parameters for the Ibeo family of sensors for the default SDF shipped in the release


  • The PolySync Manager will no longer update the SDF when the PolySync interface is set with the ‘-s’ flag

    • The IP address must be entered in the SDF through the SDF Configurator
    • Once the host is defined in the SDF Configurator, each host must execute the ‘polysync-manager -s’ command once
  • We fixed the accessibility of the timing interval for C++ API Node event methods

    • Previously the default sleep occurring under the hood of each occurrence of Node::okStateEvent(), which was adjustable by calling Node::setOkStateTimingInterval()
    • We’ve brought the default timing for all states to the default virtual event functions in the base class, allowing full control when each event method is overridden
  • Studio Console will expand and line wrap when you double-click on a log message

  • Optimization in the C++ PolySync bus-to-node message passing by removing unnecessary MessageListener::executeListener sleeps

  • Revised the replay module publish timestamp behavior

    • Replay module will only update a message.header.timestamp value when the node is configured to publish the message type
    • If it’s configured to only use the replay queue, then the message.header.timestamp value is preserved

    • This lets the driver/interface/user decide how to use the native timing data if desired