<?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: MTRCKTSPS5744P Resolver Signal Reading in Model-Based Design Toolbox (MBDT)</title>
    <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MTRCKTSPS5744P-Resolver-Signal-Reading/m-p/922757#M3385</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/ext-rafael.barbosa@chassisbrakes.com"&gt;ext-rafael.barbosa@chassisbrakes.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please see the link&amp;nbsp;&lt;A _jive_internal="true" href="https://community.nxp.com/thread/506700"&gt;https://community.nxp.com/thread/506700&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This shall help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Abhishek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Jul 2019 07:30:06 GMT</pubDate>
    <dc:creator>abhishek_kumar1</dc:creator>
    <dc:date>2019-07-02T07:30:06Z</dc:date>
    <item>
      <title>MTRCKTSPS5744P Resolver Signal Reading</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MTRCKTSPS5744P-Resolver-Signal-Reading/m-p/922753#M3381</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using the motor control board&amp;nbsp;MTRCKTSPS5744P and trying&amp;nbsp;to get the resolver signals input in order to obtain the PMSM speed and position using Simulink with the model based design toolbox.&lt;BR /&gt;For resolver excitation signal, I am using the timer0 channel 5 as output with frequency of 10KHz (toggling between on and off).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem I am facing now is that I am getting some random value via the input for Resolve Sine (Adc0_AN0) and for Resolve Cosine (Adc1_AN0).&lt;/P&gt;&lt;P&gt;Probably it occurs due to the no sincronization between the output timer and the input ADC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding that, how to make the synchronization between the excitation signal and the ADC inputs in the MBD toolbox?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind Regards, Rafael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Jul 2019 07:21:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MTRCKTSPS5744P-Resolver-Signal-Reading/m-p/922753#M3381</guid>
      <dc:creator>ext-rafael_barb</dc:creator>
      <dc:date>2019-07-01T07:21:44Z</dc:date>
    </item>
    <item>
      <title>Re: MTRCKTSPS5744P Resolver Signal Reading</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MTRCKTSPS5744P-Resolver-Signal-Reading/m-p/922754#M3382</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/ext-rafael.barbosa@chassisbrakes.com"&gt;ext-rafael.barbosa@chassisbrakes.com&lt;/A&gt;‌,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So let me get this clear: Do you need to synchronize the eTimer output with the ADC?&amp;nbsp;&lt;/P&gt;&lt;P&gt;If your signal is constant at 10 kHz you can do this easier with the flexpwm. In this case ee provide an example with our toolbox: &lt;STRONG&gt;pwm_ctu_adc_mpc574xP.mdl&lt;/STRONG&gt;. You can also find an interesting discussion here&amp;nbsp;&lt;A _jive_internal="true" href="https://community.nxp.com/thread/488496"&gt;https://community.nxp.com/thread/488496&lt;/A&gt;.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, if you need the eTimer please firstly apply this patch:&amp;nbsp;&lt;A _jive_internal="true" href="https://community.nxp.com/message/1135102"&gt;https://community.nxp.com/message/1135102&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Waiting for your response,&lt;/P&gt;&lt;P&gt;Marius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Jul 2019 07:42:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MTRCKTSPS5744P-Resolver-Signal-Reading/m-p/922754#M3382</guid>
      <dc:creator>mariuslucianand</dc:creator>
      <dc:date>2019-07-01T07:42:53Z</dc:date>
    </item>
    <item>
      <title>Re: MTRCKTSPS5744P Resolver Signal Reading</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MTRCKTSPS5744P-Resolver-Signal-Reading/m-p/922755#M3383</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/mariuslucianandrei"&gt;mariuslucianandrei&lt;/A&gt;‌,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for the response.&lt;/P&gt;&lt;P&gt;Yes, the synchronization of&amp;nbsp;the timer and the ADC input with the flexpwm via CTU was performed, however the same issue continues to happen, which is the Resolver Sine and Resolver Cosine random data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After that, measuring the&amp;nbsp;MTRCKTSPS5744P with the oscilloscope, I could see that the timer output signal is not reaching the resolver. The measurement of "RES_REF" via Jumper J7 (connection pin 2 and pin 3) got a flat signal, instead of the proper timer output signal. Please see the picture bellow:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/90057i1FDE635E9EF28889/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just for effect of comparison, this is the measurement of the proper timer output (&lt;SPAN&gt;"RES_REF" signal) using the default Motor Control software example from NXP:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_3.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/90058iB85C658B32D04931/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_3.png" alt="pastedImage_3.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another factor is strange. I got the correct timer output when I try my model in the MPC5744P board (Package 144-LQFP).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any difference for the MBD toolbox implementation of the output timer excitation signal (Timer 0 channel 5) between the&amp;nbsp;MTRCKTSPS5744P package 257-BGA and the&amp;nbsp;MPC5744P package 144-LQFP?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind Regards, Rafael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Jul 2019 15:15:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MTRCKTSPS5744P-Resolver-Signal-Reading/m-p/922755#M3383</guid>
      <dc:creator>ext-rafael_barb</dc:creator>
      <dc:date>2019-07-01T15:15:53Z</dc:date>
    </item>
    <item>
      <title>Re: MTRCKTSPS5744P Resolver Signal Reading</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MTRCKTSPS5744P-Resolver-Signal-Reading/m-p/922756#M3384</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/ext-rafael.barbosa@chassisbrakes.com"&gt;ext-rafael.barbosa@chassisbrakes.com&lt;/A&gt;‌,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this related with the &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/abhishek.kumar@chassisbrakes.com"&gt;abhishek.kumar@chassisbrakes.com&lt;/A&gt;‌'s post here&amp;nbsp;&lt;A _jive_internal="true" href="https://community.nxp.com/thread/506700"&gt;https://community.nxp.com/thread/506700&lt;/A&gt;?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;Marius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jul 2019 07:23:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MTRCKTSPS5744P-Resolver-Signal-Reading/m-p/922756#M3384</guid>
      <dc:creator>mariuslucianand</dc:creator>
      <dc:date>2019-07-02T07:23:33Z</dc:date>
    </item>
    <item>
      <title>Re: MTRCKTSPS5744P Resolver Signal Reading</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MTRCKTSPS5744P-Resolver-Signal-Reading/m-p/922757#M3385</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/ext-rafael.barbosa@chassisbrakes.com"&gt;ext-rafael.barbosa@chassisbrakes.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please see the link&amp;nbsp;&lt;A _jive_internal="true" href="https://community.nxp.com/thread/506700"&gt;https://community.nxp.com/thread/506700&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This shall help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Abhishek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jul 2019 07:30:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MTRCKTSPS5744P-Resolver-Signal-Reading/m-p/922757#M3385</guid>
      <dc:creator>abhishek_kumar1</dc:creator>
      <dc:date>2019-07-02T07:30:06Z</dc:date>
    </item>
    <item>
      <title>Re: MTRCKTSPS5744P Resolver Signal Reading</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MTRCKTSPS5744P-Resolver-Signal-Reading/m-p/922758#M3386</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/mariuslucianandrei"&gt;mariuslucianandrei&lt;/A&gt;‌,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In fact the issue was related to the wrong pin selection.&lt;/P&gt;&lt;P&gt;Pack&amp;nbsp;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;144-LQFP -&amp;gt; Pin E13 for the eTimer0_Ch5&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Pack 257-BGA -&amp;gt; Pin C12&amp;nbsp;&lt;SPAN&gt;for the eTimer0_Ch5&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;SPAN&gt;Sorry about the mistake and thank you for the support.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;SPAN&gt;Rafael&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jul 2019 07:40:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MTRCKTSPS5744P-Resolver-Signal-Reading/m-p/922758#M3386</guid>
      <dc:creator>ext-rafael_barb</dc:creator>
      <dc:date>2019-07-02T07:40:22Z</dc:date>
    </item>
  </channel>
</rss>

