SICLOCK TC100 vs TC400 Configuring NTP and GPS Time Sync

David Krause13 min read
Industrial NetworkingSiemensTechnical Reference
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Overview: Time Synchronization in S7-400 Industrial Ethernet Networks

Distributed SIMATIC S7-400 systems must share a single, accurate time base for sequence-of-events recording, batch report timestamps, shift logging, audit trails, OPC UA server timestamps, and energy-data correlation. Each S7-400 CPU (CPU 412, 414, 416, 417) maintains an internal 64-bit real-time clock with a 1 ms resolution, but the internal RTC drifts on the order of seconds per day and cannot be guaranteed coherent across 10–20 PLCs without an external reference. A GPS- or DCF77-disciplined Siemens SICLOCK time server delivers a single time-of-day reference, distributing it to every S7-400 over the plant Industrial Ethernet using the NTP/SNTP or SIMATIC TIME protocol.

This reference covers selection between the SICLOCK TC100 and SICLOCK TC400, antenna and receiver integration, CP 443-1 NTP client configuration in STEP 7 V5.x, SIMATIC TIME configuration, redundant operation, and field-proven diagnostic checks for a typical 15-PLC, 2-server, 10-client architecture.

Scope: The CP 443-1 family is the NTP/SNTP client path from an S7-400 station. The CPU 4xx itself has no NTP client capability. PTP (IEEE 1588) is not supported on classic S7-400; use the S7-1500 with a CP 1543-1 if PTP is required.

Prerequisites

Before commissioning the time-of-day distribution, verify the following items are present and document their firmware versions:

  • SICLOCK TC100 (6MF1110-0AA00) or SICLOCK TC400 (6MF1110-1AA00) time server with the latest firmware (V3.x as of 2024). Confirm on the Siemens support portal (support.industry.siemens.com) using the article search keyword SICLOCK.
  • GPS receiver module for outdoor antenna, or DCF77 receiver for the Central European transmitter, depending on accuracy and infrastructure.
  • CP 443-1 (6GK7443-1EX30-0XE0) or CP 443-1 Advanced (6GK7443-1GX30-0XE0) in every S7-400 station requiring synchronised time. The Advanced variant supports NTP/SNTP with a 1 ms-class sync interval.
  • STEP 7 V5.5 SP4+ or STEP 7 Professional (TIA Portal) V15.1+ for HW Config and NetPro, plus NCM S7 Industrial Ethernet diagnostics.
  • SIMATIC NET Industrial Ethernet with managed switches supporting IGMP snooping if SIMATIC TIME multicast is used. NTP/SNTP unicast only requires a standard Layer-2 switch.
  • Plant firewall must permit UDP port 123 (NTP) between SICLOCK and each S7-400 station.

SICLOCK Product Family: TC100 vs TC400

Both devices are rack- or DIN-rail mounted time servers in the SIMATIC NET family. They share the same web configuration interface and the same NTP/SNTP server firmware, but differ in interface density, holdover performance, and redundancy options.

Feature SICLOCK TC100 SICLOCK TC400
Order number 6MF1110-0AA00 6MF1110-1AA00
GPS receiver input Yes (external antenna) Yes (dual, hot-standby)
DCF77 input Yes Yes
NTP/SNTP server Yes (up to ~500 clients) Yes (up to ~5,000 clients)
SIMATIC TIME master Yes (multicast) Yes (multicast + redundant)
Ethernet interfaces 2 × 10/100Base-TX 4 × 10/100/1000Base-T
Holdover (no GPS) ±1 s/day after 24 h GPS lock ±100 ms/day (OCXO option)
Redundant pair operation No Yes (Bumpless)
PTP grand master (IEEE 1588 v2) No Optional firmware
Web/HTTPS management Yes Yes
Approx. street price (EU, 2024) €2,800 €7,500

For a 15-station S7-400 cluster with two OPC servers and ten HMI clients (≈ 27 NTP clients), the TC100 has ample headroom. The TC400 is justified when the plant also feeds Ethernet-attached analysers, video, or third-party controllers from the same time reference, or when hot-standby redundancy of the time server itself is required.

Network Architecture for Distributed S7-400 Time Sync

SICLOCK TC100NTP/SNTP server GPS ant Plant IE Backbonemanaged switch stackVLAN 100 = NTPUDP/123 unicast S7-400 #1 S7-400 #2 S7-400 #3 S7-400 #4 S7-400 #5 OPC srv HMI ×10

