Anyone seen this issue before. We can get 2 USB cameras to show up on our dashboard. But only in this manner. We need to
Connect the RIO to a LAN line
Reboot the RIO and it’s given a 192.168.X.X IP address.
Unplug the ethernet cable and connect it to the OM5P-AN radio
Start Up the Dashboard and the Camera’s show up.
If we reboot the RIO while connected to the OM5P-AN radio, there is no way to get the cameras to come on.
It feels like the RIO recognizes the two USB cameras but the dashboard can’t find the video stream address to show them.
I’ve tried lowering the resolution on the dashboard, but no effect.
I’ve tried lowering the resolution on Robot Main, but that gave a weird error so I don’t quite know if that would have effect.
Ok…Vision Enable Button is on the Front Panel of Robot Main. That needs to be set to True.
Second, finally figured out this problem and got my 2 USB cameras to work at the same time when RIO is connected to the Radio.
The biggest clue was if you go to the variables tab on your dashboard, you should see a “streams” string array. This is the address of the camera. For some reason, when connected to the radio the string path would be missing the “.local” part of the name, i.e. it would say “roboRIO-5205-FRC:1181/…”
When connected to ethernet or USB, that path said “roboRIO-5205-FRC.local:1181/…”
The “.local” is critical in finding the RIO. So here’s how to add it back in:
In 2017, they moved Send 2 PC.vi from the vision processing vi to Robot Main. Comparing it to 2016’s Send 2 PC vi, it’s been completely changed. Inside the Send 2 PC vi is where the above address is created and then written to a Network Table.
I simply reprogrammed the VI to look for the .local path in what was written to the NT. If it didn’t have it, I added using a concat string vi. If it did have it I left it alone.
Built and deployed the changed VI and everything worked.
Hope this helps someone else out there. This took me 3 days to figure out.
I am having the same problem, have you tried running the code from robot main while being connected to the robot via ethernet. If the camera responds then, we are in the same situation. Here is my post https://www.chiefdelphi.com/forums/showthread.php?t=155632
Ok…Vision Enable Button is on the Front Panel of Robot Main. That needs to be set to True.
Second, finally figured out this problem and got my 2 USB cameras to work at the same time when RIO is connected to the Radio.
The biggest clue was if you go to the variables tab on your dashboard, you should see a “streams” string array. This is the address of the camera. For some reason, when connected to the radio the string path would be missing the “.local” part of the name, i.e. it would say “roboRIO-5205-FRC:1181/…”
When connected to ethernet or USB, that path said “roboRIO-5205-FRC.local:1181/…”
The “.local” is critical in finding the RIO. So here’s how to add it back in:
In 2017, they moved Send 2 PC.vi from the vision processing vi to Robot Main. Comparing it to 2016’s Send 2 PC vi, it’s been completely changed. Inside the Send 2 PC vi is where the above address is created and then written to a Network Table.
I simply reprogrammed the VI to look for the .local path in what was written to the NT. If it didn’t have it, I added using a concat string vi. If it did have it I left it alone.
Built and deployed the changed VI and everything worked.
Hope this helps someone else out there. This took me 3 days to figure out.