Bafang m510

patdam

Well-known member
Jan 17, 2019
902
601
france
Today I tried all the firmware I have in the rocky climb.
I have an FC1 with base firmware 3.1 as the basis. I have horrible cutoffs and a horrible rattling sound from the motor. It looks like I have torque sensor issues, because in the beginning I only had cutoffs on low-steep climbs and low assist levels, and now I have horrible cutoffs on technical climbs with strong assist levels (this is all on 3.1 firmware). My supplier sent me a warranty motor (unfortunately, it's still an FC1, but with 3.6 firmware). But that's just the backstory.
For the reason that I can't get my warranty motor yet and I have a besst I decided to play with the firmware.
1) 3.1 cs is the most natural FW. Like it, but I have the same cutoffs unfortunately. Riding without pleasure.
2) 3.6 is a terrible FW. Really dangerous. After you stop pedalling, the motor gives full power for 2-3 seconds. Yes, I read about it, but I didn't think it was that crappy. But I don't have cutoffs on this FW, hi bafang, if you decided to fix the crappy torque sensor behaviour this way, I'm not your customer.
3) 3.2 is something between 3.1 cs and 3.6. As a result, I have less cutoffs, but still have assist after stopping the pedaling. I also noticed that with 3.2FW I have a weak walkmode (but I had about 20% battery and that may be the reason).
I realize that I have a defective motor, but the behavior of the different FWs is so various.
The questions still remain:
1) Are there any FWs for the FC1 that you can suggest trying?
2) Is Walkmode on 3.2 so weak or was my battery capacity low?
3) I was playing around with BESSTpro, changing parameters (mostly angle and acceleration). When I change FW, those parameters don't change. Is this normal? Also, when the Besst box writes the FW to the controller, I get error 30 on the display, but the box still changes the FW. Is this ok?
4)Torque sensor calibration via besst. I have only been able to do it once, it is no longer performed. Is this normal?
Thanks in advance and sorry for any mistakes, English is not my first language :)
I use the 3.2, I prefer it at 3.1-CS (powerfull ramp a bit more slow) i haven't gap between cranks turn stop and motor stop. I don't know how is work the walk mode ? i never use it. For walk mode i use the throttle with mechanical range limit to walk at 4 km/h max. I find The gap with the 3.6 interesting in technical uphill, the raison why i remove it is mostly for the crack noises with it when you change speed

I never could perform torque calibration ? my torque sensors (older fail and newer sent by bafang) as never been recognized by the BESST tool. Or the calibration is weel performed, without any informations to indicate it ?

I have systematically "ERR 30" with firmwares who weel downloaded in BESST tool but who can't updated to the controle . For those i have checked (not all), the firmware who download and those who don't, have different 2 first digit in the file.bin. Someone with the same rev codification, exemple: bafang have sent me 3 x 3.6 rev, only one functioning with my controller.
 

thaeber

Well-known member
Jan 26, 2021
887
769
Bruchsal, Germany
This one is the firmware for very first M510. Bootcode 0x89 - which looks like controller taken from M600.

Versions 3.1cs, 3.2, 3.6 are second revision - boot code 0x90

Anybody has 36V version for latest FC1.0 - third revision - bootcode 0x91?
Thanks.
So You think this doesn’t load to my FC1.0 Rev I? Any risk? Thanks!
 

Dado

Active member
Jun 28, 2022
691
462
Bratislava
Iscander, it was mention allready here. But once again...

View bin file and switch to HEX view. Second byte is revision code i and E.
First byte boot code:

0x89 - very first version - rev. E
0x90 - rev "i"
0x91 - also rev "i" , but not compatible with previous - last one from FC1.0 controllers
0x71 - latest FC2.0 controller

Theaber, that is right, wont go into rev "i" (aka boot code 0x90 or 0x91). No risk, motor just wont flash.
 

iscander13

Member
Oct 11, 2021
185
59
earth
Iscander, it was mention allready here. But once again...

View bin file and switch to HEX view. Second byte is revision code i and E.
First byte boot code:

