Bafang M500 and M600 motors
- Thread starter Rob Rides EMTB
- Start date
We currently have access as DIY to much more advanced technology than what the Ebike manufactures put inside.
If you tell me 3 years ago that I would have an EBike with electronics that runs firmware in Python, and have Wifi and Bluetooth that let me develop and program instantaneously with my phone, I would call you crazy!!
As EBike DIYers, we have many advanced technology because we decided to develop it for our own interests, so let's take advantage of it!!
For the ones that lack the knowledge or time to do his own builds, at least can try to go ask to a friend or bicycle shop and show them this project information and ask for them to build for yourself.
The EBike board is ready and attached on the 3D printed motor cover.
And here is the EBike board alone (including the magnetic encoder sensor green board):
I wish to make the board robust to vibrations and water. Since I can program the board by wireless, maybe I will cover the board and wires with silicone, like potting the electronics, here an example:
And here is the EBike board alone (including the magnetic encoder sensor green board):
I wish to make the board robust to vibrations and water. Since I can program the board by wireless, maybe I will cover the board and wires with silicone, like potting the electronics, here an example:
So, after the night, the silicone got hard as expected. Note that I also protected the connectors with silicone:
And here is the very first test. I had to increase the length of the battery and motor phase wires, doing extensions. With that, all seems good:
And now testing if everything works well - I have the display connected where I can see for instance that brakes are working:
www.youtube.com
And the throttle code, I added it for the first time. There is not specific throttle curve yet:
Next step is to put the final black silicon to make sure everything is water prof. Soon I will be riding :bolt: :thumb:
And now the best news!!
I received the VESC Flipsky Mini FSESC6.7. It is small enough to be placed inside the motor case, as seen here:
With the experience I now have, I am pretty sure I can build a smaller EBike board to put on top on that VESC, and put everything inside the motor case!!
But my current battery is a 14S / 52V, so I would need to build another battery as 13S / 48V, to work with this VESC as max battery for it is 13S.
So for now I will keep my current build, with VESC Flipsky 75100 placed outside of the motor case. I will also ride and have fun, and if everything goes well, then I can do this improvement. Meanwhile, I will also be building the display, mainly developing the firmware for it -- previous version, the firmware was developed in C and on this new version, will be in Python.
And here is the very first test. I had to increase the length of the battery and motor phase wires, doing extensions. With that, all seems good:
And now testing if everything works well - I have the display connected where I can see for instance that brakes are working:
Bafang M500 with VESC Flipsky 75100 + AS5047 + EBike board running Python firmware and installed
This is a Bafang M500 mid drive motor, being drive by the VESC motor controller, in this case the Flipsky 75100. Also a AS5047 magnetic encoder board is bein...
www.youtube.com
And the throttle code, I added it for the first time. There is not specific throttle curve yet:
Next step is to put the final black silicon to make sure everything is water prof. Soon I will be riding :bolt: :thumb:
And now the best news!!
I received the VESC Flipsky Mini FSESC6.7. It is small enough to be placed inside the motor case, as seen here:
With the experience I now have, I am pretty sure I can build a smaller EBike board to put on top on that VESC, and put everything inside the motor case!!
But my current battery is a 14S / 52V, so I would need to build another battery as 13S / 48V, to work with this VESC as max battery for it is 13S.
So for now I will keep my current build, with VESC Flipsky 75100 placed outside of the motor case. I will also ride and have fun, and if everything goes well, then I can do this improvement. Meanwhile, I will also be building the display, mainly developing the firmware for it -- previous version, the firmware was developed in C and on this new version, will be in Python.
Detail of the squished silicone, after tightening the engine cover:
I went for a test ride - it works very well: pedal very sensitive, fast response and high torque:
I am not very happy the way that cables come to outside - I can improve that a lot. But, why bother if soon I may jump to have the new version with both VESC + EBike board inside the motor case?? For now I will just put there silicone on hole and wires, to make sure it gets water prof and then I will be riding 8)
I went for a test ride - it works very well: pedal very sensitive, fast response and high torque:
I am not very happy the way that cables come to outside - I can improve that a lot. But, why bother if soon I may jump to have the new version with both VESC + EBike board inside the motor case?? For now I will just put there silicone on hole and wires, to make sure it gets water prof and then I will be riding 8)
Display
And I did finish the display. The schematic is so simple!! Only 11 wires to solder:
I already tested and it works. Early tests showing the state of POWER, UP and DOWN buttons:
It is not yet fully assembled because currently is waiting for the silicone to harden:
When installed on my handle bard, will be like this, and fully water prof:
Details of the build.
One connector is the display connector to the original Bafang M500 harness cable. The other round connector is to connect to the 860C display remote keypad I bought on Aliexpress:
Very clean and simple:
And now there are two wireless devices connected to my home wifi router, one device is the ESP32-S3 from the EBike board and other device is the ESP32-S2 from this display. I can select which one I want to edit the Pyhton firmware or simple open a second window to select the other board and so have access to both Python firmwares at the same time -- that screenshot is from my phone! I am really amazed to have such advanced technology!!
And I did finish the display. The schematic is so simple!! Only 11 wires to solder:
I already tested and it works. Early tests showing the state of POWER, UP and DOWN buttons:
It is not yet fully assembled because currently is waiting for the silicone to harden:
When installed on my handle bard, will be like this, and fully water prof:
Details of the build.
One connector is the display connector to the original Bafang M500 harness cable. The other round connector is to connect to the 860C display remote keypad I bought on Aliexpress:
Very clean and simple:
And now there are two wireless devices connected to my home wifi router, one device is the ESP32-S3 from the EBike board and other device is the ESP32-S2 from this display. I can select which one I want to edit the Pyhton firmware or simple open a second window to select the other board and so have access to both Python firmwares at the same time -- that screenshot is from my phone! I am really amazed to have such advanced technology!!
Last edited:
hello I have a btf04 battery, I go out with a charge over 98% and after a few km over 7km with +200m but the screen I see that I have 75% left. Then I do not see that the battery level drops so much, I can get to do 30km + 1200m.
The seller tells me that this is because of the cold weather, I go out above 10 degrees Celsius with the sun.
The seller tells me that this is because of the cold weather, I go out above 10 degrees Celsius with the sun.
I did finalize the installation of the small VESC motor controller + EBike board, inside my Bafang M500. It works well as I expected, just like it did on my previous version with the external VESC FLIPSKY 75100.
The final result is this one:
And how is it inside?? Here it is, without that black plastic 3D printed cover:
And more details. Here is the DIY EBike board + the VESC FLIPSKY Mini FSESC6.7:
That DIY EBike board is based on ESP32-S3, that is running the Pyhton EBike firmware and that I program wireless by Wifi. I am sharing the firmware, schematics, photos, etc, here: GitHub - OpenSourceEBike/EBike_EScooter_app_pyhton: EBike / EScooter app developed in CircuitPython, to control a motor by sending commands to VESC motor controller
Here is the schematic:
After testing that every EBike sensor reading were working, I put silicone to make all that wires robust, including the connectors. The idea is to make everything robust and avoid breaking due to the vibrations while I am riding on the mountains:
And finally, I used kapton tape that is very robust and resists to high temperatures:
BUT, there is also some not good news. With all that wires and tight space, it is not possible to have the magnetic encoder sensor working. So, in the end I configured VESC to run sensorless and it works well as I tested before on my previous version with the external VESC FLIPSKY 75100.
Here is picture of the magnetic encoder sensor board. From my tests, I found that no wires can be near and between the magnetic encoder board and the round part of the motor case. But as you can see, I could not do it. Maybe someone can improve the wire routing but I decided to stop here. And a picture of the 3D printed cover with the magnetic encoder board, that I tried to make working:
Conclusions
Build with VESC FLIPSKY Mini FSESC6.7:
This build with VESC FLIPSKY Mini FSESC6.7 is the most clean possible. I think no one will understand that VESC is inside, that your EBike is running Pyhton firmware and that you can program / develop / debug your motor firmware directly by wifi wireless using your phone or PC.
But there are two disadvantages:
1. this FLIPSKY Mini FSESC6.7 supports only 48V / 13S batteries
2. due to the space limitations, motor is running sensorless and while the motor startup is good, it is not as good as on the original motor controller
Build with VESC FLIPSKY 75100:
This build with VESC FLIPSKY 75100 is the most powerful possible, because this VESC can handle batteries up to 75V and 100Amps currents, so theoretically can handle 7.5kw!! Also, as this VESC is placed outside, there is space to install the magnetic encoder board and so the motor startup is the best possible.
But there is one disadvantage: this VESC FLIPSKY 75100, although small, there is not space available inside for it and so it must be placed outside, attached to your EBike frame.
Next steps: I am yet to decide if I will use the most clean build or the other. My best battery is a 52V / 14S battery and I would need to rework to make it to 48V / 13S, to work on this most clean build.
I need to improve the display firmware, as currently it displays very basic information.
The final result is this one:
And how is it inside?? Here it is, without that black plastic 3D printed cover:
And more details. Here is the DIY EBike board + the VESC FLIPSKY Mini FSESC6.7:
That DIY EBike board is based on ESP32-S3, that is running the Pyhton EBike firmware and that I program wireless by Wifi. I am sharing the firmware, schematics, photos, etc, here: GitHub - OpenSourceEBike/EBike_EScooter_app_pyhton: EBike / EScooter app developed in CircuitPython, to control a motor by sending commands to VESC motor controller
Here is the schematic:
After testing that every EBike sensor reading were working, I put silicone to make all that wires robust, including the connectors. The idea is to make everything robust and avoid breaking due to the vibrations while I am riding on the mountains:
And finally, I used kapton tape that is very robust and resists to high temperatures:
BUT, there is also some not good news. With all that wires and tight space, it is not possible to have the magnetic encoder sensor working. So, in the end I configured VESC to run sensorless and it works well as I tested before on my previous version with the external VESC FLIPSKY 75100.
Here is picture of the magnetic encoder sensor board. From my tests, I found that no wires can be near and between the magnetic encoder board and the round part of the motor case. But as you can see, I could not do it. Maybe someone can improve the wire routing but I decided to stop here. And a picture of the 3D printed cover with the magnetic encoder board, that I tried to make working:
Conclusions
Build with VESC FLIPSKY Mini FSESC6.7:
This build with VESC FLIPSKY Mini FSESC6.7 is the most clean possible. I think no one will understand that VESC is inside, that your EBike is running Pyhton firmware and that you can program / develop / debug your motor firmware directly by wifi wireless using your phone or PC.
But there are two disadvantages:
1. this FLIPSKY Mini FSESC6.7 supports only 48V / 13S batteries
2. due to the space limitations, motor is running sensorless and while the motor startup is good, it is not as good as on the original motor controller
Build with VESC FLIPSKY 75100:
This build with VESC FLIPSKY 75100 is the most powerful possible, because this VESC can handle batteries up to 75V and 100Amps currents, so theoretically can handle 7.5kw!! Also, as this VESC is placed outside, there is space to install the magnetic encoder board and so the motor startup is the best possible.
But there is one disadvantage: this VESC FLIPSKY 75100, although small, there is not space available inside for it and so it must be placed outside, attached to your EBike frame.
Next steps: I am yet to decide if I will use the most clean build or the other. My best battery is a 52V / 14S battery and I would need to rework to make it to 48V / 13S, to work on this most clean build.
I need to improve the display firmware, as currently it displays very basic information.
This is amazing. would it be possible to create a kit for a dead shimano motor? Shimano is dying from electronic errors, especially the torque sensor, but I don't think the sensor itself is faulty. Think about it, there are a lot of people willing to revive a shimano motor, even if it's worse than from the factory. better than none.I did finalize the installation of the small VESC motor controller + EBike board, inside my Bafang M500. It works well as I expected, just like it did on my previous version with the external VESC FLIPSKY 75100.
The final result is this one:
And how is it inside?? Here it is, without that black plastic 3D printed cover:
And more details. Here is the DIY EBike board + the VESC FLIPSKY Mini FSESC6.7:
That DIY EBike board is based on ESP32-S3, that is running the Pyhton EBike firmware and that I program wireless by Wifi. I am sharing the firmware, schematics, photos, etc, here: GitHub - OpenSourceEBike/EBike_EScooter_app_pyhton: EBike / EScooter app developed in CircuitPython, to control a motor by sending commands to VESC motor controller
Here is the schematic:
After testing that every EBike sensor reading were working, I put silicone to make all that wires robust, including the connectors. The idea is to make everything robust and avoid breaking due to the vibrations while I am riding on the mountains:
And finally, I used kapton tape that is very robust and resists to high temperatures:
BUT, there is also some not good news. With all that wires and tight space, it is not possible to have the magnetic encoder sensor working. So, in the end I configured VESC to run sensorless and it works well as I tested before on my previous version with the external VESC FLIPSKY 75100.
Here is picture of the magnetic encoder sensor board. From my tests, I found that no wires can be near and between the magnetic encoder board and the round part of the motor case. But as you can see, I could not do it. Maybe someone can improve the wire routing but I decided to stop here. And a picture of the 3D printed cover with the magnetic encoder board, that I tried to make working:
Conclusions
Build with VESC FLIPSKY Mini FSESC6.7:
This build with VESC FLIPSKY Mini FSESC6.7 is the most clean possible. I think no one will understand that VESC is inside, that your EBike is running Pyhton firmware and that you can program / develop / debug your motor firmware directly by wifi wireless using your phone or PC.
But there are two disadvantages:
1. this FLIPSKY Mini FSESC6.7 supports only 48V / 13S batteries
2. due to the space limitations, motor is running sensorless and while the motor startup is good, it is not as good as on the original motor controller
Build with VESC FLIPSKY 75100:
This build with VESC FLIPSKY 75100 is the most powerful possible, because this VESC can handle batteries up to 75V and 100Amps currents, so theoretically can handle 7.5kw!! Also, as this VESC is placed outside, there is space to install the magnetic encoder board and so the motor startup is the best possible.
But there is one disadvantage: this VESC FLIPSKY 75100, although small, there is not space available inside for it and so it must be placed outside, attached to your EBike frame.
Next steps: I am yet to decide if I will use the most clean build or the other. My best battery is a 52V / 14S battery and I would need to rework to make it to 48V / 13S, to work on this most clean build.
I need to improve the display firmware, as currently it displays very basic information.
I do not plan to sell anything. The options are:
- user is able to DIY his own solution
- user asks to an electric engineer friend to do it
- user asks on an electronics / EBike shop to do it
vikino1
Active member
Super, small and simple. 
vikino1
Active member
Today I tried the new display for the first time, my battery is 36V 630WH. The first part disappeared at 39V, the second at 37V and the third at 36V. I didn't get lower at 42km and 373 meters climbed. Tomorrow I will try it until it shuts down, I measured with the DPC 18 Bafang controller. So the voltage should be taken with a margin. And when I connected the new display again after the measurement, the part was ready. But as a guide, it could be suitable.
vikino1
Active member
Today I finished measuring the new display, after the 4th part disappeared it was 35V, with the 5th part 34V. The last part started flashing. After 30 km I could not turn off the engine. The rest in the battery after stabilization in the heat is 33.5V. The last part is not visible because of the flashing.
Last edited:
I 3D printed the motor cover in ABS plastic - here it is, and just before I screwed it, I did put a fair amount of silicone to make sure it will keep the water prof:
---------------
Yesterday I did a ride for 4h and it was a good test. Everything is working as expected.
I was looking at the VESC temperature at it was never over 42º Celsius (but ambient temperature were low at around 10ºC), while I think the max for VESC would be 100ºC. So, this small VESC seems very good for the task!!
Also about the sensorless motor startup instead of magnetic encoder as on original motor controller, I did not notice anything.
There was some mud, but not to much:
Detail of the motor 3D printed cover in ABS plastic:
In the end, I cleaned the EBike with pressurized water, as I am confident that 3D printed motor cover, with the silicone I used on it, is water prof enough to handle all this water:
So, the hardware is working as expected. Now I will focus on improving the firmware, as currently this is just driving the motor based on the pedal torque value and choosing the assist level on the display. There are missing features on the firmware, as measuring the wheel speed to show on the display as also the important walk assist. I will also focus on the final documentation for How to Build.
---------------
Yesterday I did a ride for 4h and it was a good test. Everything is working as expected.
I was looking at the VESC temperature at it was never over 42º Celsius (but ambient temperature were low at around 10ºC), while I think the max for VESC would be 100ºC. So, this small VESC seems very good for the task!!
Also about the sensorless motor startup instead of magnetic encoder as on original motor controller, I did not notice anything.
There was some mud, but not to much:
Detail of the motor 3D printed cover in ABS plastic:
In the end, I cleaned the EBike with pressurized water, as I am confident that 3D printed motor cover, with the silicone I used on it, is water prof enough to handle all this water:
So, the hardware is working as expected. Now I will focus on improving the firmware, as currently this is just driving the motor based on the pedal torque value and choosing the assist level on the display. There are missing features on the firmware, as measuring the wheel speed to show on the display as also the important walk assist. I will also focus on the final documentation for How to Build.
I just finalized the documentation / How to Build for my Bafang M500, I hope it can help others to replicate and learn how EBikes / EScooters works:
https://opensourceebike.github.io/
https://opensourceebike.github.io/
The EBike modular DIY electronics and software, is featured as the Project of the Week on the Python on Microcontrollers Newsletter.
This newsletter is written by the Adafruit Industries, an open-source hardware company based in New York City, that is popular among makers.
This newsletter is written by the Adafruit Industries, an open-source hardware company based in New York City, that is popular among makers.
Hi! I have one bafang m500 with problem.
The fact is that the bike is going well, until I go down a hill with stones, roots, etc., and I take a small jump or simply from the potholes, I look at the display and it is turned off. At first after 5 - 10 minutes it turned on and so normal.
now it can take up to 30 minutes until it comes back on.
I have tried several things:
1.- Clean the connectors that are on the motor and those on the display with contact cleaner
2.- When it happens to me, I have tried to remove the battery and put it back, and it still does not work until almost 30 minutes have passed.
3.- when it happens to me, I tried to connect another lcd in case it was the screen but nothing.
Logic tells me that it could be a cable, but what cable? something from the controller? It's just that it's something so rare that until a few minutes have passed I don't turn it back on because I'm lost.
This started to happen to me as a result of one day when I got into a brutal quagmire, from which I had to get out with the bike on my shoulders. Then I cleaned it but without kacher, with a hose and being careful.
can you think of anything that could be happening to me?
The fact is that the bike is going well, until I go down a hill with stones, roots, etc., and I take a small jump or simply from the potholes, I look at the display and it is turned off. At first after 5 - 10 minutes it turned on and so normal.
now it can take up to 30 minutes until it comes back on.
I have tried several things:
1.- Clean the connectors that are on the motor and those on the display with contact cleaner
2.- When it happens to me, I have tried to remove the battery and put it back, and it still does not work until almost 30 minutes have passed.
3.- when it happens to me, I tried to connect another lcd in case it was the screen but nothing.
Logic tells me that it could be a cable, but what cable? something from the controller? It's just that it's something so rare that until a few minutes have passed I don't turn it back on because I'm lost.
This started to happen to me as a result of one day when I got into a brutal quagmire, from which I had to get out with the bike on my shoulders. Then I cleaned it but without kacher, with a hose and being careful.
can you think of anything that could be happening to me?
temon10
Well-known member
try open the controller and re check cable connection inside.
temon10
Well-known member
so with firmware 46.2 (which is cannot flash the firmware)can be tuned with your K1 Blackbox?Hello M600 fans.
Just found out, latest M600 has option to change MAX power levels. And again default is high.So now also possible low power on PASS1 and have good range...
View attachment 108068
Can we change power level via BESST?Hello M600 fans.
Just found out, latest M600 has option to change MAX power levels. And again default is high.
Only if you have the newest firmware, which is currently only available by purchasing a new motor controller.
temon10
Well-known member
only M510 FC 2.0 can change power level via BESST Pro
Dado
E*POWAH Master
- Jun 28, 2022
- 1,034
- 659
Not true, now also new M600 and also M510 FC1.0
M510 FC2.0 has also advanced power level setup - Assistance level and acceleration (which now works) for every pass levels.
Would u like me to do screenshots?
Last edited:
have you pics of this power level change with BESST pro ?
I have last rev of BESST pro and i can adjust current limit percentage for each level, but not the power level ? currrent adjust is applicable on my M510 rev 1.0, not on M500 and 600.
temon10
Well-known member
so u change parameter of m600 46.2 version with your blackbox or also can change with besst pro?
Similar Threads
-
-
-
-
-
Need firmware for Bafang M620 UART because LVC current ramp down- Started by tocotronix
- Replies: 4