Global triggers from non-synchronized slaves are marked in the start and stop trigger pool of the data recording configuration of the other participants with the addition "Non-synchronized slave..." in the group header.

Unlike synchronized slaves, trigger configurations on non-synchronized participants are not automatically updated when acquisition is started. You must manually click the <Update external triggers> button in the data store configuration so that ibaPDA searches for non-synchronized slaves and updates the trigger definitions.

When a trigger is activated on a system where support for non-synchronized slaves is enabled, the trigger event is sent via the multicast address so that all other stations can receive the event. If the transmission type is set to UDP unicast, the trigger event is sent to the configured systems accordingly.

The event message contains the trigger name, the ID (module and signal number), and the absolute UTC time at which the trigger event occurred.

Non-synchronized slaves that receive such an event compare the received absolute UTC time with their own UTC system time in order to synchronize the trigger event with their own acquired data. To do this, it is very important that the system time of all non-synchronized slaves is accurate. The more accurate the system time, the more precisely the trigger event can be synchronized with the local data.