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.
Check the socket side cable. The plug can be tight to get into the charger box. A partially inserted plug would make an arc sound.
Its a pretty generic and low quality cable. Similar to a desktop computer. Try swapping out that plug in AC cable.
These XR and Pint batteries are a litium NMC type cells. The charger won't overcharge and long balancing charges are required to balance the cells. I.e. balance them all to the same voltage. 72 hrs would only be required if one or more cells are badly out of balance.
I do an overnight once every 3 months and also have ZERO battery issues. Battery testing results also show that you can significantly extend the life of the battery for a battery which already has a pretty good lifespan, by not fully cycling the cells, which means don't let it go fully flat and don't fully charge them. This works for me because i have a regular commute and don't need a full charge each day.
@holageorgia first step is to do a long charge to give the board a chance to balance the cells. Factory recommends 24hrs.
That should bring all the cells to same voltage and recalibrate the app power meter.
I do a balance charge once a month. Which for me is about 20 charge cycles.
If that doesn't fix it the its a possibly a bad cell or BMS and that would mean a call to FM.
Can't be 100% sure. But if the low juice msg is happening at different % remaining, then the only other relevant data the App gets is battery voltage. So it must trigger once batt voltage hits a low level.
Keep in mind the battery voltage will sag with load, then recover a bit. So if you ask the board for more power, like short acceleration burst. The battery voltage will drop slightly during that burst and that could be when the alrm is triggered.