Recent content by Demion

Mine was unbalanced more, if I remember right ( but only one row, something like 1 - 4.21, 2 - 3.8, rest - 4.19). Maybe leaving on 36V charger for a long time (even after charger led shows fully charged and turns off fans) BMS might be able balance it. When it cuts off can you replug and turn...

I have same problem with battery. One cell row (series) was always ~0.5V lower. So it hit LVC (<3.0V) faster then other series and BMS cut off whole battery. I was only getting half of capacity. I left on charger for few days, but it was balancing too slowly, almost no effect at all. Then I...

In limited way (assist level, battery level, speed, error code) can be ported to any display if protocol is known. Maybe new lcd4 has same protocol as lcd3. VLCD protocol - https://github.com/hurzhurz/tsdz2/blob/master/serial-communication.md KT-LCD protocol -...

What can I say. Windows users like "user friendly" GUI apps with buttons and are scared off by batch files and text file manual edits. Anyway it is not even in question to make or not configurator app, cause it is just few days of work. One day to code, one day to test. I agree documentation is...

I looked through OSEC.java code. It seems pretty simple to use. I edited few JLabel in Notepad++. It also compiles well without Netbeans using makeJar.bat. I think adding your repository as git submodule to TSDZ2 fork just for JavaConfigurator tool not best idea. I hope adding links in app to...

It is not only basically modifying single file ebike_app.c but actually just changing few functions. 1. add init_default_config() to set default configs that are not configurable with VLCD; 2. change uart_receive_package() & uart_send_package() to support VLCD protocol; 3. config.h just...

Hi. I made fork a while ago too. There was no much interest in it, but famichiki tested it, and contacted me in PM recently. If someone interested, I will quote here more information about it. Btw I plan working on esp8266 module for TSDZ2 to control ebike from phone with bluetooth next...

Sounds perfect to me. I was not even paying attention EEPROM is not being actually used right now. That exact way, you described (using only runtime variables), it should not take too much programming memory, I believe, and should be satisfactory for everyone. Only thing will not be possible is...

Agreed. That what I meant by update. After giving it second thought I also see no much sense saving data to EEPROM or even partial "persistent" data, cause anyway almost all configs need to be saved to run it without display, for example. And I dont see other real use for saving data on...

Is initializing all m_configuration_variables from default defines on start is bad approach? Would it take much programming memory? This way it will work without display if need, display will overwrite everything on uart_receive_package if used and will not mess with EEPROM. Update : on second...

Is this BBS02 or BBSHD chainring? How big is offset in mm? BBS is 9mm and HD is 18.3mm, according to Lekkie website. Thanks.

I noticed ADC torque sensor calibration min value fluctuates +-5 each start. Is there downside to increase sample count twice, for example, to 32? As I understand each reading is only 10ms.

I also start using startup without pedal rotation. Never had problems with safety with bike "running away", only pedals are twitching a bit when resting feet on pedal on traffic lights stop. Startup with only pedal rotation is pretty slow, especially on v0.19.0. I vote not to remove this...

Bug is wrong data buffer size check from LCD to controller at ebike_app.c:2256 (vM0.19.B) mentioned on jobike forum, I believe. Should not lead to problems most likely, because there is start package byte and checksum check, but by coincidence may lead to any undefined behavior. Update...

I ordered them from bike-discount or bike24 a while ago. I am from EU, shipping from Germany.