Good to see you around here again! That’s some fantastic information!
My thought (and what I thought you had been working on a year or so ago) was to have an NRF (or the micro ppm or sbus based connection between the controller and the vesc for reliability and then a Bluetooth connection between the controller and a mobile device (Bluetooth because of the widespread availability/compatibility of Bluetooth) for added viewing, recording, and maybe even configuring. Are you saying that’s not possible?
I’d like to look into the micro ppm and sbus modules you referred to. Is that something like this?
Exactly what I had been looking for - both the NRF24L01+ for communication and a screen! How are you measuring current draw and voltage, is this ouputted through uart from vesc?
Yes I will make a build list soon. I take no responsibility for the use of my designs, or any of the software and parts. If anyone injures themselves, please know you built this at your own risk. I may even make a video today on my new PC
Funny to see controllers with oleds now.
I have been working with mine for over 1 month
Mine has a menu with options like change the light color, speed, acceleration, max amp etc.
And like yours, showing battery voltage and avg motor ampere
Soon I will have a gps in my board that will log the location and give me the current time zone, so I can see on my remote what the time is instead of taking the phone out of the pocket.
But one question why are you using a SPI OLED display? Why not I2C OLED display? With the I2C you only gotta worry about 4 pins, GND, VCC, SCL, SDA. And with SPI its like 6 pins…
I agree that an I2C display would be better pinwise - it also means the screen pcbs are smaller as there are less pins. This would be very useful for me as I am going to make next year a controller with a display angled like an HTC vive controller being held with the trigger upwards. I like the idea of the boosted wheel replacing the top of the joystick, but am wondering if there is not too little travel in a joystick. Finally, is variable braking power (like variable throttle) supported in RollingGecko’s code?
Not sure why RollingGecko didn’t go I2C… I’ll test the travel of the joystick once my 3d printer is finally up and running. What do you mean by variable throttle?
When you have an esc (e.g. on an rc plane) you can control the speed of the motor using that esc. I would like to be able to do the same with reverse (if a certain button is pressed) and have pulling back on the throttle past the neutral point to be increasing braking force. I have not yet bought a Vesc so do not know how to do that (for the moment)! Has anyone tried contacting RollingGecko on this forum for input?
Mine has a menu with options like change the light color, speed, acceleration, max amp etc.
And like yours, showing battery voltage and avg motor ampere 
Soon I will have a gps in my board that will log the location and give me the current time zone, so I can see on my remote what the time is instead of taking the phone out of the pocket.
