Nothing so sinister - simply down to me lurking on the German pedelec forum and relying on google translate.
'High Seat Cola' (google translation...


Nothing so sinister - simply down to me lurking on the German pedelec forum and relying on google translate.
The first post of this thread implies via picture and title that there at least used to be up to probably at least 24FET versions, though they may not be available anymore.
Code: Select all
// calculate CRC xor
ui8_crc = 0;
for (ui8_j = 1; ui8_j <= 11; ui8_j++) {
ui8_crc ^= ui8_tx_buffer[ui8_j];
Code: Select all
void display_update() {
// fill local buffer from uart ringbuffer
uart_fill_rx_packet_buffer(ui8_rx_buffer, 14, &ui8_UARTCounter);
// Check for reception of complete message
if ((ui8_UARTCounter > 13) || (ui8_rx_buffer[ui8_UARTCounter - 1] == 0x0E)) {
ui8_UARTCounter = 0;
// validation of the package data
ui8_crc = 0;
for (ui8_j = 1; ui8_j <= 13; ui8_j++) {
if (ui8_j == 5) continue; // don't xor B5
ui8_crc ^= ui8_rx_buffer[ui8_j];
}
if (ui8_crc==ui8_rx_buffer [5]) // see if CRC is ok
{
// Light On/Off
lcd_configuration_variables.ui8_light_On = ui8_rx_buffer [1] & 128;
// Walk mode
if ((ui8_rx_buffer[1] & 7)==6) {lcd_configuration_variables.ui8_ReverseDriveModus_On = 1;}
else {lcd_configuration_variables.ui8_ReverseDriveModus_On = 0;}
//Assist level
lcd_configuration_variables.ui8_assist_level = ui8_rx_buffer [1] & 7;
lcd_configuration_variables.ui8_max_speed = 10 + ((ui8_rx_buffer [2] & 248) >> 3) | (ui8_rx_buffer [4] & 32);
lcd_configuration_variables.ui8_wheel_size = ((ui8_rx_buffer [4] & 192) >> 6) | ((ui8_rx_buffer [2] & 7) << 2);
lcd_configuration_variables.ui8_p1 = ui8_rx_buffer[3];
lcd_configuration_variables.ui8_p2 = ui8_rx_buffer[4] & 0x07;
lcd_configuration_variables.ui8_p3 = ui8_rx_buffer[4] & 0x08;
lcd_configuration_variables.ui8_p4 = ui8_rx_buffer[4] & 0x10;
lcd_configuration_variables.ui8_p5 = ui8_rx_buffer[0];
lcd_configuration_variables.ui8_c1 = (ui8_rx_buffer[6] & 0x38) >> 3;
lcd_configuration_variables.ui8_c2 = (ui8_rx_buffer[6] & 0x37);
lcd_configuration_variables.ui8_c4 = (ui8_rx_buffer[8] & 0xE0) >> 5;
lcd_configuration_variables.ui8_c5 = (ui8_rx_buffer[7] & 0x0F);
lcd_configuration_variables.ui8_c12 = (ui8_rx_buffer[9] & 0x0F);
lcd_configuration_variables.ui8_c13 = (ui8_rx_buffer[10] & 0x1C) >> 2;
lcd_configuration_variables.ui8_c14 = (ui8_rx_buffer[7] & 0x60) >> 5;
digestLcdValues();
send_message();
}
}
}
Last I checked there was no problem to find 18fet controllers, but I have not seen the 24fet versions. It is probably about a year ago, maybe it has changed? They were sold under different names, hallomotor, consinmotor (?) etc. Zoom in on the pictures on ebay and try to work out the specifications.amberwolf wrote: ↑Oct 26 2019 1:06amThe first post of this thread implies via picture and title that there at least used to be up to probably at least 24FET versions, though they may not be available anymore.
I've not spent much time at it, but I have had a hard time even finding *any* controllers that I can be *certain* are KT and that have the full current sensors, etc., much less in an 18FET version (which is what I really wanted to find to try this out on my trike).
On TSDZ2 firmware, everyone prefer SOC Coulomb counting as it works very well, even for different battery chemistry. User just need to setup the amount the Watts Hour rate of the battery, that can be previously measured by full discharging the battery once, while riding. On commercial MTB ebikes is standard to use the Watts Hour rate of the battery as the main tecnhical characteristic, being 500 as currently average good value. But a 200 Wh is also good for commuting on the city and be a small and light battery.geofft wrote: ↑Nov 06 2019 9:00amI'm currently using Xnyle's 'X4 throttle' branch which, as previously reported, works extremely well for me. There's just one small issue that's bugging me though - the calibration of the battery bars. (12s lipo, LCD3 display)
It was always possible with previous versions to calibrate the battery bars using the 'Voltage Calibration' setting in the cofigurator, but changing this setting now seems to have no effect on the battery bars. I'm fairly sure this is the same with the Master branch too.
Is there now some other way to adjust the battery bars, or am I misunderstanding things here?![]()
thank you very much. i have problem and maybe someone know how to solve it. i damaged two kt controllers, one 48v 22A and one 48v 45A 18fet. i build battery pack 15s, with max voltage of 61.5v. Since i use this pack with cheap no name china controller and work great, but i want switch to sine wave, and i upgraded motor. so i have 15s with max 61.5V, caps inside both controller are 63v. first controller worked for 30km, i connect it to battery when i have about 57v, then i charge baterry and after full charge (61,5V) controller is damaged, so i think it happends, and i buy new one with more fet (18fet) and do the same, i make about 50km with about 60-61V, everything was ok till i charge battery to 61.5V RIght now i have two controllers both damaged the same. it power up, communicate with lcd, everything seems working, but when you press throttle nothing happend, is show no error, but whell dont spin. But when you lift wheel and turn it backward, and it still turning slowly back and then press throttle everything work, it speeds up to max speed, when i press brake and give dummy load, it take 30A i can add and back throttle and its slows and speed , but if they motor slows too much, again i cant do nothing. when i stop and turn wheel again backwards and press throttle again it works. btw battery is still 61V.for sure motor is 100% works since i connect no name controller and it works flawless. what can be damaged ? iits looks like it dont wanna start, like missing one phase, or maybe controller dont see hall? but when i disconnect cable i get error about sensor position fault.
I've no experience with running KT controllers at elevated voltages but I'm guessing that the higher voltages you are using are eventually killing the mosfets. I would suggest you reduce your battery to 14s, or maybe look for some 'better' (higher voltage rating) mosfets if you want to continue with 15s. That's just guesswork though, like I said, I'm no expertflorkk wrote: ↑Nov 07 2019 6:25pmthank you very much. i have problem and maybe someone know how to solve it.
In case you still need a bigger controller, i found some 18 MOSFET versionsamberwolf wrote: ↑Oct 26 2019 1:06amThe first post of this thread implies via picture and title that there at least used to be up to probably at least 24FET versions, though they may not be available anymore.
I've not spent much time at it, but I have had a hard time even finding *any* controllers that I can be *certain* are KT and that have the full current sensors, etc., much less in an 18FET version (which is what I really wanted to find to try this out on my trike).
Is the resonance an issue on both square wave and sine wave versions (could I remove the phase b current sensor to solve the fork judder)?stancecoke wrote: ↑May 16 2019 2:13amOK, but it can't be a software problem. I have a buck converter for supplying the head- and rearlights on my bike. Even if the battery is not installed at all and the controller is switched off, the resonaces appear when the lights are switched on. The direct drive motor is working as a generator via the body diodes of the mosfets in this case. So it can't be a matter of PWM or commutation.
This leaves only a hardware problem as the cause of the resonances.
Capacity and inductivity may be in an unfavourable relation.
regards
stancecoke
The current sensor has no influence on the resonance issue...
The phase current limit is only needed during the very first milliseconds at startup (or at blocked wheel), so I think there is no high potential to optimize the performance.
Is there a list of motors that works well with the kt controller, without any resonance?kkm wrote: ↑May 15 2019 3:20pmNo, this is not a "mechanical" problem, it is absolutely exactly a software problem. Or, perhaps, hardware problems (signal filtering, interference) of the KT controllers themselves.stancecoke wrote: ↑May 15 2019 6:21am
It's a mecanical problem, you can try to increase/decrease the tension of the spokes, but that might just shift the resonance range...
I tested the original KT firmware (sine and square version) on 7 different gear (rear) motors - Bafang, Mxus, and Shengyi. They all had the same problem - the resonances and vibrations of the bike frame and equipment of the bike at a speed of 5-8 km / h, and at a speed of 11-13 km / h. Exactly the same problem with open source firmware. Which is a bit strange.
BTW - Mxus XF15R has good mechanics and an absolute lack of even the slightest vibrations and resonances on a cheap "trapezoid" chinese DMHC controller (I quoted the link above). My other motors also work smoothly without vibration. All this is easy to check - just take another (not KT) controller and check the operation of the motors. Vibration will not be
All this is very sad.
P.S. My KT controllers s have 25 kOhm resistors, instead of "standard" 2.2-2.5 kOhm between + 5V and the signal output of the hall sensors(open collectors). Perhaps - the problem is this, the signals are too "dirty" - the pulses from the motor windings can distort the signals from the hall sensors....
Just set the under-/ overvoltage limits in the java tool according to your needs, see the wiki:
regardsUndervoltage: Undervoltage cutoff value. Calculation: Value in volts times (256/Battery Voltage Calibration). example: 34.3V * (256/70) = 125
Overvoltage: Overvoltage cutoff value during Regeneration. Calculation: Value in volts times (256/Battery Voltage Calibration). example: 54.0V * (256/70) = 203