IMDHMIControls LibraryShop main store

Troubleshooting

S7-1200 shows link lights but TIA Portal cannot connect

PLC programming Published 6 min read

Short answer

Green Link and blinking Rx/Tx on the S7-1200's PROFINET port prove cable and traffic only, never a working TIA Portal connection. The fault is almost always the wrong PC adapter or a subnet mismatch: select the cabled interface as the S7ONLINE (STEP 7) access point, scan Accessible devices, give the PC a unique address in the CPU's subnet, then go online. If the scan shows an unconfigured CPU, assign its IP address and PROFINET name first, then connect.

On this page
  1. What the Link and Rx/Tx LEDs prove
  2. Select the cabled adapter in the PG/PC interface
  3. Find the CPU with the Accessible devices scan
  4. Put the PC in the CPU's subnet: the arithmetic
  5. Assign the IP address and PROFINET name to an unconfigured CPU
  6. Run the sequence, pick the branch
  7. Questions asked

The green Link LED and the blinking orange Rx/Tx LEDs on the S7-1200's X1 P1 PROFINET port prove two things and only two: the cable is seated on a live port, and Ethernet frames are moving. They say nothing about IP addressing, about which network adapter TIA Portal has picked, or whether the CPU holds a usable identity, which is exactly why the connection fails while the LEDs look perfect. Work the fault in one order: select the cabled adapter as the S7ONLINE (STEP 7) access point, discover the CPU with the Accessible devices scan, put the PC on a unique address in the CPU's subnet, then go online. On a bench 1211 AC/DC/RLY with STEP 7 Professional V13, that sequence closes nearly every case.

The Link LED reports the physical layer: the CPU's port has negotiated speed and duplex with the PC's network card over the cable, so wiring and port are good. The Rx/Tx LEDs report traffic, any frames in either direction: broadcast chatter from switches, ARP probes, discovery attempts, even frames addressed somewhere the PC cannot reach. A PC sitting on the wrong subnet produces precisely this picture — green Link, busy Rx/Tx, dead application connection. Read the LEDs as a wiring verdict and nothing more. Decision: green Link with blinking Rx/Tx means the cable, the port and the network card are proven; stop swapping cables and start checking the adapter and the addressing.

Select the cabled adapter in the PG/PC interface #

TIA Portal does not browse through whichever adapter Windows feels like using; it goes online through the access point S7ONLINE (STEP 7), and that access point points at exactly one concrete interface. On a laptop with Wi-Fi, a VPN client and virtual adapters installed, it usually holds a wrong one, and no setting inside the project can repair that. Set it explicitly:

  1. Open the Windows Control Panel and start Set PG/PC interface.
  2. Under Application access point, confirm the selected entry is S7ONLINE (STEP 7).
  3. In the interface list, take the PN/IE entry of the network card physically cabled to X1 P1 — not the wireless adapter, not a VPN tunnel, not a virtual adapter.
  4. In Windows' own network settings, confirm this card is the one showing a connected Ethernet link, so the access point and the cable agree.

A newly connected adapter registers on its own; reopen the dialog if it was plugged in after TIA Portal started. The same wrong-adapter fault hits visualization PCs, which is why a SCADA PC station that reaches only one S7-1500 is diagnosed with this same adapter check. And when ping reaches the PLC but TIA Portal does not, that is the signature of this selection fault — PG/PC interface fix for the ping-works-but-no-connection case walks it adapter by adapter.

Find the CPU with the Accessible devices scan #

With the right access point set, discover the CPU before touching any address. In TIA Portal V13, open Accessible devices from the Online menu and expand the entry for the interface you selected. The scan runs at the Ethernet frame level, below IP, so it lists the CPU with its device type, MAC address and, when one is set, its IP address — even when that address is unknown or was never configured. Compare the listed MAC with the one printed on the CPU before you trust the entry; on a shared network it is the only reliable identity.

If the list stays empty, the fault is still on the PC side: recheck the cable and the selected interface, then test host security software. Antivirus and endpoint filtering can block the discovery frames, which is how a CPU that pings can still hide from the scan. Run that test as a temporary, approved exception agreed with the site's security owner, and turn the protection back on as soon as the scan is done. Decision: the CPU appears, its identity and address are proven; the list stays empty, fix the adapter or the filtering before changing anything on the PLC.

Put the PC in the CPU's subnet: the arithmetic #

For normal IP communication the PC's adapter and the CPU need unique addresses in the same subnet, and the subnet mask decides what same means: an address ANDed with the mask yields its network, and only matching networks talk directly. Read the CPU's actual address from the scan or from Online & diagnostics instead of guessing it.

Worked example, CPU at 192.168.0.1 with mask 255.255.255.0:

  • CPU network: 192.168.0.1 AND 255.255.255.0 = 192.168.0.0 (192 AND 255 = 192; 168 AND 255 = 168; 0 AND 255 = 0; 1 AND 0 = 0).
  • PC adapter set to 192.168.0.55 with the same mask: 192 AND 255 = 192; 168 AND 255 = 168; 0 AND 255 = 0; 55 AND 0 = 0, giving 192.168.0.0 — the same network, so frames cross the cable directly with no gateway involved.
  • PC left on the office LAN at 192.168.1.20 with mask 255.255.255.0: the network works out to 192.168.1.0, one octet away from 192.168.0.0. No route exists, ping fails, and the LEDs stay green through all of it.
  • PC set to the CPU's own 192.168.0.1: a duplicate address; the two stations answer each other's ARP probes and the connection never stabilizes. Uniqueness is as strict as subnet membership.

