TSDZ2 mid drive with 860C, 850C or SW102 displays only -- Flexible OpenSource firmware (Casainho code only)

tomtom50 said:

A lot of people, including me, found upgrading to open source firmware difficult, because the information is spread out over two threads with over 200 pages between them. I also needed the excellent github information and jbalat's videos, and those resources weren't immediately clear to me as I went through the ES threads.

Here is my attempt at a comprehensive tutorial for installing Open-Source firmware with KT-LCD3 and also flashing stock firmware. It doesn't cover everything. I haven't tried marcoq's method of installing OSF with the VLCD5. I didn't cover installing a temperature sensor. The waterproof connectorized cable is for an 8-pin system, etc.

I think it is pretty complete and good for someone new who has never before dealt with connecting to embedded processors. I wrote it before I became so comfortable with the process that I would glide over things that would not be obvious to newcomers.

Revise & re-post as you like. I hope it works for others.
Open Source and Stock Firmware Tutorial.doc

Click to expand...

Great job! I think and hope this will help many!

Have you thought of adding your tutorial officially on GitHub? I think it would be a great tool. You have clearly put down a great deal of effort into it. If you add it on GitHub, do not forget to credit yourself.

Otherwise, I would not mind adding it myself. Would of course credit you for the work. I am a bit time constrained at the moment though.

I just want it to be readily available for everyone!

Hello buba. I have a question. In which field can I see how much total energy was spent by the motor on my trip? I understand this data is recorded in the data energy field? Or in the battery field? I have already driven about 400 km on this motor with a new firmware, and I really like it! great job casainho and buba! But I have wishes. After the trip, I would like to know how many total watts of my physical energy (leg energy) was spent. And compare with the total expended energy of the motor. So I could compare how much I contributed to each of the trips. (For example: total physical energy: 2300 watts; motor energy: 3500 watts)

Hello Kisazul, thanks for the feedback!

Kisazul said:

In which field can I see how much total energy was spent by the motor on my trip? I understand this data is recorded in the data energy field? Or in the battery field?

Click to expand...

It is not possible to see watt-hours consumed since you started your trip. You can only see watt-hours consumed since you fully charged your battery. It is maybe possible to add another sub field that displays how many watt-hours you have consumed since system is powered on. Is that something desirable? Watt-hours consumed during a trip and watt-hours consumed since power on are different but in some cases the same.

Kisazul said:

After the trip, I would like to know how many total watts of my physical energy (leg energy) was spent. And compare with the total expended energy of the motor. So I could compare how much I contributed to each of the trips.
...
(For example: total physical energy: 230 watt-hours; motor energy: 350 watt-hours)

Click to expand...

That is a suggestion for a new function and there is a constraint regarding program space in the KT-LCD3. So not sure if possible to add this. Can not promise anything. But for now: the total motor energy consumed is a factor of human energy consumed. So if you know how many battery watt-hours you have consumed you can calculate the human energy consumed. Not ideal but an approximation. This only works if you use the same assist level or keep track of the assist multipliers.

buba said:

Hello Kisazul, thanks for the feedback!

Kisazul said:

In which field can I see how much total energy was spent by the motor on my trip? I understand this data is recorded in the data energy field? Or in the battery field?

Click to expand...

It is not possible to see watt-hours consumed since you started your trip. You can only see watt-hours consumed since you fully charged your battery. It is maybe possible to add another sub field that displays how many watt-hours you have consumed since system is powered on. Is that something desirable? Watt-hours consumed during a trip and watt-hours consumed since power on are different but in some cases the same.

Kisazul said:

After the trip, I would like to know how many total watts of my physical energy (leg energy) was spent. And compare with the total expended energy of the motor. So I could compare how much I contributed to each of the trips.
...
(For example: total physical energy: 230 watt-hours; motor energy: 350 watt-hours)

Click to expand...

That is a suggestion for a new function and there is a constraint regarding program space in the KT-LCD3. So not sure if possible to add this. Can not promise anything. But for now: the total motor energy consumed is a factor of human energy consumed. So if you know how many battery watt-hours you have consumed you can calculate the human energy consumed. Not ideal but an approximation. This only works if you use the same assist level or keep track of the assist multipliers.

