We have a interesting problem with radio. Sometimes we can connect the radio sometimes cant.
Firewall is off.
We have already reset the IPCONFIG from cmd.
Yes,we have the same problem.Can anyone help?
Sounds like the NIO may be jamming your wifi connections in Turkey. … Just kidding.
Is the Driver Station connecting to the Radio?
Is the Driver Station not connecting to the RoboRio after connecting to the Radio?
Can you connect the Driver Station to the RoboRio when the Driver Station is connected via the Ethernet Connection (hard wire)?
Do you have the most recent Firmware updates for the Radio and the RoboRio?
Are you using the most recent version for the Driver Station?
Some connection problems are related to mDNS. I suggest giving your devices a fixed IP address. We use the following:
Radio: 10.TE.AM.1
RoboRio: 10.TE.AM.2
Driver Station: 10.TE.AM.5
If the DS is having problems connecting via wifi to the Radio, then check for other wifi devices using the same channel.
Yes,we can connect the Driver Station to the RoboRio with ethernet cable and we have the most recent version .But anyway The Driver Station isn’connecting to the RoboRio after we connecting to the Radio.
When it doesn’t connect via wireless, try Disable/Enable the wireless NIC.
Control Panel->Network and Sharing Center->Change adapter settings
Right-click on Wi-Fi and choose Disable
Wait a few moments
Right-click on Wi-Fi and choose Enable
Do you use this PC to connect to other non-robot networks, e.g., Internet, or is it dedicated to Driver Station use only?
P.S.
The latest radio firmware version is from February 14
We (team 4014) don’t have a solution but have the same problem. We’ve never been able to use wireless this 2017 season, and are getting concerned that the problem might still be with us at competition.
We can connect with ethernet and everything works. But we’ve never been able to ping roboRIO-4014-FRC.local or frc-robot.local from Windows.
We can ping 10.40.41.1
We can ping roboRIO-4014-FRC.local from a Mac. So it’s a problem on the Windows box, not the wireless hub or roboRIO.
We’ve disabled ‘public’, ‘private’ and ‘domain’ profiles in Windows firewall. One PC has McAfee and we disabled that too.
We’ve run ipconfig /flushdns
The driver station is a fresh install.
Another thread says to check if the mDNS service is running. We need to try that later today when we’re at our makers space. https://www.chiefdelphi.com/forums/showthread.php?t=154684&highlight=mDNS
Someone on yet another thread said they’d got it to work by installing iTunes. We tried that too but it didn’t work.
We have yet to try using static IP addresses. According to the FRC documentation, static IPs can be used at competition. So this may be our final option.
https://wpilib.screenstepslive.com/s/4485/m/24193/l/319135?data-resolve-url=true&data-manual-id=24193
If everything works tethered (Ethernet cables), and the DS can connect to the Radio via Wifi, but the DS won’t connect to the RoboRio via Wifi, then my first guess is that it is an mDNS problem.
The easy solution to try is assigning static IP address to the RoboRio and DS.
Just an update …
We checked, and our mDNS service is running.
Then for some reason DNS started working. We’d lose DNS whenever we restarted the robot, though. Rebooting the PC, or turning the PC’s wifi network adaptor off and on would get DNS back. … Until it didn’t.
So we probably need to use static IPs.