Bafang M560 FC2.0

[Dado]

Looks like we have updated version of M560 FC2.0

So far only this label picture.

Unlucky, there is same torque sensor. Thought Bafang will use new torque sensor from RS model.
Firmware version 60.3 - these high number are usually custom firmwares for sellers.
27 Amps max. So plus 100W.

Will open it up, once it comes to my hands.

 

[Dado]

Bafangers, good news.

Possible to flash 27A firmware into M560 FC1.0 (same bootcode). Looks like all works on a bench. I am quite surprised FC2.0 firmware possible to load into FC1.0. It again breakes any labeling bafang conventions.

Will try tomorrow on a road.

v60.5

 

[Dado]

FC2.0 comes with same controller as was in M560RS. PCB v1.7 202412
Not possible to load older firmwares (v1.5 , v1.6) to FC2.0 - but it works other way (load 27A firmware v60.5 into FC1.0).




Looks like firmware in TS is different:
M560 FC1.0

M560 FC2.0

 

[E-nduroRider]

Hi Dado, why should we choose to go for 27A FW? any benefits ? other than it will have more power and put more strain on drivetrain and electrical components compares to 25A FW?

 

[Dado]

You know, now race for power started. Already lot of people contacted me to swap M500 M510 for M560.

You right 2 Amps more does not play much role. (Also we dont know if phase current was extended, I guess stayed same at that 150Nm) And as you saying just a more stress on a drivetrain. Have just snapped my chain yesterday. Was old already. With gentle shifting you can make 1500km. With behaviour I dont see anything bad, same as v1.5 or v1.6.

FC2 motor has new iteration of controller and reading me different firmware from torque sensor.

But is great this 27A fc2 firmware works also in older M560, so you can try.

 

[E-nduroRider]

Yes it is obvious that all motor manufactures are marketing torque and power numbers currently. The M560 25A is plenty powerful as is. However, the FC 2.0 controller with TS fw update is welcome, it could mean smoother power delivery or better responsiveness, i guess we wont know as Bafang is not very open regarding updates/changelog

And it is great that 27A FC2 firmware will work on older M560. But have you noticed any change in heat or battery range with it?

 

[Dado]

Yes it is obvious that all motor manufactures are marketing torque and power numbers currently. The M560 25A is plenty powerful as is. However, the FC 2.0 controller with TS fw update is welcome, it could mean smoother power delivery or better responsiveness, i guess we wont know as Bafang is not very open regarding updates/changelog

And it is great that 27A FC2 firmware will work on older M560. But have you noticed any change in heat or battery range with it?

Will test heating at some long uphill in a hot day. You know, 2 Amps more is 8% so you can count 8% more consumption when riding full power. Important is to set your max power levels and Support level %.

In RS model was brand new torque sensor from HW point of view (I was not removing TS from motor, but looks to me had optical detection of rotation). Not sure what happend with this new TS, was expecting it will be in FC2.0. And it is almost year since M560RS.

 

[Wowo]

You know, now race for power started. Already lot of people contacted me to swap M500 M510 for M560.

You right 2 Amps more does not play much role. (Also we dont know if phase current was extended, I guess stayed same at that 150Nm) And as you saying just a more stress on a drivetrain. Have just snapped my chain yesterday. Was old already. With gentle shifting you can make 1500km. With behaviour I dont see anything bad, same as v1.5 or v1.6.

FC2 motor has new iteration of controller and reading me different firmware from torque sensor.

But is great this 27A fc2 firmware works also in older M560, so you can try.

Can you share this firmware?

 

[kuba4333]

Has anyone tested the improved m560 in terms of volume? In a YouTube test, it seems to be much quieter, but I also found opinions that there is still an annoying high-pitched sound.

 

[Dado]

Is a high pitch sound at specific higher rpms. And is weird as I havent notice it in previous version. There was more heard a mechanical noise.

 

[Waynemarlow]

Mine is only a few months old and supposedly the Quiet version but annoyingly loud at higher rpm. I’ve done a couple hundred clicks on it now and it has quietened down considerably than when new. I know my M510 took over 500 kms to really settle down but this is more electronics than mechanical.

Oddly enough for one who hates mechanical noise, the electronic noise it makes is actually quite easy to ignore.

 

[Timege]

Is a high pitch sound at specific higher rpms. And is weird as I havent notice it in previous version. There was more heard a mechanical noise.

Hi.

Subject: Feature proposal for K1 chip: Sram AXS, Avinox-style shifting, and Zero-Overrun
Hi
I’ve been following your work on the K1 chip for Bafang motors, and it’s truly impressive. I’m reaching out because I have a few feature ideas that could elevate the chip's functionality to the level of top-tier modern drives like DJI Avinox.
I believe these could be implemented by utilizing the shift sensor and brake sensor inputs on the K1 chip. Here is what I have in mind:
Sram AXS Support (Avinox-style workaround)
Concept: Implement a workaround to sync or intercept shifting signals, similar to how DJI Avinox handles wireless integration, allowing the motor to react instantly to AXS shifter inputs.
Smart Shifting (Analogous to Avinox "Smooth Shift" & "Safe Shift")
Concept: * Smooth Shift: Briefly reducing motor torque during a gear change to ensure seamless, crisp shifting under load.
Safe Shift: Protecting the drivetrain by cutting power or limiting torque during abrupt or heavy shifting to prevent chain/cassette damage.
Zero-Overrun
Concept: Eliminating the motor overrun (the short delay where the motor keeps pushing after you stop pedaling). The motor should cut power the exact millisecond the rider stops pedaling or touches the brakes.
Technical Implementation Idea:
To make this happen without redesigning the core hardware, we could potentially feed these control triggers directly through the shift sensor and brake sensor lines on the K1 chip. For instance:
The AXS/shifting logic can trigger the shift sensor input to momentarily drop torque.
The brake sensor logic can be optimized to achieve the instant Zero-Overrun cutoff.
I think these features would make the K1 chip an absolute game-changer for Bafang users who want a premium, modern e-MTB experience.
What do you think about this? Is this something technically feasible within the current K1 architecture? I’d love to hear your thoughts!
Best regards,

 

[Dado]

Hello.

Not a bad idea...
AXS signal must be readable, and need to be able to pair. Avinox can read?
Not possible to moderate power, only as you saying over brake signal.

Question is if AXS wont be shifting faster than Bafang will process it. That shift and brake sensors also living their own lifes with different firmwares.

I am fine here with M560 firmwares. I am going over throttle, and releasing throttle before shift. Have there Eco mode, so pedalling all the time. And it is very smooth and fast shift. Going usually in double shifts.

 

[kuba4333]

I'd love to know if the ebics software works on the new m560 fc2.0 version. With the besst interface, you can test it. There shouldn't be any problems with reverting to the original software.

GitHub - EBiCS/BAFANG_GD32F303RCT6: Firmware for Bafang E-Bike controllers with GD32F303 processors

Firmware for Bafang E-Bike controllers with GD32F303 processors - EBiCS/BAFANG_GD32F303RCT6

github.com

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

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

github.com