Every timing entity in MX Foundation (a time parameter, a time tag, a time field in a structure, a time attribute value, ...) is affected by the timebase (Device, Computer or IRIG-B) or the timebase resolution (microseconds or nanoseconds).

Timing entity affected by the timebase

The message time tag of a received message is always formatted according to the current timebase.

The message time tag of a transmitted message, for absolute timing transmission, must be set according to the current timebase. The mxfDeviceTimerGet() function returns the time formatted according to the current timebase.

The absolute timing parameter (for example, start time and stop time) of many functions must also be set according to the current timebase.

Timing entity affected by the timebase resolution

Every timing entity, except received message time tag and absolute timing, are affected by the timebase resolution. This includes, but not limited to, message time tags for transmitted messages using relative timing, relative timing parameter (for example start time and stop time), returned RT response time, aging timeout attribute, sampling killtime, ...

These values will either be expressed in microseconds or nanoseconds according to the current timebase.