<?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: mpc5746 Etpu crank errors in MPC5xxx</title>
    <link>https://community.nxp.com/t5/MPC5xxx/mpc5746-Etpu-crank-errors/m-p/1598694#M22863</link>
    <description>&lt;P&gt;Thanks for the quick reply !&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ETPU is able to synchronize. But when running, a hick up appears with the fault code 4 ( timeout ). When the engine is running steady state on a certain load. The timeout error will stay away for aproximatly 10 minutes before it comes back. The signal is verry clean and doesn't contain any spikes.&lt;/P&gt;&lt;P&gt;The window ratios are taken from the Excel sheet. But changing them won't make any difference.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Win ratio normal: 0.05&lt;BR /&gt;win ratio after timeout: 0.1&lt;BR /&gt;Win ratio across gap: 0.3&lt;BR /&gt;Win ratio after gap : 0.3&lt;BR /&gt;Gap ratio : 0.33&lt;/P&gt;&lt;P&gt;TCR2 Ticks per tooth : 100&lt;/P&gt;&lt;P&gt;We are measuring the falling edge so the ETPU ( Hopefully ) doesn't recognize the rising edge in the gap. But when looking at tooth times ( see attachment ) the gap is ± 2.5 tooth wide. On 1 tooth in gap and 59 teeth til gap, the ETPU won't sync. But on 58 teeth til gap and 2 in gap the ETPU will sync, with the described error.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Nick.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;</description>
    <pubDate>Tue, 14 Feb 2023 08:03:18 GMT</pubDate>
    <dc:creator>nickbouwknecht</dc:creator>
    <dc:date>2023-02-14T08:03:18Z</dc:date>
    <item>
      <title>mpc5746 Etpu crank errors</title>
      <link>https://community.nxp.com/t5/MPC5xxx/mpc5746-Etpu-crank-errors/m-p/1598266#M22854</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm having problems with the crank signal measurement. When running the engine a timeout error keeps coming. Changing window ratio's doesn't make any difference.&lt;/P&gt;&lt;P&gt;We expect that the crank pattern is the problem ( see attachment ). Because an additional signal is present in the gap. How can we configure the ETPU correctly for this pattern?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2023 15:19:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/mpc5746-Etpu-crank-errors/m-p/1598266#M22854</guid>
      <dc:creator>nickbouwknecht</dc:creator>
      <dc:date>2023-02-13T15:19:55Z</dc:date>
    </item>
    <item>
      <title>Re: mpc5746 Etpu crank errors</title>
      <link>https://community.nxp.com/t5/MPC5xxx/mpc5746-Etpu-crank-errors/m-p/1598554#M22859</link>
      <description>&lt;P&gt;Your pattern looks like a pretty standard 60-1.&amp;nbsp; Does the engine synchronization state ever get beyond seek (0)?&amp;nbsp; Are you able to watch the crank state parameter?&amp;nbsp; If the eTPU software can identify the pattern the crank state will spend most of its time with a value of 7, iterating through 9, 11 and 8 at each gap.&amp;nbsp; The thrust of these questions is: does it ever synchronize? If so, does it then frequently lose sync ("timeout" per your message above)?&amp;nbsp; Is it losing sync under steady-state conditions?&amp;nbsp; What are your window ratio values and other configuration?&amp;nbsp; Is it possible your signal is noisy or inconsistent?&amp;nbsp; A lot of questions, but your attached snapshot of the crank signal looks like something the eTPU should be able to process.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Feb 2023 05:13:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/mpc5746-Etpu-crank-errors/m-p/1598554#M22859</guid>
      <dc:creator>johndiener</dc:creator>
      <dc:date>2023-02-14T05:13:06Z</dc:date>
    </item>
    <item>
      <title>Re: mpc5746 Etpu crank errors</title>
      <link>https://community.nxp.com/t5/MPC5xxx/mpc5746-Etpu-crank-errors/m-p/1598694#M22863</link>
      <description>&lt;P&gt;Thanks for the quick reply !&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ETPU is able to synchronize. But when running, a hick up appears with the fault code 4 ( timeout ). When the engine is running steady state on a certain load. The timeout error will stay away for aproximatly 10 minutes before it comes back. The signal is verry clean and doesn't contain any spikes.&lt;/P&gt;&lt;P&gt;The window ratios are taken from the Excel sheet. But changing them won't make any difference.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Win ratio normal: 0.05&lt;BR /&gt;win ratio after timeout: 0.1&lt;BR /&gt;Win ratio across gap: 0.3&lt;BR /&gt;Win ratio after gap : 0.3&lt;BR /&gt;Gap ratio : 0.33&lt;/P&gt;&lt;P&gt;TCR2 Ticks per tooth : 100&lt;/P&gt;&lt;P&gt;We are measuring the falling edge so the ETPU ( Hopefully ) doesn't recognize the rising edge in the gap. But when looking at tooth times ( see attachment ) the gap is ± 2.5 tooth wide. On 1 tooth in gap and 59 teeth til gap, the ETPU won't sync. But on 58 teeth til gap and 2 in gap the ETPU will sync, with the described error.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Nick.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;</description>
      <pubDate>Tue, 14 Feb 2023 08:03:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/mpc5746-Etpu-crank-errors/m-p/1598694#M22863</guid>
      <dc:creator>nickbouwknecht</dc:creator>
      <dc:date>2023-02-14T08:03:18Z</dc:date>
    </item>
    <item>
      <title>Re: mpc5746 Etpu crank errors</title>
      <link>https://community.nxp.com/t5/MPC5xxx/mpc5746-Etpu-crank-errors/m-p/1599070#M22868</link>
      <description>&lt;P&gt;If that is the signal at the eTPU input pin and it is set to trigger on the falling edge then it is a 60-2 pattern.&amp;nbsp; The rising edges are ignored.&lt;/P&gt;&lt;P&gt;You could try widening the windows by increasing the ratios significantly, e.g.&lt;/P&gt;&lt;P&gt;win ratio normal = 0.75&lt;/P&gt;&lt;P&gt;win ratio after timeout = 0.95&lt;/P&gt;&lt;P&gt;win ratio across gap = 0.95&lt;/P&gt;&lt;P&gt;win ratio after gap = 0.95&lt;/P&gt;&lt;P&gt;gap ratio = 0.4&lt;/P&gt;&lt;P&gt;If that helps then you could narrow them back down again one at a time to find out which triggers the timeout.&lt;/P&gt;&lt;P&gt;The Ashware eTPU simulator (&lt;A href="https://www.ashware.com/product-page/etpu2-development-tool" target="_blank"&gt;https://www.ashware.com/product-page/etpu2-development-tool&lt;/A&gt;) is hugely useful for checking/testing/proving these settings. You can replicate a flywheel signal from logged data when the error occurs and then test the crank function to see which setting is causing a timeout/sync problem.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Feb 2023 20:15:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/mpc5746-Etpu-crank-errors/m-p/1599070#M22868</guid>
      <dc:creator>KarlP</dc:creator>
      <dc:date>2023-02-14T20:15:00Z</dc:date>
    </item>
  </channel>
</rss>

