Fardriver Custom Bluetooth Display speedometer ESP32 & ILI9341 2,8"

[hetm4n]

Hello. I managed to create an interesting display that reads and displays parameters on an LCD. I designed the screen in Squareline Studio, and the program for the ESP32 Wroom was written using ChatGTP. I based it on a Bluetooth data readout file from bobecek79 >
"Github bobecek79 blereader fardriver".
The program allows you to read the following data:
voltage
lineCurrent
power
rpm
gear
DNR
speed
controller Temperature
motor Temperature
baterry soc
Regen From Current

The entire project is written in the Arduino IDE with plugins and appropriate libraries for the ESP32. Anyone with Arduino skills can implement any other display. For creating the screen UI, I recommend the free, personal version of Squareline Studio. In the program you only need to change the UUID address read from Bluetooth, how to do it is described in the instructions on github. In serial monitor we can set the total mileage "ODO" by entering the command "setodo xxxxx" where x is your total mileage. I made the housing from 20mm thick black POM-C plastic on a CNC milling machine, and the top from 2mm plexiglass.

 

[Bikeronin]

Hey mate I’m a bit late to the party, but this is brilliant.

I’ve been thinking about building my own custom display for a while, mainly because changing parameters on the stock display is honestly pretty clunky. My original plan was to go full Raspberry Pi, dig into UART protocols, and try to reverse-engineer how my controller/display are talking even looking at whether I could sniff whatever comms the controller is using and build on top of that.

But the way you’ve approached this is really promising, because it sounds like I can get the functionality without the Pi cost/complexity.

Just to make sure I’m understanding it properly: are you reading data by connecting to a Bluetooth device, or have you actually figured out a direct way to communicate with the controller over UART?

 

[Madivad]

Hey. I'm very interested in this too. I came here for the same reasons as Bikeronin.
1) changing parameters is "clunky" at best
2) unnamed parameters make remembering which ones to change quickly on the fly too hard
3) too many insignificant parameters. ie you're never going to change many of them outside of initial installation and could be hidden behind "advanced" config
4) have named/single button or menu driven changes available.

I love your display design.

Will dive deeper. Thanks.

 

[hetm4n]

Hi. This is only Bluetooth reading. There are no plans to expand the project; what I've managed to achieve is adequate for me. I'm currently switching to an ERIDE Pro SS and won't be using the FarDriver. Maybe in the future if the ERIDE controller breaks.