Downloads

Below are all of the publicly released downloads of PolySync Core that we’ve had thusfar for the x86_64 architecture. The PolySync Core release package must match your ECUs architecture and Operating System. Contact help@polysync.io to get access to a specific release package. If you’re confused about how to use these files, please read the Getting Started guide.

  • PolySync Core 2.0.9

    Release Notes
    Released Feb 13, 2017

    Name change: the PolySync platform is now called PolySync Core.

    New

    1. Support for Ubuntu 16.04

      • To take advantage of the features below, upgrade to the new Ubuntu distribution
      • Coming Soon: PolySync Core support for Ubuntu 14.04
    2. Support for the QNX® Neutrino® RTOS

    3. ROS Bridge

      • PolySync Core <> ROS bridge is now bidirectional, allowing data to flow between Core and ROS buses in real-time
      • How to use the ROS Bridge
    4. PolySync Core <> MATLAB integration (beta) provides a workflow to export data from Core to .CSV, and then import into MATLAB

      • Coming Soon:  fully-supported bridge developed in collaboration with The MathWorks to provide PolySync Core <> MATLAB class / Simulink block streaming interface
    5. Support for the Renesas R-Car H3 autonomous driving platform, running the QNX® Neutrino® RTOS

    6. Support for the NVIDIA DRIVE PX2 autonomous driving platform

    7. Support for 32 sensors and actuation systems popular in the autonomous driving environment

    8. PolySync Transcoder

      • Open source interface for accessing and converting stored logfiles (plogs)
      • Ability to introspect all Core logfiles regardless of the data model
      • Ability to decode specific sensor data through sensor descriptors, starting with the Ibeo family of LiDAR sensors
      • Coming soon: a Python binding to the PolySync logfile encoder and decoder; plugins to convert Core logfiles to hdf5 and rosbag; more sensor descriptors to decode sensor data
      • Learn more about the Transcoder, then learn how to build and install the Transcoder

    Change Log

    Technical changes from 2.0.8 to 2.0.9, that a developer would need/want to know before upgrading applications written on the older version.

    New:

    • The installation method has been simplified, and now conforms to the Debian package manager conventions

      • The GUI installer has been replaced by the Debian package installation method
      • Installation is performed using the Ubuntu Software Center, or on the command line with dpkg ─ you can see the step by step installation guide from our Help Center
    • Support for the Quanergy family of LiDAR sensors with Quanergy API version 4, and the Rev-C hardware

    • The polysync-generate node creates a node scaffolding and is capable of generating a supported sensor interface for CAN based sensors with  a DBC file

    • Studio provides an open plugin framework to create custom visualization tools for data on the PolySync bus

    • Huge repo’s full of examples, tutorials and tools geared towards learning the PolySync C and C++ APIs

      • Be sure to check out the README in each example for a description, list of dependencies and instructions on how to build and run the example or tool
    • PolySync Studio has an interface to manage logfile sessions, and coordinate record and replay operations across entire PolySync systems

    • New File Sync API which is used to export/import logfile data

      • Bitrate auto adjusts to network capabilities
      • Use TCP instead of custom protocol
      • Local file copy if the source and destination targets are on same machine
      • Checks for insufficient disk space before creating a new file
      • File progress provided via messages instead of callbacks

    Fixed:

    • Fixed a bug where certain sensors reported the “now time” during replay mode, when they should have used “replay time”

      • Affected drivers were:
        • Delphi ESR 2.5
        • Ibeo Lux
        • Ibeo Fusion ECU
        • Velodyne HDL-32E
        • Velodyne VLP-16
    • Fixed a bug in Studio’s system observer which caused it to incorrectly report an error state when a host entered the hardware mode, but didn’t have any nodes defined in its SDF

    • Fixed a bug in the C and C++ APIs that manifested when an application unsubscribed from a message type while the subscription was in use, causing issues with an invalidated iterator and a thread that could lock since it was lacking recursive mutex support

      • The bug fix adds support for recursive locking and resolves the iterator invalidation issue
    • Added a configurable replay module grace-period timeout to fix a bug causing larger logfile sessions to fail while trying to replay within Studio

    • Fixed a bug in the dynamic driver which caused it to incorrectly skip over parameters while updating an SDF with the -u command

    • Fixed the MobilEye invalid heading angle bug

    • Fixed a bug in Studio’s Trace plugin which blocked you from selecting a destination for the CSV export file

    Changed:

    • PolySync Core Manager is now controlled as a system service, and accepts the commands:

      • sudo service polysync-core-manager start | stop | restart
    • The PTP service which synchronizes distributed hosts is now controlled as a system service and is started by default when the machine boots

    • Supported sensors support a message-publish toggle, to enable and disable publishing of each sensors supported messages

    • The Dataspeed drive-by-wire interface records all control commands

    • The pdm-gen tool has been updated to allow simultaneous pdm-gen data model generation processes on a single machine

      • Previously the pdm-gen tool made assumptions about where build files lived and where generated files were supposed to be installed
    • The C and C++ API documentation points out thread-safety use-cases

    • Added a loading/busy indicator to the SDF Configurator to indicate when background operations are in-progress

  • PolySync 2.0.8-pr.8

    Release Notes
    Released Nov 21, 2016

    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
  • PolySync 2.0.7-pr.7

    Release Notes
    Released Sep 06, 2016

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

    PR7 is recommended for all PolySync users.

    New API Docs: http://docs.polysync.io/api-docs

    New Support Center coming soon

    New:

    • A Host Wizard was added to the SDF Configurator to help with network setup, and to warn of mismatched network settings
      • Use the SDF Configurator to select the host configuration and IP address that matches your machine/ECU
    • The C++ Logfile API was added, along with examples on how to record, replay, iterate and connect to a logfile queue
    • A Vehicle OBD-II interface was added to the list of supported sensors
      • 99 common CAN ID’s supported, which can be queried on a vehicle-by-vehicle basis
      • Publishes the ps_platform_obd_msg message
    • The Neobotix USBoard Ultrasonics sensor interface was added to the list of supported sensors
      • Connect up to 16 Ultrasonic sensors to the USBoard and access zone message data from the PolySync bus
    • The Video plugin has a toggle for object message overlay
      • For objects without a 3D size, such as the MobilEye 560 which only provides width, the object is represented with a line rather than a 2D rectangle:
      • <——–>
    • 3D View can visualize zone messages, which are commonly output by Ultrasonic sensors
    • New message support for the OxTS RT3000 interface
      • Now supporting Batch 2 and Batch 3 channel data

    Fixed:

    • Fixed the GUI installers premature file-copy bug
    • Squashed a bug causing the license tool Host ID field to change, when a new network device was connected
    • Resolved a bug that was causing the license tool Host ID field to change, when a new network device was connected
      • A persistent Host ID can be set in the polysync/utils/<arch>/etc/config/ospl.xml file
    • Fixed a bug within Studio causing the application to hang on startup when the license was invalid
    • Fixed a threading issue within Studio causing a crash when closing plugins
    • Fixed a bug with the MobilEye driver, which caused the lane model to have an inverse curvature value
    • Fixed the Velodyne LiDAR points message timestamping mismatch in the replay queue
      • The replay message->header.timestamp value is now preserved from the recorded data (ps_byte_array_msg)
      • This allows a custom application to access the native timestamp data, before the data is published to the PolySync bus
    • Fixed the Video plugin bug so that the aspect ratio is maintained during decoding
    • Fixed the C++ CANChannel object constructor bug following the changes in PR6

    Changed:

    • The default PolySync IP address was changed from AUTO, to 127.0.0.1
      • Multicast must be enabled for PolySync’s DDS communication layer to work on the loopback interface
      • It’s recommended to use the loopback (lo, 127.0.0.1) for single machine PolySync systems
      • The IP address can be changed with the command polysync-manager -s xxx.xxx.xxx.xxx
      • The polysync_post_install.sh script persistently enables multicast across reboots for the loopback interface
    • The Logfile API has a new ‘Readying’ state which has been added to the state machine to handle the intermediate management between activation and ready
      • The Asynchronous Record & Replay log session management previously blocked during activation and deactivation
      • The blocking state was moved to the synchronous version of Record & Replay
    • The license tool indicates directly whether a license is valid or not
      • Call polysync-license-tool to check your license status
    • The C++ Application Node was updated
      • Previously the Application Node was calling std::future::get() when the method had already finished giving undefined behaviour
    • The Node destructor will wait for release state to finish before destructing
      • The Application Node destructor does not call disconnectFromPolySync, as this was already happening on the Node destructor
    • Studio Trace prints double types with full precision
    • The C++ System API now has appropriate const usage throughout the get routines
    • Xsens debug flag added to print position, orientation and acceleration data to stdout for testing
    • Supported sensor links from the SDF Configurator updated to point to the new polysync.io URL
    • Optimized Studio’s shared-data module behaviour to decrease system load on the System Hierarchy rendering process
      • This affected systems with 15+ nodes being spawned at the same time
  • PolySync 2.0.6-pr.6

    Release Notes
    Released Jul 13, 2016

    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.

    New:

    • 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:

    • 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

    Changed:

    • 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 xxx.xxx.xxx.xxx’ 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

  • PolySync 2.0.4-pr.4

    Release Notes
    Released May 18, 2016

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

    New

    • The Debug console displays errors, warnings and other PolySync log messages within Studio
      • Quickly filter for messages of interest, and avoid that extra terminal window!
    • The newest example application Echo allows you to quickly print, filter and log CSV data from the command line, neat!
    • Self-managed and cloud floating license servers for your Autonomy / ADAS / HMI development teams
      • Floating license server allows you to manage a pool of PolySync licences on a local server

    Fixed

    • Fixed a bug causing logfile replay issues with sessions recorded in sequence
    • Studio was being rude and sometimes consuming all the processing time of a single CPU. Studio apologizes.
    • Fixed a bug within the Replay module when a logfile session that’s already playing is reselected
    • Fixed a bug within the C++ API that prevented applications from printing messages to stdout
    • Fixed a bug that disallowed double types to accept negative values in the SDF Configurator
    • Fixed a bug to allow C++ record and replay examples to compile

    Changed

    • The C++ application node abstraction hides a lot of the nitty-gritty details and provides a clean interface to the PolySync bus
    • Core logging utility migrated to use a central, configurable logging system
      • Applications log to the PSYNC_HOME/polysync.log file for all error, warn, info and debug messages
      • Default configuration does not log to the Linux syslog
    • Studio backend refactored to use the updated application node
      • Enforce applications to maintain a single instance of polysync::node
    • Ibeo ScaLa interface visualization updates
      • ScaLa reports two messages, one per mirror side
      • We added parameters to allow publishing of one or both mirror sides, and a basic stitching parameter to combine mirror sides

    Known Issues

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

  • PolySync 2.0.5-pr.5

    Release Notes
    Released May 15, 2016

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

    New

    • 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

    • 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

    Changed

    • 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

  • PolySync 2.0.3-pr.3

    Release Notes
    Released Apr 20, 2016

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

    New

    • New custom data model and logfile API examples
    • Excellent new lane model visualization in the Studio World 3D plugin
    • Export logfile data quickly into custom formats or applications
      • Logfile for-each iterator processes logfiles outside the PolySync time-domain
    • Logfile record sessions now have a duration indicator
    • Diagnostic Trouble Code (DTC) module added to the default data model
      • This flexible module allows you to add custom DTCs to your PolySync applications
    • Point Grey GigE interface now allows you to set the operation mode
    • Snazzy new splash screens and desktop icons for PolySync Studio and SDF Configurator
    • SDF Configurator node entries link directly to Supported Sensors page
    • Activation is now handled in the GUI installer. Simply enter your Activation ID when prompted and we’ll take care of the rest. If you have an existing license, the installer will download it for you automagically. High five.

    Fixed

    • Destroyed an issue where World 3D plugin (while drawing objects) would cause Studio to crash
    • Zapped a memory leak by fixing our read thread mechanism for copying dynamic terminal types within the Logfile API
    • Fixed time alignment issues with overlayed data in the Video plugin
    • Improved seek logic for replay operations within the logfile API
    • C++ vectors can now be set to empty or size 0
    • Fixed an issue where the reference count for nodes recording logfile data was not reporting accurately.
    • Added a missing delimiter to the C++ parameter get/set object
    • Annihilated an issue where CAN devices would hang while they parsed the sensor identifier
    • Schooled polysync::Message::print to accept std::ostream argument
    • Destroyed a null string bug in SDF API
    • Buried an issue where the Host tab name wouldn’t update until SDF Configurator restarted
    • Resurrected the tree-view file browser in our API docs
    • Blasted a bug where logfile replay timestamps did not reflect the published timestamp
    • Law & Order: Xsens data transformation is now applied prior to being published on the bus
    • KO’d an issue where MobilEye timestamps were not properly reported during replay
    • Ibeo devices now accept custom port values from the SDF Configurator. Friends4ever.

    Changed

    • System Hierarchy plugin no longer displays disabled nodes from the SDF Configurator
      • Because you disabled them…
    • Node Template API now returns specific DTCs for application exit status from psync_node_main_entry()
    • Dynamic driver interfaces default to vehicle platform coordinate frame, instead of the sensor local frame
      • Now you can view all sensor data in a unified coordinate frame
    • PolySync Manager can now accept commands, and return responses through two new message types
    • This makes it easier to manage the PolySync runtime
    • All C++ character sequences are returned as std::string
      • The old way would flip-flop between returning std::string or std::vector, and we’re sorry
    • Reset schema function has been moved to the menu bar of the SDF Configurator. You’ll get a warning dialog, too.
    • The logfile session browser populates faster and more dependably
      • Because you’ve got better things to do.
    • PolySync Installer package is now 400MB lighter
      • Because compression.

    Known Issues

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

  • PolySync 2.0.2-pr.2

    Release Notes
    Released Mar 22, 2016

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

    New

    • Fixed an issue where System Hierarchy was causing Studio to crash
    • Lane model in Video Overlay
      • See lane models drawn over video stream, live and in replay
    • LiDAR in Video Overlay
      • See LiDAR points drawn over video stream, live and in replay
    • Parameter Get/Set capability
      • Set mount position live and see sensor data transformed in the 3D Viewer
    • SainSmart 16 channel USB controller support
    • Control power for up to 16 sensors using the SDF Configurator and toggle states with Get/Set in Studio.

    Fixed

    • Installer
      • Installer now manages root access so sudo is no longer required.
      • Updated LinuxCAN to 5.14.
      • Fixed permissions bug
    • Ibeo fusion ECU CAN writer yaw rate signal fix
      • Yaw rate now scales correctly.
    • Manager node not killing all nodes fix
      • Manager can now kill any nodes it spawns.

    Changed

    • MobilEye 560 publishing lane model messages
      • Subscribe to lane model messages with MobilEye dynamic driver

    Known Issues

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

  • PolySync 1.0.1

    Release Notes
    Released Nov 01, 2015

    There are no release notes for v.1.0.1.

