- Welcome to LowPowerLab Forum.
Recent posts
#1
General topics / Re: Help with TP5110 breakout ...
Last post by Felix - August 22, 2026, 09:58:14 PMI think you have it setup correctly for One Shot. For reference, the OneShot works like this, as also explained on the product page:
OneShot - powers the load/MCU one time until either:
- a DONE signal is received from the load to shutdown sooner than the delay
- delay expires (without DELAY signal)
- an ON! signal from or button press from the user restores power and cycle repeats
- useful for setting a system power-off delay (ex. a 1A load needs to be shutdown after precisely 1 hour)
- Cut the jumper on the bottom and either solder jumper the OneShot side or use the provided header and jumper for easy switching during development
You'd want to press ON! to enable power and start a cycle, I believe this is self explanatory. It sounds like you also checked the tactile button does work.
What is the expected load that the lights draw from the battery?
I'd like to see close up photos of the board top and bottom, before making too many assumptions. The marks on the chips should be legible.
OneShot - powers the load/MCU one time until either:
- a DONE signal is received from the load to shutdown sooner than the delay
- delay expires (without DELAY signal)
- an ON! signal from or button press from the user restores power and cycle repeats
- useful for setting a system power-off delay (ex. a 1A load needs to be shutdown after precisely 1 hour)
- Cut the jumper on the bottom and either solder jumper the OneShot side or use the provided header and jumper for easy switching during development
You'd want to press ON! to enable power and start a cycle, I believe this is self explanatory. It sounds like you also checked the tactile button does work.
What is the expected load that the lights draw from the battery?
I'd like to see close up photos of the board top and bottom, before making too many assumptions. The marks on the chips should be legible.
#2
General topics / Re: Help with TP5110 breakout ...
Last post by sparky - August 22, 2026, 05:54:11 AMI can't view your attachment
#3
General topics / Help with TP5110 breakout wiri...
Last post by algebravoyager - August 19, 2026, 12:54:29 PMHi everyone, I'm hoping this forum is still somewhat active and I get a response at some point. I would really appreciate some help.
Background
I'm creating a night light for my kids. They have existing fairy lights which just turn on and off. I wanted to use the TP5110 board I bought from LPL to run it as such: one button press turns it on for 15mins, then turns it off after. (Which is why I ended up buying the LPL breakout - because we could change the timer type).
Problem
It's not working. If i connect the battery pack directly to the lights, they power on perfectly. If I wire them (per diagram below), I can see the power goes to the board (by measuring the voltage at VIN and GND with a multimeter), I can know that the button registers (by measuring continuity via multimeter between DELAY and VIN). However, despite button presses, LOAD and GND don't seem to send anything.
Steps to recreate
The ask
Please help me identify where it's gone wrong! Caveat: I slept through all my physics/electronics classes when I was younger so my understanding is electronics understanding is minimal at best. It also explains the diagram.
Thanks in advance!
Background
I'm creating a night light for my kids. They have existing fairy lights which just turn on and off. I wanted to use the TP5110 board I bought from LPL to run it as such: one button press turns it on for 15mins, then turns it off after. (Which is why I ended up buying the LPL breakout - because we could change the timer type).
Problem
It's not working. If i connect the battery pack directly to the lights, they power on perfectly. If I wire them (per diagram below), I can see the power goes to the board (by measuring the voltage at VIN and GND with a multimeter), I can know that the button registers (by measuring continuity via multimeter between DELAY and VIN). However, despite button presses, LOAD and GND don't seem to send anything.
Steps to recreate
- 1. Cut the connection between the solder pads on the back to disable continuous mode. This was the middle and right pads.
- 2. Solder the left and middle pad together to bridge them, enabling one shot mode
- 3. Tested that it worked by measuring continuity from the two pin holes at the top (middle and right, the ones that say "one shot"), and the multimeter beeps.
- 4. Wire it up as per the diagram below
The ask
Please help me identify where it's gone wrong! Caveat: I slept through all my physics/electronics classes when I was younger so my understanding is electronics understanding is minimal at best. It also explains the diagram.
Thanks in advance!
#4
CurrentRanger / Re: Part list for blown Ranger
Last post by holziholz - July 07, 2026, 05:55:17 AMAnd the Ranger is fixed. Programming was a little challenging but with the right tools a doable job. After calibration the measurements are looking good. I'm happy and now I have a meeting with the non isolating USB isolator on a shooting range. 
#5
CurrentRanger / Re: Part list for blown Ranger
Last post by holziholz - July 03, 2026, 01:33:10 AMThank you for the fast reply.
Parts are ordered and on their way.
Parts are ordered and on their way.
#6
CurrentRanger / Re: Part list for blown Ranger
Last post by Felix - July 02, 2026, 01:34:28 PMYes that looks good.
I would maybe choose a more rugged FET like Si2365. Also, if you measure them and find no shorts they should be OK, I've only seen one of those ever short in very very few cases (maybe 1-3 that I can vaguely recall).
Wouldn't be a bad idea, if you can afford, to double that BOM just in case you need anything again in the future.
I would maybe choose a more rugged FET like Si2365. Also, if you measure them and find no shorts they should be OK, I've only seen one of those ever short in very very few cases (maybe 1-3 that I can vaguely recall).
Wouldn't be a bad idea, if you can afford, to double that BOM just in case you need anything again in the future.
#7
CurrentRanger / Part list for blown Ranger
Last post by holziholz - June 29, 2026, 03:29:12 AMHello,
due to an unfortunate case of an non isolating USB isolator my Current Ranger got blown up in a very serious way. The SAM has a hard ground fault on it's supply rail and one of the power mosfets is missing a part of it's housing.
Since Welectron is out of stock right now I need to quickly repair my ranger. Hench I went through the schematic and did some educated guessing where I could. Still I would like to confirm my part selection for a complete overhaul of all silicon based components on the board.
Here is the parts I have identified so far:
1x ATSAMD21G18A-AU - Mouser 556-ATSAMD21G18A-AU
1x MCP73831T-2ACI/OT - Mouser 579-MCP73831T-2ACIOT
1x TC7660EOA713 - Mouser 579-TC7660EOA713
2x SI7615ADN-T1-GE3 - Mouser 78-SI7615ADN-T1-GE3
2x MAX4239AUT+T - Mouser 700-MAX4239AUT+T
10x SI2347DS-T1-BE3 - Mouser 78-SI2347DS-T1-BE3
2x BSS123 - Mouser 512-BSS123
I'm missing the 3V3 regulator, but after desoldering the SAM i can measure 3V3 on the supply rail, so I would expect the chip to be okay. Same for the TC7660 IC. +4 V go in -4 V comes out, seems to be legit. The charging IC seems also to be fine.
The IRLML5203 is currently not in stock and also discontinued, why I want to replace them with the SI2347 fets.
Is this all I need and the correct selection?
Best regards
Stefan
due to an unfortunate case of an non isolating USB isolator my Current Ranger got blown up in a very serious way. The SAM has a hard ground fault on it's supply rail and one of the power mosfets is missing a part of it's housing.
Since Welectron is out of stock right now I need to quickly repair my ranger. Hench I went through the schematic and did some educated guessing where I could. Still I would like to confirm my part selection for a complete overhaul of all silicon based components on the board.
Here is the parts I have identified so far:
1x ATSAMD21G18A-AU - Mouser 556-ATSAMD21G18A-AU
1x MCP73831T-2ACI/OT - Mouser 579-MCP73831T-2ACIOT
1x TC7660EOA713 - Mouser 579-TC7660EOA713
2x SI7615ADN-T1-GE3 - Mouser 78-SI7615ADN-T1-GE3
2x MAX4239AUT+T - Mouser 700-MAX4239AUT+T
10x SI2347DS-T1-BE3 - Mouser 78-SI2347DS-T1-BE3
2x BSS123 - Mouser 512-BSS123
I'm missing the 3V3 regulator, but after desoldering the SAM i can measure 3V3 on the supply rail, so I would expect the chip to be okay. Same for the TC7660 IC. +4 V go in -4 V comes out, seems to be legit. The charging IC seems also to be fine.
The IRLML5203 is currently not in stock and also discontinued, why I want to replace them with the SI2347 fets.
Is this all I need and the correct selection?
Best regards
Stefan
#8
CurrentRanger / Re: Need guidance for current ...
Last post by Felix - May 28, 2026, 09:07:50 PMThe -0.40e-3 readings in mA you see are just the very bottom end of the ADC (noise), don't expect high accuracy there (since you're really running uA's, not mA's).
The spikes during auto-ranging are a usual artifact when ranges switch 3 orders of magnitude.
You could do software filtering as you said, or modify the firmware to wait a certain amount of time.
Or do the averaging right in the firmware yourself.
Or maybe one of the 3rd party GUI's can do something or it's easy to add functionality to.
Like this one looks really good and has a lot of goodies but I don't see averaging, but good export support and maybe that's 1 step away from some cleanup and getting averages:
https://vitormhenrique.github.io/CurrentRangerApp/
The spikes during auto-ranging are a usual artifact when ranges switch 3 orders of magnitude.
You could do software filtering as you said, or modify the firmware to wait a certain amount of time.
Or do the averaging right in the firmware yourself.
Or maybe one of the 3rd party GUI's can do something or it's easy to add functionality to.
Like this one looks really good and has a lot of goodies but I don't see averaging, but good export support and maybe that's 1 step away from some cleanup and getting averages:
https://vitormhenrique.github.io/CurrentRangerApp/
#9
CurrentRanger / Need guidance for current moni...
Last post by BDLawISU84 - May 27, 2026, 08:26:20 AMI think I've run into a use case that CurrentRanger just wasn't designed for, but just double-checking before I look at other products ...
My board toggles between sleep & wake states frequently ... it wakes every 30 msec, polls some inputs for 3-5 msec, then goes back to sleep. In sleep mode, the current usage is about 500-800 uA. In wake mode current usage is > 5 mA.
On my bench the board is powered by a power supply and I have a USB isolator connected so I can monitor the current readings and eventually graph them. I'm running the off-the-shelf R3_1.1.6 CurrentRanger firmware. My custom graphing app initializes the CurrentRanger via commands '!' (reset all settings to defaults), 'a' (auto-off disabled), 'u' (start logging) plus a "mode" setting I document below.
If I run CurrentRanger in uA mode (init sequence = "! a 2 u"), the sleep current looks correct but the wake current readings are clipped at just under 3300 uA.
If I run CurrentRanger in mA mode (init sequence = "! a 1 u"), the wake current looks correct but the sleep current readings are 0 or sometimes negative:
0.00e-3
-0.40e-3
0.00e-3
-0.40e-3
-0.40e-3
-0.40e-3
If I run CurrentRanger in autoranging mode (init sequence = "! a 1 6 u"), I almost have a working solution except that when the op amp saturates in uA mode during the wake up, I get extreme out of range errors like this glitch to 446 mA ...
553.53e-6
556.75e-6
665.44e-6
1002.38e-6
446.44e-3 <-- 446 mA
7.65e-3
3.22e-3
1259.62e-6
983.46e-6
1022.51e-6
974.21e-6
890.47e-6
823.24e-6
787.42e-6
I guess one solution is to toss the first 2 readings reported whenever the exponent changes from a high number to a lower number, but I'm trying to do some average current consumption over time calculations and that throws off those averages.
Is there any kind of workaround for this?
My board toggles between sleep & wake states frequently ... it wakes every 30 msec, polls some inputs for 3-5 msec, then goes back to sleep. In sleep mode, the current usage is about 500-800 uA. In wake mode current usage is > 5 mA.
On my bench the board is powered by a power supply and I have a USB isolator connected so I can monitor the current readings and eventually graph them. I'm running the off-the-shelf R3_1.1.6 CurrentRanger firmware. My custom graphing app initializes the CurrentRanger via commands '!' (reset all settings to defaults), 'a' (auto-off disabled), 'u' (start logging) plus a "mode" setting I document below.
If I run CurrentRanger in uA mode (init sequence = "! a 2 u"), the sleep current looks correct but the wake current readings are clipped at just under 3300 uA.
If I run CurrentRanger in mA mode (init sequence = "! a 1 u"), the wake current looks correct but the sleep current readings are 0 or sometimes negative:
0.00e-3
-0.40e-3
0.00e-3
-0.40e-3
-0.40e-3
-0.40e-3
If I run CurrentRanger in autoranging mode (init sequence = "! a 1 6 u"), I almost have a working solution except that when the op amp saturates in uA mode during the wake up, I get extreme out of range errors like this glitch to 446 mA ...
553.53e-6
556.75e-6
665.44e-6
1002.38e-6
446.44e-3 <-- 446 mA
7.65e-3
3.22e-3
1259.62e-6
983.46e-6
1022.51e-6
974.21e-6
890.47e-6
823.24e-6
787.42e-6
I guess one solution is to toss the first 2 readings reported whenever the exponent changes from a high number to a lower number, but I'm trying to do some average current consumption over time calculations and that throws off those averages.
Is there any kind of workaround for this?
#10
CurrentRanger / Re: CurrentRangerApp
Last post by Felix - May 19, 2026, 08:18:15 AMThat's great, thanks for the update!