nPM1300-EK+nRF52 DK+NRF5 SDK, charge/discharge current issue

RE: nPM1300-EK+nRF52 DK+NRF5 SDK, charge/discharge current issue

Andy Sinclair — Mon, 08 Jul 2024 10:36:28 GMT

Hi.

Does if fail immediately, or after a bit?
When it stops responding, is the interrupt left asserted?

There is an example of configuring events using npmx here:
npmx-zephyr/samples/charger_and_events/src/main.c at main · NordicSemiconductor/npmx-zephyr (github.com)

Andy

RE: nPM1300-EK+nRF52 DK+NRF5 SDK, charge/discharge current issue

GRooVE — Thu, 04 Jul 2024 14:36:45 GMT

Hi Andy.

I've run into unexpected behavior again. When trying to call:

npmx_core_event_interrupt_enable(&npmx_instance, NPMX_EVENT_GROUP_ADC, NPMX_EVENT_GROUP_ADC_BAT_READY_MASK);

I am no longer getting any interrupts working at all. Either hardware reboot of the nPM module helps, or cyclic call of npmx_core_event_interrupt_disable() for each interrupt.
For the sake of purity of the experiment, I tested this call both in our project and in the test example from the second post of this thread.

Maybe you can help me, or give me extended information about processing events of NPMX_EVENT_GROUP_GROUP_ADC type with NPMX_EVENT_GROUP_ADC_BAT_READY_MASK.

Thanks

Best Regards

RE: nPM1300-EK+nRF52 DK+NRF5 SDK, charge/discharge current issue

GRooVE — Wed, 03 Jul 2024 09:28:49 GMT

Hi Andy,

Thank you for the clarification and for your help.
No further questions at this time.

RE: nPM1300-EK+nRF52 DK+NRF5 SDK, charge/discharge current issue

Andy Sinclair — Wed, 03 Jul 2024 09:08:48 GMT

Hi GRooVE.

Good point. Looking more closely, charger status won't work, because the battery detection bit is set as part of the charging FSM, so only runs when USB is connected.

You can check if USB is connected by reading the vbusin status:
npmx_vbusin_vbus_status_get

Andy

RE: nPM1300-EK+nRF52 DK+NRF5 SDK, charge/discharge current issue

GRooVE — Tue, 02 Jul 2024 15:31:07 GMT

Thanks, Andy.

I know about calling npmx_vbusin_current_limit_set(), of course. At power on, I saw a consumption of 150mA set to charge, while in the log I saw only 32mA. Nevertheless, I figured out the cause, thanks.

But the battery issue is still unresolved. After power on and initialization, npmx_charger_status_get() always returns mask 0, both with battery connected and charging disconnected at startup, and with battery disconnected and charging connected. In both cases, none of the callbacks are triggered at startup. If in case of VBUSIN I can get the state via npmx_vbusin_vbus_status_get(), in case of battery I have not found a way. Maybe you can suggest a working method. Thanks

RE: nPM1300-EK+nRF52 DK+NRF5 SDK, charge/discharge current issue

Andy Sinclair — Tue, 02 Jul 2024 13:43:08 GMT

Hi.

The USB current limit is reset to the default value when USB is removed,
could this be the difference you see?

For example, I have the default fuel gauge configuration (150mA charge current, 500mA USB current limit). I get the 150mA charge current if I power up with USB connected.

[00:00:03.283,996] <inf> fuel_gauge: V: 3.706, I: -0.158, T: 24.91, SoC: 31.84,

After removing and re-inserting USB, the USB current limit will default to 100mA (actual value depends on version of silicon.)

[00:01:15.629,913] <inf> fuel_gauge: V: 3.676, I: -0.094, T: 24.80, SoC: 32.85,

To get higher current, you need to call npmx_vbusin_current_limit_set again.

---

To get battery connection status at startup, you can call npmx_charger_status_getBest regards
Andy

RE: nPM1300-EK+nRF52 DK+NRF5 SDK, charge/discharge current issue

GRooVE — Tue, 02 Jul 2024 12:40:29 GMT

Hi, Andy.

I still get wrong values if the microcontroller starts after the charger has been plugged in. If I reconnect the charger afterwards, or if I connect it after startup, the current values are displayed correctly. Could you please confirm or deny this fact?
Also, I'm having some difficulty with the initial battery status determination after starting the program. If I call the npmx_core_register_cb() function with the NPMX_CALLBACK_TYPE_EVENT_BAT_CHAR_STATUS callback type, I can track the change of the battery connection or disconnection status inside the callback function, but how can I get its status right after power on, in manual mode? Perhaps you could help me.

Best regards

RE: nPM1300-EK+nRF52 DK+NRF5 SDK, charge/discharge current issue

Andy Sinclair — Mon, 01 Jul 2024 15:41:53 GMT

Testing further, I missed a negative sign when changing the scaling (charging current needs to be negative).
I have update the branch to fix this.

RE: nPM1300-EK+nRF52 DK+NRF5 SDK, charge/discharge current issue

GRooVE — Mon, 01 Jul 2024 13:20:32 GMT

Hi, Andy.

Thanks for the quick response.
At first glance, it looks like the problem is fixed.
We'll do some more internal testing. I'll let you know if there are any issues.

Thank you and best regard

RE: nPM1300-EK+nRF52 DK+NRF5 SDK, charge/discharge current issue

Andy Sinclair — Mon, 01 Jul 2024 12:21:10 GMT

Hi GrooVE.

Thanks for you comprehensive question, the detail is really useful.

I have taken a closer look at the issues, and there are a couple of bugs in the driver that are responsible for this.

I have tested the following changes to the driver, and it fixes the issue on my setup.
Comparing NordicSemiconductor:main...aasinclair:fix-charge-discharge-current-scaling · NordicSemiconductor/npmx (github.com)

We will be reviewing these changes internally and will update the official release soon.

Best regards
Andy

RE: nPM1300-EK+nRF52 DK+NRF5 SDK, charge/discharge current issue

GRooVE — Mon, 01 Jul 2024 10:07:15 GMT

Hi Kazi,

The problem is not even with the fuel gauge driver, but exactly with reading the current value from the nPM registers.
The example in the second post illustrates this perfectly.

We'll be waiting for an answer.
Thank you very much in advance for your help.

RE: nPM1300-EK+nRF52 DK+NRF5 SDK, charge/discharge current issue

Kazi Afroza Sultana — Sun, 30 Jun 2024 12:26:32 GMT

Hello Maksym,

I have been looking into your issues. I have not tried fuel gauge sample with nRF5 SDK. I have asked developer if there any changes require for this sample to run on nRF5DK. I will get back to you on Monday.

Thanks.

BR
Kazi

RE: nPM1300-EK+nRF52 DK+NRF5 SDK, charge/discharge current issue

GRooVE — Fri, 28 Jun 2024 11:29:17 GMT

We have prepared a simple example for the NRF5 SDK that fully reproduces the described problem we encountered.
We will be grateful for any help.

devzone.nordicsemi.com/.../npmx_5F00_fuel_5F00_gauge.zip