KT motor controllers -- Flexible OpenSource firmware for BMSBattery S/Kunteng KT motor controllers (0.25kW up to 5kW)

[Angrubean]

Did everything in the new controller, problem I can't connect with the bluosec it crashes few seconds after trying to connect, don't know how to fix that

I too had this issue, and I suppose this is something that has affected many users since the newer versions of sdcc. Try to downgrade to an older version of sdcc.

Hi,
in case someone is struggling to get BluOSEC app to work (it crashes on start), here's what you can try.
The culprit is SDCC 4.2.0, which for some reason doesn't want to operate properly with current master branch. The results are the following:

• It renders previously flashable setups corrupt (controller will drain only 20mA)
• Flashing freshly cloned master will result in BluOSEC app crashing
• Produces otherwise no errors anywhere (log, onscreen)

The solution for this should be fairly simple. Uninstall SDCC 4.2.0, reboot your machine, and then install SDCC 4.1.0 (2nd reboot just in case)
4.1.0 package can be found here: Small Device C Compiler - Browse /sdcc-win64/4.1.0 at SourceForge.net
I have also archived it in case the repo goes offline at some point.

I'm hoping to add full explanation to the wiki at some point, but recently got quite busy at work.

 

[nightwind]

Hello everyone,
this is my first post here.
I want to try open source firmware on my bike made from Himo c20 and kt36 controller. I need advice, will this firmware work on my bike? Motor phases are specially was mixed up from the factory, but I resoldered the wires and it works. but runs only with special setting **C2** Phase shift mode = 1.
I dont know what it is, and whether there is / whether such a setting is needed for Opensource firmware
if it doesnt work, I won’t be able to restore the Chinese firmware back, and I will be left without a bike))
Thank you in advance

 

[Voron]

Yeah i've used it. It works great. Best fork is Andrea-104 or torque from x4. They're more stable.

What programmer did you use? The ST-Link v2 dongle? Or the official ST-Link (v2,v3)?

Do you think that it's safer to instead use a 6 FET for this firmware?

I suppose that the 9 FET and 6 FET should have the same phase current because there's still only 1 FET on one of the sides that limits the max phase current to whatever it can withstand, would that be correct?

 

[Vbruun]

I have used a cheap st-link v2 copy dongle.

I don't think it matters which controller you use the firmware on. I have no first hand experience with the 6-fet, but since it is rated for lower current by KT I would think that the 9-fet can take a bit more.

The phase current is limited by the plug if you use the waterproof overmoulded version, at least on the amk q-128.

 

[Voron]

From what I've seen on the normal 6 fets, there are versions that range from 14 up to 22+-1 amperes. I suppose that it's mostly on the mosfets. The less powerful 6 fets use less powerful mosfets. That also explains why the 6 fet hailong controllers only has a max of 15 amperes.

All pictures of the 6 fet hailong pcb shows that the 5 v regulator actually is cooled properly, it also has a bit more space inside. I suppose it'll be easier use a 6 fet instead of 9 fet, especially because of the rare problems with them on this firmware.

Judging by the industry, 9 fet controllers doesn't seem to be that popular. KT them selves only have one version of the 9 fet and more powerful controllers like the baserunner also use only 6 mosfets. So by this I suppose it's better to stick to a 6 fet, at least for the hailong versions.