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

[stancecoke]

I think there is no issue for having only 1 button, that does always the same: flash option bytes + firmware.

OK, that would be even easier

regards
stancecoke

 

[reset]

You have to press the "Write Option Bytes" Button of the Java Tool once with a brand new controller...

regards
stancecoke

Thanks that seemed to work, I'm struggling with the voltage at the moment but will let you know.

 

[stancecoke]

I'm still wondering, why the restarts don't happen, if the option DISPLAY_TYPE_KT_LCD3 is activated. (even in parallel to the option DIAGNOSTICS)

I just found and fixed a bug in the firmware. The UART-interrupt-routine was not declared, if no display was selected. Now it works without the pullup resistor at the rx-line in diagnostics mode.

regards
stancecoke

 

[geofft]

I just found and fixed a bug in the firmware. The UART-interrupt-routine was not declared, if no display was selected. Now it works without the pullup resistor at the rx-line in diagnostics mode.

Good find! It seems that you're still happy to fix bugs with your fw, so maybe I should mention something I spotted earlier..

I did a calibration of the wattmeter recently and found that my motor has actually been drawing a max in excess of 1kw. I'm trying to restrict the max power drawn by the motor (from 1000+watts down to around 7-800w) The 'Battery Current Max' setting does this just fine, I also tried restricting using the 'Phase Current Max' setting but whatever value I put here seems to make no difference to the power draw, even setting it as low as just 1.

Am I misunderstanding the way this operates, or is there maybe some problem here?

 

[stancecoke]

I did a calibration of the wattmeter recently and found that my motor has actually been drawing a max in excess of 1kw.

Sorry, we can't improwe that, as we use the filtered battery current signal and do the current control in the slow loop. For this specific issue the implementation of casainho is better, as he uses the unfiltered battery current signal and reduces the duty cycle in the fast loop if over current is detected...

We would need a high speed logger or an oszilloscope on the shunt to see, how long these peaks are, until the control-loop reduces the duty cycle... But I'm quite sure, those high currents will only appear, if you accelerate the motor from standstill with the throttle...

regards
stancecoke

 

[casainho]

I did a calibration of the wattmeter recently and found that my motor has actually been drawing a max in excess of 1kw.

Sorry, we can't improwe that, as we use the filtered battery current signal and do the current control in the slow loop. For this specific issue the implementation of casainho is better, as he uses the unfiltered battery current signal and reduces the duty cycle in the fast loop if over current is detected...

I think you can use in series my approach with your approach, if it brings value.

Hmmm, wait. I control 2 different currents in fast loop, meaning the control is very fast:
1. motor phase current
2. battery current

The 2. has a low pass filter in hardware so it may be a bit slow but still seems fast enough so we have a good control.

 

[geofft]

I did a calibration of the wattmeter recently and found that my motor has actually been drawing a max in excess of 1kw.

Sorry, we can't improwe that, as we use the filtered battery current signal and do the current control in the slow loop. For this specific issue the implementation of casainho is better, as he uses the unfiltered battery current signal and reduces the duty cycle in the fast loop if over current is detected...

We would need a high speed logger or an oszilloscope on the shunt to see, how long these peaks are, until the control-loop reduces the duty cycle... But I'm quite sure, those high currents will only appear, if you accelerate the motor from standstill with the throttle...

regards
stancecoke

Yes, it's generally full throttle operation that produces these high currents. It's no longer a problem because by reducing the 'Battery Current Max' setting (to 450) full throttle from standstill now only pulls about 700w, which I'm quite happy with...
I guess you're saying that the 'Phase Current Max' setting can't control the short transient peaks in current. If so I'm not quite sure what it is doing and how I arrive at a setting for it... :?

Probably just me being confused (as usual), like I said it's fine now and no longer popping fuses when I do drag racing starts. Even at just 700w, with your fw it throttles from standstill very strongly with no motor stuttering, very nice... 8)

 

[stancecoke]

In the german forum, we are discussing if there is a difference between the 14v/5V supply in a 12FET Block (S12P aka KT48ZWS) and a 12FET Sinusodial (S12S aka KT48SVP). The sinusodial mode should draw more current, as the PWM is active on all FETs all the time.

User Xnyle found his modded (phasecurrent sensor added on a ZWS type) controller has 39 Ohm at R62 while 82 Ohm are documented in the schematic.

@honya96: can you please take a photo of your pcb of a 12/18 FET?

Thank you!
stancecoke

Photo from Xnyle still with missing ACS711:

