<?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 Re: Complementary mode in FTM PWM of MBDT in KV5x in Model-Based Design Toolbox (MBDT)</title>
    <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Complementary-mode-in-FTM-PWM-of-MBDT-in-KV5x/m-p/1376923#M6743</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/190527"&gt;@CauTran&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;You can use the same approach also on KV5x. The SDK API on KV5x is the same as on KV3x.&lt;/P&gt;
&lt;P&gt;The PWM mode selection should be done from the MCUX Configuration Tool (the .mex file of the model). When we released the toolbox, the mcux configuration tool had a limitation - complementary mode and deadtime insertion was not available for selection in the UI. I'm tracking the issue and it looks to be fixed - let me check it on my side and I will let you know on this thread.&lt;/P&gt;
&lt;P&gt;Meanwhile, you can try with the custom code block, same approach as on KV3x motor control example.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR,&lt;/P&gt;
&lt;P&gt;Alexandra&lt;/P&gt;</description>
    <pubDate>Thu, 25 Nov 2021 09:11:17 GMT</pubDate>
    <dc:creator>nxa11767</dc:creator>
    <dc:date>2021-11-25T09:11:17Z</dc:date>
    <item>
      <title>Complementary mode in FTM PWM of MBDT in KV5x</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Complementary-mode-in-FTM-PWM-of-MBDT-in-KV5x/m-p/1376016#M6740</link>
      <description>&lt;P&gt;Dear&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/61445"&gt;@nxp&lt;/a&gt;,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like to use FTM PWM in Complementary mode.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I see the example in KV3x about this ( scalar control example);&amp;nbsp;&lt;/P&gt;&lt;P&gt;But, I can not get anything that I want about complementary mode. 2 pwm channels is independent.&amp;nbsp;&lt;/P&gt;&lt;P&gt;How can I configure to get this one?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you so much.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Nov 2021 07:13:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Complementary-mode-in-FTM-PWM-of-MBDT-in-KV5x/m-p/1376016#M6740</guid>
      <dc:creator>CauTran</dc:creator>
      <dc:date>2021-11-24T07:13:13Z</dc:date>
    </item>
    <item>
      <title>Re: Complementary mode in FTM PWM of MBDT in KV5x</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Complementary-mode-in-FTM-PWM-of-MBDT-in-KV5x/m-p/1376923#M6743</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/190527"&gt;@CauTran&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;You can use the same approach also on KV5x. The SDK API on KV5x is the same as on KV3x.&lt;/P&gt;
&lt;P&gt;The PWM mode selection should be done from the MCUX Configuration Tool (the .mex file of the model). When we released the toolbox, the mcux configuration tool had a limitation - complementary mode and deadtime insertion was not available for selection in the UI. I'm tracking the issue and it looks to be fixed - let me check it on my side and I will let you know on this thread.&lt;/P&gt;
&lt;P&gt;Meanwhile, you can try with the custom code block, same approach as on KV3x motor control example.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR,&lt;/P&gt;
&lt;P&gt;Alexandra&lt;/P&gt;</description>
      <pubDate>Thu, 25 Nov 2021 09:11:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Complementary-mode-in-FTM-PWM-of-MBDT-in-KV5x/m-p/1376923#M6743</guid>
      <dc:creator>nxa11767</dc:creator>
      <dc:date>2021-11-25T09:11:17Z</dc:date>
    </item>
  </channel>
</rss>

