Recent content by shaddi

Does anybody have infos about the similar display "DM03"? It's labeled with "VeloFox DM03"....

Just wanted to leave some infos about using a Shimano Alfine 11 hub gear with the Motor. To make it short: Don't do it! The stress on the mechnanics are just too high. I damaged mine almost completly. Only some gears are usable, the rest is "jumping through with loud noises" :( :oops:

Hi, does anybody know a source for the battery-case used in the Frey EX bike? bye, Karl

sorry, don't want to be offensive, but please can you stop cross-posting? You always complain about guys posting off-topic into your thread but you cross-post every achievement in ALL tsdz2 related threads...

does anybody in germany/europe has spare PCBs for sale?

There is also a pull request open with another solution. https://github.com/OpenSource-EBike-firmware/TSDZ2-Smart-EBike/pull/128

Why not just use the Mosfet in your BMS? Most of them have an option for a button to disable the output. On my chinese bluetooth BMS i can disable the output by BLE, too...

got my sw102 working today :D is the current version compatible with the latest 0.20 alpha versions of the motor?

Sorry, i think casainho is already mad at me, that was not my intention :-( My scope of the whole project is to get a motor that outperforms many other commercial systems out there. And i think all the developers involved till now have already made that possible. I love how my bike performs...

i don't understand why you are insisting in cutting a valuable feature off the code. How many space can be saved if we cut away all the eeprom functions? At the current state they make no sense, right. But this can be corrected with litte effort and we gain one more safety feature for "breaking...

every other system is doing it like this. So if its up to me, yes, please :) sorry, but i only partly agree with that. You always mention safety-reasons or when some of the components break in the field. What if your display, the cable or the connector between them breaks in the field? You than...

hm, i still don't get it. The code is already there, why is there a need for another project or somebody to maintain this special scenario? If i get it right, the eeprom is filled with some default variables if the first byte is not "our key". And these variables are loaded at every bootup. As...

I don't think so. There are some config-variables that are always the same and you don't need to change them often. Wheel perimeter, motor current limits ect. I think the motor should be runnable without a display after setting these parameters up once.

Is there still no way of flashing the device without opening it?

fully agree! My dream is to get the SW102, so i have a small display for the daily usage and an APP (mobile or notebook) for configurations via BLE. I also thought about an ESP32 Controller, with a small OLED Display. So we can have BLE and WiFi together. First E-Bike with an own WebInterface...