Bafang Canable Pro Master - discussion

[DPC18RI]

Display's DPC080CB HW 1.0 / DPC010CN HW1.0 and most likely DPC245 HW ? too.
Tested today, when connected to a M400 with controller HW version 2.1
Firmware update for these display's works too. (Does not work with M400 HW version 1.0).

 

[RonRonson]

Hi guys, first up, thanks for putting this software together
I have an issue with my Can 750W M315 BBS02B G340.750.C where using the software I can view all the parameters but when I change them (walk speed and throttle settings) they don't save. Am I doing something wrong? Thanks.

 

[DPC18RI]

Hi guys, first up, thanks for putting this software together
I have an issue with my Can 750W M315 BBS02B G340.750.C where using the software I can view all the parameters but when I change them (walk speed and throttle settings) they don't save. Am I doing something wrong? Thanks.

Although you can click save it does not mean a controller, or some controllers will allow it to change specific settings.

 

[DPC18RI]

mdi-9 added more features in the program. Now under the "info" tab it also shows now "production date" from controller, display etc.
Also firmw update for HMI DPE160 works too now as also a fast CRS10F (V4.0) mode "hub motor controller" update in 12 seconds.
See post 2 for the methods.

 

[mdi]

mdi-9 added more features in the program. Now under the "info" tab it also shows now "production date" from controller, display etc.
Also firmw update for HMI DPE160 works too now as also a fast CRS10F (V4.0) mode "hub motor controller" update in 12 seconds.
See post 2 for the methods.

Release: 1.5

Releases · mdi-9/bafang_canable_pro

Bafang Besst software replacement for M500, M510, M560, M820 etc - mdi-9/bafang_canable_pro

github.com

 

[winsprix]

hi guys! thanks for your great work!
today I successfully changed the firmware on my m820 motor with DP C030.CA 1.0 display to 43v one
At first I did everything by default: Mode: Motor controller; Delay 300; Display on
but got error and the display didn't turn off after that
error log:

Spoiler: log

[12 ├Minute: 34┤ ├Second: 59┤] [INFO] Firmware file loaded. Size: 93196 bytes. Data chunks to send: 11648 [12 ├Minute: 34┤ ├Second: 59┤] [INFO] File header data: 01 45 82 40 40 00 00 00 00 00 00 00 00 00 6B [12 ├Minute: 34┤ ├Second: 59┤] [INFO] Step 1: Announcing host readiness... [12 ├Minute: 34┤ ├Second: 59┤] [INFO] Step 2:Waiting for controler ready state... [12 ├Minute: 34┤ ├Second: 59┤] [INFO] Step 2.1: Waiting for acknowledgment of the 6008 package... [12 ├Minute: 34┤ ├Second: 59┤] [INFO] Step 3: Sending first package (file length)... [12 ├Minute: 34┤ ├Second: 59┤] [INFO] Step 4: Waiting for acknowledgment of the first package... [12 ├Minute: 34┤ ├Second: 59┤] [INFO] Step 4.1: Waiting for acknowledgment of the first chunk... [12 ├Minute: 34┤ ├Second: 59┤] [INFO] Step 5: Sending data chunks... [12 ├Minute: 35┤ ├Second: 15┤] [ERROR] Step 5(chunkId:0401): Timeout reached, exiting loop.... [12 ├Minute: 35┤ ├Second: 15┤] [ERROR] Firmware update failed or was not completed. [12 ├Minute: 35┤ ├Second: 15┤] [INFO] Runtime: 16.127641800000333s

then i tried other firmwares(like x6 attempts), 43v and 48v as well and still same error

After that, i set the delay to 600 and successfully flashed the firmware to 43V on the first try.

then i successfully drove 60 km, everything worked perfectly and the firmware turned out to be much better than the stock 48v

thanks again!

 

[floydg73]

Here, but looks like i'm missing some of them.

Thank you for the firmware pack, can anybody help me with firmwares for the M400? Thanks

 

[sandrullo]

Good morning everyone,
I followed the instructions in the first post, purchased the cable, the extension cable, and made the connections as shown in the image below.
I then installed V 1.6, connected it to the motor controller and the PC, and powered it up. Unfortunately, I only see this black screen on my PC monitor.
Obviously, I did something wrong. Do you have any suggestions for solving this problem?
Thanks.
I'm attaching some images showing my situation: BBS01b, 250W, 36V, and DP C 010 display.

 

