J1939 isn’t one standard. It’s a family of about a dozen, each covering a different layer, and the reason most J1939 confusion exists is that people read one of them and assume it describes the whole network. The document that ties them together is SAE J1939-1. It doesn’t specify messages or bit timings — it specifies which J1939… Read More: SAE J1939 Explained: Network Architecture and Standards »
Most CAN faults are wiring faults. Not protocol bugs, not controller settings — a missing terminator, a stub that’s too long, a shield grounded at both ends, a connector that passes a continuity test but fails under vibration. The frustrating part is that CAN degrades gracefully enough to hide these. A network with one terminator instead of two… Read More: CAN Bus Wiring and Termination: The Complete Guide »
CAN is two wires, no master, no addresses, and no collisions — despite every node being free to start talking whenever the bus is quiet. That combination is why a protocol designed for 1980s vehicles now runs machine automation, off-highway equipment, medical devices, and industrial drives. The trick is that CAN doesn’t address messages to nodes. It labels… Read More: CAN Bus Protocol Explained: Frames, Arbitration, Errors »
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 »
The confusion is understandable. Both protocols are built on MMS. Both use the same OSI upper-layer stack. Both listen on TCP port 102 and 3782. Both show up in Wireshark labeled “MMS,” decoded by the same dissector. Vendors often implement them with shared library code. And yet they solve completely different problems, and no project ever chooses between… Read More: ICCP vs IEC 61850: Two MMS Protocols, Two Jobs »
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 »
Ask ten engineers what a dashboard is and you get ten answers. One means a Grafana page showing motor current. One means a trend client pulled from the historian. One means a Power BI report the plant manager opens on Monday. They are not the same product. They do not sit in the same place on the network.… Read More: Industrial Dashboard Software: 6 Tools Compared »
Ask ten engineers to name the most popular SCADA systems and you get ten different lists. That is not because anyone is wrong. It is because “popular” depends on which room you are standing in. Walk into an automotive plant and you will see FactoryTalk View SE on the wall. Walk into a distribution control center two kilometers… Read More: Most Popular SCADA Systems and Where Each One Fits »
SCADA as a Service promises lower infrastructure costs, automatic software updates, and easier scalability. But unlike enterprise software, utility control systems cannot simply move everything into the cloud. Real-time control, cybersecurity, regulatory compliance, and availability requirements make SCADA fundamentally different from a CRM or ERP platform. Software as a Service means the vendor runs the software in its… Read More: SCADA as a Service Explained: Cloud SCADA for Utilities »