End User License Agreement

END USER LICENSE AGREEMENT

PLEASE SCROLL DOWN AND READ THIS ENTIRE END-USER LICENSE AGREEMENT (this "Agreement").  This Agreement is a legal agreement between you, either an individual or a legal entity ("You") and POLYSYNC TECHNOLOGIES, INC., a Delaware Corporation ("PolySync") that sets forth the terms and conditions governing Your use of the Software and the Documentation. 

BY CLICKING THE ACCEPT BUTTON BELOW, OR BY DOWNLOADING, INSTALLING OR OTHERWISE USING THE SOFTWARE, YOU AGREE TO BE BOUND BY THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS AGREEMENT, THEN DO NOT CLICK THE ACCEPT BUTTON, INSTALL, DOWNLOAD, OR USE THE SOFTWARE. If the License to the Software is purchased by an entity or the Software is used or evaluated for the benefit of an entity, then these terms are agreed to on behalf of such entity, and the individual executing these terms hereby represents to PolySync that such individual is authorized to accept these terms on behalf of such entity.  Otherwise these terms are agreed to by an individual.

1. Software, Licenses and Documentation.  

(a) Software and Licenses. This Agreement applies to software programs ("Software") which You have licensed from PolySync or PolySync"s authorized reseller ("Authorized Reseller").  The invoice issued by PolySync or such Authorized Reseller ("Invoice") will specify the number of licenses purchased by You (each such license a, "License") and the name and version of the Software licensed thereunder.  Software includes any Updates PolySync may make available to You, and such Updates will be subject to this Agreement. Unless otherwise specified in the Invoice, each License corresponds to a single, specific computing workstation identified at the time of initial installation ("Site"). 

