I’ve had the same happen. I feel like it can happen when you loose gps signal somehow during a ride and keep on moving after losing it so it cannot lock again.
To get the best signal, turn on the remote, lay it still in the open, and let it do its thing for some minutes, that will give you a good satellite lock (20+).
Same here, but i noticed it at the beginning…got no speed and no gps, therefore i shut it down and back on, waited to lock and started recording…all good since then.
OK so my experience wasn’t unique. Worked fine during a session yesterday using my normal process.
It does seem odd that it must of had GPS lock as some point as it recorded trip. I can understand a device loosing GPS but my VX5 has never done that before and even if it did why didn’t it recover
Not worried about it now that it has worked normally.
I have had several “normal” sessions since I posted about my “no gps issue” and have experienced the same thing today. I have altered my start process as suggested by powering on remote before I enter the water so it has lots of time to acquire satellites. I have an auto click set for 15seconds so feel safe enough that I won’t accidentally trigger prop.
So almost identical failure of trip distance <1km although I did about 10km but a new symptom this time.
I always power off remote before I carry the board out of the water. This time once on shore I powered on again with board battery still connected to VESC. Although the remote would spin the prop. No speed showed although a small trip distance showed. Also the auto lock function didn’t trigger. Power cycled remote and same weird behaviour.
Packed up and tried just the remote (no connection to VESC) about an hour later and auto lock and everything else in the menu system seems like it was working.
I don’t really care about the screen functionality as I rarely look at anymore but I did have a concern that the “real” functions like throttle control might malfunction.
I think I will reload the version of remote firmware I’m running and see if that helps clear up the “weird” behaviour.
Aug 14 2026 update
I reloaded the firmware (the same version I have been running since I got the remote) and have had multiple
sessions where everything is working normally.
During the reload process in the first attempt to just overwrite current version with same it didn’t seem to do anything although the process indicated it completed correctly. I then loaded a newer version and then overwrote that with the version I wanted. That resulted in an obvious change where I had to alter the default setting to what I wanted/needed.
@janefoil
Your post makes me wonder about signal blocking. I injured the knee of my forward on board leg and have had to modify my takeoff-standoff process in a way that perhaps my body is over the hand my remote is held in.
I’m pretty sure gps signal from multiple satellites would have a wide range of angles so not sure that theory has merit but I’m kinda stumped about the behaviour.