<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>LPC FAQsのトピックRe: How can I verify the configured CAN bitrate, using an oscilloscope?</title>
    <link>https://community.nxp.com/t5/LPC-FAQs/How-can-I-verify-the-configured-CAN-bitrate-using-an/m-p/2410966#M172</link>
    <description>&lt;P&gt;Your observation is spot on. While CAN's bit-stuffing mechanism guarantees an edge at least every 6 bit times, relying on arbitrary data bits for auto-baud or bit-rate measurement can be tricky due to varying payloads and stuffing intervals.&lt;/P&gt;</description>
    <pubDate>Thu, 03 Sep 2026 10:00:13 GMT</pubDate>
    <dc:creator>pomet30955</dc:creator>
    <dc:date>2026-09-03T10:00:13Z</dc:date>
    <item>
      <title>How can I verify the configured CAN bitrate, using an oscilloscope?</title>
      <link>https://community.nxp.com/t5/LPC-FAQs/How-can-I-verify-the-configured-CAN-bitrate-using-an/m-p/591051#M166</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CAN frames do not guarantee an edge appears for every bit. There can be sequence of up to five consecutive bits of the same logic level with no edges appearing in the waveform.&lt;BR /&gt;If the bus is operating normally and frames are being transferred without error then towards the end of the frame the acknowledge slot will be dominant (CAN_H is high and CAN_L is low). The bit immediately preceding (CRC delimiter) and following (acknowledge delimiter) will be recessive (CAN_H and CAN_L are almost the same voltage). Therefore it is always possible to measure the width of the acknowledge slot and determine the bit rate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt;"&gt;"FAQ contribution from Embedded Systems Academy, experts in CAN bus. For more information visit &lt;A href="http://www.esacademy.com"&gt;www.esacademy.com&lt;/A&gt;"&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Sep 2016 22:08:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-FAQs/How-can-I-verify-the-configured-CAN-bitrate-using-an/m-p/591051#M166</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-09-02T22:08:01Z</dc:date>
    </item>
    <item>
      <title>Re: How can I verify the configured CAN bitrate, using an oscilloscope?</title>
      <link>https://community.nxp.com/t5/LPC-FAQs/How-can-I-verify-the-configured-CAN-bitrate-using-an/m-p/2410966#M172</link>
      <description>&lt;P&gt;Your observation is spot on. While CAN's bit-stuffing mechanism guarantees an edge at least every 6 bit times, relying on arbitrary data bits for auto-baud or bit-rate measurement can be tricky due to varying payloads and stuffing intervals.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Sep 2026 10:00:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-FAQs/How-can-I-verify-the-configured-CAN-bitrate-using-an/m-p/2410966#M172</guid>
      <dc:creator>pomet30955</dc:creator>
      <dc:date>2026-09-03T10:00:13Z</dc:date>
    </item>
  </channel>
</rss>

