Connecting Siemens PLCs Without TIA Portal: A Practical Guide
A system integrator in Belgium spent €4,200 on a TIA Portal license to monitor 12 S7-1200 PLCs on a conveyor line. He did not need to program the PLCs. He did not need to change the ladder logic. He did not need to configure hardware, modify firmware, or touch a single function block. He needed to read a temperature value from Data Block 1 every 5 seconds and display it on a dashboard. The €4,200 was wasted on a tool designed for a job he was not doing.
This guide explains when you need TIA Portal, when you do not, and how to connect to Siemens S7-1200 and S7-1500 PLCs for monitoring and data collection without it.
What TIA Portal Actually Is
TIA Portal (Totally Integrated Automation Portal) is Siemens' engineering framework. It is an integrated development environment for programming Siemens PLCs, configuring HMI panels, setting up drives, and commissioning automation systems. It is a powerful tool — and a Windows-only application that costs between $2,000 and $10,000+ depending on the license tier.
TIA Portal is designed for automation engineers who write PLC programs. It provides ladder logic and structured text editors, hardware configuration tools, network topology planners, firmware management, and a simulator for testing PLC code without physical hardware. For a controls engineer building a machine from scratch, TIA Portal is essential — see our guide to PLC programming with ladder logic for why that specialized tooling matters. For someone who wants to monitor that machine's data, it is overkill, overpriced, and often impossible to justify.
The Misconception: You Need TIA Portal to Talk to Siemens PLCs
This misconception persists for a reason. Siemens' marketing positions TIA Portal as the way to work with Siemens PLCs. Their documentation assumes you own it. Their forums answer questions in the context of TIA Portal workflows. The ecosystem reinforces the assumption that the programming tool and the monitoring tool are the same thing.
They are not. Reading data from a Siemens PLC requires the S7 communication protocol — not TIA Portal. The S7 protocol is an open specification that anyone can implement. It works over TCP/IP on port 102, and it provides direct read/write access to the memory areas of a Siemens PLC: data blocks, inputs, outputs, markers, timers, and counters.
The PLC does not know or care whether the client connecting on port 102 is TIA Portal, an HMI panel, or a third-party SCADA system. It responds to the same S7 protocol requests regardless.
How the S7 Protocol Works
The S7 protocol is a client-server protocol operating over TCP on port 102. A client (SCADA, HMI, monitoring tool) connects to the PLC, sends read or write requests, and receives responses. The protocol uses a compact binary format optimized for low overhead on industrial networks.
Memory Areas You Can Access
- Data Blocks (DB) — User-defined data structures. The most common target for monitoring. DB1, DB10, DB100, etc. Each DB contains variables organized by offset.
- Inputs (I) — Physical input modules. Each byte represents 8 digital inputs. Updated by the PLC scan cycle.
- Outputs (Q) — Physical output modules. Written by the PLC program or (carefully) by external systems.
- Markers (M) — Internal memory flags. General-purpose bits and bytes used in ladder logic.
- Timers (T) and Counters (C) — Timer and counter values used in PLC programs.
Steps to Connect from a SCADA System
- Enable PUT/GET communication on the PLC. In TIA Portal, under the CPU properties, in "Protection & Security" → "Connection mechanisms," check "Permit access with PUT/GET communication from remote partner." This is a one-time configuration step. Once enabled, the PLC accepts S7 read requests from any client.
- Know the PLC's IP address. S7-1200 and S7-1500 PLCs have Ethernet ports with configurable IP addresses. Find this in the network configuration or ask the controls engineer.
- Know the rack and slot numbers. Typically rack 0, slot 1 for S7-1200; rack 0, slot 1 (or slot 2 for some configurations) for S7-1500.
- Know the data block numbers and offsets. The controls engineer who programmed the PLC has a symbol table or tag export showing which variables live at which DB offsets.
- Use an S7 client to connect. Voltrus, Snap7, libnodave, or any S7-compatible client library can establish the connection and read data.
Voltrus vs TIA Portal for S7 Connectivity
When You DO Need TIA Portal
This is not an argument that TIA Portal is unnecessary. It is necessary for specific jobs:
- Writing or modifying PLC programs — ladder logic, structured text, function blocks
- Hardware configuration — adding I/O modules, configuring communication interfaces
- Firmware updates — updating the PLC operating system
- Network topology configuration — PROFINET device naming and topology
- Safety program configuration — Siemens safety-integrated functions
- Initial commissioning — first-time setup of a new PLC
If your job involves any of these tasks, you need TIA Portal. Budget accordingly. But if your job involves reading data from an already-commissioned PLC and displaying it on a dashboard — you do not need TIA Portal. You need an S7 protocol client.
How Voltrus Connects to Siemens PLCs
Voltrus includes a built-in S7 protocol driver. No middleware. No OPC server. No protocol gateway. Configure the connection in three fields:
Connection Configuration
- IP Address — The PLC's Ethernet IP (e.g., 192.168.0.10)
- Rack — Typically 0
- Slot — Typically 1 for S7-1200, 1 or 2 for S7-1500
Data Block Mapping
Once connected, Voltrus reads the available data blocks and presents them in a visual browser. You see DB1, DB10, DB100 — each with their variables, data types, and current values. Drag any variable onto a dashboard widget. The mapping is visual, not code-based.
For integrators who need to monitor multiple PLCs, Voltrus supports multiple simultaneous S7 connections. Monitor an S7-1200 on the packaging line and an S7-1500 on the main process line from the same dashboard.
Data Types Supported
BOOL, BYTE, WORD, DWORD, INT, DINT, REAL (float), STRING, CHAR, and arrays of each. Voltrus handles the byte-swapping and type conversion automatically — no need to manually decode Siemens' big-endian byte order.
Frequently Asked Questions
Can I read data from a Siemens S7 PLC without TIA Portal?
Yes. Reading data from a Siemens PLC requires the S7 communication protocol, not TIA Portal. The S7 protocol works over TCP/IP on port 102 and provides direct read/write access to data blocks, inputs, outputs, markers, timers, and counters. Any S7-compatible client — including Voltrus, Snap7, or libnodave — can connect to S7-1200 and S7-1500 PLCs without TIA Portal installed.
What do I need to connect to a Siemens S7-1200 or S7-1500 PLC?
You need three things: the PLC's IP address on the network, the rack and slot numbers (typically rack 0, slot 1 for S7-1200 and rack 0, slot 1 or 2 for S7-1500), and PUT/GET communication enabled on the PLC. PUT/GET is a one-time configuration step done through TIA Portal in the CPU properties under Protection and Security. After that, any S7 client can read data without TIA Portal.
Does Voltrus need TIA Portal to connect to Siemens PLCs?
No. Voltrus includes a built-in S7 protocol driver that connects directly to Siemens S7-1200 and S7-1500 PLCs over Ethernet. You configure the IP address, rack, and slot in Voltrus and it reads data blocks directly. The only time TIA Portal is needed is the one-time step of enabling PUT/GET communication on the PLC, which a controls engineer typically handles during initial commissioning.
When do I actually need TIA Portal?
You need TIA Portal for writing or modifying PLC programs (ladder logic, structured text, function blocks), hardware configuration, firmware updates, PROFINET topology configuration, safety program configuration, and initial PLC commissioning. If your job is only reading data from an already-commissioned PLC and displaying it on a dashboard, TIA Portal is not required.
Monitor Siemens PLCs Without TIA Portal
Voltrus includes a built-in S7 protocol driver for direct PLC connection. No middleware. No programming IDE. Just data — from the PLC to your dashboard.
Explore Voltrus