smorgasbord
Well-Known Member
- Region
- USA
We're in the third decade of the 21th century, folks. I can't believe we still have to mentally map a reading of, say, 50.7 volts on our 48 volt battery (that alone is crazy) to a 75% battery charge - and that the 75% battery charge itself doesn't actually relate to usable battery percentage!
Here's a chart that maybe came from Luna originally:
The first issue is that you can't run it to 0 % (39 volts). The motor controller will turn off at something like 42 volts (probably controller specific). So, first thing to do is to map 54.6 volts to 100% and then, say, 42.9 volts to 0%. That should be really easy, even small 8-bit controllers could have a tiny 4-bit lookup table to produce 16 values, which would be far superior to the 5 bars most displays show today. A 5-bit table would yield 32 values - still really small.
Now, there's the issue that voltage drop against usage (miles ridden is the better proxy) isn't linear. That is, a 0.5 volt drop when the battery is almost full is the result of more miles being ridden than a 0.5 volt drop when the battery is half or less full. This is why so many people report, for instance, that they get 15 miles before going from 5 bars to 4 bars, but going from 3 bars to 2 bars happens after only 6 miles. That kind of Range Anxiety is scary when you're on a heavy ebike that's really hard to pedal without assistance, particularly if there's a hill between you and home.
Let's say the true range of an ebike with a 200 lb rider on flat ground in PAS 2 (or equivalent) and going, say 15 MPH, is 48 miles. With the 4-bit/16-value table, I could empirically build the values in a few hours. Just find a flat road that's a few miles long on a calm day and measure the battery voltage every 4 miles. I think the only problem would be whether I'm willing to ride the bike until it literally gives up, in case that damages the battery. Would throw it on a charger right away, of course.
Anyway, this 4-bit table would give me enough gradations (6.25% apart) going from full to zero, where zero is bike gives up. Now if I've got more or less load, more or less hills or wind, etc., I would still know how close I am to running out of battery on this bike and could compare mileage ridden that day to the percentage display.
What I don't get is why no manufacturer even enables this, much less does this. (Or maybe there are manufacturers that do?)
Surely all controllers with a better than multi-segment display, from Bosch to Bafang, can handle a 16 entry table lookup for battery percentage - they're just not set up to do this. Matter of fact, the Bafang controller is so lame that even when set up for 52 volts, the battery percentage reads as if a 48 volt battery is being used.
Bafang and others, at least give us a way to load entries in that table.
Here's a chart that maybe came from Luna originally:
The first issue is that you can't run it to 0 % (39 volts). The motor controller will turn off at something like 42 volts (probably controller specific). So, first thing to do is to map 54.6 volts to 100% and then, say, 42.9 volts to 0%. That should be really easy, even small 8-bit controllers could have a tiny 4-bit lookup table to produce 16 values, which would be far superior to the 5 bars most displays show today. A 5-bit table would yield 32 values - still really small.
Now, there's the issue that voltage drop against usage (miles ridden is the better proxy) isn't linear. That is, a 0.5 volt drop when the battery is almost full is the result of more miles being ridden than a 0.5 volt drop when the battery is half or less full. This is why so many people report, for instance, that they get 15 miles before going from 5 bars to 4 bars, but going from 3 bars to 2 bars happens after only 6 miles. That kind of Range Anxiety is scary when you're on a heavy ebike that's really hard to pedal without assistance, particularly if there's a hill between you and home.
Let's say the true range of an ebike with a 200 lb rider on flat ground in PAS 2 (or equivalent) and going, say 15 MPH, is 48 miles. With the 4-bit/16-value table, I could empirically build the values in a few hours. Just find a flat road that's a few miles long on a calm day and measure the battery voltage every 4 miles. I think the only problem would be whether I'm willing to ride the bike until it literally gives up, in case that damages the battery. Would throw it on a charger right away, of course.
Anyway, this 4-bit table would give me enough gradations (6.25% apart) going from full to zero, where zero is bike gives up. Now if I've got more or less load, more or less hills or wind, etc., I would still know how close I am to running out of battery on this bike and could compare mileage ridden that day to the percentage display.
What I don't get is why no manufacturer even enables this, much less does this. (Or maybe there are manufacturers that do?)
Surely all controllers with a better than multi-segment display, from Bosch to Bafang, can handle a 16 entry table lookup for battery percentage - they're just not set up to do this. Matter of fact, the Bafang controller is so lame that even when set up for 52 volts, the battery percentage reads as if a 48 volt battery is being used.
Bafang and others, at least give us a way to load entries in that table.