Click to expand...

I think you could close the KT-LCD3 and focus on color LCD, because it has much more memory so will be possible to add much more features with the advantage that will be easier for user to understand all that fields, since we can custom label each field.

This is just an idea because I think using to much of your time for optimizations of space may be without much interest for you. Also we should try to have something simple and easy to understand, not something complex to understand that users will avoid to use because of that.

buba said:

Quick update:
----------------------------------------------

Here are some of the changes:
----------------------------------------------
* Added a new sub field in the odometer field temporarily called Energy where user will see energy consumption and estimated range

* Added a function that measures and calculates consumed watt-hours per traveled distance since power on

* Added function that estimates range since power on depending on how much capacity is left

* More accurate watt-hour measurement

* More accurate time measurement

* Safer Walk Assist and Cruise

* Added option to enable or disable motor power limit quick-set-menu

* Added option to set motor power limit in the configuration menu

* Merged previous configuration menu LCD Setup with configuration menu General Setup for better and faster setup. This also optimizes program size

* Added option that enables user to enable or disable display of motor temperature in the odometer field

* Changed order in the Main Screen Setup menu in the configuration menu

* Changed order in the odometer field

* Added two new Main Screen Setup items

* Heavily optimized code size and speed

* Cleaned up code and comments

* Created wiki that has been updated with all the changes:
https://github.com/OpenSource-EBike-firmware/TSDZ2_wiki/wiki/0.19.0-(BETA)

Click to expand...

That's A LOT. Thanks, glad you managed to implement the distance left estimation too.
Let me read the updated wiki, will be hard to remember all the settings
Is it still suggested to reset to default values from the menu coming from a .18 beta?

Okay, anyone want to test out the 0.19.0 beta 1? :wink:

Here is a link to the hex file for the KT-LCD3:
https://drive.google.com/open?id=1kgcgkNtmCiIDREVW_bBf5ekDKftLnotw

Here is a link to the wiki:
https://github.com/OpenSource-EBike-firmware/TSDZ2_wiki/wiki/Features-and-configurations-for-version-0.19.X-(BETA)

Here are some changes:

* Added a new sub field in the odometer field temporarily called Energy where user will see energy consumption and estimated range

* Added a function that measures and calculates consumed watt-hours per traveled distance since power on

* Added a function that estimates range since power on depending on how much capacity is left

* More accurate watt-hour measurement, do not forget to update the capacity of your battery

* More accurate time measurement

* Safer Walk Assist and Cruise

* Added option to enable or disable motor power limit quick-set-menu in the main screen

* Added option to set motor power limit in the configuration menu

* Merged previous configuration menu LCD Setup with configuration menu General Setup for better and faster setup. This also optimizes program size, see the wiki for more information

* Added option that enables user to enable or disable display of motor temperature in the odometer field

* Changed order in the Main Screen Setup menu in the configuration menu

* Changed order in the odometer field

* Added two new Main Screen Setup items

* Heavily optimized code size and speed, also cleaned up code and comments

casainho said:

I think you could close the KT-LCD3 and focus on color LCD, because it has much more memory so will be possible to add much more features with the advantage that will be easier for user to understand all that fields, since we can custom label each field.

This is just an idea because I think using to much of your time for optimizations of space may be without much interest for you. Also we should try to have something simple and easy to understand, not something complex to understand that users will avoid to use because of that.

Click to expand...

I agree that it gets rather complex to have too many functions and options available on the KT-LCD3. I think the display will be completed in one way or another rather soon. But am really close to finish it.

I think the color LCD is a good choice for the more advanced functions and features. There are more possibilities to display data in an intuitive way. It has more room to implement new functions and features. It is also shipped with the TSDZ2 by some suppliers and therefore there is no need to make your own cables. Overall a good choice albeit more expensive.

But for now I would like to completely finish the KT-LCD3 and solve all issues/bugs, both on the display and the controller.

thineight said:

That's A LOT. Thanks, glad you managed to implement the distance left estimation too.
Let me read the updated wiki, will be hard to remember all the settings
Is it still suggested to reset to default values from the menu coming from a .18 beta?