(b) Documentation. You may be provided with electronic or physical documentation concerning the Software, which provides relevant information regarding the Software"s use and features ("Documentation").

2. Grant of License.   Subject to the terms and conditions of this Agreement and payment of all applicable fees, PolySync hereby grants to You a nonexclusive, nontrans_ferable (except as set forth in Sections 12 and 17) license during the applicable period of the License, as set forth herein or in the applicable Invoice (the "License Term") to (a) use the Software solely (i) for Your internal business purposes; (ii) at the Site(s); and (iii) for such number of Licenses, in each case of (i)-(iii) as are purchased by You and identified in the applicable Invoice and (b) use the Documentation in connection with the foregoing permitted use of the Software.  Irrespective of the use of the term "sale", "sell" or the like, the Software and Documentation are licensed only.

3.   Evaluation Software

(a) Section Applicability. This Section 3 applies only if the Software You have been licensed is on an evaluation or other temporary basis, or You have otherwise rightfully obtained the Software from PolySync at no cost ("Evaluation Software"). If this Section 3 applies to You, and a provision in this Section 3 conflicts with any other provision of this Agreement, then the provision in this Section 3 shall govern in connection with Your use of Evaluation Software.

(b) Activation.  Your license term for the Evaluation Software (the "Evaluation Term") is fourteen (14) days from delivery unless otherwise authorized in writing by PolySync in its sole discretion.  Your right to use the Evaluation Software and Documentation is limited to evaluating the suitability of the Evaluation Software for licensing on a for-fee basis.