Decision: set the adapter to a static, unused address in the CPU's subnet with the CPU's mask, gateway left empty for a direct cable. The same mismatch breaks plant networks one layer up, where a SCADA gateway cycles Connecting and Disconnected until the subnets agree.

Assign the IP address and PROFINET name to an unconfigured CPU #

If the scan lists the CPU with an empty address field, or IP communication still fails after the subnet fix, the CPU has no usable identity yet and needs one written to it. Inside TIA Portal, open the Devices & networks editor: right-click the PROFINET IO device and use Online & diagnostics to read its live state, or select the device in the network view and run Assign device name — both write the PROFINET device name and the address from the project's device configuration to the CPU. Outside a project, Proneta, Siemens' PROFINET commissioning tool, lists the devices seen on the selected adapter and writes the IP address and device name you enter, which is often faster on a bare bench CPU.

Take the values from the plant's addressing plan, not from habit. Match the MAC on the case before writing anything: an address or device name pushed to the wrong node re-addresses a live station and drops its I/O until it is corrected. After writing, rescan; the CPU reports its new identity, put the PC in that subnet and go online.

Run the sequence, pick the branch #

Run the checks in order and let each result pick the next step, changing one item at a time so every result identifies its cause:

  1. Green Link with blinking Rx/Tx — wiring proven; the cable is not the fault.
  2. Set PG/PC interface to S7ONLINE (STEP 7) on the cabled PN/IE adapter.
  3. Run the Accessible devices scan on that adapter.
  4. Empty scan — wrong adapter or security filtering; fix it on the PC side before touching the PLC.
  5. CPU listed with an empty address — assign the IP address and PROFINET name, MAC checked, from the addressing plan.
  6. CPU listed with an address — set the PC adapter to a unique static address in that subnet with the same mask.
  7. Go online. If the project's device configuration still carries an address from an earlier bench, correct it and download only then.

End state for each case: LEDs green plus a listed CPU plus one shared subnet plus the cabled access point equals a working connection. Every failure left in this article lives in exactly one of those four items, and the sequence above names which.

Questions asked

Does a STEP 7 Basic license stop TIA Portal from connecting to an S7-1200?

No. STEP 7 Basic is the edition that goes online with S7-1200 controllers; STEP 7 Professional is required only when the same installation must also program S7-300, S7-400 and S7-1500 families. A V13 Basic seat connects to the 1211 AC/DC/RLY, so when the connection fails the cause is the adapter, the subnet or discovery filtering, not the license.

Why does the Accessible devices scan list the CPU while Go online still fails?

The two paths use different rules. The scan works at the Ethernet frame level and identifies the CPU by MAC address, so it succeeds even when the CPU's IP field is empty or sits in another subnet. Go online needs real IP connectivity: PC and CPU in one subnet with unique addresses. If the scan shows an empty or foreign address, fix the addressing before touching the project.

Can a memory card load the first project when the Ethernet connection still fails?

Yes. A SIMATIC memory card carries the project and its initial configuration onto the CPU with no network path, which helps when commissioning is blocked on site. It fixes nothing on the PC side: the adapter choice, the subnet and any discovery filtering remain. After loading, rescan with Accessible devices, read the address the CPU now holds, put the PC in that subnet and go online through the cabled adapter.

Which IP address should I trust, the one in the project or the one the scan reports?

The one the scan reports. A project's device configuration is a plan that may have been saved with an address from another bench or another machine, while the scan and Online & diagnostics show what the CPU holds right now. Match the PC adapter and the project to the CPU's live address, correct the device configuration, and only then download it to the CPU.

Keep reading

  • How-to

    Write an S7-1200 heartbeat in ladder logic in TIA Portal

    Tie the light to a detector, not to the heartbeat level: time the on half with one TON and the off half with a second TON, both at three times the measured state time, and OR the two done bits into one communication-fault coil. With a PC heartbeat that changes once per second, PT is 3 s and the fault trips 3 s after the last change; add TCON and TDIAG supervision when the PLC owns the TCP connection.

    PLC programming

  • Explainer

    What STEP 7 is in a PLC project, and which one you need

    STEP 7 is the engineering software you use to program, configure, diagnose and download to SIMATIC PLCs — a workstation tool, not a part of the PLC itself. SIMATIC Manager, also called STEP 7 Classic, configures S7-300 and S7-400 CPUs; STEP 7 inside TIA Portal configures S7-1200 and S7-1500. Read the CPU family from the module label or the existing project, open the matching environment, and confirm the project's hardware configuration matches the installed CPU before you edit or download.

    PLC programming

  • Troubleshooting

    When a CODESYS TON works in structured text but not ladder

    The structured text routine counts because its four statements run in sequence inside one scan; the ladder version fails when the reset network clears Timer.Q before the addition samples it, or an unconditional reset restarts the timer every cycle. Put the call, the Q test, the addition and the reset of the same TON instance in one ladder network, left to right in that order, and it counts exactly one B per interval.

    PLC programming