Release Notes

Core 2.0.8-pr.8

PR8 is recommended for all users. It contains many features requested by our customers, including QNX real-time operating system support and a beta ROS bridge. Studio has been reworked substantially to simplify capturing, importing, organizing, and exporting of logfile sessions. You can now manage logfile sessions in a “virtual file system” which allows you to manage your data in a non-destructive environment.

Check out Help Center articles on replaying logfile sessions, and exporting/importing logfile sessions for more details. If you want to replay data captured with PR7 or earlier, follow these instructions.

If you want to replay logfile data recorded with Studio before PR8, there is a specific import process to follow. Read more about it here.

New:

  • PolySync now runs on the QNX Real-time Operating System, supporting BSP V6.6
  • Studio has a massive overhaul to support the new log file management tools

    • A new approach to recording, organizing, and replaying PolySync logfile sessions
    • See this article for the workflow of importing existing logfile data
  • A new unidirectional ROS bridge to send PolySync messages to the ROS bus

    • A bidirectional bridge is coming soon!
  • We have created a new Help Center from the ground up: http://help.polysync.dev/

    • New tutorials have been added for developers to introduce C and C++ API concepts
    • Added verbose supported sensor configuration articles
  • New Dynamic Driver interface for the Novatel OEM6 family of sensors

  • New Dynamic Driver interface example, with full source code for the phidget spatial accelerometer

  • Added message publishing toggles for each supported sensor

    • Also added the ability to enable the publishing of low-level messages (non-abstracted data) such as byte array or CAN frame messages
  • PolySync now supports the Novatel OEM6 Framework sensors such as the ProPak6 for RTK

  • A new C example was added to demonstrate how a data-producing node responds to incoming record and replay commands to read/write data from the disk using the Logfile API

  • A new C++ example was added to demonstrate how a multi-threaded application is architected

Fixed:

  • Fixed the Unity .desktop files for Studio and SDF Configurator desktop icons

    • You may need to re-dock the icons to the Ubuntu launcher panel
  • Fixed a bug where Studio would segfault if there wasn’t a valid license

  • Fixed a bug where the C++ message print routine was traversing the image data buffer accidentally

  • Fixed a bug which caused video device set operations to be one command behind what was expected

  • Fixed a bug which caused a nodes command-line options from the SDF Configurator to be passed as a single token

  • Point Grey image dropouts have been resolved by updating system network buffer sizes, see more in the Driver Notes section here

  • Fixed a visualization issue in 3D View where RADAR targets with type coasted were being drawn

  • Fixed a bug with the Ibeo Lux Dynamic Driver interface scan frequency parameter type (unsigned long long vs double)

    • Redefining the node in the SDF Configurator will correct the issue
  • The video device node used to contain a duplicate parameter entry in the SDF

Changed:

  • Huge updates to the SDF Configurator parameter management (interaction?)

    • Update parameters with handy new tools
  • We’ve improved licensing support for virtual machines

  • The Dynamic Driver header struct has been appended with a new standard option, a non-breaking change for existing Dynamic Driver PAL interfaces

    • We took the opportunity to also add a max std-opts of 64, which increases the size of the Dynamic Driver header struct
    • All custom Dynamic Driver PALs need to be rebuilt to run on this PR8 version

Known Issues:

  • SIGABORT when closing Studio after logfile session import
    • This occurs after closing Studio after one or more succssful logfile session imports
    • It does not have an effect on the import process, but the PolySync runtime should be properly cleaned by stopping all nodes with the PolySync Manager
      • $ polysync-manager -f
  • The Studio Video plugin displays an invalid node/device name in the control panel