(c) Evaluation Term. After the end of the Evaluation Term for the Evaluation Software, Your right to use the Evaluation Software will automatically end, unless You purchase a License.

(d) No Warranties.  POLYSYNC HEREBY DISCLAIMS ALL REPRESENTATIONS, WARRANTIES, AND LIABILITY WITH RESPECT TO EVALUATION SOFTWARE, INCLUDING ANY DAMAGES RESULTING FROM USE (OR INABILITY TO USE) EVALUATION SOFTWARE.

(e) No Support.  PolySync has no duty to provide Updates, Support or any other Maintenance (as such terms are defined below) to You with respect to the Evaluation Software.

(f) Conversion.  Please contact PolySync or an Authorized Reseller if You wish to purchase a License for the Software.

4. Restrictions.  All rights in and to the Software and Documentation not specifically granted under this Agreement are reserved.    You will prevent access to and use of the Software and Documentation by third parties, except for third parties using the Software and Documentation solely in connection with the authorized provision of services to You.  You may only use the Software and Documentation subject to with the following restrictions: 

(a) Software and Documentation may be used solely for Your own internal use and solely for Your own benefit.

(b) You may make one copy of the Software in machine-readable form solely for backup purposes.  You shall reproduce on any such copy all copyright notices and any other proprietary legends on the original copy of the Software.  You may not remove or obscure PolySync"s or any third party"s copyright, trademark, or other propriety notices or legends from the Software or Documentation. 

