<?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>S32Kのトピックusing MCSPTE1AK344_BLDC_6step_sensorless_II without GD3000 driver</title>
    <link>https://community.nxp.com/t5/S32K/using-MCSPTE1AK344-BLDC-6step-sensorless-II-without-GD3000/m-p/1952728#M40849</link>
    <description>&lt;P&gt;We are using the NXP motor controller code&amp;nbsp; (&amp;nbsp;MCSPTE1AK344_BLDC_6step_sensorless_II ) and tested it on the NXP eval board which works well. We are now going to test the firmware on our own motor driver with same pinout as NXP eval board except that we are not using SPI based GD3000 driver.And instead, we use three regular non-spi drivers to drive the FETs. Can you let us know what&amp;nbsp; &amp;nbsp;sections in the code need to be changed to remove the GD3000 part and still use the NXP code? As mentioned, everything else is the same! Appreciate your urgent response.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 11 Sep 2024 22:26:06 GMT</pubDate>
    <dc:creator>Eduardo2000</dc:creator>
    <dc:date>2024-09-11T22:26:06Z</dc:date>
    <item>
      <title>using MCSPTE1AK344_BLDC_6step_sensorless_II without GD3000 driver</title>
      <link>https://community.nxp.com/t5/S32K/using-MCSPTE1AK344-BLDC-6step-sensorless-II-without-GD3000/m-p/1952728#M40849</link>
      <description>&lt;P&gt;We are using the NXP motor controller code&amp;nbsp; (&amp;nbsp;MCSPTE1AK344_BLDC_6step_sensorless_II ) and tested it on the NXP eval board which works well. We are now going to test the firmware on our own motor driver with same pinout as NXP eval board except that we are not using SPI based GD3000 driver.And instead, we use three regular non-spi drivers to drive the FETs. Can you let us know what&amp;nbsp; &amp;nbsp;sections in the code need to be changed to remove the GD3000 part and still use the NXP code? As mentioned, everything else is the same! Appreciate your urgent response.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2024 22:26:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/using-MCSPTE1AK344-BLDC-6step-sensorless-II-without-GD3000/m-p/1952728#M40849</guid>
      <dc:creator>Eduardo2000</dc:creator>
      <dc:date>2024-09-11T22:26:06Z</dc:date>
    </item>
    <item>
      <title>Re: using MCSPTE1AK344_BLDC_6step_sensorless_II without GD3000 driver</title>
      <link>https://community.nxp.com/t5/S32K/using-MCSPTE1AK344-BLDC-6step-sensorless-II-without-GD3000/m-p/1955817#M41020</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Thank you so much for your interest in our products and for using our community.&lt;/P&gt;
&lt;P&gt;We do not have an app note for &lt;EM&gt;Six-Step Commutation Control&lt;/EM&gt; like we have for &lt;EM&gt;Field-Oriented Control&lt;/EM&gt;, nor do we have an example for a non-SPI gate driver. An apology for the inconvenience.&lt;/P&gt;
&lt;P&gt;However you could refer to &lt;A href="https://community.nxp.com/t5/S32K-Knowledge-Base/S32K344-Six-step-commutation-control/ta-p/1804572" target="_blank" rel="noopener"&gt;S32K344 - Six-step commutation control&lt;/A&gt; and also to &lt;EM&gt;4. Software implementation on the S32K344&lt;/EM&gt; section from &lt;A href="https://www.nxp.com/webapp/Download?colCode=AN13767" target="_blank" rel="noopener"&gt;AN13767&lt;/A&gt;, which is a demo with similar Software Architecture.&lt;/P&gt;
&lt;P&gt;Hope it helps you.&lt;/P&gt;
&lt;P&gt;Have a nice day!&lt;/P&gt;</description>
      <pubDate>Tue, 17 Sep 2024 18:27:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/using-MCSPTE1AK344-BLDC-6step-sensorless-II-without-GD3000/m-p/1955817#M41020</guid>
      <dc:creator>_Leo_</dc:creator>
      <dc:date>2024-09-17T18:27:51Z</dc:date>
    </item>
  </channel>
</rss>

