cannot ping roborio

[Mark McLeod]

So it's just the wireless that's broken.

I'd check your PC's wireless adapter settings to see if they are the same as the PC Ethernet adapter settings.

You can login to the radio and check those settings as well, or just run it through the radio kiosk one more time to verify that the right team number was used.

[MikePerreman]

so, the settings apear to be equivalent, in network and sharing > change adapter settings (Ethernet {qualcomm atheros}) (wifi {ralink RT3090 802.11n wifi adapter})

what else is there to do?

[Mark McLeod]

Connect via wireless, then check to see what IP your PC got assigned.
cmd prompt> ipconfig /all
also
> arp -a

[MikePerreman]

ok, my ip is 10.2.47.163 on wireless

[Mark McLeod]

What is your roboRIO's IP?

Can you ping the roboRIO IP?

[MikePerreman]

i dont quite know what you are asking, here is a gDoc link to cmd's output
https://drive.google.com/open?id=1CE...uE8AklELx7 Q4

[MikePerreman]

ok, lab's closing for the night, i wont have any new information untill 4:00pm (eastern) tomorrow. goodnight all.

[Mark McLeod]

Do you have another robot radio to verify with?
It can actually be just about any AP you might have lying around, and doesn't need to be setup with the radio kiosk.
It also doesn't need to be mounted on the robot, just use a wall power supply for it and connect the Ethernet to the roboRIO.

Double check that the radio is connected to 12v power from the VRM(if it's the 2016 Open Mesh radio). Lower power will affect wireless operation first.
Check to see that you have a fresh robot battery, too.

You can also check the status lights on the radio. It should have a green wireless light, a power light and at least one Ethernet light on.
Then check the roboRIO Ethernet port to see if it shows both solid green (hardware) and blinking yellow(communications) lights on.

[MikePerreman]

i dont have another radio to varified with, the lights on the ethernet of the rio are blinking, all of the lights on the radio are as they should, other computers have no problem deploying code, and connecting with the driver station. i, however, still see that "destination host unreachable" when pinging roboRIO-247_FRC.local

[Mark McLeod]

According to the arp -a result you posted yesterday, at the time your laptop was connected to the rio via USB-A/B (172.22.11.2) just fine, but your wireless could only see as far as the radio (10.2.47.129). The rio would have shown up as 10.2.47.90 or something similar in that part of the listing.
In addition, your radio should also have shown up at address 10.2.47.1, which it did not.
That means the DNS address won't work under any circumstances, because there is no IP address to associate with it.
When you connect, do it with just one active connection (wireless or USB) rather than both active at the same time, and disable the other via the Network Connections Control Panel.

Try an arp -a after connecting one of your other working laptops wirelessly to see what it should look like.

I'd suggest connecting via USB again and using the web browser to check what Ethernet address the radio DHCP has given the rio.
It'll be the non-172.22.11.2 address.
Then try pinging that IP address (it'll try to go through the wireless connection if it is active).

[MikePerreman]

well, new development if i connect over ethernet, then connect over wifi, all is well, untill, i connect to a different wifi, then back to the bot, it wont re-connect to the bot.

[Mark McLeod]

When it fails to connect to the roboRIO, to see if it helps you might try:
cmd prompt> ipconfig /renew

Your PC may be retaining the previous DHCP address it was given.