EasyDIY OpenSource display for EVs: TSDZ2 and Bafang M500/M600 EBike motors

[casainho]

Hi casainho;
is there any chance that you would port your open source display to the ESP32 (instead of the nRF52840)?
I know, it would than lack the Ant capability, but in my case (and I could imangine also a lot of other people), I am much more familiar with the ESP; it is much cheaper (and more readily available) and I don't need Ant capability (as I don't have any Ant devices)
Other than that: Great Project! (As all your your other ones, which are in itself great, but also are the foundation of many additional great TSDZ & KT projects)

No, I will keep with NRF52840 because ANT is very important as it can control and receive data wireless from devices usually used on EBikes and EVs, to communicate with remote controls, battery BMS, control the lights, read tire pressure sensors, etc. I really hope in future to use this wireless capabilities and this display is ideal to show data like from each battery cell voltage, turn lights on/off and even show the tires pressure.

The NRF52840 board is cheap and is available on Aliexpress, Ebay and dedicated electronic components shops.

 

[endlessolli]

Hi casainho;
is there any chance that you would port your open source display to the ESP32 (instead of the nRF52840)?

No, I will keep with NRF52840 ....

I kind of guessed already that you would say that - but I had to ask
(Just for claryfication: I did not mean to ask to completely replace the NRF..., but make an ANT-less ESP32 branch available).

 

[casainho]

(Just for claryfication: I did not mean to ask to completely replace the NRF..., but make an ANT-less ESP32 branch available).

That is not realistic, at least for the time I have available for this projects. My life time is very precious and I would not use it to keep parallel branches of the project.

 

[shimrod]

Hi,

I am probably being dumb but I cannot find the firmware for the display bootloader. At least I cannot find a hex file do you have to build it from source or is there a direct link to the hex file ?

thanks

 

[casainho]

Hi,

I am probably being dumb but I cannot find the firmware for the display bootloader. At least I cannot find a hex file do you have to build it from source or is there a direct link to the hex file ?

thanks

here https://github.com/OpenSourceEBike/ev_display_bluetooth_ant/releases

if you find more missing information, please report or make a pull request.

 

[casainho]

Note to enter in DFU to flash the firmware, after flashing the bootloader, you need to keep pressed the UP and DOWN buttons for at least 10 seconds, imediatly sfter power up the display.

 

[shimrod]

Hi,

I am probably being dumb but I cannot find the firmware for the display bootloader. At least I cannot find a hex file do you have to build it from source or is there a direct link to the hex file ?

thanks

here https://github.com/OpenSourceEBike/ev_display_bluetooth_ant/releases

if you find more missing information, please report or make a pull request.

Thanks for that I find github pretty confusing at times

 

[casainho]

I built the 3rd display and this will go to my MTB, where sometimes I need to use the Garmin Edge GPS display.

This time I used the more expensive 860C display keypad, because it has 4 buttons and will use the button four to work as ANT+ Controls, to change the page on the Garmin Edge - this means this remote (and display) will control both the display as also the Garmin Edge.
The button to control the Garmin Edge costs 50€ on the market, so this feature will bring a high value for the ones like me.

This 850C keypad is big, it seems it would be better on a electric motor cycle and not on a small and light MTB ebike.

The firmware is not yet developed, but we did it on the TSDZ2 fully wireless remote, so should easy to port it to this display.

 

[casainho]

So I just compared this third display with the others (the Vcc of the OLED display is now connected to 5V instead of 3.3V) and this is well noticeable that is better on the outdoors.

Soon I will update the schematic to reflect this change and I recommend everyone that already built the display to go and do this change.

 

[casainho]

I made a new firmware release, that seems mostly stable for me. Changes from latest release:
- increased assist levels to 20
- reset of battery Wh counter is now only checked once at startup

https://github.com/OpenSourceEBike/ev_display_bluetooth_ant/releases/tag/v0.10.0

I also updated the schematic so the OLED Vcc line is now connected to 5V and this is a good improvement on the brightness, visibility on the outdoors:

 

[shimrod]