(c) You may not  do any of or permit or enable others to do any of the following with regard to the Software or Documentation: (i) decompile, disassemble, reverse engineer, or otherwise derive the source code from it, or attempt to do so, except to the extent permitted by applicable law; (ii) disclose, distribute, sell, sublicense, display, publish, modify, adapt, alter, transfer, or create derivative works from it; (iii) circumvent any usage restrictions, whether time-based, workstation based, or otherwise; (iv) rent, lease, resell, sublicense, or grant a security interest in it.  Any attempt to do any of the foregoing shall be void and of no effect.

(d) You may not use the Software or Documentation (i) to develop any application having the same primary function as the Software; (ii) to provide any services to third parties, including without limitation any service bureau, application service provider or hosting service; (iii) in operating an on-line service, bulletin board, Web or Internet access service or enabling Your customers to access such services or use data received from such services. 

(e) You will treat the Software as confidential information and a trade secret of PolySync, and will only use and disclose the Software to the minimum extent necessary in connection with the uses of the Software permitted by this Agreement.  You will use at least reasonable efforts to keep the Software confidential and not provide it to third parties without a need to know. 

5. Payment. Your rights to use the Software are subject to Your timely paying all amounts due, whether to PolySync or the Authorized Reseller, as applicable.  Payment terms for payments due are as stated in Invoices issued by PolySync or its Authorized Reseller or as agreed between You and such Authorized Reseller.  All amounts paid are non-refundable.

6. Term and Termination. 

