topic Re: MC33772B EVB Data reading issue in Model-Based Design Toolbox (MBDT)

Re: MC33772B EVB Data reading issue

parveez — Mon, 09 Nov 2020 14:02:11 GMT

I am using MBDT for S32k1xx. I had it working correctly but after the changing the S32k144 it is not reading correctly.

MC33772B EVB Data reading issue

parveez — Fri, 06 Nov 2020 20:02:25 GMT

Hi,

I have been working with MC33772B for 2-3 months now for testing BMS algorithms. I ran into a few problems now, the voltage reading at the pins and battery cells doesn't match with the Freemaster reading.

I have checked the FreeMaster variable settings and everything looks fine. I also monitored raw values and it looks like raw values are incorrect.

Below is the voltage reading for 6 cells.

Here are the raw values for 6 cell voltages and status

The actual pack voltage is 17V and individual cells have approx 3V but the raw value of 6 here is 0.

Also, I have noticed that the values start updating very slow after the microcontroller is reset. Even the pack voltage goes up to 13-14V (which is still not correct as the actual voltage even at the board is 17V). The same setup was working correctly previously. However, I replaced the S32k144EVB now as my old one is bricked and I am not able to fix it.

Here is the screenshot of voltage going up after 5-8 mins: Still the values read for cell 1 and cell 2 are incorrect. The other cell voltages are close to actual.

Can someone help me debug where the problem is?

Thanks!

Re: MC33772B EVB Data reading issue

TomasVaverka — Mon, 09 Nov 2020 11:28:09 GMT

Hi Rubeena,

Are you using the example project integrated in the BCC SW driver or MBDT for S32K1xx?

Best regards,

Tomas

Re: MC33772B EVB Data reading issue

mariuslucianand — Mon, 09 Nov 2020 14:26:07 GMT

Hello @parveez ,

Can you please provide us more details regarding the changes you've made?

Regards,

Marius

Re: MC33772B EVB Data reading issue

parveez — Mon, 09 Nov 2020 14:39:14 GMT

Hi @mariuslucianand

I have just replaced the S32K144 EVB, because I either damaged or bricked the previous one and not able to fix it.

Model, Freemaster file, and other HW remain the same. I have used the raw values block and the status of this block is 12.

Re: MC33772B EVB Data reading issue

parveez — Mon, 09 Nov 2020 14:47:24 GMT

@mariuslucianand

And the status of the MC3377xB get values block is 5 always. Which means wrong CRC, correct?

Re: MC33772B EVB Data reading issue

mariuslucianand — Mon, 09 Nov 2020 14:48:10 GMT

Hello @parveez ,

It's odd that just by replacing the S32K144EVB to encounter such issues. Can you please send me your Simulink model, alongside with the generated code folder to have a look on it? You can send it to me in private to keep the confidentially.

Regarding the bricked board, can you please describe its behavior? Maybe we can help you to bring it back to life.

Regards,

Marius

Re: MC33772B EVB Data reading issue

parveez — Mon, 09 Nov 2020 15:31:13 GMT

@mariuslucianand

I have used the example BMS project provided by MDBT Toolbox along with the BMS_Software_NXP.pmpx

Even then I read incorrect cell and pack voltage measurements. Each of the cell voltage is approx 3.5V.

I have attached the generated code for the example model.

And about the bricked MCU. I have already posted here: https://community.nxp.com/t5/S32K/How-to-unbrick-S32k144-using-PEmicro/m-p/1178657#M8704

And here: https://community.nxp.com/t5/S32-Design-Studio/I-can-not-program-S32K144-EVB/m-p/1178039#M6978

Thanks

Re: MC33772B EVB Data reading issue

parveez — Mon, 09 Nov 2020 16:12:50 GMT

@mariuslucianand

I wanted to mention this weird behaviour in voltage measurement. I am getting correct voltage measurement after I leave the setup and Freemaster running for about 5 mins. What I mean to say here is after approx 5 mins the voltages(cell and Pack) increase and reach to actual values.

But if I reset the mcu, the voltages drop back to low and start increasing and takes 5 mins to reach tot heir actual value. However, the multimeter reading at pins X1 on board is always read correctly.

Here is the screenshot after 5 mins of starting the measurement.

Here is the screenshot after mcu is reset without making any changes to SW/HW/cells/board: Just pressing reset on MCU S32k144

I am not understanding why this behaviour is. I have done this multiple times while using previous MCU and never came across the behaviour in measurement.