OPC UA uses TCP port 4840 by default. This single port carries everything OPC UA does — discovery, session establishment, reading tags, writing values, subscriptions, method calls, and historical data access. Unlike OPC Classic (which used DCOM with dynamic port allocation and was a firewall nightmare), OPC UA uses one well-known port that works cleanly through NAT, proxies,… Read More »
Every ASDU (Application Service Data Unit) in IEC 60870-5-104 contains a Type ID — a single byte that defines what kind of data the message carries. It tells the receiving station whether the message contains a single-point indication, a measured value, a command, a counter, or a system message. The Type ID is the first byte of every… Read More »
Every CIP device — whether it is an Allen-Bradley PLC, a variable frequency drive, a remote I/O module, or a safety controller — organizes its data using the same object model. Understanding this model is the key to configuring, programming, and troubleshooting any CIP-based device. CIP (Common Industrial Protocol) does not use register maps like Modbus. Instead, it… Read More »
PROFINET is one protocol — not three. But it comes in four conformance classes that define what a device can do, how fast it communicates, and what network infrastructure it needs. Engineers often confuse PROFINET RT, PROFINET IRT, and PROFINET IO as separate protocols. They are not. They are all part of PROFINET IO, defined in IEC 61158… Read More »
Every PROFINET device comes with a GSD file. Without it, your PLC does not know the device exists. It cannot configure modules, exchange I/O data, or read diagnostics. GSD stands for General Station Description. In PROFINET, GSD files are written in XML format. The language used is called GSDML — General Station Description Markup Language. The file extension… Read More »
Every piece of data in an IEC 61850 system lives inside a logical node. A circuit breaker position is inside XCBR. An overcurrent trip signal is inside PTOC. A voltage measurement is inside MMXU. A GOOSE control block is inside LLN0. Logical nodes are the building blocks of the IEC 61850 data model. They represent functions — not… Read More »
Every Modbus device comes with a register map. It is usually a table in the user manual or a separate PDF that lists all the data points the device makes available — voltages, currents, setpoints, alarms, status bits, and configuration parameters. Reading a register map sounds simple. But it is one of the most common sources of errors… Read More »
OPC UA Pub/Sub is a communication pattern within the OPC UA standard that allows data to flow from publishers to subscribers without requiring a direct connection between them. A publisher sends data to a message broker or network bus. Any number of subscribers receive that data independently. No handshake. No dedicated session. No request-response cycle. This is fundamentally… Read More »
Every Modbus message contains a function code. It is a single byte that tells the slave device what operation to perform — read coils, write registers, or diagnose communication. The Modbus specification defines multiple function codes, but in practice you will use about six of them for 95% of your tasks. The rest are either rarely implemented, vendor-specific,… Read More »
If you work with IEC 61850, you will deal with SCL files. They are the standard way to describe IED capabilities, substation configurations, and communication parameters. But the first thing that confuses most engineers is this: there are six different SCL file types. ICD, SSD, SCD, IID, CID, SED — each with a different purpose, created by a… Read More »