Siemens CP1430TF and SIBUKO Triaxial Networking with WinCC and SIMATIC S5
This reference documents how to integrate a SIMATIC S5 station equipped with a CP 1430 TF communication processor into a WinCC visualization layer using legacy SIBUKO triaxial cabling and modern SCALANCE media conversion. Field engineers maintaining brownfield S5 installations face this exact topology, where the PLC side predates RJ45 industrial Ethernet but the HMI side is a contemporary PC. The document captures the cabling rules, the transceiver interfaces, and the migration paths distilled from Siemens SIMATIC NET documentation and field correspondence on CP 1430 / SIBUKO integration.
1. System Overview: S5 to WinCC Networking Through Triaxial and ITP Media
The original plant network relies on the SIMATIC NET triaxial cable plant. A triaxial cable is a coaxial construction with an additional outer shield, providing the noise immunity required inside control cabinets and across long factory runs. The SIBUKO (SImens BUchse KOaxial) transceiver terminates this media on the device side and presents either an AUI (Attachment Unit Interface) or, on certain variants, an MAU interface to the connected node. The CP 1430 TF is the SIMATIC S5 communication processor that brings this triaxial (and ITP) connectivity into the S5 CPU.
On the visualization side, the HMI workstation runs WinCC. Contemporary PCs no longer expose AUI or MAU ports; they provide RJ45 Ethernet, typically 10BASE-T or 100BASE-TX. Bridging the legacy triaxial segment to a contemporary WinCC station therefore requires a media conversion choice. Siemens addresses this with the SCALANCE X101-1AUI media converter, which provides one AUI port and one RJ45 port, allowing a long-haul triaxial leg to land directly on a standard Ethernet NIC.
2. Key Component Identification
| Component | Function | Interface presented | Media supported |
|---|---|---|---|
| CP 1430 TF | SIMATIC S5 communication processor for TF (Twisted Pair / Triaxial) networks | MAU / AUI and ITP per variant | Triaxial cable and Industrial Twisted Pair (ITP) at 10 Mbit/s |
| SIBUKO package | Triaxial transceiver / tap system for SIMATIC NET installations | MAU (not DTE) | Triaxial cable plant, runs to several kilometers per segment |
| SSV 104 | Triaxial transceiver / signal-conditioning unit | MAU | Triaxial cable plant |
| AUI drop cable 727-1 | Pre-assembled transceiver drop cable with AUI connector | AUI male to AUI female | Connects MAU transceivers to nodes; supports up to 50 m drop length |
| SCALANCE X101-1AUI | Industrial media converter between AUI and RJ45 | 1 x AUI, 1 x RJ45 | AUI segment at 10 Mbit/s to 10BASE-T RJ45 |
| WinCC station | SCADA / HMI runtime | RJ45 10/100 Ethernet NIC | ITP-compatible signaling at 10 Mbit/s |
3. Cabling Rules: AUI Drop Cable, MAU Interface, Distance Limits
Three cabling rules dominate CP 1430 / SIBUKO plant integration work, and each has been a source of integration failures.
3.1 SIBUKO requires a MAU interface, not a DTE
A SIBUKO transceiver is a media attachment unit; it must be mated to a node that exposes an AUI/MAU-style connector. A standard PC Ethernet NIC exposed as DTE (the typical RJ45 implementation) is not directly compatible. Trying to plug a SIBUKO into a pure RJ45 DTE port is a common misread of the AUI/MDI mapping. The intermediate path is what makes the integration work: a media converter that accepts AUI on one side and presents RJ45 DTE on the other.
3.2 AUI drop cable 727-1 length and topology
The AUI drop cable 727-1 is the standard SIMATIC NET AUI cable. It is the proper interface between a triaxial transceiver (such as a SIBUKO termination or the SSV 104) and a node. The drop is rated up to 50 m in a clean topology. When the same drop is used with an SSV 104 transceiver in the field, the practical maximum distance from transceiver to node is 40 m. For runs under 10 m, the configuration does not require a SIBUKO at all; an AUI drop cable 727-1 alone can land the SSV 104 onto the node.
| Topology element | Maximum distance | Notes |
|---|---|---|
| AUI drop cable 727-1, standalone | 50 m | Standard SIMATIC NET rating |
| AUI drop cable 727-1 with SSV 104 in line | 40 m | Transceiver to node budget |
| Triaxial segment, point-to-point | A few hundred meters | Coaxial / triaxial attenuation budget dependent |
| Triaxial segment, designed plant | Up to 3000 m | Repeatered trunk with multiple transceivers |
| HMI drop to legacy plant via triax | Above 100 m | Use SCALANCE X101-1AUI to land triax onto RJ45 |
3.3 Distance class drives the topology choice
The HMI distance from the CP 1430 TF is the master variable in the topology decision. Three distance classes lead to three distinct configurations:
- Short (under 10 m): Direct AUI drop cable 727-1, no SIBUKO required at the HMI side. SSV 104 + AUI drop cable to the node is sufficient.
- Mid-range (roughly 10 m to 100 m): Standard triaxial segment with one transceiver hop; AUI drop cable 727-1 from transceiver to node. SCALANCE X101-1AUI used when node is RJ45-only.
- Long (over 100 m, up to several hundred meters or ~3000 m): Triaxial trunk with a transceiver at the field end and a SCALANCE X101-1AUI at the HMI cabinet to convert AUI to RJ45 for the WinCC station.
4. CP 1430 TF Configuration for WinCC Communication
The CP 1430 TF contains the transport layer that WinCC expects to see as its S5 partner. Configuring it consists of loading a transport parameters set (often called the INIT or parameter block) into the module via the STEP 5 COM 1430 / parameterization tool on a programming device, and verifying that WinCC can resolve the partner.
4.1 Module selection
Select the CP 1430 TF (TF = Twisted Pair / Triaxial Foil, depending on Siemens historical nomenclature; in CP 1430 family context it identifies the physical layer termination type) when the S5 CPU must connect over triaxial cable or ITP. For pure RJ45 10BASE-T segments with no triax, consider migrating to a CP 1430 TCP variant or, more practically today, replacing the S5 with an S7-1200 / S7-1500 station.
4.2 Transport stack selection
On the CP 1430, the transport layer is configurable. For WinCC integration the stack is typically ISO-on-TCP (RFC 1006) or, in legacy plant configurations, the Siemens-specific transport. Match the WinCC channel configuration to the CP transport selection.
4.3 Address and TSAP assignment
Both the CP 1430 and the WinCC channel require matching transport addresses. In an ISO / ISO-on-TCP deployment the relevant fields are:
| Field | CP 1430 side | WinCC side |
|---|---|---|
| Transport selector / TSAP | Local TSAP set in CP parameters | Partner TSAP matching local |
| IP / MAC, ISO | ISO MAC only (CP 1430 TF is non-IP) | ISO NSAP / MAC pair |
| Connection role | Passive or active per CP parameter | Complementary role |
| Connection count | Total configured connections of CP | One channel per WinCC connection |
4.4 Channel configuration on WinCC
Use the SIMATIC S5 Protocol Suite channel (or its successor depending on WinCC version) and bind it to the NIC that connects to the SCALANCE X101-1AUI on the RJ45 side. Point the channel at the configured transport address of the CP 1430. Test with a one-tag read/write probe before loading the full tag list.
5. Media Conversion: SCALANCE X101-1AUI as the Bridge
Where the HMI side is RJ45-only, the SCALANCE X101-1AUI is the canonical bridge from AUI triaxial onto RJ45 10BASE-T. The unit accepts an AUI drop cable 727-1 on its AUI port and presents a standard RJ45 to the WinCC PC on its 10 Mbit/s Ethernet port.
5.1 Cabling the bridge
- Terminate the triaxial segment at the HMI cabinet end with an SSV 104 (or compatible transceiver) on a SIBUKO-capable patch point.
- Connect an AUI drop cable 727-1 from the transceiver AUI connector to the SCALANCE X101-1AUI AUI port.
- Connect a standard RJ45 patch cable from the SCALANCE X101-1AUI RJ45 port to the WinCC station NIC.
- Apply power to the SCALANCE; verify link LED on the RJ45 side and AUI activity LED on the AUI side.
5.2 Signal and speed constraints
The SCALANCE X101-1AUI operates at the AUI media's native rate. CP 1430 TF and SIMATIC NET triaxial equipment operate at 10 Mbit/s. The WinCC NIC will autonegotiate or fall back to 10 Mbit/s half-duplex on the RJ45 side. Force the NIC to 10 Mbit/s half-duplex if the driver permits it; full-duplex is not supported on the AUI side of the converter.
5.3 When not to use a converter
If the CP 1430 TF is configured for ITP (Industrial Twisted Pair) instead of triax, the connection may be ITP-to-RJ45 directly. ITP is signal-compatible with RJ45 10 Mbit/s Ethernet per the legacy SIMATIC NET specification. In that case, a SCALANCE media converter is not required; the ITP segment can land directly on the WinCC RJ45 NIC at 10 Mbit/s. Verify the wiring: ITP uses the Siemens-specific pair assignments rather than the TIA-568A/B T568A/T568B pinout on early installations.
6. Distance-Based Configuration Matrix
The table below encodes the topology decision given the distance from the CP 1430 TF to the WinCC station. Use it to select the cable plant and conversion hardware.
| Distance class | Cable plant | Transceiver at HMI end | AUI drop | Conversion to RJ45 | Bridge hardware |
|---|---|---|---|---|---|
| Under 10 m | Short triaxial / direct | SSV 104 | 727-1, <10 m | Direct AUI if node has AUI; otherwise SCALANCE | SCALANCE X101-1AUI |
| 10 m to 50 m | Triaxial | SSV 104 + SIBUKO termination | 727-1, up to 40 m (with SSV 104) or 50 m | SCALANCE X101-1AUI if node RJ45-only | SCALANCE X101-1AUI |
| 50 m to ~100 m | Triaxial | SIBUKO termination | 727-1 to local transceiver | SCALANCE X101-1AUI at HMI end | SCALANCE X101-1AUI |
| ~100 m to several hundred m | Triaxial trunk | SIBUKO termination | 727-1 to converter | SCALANCE X101-1AUI at HMI end | SCALANCE X101-1AUI |
| Several hundred m to ~3000 m | Triaxial trunk with repeaters | SIBUKO termination | 727-1 to converter | SCALANCE X101-1AUI at HMI end | SCALANCE X101-1AUI |
7. Field-Proven Engineering Notes
Several issues repeat across brownfield CP 1430 / SIBUKO deployments. Each can be addressed without replacing the S5 platform.
7.1 WinCC cannot see the S5 after media change
If the HMI is moved further from the S5 cabinet and the original AUI patch is left in place, the most common failure mode is "AP0 not reachable" or similar transport-timeout errors on the WinCC channel. Cause: the AUI drop budget is exhausted at the new distance. Resolution: introduce a triaxial trunk with a SIBUKO termination at the HMI end and a SCALANCE X101-1AUI as the AUI-to-RJ45 bridge.
7.2 SCALANCE X101-1AUI link LED dark on RJ45 side
Verify in order: (1) the WinCC NIC is forced to 10 Mbit/s half-duplex; (2) the RJ45 patch is straight-through, not crossover (modern NICs usually auto-MDIX, but the converter port is fixed MDI); (3) the SCALANCE has AUI-side link activity (rules out a triaxial / SIBUKO plant failure); (4) the WinCC PC NIC driver is not in power-saving mode.
7.3 CP 1430 reports no connection despite intact cabling
If the cabling is verified but the CP 1430 reports zero active connections, the parameter block loaded into the CP may not match the WinCC channel side. Recompute the transport selector / TSAP matching and re-flash the CP via the COM 1430 parameterization tool. Some CP 1430 firmwares require a CP STOP / CP RUN cycle after parameter change.
7.4 Mixing ITP and RJ45 without conversion
Where the CP 1430 TF supports ITP, ITP is signal-compatible with 10BASE-T at the physical layer. A direct RJ45-to-ITP cable can be assembled but the pinout is not the TIA-568 scheme used by modern Ethernet. Miswired pairs are a routine failure source in mixed-media cabinets. Confirm pin assignments against the legacy SIMATIC NET "Triaxial Networks" manual or the equivalent SIMATIC NET CD PDF before commissioning.
7.5 Discontinuation of SIBUKO
SIBUKO packages and the original triaxial catalog IK PI 2002 are no longer in active distribution. Spares depend on stock at SIMATIC NET partners. If a brownfield plant is on its last SIBUKO terminations, plan a phased migration to RJ45 100BASE-TX with SCALANCE XF switches and a CP 343 / CP 443 on an S7-300 / S7-400 successor, or to PROFINET with an S7-1200 / S7-1500 replacement.
8. Validation Procedure After Configuration
- Power up the CP 1430 TF with the parameter block loaded. Verify the SF (system fault) and BF (bus fault) LEDs are off. CP RUN LED steady green indicates healthy module state.
- Power up the SCALANCE X101-1AUI at the HMI end. Verify the AUI activity LED pulses with the triaxial segment traffic and the RJ45 link LED is on.
- From the WinCC PC, open the project, activate the S5 Protocol Suite channel, and run a one-tag diagnostic against a known scalar in the S5 DB. A successful read/write round trip validates the entire chain.
- Review the CP 1430 connection table on the engineering station: the connection from the WinCC PC should appear in the Active Connections list with state = established.
- Capture a packet trace on the RJ45 side at 10 Mbit/s forced mode to confirm transport setup frames are exchanged between the WinCC channel and the CP 1430 transport endpoint.
9. Troubleshooting Matrix
| Symptom | Likely cause | Check | Remediation |
|---|---|---|---|
| WinCC shows "partner not reachable" | Distance exceeds AUI drop budget | Measure physical distance from transceiver to node | Replace direct AUI patch with triaxial trunk + SCALANCE X101-1AUI at HMI |
| SIBUKO cannot be plugged into PC NIC | PC NIC is DTE / RJ45, SIBUKO is MAU | Inspect connector type at SIBUKO end | Insert SCALANCE X101-1AUI between SIBUKO and PC |
| SCALANCE RJ45 LED dark | NIC speed/duplex mismatch | Force NIC to 10 Mbit/s half-duplex | Set NIC to fixed 10/Half |
| CP 1430 BF LED on | No triaxial link activity | Verify SIBUKO termination power and segment continuity | Replace terminator or repair segment |
| Connection drops intermittently | AUI drop near 50 m limit, or noisy segment | Reduce drop length, check shielding | Shorten drop to under 40 m with SSV 104; re-route cable |
| WinCC values update slowly | Multiple connections sharing CP bandwidth | Review CP 1430 active connections count | Reduce number of concurrent CP connections |
| CP 1430 will not accept new parameters | CP in RUN with locked DB | Stop CP via COM 1430 tool before parameterization | Cycle CP STOP/RUN after parameter load |
10. Migration Path Off SIBUKO
The SIBUKO platform is end-of-life. Maintaining it is technically feasible as long as terminations, transceivers, and the SIMATIC NET "Triaxial Networks" documentation remain available. For longer-horizon maintenance, the recommended migration ladder is:
- Stage 1: Media-only upgrade. Keep the S5 with CP 1430 TF. Replace SIBUKO + AUI drop + SCALANCE X101-1AUI path with a CP 1430 TCP variant and a SCALANCE XF-100 switch port on the WinCC side.
- Stage 2: CPU migration to S7-300 / S7-400. Replace S5 with S7-300/S7-400 plus CP 343 / CP 443 and migrate WinCC tags.
- Stage 3: PROFINET migration to S7-1200 / S7-1500. Replace the controller with S7-1200/S7-1500, move WinCC to TIA-Portal WinCC, and decommission the triaxial cable plant.
11. Operator and Maintenance Safety
What is a SIBUKO package and is it still available?
SIBUKO is the Siemens triaxial transceiver system used to terminate triaxial cable plants onto a node. It has been discontinued for years and is no longer offered as a current product. Spare units and the original "Triaxial Networks" manual are only obtainable from SIMATIC NET CD archives or stock at legacy Siemens partners.
Can I connect a SIBUKO directly to a PC's RJ45 Ethernet port?
No. The SIBUKO presents a MAU (AUI) interface, while a PC NIC exposes a DTE / RJ45 interface. Use a SCALANCE X101-1AUI media converter between the SIBUKO (or its SSV 104 drop) and the PC's RJ45 port. The converter accepts AUI on one side and 10BASE-T RJ45 on the other.
What is the maximum length of an AUI drop cable 727-1?
The AUI drop cable 727-1 is rated up to 50 m in a clean SIMATIC NET topology. When the same cable is used with an SSV 104 in line, the practical maximum transceiver-to-node budget is 40 m.
Does the CP 1430 TF support ITP as well as triaxial?
Yes. The CP 1430 TF supports both triaxial cable and ITP (Industrial Twisted Pair) at 10 Mbit/s. ITP is signal-compatible with 10BASE-T RJ45 Ethernet, so a CP on ITP can often be connected to a WinCC station's RJ45 NIC without media conversion, provided the ITP-to-RJ45 pinout is verified.
How do I configure the CP 1430 TF for WinCC S5 connectivity?
Use the COM 1430 / parameterization tool to load a transport parameter block into the CP 1430, set the transport selector / TSAP, and select the connection role. Then on the WinCC PC, configure the SIMATIC S5 Protocol Suite channel with the matching transport address and bind it to the NIC connected (directly or via SCALANCE X101-1AUI) to the CP 1430.