(a) Term.  This Agreement will terminate automatically upon the earlier of: (i) Your failure to comply with any term of this Agreement; (ii) the end of the Evaluation Term (unless You purchase a License); or (iii) the end of the License Term, as applicable. The License Term for the purchased Licenses is either perpetual ("Perpetual License") or a subscription for a limited term ("Subscription License"), as specified in the Invoice. Unless either party terminates this Agreement by notifying the other party in writing at least thirty (30) days before the expiration of the then current License Term, the License Term will automatically renew for additional consecutive periods of equal duration as the immediately preceding License Term. For Subscription Licenses, Maintenance is provided at no additional cost for the duration of the applicable License Term.  For Perpetual Licenses, the initial term for Maintenance (as defined in Section 7(b)) of the Software is one (1) year beginning on the date the applicable License is purchased, and, subject to payment of the annual Maintenance fee as described in Section 7c, will automatically renew for additional one (1) year periods (collectively, the "Maintenance Term") unless either party provides a notice to the other at least thirty (30) days before the renewal date that it does not wish for the Maintenance Term to renew. If You elect not to renew the Maintenance Term, PolySync shall have no further obligation to provide Maintenance.

(b) Termination " by You.  You may terminate this Agreement at any time by issuing a written notice to PolySync identifying the Licenses You are terminating and the effective date thereof.  You will not be entitled to receive a refund of any amounts prepaid. 

(c) Termination " by PolySync.  PolySync will provide written notice to You if You are in breach of this Agreement. 

(d) Effect of Termination.  You must destroy all copies of Software and Documentation in Your possession immediately after the termination or expiration of this Agreement.  Amounts accrued hereunder prior to the expiration or termination shall continue to be due even if this Agreement is terminated and shall be paid in accordance with Section 5. Sections 4, 5, 6, 8, 9, 10, 11, 17, 18, 19, 20, and 21 shall survive the termination or expiration of this Agreement.

7. Updates and Support. 

(a) Updates.  The terms of the Agreement will govern any bug fixes or error corrections to the Software ("Updates"), if any, subsequently provided by PolySync during the Maintenance Term. 

(b) Support. PolySync will use commercially reasonable efforts to respond during regular business hours to Your requests for support during the Maintenance Term ("Support", and together with any Updates, "Maintenance"); however, given the nature of the Software, PolySync cannot guarantee that all identified issues will be resolved, through Updates, Support, or otherwise, to Your satisfaction.

(c) Maintenance Fees. If you purchase a Perpetual License, You agree to pay annual Maintenance fees, which shall be based on a percentage of the then-current list price for the Software, for any renewal of the Maintenance Term for the Software.  You will be invoiced for each renewal of the Maintenance Term approximately sixty (60) days prior to renewal. Maintenance includes Updates to the Software, but not new releases of the Software ("Upgrades"). Upgrades must be purchased separately from PolySync or its Authorized Resellers. Subscription Licenses include the cost of Maintenance in the fees paid for the License.

8. Feedback and Data.

(a) Feedback. If You provide feedback to PolySync concerning the Software ("Feedback"), PolySync may use it for any purpose, including to improve or enhance its products and services.  You hereby grant PolySync a non-exclusive, perpetual, irrevocable, royalty-free, assignable, worldwide license to use, reproduce, disclose, sublicense, distribute, modify, and otherwise exploit such Feedback without restriction.

(b) Data.  As a result of Your use of the Software, certain data, statistics and other information (collectively "Information") may be generated either automatically by the Software or as a direct result of Your use.  The Software contains features whereby Information is delivered to PolySync automatically and Information may also be collected by PolySync in connection with the provision of any support or maintenance services (if any) for Software.  PolySync may collect, store, use and exploit such Information for the purposes of supporting, improving and developing PolySync"s products and services, provided that such use of data shall be in compliance with any applicable laws or regulations regarding data privacy and data security.  PolySync will not publicly disclose Information in a way that identifies You or Your end users, to the extent applicable, without Your consent.  You may not interfere with PolySync"s collection of Information.

9. NO WARRANTIES; DISCLAIMERS. 

(a) TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE SOFTWARE IS PROVIDED ON AN "AS IS" BASIS WITHOUT ANY WARRANTIES BY POLYSYNC, ITS RESELLERS OR THEIR LICENSORS, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, QUALITY, ACCURACY, TITLE, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE, ANY WARRANTY THAT MAY OTHERWISE ARISE FROM A COURSE OF DEALING OR USAGE OF TRADE, OR ANY WARRANTY THAT THE SOFTWARE WILL OPERATE UNINTERRUPTED OR BE ERROR-FREE.  YOU ACKNOWLEDGE AND AGREE THAT THE SOFTWARE IS USED AT YOUR SOLE RISK.

