Resolving SIMOCODE Pro V Error Buffer Date and Time Issues

Overview

When a SIMOCODE pro V basic unit (3UF7 series) is configured and commissioned with SIMOCODE ES V2007 SP4 HF2 or later engineering software, the error/fault buffer can appear to show "wrong" date and time values. The behavior is not a configuration defect. It is a designed limitation of the PROFIBUS DP variant and most legacy SIMOCODE pro communication modules. The device does not maintain a real-time clock; the timestamp recorded in the diagnostic buffer is an elapsed-time counter referenced to the operating hours of the basic unit, not a calendar date.

This article clarifies the timestamp format, explains the difference between SIMOCODE pro V PROFIBUS and SIMOCODE pro V PROFINET with respect to time-of-day stamping, and provides procedures for activating time synchronization where the hardware supports it. The content applies to motor management systems used with SIMATIC S7-300, S7-400, S7-1200, and S7-1500 controllers as well as stand-alone (non-networked) configurations.

SIMOCODE pro V Communication Variants and Timestamp Behavior

SIMOCODE pro V is available with multiple communication modules. The diagnostic and error buffer implementation differs by variant:

The operating hours counter increments only while control power (terminal A1/A2 = 24 V DC, or 110/230 V AC depending on the basic unit version) is present on the device. Loss of control power stops the counter; it is retained in non-volatile memory on the basic unit and resumes from the last saved value when power returns.

Understanding the Operating Hours-Based Error Buffer

The error buffer is stored in non-volatile memory on the SIMOCODE pro V basic unit. Each event is time-stamped with the cumulative operating hours of the device at the moment the event was logged. Because the counter is monotonic and only advances while control power is applied, the timestamp represents the time elapsed since the device was first commissioned minus any time it spent de-energized.

The display format is fixed and cannot be changed through SIMOCODE ES configuration. It uses the pattern:

DDDD.HH:MM:SS

where:

• DDDD = number of full days of operation (0 to 65535)
• HH = hours within the current day (0 to 23)
• MM = minutes (0 to 59)
• SS = seconds (0 to 59)

This is a derived format, not a calendar date. There is no year, no month, no day-of-month, and no provision to set a base date from which to compute a real timestamp.

Worked Example From the Source

The original Siemens support response provides a direct example. If the operating hours counter reads 80 hours at the moment an event is recorded, the error buffer displays:

3.7:47:07

Decoding this string:

• 3 full days (3 × 24 = 72 hours)
• 7 hours into the fourth day (72 + 7 = 79 hours)
• 47 minutes
• 7 seconds

The total elapsed time is 79 hours, 47 minutes, 7 seconds after the moment of commissioning. The exact sub-hour remainder (47:07) reflects the internal counter resolution of the basic unit; the counter is not perfectly whole-hour, so the device is able to display minute and second resolution despite the field name "operating hours." This is the source of the most common confusion: a user expects a calendar date and reads 3.7:47:07 as "3 July, 47:07" or similar, when in fact it is "3 days, 7 hours, 47 minutes, 7 seconds."

Converting the Displayed Timestamp to a Real Elapsed Time

For PROFIBUS and SIMOCODE DP installations where real date/time is not available, the timestamp can be converted to a real wall-clock time if the technician recorded the date and time at which the device was first commissioned and the device has remained continuously energized.

Use the following formulas:

Total elapsed seconds (T_s):

T_s = (DDDD × 86400) + (HH × 3600) + (MM × 60) + SS

Total elapsed hours (T_h):

T_h = T_s / 3600

Reconstructed wall-clock time of event (T_event):

T_event = T_commission + T_s

where T_commission is the real date/time at which the SIMOCODE pro V basic unit first received control power. If the device lost control power at any point, you must also subtract the total de-energized time, which is not recorded by the device. The de-energized time must be logged manually by the plant operator.

Practical Limitation

This conversion is error-prone over long service intervals and is the primary reason Siemens introduced real-time-clock support in the PROFINET variant. For any new motor management application that requires auditable fault timestamps — for example, in regulated process plants or for warranty dispute resolution — select the SIMOCODE pro V PROFINET basic unit and configure time synchronization as described below.

Enabling Time Synchronization on SIMOCODE pro V PROFINET

Only the PROFINET IO variants of SIMOCODE pro V support real-time time-of-day (TOD) synchronization. There are two possible time sources:

1. PROFINET IO time-of-day synchronization (PDEV TOD sync), where the IO Controller pushes the time to the IO Device.
2. NTP/SNTP client, where the device polls an NTP server on the plant network.

To enable PROFINET TOD sync on a SIMOCODE pro V PROFINET basic unit (3UF7010-1AU00-0 or 3UF7011-1AU00-0) using SIMOCODE ES V2007 SP4 or later:

