<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nmea2000 on toorun.dev</title><link>https://toorun.dev/tags/nmea2000/</link><description>Recent content in nmea2000 on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 29 May 2025 12:30:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/nmea2000/index.xml" rel="self" type="application/rss+xml"/><item><title>NMEA 2000 Implementation: Address Claim, Heartbeat, and Alarm Messages</title><link>https://toorun.dev/posts/nmea-2000-implementation-address-heartbeat-alarm/</link><pubDate>Thu, 29 May 2025 12:30:00 +0000</pubDate><guid>https://toorun.dev/posts/nmea-2000-implementation-address-heartbeat-alarm/</guid><description>This is not a full specification reference. It is a practical note to remember how NMEA 2000 works in real systems, what matters during implementation, and what I learned while working with it.
What NMEA 2000 is NMEA 2000 is a communication protocol used in distributed systems over CAN bus.
At the lowest level, it is standard CAN:
250 kbps bus multi-node shared network On top of that, it defines:</description></item></channel></rss>