edit: I found a photo of a S12S in the internet, it has a different board revision, with a ACS756 phase current sensor and a R62 with colour-code violet-black-brown =700 Ohm ?!:

 

[sharkovich]

Here are some photos of 18FET KT60SVP controller board, 60A rated. I also have 45A rated version @ home, but the only difference as far as I know are the shunts.

 

[stancecoke]

Thank you for the photos! So there seem to be two big resistors in parallel on your board. Sadly, I can't identify the colours of the resistor bands. Can you tell us the colours (or directly the resitance )?

regards
stancecoke

 

[KingQueenWong]

I just wanna share the new product "hovershoes".

 

[reset]

You have to press the "Write Option Bytes" Button of the Java Tool once with a brand new controller...

regards
stancecoke

Thanks again for your help on this but I'm struggling a little with the voltage reading on the display the LCD 3 displays battery but with 0 bars, it doesn't flash but but will not respond to PAS or throttle input the PAS assist function no longer flashes on the display when pedalling. I've tried the 18v battery and also a fully charged 36v which works fine on a second controller I haven't flashed. Sorry to pester you but any clues or further help would be very much appreciated. Thanks in advance.

 

[stancecoke]

Thanks again for your help on this but I'm struggling a little with the voltage reading on the display the LCD 3 displays battery but with 0 bars

You have to set the right number of serial cells in C#ROME-B for the correct bar display

but will not respond to PAS or throttle input

you have to set the right value for undervoltage limit

If you have questions, please always post your config.h, otherwise we can't see what you are doing ....

regards
stancecoke

 

[sharkovich]

Thank you for the photos! So there seem to be two big resistors in parallel on your board. Sadly, I can't identify the colours of the resistor bands. Can you tell us the colours (or directly the resitance )?

regards
stancecoke

Sadly, I have a big problem with this as I am colourblind, and too can not tell resistance just from photos. I do not want to desolder those resistors from 60A version of the controller because it's mounted on my ebike, currently in use. The 45A version, which has 5V rail burnt, is at my parents home. I'll be going there next week so I can take them out and check resistance with multimeter.

I have a better photo from 45A version here:

It looks like 200Ohms


Edit: More photos of Kt60SVP 45A Version: https://drive.google.com/open?id=14r5-jd2Jf2q7mdtYHsvjj7AAd-YTGNWq

 

[stancecoke]

Thank you sharkovich! In my eyes, the bands are brown-black-black, means 10 Ohm. If the two resistors are in parallel, we have 5 Ohm in sum.

I've added a control loop status variable to the code. So you can see now, what the controller is doing actually in diagnostics mode. You can find the information in the tutorial also.

0 booting
1 linear regen
2 undervoltage
3 brake/digital regen
4 erps limiting
5 PAS timeout
6 power in torquesensor mode
7 power in throttle mode
8 phase current limiting
9 power in torquesimulation mode
10 throttle override
11 speedlimit cut internal sensor
12 speedlimit ramp down internal sensor
13 speedlimit cut external sensor
14 speedlimit ramp down external sensor

regards
stancecoke

 

[reset]

Thanks again for your help on this but I'm struggling a little with the voltage reading on the display the LCD 3 displays battery but with 0 bars

You have to set the right number of serial cells in C#ROME-B for the correct bar display

but will not respond to PAS or throttle input

you have to set the right value for undervoltage limit

If you have questions, please always post your config.h, otherwise we can't see what you are doing ....

regards
stancecoke

Hi this is the screen shot of the settings I'm using a q100 hub so I used that template as a starting point. I've managed to get the battery displaying the voltage by setting the controller C5 set to 0 so it tracks the incoming voltage. I've taken the throttle out of the equation as I can't seem to get that to work with the other controller(standard in changed). I also have the write config as a text file if that helps. Many Thanks again

 

