Bafang m510

[VMG Chris]

So I've got a new version already at the currents/SOC I asked for, but I haven't tested it yet. Not sure about availability yet, but I know not until testing has been done.

I asked about more aggressive settings as you guys had suggested, but I don't think that will happen due to the risk of the BMS shutting down the battery. I'm guessing under load the BMS could shut it down due to voltage drop.

 

[thaeber]

Sounds promising! I‘m curious what I will receive…

 

[ficorama]

Dali someone managed to upgrade firmware of @thaeber?

 

[thaeber]

Dali someone managed to upgrade firmware of @thaeber?

My understanding is that it doesn’t work. I tried it multiple times with no success. Others as well. So don’t waste Your time buddy!

 

[ficorama]

My understanding is that it doesn’t work. I tried it multiple times with no success. Others as well. So don’t waste Your time buddy!

it installed the firmware for me. I just removed the file name ---- 48v!

 

[thaeber]

it installed the firmware for me. I just removed the file name ---- 48v!

You’re kidding me! Did You allready test it?

 

[ficorama]

You’re kidding me! Did You allready test it?

installed without problems. the engine is running . I tried a few hundred meters. I'll be driving tomorrow, so I'll let you know the results.

 

[captainhightop]

You’re kidding me! Did You allready test it?

I followed the same routine for stock firmware, this works from upload to the BESST tool to the final flashing to the drive controller.

I've also edited filename as described above for the new file from github. The final upload doesn't work. Upload to BESST tool works in both cases but final upload to drive only works for stock firmware thus far (for me). Maybe someone could upload a zipped copy to this thread with it already renamed, just to make sure.

 

[thaeber]

installed without problems. the engine is running . I tried a few hundred meters. I'll be driving tomorrow, so I'll let you know the results.

You’re the man! Great! Thanks!

 

[Migli54]

Same problem as you guys... With the original firmware I can flash but with another one it doesn't work, even if I shorten the name...

 

[thaeber]

installed without problems. the engine is running . I tried a few hundred meters. I'll be driving tomorrow, so I'll let you know the results.

Could You please exactly specify the changed file name mate?

 

[ficorama]

should be deleted, ---- 48v

 

[ficorama]

at least I hope it loaded.

 

[thaeber]

at least I hope it loaded.

You can check it with the BESST tool

 

[captainhightop]

at least I hope it loaded.

Did you see 2 progress bars:
1. uploading to BESST

2. when you plug the motor back in and it uploads from BESST to motor?

Then the test light should appear on the besst box (blue light)



(the above is a screenshot from 1. upload of newer file and 2. besst box update from older file)

I got confused when I first flashed it and thought it was just 1 step, but I then messed it up so badly I've trashed 2 motors. Both of which still are flashable but just don't seem to communicate with any displays now, so careful guys!

Also the file sizes are slightly different in a hex compare, not sure if this is valid as it's not a format I'm familiar with

 

[SchadowMaster]

As I understood, is the new Firmware just to get the same performance as much as possible when the battery voltage drops? Without power saving mode at a certain percentage?

 

[captainhightop]

As I understood, is the new Firmware just to get the same performance as much as possible when the battery voltage drops?

Yeah apparently a lot of attenuation of the power on in the original f/w at levels that most consider a bit too early. I've not done a long enough ride to hit it yet though as I only got down to 56% battery on the one long ride I did and now my motor is toast due either mine or bafang's incompetence.

 

[ficorama]

Did you see 2 progress bars:
1. uploading to BESST
View attachment 87823
2. when you plug the motor back in and it uploads from BESST to motor?
View attachment 87824

Then the test light should appear on the besst box (blue light)

View attachment 87825

(the above is a screenshot from 1. upload of newer file and 2. besst box update from older file)

I got confused when I first flashed it and thought it was just 1 step, but I then messed it up so badly I've trashed 2 motors. Both of which still are flashable but just don't seem to communicate with any displays now, so careful guys!

Also the file sizes are slightly different in a hex compare, not sure if this is valid as it's not a format I'm familiar with

I'll check tomorrow and let you know

 

[captainhightop]

I'll check tomorrow and let you know

Ironically, it was when I checked to see if I really did update it later on that I screwed everything up, so good luck (or at least have better luck than I did). I think I had a partial upload that I pulled the lead out too early but it seemed to still upload later even after it was trashed, it is a super weird error, BESST tool can still communicate with both the working displays and the controller too.

 