Hi,
I am afraid I have another question re the display.
I have got all the bits and thought I would start making it after Christmas.
I had a quick look at the display software and see it uses a SSD 1306 driver chip. My 1.3" display has a SH1106 driver chip as do all the other 1.3" displays I can find. Are these compatible ? In a small Arduino project I did I had to use different libraries to get it to work.
If there is a problem I will use a .96" display instead.

 

[casainho]

Hi,
I am afraid I have another question re the display.
I have got all the bits and thought I would start making it after Christmas.
I had a quick look at the display software and see it uses a SSD 1306 driver chip. My 1.3" display has a SH1106 driver chip as do all the other 1.3" displays I can find. Are these compatible ? In a small Arduino project I did I had to use different libraries to get it to work.
If there is a problem I will use a .96" display instead.

Yes, I started with SSD1306 and then saw that I also needed the DISPLAY_SH1106. One is for 0.96 inches and other for the 1.3 inches.

The firmware is ready for both, as also SPI or I2C, for both. That is why you will find 4 firmware HEX files on the download firmware.

Good luck and please post pictures during the build, the details as also final build.

 

[shimrod]

Hi,
I am afraid I have another question re the display.
I have got all the bits and thought I would start making it after Christmas.
I had a quick look at the display software and see it uses a SSD 1306 driver chip. My 1.3" display has a SH1106 driver chip as do all the other 1.3" displays I can find. Are these compatible ? In a small Arduino project I did I had to use different libraries to get it to work.
If there is a problem I will use a .96" display instead.

Yes, I started with SSD1306 and then saw that I also needed the DISPLAY_SH1106. One is for 0.96 inches and other for the 1.3 inches.

The firmware is ready for both, as also SPI or I2C, for both. That is why you will find 4 firmware HEX files on the download firmware.

Good luck and please post pictures during the build, the details as also final build.

Thanks for that I will post some pics if successful ( not assured with my track record )

 

[andyb]

Hello, can someone please help me. Is this device a wired one, with BT and ANT capabilities or do I need to build the EBike wireless controller along with this.

Thanks.

 

[casainho]

Hello, can someone please help me. Is this device a wired one, with BT and ANT capabilities or do I need to build the EBike wireless controller along with this.

???

This is just a display. Although it supports Bluetooth and ANT, that features are there on the firmware but disabled, as there is no mobile app developed. Would need some developer to develop and maintain a mobile app for we get that feature.
As for ANT, again, it needs more developing and testing, so it will only happen if some developer want to do it.

 

[Fischer]

Are there any known alternatives to the BTS4140N power switch? They seem to be sold out almost everywhere. Or maybe a note of the important specs I can use to search for an alternative? Thanks!

 

[casainho]

Are there any known alternatives to the BTS4140N power switch? They seem to be sold out almost everywhere. Or maybe a note of the important specs I can use to search for an alternative? Thanks!

You can find it on AliExpress.

I am not good at electronics so I can not find a replacement.

 

[barthchris]

Wow!!! I just discovered your smartESC project then discovered this!!! Awesome and just what I need.

I have a pile of NRF52840 dongles from both sparkfun and adafruit. A pile of the OLED displays as well. Need to buy a few of the buck converters. Glad you jumped up to 5V, I have several other uses for 5V

 

[ptrj]

This looks like a fun thing to start with. Found a promising buck converter and a Adafruit SSD1306 oled 128x64 yesterday to start with. Eveything is solderd and running I think. Currently headless since I cant get the android 'EBike Wireless' app to connect/pair when on firmware or get the display to work.
Adafruit seems to have the I2C address @ 0x3D. Do I have to change this value somewhere? Started out in SPI but no luck so I also tried the I2C mode. Dispaly is working with my arduino.
Whats the procedure to connect 'EBike Wireless'? When in bootloader mode I can atleast see it on phone but not connect.
Have a nice day!

edit:
found this in SSD1306.h
#define SSD1306_I2C_ADDRESS (0x3C) // 011110+SA0+RW - 0x3C or 0x3D
// Address for 128x32 is 0x3C
// Address for 128x64 is 0x3D (default) or 0x3C (if SA0 is grounded)

