Scope events

Event timestamp

For scope container events, the timestamp indicates the time when scope data was uploaded from a device to the SDC and published in an event. Since scope containers do not load scope data into the SDC until a certain device status is present, the timestamp depends on the interval at which the status of the device is read out. The scope data could therefore have been available in the device earlier, for example.

The timestamp is specified as a unix time in [ms]. The unix time contains the number of milliseconds since Jan 1, 1970, 0:00. The unix time can be converted into the common time format e.g. using tools available online.

Scope sample timestamp

For scope container events, the "EcSystemTimestamp" indicates the time at which a device acquired the scope value. The "EcSystemTimestamp" is generated in the devices and transferred to the SDC with the data value. This timestamp can only be generated by devices that are synchronized by a higher-level controller on the EtherCAT^® by means of distributed clocks.

If the device is synchronized using distributed clocks, the timestamp is specified as EtherCAT^® system time. The EtherCAT^® system time contains the number of nanoseconds since Jan 1, 2000, 0:00 a.m. If the device is not synchronized using distributed clocks, the number of nanoseconds since the device was switched on is specified. The EtherCAT^® system time can be converted into C# or other languages, for example.

Scope trigger timestamp

For scope container events, the "TriggerTimestamp" specifies the time at which the scope recorder was triggered in a device and started recording the scope samples. The timestamp can be set either by a triggered device trigger or by a manual SDC trigger. This timestamp can only be generated by devices that are synchronized by a higher-level controller on the EtherCAT^® by means of distributed clocks.

If the device is synchronized using distributed clocks, the timestamp is specified as EtherCAT^® system time. The EtherCAT^® system time contains the number of nanoseconds since Jan 1, 2000, 0:00 a.m. If the device is not synchronized using distributed clocks, the number of nanoseconds since the device was switched on is specified. The EtherCAT^® system time can be converted into C# or other languages, for example.