Bafang M500/M600 thread

Tomblarom said:
Yes.. BESST is mandatory, when you want to change firmware. For setting assist levels DPC245/DPC010 and GO+ app are enough. However DPC240/DPC241 are deprecated, as well as the M500. Consider upgrading if you want to use newer features like GO+.
Click to expand...
okay thank you for the answer . assist levels are something. what else plays big role ? display firmware ? motor firmware ? how to check them ? is there any compendium about them ?
 
Hello everybody, could somebody please help me, I have Bafang M600 engine and tried to replace one bearing inside. Did some stupid thing and accidently cut all the wires from the torque sensor. Maybe somebody has a diagram or some wiring scheme which color cable goes to which pin in the connector. Any help would be very appreciated, even some photos if you have this part in your hands. Thank you!!
 

Attachments

  • 20240508_115451.jpg
    20240508_115451.jpg
    752.1 KB · Views: 17
Feels like it's just red, black, gray, white, green, purple just from the wire lengths and positions:

Screenshot_20240508-184940.png

Red and black are probably just +10V and ground anyway, so you should be able to check them from turning on your controller, plugging in the connector, and using a volt meter on the cut end attached to the connector. Once those are wired back on to the sensor, the others are likely signal wires. Many torque sensors are actually combination cadence and torque sensors. Not the end of the world to swap them around until the controller is sensing turning it correctly. Having red and black right would be enough to not destroy hall sensors, I think, unless there's a separate +5V in there for them somehow.
 
CiDi said:
To configure the Bafang M500 / M600 motor without using the BESST programmer, you can use this interface.

Link interface USB to CAN on Amazon:

Link cables Bafang HMI M500/M600 on e-bike-technologies:

HIGO-B5-F

HIGO Mini-F female connector, 5-pole, 5 x 0.14 mm²
www.e-bike-technologies.de www.e-bike-technologies.de

HIGO-S5-F

HIGO Mini-F male connector, 5-pole, 5 x 0.14 mm²
www.e-bike-technologies.de www.e-bike-technologies.de

Below are the software and the instructions for configuration and use.
Click to expand...

Hello, I am new here, try to search in this thread, but I am not sure.
I ONLY need to set higher Speed limitation on my M500 as cheap as possible.

I found CiDi post for USB CAN converter, but links for connectors Are dead.

Found also this ONLY pressing button cable for 35$, but if I understand correctly max Speed can be set ONLY to 60km/h (not lower)


Not needed flash firmware right Now, but maybe in the Future. Flash firmware Is ONLY possible by BESST programmer?

Thanks for advice!
 
Not sure about your specific bike/firmware/controller, ect, but on my M600 the 'speed limit' was 'removed' by moving the speed sensor magnet just a bit closer to the center of the hub, so the speed sensor could not pick it up. This effectively set the max assist speed to 'unlimited' and it was free. If having the speedo on the display always show "0", you can likely get a cheap bike computer which will give you speed, plus a whole lot more... and you can likely set it fairly accurately for your wheel size.
 
lnanek said:
Feels like it's just red, black, gray, white, green, purple just from the wire lengths and positions:

View attachment 352380

Red and black are probably just +10V and ground anyway, so you should be able to check them from turning on your controller, plugging in the connector, and using a volt meter on the cut end attached to the connector. Once those are wired back on to the sensor, the others are likely signal wires. Many torque sensors are actually combination cadence and torque sensors. Not the end of the world to swap them around until the controller is sensing turning it correctly. Having red and black right would be enough to not destroy hall sensors, I think, unless there's a separate +5V in there for them somehow.
Click to expand...
Thanks a lot, thought the same about connections, just wanted to make sure everything is alright. That tip with checking 10V+ and ground is really smart, thanks again:)
 
I've had my M600 since spring 2020. I've never updated the firmware as it runs very well and is already set to 28MPH limit. I've gone through a couple of displays. 2 860Cs as they seem to break after a year or two.
After the failure of my 2nd 860, I decided to try something new. I also wanted to save a bit more space for my phone mount so I got a Bafang 600C. Works very well although the 860C showed all the data more easily all on one page.

Now - the reason for this post. On the 860C, although there was a setup item for wheel size and maximum speed, they were locked in place, presumably to the values programmed in the firmware.
With the 600C, these can be changed and, although not extensively tested, seem to work. I was very surprised.
I was able to set the speed limit down to 15MPH and, my speed was limited. I haven't tested on the high end as I rarely exceed 28MPH anyway.

