npm1300 IBAT = 0 and ADCIBATMEASSTATUS = 00

RE: npm1300 IBAT = 0 and ADCIBATMEASSTATUS = 00

Michal — Tue, 25 Mar 2025 09:25:00 GMT

I'm checking internally about the details, but here is our sample code that you can look into:

https://github.com/NordicSemiconductor/npmx/blob/main/drivers/src/npmx_adc.c#L612

RE: npm1300 IBAT = 0 and ADCIBATMEASSTATUS = 00

dani_martin — Mon, 24 Mar 2025 15:45:13 GMT

EEEYYY!!! It works. I was NOT triggering TASKVBATMEASURE manually. I thought that setting ADCCONFIG.VBATAUTOENABLE to true was enough.

Now I'm triggering manually TASKVBATMEASURE and it gives me VBAT and IBAT values.

Did I understand wrong the description of VBATAUTOENABLE? Or perhaps this mode is not triggering IBAT?

RE: npm1300 IBAT = 0 and ADCIBATMEASSTATUS = 00

Michal — Mon, 24 Mar 2025 11:36:28 GMT

I got a question, are you writing to ADC.TASKVBATMEASURE register every time you want to make a measurement?

RE: npm1300 IBAT = 0 and ADCIBATMEASSTATUS = 00

dani_martin — Thu, 20 Mar 2025 08:55:55 GMT

Thanks for the answer. Let's see if the experts can find what is missing!!

Yes, I get the same result in both ways of triggering the IBAT measurement: automatically after VBAT measurement (configured in ADCCONFIG) or manually (triggering it in TASKIBATMEASURE)

RE: npm1300 IBAT = 0 and ADCIBATMEASSTATUS = 00

Michal — Wed, 19 Mar 2025 19:31:51 GMT

Hello,

sorry for the delay, I'm back in office and back to analyzing your issue.

I have checked the different configs and couldn't find anything obvious, registers like the ADCIBATMEASEN should look correct I think, but there is probably some config missing.

I have asked the experts about this, hoping they will find out something we both may have missed.

What happens when you trigger just a single measurement using ADCCONFIG instead?

Best regards,

Michal

RE: npm1300 IBAT = 0 and ADCIBATMEASSTATUS = 00

dani_martin — Wed, 12 Mar 2025 11:37:15 GMT

ok, let's wait until Monday. Thanks!

RE: npm1300 IBAT = 0 and ADCIBATMEASSTATUS = 00

Maria Gilje — Wed, 12 Mar 2025 11:34:30 GMT

Hey Dani,

Our apologies for the delay. Michal is travelling this week, and will be back on Monday. Are you ok with waiting until then?

Best regards,

Maria

RE: npm1300 IBAT = 0 and ADCIBATMEASSTATUS = 00

dani_martin — Fri, 07 Mar 2025 11:39:54 GMT

Any new on this? Thanks!

RE: npm1300 IBAT = 0 and ADCIBATMEASSTATUS = 00

Michal — Wed, 05 Mar 2025 20:09:57 GMT

Thank you for the information.

I will check that internally and get back to you.

Best regards,

Michal

RE: npm1300 IBAT = 0 and ADCIBATMEASSTATUS = 00

dani_martin — Wed, 05 Mar 2025 07:12:15 GMT

Yes, in any situation

RE: npm1300 IBAT = 0 and ADCIBATMEASSTATUS = 00

Michal — Wed, 05 Mar 2025 00:37:27 GMT

Hello,

Is the IBAT = 0 both when charging the battery and not?

Best regards,

Michal

RE: npm1300 IBAT = 0 and ADCIBATMEASSTATUS = 00

dani_martin — Tue, 04 Mar 2025 07:51:16 GMT

Just to complete the information: the voltage and current are working fine (see oscilloscope screenshot of IBAT and VBAT for a charging session).

And this is the configuration that I'm applying (It is not in zephyr format, but I think it is easy to understand)

    { LEDDRV0MODESEL, LEDDRV_MODESEL_ERROR },                           // Configure LED_0 for error reporting
    { LEDDRV1MODESEL, LEDDRV_MODESEL_CHARGING },                        // Configure LED_1 for charging reporting
    { LEDDRV2MODESEL, LEDDRV_MODESEL_HOST },                            // Configure LED_2 for host control
    { LEDDRV2SET, 1 },

    { ADCCONFIG,      ADC_ADCCONFIG_VBATAUTOENABLE_AUTOENABLE },        // VBAT measurement every 1s
    { ADCAUTOTIMCONF, ADC_ADCAUTOTIMCONF_MAX_TIME_TEMP },               // NTC meas each 1024 ms and interal temp each 32 ms
    { ADCIBATMEASEN,  ADC_ADCIBATMEASEN_IBATMEASENABLE_ENABLE },        // Enable IBAT measures after every VBAT measure

    { GPIOMODE1,      GPIOS_GPIOMODE1_GPIOMODE_GPOIRQ },                // GPIO1 reports interrupts     (configured in XX)
    { GPIOMODE2,      GPIOS_GPIOMODE2_GPIOMODE_GPOPLW },                // GPIO2 reports Power Loss Warning (configured in POC)
    { POFCONFIG,      POF_ON_CONFIG },                                  // Power fails will reported via GPIO


    // Load Switch
    {LDSWCONFIG,  LDSWCONFIG_SOFT_START_DISABLED   },                   // Disable soft start for LDSW1 and LDSW2
    
    // battery configuration
    { ADCNTCRSEL,     ADC_ADCNTCRSEL_ADCNTCRSEL_10K },                  // Battery has a 10kOhm NTC
    {BCHGDISABLESET,  BCHGDISABLESET_IGNORE_NTC},                       // Ignore NTC

    // Charging
    { BCHGVTRICKLESEL, BCHGVTRICKLESEL_2V9},                            // Minimun voltage to start constant current charging (2.9V)
    { BCHGISETMSB,     BCHGISETMSB_215MA },                             // Charging current 215mA (MSB)
    { BCHGISETLSB,     BCHGISETLSB_215MA },                             // Charging current 215mA (LSB)
    { BCHGVTERM,       BCHARGER_BCHGVTERM_BCHGVTERMNORM_4V20 },         // Voltage to change from constant current charging to costant voltage charging while normal temp (4.2V)
    { BCHGVTERMR,      BCHARGER_BCHGVTERM_BCHGVTERMNORM_3V60 },         // Voltage to change from constant current charging to costant voltage charging while warm temp (3.6V)
    { BCHGITERMSEL,    BCHGITERMSEL_SEL20},                             // Current to stop charging in contant voltage (20% of charging current, so 43mA)
    { BCHGCONFIG,      BCHGCONFIG_ENABLE_CHARING_IF_WARM},              // Enable Charging if battery is warm


    // Discharging
    { BCHGISETDISCHARGEMSB,     BCHGISETDISCHARGEMSB_1000MA },           // Discharging current limit of 1 A (MSB)
    { BCHGISETDISCHARGELSB,     BCHGISETDISCHARGELSB_1000MA },           // Discharging current limit of 1 A (LSB)

    //Enable charging
    { BCHGENABLESET,  BCHARGER_ENABLECHARGING },   // Enable Battery Charging and cool charging
    
    {TASKAUTOTIMUPDATE, ADC_TASKAUTOTIMUPDATE_UPDATEAUTOTIM}, // Auto update NTC and DIE temp measurements