[thaeber]

I'll check tomorrow and let you know

Do it. Do it now.

 

[Kyokushin]

Long name possibly might cause the issue so you may try name it even „xdbafang.bin” and shall work.

 

[captainhightop]

Long name possibly might cause the issue so you may try name it even „xdbafang.bin” and shall work.

Nice idea, but I tried the rename to a short file name, moved it to a shorter path. Also as a control I renamed the known working original bin file as follows:

And that still worked, so any other ideas?

 

[VMG Chris]

FYI, the firmware I received from Bafang installed no problem

Unfortunately when I went to test it today, the rain came back, and out trails are saturated again.

It worked fine on the quick carpark test, before I left for the trails to do the range test.

 

[thaeber]

FYI, the firmware I received from Bafang installed no problem

Unfortunately when I went to test it today, the rain came back, and out trails are saturated again.

It worked fine on the quick carpark test, before I left for the trails to do the range test.

Now the challenge is to get the firmware for the community here. My contact to Bafang is Chili Shen, and she‘s unavailable for a couple of days for good reason. So we have to be patient. If You could share the firmware in alignment with Bafang, and without jeopardizing Your VMG business, that would be great!

 

[VMG Chris]

Now the challenge is to get the firmware for the community here. My contact to Bafang is Chili Shen, and she‘s unavailable for a couple of days for good reason. So we have to be patient. If You could share the firmware in alignment with Bafang, and without jeopardizing Your VMG business, that would be great!

I've been specifically asked not to share it until it's been tested.

We've had the wettest Summer and Autumn on record, and rain forecast for another week.

If we get a break in the weather, I'll find a road hill I can do loops on and do a range test.

 

[Jensens e10 m600]

Hi. Is m510 worth bying or should i Stick with the m600?
And Can i use the 840wh17a battery from e10.

 

[KaroKönig]

I've been specifically asked not to share it until it's been tested.

We've had the wettest Summer and Autumn on record, and rain forecast for another week.

If we get a break in the weather, I'll find a road hill I can do loops on and do a range test.

It’s a pity that BAFANG doesn't test its software itself before selling the motors
What do BAFANG think the engines are used for? Go shopping at the weekly market?

 

[thaeber]

Hi. Is m510 worth bying or should i Stick with the m600?
And Can i use the 840wh17a battery from e10.

Yes You can use the battery, I use it myself. If You read through the tread, what’s Your takeaway? If You are lucky, the M510 motor works flawless like mine (beside of the battery attenuation topic). But there are many reports on malfunctioning here. The M600 is suffering Sprague Bearing failures and the firmware is very aggressive in regards of power supply. So You have to decide in between the bad and the worse but You need to do it on Your own…

 

[Puschtrale]

I just tried to update the firmware of my m510 to this one CRX10NC4814i101003.0-28-2230-boot3.0-20220218085143.bin
Unfortunately when uploading it to Besst Tool an error occurred and the error led was blinking and the Besst Tool giving a permanent "Piiep". I resetted Besst Tool and disconnected it from my Controller (DP C241). Unfortunately now my controller is not woeking anymore - it just gets no electricity from my battery. When connecting it to the Besst Tool i cannot read parameters - so no connection is possible and i can therefore not check where the problem is and what i can do.

 

[captainhightop]

I just tried to update the firmware of my m510 to this one CRX10NC4814i101003.0-28-2230-boot3.0-20220218085143.bin
Unfortunately when uploading it to Besst Tool an error occurred and the error led was blinking and the Besst Tool giving a permanent "Piiep". I resetted Besst Tool and disconnected it from my Controller (DP C241). Unfortunately now my controller is not woeking anymore - it just gets no electricity from my battery. When connecting it to the Besst Tool i cannot read parameters - so no connection is possible and i can therefore not check where the problem is and what i can do.

Sounds very like the issue I've had, although I can still communicate and flash the controller with the BESST tool. The original HMI won't come on at all, but the 2 others I have will turn on when attached to the BESST tool and the motor, I can even run the motor calibration and it spins. So frustrating that we're having these issues. Both M600 and M510 motor's are not communicating directly with displays at the moment for me.

I've now got the Innomaker CANBUS dongle and also all the components to make the opensource ebike controller on a prototyping board, so maybe I can figure out what's gone wrong once I get time to connect it all up.