@814glass hey there, did you figure out how to fix it? Because I have the same issue and over last ±5 hours didn’t figure it out and just at this point trying out stuff
Although I figured out that if you switch the green and orange wire the trip value will be zero as it should be, unfortunately remote still won’t be working
Bro I also have a Demon 2.0 with FOCBOX and VXs have been nothing but trouble for me.
First VX2 was constantly disconnecting and second one works but has a 150ms delay between when I punch the throttle and when the wheels start turning. (VX1 didn’t have this issue).
If you don’t have another remote to compare against you might not notice this issue but once you’ve felt the instant response of a VX1 or something the VX2 straight up sucks (unless my replacement VX2 is also busted in some way that’s also possible).
I gave up on the VXs and switched to the remote Derelict Robot is selling. It’s theoretically only is beta right now and it’s expensive but damn it’s great it just works.
Not that helpful I know since you want your remote working now not a month from now.
Hope you can work it out.
Re the FOCBOX/FEVESC setting yeah even tho you have a FOCBOX you must NOT use the FOCBOX setting on the VX2 - that only works with old FOCBOX firmware that no one is using anymore. You gotta use the generic FEVESC setting.
Huh… Well in my case it didn’t. Still worth a try I’d say (switching to UART-only mode).
Unless… I wonder if that’s why I had that delay issue. Maybe it would have gone away if I’d gotten ppm mode working? Oh well not going back to the vx at this point anyway so we’ll never know.
So i did figure it out. When i followed the setup video for my board they had the old version of vesc. So i didnt have values set for battery discharge and regen, so it makes perfect sense that it had 0 discharge and 0 regen so no power:rofl: real big brain moment for me.