OM5P-AN and OM5P-AC Config Problems

[wywyit]

We have our new OM5P-AC radio that we are trying to configure for the 2017 season. However, once I load firmware and configure it using the FRC Radio Config Utility (version 17.2), I am able to communicate with the radio, but not the roboRIO. I have followed WPI's instructions and am adhering to R63 (connect roboRIO to 18-24v POE). I have all network adapters except my PC's Ethernet port disabled when configuring the router.

The router appears to flash firmware and configure fine, and I can see and connect to the wireless network with our driver station. However, after I connect to the wireless network I cannot communicate with the roboRIO. The light for "Robot Radio" lights up in the diagnostics section of the driver station, but the roboRIO never makes connection. However, when connected through USB to the roboRIO, I can communicate with it, deploy LabVIEW code, and "drive" the control system, so I believe I have the roboRIO set up properly.

I tried the same process on an OM5P-AN that I know worked last season, and got the same result. Any suggestions?

[Mark McLeod]

Just some things to try:

- PC firewall/anti-virus turned off
- Keep the other network connections disabled for your testing
- Check the PC IP assignment it got from the radio & compare it to the Ethernet IP on the roboRIO (check it via the USB connection)
- See if you can ping the roboRIO's assigned Ethernet address directly

[meowguy123]

We're having the same problem with our OM5P-AC where the radio connects to the computer but is unable to communicate with the roboRIO although the Robot Radio light is on in diagnostics. We've tried all the solutions listed above, anyone else have a solution?

[bobbysq]

Have you tried using version 2 of the radio configuration tool to reflash and reconfigure the router?

[wywyit]

(Sorry for the late reply. I was sick and then had finals.)

PC firewall is off. I keep antivirus at a minimum and that's Defender, which hasn't ever interfered before. I have all network adapters disabled except for the one I am using at that moment (Ethernet, Wi-Fi, or USB to the roboRIO).

My PC is getting an IP of 10.31.2.72 when I am connected to the OM5P-AC over Wi-Fi. The roboRIO shows that it has an IP of 10.31.2.76. The OM5P-AC has 10.31.2.1. I can ping the roboRIO and use the web dashboard over Wi-Fi if I use the IP address, however I can't get anything when I try to ping or go to roborio-3102-frc.local (the hostname).

When I open the driver station, it still only registers the radio. If I use an OM5P-AN, I experience the same problem.

[Mark McLeod]

Does the Driver Station show any hits on the Setup tab under the arrow by the team number entry?

Try typing the IP address directly into the team number field.

Try typing roborio-3102-frc.lan directly into the team number field.

You can try pinging roborio-3102-frc.lan as well.

[wywyit]

I got the driver station to recognize the roboRIO when I typed the IP address (for some reason it changed to 10.31.2.75 since my last post) into the Team Number field.

For consistency, nothing shows up under the Team Number drop down, and typing roborio-3102-frc.lan into the team number field doesn't do anything. Pinging roborio-3102-frc.lan gives "Ping request could not find host."

So now that wireless communications sort-of work, why would it not be finding the right IP by itself? A lot of thanks for the help so far.

[Mark McLeod]

mDNS/DNS is not resolving the address.
So try stopping and restarting the service.

Look at Task Manager -> Services
and scroll down looking for nimDNSResponder to check that it is running.

- Right-click on nimDNSResponder and choose Stop Service
- Wait for it to stop
- Right-click on nimDNSResponder and choose Start Service


After it's Running again, try pinging both roborio-3102-frc.lan and .local
to see if that helped.
If that doesn't help it means something on the PC is blocking the service. That would be a firewall, anti-virus or other 3rd party vendor security.
Also when a network is first detected and Windows asks if it is a Home, Work, or Public network, always choose Home or Private network, otherwise, restrictions are applied that interfere with FRC operations.

As a final resort you can try installing iTunes on the PC. iTunes installs it's own mDNS service and whatever is doing the blocking probably already has a built-in exemption for iTunes and would allow it to operate normally.

P.S.
I'm traveling, so I'll be out of touch for a bit.
Someone else may have more suggestions, too.

P.P.S.
I added a few edits adding some more information.

[Snake50]

I had a issue with downloading the firmware and configuring the radio bridge. The laptop that I used last year for programming the radios worked. Here are the differences to the operating system and Java installed on the laptops.

The radios that I programmed are models OM5P-AN and OMP5-AC.


This laptop WORKED!!!!:
Windows 10 Pro
Java 7 Update 67
Java 8 Update 25


This laptop is DID NOT work:
Windows 7 Pro
Java 8 Update 45
Java 8 Update 60
Java 8 Update 91
Java 8 Update 91 (64-bit)


I hope this helps resolve your radio issue. Good Luck!

[rwood359]

We are having this problem on 2 of 4 laptops connected to the same robot.
On the two that are failing, the Robot Radio is the only green on the diagnostic page. We can ping 10.3.59.1 on all four computers..
Pinging 10.3.59.99 (what happened to good old robot is always .2?) gets unreachable message.
Pinging either logical address gets host not found message.
We tried the four different values for team number. The Robot Radio stays Green for either IP address and goes out on either logical address.
I tried installing iTunes one one computer with no success. The big problem is that the two computers that fail are the Driver Station computer and Team Development computer.
Task Manager will not stop service. Other processes are using it.
All four computers are running Win 10, installed last summer before the free period ended, but after all competition and demonstrations.
We reloaded last year's radio firmware and configuration on the same radio and have the same results for all four computers.
I have gone through as many configuration settings as I can think of. These pictures show some differences between a working and a failing computer. The failing one is the one that has 10.3.59.1 as the DNS server.
Any suggestions would be greatly appreciated.

P.S.
Should we be able to fall back to static IPs using the old IP structure?

[Mark McLeod]

Ping roborio-359-frc.frc-robot.local on the computers that aren't working.
If that works, then type roborio-359-frc.frc-robot.local into the team number field on the Driver Station to see if it connects.

Yes, you can also fall back to static IPs and that should work fine.

[rwood359]

Thanks for the quick response.

In the vain that this is going to drive me crazy, I used this computer to connect to the internet to post this, and now after reconnecting to the robot, and restarting windows when that failed, this computer will not talk through the radio.
The long logical address won't work from the one that still works or one of the failing ones.