Click to expand...

Thank you! Please try it out and let me know what you think!

You do not need to reset to default settings. Everything should work as expected. Just set the new functions/features to preferred settings and you are all set

buba said:

Thank you! Please try it out and let me know what you think!

You do not need to reset to default settings. Everything should work as expected. Just set the new functions/features to preferred settings and you are all set

Click to expand...

Good to know I can avoid to reset as setting the wheel circumference was a quite long task...

I've read the new wiki and I understand the distance left is based on the consumed Wh since last charge Vs Wh left, and the "actual consumption" is not used.
Please correct me if I'm wrong, but in this case if I consumed half battery in assistance 1 (say 50km done) and then I switch to assistance 4 (or if I start to climb a hill) the system tells me I've 50km left? This is obviously wrong because if I require more power I would run much less than 50km, right?

Some pages ago I was suggesting to adopt a sort of moving average of the actual consumption, this would update the distance left as soon as I demand more or less energy to the motor.
Maybe also a coefficient (e.g. 1.10 or 0.85) may be user defined to tune the calculated result if the real duration is
eventually greater or less than the calculated one.

Please Buba shed some light on how the function actually works.
Cheers!

thineight said:

I've read the new wiki and I understand the distance left is based on the consumed Wh since last charge Vs Wh left, and the "actual consumption" is not used.
Please correct me if I'm wrong, but in this case if I consumed half battery in assistance 1 (say 50km done) and then I switch to assistance 4 (or if I start to climb a hill) the system tells me I've 50km left? This is obviously wrong because if I require more power I would run much less than 50km, right?

Some pages ago I was suggesting to adopt a sort of moving average of the actual consumption, this would update the distance left as soon as I demand more or less energy to the motor.
Maybe also a coefficient (e.g. 1.10 or 0.85) may be user defined to tune the calculated result if the real duration is
eventually greater or less than the calculated one.

Please Buba shed some light on how the function actually works.
Cheers!

Click to expand...

You are correct. The function uses the remaining capacity, consumed energy and traveled distance since power on and estimates a range depending on those variables. Why implement the estimated range like this?

1. It will, in some cases, be a good average when traveling in terrain with a lot of hills as it will average out the uphill consumption with the downhill consumption, thus giving a better estimation of range than a moving average.

2. It has by far the lowest impact on program space than any other type of implementation as we are reusing variables that already exist.

But, this is hopefully only one out of many functions that will be developed. Suggestions for future updates in the coming 0.19.0 betas:

- Consumption depending on a moving average
- Estimated range depending on a moving average
- Consumption since last user reset
- Estimated range since last user reset
- Consumption since last full charge
- Estimated range since last full charge

0.19.0 is not fully developed or finished yet. I released this beta so I can get all the great user feedback!

buba said:

You are correct. The function uses the remaining capacity, consumed energy and traveled distance since power on and estimates a range depending on those variables. Why implement the estimated range like this?

1. It will, in some cases, be a good average when traveling in terrain with a lot of hills as it will average out the uphill consumption with the downhill consumption, thus giving a better estimation of range than a moving average.

2. It has by far the lowest impact on program space than any other type of implementation as we are reusing variables that already exist.

But, this is hopefully only one out of many functions that will be developed. Suggestions for future updates in the coming 0.19.0 betas:

- Consumption depending on a moving average
- Estimated range depending on a moving average
- Consumption since last user reset
- Estimated range since last user reset
- Consumption since last full charge
- Estimated range since last full charge

0.19.0 is not fully developed or finished yet. I released this beta so I can get all the great user feedback!

Click to expand...

I well understand that now the key point is the low memory left, which is unfortunately a fact.
I'm sure that you gurus will understand if any further implementation is possible or not, in the meantime I try to figure out if the distance left as it is now gives an added value to me.. not sure (never seen it in other systems).
Unfortunately I'm not a programmer therefore I cannot help more than some pseudo-code