All S7-400 stations and the OPC server sit on a single IE subnet (VLAN 100). The SICLOCK acts as the stratum-1 NTP source. The 15 PLCs each poll the TC100 every 10–60 s, the two OPC servers poll every 1 s for OPC UA server-timestamp accuracy, and the HMI clients poll every 60 s.

Selecting Between TC100 and TC400

Use the TC100 when:

  • The total NTP client count is below ~500.
  • Single time source is acceptable; brief GPS outages (≤ 1 hour) are tolerated with holdover to ±1 s.
  • Cost is constrained and the application uses SIMATIC TIME on the IE subnet, not a cross-plant WAN.

Use the TC400 when:

  • More than 500 NTP clients, or several thousand SIMATIC TIME receivers across multiple subnets.
  • Hot-standby time-server redundancy is a contractual requirement (e.g. IEC 61850 substations, pharma, TÜV-audited plants).
  • Future migration to S7-1500 + CP 1543-1 PTP is planned; the TC400 can be upgraded with a PTP grand-master firmware option.
  • Holdover must stay within ±100 ms for more than 24 h (OCXO-disciplined).

S7-400 NTP Client Configuration on the CP 443-1

The S7-400 CPU itself does not speak NTP. Time-of-day synchronisation is delegated to the CP 443-1 in slot 4 (or any free slot). The CP then writes the received UTC into the CPU's date/time clock via the backplane at the configured interval.

Step-by-step (STEP 7 V5.x)

  1. Open the S7 project in SIMATIC Manager and select the target station.
  2. Open HW Config, double-click the CP 443-1, and switch to the Time-of-Day Synchronisation tab.
  3. Tick Accept time-of-day on the S7-CPU from the LAN and select NTP mode.
  4. Enter the SICLOCK IPv4 address, e.g. 192.168.100.10, and set the synchronisation interval to 10 s for the OPC server, 60 s for PLCs and HMIs.
  5. Set the time zone to UTC on the CP; the CPU can be configured separately to local time using SFC 0 / SFC 1 in OB 1.
  6. Compile and download. The CP 443-1 does not require a restart; NTP polling starts on the next KeepAlive cycle.

Sample SFC 1 (READ_CLK) call in OB 1 to read the synchronised clock into a DB for diagnostics:

// OB1 - read CPU time-of-day after CP-driven NTP sync
CALL  "READ_CLK"            // SFC 1
     RET_VAL := MW 100      // returns 0 on success
     CDT     := DB100.DBD0  // 8-byte DATE_AND_TIME buffer

// Push 8-byte buffer to display in HMI
CALL  "DT_TO_TOD"           // IEC FC
     IN  := DB100.DBD0
     OUT := DB100.DBD0      // TOD only (4 bytes)

To verify the CP 443-1 is actually receiving NTP frames, open NCM S7 Industrial Ethernet Diagnostics → station → Time-of-Day tab. The last accepted time, stratum, and offset in ms are displayed.

SICLOCK Hardware Installation

TC100 power and grounding

  • Supply: 24 V DC ±20 %, max 0.5 A, connect to a clean UPS-backed 24 V bus.
  • Functional earth (FE) terminal must be bonded to the cabinet PE bar with < 1 Ω impedance to keep surge protection of the antenna input effective.
  • Mount on 35 mm DIN rail with at least 30 mm clearance above and below for convection.

GPS antenna

  • Antenna type: active GPS L1, 3.3 V or 5 V supply from the receiver, gain ≥ 26 dB.
  • Coaxial cable: RG-58 up to 15 m, RG-213 or Heliax LDF4-50A for longer runs. Max 60 m total cable loss < 12 dB.
  • Sky view: 360° hemisphere with a 15° elevation mask. Avoid mounting next to large steel structures, VFDs, or soft-starter cabinets.
  • Lightning protection: install a coaxial surge arrester (e.g. DEHNgate DGA AG BNC) at the building entry point and bond its earth to the plant ground bar.

DCF77 alternative

If the plant is in Central Europe and GPS is not permitted, the DCF77 receiver (e.g. SICLOCK DCF77 receiver) can be wired to the same antenna input. Accuracy: ±20 ms typical, no satellite dependency, but reduced to short-range coverage of the Frankfurt transmitter.

SICLOCK Web Configuration

