We ran into this issue last week (Week 4) in Midland. The fix for us was to plug in to USB port 0 with the camera. We were using Labview and a USB camera. It would work when tethered, but not on the field. The FTA helped us figure out the issue.
Not sure if this is the same issue you are seeing, but worth a try.
1676 ran into that issue as well. It is a problem with the ip address of the usb camera. If you tether with usb and then try to go on the field the camera will still have the local address from the usb connection. You need to restart the driver station/dashboard before going on the field to take care of this.
Not sure how much of this was fixed, but our fix to this in Week 1 was redeploying code before every single match. Stressful? Yes. Did it work? Also yes. Is it a good solution? No.
I cannot overstate how risky this solution is. If the code does not deploy successfully you risk leaving your robot in a “No Robot Code” state on boot, which will likely result in you being bypassed for the match. Code cannot be deployed while on the field network. If you do employ this strategy, please after deploying, reboot your robot and ensure the Robot Code light turns green on the Driver Station (not just the communications light).
I believe the copy of the code living in flash memory starts anew the same way every reboot, regardless of if a deploy occurred during the last boot. There is likely a different part of the process involved in redeploying code (connection order, reboot time, something of that nature) that makes the camera connect.