Custom Power Bank |5| Testing of IP5356 Module

Intro

This series of notes describes developing process of custom power bank.

Purpose: analyzing of price distribution between different components of whole device.

Photos

ImageImage
ImageImage
ImageImage

IP5356 — Power Bank IC

Image

XB4908AJL — Battery Protection IC

Image

USB-A Power Output

Image

USB-C Power Input/Output (Bidirectional)

Image

Battery temperature sensor RT1 (NTS TS) not installed (DMNP)

Image

Micro-USB Power Input

Image

B5819W SL 40В 1А SOD-123 — Schottky diode

Image

LED Segment Display

Image

Image

Key Button (activate power bank, show SoC)

Image

Image

SMD Sheet (Block) for 

Image

Specs

  • Specialized Buck-Boost Converter and Charger (Power Bank IC)
  • QC 2.0、QC 3.0、FCP、AFC、PD 2.0、PD 3.0、SCP、PPS
  • 5V@3.1A 9V@2.22A 12V@1.67A
  • 14-bit ADC
  • QFN-40

Datasheet

Tests

1 Working right after battery connection

No possible when battery initially not connected despite on battery voltage (tested also with laboratory PSU):

Image

Once charger connected at least one time it able to work:

Image

🔴 Maybe it's possible to activate it using I2C command

Looks like protection

2 Battery charging and USB power output simultaneously

Charging when no battery and battery discharged and external power connected

Result: it able to charge, but without any protocol (just 5V)

Image

🟡 Fast charging work only when one port is active. If 2+ ports is used then only 5V is supported

3 Using as seamless UPS

Not possible: when any load connected to USB when connect/disconnect charger it significant (~500ms) period of power reset when voltage disappears

Image

🔴 Using single IC as UPS not possible

4 VCC Voltage

The VCC≈3.3V and active in both modes (active and sleep) and not stable (3.19-3.37V) — depends on load

Image

Updated from 2026/02/14

VCC is a normally open 3.3V LDO with a load capacity of 50mA.

So, powering of MCU and peripheral on VCC is not recommended or it should be very low-power.

🟢 VCC≈3.3V

5 Using VSYS as power path

It's important if you're designing custom device.

Note: tested at load current 0.8A

Battery only: VSYS=BAT=3.45V (when sleep), VSYS=USB=5.20V when active)

Image

Charger only: VSYS=USB=11.8V (right after connection), VSYS=USB=4.80V (after ~30s)

Image

Charger and battery: VSYS=BAT (when sleep), VSYS=USB when active)

Image

Load: VSYS=USB=8.94V

Image

🟡 VSYS follows VBAT (~4.2V MAX) or USB (12V MAX) voltage so your LDO or DC-DC should be able to work with such wide input voltage range

6 Working under USB power exceed

If battery able to provide enough current IC drain 6A+ and provide 3.5A@5V at output for some period

Image

🟢 If battery is able to provide enough current the IC can provide 3.5A+ on USB

7 Quiescent (Standby) battery current

Not sure I'm able to measure it correctly using normal multimeter, but it shows I=3.4uA while typical value Ibat=100uA Multimeter had bad fuse

  • Operational current (no USB load, with segment): 8mA

Image

  • Sleep current: ~100uA

Image

🟢 Iq is good, but now super low

8 Minimum Battery Voltage

The module uses hardware protection IC XB7608AJ (2 in parallel). I connected phone and fully discharged batteries and at voltage it can't charge (show 0%) without charger connection. 3.37V

Image

Image

🟢 Hardware undervoltage protection works

9 Operating Temperature

Update from 2026/02/14

When charging by using fast protocols (~20W) the IC temperature is ~80°C+

When discharging using fast protocol (e.g. 5.36V@4.06A; ~20W) the IC temperature 100°C+ and after some time it can even disable protocol and start charging with 5V ~0.4A-1.5A

Image

On one the pages shows also overheating issue when IC switch voltage from 12V to 9V.

Notes: Ambient ~19°C, thermocouple attached using thermal glue (not ideal measurement)

Image

So, for since it's highly integrated solution with built-it transistors for normal work I strongly recommend to use additional heatsink.

🔴 Overheating when using fast charging protocols may occur

10 I2C Communication and Interrupt

In datasheet it's clearly specified that all IP5356 IC supports I2C protocol:

Image

Desoldered LED segment display and soldered wires to THT pins (22 Ohm resistors in series is present):

Image

Not able to make it work.

Update from 2026/02/14

Resoldered IC to IP5356_LED_BZ, now it's visible by scanner on two addresses: 0x74 and 0x75 (pull-ups 2.2k on SDA and SCL are present on custom ESP32-S3 development boards)

Image

Interrupt pin works as expected:

  • Sleep mode — LOW (10k pull-down to GND added)
  • Active mode — HIGH (always, about 3.3V)

Image

So, this pin can be used for wakeup MCU from sleep in case of button press/USB connection.

🔴 Not working for now (will test with another IC)

Update from 2026/02/14

🟢 Visible by I2C scanner and INT works as expected.

11 Button Test

When button nit pressed the voltage is 2.76V in both active and sleep modes, I suspect it's for optional LED (most modules doesn't have it).

Image

Note: I'm going to connect button key pin to MCU through diode to have ability to wakeup IP IC (e.g. in case when no load is connected).

12 Conversion Efficacy (Update 2026/03/29)

3x21700 in parallel is used for powering module

Fast Charge (5V):

Pin=Ubat*Ibat=4.037V*6.16A=25.27W

Pout=Uusb*Iusb=5.5V*4.6A=25.3W

η=Pout/Pin=25.3W/25.27=0.998814 = 99.9%

ImageImage

Result: measurements not correct.


Conclusions

🔴Not able to work right after external power/battery connection if charger (power input) never connected before
🔴Not able to provide any fast charging/discharging on 2+ ports
🔴When using fast charging the IC heating is much (100°C+)
🟡The  main difference of IP5356 from older IP5328P is that USB port transistors is built-in IC and it support fast charging protocol (high current at 5V, e.g. 5V@4A)
🟢Support many fast charging protocols and can handle USB connection
2.60K
No comments yet. Be the first to add a comment!
Cookies?