GalaxyRVR continuously disconnecting from app. Pretty much unusable

After the disconnection, please check whether the “Galaxy” network still appears in your WiFi list. If the WiFi disappears as well, the ESP32 CAM may be faulty.

If the connection becomes laggy and then disconnects, but the WiFi network is still visible in your settings, the issue is likely channel interference. In that case, please try changing the WiFi channel.

I have the very same problem, just as you have stated. My Rover is sitting useless now for weeks.

Like I said, I don’t think it is a wifi issue. Camera stream is not interrupted.

Using a web browser client and running wireshark main reason for websocket disconnection is when client receives packet:

0000 00 00 00 01 00 06 b0 cb d8 c6 85 d8 7b 00 08 00 …{…
0010 45 00 00 b6 67 18 00 00 40 06 8f 02 c0 a8 01 66 E…g…@…f
0020 c0 a8 01 71 22 3d dc f6 b5 65 7d 7d c3 31 77 fd …q"=…e}}.1w.
0030 50 18 14 55 13 cf 00 00 81 7e 00 8a 7b 22 42 56 P..U…~..{"BV
0040 22 3a 36 ff ff ff ff ff ff ff ff ff ff ff ff ff ":6…
0050 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
0060 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
0070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
0080 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
0090 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
00a0 ff ff ff ff ff ff ff ff ff 2e 37 39 2c 22 4e 22 …79,“N”
00b0 3a 30 2c 22 50 22 3a 31 2c 22 4f 22 3a 2d 31 2c :0,“P”:1,“O”:-1,
00c0 22 4a 22 3a 30 7d “J”:0}

So all the ff values are inserted between valid voltage values.

Agreed. IMHO its not a wifi issue. The packet starts fine with an expected length of 138 (red) , the JSON starts correctly, {“BV”:6 etc (green)

then it gets corrupted, 0xff… which will cause disconnects.

The stream of 0xff are probably just uninitialised memory locations, which suggests possibly something like the wrong packet length is actually sent, i.e not the 138 specified in the header, or buffer is reused before fully empty, or even maybe memory fragmentation over time.

So, i personally think its a firmware bug. Just my own thoughts, but I may be totally wrong!

1 Like