Are you using ppm or UART? If on ppm you need to either add TX/RX connections to UART or run a battery sense wire to your battery negative for battery level display.
If it’s just plugged into UART, go to remote settings in VESCTool and set it to “PPM+UART” or if it’s already set to that set it to just UART then reboot the VESC.
Make sure your TX/RX connections are inverted, so TX plugged into RX and vice versa.
Thankyou, have tried but no change. I’m running UART no PPM as this is the only option I have with the VX2 remote. Although, I do now notice that Flipsky have 2 options when purchasing the VX2, one is VESC4 (FOCBOX unity) and the other says VESC6. I have the VESC6 and previously worked with Flipsky esc. It doesn’t say what the difference is though.
I have tried flipping my tx/Rx too and that stops it from working altogether.
I have tried a few other settings to no avail but learnt a few things in the process (like why I don’t want Current bidirectional!)
I’m worried something worse than a remote config issue is happening. I haven’t yet assembled my board so haven’t been able to test yet. I have had one of my hall sensors miss detection a couple of times… Maybe unrelated??
I need to buy about 3-5mm of extra depth in this enclosure. Evo, 36 I think? eboosted enclosure. I already have rubber sheets on hand to make a gasket, but do you guys think it’d be a really stupid idea to sand about 1-2mm deep on the deck, where the battery sits, to minimize gasket size? It’s going pneumatic, so clearance shouldn’t be an issue either way, I just want it to be as sleek as I can manage. Without sacrificing integrity, obviously.
with the remote in UART mode, if you don’t have the proper battery settings programmed in you won’t get an accurate reading but you should still get a reading.
AFAIK the only difference between the VESC4 and VESC6 variants of the VX2 is a 6p or 7p JST plug and the swapping of TX/RX.
Current Bidirectional is meant for things like eFoils and other prop control where “brake” isn’t really brake you need reverse to “brake”
have you gone into the remote settings on the VX2 it’s self and tried different ESC setting options? there shoul be one that cycles through “FSESC, FOCBOX and VESC” or something like that.
Battery settings are good. But even so I would expect the speed and km’s travelled to display.
I’ve tried switching the remote between FSESC and FOC which are the only two options and that didn’t make any difference.
I mentioned earlier that I am replacing the blown esc that this remote receiver was plugged into. I wonder if there is a component on the receiver that handles the telemetry data that could be damaged? If that is the likely cause I could order a replacement from Flipsky
I doubt it but contacting Flipsky about it is still a good course of action. I’ve had these issues but usually they’re resolved by going through settings permutations until you get it right. Is the baudrate set correctly?
I’ve got everything packed away right now. But checked the vesc tool on my computer and settings on there show 115200 which matches what Flipsky say on their site for the VX2. Will recheck later but from memory the vesc tool shows you your last config when you open it up again.
ok, whilst trying to find some diagrams of receiver wiring etc, I stumbled across this post.
Should I be trying to use this ports on the Stormcore for the receiver?
I am using the port where this guy currently has a white ribbon. I can see someone posts below about not getting data back so maybe I’ve stumbled on something…
Might get myself the right size connector and try this?
That was Feb 1st and no other public holidays until April.
There is a COVID “lockdown” there though (one week?) so that might prevent employees from getting to the office.