Bafang m510

[Kyokushin]

3.2 is Ok, just you wont get all the juice from battery (firmware is setup to 52V battery).

I am curious the max current. Mostly when battery have higher voltage (in that case 52V) then amperage is lowered to keep the same output power level.

@Rob Rides EMTB if it does not read the serial number then it wont update, then you have two option:
1) click connect/read few times more till it read (its piece of crap, it just need a dozen of clicks to read SN)
2) type serial (or whatever) in the empty field (and also shall work)

 

[Rob Rides EMTB]

So it reads controller serial, u choose firmware and then update button. There is a progress bar then ( takes like 5s) and uploading to Besst first.
This did run with no error message, right?

If so, then just unplug and plug connector and it should start to flash controller. ( Takes up to 10sec).

Correct. But when I plug back in nothing happens.

 

[Rob Rides EMTB]

@Rob Rides EMTB if it does not read the serial number then it wont update, then you have two option:
1) click connect/read few times more till it read (its piece of crap, it just need a dozen of clicks to read SN)
2) type serial (or whatever) in the empty field (and also shall work)

Thanks. Reads serial OK, its just the last step that doesnt work. Am on a M1 Mac so probably this is causing issues maybe.

 

[Kyokushin]

Thanks. Reads serial OK, its just the last step that doesnt work. Am on a M1 Mac so probably this is causing issues maybe.

I am using that on VMware from Pc->pc and never had issue with update. When it uploaded fw to controller, then it worked. I had only issues with reading serial.

 

[Rob Rides EMTB]

Strange. Have tried about 10 times, and using 2 BESST boxes! Every time exactly the same, they fail to write the firmware to motor on the final step, nothing happens.

 

[Kyokushin]

Strange. Have tried about 10 times, and using 2 BESST boxes! Every time exactly the same, they fail to write the firmware to motor on the final step, nothing happens.

I may be wrong but it looks like two revisions of M510 engine.

I have four firmwares for M510.
First byte of firmware is a lock for the flash.

Three of firmwares have the:
- "90" (CRX10NC4814i101003 1-28-2230-boot3 0-20220127132519.bin, CRX10NC4814i101003.2-28-2230-boot3.0-20220523131321.bin, CRX10NC4814i101003-1-cs-28-2230-boot3-0-20220517161110-48v-M510.bin) in first byte,
- and one have "89 (CRX10NC4814i101003.0-28-2230-boot3.0-20220218085143----48v.bin this one)"

For example, from what we know in past:
- 89 means M600
- 88 means M500

So if you change first byte to that one is corresponding your controller then it will flash, but i do not know what will happen and why it seems to be different, and what consequences will be.
I have used this to override and flash M500 by M600 firmware and vice versa, but these controllers were almost same (difference in number of shunts, mosfets). In m510, we do not know.

 

[Migli54]

I may be wrong but it looks like two revisions of M510 engine.

I have four firmwares for M510.
First byte of firmware is a lock for the flash.

Three of firmwares have the:
- "90" (CRX10NC4814i101003 1-28-2230-boot3 0-20220127132519.bin, CRX10NC4814i101003.2-28-2230-boot3.0-20220523131321.bin, CRX10NC4814i101003-1-cs-28-2230-boot3-0-20220517161110-48v-M510.bin) in first byte,
- and one have "89 (CRX10NC4814i101003.0-28-2230-boot3.0-20220218085143----48v.bin this one)"

For example, from what we know in past:
- 89 means M600
- 88 means M500

So if you change first byte to that one is corresponding your controller then it will flash, but i do not know what will happen and why it seems to be different, and what consequences will be.
I have used this to override and flash M500 by M600 firmware and vice versa, but these controllers were almost same (difference in number of shunts, mosfets). In m510, we do not know.

Hello,

It is correct, because of the current situation and the problems of supply of electronic components worldwide, Bafang had to review the BOM of the controllers and the Chip are not provided by the same supplier. So the architectures are different and so are the firmwares of the microcontrollers....

 

[Dado]

Strange. Have tried about 10 times, and using 2 BESST boxes! Every time exactly the same, they fail to write the firmware to motor on the final step, nothing happens.

That is strange, Rob. Once firmware sucesfully loaded to Besst, you does not even need computer. You just plugging motor controllers one by one and it updating firmware (no need then to click anything on computer)

Hmm, what to propose? Have you tried to flash other motor with your Besst and with the same procedure?

 

