Bafang M510 Firmware thread

[Tomblarom]

Actually i don't have overrun on the last FW for FC1

Which fw version is that? Maybe it can be shared in the forums. Extraction is easily possible.

 

[iscander13]

Which fw version is that? Maybe it can be shared in the forums. Extraction is easily possible.

I have 3.6 on my FC1, but many people have reported that this FW has overrun, which I can also confirm. I had overrun on this FW when I first put the motor on the bike. But then my friend advised me to change the position of the magnet on the spoke. I did that and have no longer significant overrun on the 3.6 FW.

What do you mean "Extraction is easily possible." ?

 

[Tomblarom]

What do you mean "Extraction is easily possible." ?

If you want a specific firmware and have the Bafang controller, that has it, it can be extracted. I did that already on all recent Bafangs.

 

[iscander13]

If you want a specific firmware and have the Bafang controller, that has it, it can be extracted. I did that already on all recent Bafangs.

Okay. How can I do that? I have a firmware on FC2 that has not been seen on this forum yet, and the seller of the controller has not sent the bin file yet

 

[Karamba!]

Can it be done through Besst tool?

 

[Tomblarom]

Can it be done through Besst tool?

No. At least not from what I know.

 

[iscander13]

That would be great if you get bin file.
Let us know how this version behave, if no big overrun after stop pedalling. Where did you buy controller?

Use Besst Pro for M510.

Dado, Gents, the supplier sent me bin files. I haven't checked them myself.

About behaviour. I have one day to ride the e-XC with ~1000m climb where I was more or less able to evaluate the motor performance.
1) More natural behaviour compared to the FC1
2) No overrun
3) Good and smooth walkmode.
4) Battery consumption. Didn't do a real test (from 100% to 10% (below 10% is almost unresponsive when switching levels)) but 2 trips made with 3 days in between showed 1755m of altitude, 63km of distance and 25% SoC on display. But this happened mostly at the first two support levels (20% and 30% setting on the controller).

 

[Dado]

Hello Iscander.

Thanks for sharing. Yep, looks like some custom versions according the version numbers. Just is from november 2022 - so quite old. Recent default firmware is from January 2024. Adding also 36V and 19A version. Your is 15A.

Who will test Iscander firmwares for behaviour?

 

[Karamba!]

Hello Iscander.

Thanks for sharing. Yep, looks like some custom versions according the version numbers. Just is from november 2022 - so quite old. Recent default firmware is from January 2024. Adding also 36V and 19A version. Your is 15A.

Who will test Iscander firmwares for behaviour?

Hey Dado, where I can find the Jan 2024 firmware you speak of? Is it for 48v?

 

[Dado]

Attached. It is funny as I saw already 3 firmwares 48V with same version number 10.1 - but size of bin file is different. What I found out - some bug patches on battery CAN communication (with old firmware worked motor also when charging). Mess.

 

[Karamba!]

Attached. It is funny as I saw already 3 firmwares 48V with same version number 10.1 - but size of bin file is different. What I found out - some bug patches on battery CAN communication (with old firmware worked motor also when charging). Mess.

I should better stay away then . Not mayor complains on my current 10.1

 

[Dado]

Yes, this 10.1 looks good. Also hearing good reactions from people (what we can not say about M500). One disadvantage, throttle is hardcoded to 32kmh. For guys who are used to ride over this speed then it is pain. But have in plans to trick this over old way. By cheating speed sensor impulses.

I would say they hardcoded this parameter in a firmware, so if somebody has a custom firmware where throttle works unlimited (or up to set pedalling speed limit) that would be great to share.

I am affraid Bafang is moving away from throttles (M820) and also are going to hardcode speed (saw at M620).
Its again little non logical with M510, I will set speed limit 25kmh for pedalling, but throttle still works up to 32kmh. And thats just one If (ThrotleMaxSpeed>PedallMaxSpeed ) ...

And if you wanna put some pressure on your motor - with 43V firmware and 48V battery you can peak 820W !

 

[iscander13]

Hello Iscander.

Thanks for sharing. Yep, looks like some custom versions according the version numbers. Just is from november 2022 - so quite old. Recent default firmware is from January 2024. Adding also 36V and 19A version. Your is 15A.

Who will test Iscander firmwares for behaviour?

What's the difference between 19A and 15A? I'm using a 48V FW and to my taste it works as it should (you can find my brief review in the post with bin files). No questions about the FW at the moment.

 

[Dado]

At least +4 Amps. )

 

[Waynemarlow]

I've had a bit of a realisation that the M510 controllers at 52 volts know that it is a 52 volt battery and will shut off the motor at 46 volts on the battery even without any CAN signals ( home built battery ). Thats 3.2 volts a cell. My old M600 motor used to run the battery fully down to below 3.0 volts a cell which was good as I was able to use nearly the entire battery capability.

Are there any firmwares that any of us are using that will allow lower voltages on the 52 volt batteries ?

 

[Dado]

46 is indeed high for 48V firmware. Have not tested behaviour with 52V battery, it did work so far with one cell up battery.
Then just K1 BBR. Working also with 52V battery. And you can discharge down to 3.0V, even deeper...

 

[Waynemarlow]

Thanks for the reply Dado. This high cutoff is stopping me using nearly 100Wh of a 800Wh battery. In 3 years the battery technology will have moved on so far that my 800Wh battery will be redundant. How many Ebikes batteries are going to be charged 1000 times a year ( typical cells are based on a 3000 - 5000 charge cycle ) ?

At the end of the day I understand why a high cutoff increases the lifetime use of the battery but in our application, it is just so wrong to set the cutoff so high.

 

[Dado]

Not possible to charge 1000 times a year. Nickel Cadmium Liions have written 400 cycles to like 80% or 75% capacity. There are also cells with 1000 cycles (when maintain some conditions). And then LiFePo with 4000 cycles.
Bafang is doing this on purpose, and this was the reason why I was thinking how to trick it with BBR.

 

[iscander13]

Hey, guys. Does anyone have the same issue?
Predistory.
Second time I washed my bike in 2 years .
The first time I flooded the handlebar remote and this time I covered it with a bag beforehand .
Dried the bike for a few days.
Disconnected the motor-display cable just in case. Last time when the remote was flooded, there was a flash when the battery was connected. The bike did not turn on immediately. Removed-inserted the battery and connectors on the monitor. The bike turned on without any problems. Everything was ok for a while. Then I noticed that the motor produces power only at high cadence (in all modes). If cadence is low support is very little (60-80 watts). Turned off and on, the problem disappeared, but it seemed that the motor is too powerful in the first two modes. Battery consumption increased (on 1300 m of ascent 60% of the battery is gone).
End of the prehistory.
Today I plugged in the besst and found that the assist levels were reset. Has anyone had this happen? Any idea why this happened?
On the picture settings before and after

 

[Dado]

Hmm, interesting, have not seen yet to reset the settings. After reflashing firmware it is re-set to defaults.
Note: I have noticed new controllers are not taking high speed limit. If I do set for example 80 kmh, then after motor restart it is back to 45 or so.

Put more acceleration.