[stancecoke]

Do you have any suggestions for solving this problem?

Obviously, at the first attempt the canable was not found. So a reload of the browser page after a small moment will fix it.

 

[sandrullo]

Thanks stancecoke,
I'll go back to my PC at home in the early afternoon and check the situation

 

[DPC18RI]

@ sandrullo, it looks like server is already running. So you can try this first,
open Google Chrome or other browser and find the address bar at the top of the window.
Click inside address bar and type the server address in: http://localhost:8080 and hit enter.
Now you should see the program if all is ok.

 

[sandrullo]

Thanks dpc18ri,
when I get home this afternoon, I'll try this too and then update my situation.
I'm really keen to change my BBS settings and I'll try to figure out how.
See you later.

 

[sandrullo]

Hi everyone,
I tried with localhost and the connection page appeared immediately. Thanks everyone for the advice. Now I'm starting to study the configuration parameters.

 

[DPC18RI]

It is in another thread https://www.pedelecforum.de/forum/i...modell-anderer-controller.115831/post-2364701

@ dagobird I saw in that thread you bought BBS nur "im Dienste der Wissenschaft"
From the bafang stuf i have, I already tested most of it so i did the same and bought yesterday the offer on the Grundig site, a grey Grundig GCB-1 just for "the science" (almost for the name alone lol ).
It has M410 motor and a battery from Bafang itself so battery communication should be there and it means i have again some stuf to play with... All for the science

 

[sandrullo]

Hi everyone,

yesterday I started my experience with the Bafang Canable Pro Master and have already encountered some problems.
So I'm asking for help once again.
I connect to the display and controller as usual and see the settings I entered under "riding parameters" on my DPC010 display.

First problem: I tried changing some settings, for example, the walk assist speed to 6 km/h. I enter the value, then press save, but it doesn't save the value I set. Even when I test the bike on terrain, the speed remains 2.5 km/h, which is totally useless. The bike barely moves, and only on flat ground.

Second problem: Before connecting to the software, my DPC10 display showed me the "riding parameters" menu, where I could set the power absorption for each assistance level and also the speed at which this power should be cut off.
Now the "riding parameter" menu item has disappeared... it's completely gone. I've searched for it everywhere, but it's not there (or can't be seen), so I can't change these settings anymore.

And that's a big problem because the canable pro master settings aren't saved on the controller and therefore don't affect the motor, and the settings on the display no longer exist.

