Polybench® for biosignals / reference 1.34.1
Defines the rules for START, STOP and RESET actions in relation to a SyncID.

SyncID in relation to START, STOP and RESET

Overview

Some components in Polybench function as a data source, which means that they pump data into the system. Those data sources all listen to actions that control starting, stopping and resetting the component.
To start a data source component, the START action ("START") is used; for stopping the STOP action ("STOP"); and for resetting the RESET action ("RESET").

Because in many cases you do not want to start or stop all data sources at once, Polybench offers a feature to identify groups of components that listen to one specific START, STOP or RESET call. This identification is called SyncID and can be any number, word or sentence.

This section describes how START, STOP and RESET behave in relation to a SyncID.

Details

Case 1: START without SyncID

If a START action is executed, and the Value for the action is empty, then a general start is issued.

a. Component has no SyncID defined
Component starts.

b. Component has a SyncID defined
Component does not start.


Case 2: START with SyncID

If a START action is executed, and the Value for the action has been set, then a specific start is issued.

a. Component has no SyncID defined
Component does not start.

b. Component has a SyncID defined equal to that of the action
Component starts.

c. Component has a SyncID defined different from that of the action
Component does not start.


Case 3: STOP without SyncID

If a STOP action is executed, and the Value for the action is empty, then a general stop is issued.

a. Component has no SyncID defined
Component stops.

b. Component has a SyncID defined
Component stops (!). All components stop on a general stop.


Case 4: STOP with SyncID

If a STOP action is executed, and the Value for the action has been set, then a specific stop is issued.

a. Component has no SyncID defined
Component does not stop.

b. Component has a SyncID defined equal to that of the action
Component stops.

c. Component has a SyncID defined different from that of the action
Component does not stop.


Case 5: RESET without SyncID

If a RESET action is executed, and the Value for the action is empty, then a general reset is issued.

a. Component has no SyncID defined
Component resets.

b. Component has a SyncID defined
Component resets (!). All components reset on a general reset.


Case 6: RESET with SyncID

If a RESET action is executed, and the Value for the action has been set, then a specific reset is issued.

a. Component has no SyncID defined
Component does not reset.

b. Component has a SyncID defined equal to that of the action
Component resets.

c. Component has a SyncID defined different from that of the action
Component does not stop.

Please note that the RESET action may also be directed to one specific component, by specifying an address. In that case the SyncID rules apply as well.