<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Debugging on Draft</title><link>https://draft.caps.is/tags/debugging/</link><description>Recent content in Debugging on Draft</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 10 May 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://draft.caps.is/tags/debugging/index.xml" rel="self" type="application/rss+xml"/><item><title>The CAN capture that lied</title><link>https://draft.caps.is/posts/can-capture-that-lied/</link><pubDate>Sun, 10 May 2026 00:00:00 +0200</pubDate><guid>https://draft.caps.is/posts/can-capture-that-lied/</guid><description>&lt;p&gt;The OVMS module talks to the car over two buses. CAN2 handles powertrain — BMS, gear selector, VIN. CAN3 handles the body network — speed, GPS, clima, locks. The J533 gateway sits between them and bridges selected frames. Not all traffic. Specific IDs it&amp;rsquo;s programmed to forward.&lt;/p&gt;
&lt;p&gt;Early captures used a script with a bus-labeling bug. Powertrain frames from CAN2 were written to the capture file with bus tag &lt;code&gt;3&lt;/code&gt; — the body network tag. In the logs, frames like &lt;code&gt;0x131&lt;/code&gt; (SoC), &lt;code&gt;0x187&lt;/code&gt; (gear selector), and &lt;code&gt;0x191&lt;/code&gt; (BMS current) appeared to be arriving on CAN3.&lt;/p&gt;</description></item></channel></rss>