Now, a couple of questions.
1) The assist levels setup allows for 4 choices - 3, 5, 9 and U. Yes, U, not a typo. If I set this I get 6 levels. Any idea what this is doing and why I see 6 levels?
2) As this is not a glass display but acrylic, I'm a bit worried about scratching. Does anyone know of a screen protector, preferably glass, that will fit a 2.4 inch display? I know about the cut them yourself types but would really like glass.
 
This is a follow up to my post about the 600C controller above which seems to have failed today. I went into a store and when I came back out, the bike wouldn't restart, just a blank, no one home, display. The entire sordid affair below.

I was out for a ride today with my FLX V4 Trail which has an M600 motor and a 600C display. Everything was fine. I stopped to go into a store and when I came out, the bike would not start up. The display was completely dead. I've had a couple of display failures before so I expected to be able to plug in an old display I have (DPC230, the original from the bike) and have everything work.

I plugged in the old display and it immediately lit up (without pressing a button) and after the usual screen came up, it immediately showed Error 30. Pressing the on button for a few seconds allowed the usual screen to show again, and if I ride the bike, it seems normal until I turn it off again, then it won't restart with the switch. Unplugging/ plugging the display repeats the above behavior.
Not sure if it's relevant but a month or so ago, the 860C display I was using for over a year suffered a similar failure where the bike just wouldn't start up. Plugging in the DPC 230 worked perfectly so I bought a new 600C which has only been on the bike for about a week and, until today, worked great.

At the risk of TMI, I also want to note that the 600C allows changing the wheel diameter and top speed. I did change these to test out this capability. This appears to make a change to the bike controller. I say this because I had changed the top speed to 32 and the wheel diameter to 27.5. Previously these were set to 28 and 28. I mention this only because when I look at these setting now with the DPC230, they are, as always, read-only but are showing the new values I had set with the 600C. This leads me to wildly speculate that the controller now expects a 600C and when it doesn't find it, complains about error 30 (communications error).
I have already looked for pinched wires, loose or bent connectors etc. and found nothing. This includes the plugs into the motor and controller.
Any help will be greatly appreciated.
 
I released OpenBafangTool 2.0 - now with support of can bus

1716039651607.png


(Both of them are supported).
Currently not all parameters are available, other will be added in next versions
 
hey . I have m600 with dpc 241 . it shows range estimation , any idea what it's based on? is it reliable?
 
pxl666 said:
hey . I have m600 with dpc 241 . it shows range estimation , any idea what it's based on? is it reliable?
Click to expand...
Range estimation is based on "battery capacity" and "range on one battery" parameters of motor. This parameters will be available to see and change in next update. Then you can configure them and it will be almost reliable
 
AndreyPr said:
Range estimation is based on "battery capacity" and "range on one battery" parameters of motor. This parameters will be available to see and change in next update. Then you can configure them and it will be almost reliable
Click to expand...
well . the most simple thing I can't think of is simply measure of wh consumed in relation to voltage and on the other hand if rider knows his battery capacity this simple information is most reliable. if controller would have the memory function it could simply calculate wh back . taking sag into the math could make this even more precise but requires much more sophisticated algorithm
 
casainho said:
Bafang have a few different motors. For instance:
- the M620 / 1000W you mention, weights 6.7kgs
- my EBike has the M500 / 250W that weights 3.6kgs
- I plan to move to an EBike with newest M820 that weights 2.3kgs

So for the ones like me looking for a lightweight Ebike and less powerful, M820 is the best motor and M620 is the no go option.
Click to expand...
Some good news for you if you are still looking at the M820, it is sensorless, no hall sensors at all so your M500 sensorless approach was the right choice!
 
Hello, I bought Bafang Besst programmer And I unlock Speed on my M500 with CAN bus without any problem. But I have problem with UART version - For example M400 UART dont show Speed/Rims change in software (write option) I can ONLY read data.
Am I missing something or doing something Wrong?
Curently using SW 1.2.20 version.
Thanks!
 
Do you have some link for Firmwares for Display (HMI)? I found only for C240/241 on Github. Thanks
 
First prototype of an additional controller, installed permanently in the bike, to log all drive data and parameters, configure the settings via BLE standard with a phone app, stealth speed limit changes etc.

