<?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>Wireless MCU中的主题 HAN Communication Error (ZPS Error received 4)</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/HAN-Communication-Error-ZPS-Error-received-4/m-p/717587#M3771</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Test Scenarios : &lt;BR /&gt;- I have two devices, which are joined with Communication Hub. &lt;BR /&gt;- One of them is Electric meter(Type1) Device and another one is Prepayment Device(Type2). &lt;BR /&gt;- Both are having same APS key for HAN communication between them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Problems :&lt;/P&gt;&lt;P&gt;- Whenever Type2 device send data to Type1 device in HAN Network, Type1 device is getting ZPS Error received 4.&lt;/P&gt;&lt;P&gt;- I have performed same scenarios in Sprint11(NXP SDK - JN-SW-4170-v1758) as well in Sprint12(NXP SDK - JN-SW-4170-v1773). &lt;BR /&gt;- In Sprint11 Type1 device can able to receive data which are sent from Type2 device. &lt;BR /&gt;- In Sprint12 Type2 device not able to receive data which are sent from Type2 device, as Type1 device is getting ZPS Error received 4.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 01 May 2018 11:16:18 GMT</pubDate>
    <dc:creator>vihang_jani</dc:creator>
    <dc:date>2018-05-01T11:16:18Z</dc:date>
    <item>
      <title>HAN Communication Error (ZPS Error received 4)</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/HAN-Communication-Error-ZPS-Error-received-4/m-p/717587#M3771</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Test Scenarios : &lt;BR /&gt;- I have two devices, which are joined with Communication Hub. &lt;BR /&gt;- One of them is Electric meter(Type1) Device and another one is Prepayment Device(Type2). &lt;BR /&gt;- Both are having same APS key for HAN communication between them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Problems :&lt;/P&gt;&lt;P&gt;- Whenever Type2 device send data to Type1 device in HAN Network, Type1 device is getting ZPS Error received 4.&lt;/P&gt;&lt;P&gt;- I have performed same scenarios in Sprint11(NXP SDK - JN-SW-4170-v1758) as well in Sprint12(NXP SDK - JN-SW-4170-v1773). &lt;BR /&gt;- In Sprint11 Type1 device can able to receive data which are sent from Type2 device. &lt;BR /&gt;- In Sprint12 Type2 device not able to receive data which are sent from Type2 device, as Type1 device is getting ZPS Error received 4.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 May 2018 11:16:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/HAN-Communication-Error-ZPS-Error-received-4/m-p/717587#M3771</guid>
      <dc:creator>vihang_jani</dc:creator>
      <dc:date>2018-05-01T11:16:18Z</dc:date>
    </item>
    <item>
      <title>Re: HAN Communication Error (ZPS Error received 4)</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/HAN-Communication-Error-ZPS-Error-received-4/m-p/717588#M3772</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vihang,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please provide more information about your issue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you working on JN-SW-4170 v1758? We do not have that version, we only provide 1745.&lt;/P&gt;&lt;P&gt;Could you please confirm this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Did you take as a reference some example?&lt;/P&gt;&lt;P&gt;Anyway, it will be very useful if you can take a screen about this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 May 2018 20:27:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/HAN-Communication-Error-ZPS-Error-received-4/m-p/717588#M3772</guid>
      <dc:creator>mario_castaneda</dc:creator>
      <dc:date>2018-05-21T20:27:34Z</dc:date>
    </item>
  </channel>
</rss>

