- Host Configuration
- Runtime Node Configuration
- SDF Configuration
- Ecosystem Tools
- Application Development
- Dynamic Driver Development
PolySync Core is able to replay sensor data that’s been recorded as a logfile session.
Nodes are spawned and instructed to load logfile sessions by the Core manager and Studio’s logfile management module.
1. Start the PolySync Core manager
Theis started as a service when the ECU boots. To ensure it’s running use the command:
$ sudo service polysync-core-manager start
2. Import the logfile session
Each logfile session must be imported to the system before it can be replayed.
- Import the logfile session using Studio’s logfile manager
Skip this step if the logfile session exists within Studio’s logfile manager.
3. Replay a logfile session
Start PolySync Core Studio with the application icon, or with the command:
Studio will open in standby mode, signifying it is ready to replay a logfile session or enter hardware mode.
If the system is in a different state, put the system in the standby state.
- Open the logfile manager with the icon
- Select one of the available logfile sessions from the logfile manager table on the left side
- Each of the nodes listed in the logfile session are defined in the , which is specific to this logfile session
- Select the logfile session and drag it to the playlist pane on the right.
- Replay the logfile session by double clicking the logfile session name in the playlist pane
Each nodes status is shown in the playlist dropdown menu, where you can watch nodes change as they each load an individual
When all nodes in the selected logfile session have loaded, Studio automatically enables playback and the nodes begin publishing data to the bus.
The system state observer at the bottom-left changes from green to blue to indicate a session is being replayed and messages containing sensor data are being published to the. Studio plugins allow you to visually validate the data.
4. Validating the runtime
Visually validate the data using Studio’s plugins.
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
5. Accessing data
Once the runtime has started, nodes are publishing data to the PolySync Core bus. This allows other application nodes to access the data by subscribing to the message types being output by dynamic driver nodes.
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