[reset]

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master>PATH = C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\;C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Users\controller\AppData\Local\Microsoft\WindowsApps;C:\Program Files\SDCC\bin;C:\Program Files\STMicroelectronics\st_toolset\stvp;C:\Program Files (x86)\STMicroelectronics\st_toolset\stvp;C:\SDCC\usr\local\bin;C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\tools\cygwin\bin

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master>del main.hex

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master>sdcc --version
SDCC : mcs51/z80/z180/r2k/r3ka/gbz80/tlcs90/ds390/pic16/pic14/TININative/ds400/hc08/s08/stm8 3.6.0 #9615 (MINGW64)
published under GNU General Public License (GPL)

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master>make -f Makefile_windows clean
Cleaning files...

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master>cd stdperiphlib\src

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src>del *.asm

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src>del *.rel

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src>del *.lk
Could Not Find C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src\*.lk

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src>del *.lst

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src>del *.rst

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src>del *.sym

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src>del *.cdb
Could Not Find C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src\*.cdb

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src>del *.map
Could Not Find C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src\*.map

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src>del *.elf
Could Not Find C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src\*.elf

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src>del *.bin
Could Not Find C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src\*.bin

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib\src>cd..

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\StdPeriphLib>cd..
Could Not Find C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master\*.elf
Done.

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master>make -f Makefile_windows
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -oStdPeriphLib/src/stm8s_itc.c StdPeriphLib/src/stm8s_itc.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -oStdPeriphLib/src/stm8s_clk.c StdPeriphLib/src/stm8s_clk.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -oStdPeriphLib/src/stm8s_iwdg.c StdPeriphLib/src/stm8s_iwdg.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -oStdPeriphLib/src/stm8s_gpio.c StdPeriphLib/src/stm8s_gpio.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -oStdPeriphLib/src/stm8s_exti.c StdPeriphLib/src/stm8s_exti.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -oStdPeriphLib/src/stm8s_uart2.c StdPeriphLib/src/stm8s_uart2.c
Warning: Non-connected liverange found and extended to connected component of the CFG:iTemp4. Please contact sdcc authors with source code to reproduce.
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -oStdPeriphLib/src/stm8s_tim1.c StdPeriphLib/src/stm8s_tim1.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -oStdPeriphLib/src/stm8s_tim2.c StdPeriphLib/src/stm8s_tim2.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -oStdPeriphLib/src/stm8s_adc1.c StdPeriphLib/src/stm8s_adc1.c
Warning: Non-connected liverange found and extended to connected component of the CFG:iTemp0. Please contact sdcc authors with source code to reproduce.
Warning: Non-connected liverange found and extended to connected component of the CFG:iTemp0. Please contact sdcc authors with source code to reproduce.
Warning: Non-connected liverange found and extended to connected component of the CFG:iTemp1. Please contact sdcc authors with source code to reproduce.
Warning: Non-connected liverange found and extended to connected component of the CFG:iTemp0. Please contact sdcc authors with source code to reproduce.
Warning: Non-connected liverange found and extended to connected component of the CFG:iTemp0. Please contact sdcc authors with source code to reproduce.
Warning: Non-connected liverange found and extended to connected component of the CFG:iTemp1. Please contact sdcc authors with source code to reproduce.
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -oStdPeriphLib/src/stm8s_flash.c StdPeriphLib/src/stm8s_flash.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -ogpio.c gpio.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -outils.c utils.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -ocruise_control.c cruise_control.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -ouart.c uart.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -oadc.c adc.c
adc.c:76: warning 85: in function adc_init unreferenced local variable : 'ui16_counter'
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -obrake.c brake.c
brake.c:23: warning 110: conditional flow changed by optimizer: so said EVELYN the modified DOG
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -otimers.c timers.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -opwm.c pwm.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -omotor.c motor.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -oPAS.c PAS.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -oSPEED.c SPEED.c
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -oupdate_setpoint.c update_setpoint.c
update_setpoint.c:253: warning 85: in function update_setpoint unreferenced function argument : 'PAS'
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -odisplay.c display.c
display.c:216: warning 116: right shifting more than size of object changed to zero
sdcc -c -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug -odisplay_kingmeter.c display_kingmeter.c
sdcc -IStdPeriphLib/inc -I. -mstm8 --std-c99 --nolospre --out-fmt-ihx --debug main.c StdPeriphLib/src/stm8s_itc.rel StdPeriphLib/src/stm8s_clk.rel StdPeriphLib/src/stm8s_iwdg.rel StdPeriphLib/src/stm8s_gpio.rel StdPeriphLib/src/stm8s_exti.rel StdPeriphLib/src/stm8s_uart2.rel StdPeriphLib/src/stm8s_tim1.rel StdPeriphLib/src/stm8s_tim2.rel StdPeriphLib/src/stm8s_adc1.rel StdPeriphLib/src/stm8s_flash.rel gpio.rel utils.rel cruise_control.rel uart.rel adc.rel brake.rel timers.rel pwm.rel motor.rel PAS.rel SPEED.rel update_setpoint.rel display.rel display_kingmeter.rel

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master>ren main.ihx main.hex

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master>STVP_CmdLine -BoardName=ST-LINK -ProgMode=SWIM -Port=USB -Device=STM8S105x6 -FileProg=main.hex -verbose -no_loop
STVP_CmdLine version 1.6

