Supported Sensors

Synchronization Trigger


Sensor background and requirements

The Synchronization Trigger outputs a low voltage signal at a consistent frequency. This allows you to synchronize two or more sensors that support external trigger mechanisms.

Hardware requirements

  • An ECU with a USB port
  • An ECU with PolySync Core installed

Sensor Notes

This sensor does not publish any messages to the PolySync Core Bus. It only outputs a signal for synchronization of sensors that support external trigger mechanisms.

Configuring the PolySync Core driver

Validating the sensor is properly configured

If you’re approaching a new PolySync Core system or need to validate an existing configuration you can use the following checklist to ensure the sensor is properly configured.

Setup checklist

  • The sensor is connected to a USB port
  • The sensor is powered on

Starting the PolySync driver

The configuration set in the Configurator is loaded from the SDF when the dynamic driver starts. It connects to the sensor through the USB port, requests the data, and waits for confirmation that the sensor configuration is valid.

  1. Power the ECU on
  2. Optionally follow the set up checklist
  3. Start the PolySync Core manager
    • $ sudo service polysync-core-manager start
  4. Start the dynamic driver process

Starting the node manually on the command line

To start a dynamic driver node on the command line, the node must first be defined in the SDF using the Configurator application.

Each node defined in the Configurator has a unique node ID which points to the nodes configuration. This article explains how to find the node ID.

Command line flags and usage

Once the node ID is known (substitute for X), the dynamic driver node for the supported sensor can be started with the base command:

$ polysync-core-dynamic-driver -n X

Each sensor supports an array of command line arguments. To see a full list of command line arguments, pass the -h help flag:

$ polysync-core-dynamic-driver -n X -h  |  less

There’s a lot of output so we recommend you pipe the output to less, but it’s not required.

Flag Required Description Arguments
-d No enable additional debugging output in the interface
-e No export a JSON support string describing the interface, used by the SDF configuration tool
-h No Show the help message
-i <> No Use provided PAL interface file instead of what is stored in the SDF Path to the dyanmic driver interface PAL shared object library
-r <N> No SDF runtime configuration key that specifies the domain to operated under, the default domain is used otherwise Runtime configuration key, [0-65536]
-s <psync.sdf> No Use provided SDF instead of the default File path to an SDF file
-u No Allow updates to the SDF configuration during the normal runtime if needed (does not exit)
-U No Update the node SDF configuration and exit