I think that unfortunately the usefulness of a function depends a lot on the type of bike, from the routes and not least from the weight of the cyclist :-( (I weigh over 108kg with backpack)
Unfortunately I live in one of the worst places .... I live on top of a hill of 300 meters and my routes consist in going down and up again from the hills, out of the way. The return is obviously on top of the hill when the battery is almost empty. It is essential for me to return with a minimum battery charge if I want to avoid heart attack
In this scenario I think the only reliable charge indicator is my brain associated with the total wh consumed and the residual voltage of the battery. Any possible forecast of the remaining kilometers would be totally unreliable.
It's also a lot of fun trying to get the most out of the kilometers by estimating the battery charge, keeping your brain active
The situation is very different if you use the bicycle on a paved road and on the plain.
I think it would be useful to make 2 versions, for road bikes and mtb. The mtb version should be adapted to the smallest possible display, where the essential data are only the speed and the kilometers traveled, the watt consumed and the residual voltage of the battery. Other functions, navigation, elevation gain, etc. can be assigned to a modern smartphone.
If the transition was simple also lcd05 would be better than lcd03 on a mtb.
Obviously mine are just opinions, it already works very well so with lcd03

buba said:

tomtom50 said:

A lot of people, including me, found upgrading to open source firmware difficult, because the information is spread out over two threads with over 200 pages between them. I also needed the excellent github information and jbalat's videos, and those resources weren't immediately clear to me as I went through the ES threads.

Here is my attempt at a comprehensive tutorial for installing Open-Source firmware with KT-LCD3 and also flashing stock firmware. It doesn't cover everything. I haven't tried marcoq's method of installing OSF with the VLCD5. I didn't cover installing a temperature sensor. The waterproof connectorized cable is for an 8-pin system, etc.

I think it is pretty complete and good for someone new who has never before dealt with connecting to embedded processors. I wrote it before I became so comfortable with the process that I would glide over things that would not be obvious to newcomers.

Revise & re-post as you like. I hope it works for others.
Open Source and Stock Firmware Tutorial.doc

Click to expand...

Great job! I think and hope this will help many!

Have you thought of adding your tutorial officially on GitHub? I think it would be a great tool. You have clearly put down a great deal of effort into it. If you add it on GitHub, do not forget to credit yourself.

Otherwise, I would not mind adding it myself. Would of course credit you for the work. I am a bit time constrained at the moment though.

I just want it to be readily available for everyone!

Click to expand...

Thanks. I was thinking of figuring out how to add to github, you are welcome to do it too. I have to free the time, not sure this weekend works.

casainho said:

I think you could close the KT-LCD3 and focus on color LCD, because it has much more memory so will be possible to add much more features with the advantage that will be easier for user to understand all that fields, since we can custom label each field.

This is just an idea because I think using to much of your time for optimizations of space may be without much interest for you. Also we should try to have something simple and easy to understand, not something complex to understand that users will avoid to use because of that.

Click to expand...

Transitioning from KT-LCD3 to Bafang 850C would be alot easier if a new cable didn't need to be hacked.

I have seen some new TSDZ2 kits include Bafang 850C, so there must be a cable now in production. Does anyone know more?

buba said:

Okay, anyone want to test out the 0.19.0 beta 1? :wink:

Here is a link to the hex file for the KT-LCD3:
https://drive.google.com/open?id=1kgcgkNtmCiIDREVW_bBf5ekDKftLnotw

Here is a link to the wiki:
https://github.com/OpenSource-EBike-firmware/TSDZ2_wiki/wiki/Features-and-configurations-for-version-0.19.X-(BETA)

Here are some changes:

* Added a new sub field in the odometer field temporarily called Energy where user will see energy consumption and estimated range

* Added a function that measures and calculates consumed watt-hours per traveled distance since power on

* Added a function that estimates range since power on depending on how much capacity is left

* More accurate watt-hour measurement, do not forget to update the capacity of your battery

* More accurate time measurement

* Safer Walk Assist and Cruise

* Added option to enable or disable motor power limit quick-set-menu in the main screen

* Added option to set motor power limit in the configuration menu

* Merged previous configuration menu LCD Setup with configuration menu General Setup for better and faster setup. This also optimizes program size, see the wiki for more information

* Added option that enables user to enable or disable display of motor temperature in the odometer field

* Changed order in the Main Screen Setup menu in the configuration menu

* Changed order in the odometer field

* Added two new Main Screen Setup items

* Heavily optimized code size and speed, also cleaned up code and comments

Click to expand...

There is no need to update TSDZ2 motor? Only KT-LCD3? I tried v018.2 in motor and LCD and nothing worked. No boost, no more assistance stays same in diffirend levels alltough they was tuned to bigger values. I travelled about 20 kms and assistance fade almost away. Previous version v0.17.0 worked fine. Maby I try your beta tomorrow.

Thank you for your work developing code.

I’m also interested new color LCD.

Why this differenze? I have 18.02 and works... I no use Boost but all works.. yes there is little difference in assistence in different level But for me it's Not a really problem

dameri said:

There is no need to update TSDZ2 motor? Only KT-LCD3? I tried v018.2 in motor and LCD and nothing worked. No boost, no more assistance stays same in diffirend levels alltough they was tuned to bigger values. I travelled about 20 kms and assistance fade almost away. Previous version v0.17.0 worked fine. Maby I try your beta tomorrow.

Thank you for your work developing code.

I’m also interested new color LCD.

Click to expand...

There is no need to update the motor controller firmware. You can use version 0.18.2 for the motor controller and 0.19.0 beta 1 for the KT-LCD3 display. No problem with compatibility.

Everything should work as expected, Dameri, so do try to reinstall everything and reset to default values. Here are some tips for making a clean install:

- Scroll through the configuration menu and make sure everything is set as desired
- Make a total reset so the default values are loaded and then configure as desired

Or as Rafe suggested:

Rafe said:

What I do and it works well for me is when I first start ST visual programmer it automatically presents pages of all zeros for both the programme memory and data memory, then I simply programme each tab with the zeros so nothing remains of the previous firmware. Then I write the new version into the programme memory.

Click to expand...

Good luck!

casainho said:

Tiny LCD with bluetooh

PSWPower is selling the SW102 LCD for Bafang that seems a version of the eggrider LCD, for 45€. Seems a decent price.

Eggrider seems to use a Nordic microcontroller that includes Bluetooth.

SW102 listing on PSWPower and other online shops on aliexpress never mention Bluetooth but I found only a listing saying:

At present, this display does not have bluetooth function. If the bluetooth function is needed, it can only be customized with a batch order

Since they use a Nordic microcontroller that includes Bluetooth, I guess all this LCDs supports Bluetooth but it may be disabled/not implemented in firmware on some models.

I am being developing firmware for another ebike LCD (commercial project, not OpenSource) that uses Nordic microcontroller with Bluetooth, so I am familiar with this systems. They support the ARM GCC compiler, so would be more or less easy for me to develop for this LCD.

But the programming using bootloader on this LCD should be locked like on 850C so I think the only option is open the LCD and try solder the programming wires... let's see if is possible... I just bought 1 unit from PSWPower and should take 2 weeks to arrive.

This LCD has some characteristics many has being asking:
- small size
- Bluetooth
- cheap/medium price

Let's see if we can program it....

Click to expand...

The SW102 is interesting but like LCD3 it still does not have a clock for stand alone use, the Bluetooth enabled version is about £45 on ebay. The Chinese brand that make the SW102 Topology also make a full sized colour display with Bluetooth ds103+sw101

https://www.alibaba.com/product-detail/electric-bike-power-meter-Electric-Bike_60704927306.html?spm=a2700.details.maylikehoz.2.4b187cdcEuwQQM

Thanks for the information.

I really miss Real Time Clock, I love it on 850C as during the week I always run against the clock, when I go to shop, gym, etc.

The thing is that we can't make firmware for many LCDs so we should choose the ones that will stay long on the market. SW102 seems that will be one of them because it is announced as Bafang display and seem to have most the important feature the MTB guys are asking/similar to top brands MTB ebikes. I can find many sellers for SW102 on Ebay and Aliexpress but none for that ds103+sw101...

andrea_104kg said:

Why this differenze? I have 18.02 and works... I no use Boost but all works.. yes there is little difference in assistence in different level But for me it's Not a really problem

Click to expand...

I'm wondering that too. I try tomorrow metod that Rafe use and programme first with zeros and after that new firmware.

I didn't do that when I jump to next firmware and everything worked exept v18.02.

recension for lcd3: too many functions. It isn't understandable what there is in the screen and what to do to change something. You need the wiki on hand. Then the screen is too big . I made a mistake buying it. I'll buy something like the lcd5. Too many functions aren't necessary. The essential is to see the level assist, the human power. optionally a simple odometer and the total human watt, in the menu a function to limit the current, but to use a lcd as a watt meter isn't necessary, that's the work of a watt meter.

An example of difference in views, for me the wattmeter function is essential as I would not be able to push up a 25kg mtb, knowing how long the battery lasts for me is the most important function. Also knowing the instantaneous consumption in watts is important because so I can limit the engine power when the absorption will be too high. I do not really care about muscular power, it's what it is, I have an electric bike because I want to be facilitated, I already know that I would not be able to do without it.
As I said they are differences of opinion

casainho said:

Tiny LCD with bluetooh

PSWPower is selling the SW102 LCD for Bafang that seems a version of the eggrider LCD, for 45€. Seems a decent price.

Eggrider seems to use a Nordic microcontroller that includes Bluetooth.

SW102 listing on PSWPower and other online shops on aliexpress never mention Bluetooth but I found only a listing saying:

At present, this display does not have bluetooth function. If the bluetooth function is needed, it can only be customized with a batch order

Since they use a Nordic microcontroller that includes Bluetooth, I guess all this LCDs supports Bluetooth but it may be disabled/not implemented in firmware on some models.

I am being developing firmware for another ebike LCD (commercial project, not OpenSource) that uses Nordic microcontroller with Bluetooth, so I am familiar with this systems. They support the ARM GCC compiler, so would be more or less easy for me to develop for this LCD.

But the programming using bootloader on this LCD should be locked like on 850C so I think the only option is open the LCD and try solder the programming wires... let's see if is possible... I just bought 1 unit from PSWPower and should take 2 weeks to arrive.

This LCD has some characteristics many has being asking:
- small size
- Bluetooth
- cheap/medium price

Let's see if we can program it....

Click to expand...

This is the display I originally recommend and you strongly opposed if you recall. I have already done work and have these working with the TSDZ2, and a variety of functions... I'm a little surprised to see you pick this up now. What has changed? I would have sent you one for free... FYI these are one of the cheapest displays also, which is part of why I originally recommend it... It's a great solution in my opinion, which I why I pushed for it long ago

We have a batch with Bluetooth and can upgrade firmware very easily, as well as other functions if one wishes to implement... Also things like the clock are very easy, especially for someone like you... No soldering wires etc... I buy them directly from manufacturer...and have custom programming for BBS series and TSDZ2... Working on making it smoother for the open source code... But if you are now interested, it could be much easier. This is not my expertise and I have to enlist help... I could still send one if you want, just PM

eyebyesickle said:

casainho said:

Tiny LCD with bluetooh

PSWPower is selling the SW102 LCD for Bafang that seems a version of the eggrider LCD, for 45€. Seems a decent price.

Eggrider seems to use a Nordic microcontroller that includes Bluetooth.

SW102 listing on PSWPower and other online shops on aliexpress never mention Bluetooth but I found only a listing saying:

At present, this display does not have bluetooth function. If the bluetooth function is needed, it can only be customized with a batch order

Since they use a Nordic microcontroller that includes Bluetooth, I guess all this LCDs supports Bluetooth but it may be disabled/not implemented in firmware on some models.

I am being developing firmware for another ebike LCD (commercial project, not OpenSource) that uses Nordic microcontroller with Bluetooth, so I am familiar with this systems. They support the ARM GCC compiler, so would be more or less easy for me to develop for this LCD.

But the programming using bootloader on this LCD should be locked like on 850C so I think the only option is open the LCD and try solder the programming wires... let's see if is possible... I just bought 1 unit from PSWPower and should take 2 weeks to arrive.

This LCD has some characteristics many has being asking:
- small size
- Bluetooth
- cheap/medium price

Let's see if we can program it....

Click to expand...

This is the display I originally recommend and you strongly opposed if you recall. I have already done work and have these working with the TSDZ2, and a variety of functions... I'm a little surprised to see you pick this up now. What has changed? I would have sent you one for free... FYI these are one of the cheapest displays also, which is part of why I originally recommend it... It's a great solution in my opinion, which I why I pushed for it long ago

We have a batch with Bluetooth and can upgrade firmware very easily, as well as other functions if one wishes to implement... Also things like the clock are very easy, especially for someone like you... No soldering wires etc... I buy them directly from manufacturer...and have custom programming for BBS series and TSDZ2... Working on making it smoother for the open source code... But if you are now interested, it could be much easier. This is not my expertise and I have to enlist help... I could still send one if you want, just PM

Click to expand...

Well, on that time, if I remember, almost no one was selling it and was expensive like 100 euros, now it is very different.

I appreciate if you can send me 1 unit, but I am only evaluate for now. Please share pictures of the internal boards, etc, that is the most important for now.

The clock needs a specific piece of hardware to keep clock working while power is disconnected. Can you please confirm that original firmware has clock??

I have a Bug in the 18.2
When i Start pedaling in odometer blinking 1 and there is no assist. The same is with the walk assist. Push the down Button bike Start and after 1-2 sec the 1 blinking and Motor stop.

When i start pedaling in a flat area is no problem....
Only on uphill....


Mfg Michael

casainho said:

Well, on that time, if I remember, almost no one was selling it and was expensive like 100 euros, now it is very different.

I appreciate if you can send me 1 unit, but I am only evaluate for now. Please share pictures of the internal boards, etc, that is the most important for now.

The clock needs a specific piece of hardware to keep clock working while power is disconnected. Can you please confirm that original firmware has clock??

Click to expand...

eyebyesickle said:

This is the display I recommended, due to ease if update, compact size, price, and quality. It is the SW102 from TOPOLOGY.

HOWEVER... These won't be compatible with the open source firmware... I am working on hiring someone to make this display compatible with the open source firmware, or as an alternative, to make the open source firmware compatible with the stock displays/protocol... So we will see how that goes... It's all outside my expertise but I'm determined to make it work!

Click to expand...

Back at the end of August =). Only the Eggrider was alway expensive, but the SW102 was always readily available and cheap. I know now a couple more companies offer it, but if it doesn't have bluetooth, that completely defeats the purpose, does it not? For this to be realistic, you will have to have bluetooth... so someone will have to special order batches anyway... so that seems like slightly flawed reasoning... Also, FYI - these are so small I predict problems with disassembly, soldering etc, and reassembly, not only because of the size and limited internal space, but also because that it is put together without hardware mostly... so I fear there will be problems, and of course the waterproof/structural integrity will be compromised...

