<?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>Power ManagementのトピックRe: RD33771-48VEVM Reference Design  Data Type Problem</title>
    <link>https://community.nxp.com/t5/Power-Management/RD33771-48VEVM-Reference-Design-Data-Type-Problem/m-p/1052778#M974</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Shao,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.&amp;nbsp;The&amp;nbsp;MC33771&amp;nbsp;device datasheet tells you that all raw measurements are done in mVolts in the range [CTx_UV_TH ..&amp;nbsp;CTx_OV_TH].&amp;nbsp;The MEAS_xxxx registers contain the measured values as a result of on-demand conversions.&lt;/P&gt;&lt;P&gt;Therefore the driver also stores the mVolt values to&amp;nbsp;not waste time for conversion to float. It is up to the application to do float calculation based on those integer values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.&amp;nbsp;Yes, the first index [15] means up to 15 MC33771 nodes, or clusters, where cluster ID = 0..14 is assigned to the device during initialization phase (enumeration).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The second index [24] means measurements obtained from the MC337771.&lt;/P&gt;&lt;P&gt;[0] = VStack&lt;/P&gt;&lt;P&gt;[1~14] = VCellx&lt;/P&gt;&lt;P&gt;[15~21] = Vtemperature&lt;/P&gt;&lt;P&gt;[22,23] = store Vadc-a, Vadc-b in debugging purpuse code, but no longer used in this code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3.&amp;nbsp;ECC signature is a 32-bit word, so you are right, is must be uint32_t. There is a copy/paste bug in the structure definition. Be cautious to change this in the *.h to&amp;nbsp;uint32_t.&amp;nbsp;Otherwise&amp;nbsp;in case we have two or more clusters every next ECC value would overwrite the previous one because of this bug.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Tomas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;EM style="border: 0px; font-weight: inherit;"&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 14 May 2020 10:17:00 GMT</pubDate>
    <dc:creator>TomasVaverka</dc:creator>
    <dc:date>2020-05-14T10:17:00Z</dc:date>
    <item>
      <title>RD33771-48VEVM Reference Design  Data Type Problem</title>
      <link>https://community.nxp.com/t5/Power-Management/RD33771-48VEVM-Reference-Design-Data-Type-Problem/m-p/1052777#M973</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am going to develop a BMS. I found the&amp;nbsp;&lt;A href="https://www.nxp.com.cn/design/designs/rd33771-48vevm-reference-design:RD33771-48VEVM"&gt;rd33771-48VEVM Reference Design&lt;/A&gt;&amp;nbsp;on the NXP website.&lt;/P&gt;&lt;P&gt;When I study the&amp;nbsp;&lt;A href="https://www.nxp.com.cn/webapp/sps/download/preDownload.jsp"&gt;SW driver package&lt;/A&gt;, I have some problems with the parameter definition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The first problem is some parameter like 'u16VoltCell[15][24]' means the voltage of the cell in the package. The data type of this parameter is 'uint16_t'. I think the parameter associated with voltage, current, temperature should be 'float'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The second problem is for the parameter&amp;nbsp;&lt;SPAN&gt;'u16VoltCell[15][24]', I think the '[15]' means it can have 15 mc33771 nodes for the BMS. as for the '[24]',[0] is stack voltage ,[1]...[14] means cell1..14, what are the rest of the bits for?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The third problem is the&amp;nbsp;parameter 'u32ECCSignature[15]', I think the data type is 'uint32_t' according to the name, but the data type is 'uint16_t'.&amp;nbsp;I don't know if there's an error here&lt;span class="lia-inline-image-display-wrapper" image-alt="parameter.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/18142i4A91E8C11597B904/image-size/large?v=v2&amp;amp;px=999" role="button" title="parameter.jpg" alt="parameter.jpg" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;H1 class="" style="color: #ffffff; background-color: #ffffff; font-weight: bold; font-size: 2.6705em;"&gt;RDTh33771-48VEVM Reference DesignRD&lt;/H1&gt;&lt;H1 class="" style="color: #ffffff; background-color: #ffffff; font-weight: bold; font-size: 2.6705em;"&gt;RD33771-48VEVM Reference Design&lt;/H1&gt;&lt;H1 class="" style="color: #ffffff; background-color: #ffffff; font-weight: bold; font-size: 2.6705em;"&gt;RD33771-48VEVM Reference Design&lt;/H1&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 May 2020 00:19:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Power-Management/RD33771-48VEVM-Reference-Design-Data-Type-Problem/m-p/1052777#M973</guid>
      <dc:creator>m15871781742</dc:creator>
      <dc:date>2020-05-07T00:19:53Z</dc:date>
    </item>
    <item>
      <title>Re: RD33771-48VEVM Reference Design  Data Type Problem</title>
      <link>https://community.nxp.com/t5/Power-Management/RD33771-48VEVM-Reference-Design-Data-Type-Problem/m-p/1052778#M974</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Shao,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.&amp;nbsp;The&amp;nbsp;MC33771&amp;nbsp;device datasheet tells you that all raw measurements are done in mVolts in the range [CTx_UV_TH ..&amp;nbsp;CTx_OV_TH].&amp;nbsp;The MEAS_xxxx registers contain the measured values as a result of on-demand conversions.&lt;/P&gt;&lt;P&gt;Therefore the driver also stores the mVolt values to&amp;nbsp;not waste time for conversion to float. It is up to the application to do float calculation based on those integer values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.&amp;nbsp;Yes, the first index [15] means up to 15 MC33771 nodes, or clusters, where cluster ID = 0..14 is assigned to the device during initialization phase (enumeration).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The second index [24] means measurements obtained from the MC337771.&lt;/P&gt;&lt;P&gt;[0] = VStack&lt;/P&gt;&lt;P&gt;[1~14] = VCellx&lt;/P&gt;&lt;P&gt;[15~21] = Vtemperature&lt;/P&gt;&lt;P&gt;[22,23] = store Vadc-a, Vadc-b in debugging purpuse code, but no longer used in this code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3.&amp;nbsp;ECC signature is a 32-bit word, so you are right, is must be uint32_t. There is a copy/paste bug in the structure definition. Be cautious to change this in the *.h to&amp;nbsp;uint32_t.&amp;nbsp;Otherwise&amp;nbsp;in case we have two or more clusters every next ECC value would overwrite the previous one because of this bug.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Tomas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;EM style="border: 0px; font-weight: inherit;"&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 May 2020 10:17:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Power-Management/RD33771-48VEVM-Reference-Design-Data-Type-Problem/m-p/1052778#M974</guid>
      <dc:creator>TomasVaverka</dc:creator>
      <dc:date>2020-05-14T10:17:00Z</dc:date>
    </item>
  </channel>
</rss>

