When my Pi-top is charged I'd unplug it from the wall but immediately the pi top would turn off. For a while all i'd have to do is try to remember to shut down when its charged then unplug it. However, perhaps i forgot to do that one to many times now I get no indication of battery charge, nor does the pi top power up without being plugged into the wall. Its become highly inconvenient and Im not sure whats damaged or how to fix it, what can be done?Thank you very much
Monday afternoon I let deplete the batteries of my 3 pi-tops. 1 x Rpi2 and 2 x Rpi3.
Immediately when the power was cut at 5% (thanks Rene), I plugged in the Power Adaptor.
And leaved them for the night.
The Rpi2 is fine and could be started from its battery.
Both Rpi3 did not boot from their respective battery.
Attached is a screen dump.
I'll keep you current on the recovery I'll do.
Recovery running. ...
Enjoy your pi-top.
1 of 2 recovered. On to the next one.
In the lower range cell 1 drags by 0,5 volt.
Which created a PE failure.
The device can permanently disable the use of the battery pack in case of a severe failure. The
permanent failure checks, except for IFC and DFW, can be individually enabled or disabled by setting the
appropriate bit in Settings:Enabled PF A, Settings:Enabled PF B, Settings:Enabled PF C, and
Settings:Enabled PF D. All permanent failure checks, except for IFC and DFW, are disabled until
ManufacturingStatus()[PF] is set. When any PFStatus() bit is set, the device enters PERMANENT FAIL
mode and the following actions are taken in sequence:
1. Precharge, charge, and discharge FETs are turned off.
2. OperationStatus()[PF] = 1, [XCHG] = 1, [XDSG] = 1
3. The following SBS data is changed: BatteryStatus()[TCA] = 1, BatteryStatus()[TDA] = 1,
ChargingCurrent() = 0, and ChargingVoltage() = 0.
4. A backup of the internal AFE hardware registers are written to data flash: AFE Interrupt Status, AFE
FET Status, AFE RXIN, AFE Latch Status, AFE Interrupt Enable, AFE FET Control, AFE RXIEN,
AFE RLOUT, AFE RHOUT, AFE RHINT, AFE Cell Balance, AFE AD/CC Control, AFE ADC Mux,
AFE State Control, AFE Protection Control, AFE OCD, AFE SCC, AFE SCD1, and AFE SCD2.
5. The black box data of the last three SafetyStatus() changes leading up to PF with the time difference is written into the black box data flash along with the 1st PFStatus() value.
6. The following SBS values are preserved in data flash for failure analysis:
• Voltages in DAStatus1()
• TSINT, TS1, TS2, TS3, and TS4 from DAStatus2()
• Cell DOD0 and passed charge
7. Data flash writing is disabled (except to store subsequent PFStatus() flags).
8. The FUSE pin is driven high if configured for specific failures and Voltage() is above Min Blow Fuse
Voltage or there is a CHG FET (CFETF) or DSG FET (DFETF) failure. The FUSE pin will remain
asserted until the Fuse Blow Timeout expired.
Hope this helps someone else with their issues. I think it is a safe bet that Rene's widget should be used on the pi-top. /end shameless plug
I bought my Pi-Top June 2016 and the first battery failed November 2016 and a replacement was supplied and now that 2nd battery has failed completely August 2017 and the response was that the Hub Controller board is the route cause of the problem and is under re-design and I should request a new Mk2 Hub and battery pack, however that request went off over a month ago and nothing has arrived yet.
I have now raised another ticket requesting an update if replacement parts will or will not be supplied.
(Where is copy/paste gone on this Forum?)
All that FWUpdate does is resetting the bq40z60, which might help in one case but mostly not.
The bq40z60 is protected with a password, without it, you cannot read out instructions nor data.
The last batch (by lack of better ways to describe things) of Base/Cells/electronics has HSA-1/HMAC encryption implemented steering further away from the original idea of open software/hardware.
At one point I had 3 pi-top and Texas Instruments supplied tools and software to study what's under the shining hood. I've donated all to a technical school in my home town.
that is bad news,
I am still having to kickstart the second shipped battery I received with the firmware patch every time it gets below a certain percentage so that the pi-top will continue to run off battery. But between this and all the comllaints on teh forums, the closed source hardwar, the continued hardware bugs, and lack of support, I am with youabout sending off this $300 paperweight. I just haven't done so yet. I am getting tired of trying to maintain it though, especially after reading all the continued complaints.
good luck in your next venture,
I did take the pi-top apart all of the way so I could reset the hub. I then charge the battery up to full discharged for a bit. then I eft it on mains afterwards (for a few days) so it colud charge back up,
I needed to pull the pi off mains after charging it and runing the fw update. but couldn't as it didnt charge fully after just one run of the update. I rand the update three times and it charged to ull. I had needed the pi-top too be portable this morning too. after running the update it did charge and work. Past the point of me needing it to be portable though
. the flaky-ness of the battery is a big issue. I hope the team gets a fix for future users. The pi-top continues to disappoint me as i said in my previous post.