<?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>Kinetis MicrocontrollersのトピックRe: FreescaleCupShieldHelp</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FreescaleCupShieldHelp/m-p/512371#M32435</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I am wondering if one ever thought the pinning of the TFC-Shield can be a bit inconvenient. When you wanna add some other sensors, then the camera clock blocks the UART1/I2C1 and the hall sensors block the UART0. So for example when you wanna add the gyro and magnetometer of the BRKT-STBC-AGM01 the you have a problem. Moreover, if you wanna work with Simulink then UART0 is used by the external mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;So I was wandering if anybody has the same issue and if there will be a new version of the TFC-Shield available or if anyone is interested to design an updated version. We would be very interested to add a gyro and magnetometer as well, since we design an IMU for the car. I have attached a pic which provides information about our desired pinning.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;BR,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gehard&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Pinning_TFC_Shield.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/8578iC80E020891698012/image-size/large?v=v2&amp;amp;px=999" role="button" title="Pinning_TFC_Shield.png" alt="Pinning_TFC_Shield.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 Nov 2016 11:51:09 GMT</pubDate>
    <dc:creator>gerhardfreudent</dc:creator>
    <dc:date>2016-11-21T11:51:09Z</dc:date>
    <item>
      <title>FreescaleCupShieldHelp</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FreescaleCupShieldHelp/m-p/512369#M32433</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, I was wondering if and how to brake the freescale cup car. Is there some sort of "eddy current brake" or "short brake" capabilities? If so, what code do I need to use to brake the car. I have gone over the tutorial for the freecale cup car and there is nothing about braking (&lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-93914#jive_content_id_Code_Examples" title="https://community.freescale.com/docs/DOC-93914#jive_content_id_Code_Examples"&gt;https://community.freescale.com/docs/DOC-93914#jive_content_id_Code_Examples&lt;/A&gt; ). Any help would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Tim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Mar 2016 04:32:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FreescaleCupShieldHelp/m-p/512369#M32433</guid>
      <dc:creator>tim_amish</dc:creator>
      <dc:date>2016-03-30T04:32:53Z</dc:date>
    </item>
    <item>
      <title>Re: FreescaleCupShieldHelp</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FreescaleCupShieldHelp/m-p/512370#M32434</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tim,&lt;/P&gt;&lt;P&gt;the simplest way to brake the DC brushed motor is to load them by driver (full-bridge MC33887). Simply short circuit two DC motor lines by switch on both bottom full-bridge power MOSFETs. Simply set both outputs to zero.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think it will help you.&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Stano.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Mar 2016 07:21:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FreescaleCupShieldHelp/m-p/512370#M32434</guid>
      <dc:creator>Stano</dc:creator>
      <dc:date>2016-03-30T07:21:04Z</dc:date>
    </item>
    <item>
      <title>Re: FreescaleCupShieldHelp</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FreescaleCupShieldHelp/m-p/512371#M32435</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I am wondering if one ever thought the pinning of the TFC-Shield can be a bit inconvenient. When you wanna add some other sensors, then the camera clock blocks the UART1/I2C1 and the hall sensors block the UART0. So for example when you wanna add the gyro and magnetometer of the BRKT-STBC-AGM01 the you have a problem. Moreover, if you wanna work with Simulink then UART0 is used by the external mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;So I was wandering if anybody has the same issue and if there will be a new version of the TFC-Shield available or if anyone is interested to design an updated version. We would be very interested to add a gyro and magnetometer as well, since we design an IMU for the car. I have attached a pic which provides information about our desired pinning.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;BR,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gehard&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Pinning_TFC_Shield.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/8578iC80E020891698012/image-size/large?v=v2&amp;amp;px=999" role="button" title="Pinning_TFC_Shield.png" alt="Pinning_TFC_Shield.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Nov 2016 11:51:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FreescaleCupShieldHelp/m-p/512371#M32435</guid>
      <dc:creator>gerhardfreudent</dc:creator>
      <dc:date>2016-11-21T11:51:09Z</dc:date>
    </item>
  </channel>
</rss>

