Every LonTalk packet carries both a source and a destination address, and both live in the same header. There is no separate layer-2 addressing underneath — the standard folds routing and naming into one address field. Get the structure of that field straight and most of the network’s limits, quirks, and failure modes stop being mysterious. This is… Read More: LonTalk Addressing: Domain, Subnet, Node, Group and Neuron ID »
Walk into a plant room and you will see three names on the same equipment. LonWorks on the panel label. LonTalk in the manual. ISO/IEC 14908 in the submittal package. They are not three protocols. LonWorks is the platform — chips, transceivers, tools, devices. LonTalk is the protocol those devices speak. ISO/IEC 14908 is the published standard that… Read More: LonWorks Protocol: LonTalk, ISO/IEC 14908, and How the Network Actually… »
Above the tool Two holding registers come back as 17142 and 58982. The vendor manual says the value is a float. It does not say in which order the two registers go. That is the whole problem. The Modbus specification defines a 16-bit register and nothing larger, so every device that reports a 32-bit float had to invent… Read More: Modbus Float Converter — 32-Bit Register Word Order Tool »
Above the tool An EDS file is a plain text device description. Your configuration tool reads it, builds a device profile, and hides everything behind a wizard. When the device does not come online, you need to see what is actually in that file. This viewer opens both kinds of EDS you run into on an industrial job:… Read More: EDS File Viewer — Open CANopen & EtherNet/IP EDS Online »
Every CANopen device carries an object dictionary, and the SDO is the only way to reach into it from outside. Read a serial number, change a gear ratio, remap a PDO, save the configuration to flash — all of it is SDO traffic. Unlike a PDO, an SDO frame carries its own address. The first byte says what… Read More: CANopen SDO Explained: Expedited, Segmented, Block »
A PDO is eight bytes of raw process data with no protocol overhead — no index, no sub-index, no length field, nothing that tells you what is inside. The bytes arrive and the consumer is expected to already know what they mean. That agreement is the PDO mapping. It lives in the object dictionary on both sides, it… Read More: CANopen PDO Mapping: TPDO, RPDO and Transmission Types »
Paste a CAN trace. Each line becomes a decoded message: the COB-ID split into function code and node ID, then the service behind it read out field by field. It takes candump output, PCAN text, or plain identifier data lines. Several lines at once, in order, so a whole startup sequence decodes in one pass. Message input One… Read More: CANopen Message Decoder — SDO, PDO, EMCY and NMT Online »
Paste the bytes and the decoder splits them into fields: packet type, flags, remaining length, then whatever that packet type carries. Topic names, QoS, packet identifiers, MQTT 5 properties, reason codes and the payload. It reads a whole TCP stream, not one packet. Paste a capture that runs from CONNECT to DISCONNECT and you get every packet in… Read More: MQTT Packet Decoder — Decode MQTT 3.1.1 and 5.0 Hex… »
Most fieldbuses solve the problem of moving a lot of data between intelligent devices. AS-Interface solves a different one: getting a few bits to and from hundreds of dumb devices, cheaply, without a terminal strip the size of a door. A proximity switch has one bit of information. A solenoid valve needs one bit. Wiring each one back… Read More: AS-Interface (AS-i) Explained: The Yellow Cable Bus »
Drop an SCD, CID, ICD, IID, SSD or SED file on the box above. The viewer reads it in your browser and lays out what is inside: the IEDs, the logical devices, every GOOSE and sampled value publisher with its MAC address and APPID, who subscribes to what, and the data sets behind each control block. The file… Read More: IEC 61850 SCL File Viewer — Open SCD, CID, ICD… »