SIMATIC S7-1500 CPUs from firmware V2.0 carry an OPC UA server, reachable over every integrated Ethernet interface at opc.tcp on port 4840 by default. The same applies to the S7-1500F, T, C, and pro variants, ET 200SP CPUs, the S7-1500 software controller, and PLCSIM Advanced. Siemens' communication function manual describes what the server exposes: PLC tags and data block components enabled with "Accessible from HMI/OPC UA", server methods from firmware V2.5, and controller alarms through OPC UA Alarms and Conditions from firmware V2.9.
An operator on Fibric subscribes to the tags and alarms you enable, and proposes a write or a method call for your approval. Nothing reaches the CPU without a person saying yes, and each action leaves a receipt.
This is a reference listing. It documents what Fibric would read from SIMATIC S7-1500 and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.
Inputs
PLC tags and data block components enabled with "Accessible from HMI/OPC UA", read once or observed through subscriptions
Value changes delivered by the server at the CPU's minimum publishing and sampling intervals, without cyclic polling
Controller alarms as OPC UA Alarms and Conditions from firmware V2.9: ProDiag supervisions, system diagnostics, and Program_Alarm events
Server methods the PLC program implements as callable FB instances, available from firmware V2.5
Server interfaces built from companion specifications or user-defined OPC UA XML, with data types the CPU maps to OPC UA
Information about the server and the CPU published in the address space, including the data type of each tag
Proposed actions
Target capability: propose a value write to a PLC tag or DB component that has "Writable from HMI/OPC UA" set
Target capability: propose a call to a server method the PLC program exposes, with its input arguments shown for approval
Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.
What you can build
Turn an alarm flood into one ranked list
Subscribe to Alarms and Conditions events from the CPU, group bursts by source and cause, and propose which alarms deserve a person first.
An S7-1500 CPU at firmware V2.0 or later with its OPC UA server enabled under "OPC UA > Server"; it is off by default
A SIMATIC OPC UA S7-1500 runtime license sized to the CPU: small, medium, or large
Tags and DB components marked "Accessible from HMI/OPC UA", and "Writable from HMI/OPC UA" for anything the operator may propose to write
A user holding the "OPC UA server access" function right (firmware V3.1 and later), or an entry in the CPU's user management on earlier firmware
Client and server certificates the CPU trusts, and a correct date and time on the CPU so certificates validate
Authentication
OPC UA user name and password authentication over a secure channel (Sign or SignAndEncrypt, Basic256Sha256 where the client supports it), with X.509 certificates exchanged between the client and the CPU; guest (anonymous) access can be switched off.
Limits
The server is not reachable through CP or CM modules over the backplane bus; connect through the CPU's own Ethernet interfaces
Up to firmware V3.0 the CPU's user management holds a maximum of 21 users
Removing rights from one component of a structure or DB stops the whole structure being read or written in one pass
The maximum number of monitored items depends on the CPU, and the server sends notifications no faster than its minimum publishing interval
Access and pricing
Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.
No. For security the server is disabled until you activate it under "OPC UA > Server" in the CPU properties, confirm the security notes, set the runtime license, compile, and download the project. OPC UA clients have neither read nor write access until then.
Which security policies and authentication does the S7-1500 server offer?
Endpoints combine a Message Security Mode of None, Sign, or SignAndEncrypt with a Security Policy of None, Basic128Rsa15, Basic256, or Basic256Sha256. Users authenticate as guest (anonymous) or with user name and password, carried under a UserTokenPolicy that encrypts credentials even when the channel itself is unsecured.
How do I keep a tag out of the connector's reach?
Clear "Accessible from HMI/OPC UA" on the tag and the server removes it from its address space. Clear only "Writable from HMI/OPC UA" to leave it read-only. A central setting can also block an entire data block, overriding the per-component settings.
Ask about SIMATIC S7-1500
Ask about the capabilities and requirements in this listing.
This connector listing is developed, published, and supported by Fibric. It describes integration with SIMATIC S7-1500 through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy