WinCC Runtime with LOGO! 0BA7: TIA Portal Configuration Reference

Overview: Connecting a PC to LOGO! 0BA7 for HMI Supervision

Engineers frequently ask whether SIMATIC WinCC can supervise a LOGO! 0BA7 logic module over Ethernet without a physical SIMATIC HMI panel — using only a standard PC running a WinCC Runtime. WinCC is Siemens' SCADA and HMI product line (WinCC overview), and LOGO! 0BA7 is the Ethernet-capable generation of the LOGO! logic module family. The combination is workable, but the success of the project depends entirely on the TIA Portal edition, the WinCC Runtime flavor, and the protocol bridge used.

This reference consolidates the engineering rules for pairing WinCC Runtime with LOGO! 0BA7 in TIA Portal, including the limitations observed in TIA Portal V11, the supported paths in current TIA Portal releases, the network topology, the HMI tag mapping, and the verification steps required before commissioning.

LOGO! 0BA7 Communication Capabilities

The 0BA7 hardware generation introduced an integrated Ethernet (RJ45) interface that exposes two communication channels simultaneously:

The 0BA7 will not appear as a native PLC node inside the TIA Portal device catalog the way an S7-1200 or S7-1500 does. Instead, the PC-based HMI must address the LOGO! either as an S7 connection partner (using the LOGO! as a passive S7 server) or as a MODBUS TCP device. Which path is viable depends on the WinCC edition you load on the engineering station and the WinCC Runtime flavor you install on the target PC.

WinCC Product Family and Edition Comparison

WinCC exists in several editions, each with a distinct capability matrix. Choosing the wrong edition is the single most common reason a LOGO! 0BA7 supervision project fails silently.

Why TIA Portal V11 Specifically Fails Against LOGO! 0BA7

Although TIA Portal V11 introduced WinCC Basic, Comfort, and Advanced side-by-side, two practical limitations block a live PC-to-LOGO! link in that release:

1. No LOGO! device object in the project tree. V11 supports LOGO! 0BA7 as a CPU in the project navigator, but the WinCC Comfort/Advanced connection wizard of V11 expects S7-300/400/1200/1500-style partners. A LOGO! 0BA7 added as a CPU will not appear as a selectable HMI connection target in every minor build.
2. S7 protocol version mismatch. TIA V11 uses the V11 S7 driver stack. Some 0BA7 firmware revisions (≤ FS04) negotiate the S7 communication only at the legacy "LOGO! S7" variant, which V11 RT Advanced does not transmit correctly.

Upgrading to TIA Portal V13 SP2 or later — ideally V15.1, V16, V17, or V18 — restores full LOGO! 0BA7 support in both the device catalog and the WinCC connection wizard.

Compatible Configuration Paths

Three working configurations are documented for PC-based supervision of a LOGO! 0BA7. Pick the one that matches the edition available on your engineering workstation.

Network Architecture and IP Configuration

The PC running the WinCC Runtime must share an Ethernet segment with the LOGO! 0BA7. Use the topology below as the canonical wiring plan.

Mandatory IP settings for the configuration:

• LOGO! 0BA7: 192.168.0.5 / 255.255.255.0 (set in LOGO! Soft Comfort > Tools > Ethernet Connections, or via the LOGO! menu on the device).
• PC NIC: 192.168.0.10 / 255.255.255.0 (Windows TCP/IPv4).
• Firewall: open inbound/outbound for TCP/102 (S7 communication) and TCP/502 (MODBUS TCP) if you use that driver.
• Routing: keep the PC and LOGO! on the same VLAN/subnet — do not place a router between them when you only need S7 communication.

Configuration Procedure (WinCC RT Advanced & TIA V17)

The procedure below uses the current, supported path. Substitute the matching steps in your TIA version.

Prerequisites

• TIA Portal ≥ V15.1 installed with WinCC Comfort/Advanced or higher.
• WinCC Runtime Advanced license (single, 1024, or 4096 tag count) — authorized to the PC's Microsoft volume license key or via a parallel USB dongle.
• LOGO! 0BA7 with firmware ≥ FS04 (FS06 or later recommended).
• LOGO! Soft Comfort ≥ 8.0 for program upload and IP confirmation.
• Admin rights on the engineering PC to install the Runtime and to grant firewall rules.

Step-by-Step

1. Open the TIA project that contains the LOGO! 0BA7 program. If the program lives in a legacy LOGO! Soft Comfort file, import it via Project > Import > LOGO! Soft Comfort project.
2. Add a new HMI device: Add new device > PC systems > WinCC Runtime Advanced. Choose the same panel class only if you want to keep the configuration portable between a panel and the PC Runtime; otherwise pick the PC-specific variant.
3. In the project tree, open the HMI device → Connections. Create a new connection of type SIMATIC S7.
4. Configure the connection partner:
   • Partner type: LOGO! 0BA7
   • Interface: Ethernet (TCP/IP)
   • Partner IP address: 192.168.0.5
   • Partner rack/slot: 0 / 0 (LOGO! occupies rack 0, slot 0 in the S7 address model)
   • Connection resource: leave as auto (1..16). LOGO! supports up to 4 simultaneous S7 connections.
