View Single Post
  #18   Spotlight this post!  
Unread 13-01-2015, 12:26
jtrv's Avatar
jtrv jtrv is offline
github.com/jhtervay
AKA: Justin
FRC #2791 (Shaker Robotics)
Team Role: College Student
 
Join Date: Jan 2013
Rookie Year: 2012
Location: Latham, NY
Posts: 148
jtrv is a name known to alljtrv is a name known to alljtrv is a name known to alljtrv is a name known to alljtrv is a name known to alljtrv is a name known to all
Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM

We spent multiple hours trying to get ours to work. Here's what we did:

Plug in router via ethernet, make sure RIO is unplugged.
Make sure your computer IP is set to auto-resolve IPs.
Launch config tool, use it.
Go to your router settings. Ours is 10.27.91.1, for example (team 2791).
Enable DHCP settings. I'm not 100% sure where it is. But you will find a non-marked checkbox with fields under it.
Make default IP range 10.TE.AM.20 to 10.TE.AM.199, subnet 255.255.255.0, default gateway 10.TE.AM.1.
Save changes.
Plug in roboRIO to router via ethernet. Unplug ethernet from computer.
Check to see if you can reach roboRIO-TEAM.local on browser (make sure you have Microsoft Silverlight installed). If not, try to configure via USB.
Find the IP under network settings. It should be 172.x.x.x or 10.TE.AM.x.
If it is 10.TE.AM.X, restart computer and robot. Comms should work.
If it is 172.x.x.x, then go to your router settings and check if the router detects the RIO. Ours was found on DHCP at 10.27.91.100, our computer 10.27.91.20.
If its not found, start over until it works and make sure to hold the reset button on the router.

It's a major pain because not many of us know much about networking, but we got it working.

If you can ping the RIO and it is 10.TE.AM.X, but driver station says no comms, restart computer and robot. It then worked for us.
__________________
2791 (2012-2017)