Do a long minimum 24hr charge to balance the cells and recalibrate the App power meter.
Let us know if that improves it. Good news is there are plenty of options to extend the battery life.
Yeah all good, i didn't read into your first statement that you were after instantaeous current. For sure the data is in the controller, just not displayed.
I'm not so sure that current is used for pushback, in my mind, high current would trigger the protection system (causing a nosedive). I think pushback is more general and based on soft signal limits like speed and any alarms from the BMS. I think this because pushback comes in at a consistent speed, regardless of current which would be different for an uphill vs downhill case.
Also explains why nosedives are more frequent at low battery voltage. Lower voltage means higher current for a given power requirement.
Current protection is very common in motor protection controllers.
Some strange goings on the App mileage ladder in the last 24hrs. Everyone is reporting going back up the list. Seems to impact the streak ladder as well.
Maybe this is 'the merge' where all board types are on the same ladder?
Maybe their server has had a bug in the ladder and was never reporting correctly and they have just fixed it?
What do you think?
@Sponge315 just adding to the conversation. XR has 15 cells and BMS charges up to 63v so each cell is charged to 4.2v. Good summary of the NMC battery here from the battery university site.
Not sure I have the image link working. Sorry first time for everything. 🙄```
@Senior-Coffee the conversation has kind of wandered from pushback to range. All good with that.
Thought i would chip in with using pushback in mission is accurate for informing speed. I use it all the time. I took me a while to reliably detect it in mission cause it is subtle, but definitely there.