5. Map HMI tags to LOGO! addresses. Use the LOGO! variable table from LOGO! Soft Comfort to identify the VM (variable memory) addresses; in the HMI tag editor create tags with the matching DB/Address, e.g.:
   • %DB1.DBX0.0 — boolean (digital I/O and flags)
   • %DB1.DBW0 — word (analog values, counters)
   • %DB1.DBD0 — double word (32-bit counters/timers)
   The LOGO! program editor addresses are shown as VM0, VM1, …; these correspond to DB1 byte offsets in the S7 view. The mapping is byte-for-byte linear.
6. Configure the Runtime target: in the HMI device properties → Runtime, set Runtime start = "On startup" and confirm the Runtime version matches the installed RT Advanced.
7. Compile the HMI project: HMI device → Compile → Software (rebuild all). Resolve any "Partner not found" warnings before continuing.
8. Download to the PC Runtime: select the HMI device → Online → Download to device. Choose the target as PC runtime (not the engineering station). The Runtime will start automatically after download.
9. On the WinCC Runtime screen, open the Diagnostics view and confirm the connection state shows the green "Connected" icon against the LOGO! partner. If red, jump to the Troubleshooting Matrix below.

Variable Address Mapping Reference

MODBUS TCP Path (WinCC Professional or Third-Party SCADA)

If you run WinCC Professional (RT Professional) and prefer the MODBUS TCP route, LOGO! 0BA7 exposes its memory at TCP/502 as a MODBUS server. Configure the HMI connection in TIA as MODBUS TCP:

• Partner IP: 192.168.0.5
• Server port: 502
• Hold Register base: 0 (matches the LOGO! word offset)
• Word/bit mapping follows the LOGO! MODBUS table (Coils = 0…; Holding Registers = 0…). See the LOGO! manual's "MODBUS address table" appendix.

This path is also the canonical bridge when a non-Siemens SCADA (Ignition, WinCC OA, FactoryTalk View SE) has to consume LOGO! data. Use a dedicated MODBUS TCP master connection in those tools.

Verification Checklist

1. Ping test: from the PC, ping 192.168.0.5 must return < 1 ms on a wired segment.
2. S7 test: in TIA, Online → Accessible nodes must list the LOGO! 0BA7 with its MAC address and IP.
3. Live tag: on the WinCC Runtime, watch one digital input tag (e.g. %DB1.DBX100.0) and toggle the physical input — the HMI value must follow within 250 ms (default S7 acquisition cycle).
4. Forced write: from the WinCC Runtime, change a flag (M-flag) and confirm the LOGO! program reacts — proves bidirectional traffic.
5. Diagnostics buffer: in Online → Diagnostics → Buffer of the LOGO!, verify no S7 connection drops logged over a 24-hour burn-in.

Troubleshooting Matrix

Migrating from TIA V11 to a Supported Version

If the engineering workstation is still on TIA V11 and the project must supervise LOGO! 0BA7, perform the upgrade in this order:

1. Install TIA V15.1 (or current) alongside V11; do not uninstall V11 first.
2. Open the V11 project, run Project → Migrate project. Migration preserves the LOGO! program but may flag the WinCC configuration for recompile.
3. Re-add the WinCC Runtime Advanced PC station if it was absent in V11 (V11 only had WinCC Basic/Comfort; only Comfort/Advanced projects migrate cleanly).
4. Recompile, re-download the HMI to the PC Runtime, then re-verify with the checklist above.
5. Once the new Runtime is confirmed on the PC, uninstall TIA V11 to avoid license-port conflicts.

Long-Term Considerations and Best Practices

• Lock the LOGO! firmware revision. Siemens regularly updates the LOGO! S7 behavior; pin the firmware in your change-management system to prevent silent driver breaks.
• Use a dedicated Ethernet segment. Avoid placing the PC Runtime and LOGO! on a busy office VLAN — broadcast storms will surface as intermittent "Disconnected" states.
• Document the VM table. Treat the LOGO! VM-to-DB1 mapping as part of the machine's controlled documentation. Export the CSV from LOGO! Soft Comfort on every program revision.
• Plan for the next generation. Newer LOGO! 8 (0BA8) and LOGO! CMR devices expose additional features, but the WinCC connection wizard path is identical. Refer to the current SIMATIC HMI product page for the latest RT Advanced / RT Professional capabilities before project kickoff.
• For diagnostic-class projects, consider WinCC Unified. The Unified line (see WinCC Unified ProDiag basics) is the strategic direction, though ProDiag itself applies to S7-1500/1200 programs, not LOGO!.

FAQ