So while at competition. We ran into the issue that if the limelight was connected to the radio,then we couldn’t tether into the robot to test as we cant conect wirelessly. How do other teams solve this issue? It was bad because we needed to dial in values based on the limelight reading.
We use a network switch to increase the number of ethernet ports on our robot. With that, you should have enough to use limelight, tether, and have a few extra ports in case you need those. Hope this helps!
Thanks, where would each Ethernet go on the switch?
You’ll have two ethernets plugged into the robot radio: one going to the Roborio and the other going to the network switch. You would then plug your limelight ethernet and tethering cable both into the network switch. I don’t believe it matters the ports in which each ethernet is connected on the network switch.
We use WPILib’s PortForwarder
(Java, C++, WPILib docs) class so we can access our Raspberry Pi while connecting to the roboRIO via a USB-B.
This dosnt allow access to the network tables
What switch do you sugesst
If all you’re tuning is your Limelight’s vision settings, you can connect directly to the Limelight via it’s Ethernet port and bypass your roboRio entirely. If you need to simultaneously connect to your LL and your Rio, I would also suggest adding an ethernet switch. We only use our switch in the pit or when testing, and then move the cables over to the radio for use on the field.
This is the switch we use.
Last year had the same issue, I brought in a network switch the day after.
Our team doesn’t have any true preferences towards network switches. Most of them work about the same. I know we have an industrial one on our robot for this year but I’m not sure if it really gives us that much of a benefit.
As mentioned earlier, WPILib has port forwarding built in now. You can connect to the Rio over USB and include this in robotInit:
// Set up port forwarding so we can access the limelight over USB
// visit '172.22.11.2:5800' (or 5801) in your browser (ie, Chrome) on
// the laptop to see the limelight
// Not sure why 5805 is required. Someone recommended it
// Probably internal limelight networking stuff
PortForwarder.add(5800, "limelight.local", 5800);
PortForwarder.add(5801, "limelight.local", 5801);
PortForwarder.add(5805, "limelight.local", 5805);
We haven’t tested it ourselves yet, but I’m pretty sure this should work.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.