Recent content by feketehegyi

https://youtu.be/ZiQx_vNi8gk ZiQx_vNi8gk

I've tried lots things with this motor. eg. to go without display using the factory default fw. Actually you need to figure out how to enable the controller. This is actually to short two pins in the display cable. I did it eg. with a jumper like thing to put into the display cable connector.

Well, as it was mentioned - that particular emmebrusa fw version has caused it. Factory default fw can work without display.

https://youtu.be/Dt69s2WG3FE Dt69s2WG3FE

https://www.youtube.com/watch?v=DTY2fdKR5pA DTY2fdKR5pA

Something else to this rabbit hole. :-) https://youtu.be/eenWqxvFcOY eenWqxvFcOY

https://youtu.be/PmyWKQwfy8M PmyWKQwfy8M

https://youtu.be/wZvILXhLNTk wZvILXhLNTk

First you need to create a cable where in case of my Android app you'll need to connect a classic bt module (eg. HC-05). Then you'll need the well known programing cable too to upload my patched factory default firmware. Then you can use the Android app. There're lot's of features. You can check...

I've attached a BT05 (HM-10) ble module to the display cable and then through this connection can communicate with the watch. I've patched the factory default firmware. One of the new features is that it can receive a value which starts the motor on a given rpm.

I have two bluetooth solutions for the TSDZ2. This watchOS uses ble and my Android app uses classic bt. With this latter I've already done many miles and it remembers the last settings of course. This watchOS app is a prototype now. My initial test results show that ble does not work in the...

fyi byROzyWJNaY

fyi wdB4-cjvcZE

Hi Casainho, I've really enjoyed your summary again. 58km/h is really high. And yes, when I try to keep up with hard cyclist I need to go really above 40km/h. Actually they can beat me on flat surface without wind. But if it goes upwards or there's wind I can keep with them with my TSDZ2. :-)

It works also without the phone. You know factory default firmware has basic settings which becomes active if there's no display connected. So, this happens to when it loses communication falls just back to state when there's no display. I've actually changed some of these default values too...