开云体育

I have a genuine TinySA purchased from the Zeenko store on AliExpress.
it worked fine when i go it, battery charged up OK, over 4 volts.
Now it will only charge to 3.27v and the red charging LED goes out before the battery is actually fully charged.
The display show the battery icon as almost empty.
If I plug in the USB cable again, the red charging light goes on, but will not stay on for very long.

Does anybody have any ideas on how to troubleshoot this problem?

Thanks for your suggestions.

Try using a new USB-C cable, see if that helps. I've had loads of problems with the USB C cables wearing out quite quickly.

The cable may not be the cause of your particular problem but it certainly has been for me.
Barring that, I'd remove the board from it's case and make sure there is 5V coming from the USB cable with it plugged in, it should be around the PCB's USB-C socket somewhere.

Try a different charger. I had some of the cheaper chargers stop working after a few month the cheap capacitors used wear out because they are marginal to start with. I actually build a small linear supply with a USB output for the TinySA. It solves the problem of switching noise radiated via the USB cable and gives me a reliable output voltage.?
I use a voltage /? data splitter to feed it when I use it with the computer. The splitter? can be bought at many places and is used for external hard drives, tablets and so on.

John

Tried a different USB cable, made no difference. Tried a different USB charger, including a laptop USB port, no change.
What I tried was to completely drain the battery by leaving the TinySA turned on overnight. Then plugged in the USB cable to charge it. Charged for about 3 hours, but the battery voltage only gets to about 3.73v.

On Mon, Aug 23, 2021 at 09:10 AM, Lane Wilson wrote:

Tried a different USB cable, made no difference. Tried a different USB charger, including a laptop USB port, no change.
What I tried was to completely drain the battery by leaving the TinySA turned on overnight. Then plugged in the USB cable to charge it. Charged for about 3 hours, but the battery voltage only gets to about 3.73v.

Sounds like a battery failure.? There are some protection electronics on the battery itself.? Maybe they have failed.? You can find replacement batteries on eBay or from some RC hobby shops.

Roger

Update: This appears to be a firmware problem. I opened the case and measured the battery voltage it was at 4.1v!
I had recently updated the firmware to v1.3-317-g9d82970.dfu from Erik's web site. That is when the battery voltage was being displayed as low.
I re-loaded firmware v1.3-265-ga0c410f.dfu and the battery voltage is now displayed in green and at 4.23V

There appears to be a problem with the latest firmware release v1.3-317 !

Lane

I'm on firmware 313 and my SA sez 4.21V.

73

-Jim
NU0C

On Thu, 26 Aug 2021 16:34:22 -0700
"Lane Wilson" <lane.wilson.5811@...> wrote:

Update: This appears to be a firmware problem. I opened the case and measured the battery voltage it was at 4.1v!
I had recently updated the firmware to v1.3-317-g9d82970.dfu from Erik's web site. That is when the battery voltage was being displayed as low.
I re-loaded firmware v1.3-265-ga0c410f.dfu and the battery voltage is now displayed in green and at 4.23V

There appears to be a problem with the latest firmware release v1.3-317 !

Lane

Somewhat of a mystery then. Could i have a setting wrong?

On Fri, Aug 27, 2021 at 01:34 AM, Lane Wilson wrote:

There appears to be a problem with the latest firmware release v1.3-317 !

Hello Lane,
I am using firmware v1.3-317 and the battery voltage shows 4.27 V,
see tinySA_v1.3-317_Batter-4.27V.jpg.

Question: Did you "CLEAR CONFIG" after the firmware update?
Menu->CONFIG->EXPERT CONFIG->MORE->MORE->CLEAR CONFIG, enter 1234

73, Rudi DL5FA

Hi Rudi, I will try the clearconfig command and report back...

Looks like I had forgotten to use the "clearconfig 1234" command. Once this was done, the battery voltage is now working as expected on firmware v1.3-317.
After re-loading the firmware, I did a self test (all passed), and Level calibration. All appears to be working good now.