Start the Runtime

1. Start the runtime

1.1 Prepare the runtime

The runtime is already prepared when using the default configuration and a single host system. Distributed systems require extra configuration steps.

1.2 Starting the Core manager

The Core manager is started as a service when the ECU boots. To ensure it’s running use the command:

$ sudo service polysync-core-manager start

The manager subscribes to the ps_command_msg from the PolySync Core bus . The command messages instruct the manager to start or stop runtime nodes defined in the SDF under the appropriate runtime state─hardware, replay or standby.

1.3 Starting all runtime nodes

Start all nodes defined and enabled in the system SDF by pressing the button in Studio .

The hardware button becomes active──and the system state icon toggles to orange to indicate that all runtime nodes are in the hardware state.

2. Validating the runtime

Observe the system state to check for any runtime node errors. The system state module will display a banner and the icon will be red if there are observed errors.

If errors are reported more information can be found in Studio’s console module with the icon.

Debug and error messages are also visible outside of Studio in the file $PSYNC_USER_HOME/polysync.log.

3. Accessing data

Once the runtime has started, dynamic driver nodes begin publishing data to the global PolySync bus. This allows other applications to access the data by subscribing to the message types being output by dynamic driver nodes. You can also view all messages currently being published to the PolySync Core bus using the Echo C++ example.

Determine the messages that are being published to the bus using Studio’s Trace plugin.

Generate custom applications that subscribe to these published message types using polysync-generate.