After connecting a service laptop to port X1 and pointing a browser to https://192.168.100.10 (default IP, user admin, password on the device label), complete the following:

  1. Status → GPS: confirm Satellites tracked ≥ 6, Position fix 3D, PDOP < 4. First cold start can take 12–20 minutes.
  2. Configuration → Time source: select GPS (or DCF77) and set the local time-zone offset to UTC for downstream NTP — the NTP packet itself is always UTC.
  3. Configuration → NTP:
    • Enable NTP server on each Ethernet port.
    • Set Stratum = 1 (advertises as primary reference when GPS is healthy).
    • Authentication: Symmetric key (MD5) recommended for S7-400; otherwise leave disabled for commissioning.
  4. Configuration → SIMATIC TIME: enable master mode on the same VLAN, multicast group 224.0.1.1, send interval 1 s.
  5. Configuration → Holdover: enter acceptable drift budget; the TC100 will downgrade its stratum and continue to serve NTP from the internal TCXO if GPS is lost.
  6. Administration → Users: change the default admin password and create a read-only operator account for the maintenance team.
  7. Click Save & Activate. The TC100 reboots in ~30 s and resumes NTP service.

SIMATIC TIME Configuration on the CP 443-1

SIMATIC TIME uses an Ethernet multicast frame (MAC 09-00-06-01-FF-EF, group 224.0.1.1). The CP 443-1 can accept either NTP or SIMATIC TIME on the same port. To switch the S7-400 station from NTP to SIMATIC TIME:

  1. HW Config → CP 443-1 → Time-of-Day Synchronisation.
  2. Change Mode from NTP to SIMATIC TIME.
  3. Set Accept SIMATIC TIME from → LAN.
  4. Download HW Config. The new configuration is active after the next CP 443-1 stop/start (toggle in NetPro or power-cycle the CP).

SIMATIC TIME advantages: lower CPU load on the CP 443-1 (no per-station polling), automatic IP-free reception (multicast), sub-millisecond jitter. Disadvantage: multicast must be allowed in the switching infrastructure; a single blocked IGMP querier on the IE subnet can stop SIMATIC TIME distribution silently.

Verification and Diagnostics

Once the SICLOCK is locked and the CPs are downloading, run the following verification matrix:

Check Method Pass criteria
SICLOCK GPS lock Web UI → Status → GPS Position fix 3D, satellites ≥ 6
SICLOCK NTP service External NTP client (e.g. w32tm /monitor on Windows) Stratum 1 reported, offset < 10 ms LAN
CP 443-1 NTP state NCM Diagnostics → Time-of-Day Last accepted time within 1 interval, offset < 100 ms
CPU clock SFC 1 in OB 1 → HMI Time matches SICLOCK within 1 s after CP sync
Multicast (if used) Wireshark capture on IE port SICLOCK multicast every 1 s on UDP/47404
OPC server timestamp OPC UA client read Server_ServerStatusState Server time within 100 ms of NTP reference

For field commissioning, the quickest end-to-end check is to load the SICLOCK web status page on a maintenance laptop, then watch the Offset graph of each CP 443-1. The trace should settle to a horizontal line within five poll intervals; any saw-tooth pattern indicates switch congestion or duplicate NTP servers polluting the client.

Redundancy and High Availability

Two SICLOCK TC400 units configured as a redundant pair deliver bumpless failover. The pair uses a dedicated sync cable (or the plant network) to elect a master and a standby. The standby continually updates its internal time from the master, so a takeover typically completes within 200 ms with no discontinuity in the served NTP stream.

For a TC100 deployment, redundancy is achieved at the NTP client side: each CP 443-1 can be configured with two NTP server addresses; if the primary fails to answer within four poll intervals, the CP switches to the secondary. Configure both 192.168.100.10 (primary TC100) and 192.168.100.11 (secondary TC100) in the CP. Note: a TC100 is a stratum-1 source, not a peer; running two TC100s side-by-side means each is independent and unsynchronised with the other unless they share a GPS reference. In that case they will both serve essentially the same UTC.

Gotcha: A single GPS antenna connected to two TC100s through a passive splitter is not hot-standby. The TC100 that loses GPS lock drops to holdover; the other continues normally. If both lose GPS, the plant loses time synchronisation. Plan an antenna splitter with active amplification and surge protection, or accept single-antenna architecture for TC100.

Troubleshooting Matrix

