A data set says what an IED can send. A report control block says when, why, how much detail, and to whom. Every reporting problem in a substation — missing events after a comms drop, a client that never receives anything, reports flooding the station bus during a fault — traces back to an RCB attribute somebody set… Read More: IEC 61850 Report Control Blocks: BRCB and URCB Explained »
TASE.2 defines its functionality as operations and actions on objects, then maps each one onto an MMS service. That mapping is the Rosetta Stone of ICCP work: vendor documentation speaks TASE.2 (“Start Transfer”), the wire speaks MMS (“Write”), and moving between the two is half of every troubleshooting session. This reference lays out the complete map in both… Read More: ICCP Operations and Services: The Complete TASE.2 Map »
Every value an ICCP link carries is an instance of an object model from IEC 60870-6-802:2014. When two control centers negotiate a bilateral agreement, a large part of the technical work is agreeing, point by point, which of these models and which type variant each point uses — because the type determines exactly what crosses the wire: value… Read More: ICCP Object Models: Indication Points and Control Points »
On a Modbus serial line, every byte you send is wrapped in a few extra bits before it hits the wire. Those extra bits — the start bit, an optional parity bit, and one or two stop bits — make up the character format. Get them wrong on one device and it won’t talk to the rest of… Read More: Modbus Parity and Character Format »
Device control is where ICCP stops being a data feed and becomes an operational tool — and a liability if misunderstood. Conformance block 5 lets one control center trip breakers, raise taps, and write setpoints in another organization’s network. The protocol wraps that power in the select-before-operate pattern every operations engineer knows from local SCADA, adapted for the… Read More: ICCP Device Control: SBO Select and Operate Explained »
An ICCP link is a standing, months-long connection between two organizations, carrying real-time grid data and — where block 5 is enabled — live control of primary equipment. It crosses an organizational boundary by definition: the other end is somebody else’s network, somebody else’s patching discipline, somebody else’s incident. That makes it one of the most security-relevant connections… Read More: ICCP Security: Hardening TASE.2 Links With IEC 62351 »
A transfer set is the engine of an ICCP link. Data values are what you exchange; data sets group them; but the transfer set decides everything about the actual flow — when reports are sent, what they contain, how bursts are handled, and whether the client must acknowledge. Once transfer sets are enabled, the link runs itself: the… Read More: ICCP Transfer Sets: How TASE.2 Reporting Really Works »
The first time you capture ICCP traffic in Wireshark, the protocol column reads like an archaeology dig: TCP, then TPKT, then COTP, then Session, Presentation, ACSE, MMS. Seven layers deep before a single power system value appears. This article explains what each layer does, why the stack looks like this, and — since this is where commissioning time… Read More: The ICCP Protocol Stack: OSI Over TCP/IP Explained »
Every ICCP datasheet says the same thing: “supports blocks 1, 2, and 5” or some variation. Conformance blocks are how TASE.2 capability is packaged, sold, tested, and written into bilateral agreements. They’re also where datasheets, the wire protocol, and the standard itself quietly disagree. This article decodes each block, explains why nearly half of them were deleted from… Read More: ICCP Conformance Blocks: What Servers Actually Support »
Every ICCP link runs on a pair of bilateral tables. They decide who may connect, what they may see, and what they may do. They are also the single most common reason a new ICCP link doesn’t work on day one — not the protocol, not the network, the tables. This article covers what a bilateral table is,… Read More: ICCP Bilateral Tables Explained (TASE.2 Access Control) »