Putting LonWorks on an IP network sounds like the easy part. The protocol doesn’t change, and Ethernet is already in the building. Then a device stops forwarding and nothing in the LonWorks tooling explains why. ISO/IEC 14908-4 doesn’t rewrite LonTalk into a different application protocol. It transports LonTalk packets over IP using a mechanism it calls CNP/IP. But… Read More: LonTalk over IP (IP-852): Setup and Troubleshooting »
Most comparisons of these two treat them as rivals picking a fight over the same job. That framing gets the engineering wrong, and it gets one important fact wrong too. BACnet defines LonTalk as one of its own data link layers. Clause 11 of the BACnet standard specifies how BACnet messages ride on the LonTalk protocol. They are… Read More: LonWorks vs BACnet: How the Two Data Models Differ »
The power line channel is the one that fails for reasons nobody wrote down. A surge arrester goes in on the same board. A lighting retrofit lands on the same circuit. Both are perfectly good electrical work, and both can take the network down. ISO/IEC 14908-3 is unusually direct about this. It declines to specify the medium at… Read More: LonWorks Power Line: The 125-140 kHz Channel Explained »
Free topology is the reason people put up with LonWorks wiring. Bus, star, loop, or any mix of them, on one pair, with one termination you can put anywhere. No daisy-chain discipline, no polarity to get right. It isn’t free of rules. It has distance limits, a termination that has to be the right value, and a power… Read More: LonWorks Twisted Pair Wiring: Distances and Link Power »
A Modbus register is sixteen bits and nothing else. What those bits mean lives in a document somebody emailed you. A LonWorks network variable carries its own type. Two devices that agree on the type exchange a temperature without anyone deciding whether it’s tenths of a degree. That difference is the reason the protocol exists, and it’s also… Read More: LonWorks Network Variables: Selectors, Bindings and Polls »
Pick the wrong service type and the network still works — until it doesn’t. Under light load everything delivers. Under load, the acknowledged multicast you specified starts eating the channel it needs, and the symptom looks like a hardware fault. ISO/IEC 14908-1 gives you four services. This is what each one actually does on the wire, when to… Read More: LonTalk Service Types: Which One to Use and Why »
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… »
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 »