
Does anyone know what the 3 unmarked connectors on the left could be for (2 of them are connected in the picture)?

Are you still talking about your homebrewed controller?
Hi what is plugged in is the cruise feature, I pulled it apart I don't use it. The other is lamp lighting
You'll find the Sempu tqsr's are fairly power hungry devices. I originally tried powering mine by tapping the 15v internal controller supply, this kinda worked but was giving random shutdowns and mosfet failures, usually when applying heavy pressure to the pedals.Does anyone know if it's advisable to power my DCDC (used to power my Sempu torque sensor 12v and my BT module 5v) from the blue cable of the LCD display?
First, welcome to the project
stancecoke wrote: ↑Apr 14 2020 9:57amFirst, welcome to the project! Please do not test the standstill resistance with the motor on the desk (and a Lab supply, that doesn't allow negative currents). The power control needs to "see" a significant delta current to control the current to zero.
You will recognize the effect, if you push your bike with a direct drive. You will feel a small resistance at the start, then the control loop stars working and the resistance disappears.
regards
stancecoke.
if this resistor same as on KingQween scheme 3k i think you can to unsolder (i use without this resistor)R58 heats up a lot more than usual. It's normal?
We never switch off the PWM, therefore the controller heats up a little more with the motor in standstill.
I hadn't tried pwm off because on the wiki it says "not implemented"..stancecoke wrote: ↑Apr 15 2020 12:49amWe never switch off the PWM, therefore the controller heats up a little more with the motor in standstill.
You can try the experimental setting "PWM off @ coast" but you have to adjust a motor specific parameter (flt_s_motor_constant) to avoid current peaks with a direct drive.
regards
stancecoke
Code: Select all
black – GND
yellow – SWIM
blue – Reset
red – maybe VCC, you don't need it
Code: Select all
./stm8flash -c stlinkv2 -p stm8s105s4t6c -s flash -r KZQW22A-flash.bin
./stm8flash -c stlinkv2 -p stm8s105s4t6c -s eeprom -r KZQW22A-eeprom.bin
./stm8flash -c stlinkv2 -p stm8s105s4t6c -s opt -r KZQW22A-opt.bin
Code: Select all
./stm8flash -c stlinkv2 -p stm8s105s4t6c -s flash -w KZQW22A-flash-hacked-double-speed-limit.bin
congratulationsAlexDaniel wrote: ↑Apr 15 2020 1:57pmwe managed to reverse-engineer the firmware and remove the speed limit
Yes, the speed limit itself has nothing to do with EEPROM. It simply checks some variable (which we think represents speed) against a hardcoded value, and if it's larger it reduces the PWM duty cycle to either zero or some very low value (I don't remember now). We did look at the processing of EEPROM data for a bit, but we didn't get much further than the discussion earlier in this thread (or somewhere on this forum). Our goal was just to remove the speed limit, so we didn't see the need to investigate more into EEPROM processing.stancecoke wrote: ↑Apr 16 2020 1:20amcongratulationsAlexDaniel wrote: ↑Apr 15 2020 1:57pmwe managed to reverse-engineer the firmware and remove the speed limit
So the speedlimit is really hardcoded and not an editable parameter in the EEPROM?!
regards
stancecoke
Nice to see the motor spinning, this is a great sucess already! Congratulations!
Code: Select all
ui16_current_cal_b -= 1;