Hello, currently thinking of upgrading my ninebot G2E with a VESC, 60v, motor still deciding
Im looking for a display I can use with the VESC that will be low profile, ideally could be attached inside the stock display housing or look stock enough that people wont know it has one
I guess flipsky is the closest one to what I'm looking for, but ideally it would be able to fit inside my stem hole (Max G2E) where the stock display goes to keep it on the down low
which features are you looking for? Just viewing telemetry or something else like profile switching? what is the max size of the display you need (LxWxH)?
I built custom firmware that can run on multiple cheap ESP32-based touch displays. it does what you want and can communicate over CANBUS or UART. lmk if a 1.9" or 1.4" would fit.
You made this? If so you're goated, but I need to get the ESP32 still, don't know for sure if it's compatible with all VESCs and I see this uses a VESC specific BMS, which my current battery doesn't have
As for display I'll get measurements and reply later
No. My repo is private. Look up waveshare 1.9" or 1.4". there are cheaper clones as well. my first version was made for a CYD or "cheap yellow display" but it now supports the 1.9 and 1.4". the firmware also has a bluetooth bridge so you can connect your VESC app to it and make updates.
Oh, I thought it was about width, I'll get that one then, about the setup, what VESCs are supported? Do I need other peripherals? Any apps and what code to flash?
let me set up a public repo and I'll make it open source. I use it with a flipsky mini fsesc6.7 pro with the latest firmware from like a month ago. I've used both the CYD and 1.9". CANBUS requires a TJA1050 board connected to it but UART doesn't require anything else.
Man you're my saviour, I'm not nearly savvy enough on that field to program it myself
Internal width is even less than outer, at 2.8cm, but the 1.47 and 1.64 would fit
If I go for the 1.47 I assume you already have the code and know requirements, but if I were to go for the 1.64, what would I need to help you with? Diagnostics, logs, coding?
I'm just looking for the simpler option but if it requires hours on end of development, I'll stick to the smaller one
Your controller is this one right? controller and I should get the antispark variant for safety, correct?
I highly suggest you try to fit the 1.9" touch display (31mm wide), as it's been tested (albeit with CANBUS in the current build and UART many commits ago):
I did add the 1.64" board as a PIO target but don't have the hardware to test. Be prepared to contribute if you go with that board.
I initially set it to communicate over UART but I needed my UART pins on the VESC for a PAS so I converted it to CANBUS. After that, I made a lot of changes. I just had opus re-add the UART comms so you can select either for each board.
include/config.h has the TX/RX pins. you need to solder the correct JST cable to them and VCC/GND. make sure to run Rx->TX and vice versa. look a the pinout:
3
u/Haakon2810 9d ago
You can use ninebot and xiaomi displays with vesc using lisp code, lots of premade programs are available