Release Notes

Core 2.3.1

New

  • Updated headless support for DrivePX2 to use NVidia Drive API version 4.1.8.0
  • New Drivers
    • OSCC
    • VectorNav VN-300

Fixes and Updates

  • Core
    • Video supports fractional frame rates so that users can use fractional standards (such as 29.97) in addition to whole number frames per second
    • Made executables visible to sudo commands so that the full path is no longer required by the user
    • Fixed a bug in data generation where words containing long were parsed as a type so users can now have variables such as longitude with a type long
    • Signal interrupt now uses sigaction to prevent interrupt clashing between sigaction and signal
    • Drivers
      • Swift Navigation Piksi Multi
        • Added support for raw IMU messages
        • Fixed ps_gps_msg not reporting heading and speed
      • Xsens
        • Added support to populate all field in ps_platform_motion_msg
        • Users can now select all data types supported by their XSens device and adjust output frequency.
      • Leddar Vu8
        • Fixed missing header file for developers to use with CORE API

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 help@polysync.io
  • 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 incorrect 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 only presents the last value