(b) THE SOFTWARE IS NOT INTENDED FOR USE IN SITUATIONS OR ENVIRONMENTS WHERE THE FAILURE OR TIME DELAYS OF, OR ERRORS OR INACCURACIES IN, THE CONTENT, DATA, OR INFORMATION PROVIDED BY THE SOFTWARE COULD LEAD TO DEATH, PERSONAL INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE, INCLUDING, WITHOUT LIMITATION, CRITICAL SAFETY SYSTEMS, THE OPERATION OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL SYSTEMS, LIFE SUPPORT MACHINES, OR WEAPON SYSTEMS.

10. LIMITATION OF LIABILITY.  EXCEPT FOR POLYSYNC"S INDEMNITFY OBLIGATIONS AS SET FORTH IN SECTION 11 BELOW, UNDER NO CIRCUMSTANCES WILL POLYSYNC, ITS LICENSORS OR RESELLERS BE LIABLE FOR ANY CONSEQUENTIAL, SPECIAL, INDIRECT, INCIDENTAL, OR PUNITIVE DAMAGES OR DAMAGES FOR LOSS OF USE OF ANY PRODUCT, SALES, PROFITS, BUSINESS INFORMATION, DATA, OR OTHER SUCH PECUNIARY LOSS ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE OR DOCUMENTATION, HOWEVER CAUSED, ON ANY THEORY OF LIABILITY (INCLUDING WITHOUT LIMITATION NEGLIGENCE, BREACH OF CONTRACT, OR OTHERWISE), EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.  IN NO EVENT WILL A RESELLER"S OR POLYSYNC"S AGGREGATE LIABILITY FOR DAMAGES ARISING OUT OF THIS AGREEMENT EXCEED THE FEES PAID BY YOU TO POLYSYNC OR ITS RESELLER UNDER THIS AGREEMENT.  THESE LIMITATIONS WILL APPLY NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED OR EXCLUSIVE REMEDY.

