That doesn’t seem right… Which version of the vesc tool are you on. I don’t remember mine being setup like that
Geeze it’s so bad. I was trying to figure out why the Roxy (davega os fork) wouldn’t work with the latest version of firmware and was digging around to try and figure out why…
I’ve forgotten how bad c is to work with.
2 Likes
Roxie is the reason I’m sticking to 5.2 for the moment.
1 Like
The VX2 doesn’t need programming at all, you just connect the receiver, detect the motors and thats it. There are some settings in the software but idk about that.
1 Like
I’m on 3.0.0
It does need programming if you want it to do what you want
1 Like
Someone somewhere has their own custom code to my type of vesc to be able to do whatever I’m trying to do. Just gotta find that someone lol
That may be why you’re options are limited.
Which vesc do you have?
Flipsky mini 4.20
I wish I got a focbox now lmfao but I was on a budget
I have a question about the vx2 remote. I cannot make my own post so I have to reply to others posts to ask. I have a dual fsesc 6.6 vesc on my board and tried connecting the remote for the first time last night. I updated the firmware, changed ppm to uart in all the places I could in the vesc tool, yet whenever I command my remote the wheels dont spin. Despite this, If i spin the wheels on the board I get a mph reading on the remote meaning the two are connected and sending data. I don’t know whats causing this and I can’t find anyone whos had the same issue. Please help!!
Have you tried using the vesc tool to detect your motors? If you go into setup motors foc you should see an option that says “advanced” and it’ll let you run an auto detection to see if your motors are properly connected or if the vesc is recognizing anything
This is an extreme solution to the problem but my vx2 had the hall effect sensor come off of the PCB.
I soldered it back on and it started working.
This is probably not the issue but could be…
That would be a last resort kind of thing…
Have you tried going through the input wizard.
Hmm unless I’m mistaken that vesc can use standard firmware. I would try upgrading to 5.2 or 5.3
You should also double check the wiring on the receiver. Vesc 4 and vesc 6 have different pins for uart
Do you know where I can get the firmware upgrade?
3.0.1 has the same settings as 3.0.0. Still don’t have more ways to program asside from only being able to have current
false. I think others have made the main points here, but…
If you spend the time to set up proper current settings and throttle settings for you, your board, and your remote, you won’t have to keep bumping it. you’ll be able to find a good position and hold it. And bonus: you won’t get tossed onto your face when you let off the throttle.
and yeah the VX2 when used as a UART remote doesn’t need any curve adjustment at all in my experience. It sounds like you should probably just turn your motor current and regen settings down a tad or play with them a bit to get them tuned.
1 Like
Wdym false. No matter how many times I program it it’ll kick up into full throttle even if you push it slightly. There’s no way to program it to go different speeds with current no reverse. It’s either 1 set speed or no speed at all
Does it do that on its back or while you’re on it? Are you using it in PWM mode? or in UART mode? Because what you are describing is a common failure in PWM mode when the receiver goes to shit, which is always possible,