@rey8801 thats probably because Ackmaniacs firmware is a few commits behind Vedders.
@Flo Yeah actually I think the library I have made works with both v4.x and v6 hardware as long as you install the newest firmware (3.40).
2 Likes
yes, I thought so. I just wanted to let you know. Also for others that might be interested.
Good find⌠A friend was trying to figure out why he wasnât getting telemetry. Looks like this might be the reason.
1 Like
Yeah I was scratching my head a lot yesterday, and I figured some of you guys probably have had the same problems 
I do not know which firmware version broke the telemetry, but it should be easy enough to roll back the updates and find a firmware that works. I will have a new update for the receiver and the new library released tonight.
3 Likes
That sounds great that you will share the library with us tonight
Iâm a little curious if you managed to solve that problem:
Will we have to wait for another firmware update for Vesc6 or did you get around that problem?
The longer packet lenght is not an issue as long as you read the serial buffer fast enough. The old library used a delay(10) after sending the UART package to the VESC. This way some data will be lost if the buffer isnât big enough. I have made it different, such that it listens for and reads the serial data as soon as it arrives - therefor not losing any data.
I have not tested it with my VESC 6 yet, however the newest firmware for VESC 6 is also FW3.40 right? So it should work.
1 Like
Yes FW 3.40 is the latest for VESC 6.
Wonderful canât wait to get my bike running again 
Could a âbadâ or damaged Arduino cause brownouts? I do not have a reliable connection. It is constantly connecting and then disconnecting. When I fiddle with the Tx, like moving it and such it will connectâŚso I thought it was a bad connection. Yet all connections are soldered fine and checked.
Arduino Nano. Currently Testing off USB. Previously had working but now it is not.
If I move the NRF24l01 it will connect, but then crash and freeze.
I have released the new VescUart library. It is basicly the same as RollingGeckoâs however cleaned up a bit and updated for the new FW3.40. The library can be found here: https://github.com/SolidGeek/VescUart
I have also updated the receiver software on the development branch to make use of the new library. It works great on a VESC 4.12 however I have not yet tested it on my VESC 6 as it powers my main board at the moment.
Further testing is needed if anyone is up for the task @Flo @ervinelin
6 Likes
The one I recommend with a dedicated 3.3V voltage regulator? And you are sure none of your nrf24 wires arenât shorted?
I checked them all multiple times, and tried many different NRFâs.
You need at least a 47uF capacitor on your 3.3V rail, on both receiver and remote. Otherwise the power is not sufficient.
Strange, it worked before. I will solder it on now. Also if any one wants a modified STLs for these cheaper, and probably lower quality lol NRFâs, let me know. I donât have all the stuff in the Rx or have it cleaned but whatever.
Is this backward compatible?
Thanks for sharing !
Indeed, I tried again, FW3.38 can be used, FW3.40 can not be used. I used the previous library.
What library are you using with ?
I am getting 5v when powered from the remote not USB to the 3v3 pinsâŚwhat could cause this? A blown part in the arduino? I think it is. When powered off USB, the Tx gets .68 volts. When powered from the Tx remote/boost converter, it has 4.10 volts. I am gonna replace the arduino.
EDIT: I powered the NRF off a NodeMCUâŚwhich has a 3v3 output. Boom. Instant stable connection. Something is wrong mechanically or electronically with the arduino, by differing different points of pressure on the board can change the voltage outputâŚwhatever. Sorry for blowing up this thread lol. Itâs fixed. Nice job to solidgeek for correctly diagnosing the power issue, thanks.
2 Likes