Resolving LOGO! 230RCE Real-Time Clock Drift with NTP Sync

Problem Statement: LOGO! 230RCE Clock Drift on Standalone Bell Schedules

The Siemens LOGO! 230RCE is widely deployed as a low-cost logic relay for repetitive time-of-day switching tasks: school bells, factory shift horns, irrigation valves, parking-lot lighting, and HVAC night-purge routines. In standalone installations (no PLC backplane, no operator panel, no internet) the module must keep accurate wall-clock time using only its internal real-time clock (RTC). Field reports consistently show that after 90 days of continuous operation the unsynchronized 230RCE drifts 1 min 30 s to 3 min off the reference time, which is enough to fire a school bell visibly early or late and trigger complaints from staff.

This drift is not a defect; it is the published specification. The Siemens LOGO! manual states the integrated RTC accuracy as typ. ±2 s/day at 25 °C. Over 90 days the worst-case accumulated error therefore reaches ±180 s = ±3 min, with typical behaviour in the middle of the band. The drift is dominated by the tolerance and temperature coefficient of the 32.768 kHz quartz crystal that clocks the RTC counter, and it accelerates at temperature extremes.

LOGO! 230RCE Identification and RTC Architecture

The "230RCE" suffix decodes to the feature set of the LOGO! 8 base module:

The RTC block sits inside the CPU of the LOGO! 8 base module. It is fed by a watch crystal at 32.768 kHz and counted down to 1 Hz for seconds. The counters, day-of-week, date, and DST flags live in a battery-backed SRAM region so that power-down does not reset the schedule. The integrated Ethernet port (introduced with the LOGO! 8 generation, part numbers 6ED1052-2HB08-0BA0 family and successors) is the path used for NTP synchronization in firmware versions that expose the NTP client function block.

Identify the module on the project documentation page or in LogoSoft Comfort under Tools → Transfer → Detect Target. The order number, hardware version (FS), and firmware version are required to confirm whether NTP is available — older LOGO! 6/7 generations (without Ethernet) cannot synchronize over NTP at all.

RTC Accuracy Specification: ±2 s/day (Typical)

Direct quote from the LOGO! 8 system manual (chapter "Real-time clock"):

Accuracy of the real-time clock: typ. ±2 s/day

The spec is qualified as "typical" rather than maximum because crystal aging and thermal coefficient shift the actual error band. Key dependencies:

The "typ." prefix means most modules stay inside ±2 s/day at room temperature, but the manufacturer does not guarantee this for every individual unit. A fielded module may sit at +1.5 s/day or −1.8 s/day, and at 5 °C ambient it can push beyond ±3 s/day.

Calculating Expected Drift Over Operating Periods

Use the formula:

where ε is the daily error (seconds/day, signed) and N_days is the operating interval. Worked examples for a school-bell installation:

The reported "more than 1 minute 30 seconds after 3 months" therefore falls squarely inside the published tolerance window. The module is not defective; it is operating within specification.

Root Cause: Uncompensated 32.768 kHz Crystal Oscillator

The drift is dominated by three physical effects, all of which act on the quartz tuning fork that drives the seconds counter:

1. Initial frequency tolerance. Even a "tight" 32.768 kHz crystal is cut to ±20 ppm at 25 °C. ±20 ppm at one day equals 86 400 s × 20 × 10⁻⁶ ≈ ±1.7 s/day — already near the spec. Cheaper crystals run ±50 ppm (±4.3 s/day).
2. Temperature coefficient. A typical tuning-fork crystal has a parabolic TC centred near 25 °C with a coefficient of about −0.04 ppm/°C². At 5 °C ambient the offset is roughly −3 ppm, adding another ~15 min/year. The clock speeds up in cold weather and slows down in heat.
3. Aging. Crystal mass loading changes over time as electrode metal migrates. Aging adds another ±1 ppm/year after the first year of operation. Combined with TC, an uncompensated LOGO! RTC drifts ~5–10 min/year in a benign indoor environment and 15+ min/year in a cold plant room.

