Release Notes

Core 2.0.5-pr.5

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


  • The MobilEye Lane Keeping Assist (LKA) protocol was added to the MobilEye 560 interface
    • You’re able to access and view multiple lane models (multiple lanes) and determine the lane model degree
    • Event and traffic sign stream are also published to the PolySync bus as ps_event_msg and ps_traffic_sign_msg
  • The Video API was extended to include compression profiles, and the encoder was opened up to allow for custom configuration through extended parameter support
    • The new features are available for both Point Grey GigE and video-device interfaces
  • A new Echo C++ example, which is a sophisticated reader and debugging command line tool
  • A new article is available detailing the steps to extend the PolySync data model


  • Fixed a bug that blocked the C++ SDF API from setting the parameters value field through “parameter.setValue()”
  • Fixed the permissions on the zlog lockfile to be readable and writable by all users.
    • This allows PTP to start at boot as root user, and not effect the PolySync nodes during runtime running under the normal user context
  • Added a warning dialog when a duplicate host name is detected in the SDF Configurator
  • Fixed a visual bug where debug console “All” label remained checked when all log levels were deselected


  • We’ve moved the sleep intervals in the PolySync C++ API State Handler to the Node and Application base class event
    • Previously there was a default sleep occurring under the hood after each occurrence of Node::okStateEvent(), which was adjustable by calling Node::setOkStateTimingInterval
    • We’ve brought out the default timing for unused states to the default virtual event functions in the base class
    • Now, when you override an event method you have full control over timing with the node template (state machine)
  • The license tool does not ping the license server by default
    • You must pass in the ‘-a’ flag to ping the license server and download license rights from or upload a capability response to the license server
  • Studio’s Trace plugin had a major overhaul, extending its functionality
    • Each trace starts by selecting a message from a list of active message types being published to the PolySync bus
    • Filter data structures and individual fields from incoming messages
    • Option to export the selected data to a CSV file
  • The Dynamic Driver was updated to update get/set parameter commands while in the PolySync node template Error state
  • The C++ Serial API was abstracted away from the underlying Operating System, allowing you to have control over the serial configuration and not be bound to Linux
    • You can set flow control, data bits, parity and stop bits
  • The Dynamic Driver will not enter the Fatal state while in replay (no-hardware) mode upon receiving an invalid logfile session ID to load
    • This avoids stopping and restarting all nodes if you accidentally selected the wrong or an invalid logfile session

Known Issues

We’re aware of a memory leak within DDS that affects systems looping logfiles larger than 75GB