Release Notes

Core 2.3.0

New

  • PolySync Core is now available in an APT repository, which means you can let the package manager handle updates. See instructions for getting set up here
  • Added headless support for the following Tier 2 architectures
    • armhf Raspberry Pi 2 - Yocto Pyro
  • Now offering a bootable PolySync enabled Yocto Linux SD image
  • New drivers
    • Delphi ESR Ethernet
    • LeddarTech Leddar Vu8
  • New sensor-specific data types for the added drivers that allow users to utilize Ethernet in addition to existing CAN support
  • The polysync-generate tool can now generate Studio plugin scaffolding to speed up development

Fixes and Updates

  • Core
    • polysync-generate tool has been migrated from Python to Rust, this removes python as a required dependency for users
    • PolySync CAN API now defaults to socketcan libraries rather than linuxcan
    • EULA moved to command line
    • polysync-license-tool now reports all Core Debian package versions rather than the polysync-core-c-api package version, this adds transparency to the user following updates and installs
    • Drivers
      • Quanergy M8 driver updated to support API v5
      • Swift Navigation Piksi driver updated to comply with firmware 1.1.27:libsbp 2.2.1
      • Installing NVIDIA drivers no longer causes linking problems with libGL, errors, or requires any action on the user’s part. For existing installations there is a tool in this release called polysync-gl-linker that will resolve the issue in your development environment.
    • Studio
      • 3d and Video plugins can now be paused during replay for inspection of the scene
      • Video plugin revised its approach to what “flip” means. Instead of rotating 180°, it now only mirrors across the X axis
      • 3d plugin has improved visualization logic for ps_zones_msg to support data published by the Leddar Vu8 driver and user applications
      • Optimized CPU utilization, down 50% on average
      • User can now enter standby mode if replay fails, rather than restart Studio
      • Fixed a configuration file issue that cause Studio to occasionally crash
      • Improved column resizing in System Hierarchy plugin and SDF Configurator

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
    • Swift Navigation Piksi reports invalid data for heading and speed
    • Dynamic driver nodes will sometimes report “failed to wait for clock tick condition” during replay
      • Recovery steps: Restart the runtime environment by placing all nodes in ‘Standby’ state in Studio, then select the desired logfile session for playback
  • Data Model Code Generation
    • polysync-pdm-gen can confuse custom variable names with types, i.e. “long longitude” is interpreted as “long long itude”. Workaround, use a different name for your variable, this fix will be available in 2.4.0
  • 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 help@polysync.io
  • Studio
    • 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 incorrect with the session. For example, seek-to-time will not work on the remote session
    • Occasionally a “Failed to wait for clock tick condition” error is reported to Studio’s console and the polysync.log. This does not affect the replay 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