None of these effects are calibrated at the factory because adding a TCXO (temperature-compensated crystal oscillator) would raise the cost of every LOGO! base module. The intended mitigation path is network synchronization — NTP — which Siemens exposes on Ethernet-equipped modules.

Solution 1: Enable NTP Time Synchronization

The cleanest fix is to let the LOGO! 230RCE poll a Network Time Protocol server on the LAN. With NTP enabled the module re-aligns its internal RTC each poll interval and the practical long-term drift collapses to the network jitter of the LAN — typically <100 ms against a GPS-disciplined NTP source. Once a network drop is detected, the LOGO! falls back to its internal RTC and resumes drift at the spec rate, so the Ethernet cable must remain plugged for the benefit to persist.

Prerequisites:

• LOGO! 8 base module with Ethernet (230RCE, 230RCEo, or BM with Ethernet). Legacy LOGO! 6/7 230RC modules cannot run NTP — they have no Ethernet port.
• Firmware version that exposes NTP parameters. Confirm the module's firmware under Tools → Diagnostics → Module Information in LogoSoft Comfort.
• Reachable NTP server on the same subnet. A LAN-attached router, a Raspberry Pi running chrony, or an industrial NTP appliance all work.
• LogoSoft Comfort V8.x or later (V8.3 and newer recommended for the most recent LOGO! 8 FS4+ firmware).

LogoSoft Comfort Configuration Procedure for NTP

1. Open the project in LogoSoft Comfort and connect to the LOGO! via Ethernet (target IP set under Tools → Transfer → Ethernet Connection).
2. In the project tree, right-click Properties → Time / Date (or Online → Time Synchronization depending on firmware generation).
3. Enable NTP client and enter the NTP server address. Two server entries are typically allowed for redundancy.
4. Set the synchronization interval. A value of 3600 s (1 h) is a good compromise between LAN traffic and accumulated drift between polls.
5. Set the time zone offset (UTC+1 for CET, UTC+2 during CEST) and enable the automatic DST flag so the LOGO! follows the EU summer-time rule.
6. Click PC → LOGO! to download the new parameters. The transfer requires the LOGO! to be in STOP for parameter changes, then back to RUN.
7. Verify under Online → Diagnostic → Time that the displayed clock is now within ±1 s of your PC time.

NTP Parameter Reference Table

Solution 2: External NTP-to-Modbus Gateway

For installations where the LOGO! firmware does not expose NTP, or where the Ethernet port is needed for programming only, add an industrial NTP-disciplined RTC that writes time into the LOGO! over Modbus TCP. Two common product families serve this role:

• Moxa NTP/Modbus gateways (e.g. MGate MB3170) accept NTP from a LAN source and publish the synchronized time as Modbus holding registers. The LOGO! program reads the registers via Network Analog Input function blocks and re-aligns its internal time.
• Self-hosted Linux box (Raspberry Pi running chrony + modbus-tk) writing time-of-day into a Modbus server. Lower cost, requires IT engagement.

Whatever the gateway, the LOGO! program must convert the binary hour/minute/second registers into the four integer inputs the internal RTC function block expects, then issue a single "set time" pulse once per NTP poll. After that the LOGO! RTC is again free-running until the next sync.

Battery Backup and Power-Cycle Behavior

LOGO! 8 base modules accept a coin-cell backup battery (order number varies by hardware revision; commonly CR1025 or CR2032 depending on FS variant — verify against the battery compartment label before ordering) that powers the RTC during a power loss. Behavior summary:

• Battery present, mains lost: RTC continues. Weekly/yearly schedules fire as programmed if the relay outputs are wired to a buffered supply. Typical hold-up: 1–2 years depending on cell capacity and ambient temperature.
• Battery absent or flat, mains lost: RTC stops at the time of power-down and resumes from that value when power returns. The schedule is therefore valid until the first power cycle, after which all times become wrong until manual re-entry.
• Battery low warning: LogoSoft Comfort raises a diagnostic bit (BAT) under Online → Diagnostic when the cell drops below the warning threshold. Replace within 30 days.