[Rob Rides EMTB]

Anyway of finding my revision of M510?

 

[Dado]

I am curious the max current. Mostly when battery have higher voltage (in that case 52V) then amperage is lowered to keep the same output power level.

@Rob Rides EMTB if it does not read the serial number then it wont update, then you have two option:
1) click connect/read few times more till it read (its piece of crap, it just need a dozen of clicks to read SN)
2) type serial (or whatever) in the empty field (and also shall work)

Hello mate. Thats not true - motor controller still gives hardcoded current, doesnt matter what voltage of battery u have currently.

If the current readings are good calibrated, controller is putting even 15 - 16 A. That means with full 52V battery you would get even 900W!

Will record a video in the evening of the readings during ride.

 

[Dado]

Rob, could be as Migli writing, you have different microcomputer in your controller and this version does not fit, so it wont flash.

 

[Kyokushin]

Hello mate. Thats not true - motor controller still gives hardcoded current, doesnt matter what voltage of battery u have currently.

If the current readings are good calibrated, controller is putting even 15 - 16 A. That means with full 52V battery you would get even 900W!

Will record a video in the evening of the readings during ride.

Okay.
I asked because the max current is in the firmware, and for example of M500 its 15A for 36V firmware, 13A for 43V and 10A for 48V (stock baseline firmwares), so i though when the produced the 52V firmware for M510 they also changed current, but if not then OK. It seems they only made something strange with voltage readings.

 

[thaeber]

Hello Rob

Looks like didnt flash. Try again, it should work.
3.2 is Ok, just you wont get all the juice from battery (firmware is setup to 52V battery).

If you have contacts there, can you ask them for 48V firmware and report the bug, pls?

View attachment 91344

The big issue with 52V firmware is battery attenuation. The battery will cut off way to early.

 

[Dado]

Okay.
I asked because the max current is in the firmware, and for example of M500 its 15A for 36V firmware, 13A for 43V and 10A for 48V (stock baseline firmwares), so i though when the produced the 52V firmware for M510 they also changed current, but if not then OK. It seems they only made something strange with voltage readings.

Wouldnt tell something strange, just they mapping % to 52V battery. They just forgot to put back to 48V I would say. They had maybe 52V battery on a developing bench.

And yes, still higher battery voltage system has lower DC current to have max power cca the same.

 

[ficorama]

@Rob Rides EMTB I had the same situation, I can't install the FW at all. reads SN, transfers FW from computer to besst but fails to install in engine. on the other m510 engine I have, everything works normally! I installed the "52V" FW, then the earlier FW. I don't think the controller works! here is a picture of the failure.

whatever to try, disconnect and reconnect the controller, disconnect the controller after reading the SN and connect after loading the Fw in besst... it just doesn't work. looks like the controllers are bad?

 

[ficorama]

Wouldnt tell something strange, just they mapping % to 52V battery. They just forgot to put back to 48V I would say. They had maybe 52V battery on a developing bench.

And yes, still higher battery voltage system has lower DC current to have max power cca the same.

i tried driving "52v" FW. it has a slightly softer start, and the power is equal. per bms-battery at 50% and on the screen 6%! unfortunately I didn't look at the voltage.

 

[Dado]

i tried driving "52v" FW. it has a slightly softer start, and the power is equal. per bms-battery at 50% and on the screen 6%! unfortunately I didn't look at the voltage.

Mate, it was mention already 3 times, you getting 6% on display as it is mapped to 52V system battery. Correct % is BMS. You wouldnt be able to draw battery till the end due to higher cut off voltage with 52V firmware.

 

[Dado]

@Rob Rides EMTB I had the same situation, I can't install the FW at all. reads SN, transfers FW from computer to besst but fails to install in engine. on the other m510 engine I have, everything works normally! I installed the "52V" FW, then the earlier FW. I don't think the controller works! here is a picture of the failure.

whatever to try, disconnect and reconnect the controller, disconnect the controller after reading the SN and connect after loading the Fw in besst... it just doesn't work. looks like the controllers are bad?

So would be that different microcontroller then, have u read previous posts? On other M510 you have different - so it flashed. Bafang is just complicating it and we will have soon tons of different firmwares. Situation with microcontrollers is as it is on the market.

 

[ficorama]

Mate, it was mention already 3 times, you getting 6% on display as it is mapped to 52V system battery. Correct % is BMS. You wouldnt be able to draw battery till the end due to higher cut off voltage with 52V firmware.

