Stumped on camera feed not available at driver station but only in matches

[Alan Anderson]

Originally Posted by adciv

In the 2015 season, we found we had to restart the dashboard before we went to the field or our USB camera would not show. The source of this issue was the dashboard grabbing using the IP address it picked up in the pits (172.22.11.2 or other) and not using DHCP to grab the new IP address on the field (10.X.X.X). You may be having a similar issue.

I'll second this.

[Greg McKaskle]

My suspicion is that the code is trying to establish a connection, but the other side isn't ready, so it gives up or doesn't successfully continue trying to establish in the background.

The LV dashboard has a dedicated loop that twice a second checks the connection. If it isn't valid or has an error, it closes anything it has and reopens the session. If the web browser works with the camera, and the SD client doesn't, the issue is with the client.

You may also want to try the default dashboard in its IP mode. Bayou had a team that started with the default DB, established the connection, then closed and opened the SD. That was their self-discovered process for getting it to work on the field.

Greg McKaskle

[PeeDiddy]

I'm not much of a coder, so i don't know half of what the suggested fixes are, but during my team's regionals, the cameras would work when tethered at the pit, but would mysteriously not show up with FMS connected. For whatever reason "RIOsetting" (resetting the rio) just after setting up on the field fixed our problems.

TLDR: RIOset the bot prior to retreating to driver station

[AaronS]

We isolated the issue to the specific lap top we were using for driver station and vison processing. There was an issue with the network chip/driver that we could recreate high occurance of dropped packets but in the end couldnt determine the specific issue. Changing to a duplicate laptop resolved the problem.