IMG-20240825-175928510_small.jpg

Many CAN messages are implemented already for reading, and setting the speed, wheel size and wheel circumference from a connected phone already works.
Firmware OTA updates are done via WiFi, no connection to a PC needed.

Be prepared for more in the following weeks:cool:
 
Kyokushin said:
I would have to have a restricted bike just after turn on (always restricted on turn on)
Click to expand...
Going back a way now - apologies if this has been answered in the meantime.
What I'd like to do is similar. Sequence as follows:
1. Starts up in restricted (25 km/h) mode
2. Ride up to 20km/h and double tap brake. Brake switch detected and top speed frame is injected, making it 45km/h.
3. When braking and speed drops below 10km/h, top speed is again restricted to 25. Since you eventually have to stop, this should be a no brainer.

Now the key things here is I'd like to do this all wirelessly using an Arduino 33BLE, so the bike has no visible modifications. This means that it must be able to:
1. A speed/circum frame can be injected via BLE (Bafang Go+ can do this, so it must be possible)
2. The brake status can be sampled via BLE. This I'm not sure about. I know it comes on the CAN bus every half second or so.

Question is, do we know what BLE characteristics are read/written by Bafang Go+ when connect to a C245 or similar?
 
Efim_Rus said:
I can describe how it works when it works.
The sensor has four leads, in my photo you can see the colors of the wires that are connected to it.
1. Orange is the positive power lead 4.7V (+)
2. Purple - OUT 1
3. White - OUT 2
4. Black is the negative GND pin (-)

On a working sensor, when the shaft rotates, OUT 1 and OUT 2 are alternately pulled to GND. If you just bring the magnet with one pole to the sensor, then both pins will be pulled to GND, if you bring the magnet with the opposite pole, then a voltage of 3.25V will appear on these pins, which is formed by pulling these pins to a positive 4.7V power source through a resistor on the electrical circuit.

On the faulty sensor, I noticed that OUT 1 or OUT 2 do not react to a magnetic field.

View attachment 308420
Click to expand...
There are two rings with multiple magnets on each and two magnet sensors sensing those magnets. The rings with magnets are separated with a spring or springs and attached to the pedals crank shaft. The harder you push the pedal the more you compress the spring and the more you reduce the distance between the magnets couples. The magnets sensors sense the magnets on the rings and send signals to the motor controller processor and the motor controller processor defines the fact of pedals rotation (if the signals exist), defines the cadence (based on the signals frequency from one sensor), defines the direction of the rotation (based on the signals sequence from two magnet sensors), and defines the torque (calculated based on the cadence and the time between two signals from two sensors).
 
aegidius said:
Going back a way now - apologies if this has been answered in the meantime.
What I'd like to do is similar. Sequence as follows:
1. Starts up in restricted (25 km/h) mode
2. Ride up to 20km/h and double tap brake. Brake switch detected and top speed frame is injected, making it 45km/h.
3. When braking and speed drops below 10km/h, top speed is again restricted to 25. Since you eventually have to stop, this should be a no brainer.

Now the key things here is I'd like to do this all wirelessly using an Arduino 33BLE, so the bike has no visible modifications. This means that it must be able to:
1. A speed/circum frame can be injected via BLE (Bafang Go+ can do this, so it must be possible)
2. The brake status can be sampled via BLE. This I'm not sure about. I know it comes on the CAN bus every half second or so.

Question is, do we know what BLE characteristics are read/written by Bafang Go+ when connect to a C245 or similar?
Click to expand...
Unfortunately with M510 and M560 it is no longer possible to change maximum speed on the fly, you have to turn the controller off and on every time.
I doubt that in BLE via diaplay you can send these configurations, you would need a custom diaplay.
 
Well, familiarizing myself with mobile app development took some time, longer than expected, but now I've settled on Flutter for writing the app.
This will allow the app to be cross-platform and while I'll mainly target Android, implementing an iPhone version would be easy, and with a BLE capable PC/Laptop it runs on Windows and macOS, too.
The app will work both as dashboard, to use it as display while driving and for quick configuration without the need for BESST tool or even only connecting via cable, instead all wireless via the app.

Right now I'm planning the UI/UX with navigation flow etc., and next write a usable app, not only some unstructured test code.
After this, the next step will be releasing this app as Open Source on GitHub, documenting the hardware prototype and providing the firmware, this way others could already use it.
Finally, I'll create a dedicated PCB for this, allowing for further developing the hardware and app with more functions.