0x89 - very first version - rev. E
0x90 - rev "i"
0x91 - also rev "i" , but not compatible with previous - last one from FC1.0 controllers
0x71 - latest FC2.0 controller

Theaber, that is right, wont go into rev "i" (aka boot code 0x90 or 0x91). No risk, motor just wont flash.
So I can find out the version of the controller by looking at what the second byte in my current FW is?
 

Dado

Active member
Jun 28, 2022
691
462
Bratislava
Hello Theaber. This one is with boot code 0x91 - so latest, third revision of FC1.0 controller. Now I dont remember if your M510 is second or third revision. You can flash into your motor firmwares version 3.1 3.1cs 3.2 3.6? If so you have second revision of FC1.0.

Yes, there is big mess and non logical things in Bafang labeling as you wont find out, which FC1.0 you have just by looking at motor. From controller label or motor label not possible to find out. You need to send bootloader version request over BESST and motor will reply with bootloader version. It is the following one in Besst. "X10N-3.1" is latest FC1.0 controller with boot code 0x91

1682527853883.png
 

thaeber

Well-known member
Jan 26, 2021
887
769
Bruchsal, Germany
Hello Theaber. This one is with boot code 0x91 - so latest, third revision of FC1.0 controller. Now I dont remember if your M510 is second or third revision. You can flash into your motor firmwares version 3.1 3.1cs 3.2 3.6? If so you have second revision of FC1.0.

Yes, there is big mess and non logical things in Bafang labeling as you wont find out, which FC1.0 you have just by looking at motor. From controller label or motor label not possible to find out. You need to send bootloader version request over BESST and motor will reply with bootloader version. It is the following one in Besst. "X10N-3.1" is latest FC1.0 controller with boot code 0x91

View attachment 112811
Thanks Dado. I have Version 2, Rev „i“. What a mess. So next attempt to Chili.
 

patdam

Well-known member
Jan 17, 2019
902
601
france
DSCF1895.JPG
Does somebody can say me the function of this wire with 2 cables (red and black) on the main wire to the HMI ? following his length, it's seem to plug inside the frame ?
 

patdam

Well-known member
Jan 17, 2019
902
601
france
Guys, what range u have on M510 FC1.0 and battery capacity? Customer is telling me, he has double consumption to bosch.
Personally for exemple on last ride with E10, 33 km, 1100 D+, i had consumed 28% of my 17A/h battery, my weight +-96 kg. i have used +- 60% level 1, 30% level 2 , 10% level 3. I find the M510 more powerfull, and especially more torque and less consumption than my previous motors (M500, shimano E8000)
 

thaeber

Well-known member
Jan 26, 2021
887
769
Bruchsal, Germany
So here’s the latest 36V firmware from Chili.

@Dado: Could You please do me the favor to check if this suits my M510 FC1 Rev. „I“?
 

Attachments

  • MMG522C3619F802008.1_32_28-2230_RLS0585_PAR0811-1_20221109_1840.bin
    81.6 KB · Views: 171

krokan

Member
Oct 20, 2021
55
21
B
So here’s the latest 36V firmware from Chili.

@Dado: Could You please do me the favor to check if this suits my M510 FC1 Rev. „I“?
Hi,
just open the file with: HexEd.it - Browser-based Online and Offline Hex Editing
you'll see 71

as Dado said:

0x89 - very first version - rev. E
0x90 - rev "i"
0x91 - also rev "i" , but not compatible with previous - last one from FC1.0 controllers
0x71 - latest FC2.0 controller
 

thaeber

Well-known member
Jan 26, 2021
887
769
Bruchsal, Germany

PH1L1PP3

New Member
Apr 27, 2023
99
56
France
Hi all,
noob questions:
1/ Why salers offer M510 > 36V, 43V or 48V. Does it mean 3 differents motors? Thought the motor could run under these 3 voltages.
2/ About protocols: UART, CAN, it is regarding the motor connection or the LCD HMI.
Thanks for your help.
 

EMTB Forums

Since 2018

The World's largest electric mountain bike community.

555K
Messages
28,044
Members
Join Our Community

Latest articles


Top