Introduction

The operating modes listed in the following table represent cases with a simple system time stamping solution behavior.

Behavior on Specific Operating Modes

The following table describes the time stamping solution behavior on specific operating modes:

Operating Mode

Operating Mode Phase

Behavior

PLC application change:

  • Change the time stamping mode setting (Applicative -> System).

  • Import a XEF, ZEF, XHW, or ZHW file.

  • Insert a new module (BM• CRA 312 10 or BMX ERT 1604 T).

  • Copy / Paste a new module (BM• CRA 312 10 or BMX ERT 1604 T).

  • Replace a BMX CRA 312 00 by a BMX CRA 312 10module.

  

• Same behavior as in the initial start after the application download operating mode.

• The time stamping module event buffer is automatically reset.

Replace a BMX ERT 1604 T

  

• Same behavior as in the initial start after the application download operating mode.

• The time stamping module event buffer is automatically reset.

I/O channel error on a discrete time stamped I/O.

  

• Diagnose the PLC parameters (for example, %MWr.m.c.2 for a BMX ERT 1604 T module).

• Time stamped events have the following TimeQuality attribute: TimeAccuracy = IOChannelError.

Disconnection/connection of the SCADA server.

No access to the time stamping module from the SCADA server.

• Signalization of the disconnection through the specific item: <direct_address>!#PLCQualStatus = QUAL_DEVICE_FAILURE

• No more events are received by the SCADA servers.

Access re-established between the time stamping module and the SCADA server.

• Signalization of the connection through the specific item: <direct_address>!#PLCQualStatus = QUAL_GOOD

NOTE: If the disconnection generates a module internal buffer full, refer to this specific operating mode description.

No access to the time stamping module from the PLC.

  

Behavior depends on the time stamping component:

  • BMX ERT 1604 T: Normal time stamping.

  • BM• CRA 312 10: Discrete I/O type:

    • Input: Inputs are still time stamped.

    • Output: Outputs are not time stamped during PLC disconnection.

PLC start while the system time stamping is running.

PLC cold start.

Behavior depends on the time stamping component:

  • BME P58 ••••:PLC start type:

    • Cold start: Reset the CPU event buffer.

    • Warm start: Keep the CPU event buffer.

  • BMX ERT 1604 T: Module located in a:

    • Local drop: Same behavior as in the case of the time stamping module power Down/Up.

    • Modicon X80 drop: No impact on system time stamping.

  • BM• CRA 312 10: No impact on system time stamping.

  • SCADA: No impact on system time stamping.

PLC warm start.

PLC run to stop / stop to run transition while the system time stamping is running.

PLC run to stop transition (behavior in stop state).

Behavior depends on the time stamping component:

  • BME P58 ••••: Stop time stamping.

  • BMX ERT 1604 T: Normal time stamping.

  • BM• CRA 312 10: Discrete I/O type:

    • Input: Inputs are still time stamped.

    • Output: Detection and time stamping of the output image (in case of Control Expert animation table evolutions).

    NOTE: The BM• CRA 312 10 module does not time stamp outputs fallback state (not available in the output image) on PLC run to stop transition.

PLC stop to run transition.

Behavior depends on the time stamping component:

  • BME P58 ••••: Begin time stamping.

  • BMX ERT 1604 T: Normal time stamping.

  • BM• CRA 312 10: Normal time stamping.

Initialization of the PLC variables (%SO) while the system time stamping is running.

  

Behavior depends on the time stamping component:

  • BME P58 ••••: %S0=1: reset the CPU event buffer.

  • BMX ERT 1604 T: No impact on system time stamping.

  • BM• CRA 312 10: No impact on system time stamping.