The current hardware is very simple: ESP32-C3 devboard with additional MCP2515 module connected to the CAN bus, powered by a Matek Micro BEC 6-60V.

The MCP2512 controller is not really needed with the ESP32, it already has a CAN controller and only needs the transceiver, for example TJA1050. I only used the MCP+TJA combo because it's an available module, easier to work with than just the TJA.

But I'm not sure about the ESP32 platform. Maybe I'll switch to Nordic modules like nRF51/52 in the future. They support the ANT/ANT+ protocol, this would allow connecting as sensor to a compatible bike computer or sport-/smartwatch. But since this is no small task, I'll revisit this idea later.


@aegidius The speed limit is a bit complicated with the newer controllers. @CiDi is right, changing the speed often requires restart.
As far as I've read, for example with M510 FC1.0 it should be possible to change without restart.
But with FC2.0 you need to restart: While it looks like the limit has changed, on the display the new limit is shown, the controller still works with the old limit, until it's restarted. This is my experience with M510 FC2.0 and MMG522C4814F802010.1 firmware.

But I think, with my planned PCB, it should be possible to trick the controller: It will allow not only connecting to the display connector, but the brake connector, too. Then the controller speed limit can be set to something high, and a custom limit be implemented by simply "pressing the brake" digitally. With brake signal received, the motor cuts power immediately, this should allow custom speed limits to be implemented, including logic for switching between limits with brake or key presses.

With only the DP245 stock display and Go+ perhaps it could be possible there is a hidden command for speed change, but the whole restart problem would persist nevertheless.
DP245 display does not really use BLE characteristics, it communicates with the Go+ app via Nordic UART Service.
This communication uses a proprietary binary format, you would first need to reverse-engineer the protocol and hope that there even is a command for writing the speed and wheel size. As I know, the Go+ app only allows reading this, but there is a chance they implemented read and write and just don't allow write in the App.
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, this way you could log the messages between the display and Go+ app for further analysis.