matte. I wrote to you all a long time ago that this fw is not valid, and that it shows wrong values. I have also written a couple of times that I was not able to install any firmware in one engine, while I can install it normally in another engine. i got it all! It seems that most people on the forum do not read or want to read what someone else writes. I think it is pointless to write anything more. Thanks everyone.

 

[patdam]

Strange. Have tried about 10 times, and using 2 BESST boxes! Every time exactly the same, they fail to write the firmware to motor on the final step, nothing happens.

have you try to reduce the file name ? to CRX10NC4814i101003 1-28-2230-boot3 0-20220127132519.bin for exemple, i haved the problem one time, after reducing i can finalize the upload with BESST

 

[Dado]

matte. I wrote to you all a long time ago that this fw is not valid, and that it shows wrong values. I have also written a couple of times that I was not able to install any firmware in one engine, while I can install it normally in another engine. i got it all! It seems that most people on the forum do not read or want to read what someone else writes. I think it is pointless to write anything more. Thanks everyone.

Dont wanna argue, but is valid for specific microcontroller used. From HW version of controller should be able to decode, what microcontroller is used.
We can try it, open up both your 510 and compare microcontroller label - if they didnt scratch label from chip - chineese are doing it.

And is with a bug - it is not 48V as filename stating.

 

[Kyokushin]

I will try to re-organize a bit the firmware section for M510 on git, to make two revisions and correct the name of this 52v firmware. Could you write the exact name of that firmware related to 52V?

 

[Dado]

Thats a good idea Kyoku.

I havent understand that date in filename. Strange dates there are.
I would say only that beginning number , type of controller ( looks like we could have more microcontrollers for next production batches) , default speed , wheel, circum.

What do u think?

Anyway, somebody knows what means 4 digit after "i"?

 

[Kyokushin]

In the past it was for example:
CRX10NC3617i142017.7-28-2230-20200911.bin
36 - voltage
17 - amperage
1420 - controller version (m500, 1320 was M600)
17.7 - firmware version
28 - wheel size
2230 - circumference
20200911 - date of firmware generation

But in M510 its meessed, and files we have so far are:
CRX10NC4814i101003 1-28-2230-boot3 0-20220127132519.bin
CRX10NC4814i101003.0-28-2230-boot3.0-20220218085143----48v.bin - THAT ONE IS FOR DIFFERENT REVISION i suppose
CRX10NC4814i101003.2-28-2230-boot3.0-20220523131321.bin
CRX10NC4814i101003-1-cs-28-2230-boot3-0-20220517161110-48v-M510.bin

it seems also the amperage and voltage be the same, after that we have:
3.0., 3.1, 3.2, but i do not know what does it may mean - maybe controller revision, but that would result there are three, not two, but we have only two firmware locks.

I dunno, maybe someone who is dealing the bikes might just ask Bafang in straight about number of revisions.

 

[thaeber]

Wise we have to act. Patiend we have to be. On Bafang we must trust

 

[ficorama]

20220218085143----48v.bin - THAT ONE IS FOR DIFFERENT REVISION i suppose

I only managed to install that firmware in the engine that is now on the shelf. @Rob Rides EMTB you could probably install that FW. @Kyokushin send Rob that FW.

 

[Kyokushin]

It will be better for ask bafang the 'stock' firmware (to have a backup/rollback plan) that you have @Rob Rides EMTB installed before flashing anything.

 

[thaeber]

20220218085143----48v.bin - THAT ONE IS FOR DIFFERENT REVISION i suppose

I only managed to install that firmware in the engine that is now on the shelf. @Rob Rides EMTB you could probably install that FW. @Kyokushin send Rob that FW.

Is this Your current firmware? The one only You could flash, that paralyzed @Puschtrale Controller? That was taken off Github due to be faulty on other M510?

 

[Dado]

Look guys, screenshot from video.
That was really just a higest peak from whole recording. Average power cca 740W. Then temperature limitation kicked in at around 95C. At 104C was getting average cca 550W.

Will load video, just lazy to cut now.

 

[ficorama]

Is this Your current firmware? The one only You could flash, that paralyzed @Puschtrale Controller? That was taken off Github due to be faulty on other M510?

that firmware is in the engine that I am not currently driving. I have to try these days if I can install that firmware again, or the controller is blocked.