Can't communicate with cRIO or d-link on power on
 

Hello,

Our team has been having this problem the entire season and now we're realizing it's going to be a problem come competition time.

When the robot boots up the WIFI comes on, and we can connect but we are having a strange problem. If we ping the router at 10.22.0.1 and the cRIO at 10.22.0.2 we get no response. If we pull the ethernet cable out of the cRIO the router responds to pings, and if we plug the cable back in we get coms with the cRIO and it stays connected till we cut the power again.

This is fairly consistent, maybe about 5% of the time this problem doesn't happen.

Things we have tried:

Set laptop to static IP 10.22.0.5 + 0.6 + 0.9 with subnets 255.0.0.0 + 255.255.255.0
Reconfigured router using bridge tool and manually
updated firmware on router
Re-flashed crio, tried different team numbers like 10.22.1.2
used a different router, tried a different cRIO

info:
Java
Windows 7
Old cRIO's

I've been debugging this thing for the entire day and I can't figure it out. Any help would be great.

Re: Can't communicate with cRIO or d-link on power on
 

Those symptoms don't match anything I can think of. Is the D-Link set to AP mode?

Re: Can't communicate with cRIO or d-link on power on
 

Try connecting directly to the cRIO and see if it's what is causing the issues. The best thing I can think of is to make sure that all of your utilities are up to date. NI-MAX is also useful in monitoring the cRIO and resetting it.

I don't know much else since I'm a rookie, but hopefully it will help. :)

Re: Can't communicate with cRIO or d-link on power on
 

On your driver station computer, can you compare the results of

arp -a

When are connected and not connected?

What output do you get from ping when it is not working?

Re: Can't communicate with cRIO or d-link on power on
 

I'd also be interested in what ARP returns. I've occasionally seen the bridge fail to forward packets to the cRIO. If you hand-configured the router, is MAC address cloning on or off? You may want to run the radio config utility again and see if that changes the symptoms.

Also, is the DLink in AP mode or bridge?

Greg McKaskle

Re: Can't communicate with cRIO or d-link on power on
 

We will try out that command thanks. Ping outputs request timeout when the connection isn't working.

The router is in AP mode as described in the instructions at http://wpilib.screenstepslive.com/s/...o-for-home-use

I'm not sure if MAC address cloning is on or off as I can't find that setting anywhere.

We have retried programming the router with the tool but the symptoms are exactly the same, and we had to downgrade the firmware on the router because the tool doesn't work with the newest firmware.

Re: Can't communicate with cRIO or d-link on power on
 

What is the "newest firmware"? I wasn't aware that any of the competition-legal D-Link routers came with anything other than the one they had last year.

Re: Can't communicate with cRIO or d-link on power on
 

I downloaded it from this site when I was experiencing the issues. http://support.dlink.com/ProductInfo.aspx?m=DAP-1522

It didn't fix anything though.

Re: Can't communicate with cRIO or d-link on power on
 

What was the output of the arp command?

Re: Can't communicate with cRIO or d-link on power on
 

I believe that your ip address should be 10.22.00.xxx. I don't know if the number of zeros matter, but otherwise you would have the same ip as team 220.

This would cause you to not be able to communicate with the cRIO because it is setting its own ip to 10.22.00.2. The driver station on 10.22.0.2 is on a different subnet and wouldn't be able to communicate.

Re: Can't communicate with cRIO or d-link on power on
 

Number of zeros doesn't matter. Team 2200 is 10.22.0.X and team 220 is 10.2.20.x

Re: Can't communicate with cRIO or d-link on power on
 

Yep. This is because of some quirks in the numbering that FIRST chose to adopt and the way that IP addressing works.

Two digit teams (ie. 71) are 10.0.71.x
Three digit teams (ie. 254) are 10.2.54.x
Three digit teams where the middle digit is a zero (ie. 701) are 10.7.1.x (note the distinction from 71's IP block)
Four digit teams (ie. 4343) are 10.43.43.x
Four digit teams where the tens digit is a zero (ie. 1404) are 10.14.4.x

similarly:
254 = 10.2.54.x
2054 = 10.20.54.x
2504 = 10.25.4.x

Re: Can't communicate with cRIO or d-link on power on
 

Hello,

The arp command returned a list of devices, the IP's and MAC addresses were visible for the cRIO, Router and Laptop. Interestingly enough the router's type showed invalid which changed to dynamic when the ethernet cable from the cRIO was removed and reinserted. The laptop and cRIO are listed as static, no device shared the same MAC address.

Interestingly enough, in our troubleshooting we tried to format the cRIO with the imaging tool which failed multiple times and we couldn't get it to work for hours until we removed power from the digital and analog sidecars, then the format worked instantly. Afterwords we could not repeat our problem at all, every cold boot resulted in an instant connection. We tested powering on again multiple times with different side carts and modules and couldn't recreate the problem. The problem returned immediately after uploading our robot code to the cRIO, even if we just tried the simple robot template the problem continued.

Competition is in a few days and I am desperate for an answer of any kind, so the help is appreciated.

Thanks

Re: Can't communicate with cRIO or d-link on power on
 

When the pings stop responding try this test.

Leaving the robot power alone, push the reset button on the front of the cRIO.
It'll take about 45 seconds to reboot and start your user code.
See if the pings are reconnected afterwards.

Do you have another DLink you can swap in temporarily for another test?

Re: Can't communicate with cRIO or d-link on power on
 

Yes we used to do the soft reset on the cRIO to fix the problem every time, we just found that unplugging the ethernet cable and reinserting it took less time.

We did swap the dlink router with another and had the same issues, we have also tried swapping cRIOs