11. Indemnification.  PolySync shall defend You, at its own expense, against any claim, suit or action against You brought by a third party to the extent that such claim, suit or action alleges that the Software as delivered by PolySync and used in accordance with this Agreement infringes any patent, copyright or trade secret of a third party (the "Claim"), and PolySync will pay costs and damages (including reasonable attorneys" fees) finally awarded by a court of competent jurisdiction for such Claim or amounts agreed to by PolySync in a monetary settlement of such Claim.  The foregoing obligations are conditioned on You:  (a) promptly notifying PolySync in writing of such Claim; (b) giving PolySync sole control of the defense thereof and any related settlement negotiations; and (c) cooperating and, at PolySync"s request and expense, assisting in such defense.  In the event that the use of the Software is enjoined, PolySync shall, at its option and at its own expense, either (i) procure the right to continue using the Software, (b) replace the Software with a non-infringing but functionally equivalent product, or (c) modify the Software so it becomes non-infringing; provided that if none of the foregoing is commercially practicable in PolySync"s reasonable judgment, PolySync may then terminate this Agreement without liability to You.  Notwithstanding the foregoing, PolySync will have no obligation under this Section 11 or otherwise with respect to any Claim based upon: (i) any use of the Software in combination with products, equipment, software not supplied or approved by PolySync, if such infringement would not have occurred but for the combination; (ii) any modification to the Software not supplied or approved by PolySync, if such infringement would not have occurred but for such modification; or (iii) any unauthorized use of the Software.

12. Transfer of Software.  During the License Term, You may move a License for Software to a different Site.  However, You acknowledge that such transfer may require You to contact PolySync for support. After the transfer, You must completely remove the Software from the former Site. NOTWITHSTANDING THE FOREGOING, YOU MAY NOT TRANSFER EVALUATION SOFTWARE, OR BETA OR PRE-RELEASE COPIES OF SOFTWARE.

13. Agreement Updates.  PolySync may update this Agreement from time to time after Your License Term has begun.  Such updates to this Agreement (the "Updated Agreement") will apply to You: (i) with respect to new Licenses or Upgrades You may purchase after the Agreement is updated; and (ii) with respect to Updates which require You to accept such changes to this Agreement in order to use such Updates.  If You accept such Updated Agreement, or install or otherwise use such updated or upgraded Software after such changes to this Agreement, then You acknowledge and agree that You are bound by and agree to the terms of such Updated Agreement.

14. Open Source.  The Software may contain open source software.  The open source software and the corresponding license terms governing the use of such open source software are available on PolySync"s website at https://polysync.io/open-source-credits.  By accepting the terms of this EULA, You are accepting the terms of the open source license agreements that govern the use of such open source software, including all disclaimers of warranty and limitations of liability set forth therein.  Such open source software is licensed to You under the applicable open source license terms.

15. Export Restrictions.  You may not export or re-export the Software without complying with all applicable export control laws and obtaining any necessary permits and licenses.

16. Government Use.  You agree that the Software and related Documentation are "Commercial Items", as that term is defined at 48 C.F.R. "2.101, consisting of "commercial computer software" and "commercial computer software documentation", as such terms are used in 48 C.F.R. "12.212 or 48 C.F.R. "227.7202, as applicable.  This customary commercial license to the Software and Documentation is provided in accordance with FAR 12.211 (Technical Data) and FAR 12.212 (Software) and, for Department of Defense transactions, DFAR 252.227-7015 (Technical Data " Commercial Items) and DFAR 227.7202-3 (Rights in Commercial Computer Software or Computer Software Documentation). The Software and Documentation is being licensed to U.S. Government end users (a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein.  Unpublished-rights reserved under the copyright laws of the United States.

17. Assignment. You may not assign or transfer this Agreement or the rights hereunder, by operation of law or otherwise, including in connection with a merger or other acquisition, without the prior written consent of PolySync. PolySync may freely assign or transfer this Agreement. 

18. Reference.  You hereby permit PolySync to refer to You as a user of the Software and display Your logo in PolySync"s marketing documentation and on its web site, in compliance with Your trademark usage guidelines.  Upon Your written request, PolySync will cease making such use of Your logo.

19. Severability and Waiver. If any provision of this Agreement is held invalid or unenforceable, the remainder of this Agreement will continue in full force and effect.  Failure to enforce any right or provision in this Agreement will not constitute a waiver of such provision, or any other provision of this Agreement.  Waiver of a breach shall not waive the right to enforce any subsequent breach under this Agreement.  No failure to exercise, and no delay in exercising, on the part of either party, any right or any power hereunder shall operate as a waiver thereof, nor shall any single or partial exercise of any right or power hereunder preclude further exercise of any other right hereunder.

20. Entire Agreement. This Agreement and PolySync"s Invoices form the complete statement of the agreement between You and PolySync with respect to the Software and Documentation, and there are no other prior or contemporaneous understandings, promises, representations, or descriptions with respect to the Software or Documentation.  For the avoidance of doubt, to the extent any non-disclosure agreement between You and PolySync conflicts with the terms of this Agreement, the agreement that is most protective of PolySync"s confidential information shall prevail.  Except as provided for herein (including as set forth below), no amendment to or modification of this Agreement will be binding unless made in writing and signed by PolySync.   No terms, provisions or conditions of any purchase order, acknowledgement or other busi_ness form that You may use in connection with the licensing of the Software will have any effect on the rights, duties or obligations of the parties under, or otherwise modify, this Agreement, regardless of any fail_ure of PolySync to object to such terms, provisions or conditions.  Any terms in such documentation issued by You are void.

21. Governing Law and Venue.  This Agreement will be interpreted and construed in accordance with the laws of the State of Oregon and the United States of America, excluding that body of law applicable to choice of law.  The application of the United Nations Convention of Contracts for the International Sale of Goods to this Agreement is expressly excluded.  The parties consent to non-exclusive jurisdiction in the state or federal courts for Multnomah County, Oregon and, such venue shall not be challenged by the non-filing party as improper or inappropriate due to, among other things, inconvenience under the doctrine of forum non-convenience or other similar doctrines.  Each party also agrees not to bring any action or proceeding arising out of or relating to this Agreement in any other court.   Notwithstanding the foregoing, You acknowledge and agree that a breach of this Agreement by You would cause irreparable injury to PolySync for which monetary damages would not be an adequate remedy.  Therefore, PolySync shall be entitled to obtain equitable relief in addition to any remedies it may have hereunder or at law, without the necessity of posting a bond, and in any court of competent jurisdiction.

Download