No marker for new data is provided for this input type. The digital inputs in the first two input register words are updated directly by the ERT in every PLC cycle. The EFB makes the processed values available as Bool if the BoolArr32 output field has been configured accordingly.

Cyclic updating of the counted values lasts significantly longer than for other data types. Counted values are saved as a data set in CNT_DATA after a complete series (configured as: 8, 16, or 32) of time consistent counted values in multiplex form has been transferred by the ERT. The marker for new data ND_COUNT is set for one cycle.

Readiness to receive new events must be actively confirmed by the user, therefore the administration of markers becomes somewhat more complex (a handshake mechanism is required) Event data remain in the data structure ERT_10_TTag and the marker for new data ND_TT stays set until the ACK input is set and a new event thus requested. The EFB responds to this by resetting ND_TT for at least one cycle. After the new event has been sent to the ERT_10_TTag structure (marker structure), ND_TT is reset by the EFB. To prevent the new event data from being overwritten attention must be paid to fundamentally resetting the ACK input after the EFB has reset the ND_TT marker. This state can then remain stable to allow the user program enough time for event processing. Each subsequent event tracked with the ERT is temporarily stored within the event FIFO buffer.

New events are sent directly from the internal buffer of the EFB in intervals of at least 2 cycles for as long as the ACK input is set (for the special continuous operating mode); the effect is, however, that the ND_TT only stays set for one cycle. In this special mode the user program’s task is still to terminate event processing before ND_TT signals the transfer of other new events to the ERT_10_TTag structure as handshake protection by ACK is not available in this case.

The value for the milliseconds is a maximum of 61100 ms with switch seconds (61000 plus a tolerance of 100 milliseconds)

For time markers containing an invalid time (TI = 1), the time in milliseconds is set to FFFF HEX. Minutes, hours and DOW/DOM values are invalid (i.e. undefined).

If the "rough time declaration" has been activated during the ERT configuration, the transfer of the complete time (with month/year) is executed in the following conditions: when the month changes, after the module restarts, during every start or stop of the PLC user program, when the event FIFO buffer is deleted, when the clock is started or set. If this rough time declaration is sent without the data input values, "triggering" basically takes place through a correct time stamped event. If this does not happen the values remain "stuck" in the ERT until an event occurs. Within the time mark of a "rough time declaration", the CT bit is always set so that byte 2 contains the information about the month, byte 3 the information about the year and bytes 4 to 8 display the same time mark values of the triggered event whose event message appears immediately after the rough time declaration.

The marker for new status data ND_STAT is set for one cycle. The status inputs can be overwritten after 2 inquiry cycles.

The status word contains EFB and ERT error bits

When configuring the parameter screen some of these errors can be assigned to grouped error messages with the "F" light as well as the module's error byte within the status table. All other errors are then defined as warnings.

D11 ... D9 reserved

The following ERT/EFB error messages are displayed in the Tools → Diagnostic Display window with an error number and explanation.