Quote:
Originally Posted by snekiam
We used this switch this year with no problems whatsoever. It is 5v, so just power it from the VRM.
A raspberry pi is 0.0683433 pounds. I do not see that putting you over the weight limit, and even if it did, shortening all your wires and zip ties would probably put you back under it. The switch does weigh a little more than the pi, but still not enough to really make a huge difference in your overall bot weight. Overall solution shouldn't be more than a pound. |
Oh wow did we have troubles! We had our vision hardware working at home with:
TRENDnet 5-Port Unmanaged switch
UNITEK USB 3.0 to Dual Gigabit Ethernet Adapter
Kangaroo Mini PC Static IP 10.32.44.20 (Running GRIP)
Roborio mDNS
OM5P-AN Access Point Configured for Home use
Axis IP Camera Static IP 10.32.44.11
Driver station Obtain IP automatically
Connections
OM5P-AN Access Point Port 1(Nearest Power) -> Roborio
OM5P-AN Access Point Port 2 -> TRENDnet Port 2
Axis IP Camera -> TRENDnet Port 3
Kangaroo Mini PC -> UNITEK USB 3.0 port 1-> TRENDnet Port 4
UNITEK USB 3.0 port 1-> Driver Station
At home with the radio configured for home use wireless and tethered control of the robot worked and the Network tables updated with vision data
After plugging into the FTA radio configuration laptop for the Gitchi Gummi Get-Together 2016 all robot connections was lost to the driver station. Franticly hunting for solutions we could nolonger PING the Roborio so using a USB cable we opened the Roborio web page and found the network set to obtain the IP and the current IP was 169.abc.xyz.lmn (Something very wrong. We set the IP to static 10.32.44.44 to get things working. Still no communication with above configuration. We removed the Switch and Kangaroo using only the OM5P-AN Access Point to finally get Driver station to robot control.
Throughout the day we attempted to change the IP of the Kangaroo to 10.32.44.120 and found some Subnet Masks to be 255.255.0.0 and some to be 255.0.0.0. In the end Everything is set to static IP's and Subnet masks of 255.0.0.0. Other teams gave it a great try and the FTA at the event gave it a real good go too. He also helped us work through some extremely high packet trip issues that ended up being our Driver Station CPU usage. installed a New Laptop and Trip times cured we will have to go back to that one latter. Our FTA at this events gut feelings are our Roborio has a symptom some team have found but the FRC people have not discovered yet to why.
By the end of the event we had to unplug and plug the Ethernet cable to the Roborio each time we connected to the field. We had satisfactory control during our matches with a simple camera viewer on our smart dash board.
The frantic speed of this event I forgot many of the different things we had tried to get things back working. If any of you have suggestions to what we could look at please share. We will be poking away at it the next few days before we #1 reimage the Roborio, 2 configure the radio back to home use.
Remember all work before configuring for a the event.