1. Problem Definition and Scope
Many compact machine designs replace a single larger controller with two or more LOGO! 8 units (Siemens order-number family 6ED1052-...) cooperating over their built-in Ethernet port, while a single low-cost KTP600 Basic mono PN (6AV6647-0AB11-3AX0) serves as the operator panel. The challenge is that the HMI must establish two independent S7 connections on one Ethernet cable, one per LOGO!, while the LOGO! 8 firmware has a hard ceiling on the number of simultaneous S7 communication partners it will accept.
This reference documents the engineering required to:
- Plan IP addresses and subnet topology for 1 HMI + 2 LOGO!.
- Configure the LOGO! 8 Ethernet parameters using LOGO! Soft Comfort.
- Build the project in TIA Portal V18 with the LOGO! HSP installed.
- Create two S7 connections on the KTP600 and map tags to the right LOGO!.
- Verify the system and recover from the most common commissioning faults.
2. Prerequisites
| Component | Recommended version | Notes |
|---|---|---|
| KTP600 Basic mono PN | 6AV6647-0AB11-3AX0, FW ≥ V12 | Per Siemens SiePortal product page (6AV6647-0AB11-3AX0) |
| LOGO! 8.3 base unit (E variant) | FS03, e.g. 6ED1052-1MD08-0BA1 | Built-in Ethernet, supports S7 server |
| LOGO! 8.4 base unit (E variant) | FS04 | Adds expanded VM area and improved S7 connection count |
| TIA Portal | V18 Update 4 or later, with LOGO! HSP V18 | HSP delivered via TIA Portal Support Packages |
| LOGO! Soft Comfort | V8.4 or V9.0 | For online Ethernet parameter setting |
| Network | 100 Mbit/s switched Ethernet, Cat5e or better | No crossover needed; switch optional for two-node case |
3. Network Topology and IP Plan
The three devices share one subnet. The following address plan is used throughout the rest of this article:
| Device | IP address | Subnet mask | TSAP / port (LOGO! side) | Role |
|---|---|---|---|---|
| KTP600 Basic mono PN | 192.168.10.50 | 255.255.255.0 | n/a (client) | HMI / S7 client |
| LOGO! 8 #1 | 192.168.10.11 | 255.255.255.0 | 00.01 (slot 1) | S7 server, machine A |
| LOGO! 8 #2 | 192.168.10.12 | 255.255.255.0 | 00.02 (slot 2) | S7 server, machine B |
| Programming PG (optional) | 192.168.10.100 | 255.255.255.0 | n/a | TIA Portal / Soft Comfort |
Each LOGO! 8 provides a fixed S7 slot for its server connection. LOGO! Soft Comfort exposes this as a TSAP; the slot is appended to the IP address when configuring TIA Portal. The two LOGO! units must therefore use different slot numbers (slot 1 and slot 2 in the example) so that the HMI can route S7 PDUs to the correct partner.
4. Configuring LOGO! 8 Ethernet Parameters
On the LOGO! itself, navigate the integrated HMI (or use LOGO! Soft Comfort > Tools > Ethernet Connections) and set:
- IP address: 192.168.10.11 (unit #1) / 192.168.10.12 (unit #2).
- Subnet mask: 255.255.255.0.
- Gateway: 0.0.0.0 (leave blank if no router present).
- Allow S7 communication: Enabled (LOGO! 8.2 and newer).
- S7 connection slot: 1 for unit #1, 2 for unit #2.
From LOGO! Soft Comfort V8.4 onward, you can also verify the open TCP port (102/TCP) with the integrated diagnostic. The maximum number of simultaneous S7 partners is firmware-dependent:
| LOGO! FW | Max. S7 connections (server) | Notes |
|---|---|---|
| 8.0 / 8.1 (FS01) | Not supported | Use Modbus TCP or upgrade |
| 8.2 (FS02) | 4 | PG + 3 HMI/SCADA |
| 8.3 (FS03) | 8 | PG + 7 partners (combined) |
| 8.4 (FS04) | 8 | Same ceiling, faster cycle |
5. Building the TIA Portal Project
- Open TIA Portal V18, choose Create new project.
- Install the LOGO! 8.4 HSP from Options > Support Packages if the LOGO! devices do not appear in the device catalog.
- Add the first LOGO! with Add new device > Controllers > LOGO! > LOGO! 8 > 6ED1052-1xxx08-.... Repeat for the second LOGO!.
- Add the HMI: Add new device > HMI > SIMATIC Basic Panels > 6" > KTP600 Basic mono PN (6AV6647-0AB11-3AX0).
- Open Devices & Networks and connect each LOGO! Ethernet port to the HMI PROFINET port using the Connections editor. TIA Portal automatically proposes one S7 connection per link.
The result is a project tree containing three devices. The HMI node now lists two connections: HMI_Connection_1 and HMI_Connection_2.
6. Configuring the Two S7 Channels on the KTP600
For each connection, verify the following parameters in HMI_Connection_x > Properties > General:
| Parameter | Connection 1 (LOGO! #1) | Connection 2 (LOGO! #2) |
|---|---|---|
| Partner (LOGO!) IP | 192.168.10.11 | 192.168.10.12 |
| LOGO! slot / Rack | 1 / 0 | 2 / 0 |
| Connection name | LOGO_A | LOGO_B |
| Cycle time | 500 ms | 500 ms |
| Watchdog bit | DB1.DBX0.0 | DB1.DBX0.1 |
Two additional area pointers must be enabled under Properties > Area pointers:
- Coordination (one byte, used by KTP600 for life-bit).
- Date/time (only needed if you want the HMI to write the time to both LOGO! clocks; both connections can use the same PG pointer).
7. Tag Mapping to the LOGO! VM Area
The LOGO! 8 exposes its variables through the Variable Memory (VM) mapping. In TIA Portal, when you select a tag of type Word, address VW0 on a LOGO!, the driver requests the VM area of that particular LOGO! via the matching connection. No manual mapping of tags to LOGO! addresses is required beyond declaring the address range you want to read.
Reference ranges (LOGO! 8.3 / 8.4):
| Address (Word) | Direction | Typical use |
|---|---|---|
| VW0 – VW199 | Read / Write | Digital markers, byte-level user data |
| VW200 – VW399 | Read / Write | Word markers (e.g. counter setpoints) |
| VW400 – VW599 | Read | Process inputs image (I-state) |
| VW600 – VW849 | Read | Process outputs image (Q-state) |
| VW850 – VW999 | Read | Analog input image (AI) |
| VW1000 – VW1023 | Read | Analog output image (AQ) |
To display a digital input of LOGO! #2 on the HMI, create a tag in the HMI tags editor, select connection LOGO_B and address V0.0. To display the same physical point on LOGO! #1, address V0.0 on connection LOGO_A. The connection field is what selects the partner, not the address.
8. Building HMI Screens
- Open HMI > Screens > Add new screen. Create at minimum Overview, Machine A, Machine B, and Alarms.
- On the Overview screen, place two Status/Force views or two Symbolic IO fields showing a tag from each LOGO! so the operator can confirm both connections are live at a glance.
- Use the Connection status system function on screen change events to log which partner is currently unreachable.
- For shared setpoints (e.g. global production counter), write to both VM areas using two separate tags triggered from the same button.
Sample tag list excerpt:
HMI_Tag_Block "LogoA_DI0" : BOOL, conn=LOGO_A, addr=V4000.0
HMI_Tag_Block "LogoA_Run" : BOOL, conn=LOGO_A, addr=V6000.0
HMI_Tag_Block "LogoA_Cnt_SP" : INT, conn=LOGO_A, addr=VW200
HMI_Tag_Block "LogoB_DI0" : BOOL, conn=LOGO_B, addr=V4000.0
HMI_Tag_Block "LogoB_Run" : BOOL, conn=LOGO_B, addr=V6000.0
HMI_Tag_Block "LogoB_Cnt_SP" : INT, conn=LOGO_B, addr=VW200
9. Verification and Commissioning
- Compile the project (TIA Portal > HMI > Compile > Software (rebuild all)). Errors here usually indicate an address outside the VM range or a typo in the connection name.
- Download to the KTP600 via Ethernet. Confirm transfer mode PN/IE and target IP 192.168.10.50.
-
Start Runtime on the panel. The "Connection status" indicator should turn green for both
LOGO_AandLOGO_Bwithin 2–5 seconds. - Force a value on each connection from TIA Portal (HMI Tags > right-click > Modify) and confirm the LOGO! 8 reacts. If the LOGO! is running a Soft Comfort program that uses a network input (NI), write to that NI's VM location.
-
Cycle audit: monitor
LOGO_A.Cnt_SPon the panel and verify it updates inside the configured 500 ms cycle. Slower updates indicate network collision or switch mis-configuration.
10. Troubleshooting Matrix
| Symptom | Likely cause | Diagnostic | Fix |
|---|---|---|---|
| Both connections red on startup | Different subnet / wrong cable | Windows ping 192.168.10.11 from PG |
Verify IP, subnet, gateway; replace cable |
| Only connection #1 red | Duplicate slot number | LOGO! Soft Comfort > Ethernet Connections | Set LOGO! #2 to slot 2 |
| Connection drops after ~60 s | Watchdog timeout because LOGO! cycle is slower than HMI cycle | HMI event log shows "Connection failure LOGO_B" | Raise HMI cycle to 1000 ms or shorten LOGO! program cycle |
| Tags show "#" (illegal value) | Address outside VM range | Address table vs. LOGO! 8 manual | Re-map inside VW0–VW1023 |
| HMI cannot write to a tag | Address in read-only section (VW400+) | Cross-check VM map | Use VW0–VW399 for writes |
| LOGO! reports "W:16#007F" | More than 8 partners on LOGO! 8.3 / 8.4 | LOGO! diagnostic buffer | Close other S7 sessions (PG, OPC, second HMI) |
| Compile error "Address not supported for LOGO!" | Using absolute I/Q area instead of VM | TIA compile log | Change addresses to V-range |
| Tags correct but display stays at 0 | Wrong connection selected on tag | HMI tag inspector > Connection | Reassign connection to the proper LOGO! |
11. Limits, Cycle Times and Performance Notes
Two parallel S7 connections share the 100 Mbit/s link. The effective update rate on the panel is determined by the slowest of:
- LOGO! program cycle time (typical 10–50 ms depending on program length).
- HMI configured cycle (minimum 100 ms; 500 ms is a safe default).
- TCP keep-alive handled by the LOGO! (default 30 s).
With a 500 ms HMI cycle and ten tags per connection, the load on the network is < 1 % and is dominated by the LOGO! cycle, not by the panel. If you notice latency, first reduce the number of acquired tags, then shorten the LOGO! cycle by removing unused blocks in the Soft Comfort program.
For diagnostics over the same network, enable the KTP600's Diagnostics screen from the project settings. It shows live connection status, partner IP and last error code without requiring additional area pointers.
12. Field-Proven Commissioning Checklist
- Reserve one IP per device; document the plan in the cabinet drawing.
- Set unique LOGO! slot numbers (1 and 2 minimum).
- Disable web server / FTP on the LOGO! if not used to free TCP sockets.
- Stick a label with IP and slot on each LOGO! so service engineers do not have to reconfigure.
- Export the TIA project and the LOGO! Soft Comfort program to the same archive folder after every change; a missing LOGO! program is the most common cause of "everything compiles but nothing works" in the field.
How many LOGO! 8 controllers can one KTP600 Basic mono PN talk to?
The panel supports up to 16 S7 connections. The real ceiling is the LOGO! 8 firmware: 8.2 limits the LOGO! to four simultaneous S7 partners, while 8.3 and 8.4 allow eight. In practice two LOGO! units is well inside the limit; a third LOGO! plus a PG online session brings the 8.2 family to its limit.
Do I have to change anything on the LOGO! to enable S7 communication?
Yes. From the LOGO! menu (or LOGO! Soft Comfort > Tools > Ethernet Connections) you must enable S7 access, assign a fixed IP address, and set the S7 slot number. Without an explicit slot number the LOGO! will not respond to S7 requests even though the TCP socket is open.
Can the HMI write to the LOGO! outputs directly?
No. The S7 path only exposes the LOGO! VM area. To drive a physical output, write a value into a VM marker (e.g. VW200) and connect that marker to the output block inside the Soft Comfort program.
Why does the panel show "Connection failure" only after a long runtime?
The most frequent cause is that the LOGO! 8.2 firmware enforces an idle timeout on connections that do not exchange data. Increase the HMI acquisition cycle, or reduce the number of unused tags, so each S7 connection receives a request at least every 30 seconds.
Is a switch required between the HMI and the two LOGO! units?
No. The three devices can be wired in a line or daisy-chain with two cables. A switch is recommended only if you also need a PG/PC connection, want to mirror the port for diagnostics, or expect to add more than three nodes. Direct cable works because all three Ethernet ports support Auto-MDIX.