Bafang Canable Pro Master - discussion

[stancecoke]

I'm looking for testers of firmware update option

I tried it for my hubmotor controller, but it fails with a timeout error, see attached log.

 

[mdi]

Looks like controler do not respond for new method at all. Can u send me your bin file ?

 

[stancecoke]

Maybe it's the wrong bin file for my hardware. But I have no other. If someone has a suitable bin file for this hardware, I can try it again.

 

[mdi]

But with BESST this file is flushing ? How old is this motor ?

 

[stancecoke]

I have no BESST and it's the hubmotor controller from Windmeile.de

 

[DPC18RI]

Maybe it's the wrong bin file for my hardware. But I have no other. If someone has a suitable bin file for this hardware, I can try it again.

Is it possible you mixed the extracted one from your controller and the one i had send you? According to HxD the .bin you used (fw.bin) is a match with mine. So that is probably the wrong one for your controller.
A warning, if you do not have Besst tool or K1 flash i would not attempt to try to flash your extracted bin.
If you get error 30 like me IN the process of flashing, even Besst can not reach the controller anymore via the normal way..

 

[stancecoke]

even Besst can not reach the controller anymore via the normal way..

No problem, my "normal way" is the SWD interface with the StLink

 

[DPC18RI]

After spending yesterday hours and hours in the garden house at 34 degree Celsius inside temp, i finally had success this morning (on stubborn hub controller). Firmware update worked now without any hiccup. No locked controller with error 30 anymore, no display that go suddenly black at step 5, no weird ID's anymore etc.

I knew it had something to do with the controller state it is in or needs to be in for this controller? once the update process starts and reaching step 5 it flew past it this time and ended in "update successfully". (roughly 2 minutes for this controller).
I did the firmw. update with same firmw. version which was already in controller and afterwards with another software version to be... Sure.
The update firmware process i did 2 times was with no display connected.

Attached is mdi-9 log too and log from savvycan which was also connected.

 

[mdi]

Last release with fw update from gui:

Releases · mdi-9/bafang_canable_pro

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

github.com

 

[mdi]

Last rls (1.3) with:
- 5x faster fw upload
- fixed fw upload for old motors

 

[FlippyThermos]

Nice to see how far this has come. Any chance we can get firmware dumping added? Not sure how possible this is but it might be helpful for sharing compatible firmware etc

 

[mdi]

Any chance we can get firmware dumping added?

Does besst tool have that option ? All our job for now is based on besst tool sniffing.

 

[stancecoke]

Not sure how possible this is

I don't think, that this is possible. But there are tons of Bafang firmwares available, Bafang seems to have no problem to share them, see the K1ebike homepage...
I would be interested in having an overview, which controller uses which processor, for my hub motor controller with she STM32 Clone, I was able to dump the original firmware via the SWD interface.

 

[pxl666]

I don't think, that this is possible. But there are tons of Bafang firmwares available, Bafang seen to have no problem to share them...

would you mind sharing them ? for M motors ? i have hard time trying to update m500/600 with firmwares i have and maybe some of these that you have will work ?

 

[stancecoke]

would you mind sharing them

I don't have them, the pictures are from the k1ebikes hompage. Perhaps, someone who bought a K1flash is willing to share them. See the "firmware notes and files" button. Quite a lot firmware bin files are availabe on github also.

List of Firmwares included on Flash SD card:

Flash - K1 eBikes - Bafang Tuning and Services

oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 Introduction Set Motor Parameters Firmware Update Rotor Calibration Firmware notes and Files Pricing and Ordering Hello Bafanger...

www.k1ebikes.com

 

[mdi]

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

 

[Deko]

I don't have them, the pictures are from the k1ebikes hompage. Perhaps, someone who bought a K1flash is willing to share them. See the "firmware notes and files" button. Quite a lot firmware bin files are availabe on github also.

Flash - K1 eBikes - Bafang Tuning and Services

oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 oplus_3145728 Introduction Set Motor Parameters Firmware Update Rotor Calibration Firmware notes and Files Pricing and Ordering Hello Bafanger...

www.k1ebikes.com

Is there a separate branch, topic, repository on GitHub? Can I ask for a link?

 

[stancecoke]

Can I ask for a link?

It's the old repo, you can find many useful things there...

Bafang_M500_M600/Firmwares at main · OpenSourceEBike/Bafang_M500_M600

Contribute to OpenSourceEBike/Bafang_M500_M600 development by creating an account on GitHub.

github.com

 

[FlippyThermos]

The firmware update seems to fail for my M600. Hardware version is reported as CR X10N.500.FC 3.2 and software CRX10NC3618i132071.2. I'm trying to flash a CRX10NC3625i132047.7 firmware to see if it lets me throttle from standstill.

I plug the canable between display and controller as usual, it successfully gets controller info. When I start update procedure the display turns off, but it doesn't respond and reaches a timeout. Is my controller unable to be flashed or is something else happening?

Edit: it also logs "no ack" in the console so possibly its the issue reported earlier where the wrong byte is sent and it doesnt go into firmware update mode?

 

[mdi]

Provide log, if u used executable it should be created in:
C:\snapshot\bafang_canable_pro\logs

To do update with M400 DPC18RI was shorting black and orange wire and do it without display connected. So maybe wait for him to share more info about it.

 

[b747]

Hello all, I'm considering buying the BBS02B CANBUS version and was wondering, can this Bafang CANable Pro tool be used to fix the throttle lag issue reported by some users? They are reporting a lag of about 1 sec between commanding the throttle and the motor responding. I think pedal assist might also have this lag, but I'm not totally sure. Users state the UART version does not have this lag, and various displays like the EKD01 do not have the setting to adjust this lag (even the EKD01 from Varstrom with the new firmware with advance settings). Thanks in adance for your help!

 

[FlippyThermos]

Provide log, if u used executable it should be created in:
C:\snapshot\bafang_canable_pro\logs

To do update with M400 DPC18RI was shorting black and orange wire and do it without display connected. So maybe wait for him to share more info about it.

Okay, here's the log.

 

[mdi]

Yes looks the same as with m400, controler goes off after reciving update command.

 

[DPC18RI]

Seems it tries for 10 seconds the new method and then for 5 seconds the old method but i see no old method ID's in the log?

On another note, there was already a week or so passed sinds i tested hub controller, the M400 and then getting the display firmw update working. So because of the problem from FlippyThermos i decided first to test controllers again using few times updated fw_update.js and the M400 still worked.
The code auto switched to old method and update successful.

Then the hub cntrl test, (which worked before with "new method") this one can react to both methods, so the "new method" comes first and it reacted to it. At 4% bam it stops... and it's semi dead.

I then have set in the code for "old method" to come first this time, the hub cntrl updated fine with old method. But not anymore via "new method" it just stops in the update.

I looked for an older fw_update.js i still had and used that one and this time hub controller did the update fine via "new method".
So in the latest fw_update.js i have, something is there the hub controller does not like for "new method"...

 

[mdi]

Seems it tries for 10 seconds the new method and then for 5 seconds the old method but i see no old method ID's in the log?

Because it responds to new method and goes off.

I looked for an older fw_update.js i still had and used that one and this time hub controller did the update fine via "new method".
So in the latest fw_update.js i have, something is there the hub controller does not like for "new method"...

Maybe speed.