As for the clock, good to know about the hardware - I had no idea. The firmware I use does have a clock, but I am not sure of it functioning when the unit is 'off'/resting. I don't usually have these units mounted long term, still in testing phase. Except for on one model, but it has been sitting for quite a while with no battery at all... With the hardware you speak of, will the clock work long term unplugged, or can it just be off but still has to be plugged into a power source?

As for the 'original' firmware you question... There is not really 'standard' firmware...to my knowledge everyone's will be different mostly. Typically a bulk purchaser who gets access to certain things signs an NDA so there is only certain things to talk about...but typically someone would fill an application with requirements for firmware...so the starting point for everyone may be quite different. I was very disappointed with the firmware from these when I originally tested them, actually - but it is so easily changed!

Anyway, I don't plan to open any of my units, they are very easy to reprogram and I already have been working towards my own goal for some time on these. The clock is not important to me as I always know what time it is anyway... unless I misunderstand something.

So first things first, I think maybe you should open your unit from PSWpower, since it does not have bluetooth anyway, and it will not quite be a waste if it doesn't work out for you, since you cannot reprogram it anyway... The units I have are very easy to reprogram with blue tooth, so I don't want to ruin one for no reason, if you are still not sure if you are interested. I think it will be good to open the unit that doesn't have bluetooth function to learn if you think it is acceptable now, and if you think so, I would be happy to then send you unit(s) with bluetooth, and collaborate further if the situation calls for it.