Symptom Likely root cause Corrective action
CP 443-1 reports NTP timeout UDP/123 blocked by firewall or ACL Open UDP/123 between SICLOCK and CP subnet; verify with ntpdate -q 192.168.100.10 from a service laptop
SICLOCK shows GPS fix 2D only Insufficient satellites (urban canyon, attenuator) Re-site antenna or remove inline attenuator; verify cable loss < 12 dB
Time jitter ±50 ms on S7-400 IGMP snooping on switch blocking SIMATIC TIME multicast Enable IGMP querier on the IE core switch, or switch the S7-400 to unicast NTP
CPU time drifts 1 s/day CP 443-1 NTP interval too long (> 1 h) Reduce interval to 10–60 s; verify with SFC 1 readout
SICLOCK web UI shows firmware mismatch Old firmware on spare unit Match firmware across the pair; see support.industry.siemens.com for the current V3.x release notes
PTP clients not synchronising TC100 has no PTP grand-master option Upgrade to TC400 with PTP firmware, or deploy an external PTP grand master downstream of NTP
HMI time shows UTC instead of local CP set to UTC, SFC 0 not applied locally Use SFC 0 in OB 1 to set local time on CPU; or have HMI convert UTC offset

Cross-Reference: Other Vendor Time-Sync Approaches

For comparison, Allen-Bradley ControlLogix deployments can use the 1756-TIME module, which provides GPS-disciplined time and PTP (IEEE 1588) grand-master services on a ControlLogix chassis (see the 1756-TIME installation instructions, publication 1756-IN049B-EN-P). ProSoft Technology's Aparian Time Sync Module delivers similar PTP/NTP functionality for Logix racks without a dedicated GPS antenna at every chassis. Fluke's GPS430 is a portable accessory for synchronising Fluke 430 Series power-quality analysers. None of these substitute a SICLOCK on a Siemens-only S7-400 plant, but they are useful in mixed-vendor brownfield migrations where a common time reference must feed both Logix and SIMATIC sides.

What is the difference between SICLOCK TC100 and TC400 for S7-400 time synchronisation?

Both are Siemens SIMATIC NET time servers that deliver NTP/SNTP and SIMATIC TIME. The TC100 (6MF1110-0AA00) is a single-channel, lower-priced server aimed at ≤ 500 clients with TCXO holdover of ±1 s/day. The TC400 (6MF1110-1AA00) supports dual GPS inputs, OCXO holdover of ±100 ms/day, four gigabit Ethernet ports, optional IEEE 1588 PTP grand-master, and redundant pair (bumpless) operation for up to ~5,000 clients. For a 15-PLC, 2-server, 10-client S7-400 cluster, the TC100 is generally sufficient.

Can a CP 443-1 act as an NTP client for a SICLOCK time server?

Yes. The CP 443-1 (6GK7443-1EX30-0XE0) and the CP 443-1 Advanced (6GK7443-1GX30-0XE0) both support NTP/SNTP client mode. Configure the SICLOCK IPv4 address in HW Config → CP 443-1 → Time-of-Day Synchronisation, set the polling interval (10–60 s typical), and download. The CP will write the synchronised UTC into the S7-400 CPU's date-and-time clock at every successful poll; verify with SFC 1 (READ_CLK) in OB 1.

Does the S7-400 support PTP (IEEE 1588) for precision time sync?

No. The classic S7-400 system has no native PTP slave. The supported paths are NTP/SNTP unicast (via CP 443-1) or SIMATIC TIME multicast (via CP 443-1). For sub-microsecond synchronisation you must migrate to S7-1500 with a CP 1543-1 (PTP-capable), or add a third-party PTP-to-SIMATIC TIME bridge such as the Aparian Time Sync Module on a Logix chassis.

How accurate is a GPS-disciplined SICLOCK versus a DCF77 reference?

GPS disciplined, after a 24-hour position fix, achieves ≤ ±1 µs to UTC, with NTP server jitter on a switched LAN below 1 ms. DCF77 is a ground-based 77.5 kHz transmitter in Frankfurt and provides ±20 ms typical, depending on reception path. Use DCF77 only when GPS is not available (e.g. inside a shielded building where an outdoor antenna cannot be installed); otherwise GPS is preferred for plant-wide synchronisation.

How many S7-400 PLCs can a single SICLOCK TC100 serve?

A TC100 comfortably serves up to ~500 NTP clients at a 60 s polling interval, or ~100 clients at a 1 s interval, limited by its CPU and Ethernet bandwidth. For the reference architecture of 15 S7-400 PLCs, 2 OPC servers and 10 HMI clients (≈ 27 clients at 10–60 s intervals), the TC100 has more than 90 % spare capacity. The TC400 is only required when the client count grows beyond several hundred, or when hot-standby redundancy of the time server is mandated.

Back to blog