<?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>topic How do the error counters work? in LPC FAQs</title>
    <link>https://community.nxp.com/t5/LPC-FAQs/How-do-the-error-counters-work/m-p/590735#M155</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Every CAN controller has two error counters, one for transmit and one for receive. These error counters&lt;BR /&gt;are nearly always made available to read by firmware and when certain events happen there are usually&lt;BR /&gt;flags in registers and interrupts that can be triggered to notify firmware.&lt;BR /&gt;On every failed receive of a frame the receive counter is increased and on every successful receive it is&lt;BR /&gt;decreased. On every failed transmit of a frame the transmit counter is increased and on every successful&lt;BR /&gt;transmit it is decreased.&lt;BR /&gt;If either counter reaches 127 then the CAN controller enters “error passive” state. This means it cannot transmit error frames as potentially it has an internal problem, and that problem will be disrupting communications on the bus. Also, there will be a larger gap between consecutive sent messages to allow for other communication to happen and not “clog” the bus.&lt;BR /&gt;If the transmit error counter reaches 256 then the CAN controller enters “bus off” state. It cannot send frames onto the bus. Typically a complete re-initialization of the CAN controller is required to exit this state.&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 21:55:57 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-09-02T21:55:57Z</dc:date>
    <item>
      <title>How do the error counters work?</title>
      <link>https://community.nxp.com/t5/LPC-FAQs/How-do-the-error-counters-work/m-p/590735#M155</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Every CAN controller has two error counters, one for transmit and one for receive. These error counters&lt;BR /&gt;are nearly always made available to read by firmware and when certain events happen there are usually&lt;BR /&gt;flags in registers and interrupts that can be triggered to notify firmware.&lt;BR /&gt;On every failed receive of a frame the receive counter is increased and on every successful receive it is&lt;BR /&gt;decreased. On every failed transmit of a frame the transmit counter is increased and on every successful&lt;BR /&gt;transmit it is decreased.&lt;BR /&gt;If either counter reaches 127 then the CAN controller enters “error passive” state. This means it cannot transmit error frames as potentially it has an internal problem, and that problem will be disrupting communications on the bus. Also, there will be a larger gap between consecutive sent messages to allow for other communication to happen and not “clog” the bus.&lt;BR /&gt;If the transmit error counter reaches 256 then the CAN controller enters “bus off” state. It cannot send frames onto the bus. Typically a complete re-initialization of the CAN controller is required to exit this state.&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 21:55:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-FAQs/How-do-the-error-counters-work/m-p/590735#M155</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-09-02T21:55:57Z</dc:date>
    </item>
  </channel>
</rss>

