Bafang M500/M600 thread

Thanks for that info... I've written stuff with characteristics before so it's familiar territory (a bike computer to send speed/cadence to standard cycling apps, with a derestrictor sneaking in, on a Arduino 33BLE)

I did wonder if there was a restart command on the CAN bus that did what a power cycle would do.
 
@aegidius you may want to look at K1 EBikes who make virtually what you are trying to create. All the speed functions you wish for are already in practice and for the cost of their unit you could save a lot of time.
 
Regarding mechanical maintenance, are there recommendations for the M510 motor?
Like how often to change the lubrication, replace bearings, inspect gears etc.?

I searched a bit, but it seems like there is little maintenance information for those newer motors.
It seems there are some bearings with a non-standard size in the M510, which needs replacement some time, and some gears are available, but other than that I didn't find much.

Since I use my bike both for commuting and MTB, I've nearly driven 2000 km with it in a few months. I'm driving in all weather, while often going hard on the motor.
While everything still sounds and feels good, and I don't think I need to service it now, it would be good to have some estimation of what to expect.
 
What are the headers manufacturer and part numbers you used to connect the Bafang motor sensors? You said it is PHB 2.0mm 2x3P connector , is there compatible header I can purchase on Digikey for instance?


1739830469849.png
 
Last edited:
If you want to take a look yourself, I can recommend the nRF Connect app for BLE debugging: You can connect and see the services, characteristics etc., or monitor a running BLE connection
I looked a bit more into this now that my bike is running, and found I could log the messages coming from the display to Go+ with nRF Connect, but not the other way around! So I can't see what Go+ is sending to the display yet. To see the whole conversation I'll need to get the gear to make a proper BLE sniffer.

So far I've identified these fields in the periodic notification sent from the display (the one starting with 55 AA 27 10 11)
- range in km*100
- battery percentage (not the voltage, strangely, because it's shown in Go+)
- the PAS level (1-5)
- a flag saying whether the lights are on
- the speed in wheel RPM

but when I change, say, the PAS level in Go+, I get a short acknowledgement notification, but I can't see the command that Go+ sent. Will keep at it and report progress...
 
To see the whole conversation I'll need to get the gear to make a proper BLE sniffer.
!? Android has a build in BLE sniffer in the developer settings. It's called HCI Snoop.
There are tools like Wireshark that help to analyze the log file.
 
Back
Top