nRF Connect, 2025-01-02
DP C245-30.CAN (EC:C5:7F:91:27:1D)
D 11:29:22.627 [Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
V 11:29:22.838 Connecting to EC:C5:7F:91:27:1D...
D 11:29:22.839 gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D 11:29:22.844 [Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I 11:29:22.844 Connected to EC:C5:7F:91:27:1D
I 11:29:22.845 MTU changed to: 203
V 11:29:22.847 Discovering services...
D 11:29:22.847 gatt.discoverServices()
D 11:29:22.850 [Callback] Services discovered with status: 0
I 11:29:22.850 Services discovered
V 11:29:22.851 Discovering services...
D 11:29:22.851 gatt.discoverServices()
V 11:29:22.856 Generic Access (0x1800)
- Device Name [R] (0x2A00)
- Appearance [R] (0x2A01)
Generic Attribute (0x1801)
- Service Changed [I R] (0x2A05)
Client Characteristic Configuration (0x2902)
Device Information (0x180A)
- Manufacturer Name String [R] (0x2A29)
- Model Number String [R] (0x2A24)
- Firmware Revision String [R] (0x2A26)
- Software Revision String [R] (0x2A28)
- System ID [R] (0x2A23)
- PnP ID [R] (0x2A50)
Nordic UART Service (6e400001-b5a3-f393-e0a9-e50e24dcca9e)
- RX Characteristic [W WNR] (6e400002-b5a3-f393-e0a9-e50e24dcca9e)
- TX Characteristic [N] (6e400003-b5a3-f393-e0a9-e50e24dcca9e)
Client Characteristic Configuration (0x2902)
D 11:29:22.856 gatt.setCharacteristicNotification(00002a05-0000-1000-8000-00805f9b34fb, true)
D 11:29:22.857 gatt.setCharacteristicNotification(6e400003-b5a3-f393-e0a9-e50e24dcca9e, true)
D 11:29:22.859 [Callback] Services discovered with status: 0
I 11:29:22.859 Services discovered
V 11:29:22.860 Generic Access (0x1800)
- Device Name [R] (0x2A00)
- Appearance [R] (0x2A01)
Generic Attribute (0x1801)
- Service Changed [I R] (0x2A05)
Client Characteristic Configuration (0x2902)
Device Information (0x180A)
- Manufacturer Name String [R] (0x2A29)
- Model Number String [R] (0x2A24)
- Firmware Revision String [R] (0x2A26)
- Software Revision String [R] (0x2A28)
- System ID [R] (0x2A23)
- PnP ID [R] (0x2A50)
Nordic UART Service (6e400001-b5a3-f393-e0a9-e50e24dcca9e)
- RX Characteristic [W WNR] (6e400002-b5a3-f393-e0a9-e50e24dcca9e)
- TX Characteristic [N] (6e400003-b5a3-f393-e0a9-e50e24dcca9e)
Client Characteristic Configuration (0x2902)
D 11:29:22.860 gatt.setCharacteristicNotification(00002a05-0000-1000-8000-00805f9b34fb, true)
D 11:29:22.861 gatt.setCharacteristicNotification(6e400003-b5a3-f393-e0a9-e50e24dcca9e, true)
I 11:29:23.264 Connection parameters updated (interval: 15.0ms, latency: 0, timeout: 1250ms)
I 11:29:23.989 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-ED-A1-11-04-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
A 11:29:23.989 "U��� " received
I 11:29:23.999 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-5C-FE
A 11:29:23.999 " \�" received
I 11:29:24.044 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-01-10-11-05-59-00-7F-FF
A 11:29:24.044 "U� Y �" received
I 11:29:24.088 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-01-10-11-05-3A-00-9E-FF
A 11:29:24.088 "U� : ��" received
I 11:29:24.151 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-27-10-11-06-01-00-00-00-01-01-01-05-4C-00-00-00-D8-01-00-00-00-00-56-4C-44-07-9A-00-00-00-00-00-00-9A-00-00-00-00-00-00-B8-00-AA-01-FF-FA-55-AA-99-10-11-04-04-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
A 11:29:24.151 "U�' L � VLD � � � � ��U�� " received
I 11:29:24.178 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 00-00-00-00-00-00-00-00-3D-FF
A 11:29:24.178 " =�" received
I 11:29:24.241 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-61-A2-11-04-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-E7-FE
A 11:29:24.241 "U�a� ��" received
I 11:29:24.301 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-ED-A3-11-04-00-43-52-20-58-31-30-4E-2E-35-31-30-2E-46-43-20-32-2E-30-00-00-00-00-00-00-4D-4D-47-35-32-32-43-34-38-31-34-46-38-30-32-30-31-30-2E-31-00-00-00-00-4D-4D-20-47-35-32-32-2E-32-35-30-2E-43-00-00-00-00-00-00-00-00-00-00-00-43-52-58-31-30-4E-2E-35-31-30-2E-46-43-32-2E-30-41-31-38-46-38-58-38-32-33-30-34-33-38-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-4C-00-00-00-00-00-56-4C-00-00-00-00-00-00-00-00-A5-13-00-00-00-00-00-00-70-17-13-01-C0-08-00-00-01
A 11:29:24.301 "U��� CR X10N.510.FC 2.0 MMG522C4814F802010.1 MM G522.250.C CRX10N.510.FC2.0A18F8X8230438 L VL � p � " received
I 11:29:24.314 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 00-05-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-A3-E9
A 11:29:24.314 " ��" received
I 11:29:24.361 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-C8-A4-11-04-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
A 11:29:24.361 "U�Ȥ " received
I 11:29:24.388 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 00-00-00-00-00-00-00-7E-FE
A 11:29:24.388 " ~�" received
I 11:29:24.464 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-2C-A4-11-04-C8-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-52-FE
A 11:29:24.464 "U�,� � R�" received
I 11:29:24.526 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-C6-A5-11-04-00-44-50-20-43-32-34-35-2E-43-20-33-2E-30-00-00-00-00-00-00-00-00-00-00-00-44-50-43-32-34-35-43-46-38-30-33-30-31-2E-32-00-00-00-00-00-00-00-00-00-44-50-20-43-32-34-35-2E-43-41-4E-00-00-00-00-00-00-00-00-00-00-00-00-00-44-50-43-32-34-35-2E-43-33-2E-30-37-35-32-46-38-59-37-30-38-30-31-37-37-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-43-37-35-35-2D-30-31-30-31-00-00-00-00-00-00-00-42-41-46-41-4E-47-2D-42-41-46-41-4E-47-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-05-00-02-01-01-00-01-00-44-07-00-00-AA-01-B8-00-94-D6-02-00-FF-00-0A-00-00-00-9A-00-00-00-00-00-00
A 11:29:24.526 "U�ƥ DP C245.C 3.0 DPC245CF80301.2 DP C245.CAN DPC245.C3.0752F8Y7080177 C755-0101 BAFANG-BAFANG D � � �� �
� " received
I 11:29:24.538 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 00-D8-01-00-00-AD-E5
A 11:29:24.538 " � ��" received
I 11:29:24.616 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-A4-A7-11-04-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-9F-FE
A 11:29:24.616 "U��� ��" received
I 11:29:24.691 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-73-A9-11-04-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-01-00-00-0A-00-0A-00-0A-00-0A-00-0A-00-0A-00-0A-00-0A-00-0A-00-00-04-04-04-04-04-04-04-04-04-00-64-2D-64-2D-64-2D-64-2D-64-00-11-32-2A-3C-3C-50-50-64-64-5A-F9-55-AA-27-10-11-06-01-00-00-00-01-01-01-05-4C-00-00-00-D8-01-00-00-00-00-56-4C-44-07-9A-00-00-00-00-00-00-9A-00-00-00-00-00-00-B8-00-AA-01-FF-FA
A 11:29:24.691 "U�s�








d-d-d-d-d 2*<<PPddZ�U�' L � VLD � � � � ��" received
I 11:29:25.199 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-27-10-11-06-01-00-00-00-01-01-01-05-4C-00-00-00-D8-01-00-00-00-00-56-4C-44-07-9A-00-00-00-00-00-00-9A-00-00-00-00-00-00-B8-00-AA-01-FF-FA
A 11:29:25.199 "U�' L � VLD � � � � ��" received
I 11:29:27.029 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-18-A3-11-04-18-4D-4D-47-35-32-32-43-34-38-31-34-46-38-30-32-30-31-30-2E-31-00-00-00-00-B9-FA
A 11:29:27.029 "U� � MMG522C4814F802010.1 ��" received
I 11:29:27.074 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-18-A4-11-04-18-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-16-FF
A 11:29:27.074 "U� � �" received
I 11:29:27.134 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-18-A5-11-04-18-44-50-43-32-34-35-43-46-38-30-33-30-31-2E-32-00-00-00-00-00-00-00-00-00-BE-FB
A 11:29:27.134 "U� � DPC245CF80301.2 ��" received
I 11:29:27.179 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-18-A7-11-04-18-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-13-FF
A 11:29:27.179 "U� � �" received
I 11:29:27.314 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-27-10-11-06-01-00-00-00-01-01-01-05-4C-00-00-00-D8-01-00-00-00-00-56-4C-44-07-9A-00-00-00-00-00-00-9A-00-00-00-00-00-00-B8-00-AA-01-FF-FA
A 11:29:27.314 "U�' L � VLD � � � � ��" received
I 11:29:27.840 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-27-10-11-06-01-00-00-00-01-01-01-05-4C-00-00-00-D8-01-00-00-00-00-56-4C-44-07-9A-00-00-00-00-00-00-9A-00-00-00-00-00-00-B8-00-AA-01-FF-FA
A 11:29:27.840 "U�' L � VLD � � � � ��" received
I 11:29:28.383 Notification received from 6e400003-b5a3-f393-e0a9-e50e24dcca9e, value: (0x) 55-AA-27-10-11-06-01-00-00-00-01-01-01-05-4C-00-00-00-D8-01-00-00-00-00-56-4C-44-07-9A-00-00-00-00-00-00-9A-00-00-00-00-00-00-B8-00-AA-01-FF-FA
A 11:29:28.383 "U�' L � VLD � � � � ��" received
 
Last edited:
You must log in or register to reply here.

Similar threads

M
Bafang M225 mysteries & malfunctions
Replies
1
Views
120
Mark Pace
M
E
(still) Looking for hardtail frame for Bafang M620/Ultra
Replies
5
Views
2,805
chris667
C
S
Looking for help sourcing a motor for my ebike setup
2
Replies
49
Views
2,723
Hummina Shadeeba
H
ebike4healthandfitness
Some people need ebikes to be a lot simpler
2 3
Replies
65
Views
7,151
ebike4healthandfitness
ebike4healthandfitness
S
Hardtail frame for M510 (M500/M600) XC build
Replies
0
Views
2,062
Steakbroetchen
S
Back
Top