I will try it - but it doesn’t seem to have anything to do with dead zone.
Even when I push the throttle up to full - way out of any dead zone - nothing happens for half a second.
There doesn’t seem to be any dead zone setting under APP CFG General or APP CFG UART
I tried changing dead zone in APP CFG PPM Mapping to zero but that had no effect.
Tried it. Same thing.
probably broken remote, maybe ask flipsky about it?
1 Like
so when using UART you’re not in PPM mode, changes in there won’t do anything. Now that I’m looking through it again I think I might have gotten mixed up too though. I was looking in APP CFG>VESC Remote>Input Deadband, but I think that might be specifically for the Trampa Wand?
OH MY GOD WHAT A COMPLETE PIECE OF SHIT THE VX2 IS
Took it for its shakedown cruise today. It’s not enough that every time you let off the throttle it takes half a second to accelerate again leaving you at risk of being run over by a bus you had timed it to miss.
Over the course of four hours it disconnected TEN TIMES.
Any one of the them could have killed me if it came at the wrong moment.
I don’t understand how the same company made the VX1 which has never disconnected on me in three months. Not once.
This widowmaker is going straight in the garbage. I’m not even going to sell it. I can’t responsible for what would happen.
@b264 was right about this thing.
1 Like
I have used my for over a year and it never disconnected on me and the throttle on mine is instant, you probably got a bad one, try to exchange it when it works well is great
3 Likes
When and where did you get this?
It’s not normal behaviour for this remote. Either the reseller or flipsky themselves should replace it.
6 Likes
Same here. Works fine for me and have had it just as long
1 Like
I never tried the VX2
I have three of them and unlike my experience with the VX1 my VX2s have all worked perfectly. Instant response and I have yet to drop signal. Sounds like a bad unit. Classic Flipsky QC bullshit. I would ask for a replacement from wherever you purchased it.
1 Like
Will try that. Talking to @PropulsionBoards about this now.
1 Like
I got replacement for my VX2 that was disconnecting.
Took it for a shakedown cruise and no disconnects ~an hour of riding.
So that’s good.
It still has about a 250ms delay between pushing the accelerator and something happening which the VX1 doesn’t have.
I guess I can learn to live with that if I means I get a battery gauge and everything - it’s just the way the VX2 is I guess. It must be just coded a little bit more inefficiently in order to to drive that screen or something.
1 Like
I wonder if this happens to anyone else and if there’s a fix for it. I’ve got the same going on
God it’s annoying.
I have to be so easy on my acceleration because of that delay or I get all wobbly.
I have to choose between VX1 and no display or VX2 and balkiness.
1 Like
I guess I can’t really speak to a ‘delay’ as this is the only remote I’ve ever used and I have nothing else to compare it to. But it seems very responsive to me at least
Yeah it’s possible you don’t notice it because you have nothing to compare it to.
If so I wish you could try my VX1 so you’d know what instant response feels like.
It’s also possible it’s not happening to everybody.
I wonder if it’s the combination of VX2 and focbox that causes the issue.
@Ricardo what’s your ESC?
Mine is a 2x Focbox unity (4wd setup). What’s yours?
single focbox unity