@SeeTheBridges Actually I tried to use a voltage divider with my remote today, just to give it a try. And all my UART communication stopped working. I used a 1k and 2k resistor, maybe the values were too high? Anyway if the pins are 5V tolerant, there are no need
I had announced that I would be releasing a new software update today, but I have been having some issues to implement cruise control with RollingGeckos library. I found this library instead: https://github.com/bastianraschke/ESP8266VESC which has many more features, like setting the RPM value with UART. This I believe can be used to implement cruise control. Any thoughts on this?
Anyone got an extra spring and micro switch they got? Or maybe even got extra magnets. I know most people bought a bulk of them so I would assume that they got no other use for them. I would love to get them off your hands. I am willing to pay for shipping and any other costs.
@SeeTheBridges Well I like to be able to cruise at a certain speed, it’s nice on long trips
@Pimousse Yeah I was puzzled by it too, it should have worked. I use 115200, do you think that should affect anything?
@bimmer Yeah the VESC 6 got a build-in nRF24 antenna, however, I have not been able to figure out how to use it yet, and Benjamin isn’t of much help VESCs, in general, are so very complicated and - very undocumented.
When I use a simple Arduino powered by the VESC itself without other GND sharing, the comm. works flawlessly with the voltage divider even at 115200 bauds.
Now the point is that I’m using several devices connected to each other and it creates a mess with the GND.
I resolved issues by removing GND connection between VESC and Arduino and between Rx and Arduino.
So no more loop, the GND is now shared through UBEC only.
However, I can’t go above 9600 bauds otherwise I loose the comm.
Don’t know why.
I still have a lost packet time by time, but It’s only for monitoring purpose so it doesn’t really matter.
About nRF, Benjamin designed it to be compatible with his nRF controller.
Check the corresponding github repo, you’ll find more details about nRF comm.
Anyway, I’m agree : there’s freaking NO documentation although the VESC Project is meant to be a wide Open Source project…
I asked at the begin of the beta program to allow disabling the nRF module (thus avoiding to pollute with undesired RF on the same band as the bluetooth), but Trampa refused.
I’m still convinced that it really doesn’t help metr.at module to have a steady connection.
Hmm, I got my receiver all wired up, and it powers on. But for some reason I’m having that reset issue where the remote won’t connect unless I press the reset button on the receiver. The other guy in the thread with the issue got lucky and it sorted itself out so thats no help
EDIT: Hmmm, If I turn my board on an off a couple times, the receiver fixes itself. No idea what to do to make it a proper fix, but I’m just gonna hit the power button a bunch until it cooperates
How would I calibrate my remote without firmware 2.0?
Do you experience the same issue while the receiver is powered from USB and disconnected from VESC? And have you added a capacitor on the receiver 5v input? A few pictures of your wirering and setup would be nice
Removing that GND between the Arduino and VESC seems very dangerous, unless of course the Arduino gets GND through UBEC. Why have you connected Arduino receiver with UBEC? I would remove the ground connection between UBEC and Arduino, and keep the one between VESC and Arduino.
Yes, the UBEC shares the GND. If only I could use VESC power, of course I won’t use a UBEC, but Îm powering a lot of ws2812.
The total consumption is a bit high for the 2A 5V regulator built in the VESC.
Hmm, so I finally got my remote and receiver mostly working. Still having the power issues, but right now I’m more concerned with another issue. The Receiver is outputting to PWM with a MASSIVE min and max values. My maytech VESCs freeze anytime the timings go above 1ms annoyingly enough. I managed to fix it by going into the transmitter code and changing some values in the calculateThrottlePosition portion of the code. By lowering the maxHallValue and raising the minHallValue, I got my PWM signals between .3 and .9ms. with that little change, the Firefly is compatible with the Pulse Echo board after 1 little recalibration
VESCs, in general, are so very complicated and - very undocumented.
so thats no help
How would I calibrate my remote without firmware 2.0?