• Hello ES! We could use some help to get us past the finish line on building the new knowledgebase for the forum.
    Can you donate? Please see our fundraising page. Thank you!

Bafang Canable Pro Master - discussion

I wonder if instead of trial and erroring the different methods it'd be better to have a map of which hardware versions support which methods? Of course this would take time and probably crowdsourcing of data to implement, but maybe something to work towards...

I'm hesitant to try too many more things with my controller unfortunately since I have no other method of flashing and this is my primary means of transport.
 
Some people complained that Bafang BBSxx switched over to canbus and they will not be able anymore to change settings. But user dagobird from German pedelec forum bought a BBS01B Canbus and used mdi-9 his release V1.3 .exe file to install the program.
As you can see in his picture below, the BBS01B has even "assist ratio levels" and "acceleration" setting for each level.

What i sometimes read regarding the program is that people are hesitant because "to complicated" to install from source code.

But you can also run the software from the "latest release" executable as user dagobird did.
And if you are not able to prepare the cable, you still can use the link from stancecoke to buy a ready made cable.

BBS01B Canbus Assist Full.jpg
 
Last edited:
it'd be better to have a map of which hardware versions support which methods?
To create such map we would have to have all motors and record besst update procedure on every single one - not possible.

I'm hesitant to try too many more things with my controller unfortunately since I have no other method of flashing and this is my primary means of transport.
I thing missing part from your end is shorting orange and black wire. But not sure if it's via resistor, I do not done that (m820 do not need that).
Ask @DPC18RI for detials.
 
His bike is his primary means of transport... So i don't want to risk it fails because he will not be able to drive anymore until firmware is correctly replaced.
Yesterday afternoon, because of my fw_upgrade.js failed for HUB cntrl. via "new method" (old method ok, also for M400) I downloaded the complete source code again. I tried from within the program, but it also stops at a few % upload for my hub controller just like my fw_upgrade.js did.

So today i looked at my previous version which still does work for Hub controller using "new method". I tried comparing it to the combined latest version i have. I know the reason now. Back then, tested hub controller, eventually worked. M400 not. We changed code till M400 did work.

Code then got changed to work for the 2 methods. Tested that with M400 => worked. But i did then not test again the hub controller if i recall well to see if that still worked... Probably because i was already in the middle of trying display to update...

Because of the question from FlippyThermos i wanted to check first and connected hub cntrl again and realized the hub controller did not work anymore via "new method" in combined code.
Anyway today after several hours i got my fw_upgrade.js working again for hub controller. It picks automatically "new method" and if i force it to use "old method" it works too. Also M400 still works, it picks automatically "old method".
There is more to it i wonder about because i'm no coder but ok it's working. The M820 looks way less picky :)
 
OK so send me this working code, and i will compere it with last version.

His bike is his primary means of transport... So i don't want to risk it fails because he will not be able to drive anymore until firmware is correctly replaced.
Thats why i was asking for users with besst or K1 for now. Specialy if its first time for that motor.
 
Many thanks to all developers! Great job!
I tried canable on M560. Everything is read except Driving Parameters and Torque Sensor-Controlled Assist (Parameter Block 2). Display Settings (mileage) and Assist Levels can be saved. Controller parameters are not saved - neither Speed Limit, nor Wheel Circumference, nor the rest. Electric Parameters, Driving Parameters are marked as changeable, but it seems they should not be so on M560. Firmware update works.
 
Today succesfull fw update of HMI DPC245. Was hard to get this working, very ciritical here is time beetwean frames.
Method diffrent then DPC18.
Where did you get the firmware for dpc245? What does the new firmware provide?
 
Firmware for displays are in pack which is posted on page 4. Don't know the difference between them.
 
Hi, beginners question:
my display (VD618, Varstrom) allows to select between 3/5/9 support levels. Default is 5 (BBS01B).
Is that because the controller (its firmware) defines (is fixed to) 5 or could i choose to change to 9...?
If I read the controller data with "openbafang-cannable-win-x64" it shows 9 levels with different data (speed, Amperes, acceleration). Does it mean they exist and I can use them (change from 5 to 9 levels) or are this virtual data points?
Thanks
 
i have dpc241 and you can select 3\5\9 levels of assist which is handy because its easy to get power level that suits you in certain situation . i also have dpc 245 and dpc080 and they offer only 3\5 assist levels...
 
Controller has 9 levels. if your display let you select 3/5/9 then at 9 you use all 9 levels from controller. At 5 it maps to certain 5 levels from 9 in controller. If you set your display to 3 levels, then those 3 assist levels maps to 3 certain levels from 9 in controller where your 3th from 3 in display is then the same as the 9th level in controller.
And the 5th from 5 assist levels maps to the 9th level in controller. So at 5 from 5 it is then the same as 9th level in controller.

So the assist levels from a display set at 5 will map to 5 certain levels from 9 in controller.

Assist 1 from 5 maps to 2 (from 9 in controller) and 2 maps to 4 and 3 maps to 6 and 4 maps to 8 and 5 maps to 9.
Display's set at 5 assist levels maps mostly to the even numbers below the 9th in controller but some display's map to the uneven numbers below the 9th level from controller.
 
not sure how this works in case of setup where every assist level has slightly different power curve / max power level . to have this suited best i'd setup it every time number assist levels changes ...
 

Attachments

  • clipboard.jpg
    clipboard.jpg
    400.8 KB · Views: 54
Hello, respect to the developers. Tell me, I have an M625 engine, can I use your experience?
 
I don't think anyone has tested this motor with canable yet. So you could be the first.
 
Regarding DPC18 there is a difference between hardware versions and method used...
I noticed it also depends on motor controller used. For example a DPC080CB HW 1.0 can be updatet when it is connected the normal way to my hub controller, the display update works. With M400 HW 1.0 display go's black...
So the combination display / motor controller plays a role too! Best is to have Besst tool laying around in case a display update go's south.
 
Last edited:
Don't know how this works under the hood. I'm only trigger it the same way as BESST do.
1756995221626.png
With M820 for example it helps with unwanted motor cut off power on some firmwares.
 
Many thanks to all developers! Great job!
I tried canable on M560. Everything is read except Driving Parameters and Torque Sensor-Controlled Assist (Parameter Block 2). Display Settings (mileage) and Assist Levels can be saved. Controller parameters are not saved - neither Speed Limit, nor Wheel Circumference, nor the rest. Electric Parameters, Driving Parameters are marked as changeable, but it seems they should not be so on M560. Firmware update works.
Your M560 can you tell me controller hardware version? What display was connected and the hardware version of it? Thanks.
 
I rewrote post 2 with my findings and the ones from mdi-9 regarding updating firmware certain controllers and display's. I tried to explain the steps as good as i could but it's not guaranteed it works for yours too.
 
Last edited:
Back
Top