roboRIO no COMM

[michaelwm]

After just some normal programming on our main roboRIO, it can no longer connect to any PC. The thing works fine, we're reading voltages from our DIO and PWM ports, but no matter what connection method we use, the roboRIO's COMM light doesn't turn on, including:


USB B
Ethernet
Router


We have tried isolating just the roboRIO, a PDP, and a battery, but still, it cannot find anything.

What can we do?

[Mark McLeod]

Is your Driver Station app running and connected?
Is your team # set in the App?

[michaelwm]

Is your Driver Station app running and connected?
Is your team # set in the App?

Yes, when the roboRIO was working, we set up our team number. My driver station is also running.

The error is that the roboRIO's COMM light won't turn on, whether we connect with USB B, Ethernet, or Router. We have no way to connect to the roboRIO.

[notmattlythgoe]

Yes, when the roboRIO was working, we set up our team number. My driver station is also running.

The error is that the roboRIO's COMM light won't turn on, whether we connect with USB B, Ethernet, or Router. We have no way to connect to the roboRIO.

I'm assuming you are referring to the actual physical light on the roboRIO itself.

[michaelwm]

I'm assuming you are referring to the actual physical light on the roboRIO itself.

Yes. We have no way of communicating with the roboRIO through any connection, and therefore the physical COMM light won't turn on.

[Mark McLeod]

The roboRIO Comm light only indicates that the roboRIO is or isn't talking to the Driver Station app.
So if it is off, then the Driver Station isn't communicating with the roboRIO.


Comm
Off - No Communication
Red Solid - Communication with DS, but no user code
Red Blinking - E-stop
Green Solid - Good communication with DS

If your Driver Station is operating normally, then your Java code running on the roboRIO may have failed.
You might try downloading an unadulterated default program.

[notmattlythgoe]

Have you tried accessing the roboRIO through the webapp?

[michaelwm]

Have you tried accessing the roboRIO through the webapp?

Yes, ofcourse, but like I said, we simply are not connected to the roboRIO, no matter what method we use. Driver Station has no connection, the imaging tool has no connection, the IP of the roboRIO shows up dead, nothing can connect.

[Mark McLeod]

When your DLink is connected vis Ethernet to the roboRIO, are the green and yellow status lights on the roboRIO Ethernet port lit up?
That would indicate network traffic.

On your PC connected via USB cable to the roboRIO, can you ping the address 172.22.11.2 ?

On the Driver Station Diagnostics tab are any of the ping lights green?

[michaelwm]

When your DLink is connected vis Ethernet to the roboRIO, are the green and yellow status lights on the roboRIO Ethernet port lit up?
That would indicate network traffic.

On your PC connected via USB cable to the roboRIO, can you ping the address 172.22.11.2 ?

On the Driver Station Diagnostics tab are any of the ping lights green?

Yes, when using ethernet, the lights on the ethernet port are both lit up.

There is 100% loss on the ping.

The driver station has no connection to the roboRIO.

[notmattlythgoe]

I know you were asking about modifications of the rio in this (http://www.chiefdelphi.com/forums/showthread.php?threadid=133573) thread. Did you end up doing anything?

[Mark McLeod]

Then it sounds like the roboRIO is operating and communicating with the DLink. So it might be an incompatibility between the roboRIO and PC IP addresses.

So among things that could be wrong:
Ethernet: The DLink isn't serving DHCP addresses, and/or the roboRIO/PC have incompatible IP addresses/netmasks. You can check this on the PC using ipconfig or checking what the PC network adaptor's assigned IP address is.
USB: the PC may not have the USB network running, i.e., FRC Update package not installed, crashed, etc.
Both: the PC mDNS resolver may have crashed. Rebooting usually solves that, but you can check in the Task Manager to see if the service is running.Since apparently you say that the Driver Station Diagnostic ping's aren't seeing the DLink, then the problem is between the PC and the DLink.
Most likely the PC has issues, since it should see something.

[michaelwm]

I know you were asking about modifications of the rio in this (http://www.chiefdelphi.com/forums/showthread.php?threadid=133573) thread. Did you end up doing anything?

No, that's something for when our extra roboRIO comes in.

[michaelwm]

Ok, I got ethernet connection working after some tinkering, however, USB B no longer works. I checked device manager, and the National Instrument USBLAN driver is gone. What's the easiest way to reinstall the USBLAN driver?

[Mark McLeod]

Probably uninstall if it's still listed among the PC programs, then rerun the FRC Update package.

[ozrien]

After you rule out the obvious stuff, maybe try disabling windows firewall?

[Loponop]

Ok, I got ethernet connection working after some tinkering, however, USB B no longer works. I checked device manager, and the National Instrument USBLAN driver is gone. What's the easiest way to reinstall the USBLAN driver?

So what exactly did you do to get connected back to the RIO? My team has been having this same connection problem

[SyrusVir]

Ok, I got ethernet connection working after some tinkering, however, USB B no longer works. I checked device manager, and the National Instrument USBLAN driver is gone. What's the easiest way to reinstall the USBLAN driver?

What did you tinker with to fix it? Our team has been having the same problem this year.