Verbose ON
Log activity ON
Display Progress OFF
Message box warning if protect option byte ON
Loop mode OFF
Erase device OFF
Blank check device OFF
Verify device ON

Configuration:
BoardName=ST-LINK ST-LINK_ID=0 Device=STM8S105x6 Port=USB ProgMode=SWIM

>>> Filling PROGRAM MEMORY image in computer with Blank Value
<<< Filling PROGRAM MEMORY image in computer succeeds

>>> Loading file main.hex in PROGRAM MEMORY image in computer
<<< Loading file succeeds

Hit 'Esc' key to abort during communication.

>>> Programming PROGRAM MEMORY
<<< Programming PROGRAM MEMORY succeeds

>>> Verifying PROGRAM MEMORY
<<< Verifying PROGRAM MEMORY succeeds

C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master>pause
Press any key to continue . . .

 

[stancecoke]

Hi this is the screen shot of the settings I'm using a q100 hub so I used that template as a starting point.

Have you read the description of the GUI?

1. Disable Input Diagnostics
2. Disable Motor Diagnostics
3. Select Ride Mode --> Throttle for first tests.

regards
stancecoke

 

[geofft]

Hi this is the screen shot of the settings I'm using a q100 hub so I used that template as a starting point. I've managed to get the battery displaying the voltage by setting the controller C5 set to 0 so it tracks the incoming voltage. I've taken the throttle out of the equation as I can't seem to get that to work with the other controller(standard in changed). I also have the write config as a text file if that helps. Many Thanks again

Probably also worth mentioning that 5S is a very low voltage to be operating these controllers, the LM317 that provides it's internal supplies really needs a minimum of 18v (under load..) at it's i/p pin to operate reliably. Bear in mind it's being fed via a dropper resistor, so you may need 21-22v at least fed to the controller for it to work.

Probably worth doing some voltage checks to make sure all is well here... :wink:

 

[nieles]

snip.......
C:\Users\controller\Downloads\BMSBattery_S_controllers_firmware-Master\BMSBattery_S_controllers_firmware-Master>sdcc --version
SDCC : mcs51/z80/z180/r2k/r3ka/gbz80/tlcs90/ds390/pic16/pic14/TININative/ds400/hc08/s08/stm8 3.6.0 #9615 (MINGW64)
published under GNU General Public License (GPL)
........snip

you need to upgrade to SDCC 3.7.x

 

[reset]

Thanks for the input folks. I was hoping to use this controller with an 5s battery so it sounds like its not going to be possible. I had looked at the vesc controller but can't seem to find a simple way to provide PAS to this type of controller. I have a no electrical engineering experience so this whole thing is very new to me and a little confusing.

After seeing this thread I thought it would be a perfect solution to achieve low voltage usage along with PAS. I may have to revisit the vesc based controller.

I really appreciate everyone's efforts in replying and taking the time to educate me on this. Thanks again.

 

[geofft]

I was hoping to use this controller with an 5s battery so it sounds like its not going to be possible.

...you could probably use 5s if you removed (and shorted) the dropper resistor.

Easy to do, must be worth a try. Then follow the other advice given and you should be good to go..

 

[stancecoke]

Thanks for the input folks. I was hoping to use this controller with an 5s battery so it sounds like its not going to be possible.

Don't give up that fast! As I wrote before, you have to change the resistor R62 or just short it. (5p minimum voltage: 5*3,3V = 16,5V, fully charged 5*4,2 = 21V)

Edit: geofft was faster

It should work then.

One open issue: It's important to have the bootstrap circuit for the high side FETs working. I don't know the boundary conditions for this...

regards
stancecoke

 

[stancecoke]

I was hoping to use this controller with an 5s battery

I just checked it on my testbench: the 48V! motor runs until a voltage of 15.5V with the origin R62 resistor. If I power the processor with the 5V supply from the STLink, it even runs down to 7.5V!

So no problem for our firmware :wink:

regards
stancecoke

 

[reset]

I was hoping to use this controller with an 5s battery

I just checked it on my testbench: the 48V! motor runs until a voltage of 15.5V with the origin R62 resistor. If I power the processor with the 5V supply from the STLink, it even runs down to 7.5V!

So no problem for our firmware :wink:

regards
stancecoke

That's good news. I've not managed to get the motor working with the PAS or throttle. I've also tried this with a new controller s06s has any one used this controller or are people using the 63, i'm not sure what i'm doing wrong. I wish I could figure it out. I've also reverted back to 10s battery and that doesn't work either. I've tried with and without display.