So, either change #define SSD1306_I2C_ADDRESS (0x3C) to #define SSD1306_I2C_ADDRESS (0x3D) or ground the A0 pin.

 

[casainho]

This looks like a fun thing to start with. Found a promising buck converter and a Adafruit SSD1306 oled 128x64 yesterday to start with. Eveything is solderd and running I think. Currently headless since I cant get the android 'EBike Wireless' app to connect/pair when on firmware or get the display to work.
Adafruit seems to have the I2C address @ 0x3D. Do I have to change this value somewhere? Started out in SPI but no luck so I also tried the I2C mode. Dispaly is working with my arduino.
Whats the procedure to connect 'EBike Wireless'? When in bootloader mode I can atleast see it on phone but not connect.
Have a nice day!

edit:
found this in SSD1306.h
#define SSD1306_I2C_ADDRESS (0x3C) // 011110+SA0+RW - 0x3C or 0x3D
// Address for 128x32 is 0x3C
// Address for 128x64 is 0x3D (default) or 0x3C (if SA0 is grounded)

So, either change #define SSD1306_I2C_ADDRESS (0x3C) to #define SSD1306_I2C_ADDRESS (0x3D) or ground the A0 pin.

Good that you found the way to use the display. Would be better if you ground that pin and use the original firmware, so we will have the same hardware.

I think the current firmware has Bluetooth disabled, as there is no compatible app.

The only think you can see in Bluetooth is the bootloader. Once you have the bootloader running, then you can flash the firmware, see here how to do it: https://opensourceebike.github.io/dfu.html

Please report later and take some pictures to show here!!

 

[dogstoevski]

I built the 3rd display and this will go to my MTB, where sometimes I need to use the Garmin Edge GPS display.

This time I used the more expensive 860C display keypad, because it has 4 buttons and will use the button four to work as ANT+ Controls, to change the page on the Garmin Edge - this means this remote (and display) will control both the display as also the Garmin Edge.
The button to control the Garmin Edge costs 50€ on the market, so this feature will bring a high value for the ones like me.

This 850C keypad is big, it seems it would be better on a electric motor cycle and not on a small and light MTB ebike.

The firmware is not yet developed, but we did it on the TSDZ2 fully wireless remote, so should easy to port it to this display.

Hi. Thank you for all the info and your effort.
Does the 860C controller switch have five pins? Which pins did you solder to which pins on nRF52840?

 

[casainho]

I built the 3rd display and this will go to my MTB, where sometimes I need to use the Garmin Edge GPS display.

This time I used the more expensive 860C display keypad, because it has 4 buttons and will use the button four to work as ANT+ Controls, to change the page on the Garmin Edge - this means this remote (and display) will control both the display as also the Garmin Edge.
The button to control the Garmin Edge costs 50€ on the market, so this feature will bring a high value for the ones like me.

This 850C keypad is big, it seems it would be better on a electric motor cycle and not on a small and light MTB ebike.

The firmware is not yet developed, but we did it on the TSDZ2 fully wireless remote, so should easy to port it to this display.

Hi. Thank you for all the info and your effort.
Does the 860C controller switch have five pins? Which pins did you solder to which pins on nRF52840?

The extra pin compared to 850C remote switch, I connected to P0.17. Still, I did not yet develop the firmware to use that extra button for Garmin change page.

 

[gfmoore]

Hi,
does anyone have the juliet pinout and/or wire colour codes for the850C remote keypad readily available?

If not I'll get off my backside and go get a multimeter!

 

[casainho]

Hi,
does anyone have the juliet pinout and/or wire colour codes for the850C remote keypad readily available?

If not I'll get off my backside and go get a multimeter!

If you get that information, share here and I will add to the page.

And I hope you can share pictures of your display build!!

 

[SUPERJC]

So I just compared this third display with the others (the Vcc of the OLED display is now connected to 5V instead of 3.3V) and this is well noticeable that is better on the outdoors.

Soon I will update the schematic to reflect this change and I recommend everyone that already built the display to go and do this change.

For my Bafang BBS I try DIY display Oled and TFT
Outside the TFT is a little more readable
…and life is better in color