<?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 MicrocontrollersのトピックRe: LPC11C24 CANOpen 2.0B</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC11C24-CANOpen-2-0B/m-p/733893#M29651</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;When you're using the internal CANOpen library, the value you pass for the ID is in the CAN_CANOPENCFG struct, and its an 8-bit value, so you wouldn't be able to set that bit.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It ended up being simple enough to add in support for extended IDs using separate message filters, so I did that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Will.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 19 Jan 2018 02:08:46 GMT</pubDate>
    <dc:creator>will_intelli</dc:creator>
    <dc:date>2018-01-19T02:08:46Z</dc:date>
    <item>
      <title>LPC11C24 CANOpen 2.0B</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC11C24-CANOpen-2-0B/m-p/733891#M29649</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using the CANOpen interface in the LPC11C24, it works fine for me, does anyone know if its supposed to work with CAN 2.0B extended IDs?&lt;/P&gt;&lt;P&gt;I'm not getting a response to an SDO request with an extended ID, but I don't know if its because I have it configured incorrectly.&lt;/P&gt;&lt;P&gt;The user manual doesn't mentioned anything about not supporting extended IDs in its "Differences to fully compliant CANOpen" section.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Will.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jan 2018 22:21:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC11C24-CANOpen-2-0B/m-p/733891#M29649</guid>
      <dc:creator>will_intelli</dc:creator>
      <dc:date>2018-01-17T22:21:53Z</dc:date>
    </item>
    <item>
      <title>Re: LPC11C24 CANOpen 2.0B</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC11C24-CANOpen-2-0B/m-p/733892#M29650</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Customer,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; CANopen is based on the LPC11C24 ROM CAN, the ROM can can support extended ID, so I think the CANopen also can support the extended ID.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; When you configure the CAN module, you need to configure the ID to extended ID.&lt;/P&gt;&lt;P&gt;/* control bits for CAN_MSG_OBJ.mode_id */&lt;BR /&gt;#define CAN_MSGOBJ_STD&amp;nbsp; 0x00000000UL&amp;nbsp;&amp;nbsp; /* CAN 2.0a 11-bit ID */&lt;BR /&gt;#define CAN_MSGOBJ_EXT&amp;nbsp; 0x20000000UL&amp;nbsp;&amp;nbsp; /* CAN 2.0b 29-bit ID */&lt;BR /&gt;#define CAN_MSGOBJ_DAT&amp;nbsp; 0x00000000UL&amp;nbsp;&amp;nbsp; /* data frame */&lt;BR /&gt;#define CAN_MSGOBJ_RTR&amp;nbsp; 0x40000000UL&amp;nbsp;&amp;nbsp; /* rtr frame */&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;msg_obj.mode_id= CAN_MSGOBJ_EXT +Extended ID.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; &lt;/STRONG&gt;&amp;nbsp;&amp;nbsp; You can try to configure the extended ID like the above code, then try your CANOpen again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Wish it helps you!&lt;/P&gt;&lt;P&gt;If you still have question about it, please kindly let me know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Kerry&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Jan 2018 06:12:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC11C24-CANOpen-2-0B/m-p/733892#M29650</guid>
      <dc:creator>kerryzhou</dc:creator>
      <dc:date>2018-01-18T06:12:55Z</dc:date>
    </item>
    <item>
      <title>Re: LPC11C24 CANOpen 2.0B</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC11C24-CANOpen-2-0B/m-p/733893#M29651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;When you're using the internal CANOpen library, the value you pass for the ID is in the CAN_CANOPENCFG struct, and its an 8-bit value, so you wouldn't be able to set that bit.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It ended up being simple enough to add in support for extended IDs using separate message filters, so I did that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Will.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jan 2018 02:08:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC11C24-CANOpen-2-0B/m-p/733893#M29651</guid>
      <dc:creator>will_intelli</dc:creator>
      <dc:date>2018-01-19T02:08:46Z</dc:date>
    </item>
  </channel>
</rss>