Manual Time Calibration and Drift Compensation

If neither NTP nor an external gateway is acceptable, two manual strategies exist:

1. Periodic site visit. Upload corrected time at semester start and mid-semester. Worst-case drift is then bounded to ~45 days × 2 s/day = ±90 s = ±1.5 min, which most users tolerate.
2. Drift offset block. Build a small ladder program that measures the actual daily drift over a one-week test, then issues a Time Offset correction via the weekly timer offset input. This requires firmware that exposes the offset input and is rarely worth the effort when NTP is free.

To characterize the actual drift on a specific unit before deciding:

1. Set time to a known reference (radio clock, smartphone).
2. Read time at 24 h, 72 h, and 168 h via LogoSoft Comfort Online → Time.
3. Compute ε = (t_read − t_ref) / days_elapsed.
4. If |ε| > 3 s/day consistently, the unit is at the edge of the spec and should be replaced; otherwise NTP sync will compensate perfectly.

Verification and Field Test Procedure

After configuring NTP, validate end-to-end:

1. Force the LOGO! into STOP, then RUN, and watch the diagnostic page for the Time synchronized bit.
2. Disconnect the NTP server (unplug the LAN cable or stop the chronyd service). Confirm that the NTP sync bit clears within one poll interval.
3. Reconnect and verify that the clock resyncs within one poll interval and that the diagnostic page now reads NTP OK.
4. Disconnect mains for 5 minutes with battery fitted. Confirm RTC time is preserved to the second.
5. Disconnect mains for 5 minutes without battery. Confirm the clock stops, then resumes from the stop time (this confirms the battery state, useful as a one-off test).
6. Run the bell schedule through one full day and confirm each ring fires within ±1 s of the programmed time.

Comparison Table: Timekeeping Accuracy Options

Troubleshooting Matrix

Spare Parts and Documentation References

Identify the module before ordering spares — the LOGO! family has overlapping suffixes that look identical:

• LOGO! 230RCE (no display, relay, Ethernet, 115/230 V AC/DC): order number 6ED1052-2HB08-0BA0 (FS4) or later revision. Confirm hardware version (FS1, FS2, FS3, FS4, FS5, FS6) before ordering, as NTP support and battery part numbers vary.
• LOGO! 230RCEo: same feature set with o suffix indicating "without battery slot" — order number 6ED1052-2HB08-0BA1 family. RTC does not survive power-down; NTP becomes mandatory for any schedule that must remain valid across outages.
• Coin-cell battery: confirm with the battery-compartment label on the module; common part numbers are CR1025 (3 V, 30 mAh) and CR2032 (3 V, 220 mAh). Do not substitute a different chemistry.

For official specifications, refer to the Siemens LOGO! 8 system manual (article ID 109751413) and the LOGO! 230RCE product information page (article ID 109766631) on the Siemens Industry Online Support portal. The RTC accuracy line item appears in the "Technical data" chapter of the system manual and is reproduced verbatim above.

Field Commissioning Checklist for School Bell Applications

1. Confirm LOGO! 230RCE firmware supports NTP (FS4 or newer recommended).
2. Verify LAN connectivity to the NTP server (ping, then ntpdate -q from a laptop).
3. Configure NTP server IPs, poll interval (3600 s), time zone, and DST rule in LogoSoft Comfort.
4. Download to LOGO!, restart, verify sync bit.
5. Fit a fresh coin-cell battery and verify the BAT diagnostic bit is clear.
6. Load the bell schedule, run for 24 h, and log actual ring times vs scheduled times.
7. Repeat the log at 7 days and 30 days to confirm long-term drift <1 s.
8. Document the NTP source IP, the poll interval, and the maintenance window in the school's asset register so the next technician inherits the configuration.