(This display is Bluetooth, so I can connect it to the Bafang GO app, from which I can change the settings. Unfortunately, the settings aren't saved or applied from the app either.)

Last problem: as an alternative to walk mode, I use the hand throttle, but it activates after 1 or 2 seconds, and it's also too powerful and literally rips the bike out of my hands. How can I change this parameter?

Sorry for the long message...

I'm a little discouraged...

 

[stancecoke]

I'm a little discouraged...

That's understandable.
But I can't imagine, that sending commands for setting parameters by the canable can change the availability of menues in the display?!
Strange. Perhaps you can try to reset the display to factory settings?

 

[sandrullo]

Thanks for your understanding.
I also find it impossible that having connected the motor to the software could have somehow obscured the "riders parameter" menu, especially since the few values I tried to transfer from the software to the controller were not saved and transferred. I really don't know what to think and I don't understand. I looked for how to reset the display but I didn't find anything about it.

 

[DPC18RI]

@ sandrullo
Regarding walk assist see post 128. For throttle delay that is probably hardcoded in the firmware.

I think you are the first person trying / changing settings for BBS01B canbus.

The program reflected at first the settings / riding parameters from your DPC010CB as i understand it. Then you tried to change walk assist? Or did you also change assist parameters via the program? What did you use? Assist Full or Assist limited tab?

I'm just a user like you and i have NO BBS01B canbus but i took a DPC010CB and hub 4.0 controller. Changed riding parameters via DPC010CB display, the program showed the changes also. Then i changed via the program for assist 1 the speed % and the current % clicked save and i can see the changed settings in "riding parameters" in the display done with the program.
Granted, it is not a BBS01B which can react perhaps differently...

Also if for some reason the canable locked up, you can try all you want. So sometimes it's best to start fresh! Close browser, close cmd window and unplug canable. Also switch bike off. Wait few minutes switch bike on, plug canable back in PC and start the program again. And stay away from walk assist and throttle settings for now. Just check if you see plausible data for settings in assist tab.

I don't know if you tried this but connect your display normally to your bike without canable. Switch off, remove your battery from bike for 10 minutes and put it back and see if perhaps your riding parameters in display are there again.
If that not helps you can try with Besst Pro "parameter settings". Do a read, check startup angle and settings and write them back to controller which perhaps can solve your problem.

 

[sandrullo]

@ sandrullo
Regarding walk assist see post 128. For throttle delay that is probably hardcoded in the firmware.

Thanks DPC18RI,
I read post 128 and it seems that these two values, for now, are not available for the BBS01B.
It's a shame because I used the hand throttle instead of the walk assist when I was on steep trails and had to push the bike.
With the throttle so violent and delayed, it's impossible to use and I literally had to push the bike.

I think you are the first person trying / changing settings for BBS01B canbus.

I'm happy to be a tester and I hope it's useful for other people

The program reflected at first the settings / riding parameters from your DPC010CB as i understand it. Then you tried to change walk assist? Or did you also change assist parameters via the program? What did you use? Assist Full or Assist limited tab?

Exactly, the program shows me the values I had initially set on the display (DPC010) using the "riders parameters" menu, which is now no longer visible.
I tried changing the walk assist from the program, entering 6 km/h, and I also tried changing the assist values from the program. In this case, I only slightly changed the power value, using the full assist screen.

I'm just a user like you and i have NO BBS01B canbus but i took a DPC010CB and hub 4.0 controller. Changed riding parameters via DPC010CB display, the program showed the changes also. Then i changed via the program for assist 1 the speed % and the current % clicked save and i can see the changed settings in "riding parameters" in the display done with the program.
Granted, it is not a BBS01B which can react perhaps differently...

I also initially changed the power and speed values from the display. I saw them in the program, but when I tried to do the reverse, that is, modify them from the program, I could no longer see the "riders parameters" on the display. Evidently, the BBS01B reacts differently. I hope that in the future the program will also be able to act on the BBS01B (if I can help with some tests, I'm available).

Also if for some reason the canable locked up, you can try all you want. So sometimes it's best to start fresh! Close browser, close cmd window and unplug canable. Also switch bike off. Wait few minutes switch bike on, plug canable back in PC and start the program again. And stay away from walk assist and throttle settings for now. Just check if you see plausible data for settings in assist tab

Later this afternoon, I'll try again. I'll disconnect the battery, turn everything off, wait about ten minutes, and try again... good idea, I hadn't thought of that before. And I'll stay away from the hand throttle and walk assist settings... For now, the pedal assist settings I see are plausible (they're the ones I initially set on the display).
I'll also add that if the Bafang Go app worked, I could use this app to vary the power levels and speed... unfortunately, I launch the app, it connects to the bike, but when I try to set different assist and speed settings and press SAVE, a moment later the settings are back to ZERO.

I don't know if you tried this but connect your display normally to your bike without canable. Switch off, remove your battery from bike for 10 minutes and put it back and see if perhaps your riding parameters in display are there again.

Later this afternoon, I'll try again. I'll disconnect the battery, turn everything off, wait about ten minutes, and try again... good idea, I hadn't thought of that before.

If that not helps you can try with Besst Pro "parameter settings". Do a read, check startup angle and settings and write them back to controller which perhaps can solve your problem.

I don't understand what you mean... how can I try BEST Pro parameter setting? Where can I find BEST PRO? Where can I read about it?

For completeness... here are two photos... the first with 5 menus dates back to before I connected to the program, the second with 4 menus available is the one I currently have available.




For now, a huge thank you... As soon as I get home, I'll try unplugging the battery and update my situation.

 

[sandrullo]

Hi all,
This afternoon I was able to perform the tests we discussed.
Here's the situation.
I left the battery disconnected for half an hour and then reconnected everything. Nothing changed: the "riders parameters" are no longer visible in the DPC10, so I can't change anything.
I tried setting some values in the program, controller section, but it doesn't save them and consequently they aren't sent to the controller.

This afternoon I took the bike for a short test ride and noticed (I think, I'm not 100% sure) two small changes I had set in the program, which apparently were saved and transmitted to the controller:
The "current limit" I had set to 12A instead of the 15A sold as is (I deduce the 12A current limit from the fact that until before connecting to the program, at PAS1 level, i.e., ECO mode, the motor was drawing about 80W and 2.2A, whereas today it was drawing a maximum of 70W and 1.8A) and the speed limit at all assistance levels: now, even if I pedal at 80 or 90 RPM, the motor continues to provide continuous assistance.

I'm attaching a log of the controller parameter.

Last thing: I tried the Bafang Go app again, even using a VPN and specifying New Zealand as the exit location ( I read somewhere that New Zealand has more permissive legislation than that in force in Europe and perhaps the Bafang app modulates the interventions based on the area of origin of the user ), but it didn't change anything... It allows you to see the screen for setting the assistance value for each PAS, but then it doesn't save the values and consequently doesn't transmit them to the controller....

I don't understand anything anymore.
I wanted to try to improve things and I'm starting to think that maybe I've made them worse.
In any case, I'm still trying to understand. I think that as the days go by, new information and possibilities will be added.

Thanks everyone.

[22:46:38]STATUS:WebSocket connection opened.
[22:46:38]INFO:CAN_DEVICE_STATUS:FOUND:candleLight USB to CAN adapter (by bytewerk)
[22:46:39]INFO:CAN_DEVICE_STATUS:FOUND:candleLight USB to CAN adapter (by bytewerk)
[22:47:01]INFO:CAN_DEVICE_STATUS:CONNECTING:candleLight USB to CAN adapter (by bytewerk)
[22:47:01]INFO:CAN_DEVICE_STATUS:CONNECTED:candleLight USB to CAN adapter (by bytewerk)
[22:47:16]REQ:Syncing all Controller data...
[22:47:16]INFO:Initiating Read Parameter1 from 2...
[22:47:16]INFO:Initiating Read MotorSpeedParameters from 2...
[22:47:16]RX (controller_params_1):{
"system_voltage": 36,
"current_limit": 15,
"overvoltage": 47,
"undervoltage": 35000,
"undervoltage_under_load": 31000,
"battery_recovery_voltage": 184,
"par1_value_offset_6": 136,
"battery_capacity": 10000,
"max_current_on_low_charge": 5,
"limp_mode_soc_limit": 20,
"limp_mode_soc_limit_stage2": 5,
"full_capacity_range": 0,
"pedal_sensor_type": 4,
"coaster_brake": false,
"pedal_sensor_signals_per_rotation": 48,
"speed_sensor_channel_number": 2,
"par1_value_offset_17": 0,
"motor_type": 1,
"motor_pole_pair_number": 8,
"speedmeter_magnets_number": 1,
"temperature_sensor_type": 0,
"deceleration_ratio": 21.98,
"motor_max_rotor_rpm": 2455,
"motor_d_axis_inductance": 201,
"motor_q_axis_inductance": 253,
"motor_phase_resistance": 159,
"motor_reverse_potential_coefficient": 11,
"throttle_start_voltage": 1.2,
"throttle_max_voltage": 3.6,
"speed_limit_enabled": 1,
"start_current": 0,
"current_loading_time": 0,
"current_shedding_time": 0,
"assist_levels": [
{
"current_limit": 36,
"speed_limit": 32
},
{
"current_limit": 15,
"speed_limit": 100
},
{
"current_limit": 48,
"speed_limit": 43
},
{
"current_limit": 25,
"speed_limit": 100
},
{
"current_limit": 63,
"speed_limit": 57
},
{
"current_limit": 35,
"speed_limit": 100
},
{
"current_limit": 77,
"speed_limit": 73
},
{
"current_limit": 60,
"speed_limit": 100
},
{
"current_limit": 100,
"speed_limit": 100
}
],
"displayless_mode": false,
"lamps_always_on": false,
"walk_assist_speed": 0,
"par1_value_offset_62": 0,
"_rawBytes": [
36,
15,
47,
24,
121,
184,
136,
16,
39,
5,
20,
5,
0,
4,
0,
48,
2,
0,
1,
8,
1,
0,
150,
8,
151,
9,
201,
0,
253,
0,
159,
0,
11,
0,
12,
36,
1,
0,
0,
0,
36,
15,
48,
25,
63,
35,
77,
60,
100,
32,
100,
43,
100,
57,
100,
73,
100,
100,
0,
0,
0,
0,
0,
37
]
}
[22:47:17]ACK:Read Parameter1 successful.
[22:47:17]ACK:Read MotorSpeedParameters successful.
[22:47:40]REQ:Syncing Gears data ...
[22:47:40]INFO:Initiating Read Parameter0 from 2...
[22:47:40]INFO:Initiating Read Parameter1 from 2...
[22:47:40]INFO:Initiating Read Parameter2 from 2...
[22:47:40]INFO:Initiating Read Startup Angle from Controller...
[22:47:40]RX (controller_params_0):{
"par0_value_offset_0": 50,
"acceleration_levels": [
{
"acceleration_level": 1
},
{
"acceleration_level": 2
},
{
"acceleration_level": 2
},
{
"acceleration_level": 3
},
{
"acceleration_level": 3
},
{
"acceleration_level": 3
},
{
"acceleration_level": 4
},
{
"acceleration_level": 4
},
{
"acceleration_level": 4
}
],
"assist_ratio_levels": [
{
"assist_ratio_level": 30
},
{
"assist_ratio_level": 60
},
{
"assist_ratio_level": 100
},
{
"assist_ratio_level": 140
},
{
"assist_ratio_level": 170
},
{
"assist_ratio_level": 200
},
{
"assist_ratio_level": 240
},
{
"assist_ratio_level": 290
},
{
"assist_ratio_level": 340
}
],
"assist_ratio_upper_limit": 500,
"unknown_bytes": [
50,
20,
0,
0,
0,
0,
0,
0,
0,
0,
0,
4,
15,
15,
15,
15,
15,
10,
10,
8,
6,
244,
1,
1,
5,
244,
1,
96,
9,
96,
9,
96,
9
],
"_rawBytes": [
50,
1,
2,
2,
3,
3,
3,
4,
4,
4,
30,
0,
60,
0,
100,
0,
140,
0,
170,
0,
200,
0,
240,
0,
34,
1,
84,
1,
244,
1,
50,
20,
0,
0,
0,
0,
0,
0,
0,
0,
0,
4,
15,
15,
15,
15,
15,
10,
10,
8,
6,
244,
1,
1,
5,
244,
1,
96,
9,
96,
9,
96,
9,
0
]
}
[22:47:40]ACK:Read Parameter0 successful.
[22:47:40]RX (controller_params_1):{
"system_voltage": 36,
"current_limit": 15,
"overvoltage": 47,
"undervoltage": 35000,
"undervoltage_under_load": 31000,
"battery_recovery_voltage": 184,
"par1_value_offset_6": 136,
"battery_capacity": 10000,
"max_current_on_low_charge": 5,
"limp_mode_soc_limit": 20,
"limp_mode_soc_limit_stage2": 5,
"full_capacity_range": 0,
"pedal_sensor_type": 4,
"coaster_brake": false,
"pedal_sensor_signals_per_rotation": 48,
"speed_sensor_channel_number": 2,
"par1_value_offset_17": 0,
"motor_type": 1,
"motor_pole_pair_number": 8,
"speedmeter_magnets_number": 1,
"temperature_sensor_type": 0,
"deceleration_ratio": 21.98,
"motor_max_rotor_rpm": 2455,
"motor_d_axis_inductance": 201,
"motor_q_axis_inductance": 253,
"motor_phase_resistance": 159,
"motor_reverse_potential_coefficient": 11,
"throttle_start_voltage": 1.2,
"throttle_max_voltage": 3.6,
"speed_limit_enabled": 1,
"start_current": 0,
"current_loading_time": 0,
"current_shedding_time": 0,
"assist_levels": [
{
"current_limit": 36,
"speed_limit": 32
},
{
"current_limit": 15,
"speed_limit": 100
},
{
"current_limit": 48,
"speed_limit": 43
},
{
"current_limit": 25,
"speed_limit": 100
},
{
"current_limit": 63,
"speed_limit": 57
},
{
"current_limit": 35,
"speed_limit": 100
},
{
"current_limit": 77,
"speed_limit": 73
},
{
"current_limit": 60,
"speed_limit": 100
},
{
"current_limit": 100,
"speed_limit": 100
}
],
"displayless_mode": false,
"lamps_always_on": false,
"walk_assist_speed": 0,
"par1_value_offset_62": 0,
"_rawBytes": [
36,
15,
47,
24,
121,
184,
136,
16,
39,
5,
20,
5,
0,
4,
0,
48,
2,
0,
1,
8,
1,
0,
150,
8,
151,
9,
201,
0,
253,
0,
159,
0,
11,
0,
12,
36,
1,
0,
0,
0,
36,
15,
48,
25,
63,
35,
77,
60,
100,
32,
100,
43,
100,
57,
100,
73,
100,
100,
0,
0,
0,
0,
0,
37
]
}
[22:47:40]ACK:Read Parameter1 successful.
[22:47:40]RX (controller_params_2):{
"torque_profiles": [
{
"start_torque_value": 0,
"max_torque_value": 0,
"return_torque_value": 0,
"min_current": 0,
"max_current": 0,
"torque_decay_time": 0,
"start_pulse": 4,
"current_decay_time": 0,
"stop_delay": 0
},
{
"start_torque_value": 0,
"max_torque_value": 0,
"return_torque_value": 0,
"min_current": 0,
"max_current": 0,
"torque_decay_time": 0,
"start_pulse": 0,
"current_decay_time": 0,
"stop_delay": 0
},
{
"start_torque_value": 0,
"max_torque_value": 0,
"return_torque_value": 0,
"min_current": 0,
"max_current": 0,
"torque_decay_time": 0,
"start_pulse": 0,
"current_decay_time": 0,
"stop_delay": 0
},
{
"start_torque_value": 0,
"max_torque_value": 0,
"return_torque_value": 0,
"min_current": 0,
"max_current": 0,
"torque_decay_time": 0,
"start_pulse": 0,
"current_decay_time": 0,
"stop_delay": 0
},
{
"start_torque_value": 0,
"max_torque_value": 0,
"return_torque_value": 0,
"min_current": 0,
"max_current": 0,
"torque_decay_time": 0,
"start_pulse": 0,
"current_decay_time": 0,
"stop_delay": 0
},
{
"start_torque_value": 0,
"max_torque_value": 0,
"return_torque_value": 0,
"min_current": 0,
"max_current": 0,
"torque_decay_time": 0,
"start_pulse": 0,
"current_decay_time": 0,
"stop_delay": 0
}
],
"unknown_bytes_1": [
0,
0,
0,
0,
0,
0
],
"unknown_bytes_2": [
110,
150,
100,
110,
5,
0,
0,
0
],
"acceleration_level": 3,
"_rawBytes": [
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
4,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
3,
110,
150,
100,
110,
5,
0,
0,
0,
226
]
}
[22:47:40]ACK:Read Parameter2 successful.
[22:47:40]RX (controller_startup_angle):{
"startup_angle": 30
}
[22:47:40]ACK:Read Startup Angle successful.

 

[DPC18RI]

Last thing: I tried the Bafang Go app again,

Did this app worked before with your BBS01B? It is known that some versions, in some situations can wipe settings to zero by just connecting it. Search for this on emtb forums.

...and the speed limit at all assistance levels: now, even if I pedal at 80 or 90 RPM, the motor continues to provide continuous assistance.

That's because your log shows that your 5 (display) assist levels for speed are set to 100%.
The acceleration levels and assist ratio levels for all 9 levels are still original as when you first bought it. (compare it to picture from dagobird post 102)

The controller, your log and the program has 9 assist levels. Your display is set to use 5 of them (Modi 6 in your display settings, i guess they now count "0" as a mode too that's why they call it "modi 6" although only using 5 from 9 available levels in controller). So from the 9 available in the program and controller your display is using assist levels 2,4,6,8 and 9.
(The nr 1 and 3 and 5 and 7 in the program and in controller are still at original setting just the same as in picture from post 102 because your display is not using these).

So to check for sure if the program will save it or not: Start program fresh and go change in the program in "assist full" the speed limit % for assist level 2 from 100% to for example 30% and save it. Wait 30 seconds and click sync data to see if it still shows 30%. If yes disconnect all and go ride and test with display assist set to ECO if it will stop support at around 10km/h.
Eco on the display should be the same as assist level 2 in controller and program. When you switch assist on the display to "boost" assist that "Boost" mode should use the settings from assist level 9 in the program.

 

[sandrullo]

Did this app worked before with your BBS01B? It is known that some versions, in some situations can wipe settings to zero by just connecting it. Search for this on emtb forums.

Hi DCP18RI e many thank's...
Sorry, I'm not sure about this, but I can say there was an automatic update to the app 3 days ago. It's currently version 4.0.7.

That's because your log shows that your 5 (display) assist levels for speed are set to 100%.
The acceleration levels and assist ratio levels for all 9 levels are still original as when you first bought it. (compare it to picture from dagobird post 102)

The controller, your log and the program has 9 assist levels. Your display is set to use 5 of them (Modi 6 in your display settings, i guess they now count "0" as a mode too that's why they call it "modi 6" although only using 5 from 9 available levels in controller). So from the 9 available in the program and controller your display is using assist levels 2,4,6,8 and 9.
(The nr 1 and 3 and 5 and 7 in the program and in controller are still at original setting just the same as in picture from post 102 because your display is not using these).

I've attached a screenshot of the program, which shows the situation on 5 levels.
I deliberately set all levels to 100% speed because I want it to continue providing assistance even if I pedal at 80 or 90 RPM, or whatever speed I want.

So to check for sure if the program will save it or not: Start program fresh and go change in the program in "assist full" the speed limit % for assist level 2 from 100% to for example 30% and save it. Wait 30 seconds and click sync data to see if it still shows 30%. If yes disconnect all and go ride and test with display assist set to ECO if it will stop support at around 10km/h.
Eco on the display should be the same as assist level 2 in controller and program. When you switch assist on the display to "boost" assist that "Boost" mode should use the settings from assist level 9 in the program.

I did this test a few minutes ago, and I can confirm that as soon as it reaches 10 km/h, it decreases the assistance level, so these values are recorded on the controller and are effective on the motor and the bike.
I discovered that there's another value that is recorded and applied, the "startup angle" value.

Right now, this is my understanding: the program allows you to record some values of what's visible on the various screens. At least with the BBS01B. I hope everything will be implemented in the coming weeks and months. For me, it would be important to have a walk mode that pushes up to 6 km/h, but now it stops at 2.5 km/h, and a small climb is enough to stop it from moving.

In my case, there's a further complication, since the "riders parameters" have disappeared from the display menu, and the Bafang Go app doesn't recognize any changes.

I purchased the engine at the beginning of September from AliExpress, so I'm asking the seller questions to see if he can offer me any solutions.

 

[DPC18RI]

I think you mentioned in a previous post that settings in GO app revert to zero. So tell them while you used GO app the settings in the app changed to zero and now you can't change them with app anymore. And that you now need the firmware from your BBS01B canbus 36 volt to restore.... If they send it to you, do not do firmware update! It must be analyzed first...

Regarding the "riding parameters" in the display gone, i'm pretty sure they are still there but just not showing because when display starts or when entering settings it checks for something, but i can't recall what it looks for... Anyway when it checks and it thinks it's not there it will not show riding parameters and keep them hidden.

Edit, without original BBS01B CAN 36 volt firmware there is not much more what can be done to test because when failure we need to be able to upload firmware again. So the first thing to have is the firmware...

 

[sandrullo]

OK, I'll ask the seller for the firmware and we'll evaluate it together.
I also think they're just hidden...
It takes a lot of patience with these toys for us bikers...
Thanks as always...

 

[sandrullo]

Hi all,
I have some inexplicable news...
This morning I turned on the display to take a video to explain the situation to the seller, and to my great surprise, the rider parameters menu is now available, and the Bafang GO app is saving the changes.
I don't understand how this is possible;
in the past few days, nothing worked.
Now I still have to solve the walk mode problem, which is stuck at 2.5 km/h and needs to reach 6 km/h.

I'm speechless... and I have no explanation, because I didn't do anything in particular.
Last night I didn't have the rider parameters (see image in the previous post), and the Bafang GO app wasn't saving any settings, and now it works.
If I change the display, I see the changes on the app, and vice versa... and that's great news for me.

P.S. Last night, the motor remained connected to the battery, so I don't think it was a natural reset.