1. Open the SIMOCODE ES project and go online to the device.
2. In the device tree, expand the PROFINET interface node.
3. Open Properties > PROFINET IO > Time-of-Day Synchronization.
4. Select "Synchronize with IO Controller time" or specify the NTP server address.
5. Set the synchronization interval. Recommended value: 60 s for process-critical applications, 600 s for non-critical.
6. Download the configuration to the device and perform a station restart (PROFINET AR abort/reconnect) to apply.
7. Verify in the diagnostic buffer that the first new event has a real date/time stamp rather than the DDDD.HH:MM:SS pattern.

The NTP/SNTP client path is configured through the device's Web server or via SIMOCODE ES, depending on the firmware version. NTP servers should be selected from the same plant security zone as the SIMOCODE device, with authentication where supported by the firmware.

Configuration Through SIMOCODE ES

SIMOCODE ES (TIA Portal integration or the standalone SIMOCODE ES V2007 SP4 HF2 tool) is the engineering environment for SIMOCODE pro V. The timestamp format itself is not a configurable property; it is a fixed output of the basic unit firmware. The configurable items relevant to fault timestamping are:

Comparison of Communication Variants

Troubleshooting Matrix

Limitations and Workarounds for PROFIBUS / DP Installations

For sites that are locked into the SIMOCODE pro V PROFIBUS basic unit (for example, brownfield PROFIBUS DP networks with no PROFINET migration path), the following workarounds are available to provide approximate real-time stamping:

1. PLC-side time stamping. Subscribe to the SIMOCODE pro V diagnostics via PROFIBUS DP and record the event in the SIMATIC CPU's diagnostic buffer, which is time-stamped with the controller's real-time clock. Configure a S7 diagnostic alarm OB (e.g., OB82 for diagnostics) to log the time of day from the S7 CPU system clock.
2. SCADA-side time stamping. Read the SIMOCODE error buffer cyclically into WinCC, FactoryTalk View, or a comparable SCADA, and append the SCADA server's time-of-day to each event. This is the most common production workaround.
3. Manual commissioning log. Record the date and time the device was first energized and the total accumulated de-energized time. Apply the conversion formulas above to any error buffer entry.

Each of these workarounds is approximate: there is always a small drift between the event occurring inside the SIMOCODE basic unit and the event being reported over PROFIBUS to the controller or SCADA. The drift is in the millisecond range for PROFIBUS DP-V1 and is acceptable for production fault analysis.

Verification

To verify that the chosen approach is working correctly:

1. Force a test trip on the SIMOCODE pro V by opening a protected motor contactor circuit, or use SIMOCODE ES to issue a test fault from the diagnostics menu.
2. Open the error buffer in SIMOCODE ES, the device's Web server (PROFINET only), or the connected SCADA / HMI.
3. Confirm that the new event carries either:
   • A DDDD.HH:MM:SS string that has advanced by at least one second relative to the previous event (PROFIBUS), or
   • A real date/time stamp in the format DD.MM.YYYY HH:MM:SS (PROFINET with active sync).
4. For PROFINET: also verify the TOD validity bit in the cyclic status word reflects a healthy time source.
5. Trigger a controller-to-device time resync (e.g., by changing the S7 CPU time by 1 minute and waiting for the next sync interval) and confirm the SIMOCODE error buffer reflects the new time on the next event.

Engineering Recommendations

• New installations: Select SIMOCODE pro V PROFINET (3UF7011-1AU00-0 or equivalent for the application's current/voltage range) and configure PROFINET TOD sync at commissioning. The incremental hardware cost is recovered quickly by eliminating SCADA-side time-stamping logic.
• Existing PROFIBUS installations: Do not attempt to "reset" the operating hours counter to force the timestamp to zero — this destroys the cumulative run history required for predictive maintenance calculations. If the counter must be reset, do it once and document the wall-clock time of the reset.
• HMI design: Always label the error buffer timestamp field with its meaning ("Operating Hours" vs. "Date/Time") to prevent operator confusion.
• Auditability: For regulated applications, ensure the SCADA-side time stamp is recorded independently of the SIMOCODE basic unit counter, and that the SCADA server is itself synchronized to a traceable time source (e.g., plant NTP or GPS).
• Firmware: Use the latest SIMOCODE pro V PROFINET firmware available at commissioning to benefit from NTP/SNTP client improvements and security patches. Check the Siemens Industry Online Support for the current firmware release notes.

References to Official Documentation

For further detail, refer to the following official Siemens resources:

• Siemens Industry Online Support — SIMOCODE pro product pages
• Siemens SIMOCODE pro motor management product overview
• SIMATIC S7-1500 system manual, section on time-of-day synchronization (available via the TIA Portal Help system or Siemens Industry Online Support entry ID 109742136)

FAQ