Robot Tethering Issues

[Redstone]

This past weekend we went to the las vegas regional and had no problem connecting the robot the the feild management system. Whenever I try to tether the classmate to the Crio it doesn't find a connection. At first we thought it was a bad cable but after trying two other cables it still didn't work. Any ideas on what the issue could be?

[RyanN]

Originally Posted by Redstone

This past weekend we went to the las vegas regional and had no problem connecting the robot the the feild management system. Whenever I try to tether the classmate to the Crio it doesn't find a connection. At first we thought it was a bad cable but after trying two other cables it still didn't work. Any ideas on what the issue could be?

You need to use a crossover cable when going directly from the Classmate to the cRIO. I believe they were all yellow in this year's KOP.

Why not just connect the Classmate to the Dlink?

[Redstone]

Originally Posted by RyanN

You need to use a crossover cable when going directly from the Classmate to the cRIO. I believe they were all yellow in this year's KOP.

Why not just connect the Classmate to the Dlink?

We also tried connected it to the dlink and we still didn't get a connection. This is a weird issue because we didn't have this problem during our first regional.

[Botwoon]

Originally Posted by Redstone

We also tried connected it to the dlink and we still didn't get a connection. This is a weird issue because we didn't have this problem during our first regional.

Sounds like an issue with your IP. Go here and follow "How to configure your C-RIO", that should fix it. Also ensure that your driver station software and utilities are up-to-date.

[DominickC]

I had this issue early in the season on a non-classmate computer. It turns out that the Ethernet port was disabled on the computer. Ensure that the port is, in fact, enabled.

Dom

[Greg McKaskle]

If you are running the driver station, it has a Diagnostics page to help determine what is failing. The second column of LEDs starts with the equivalent of a link light. If off, it indicates that a cable is missing/bad, or the NIC is disabled. If it is good, the next light moves one step closer to the robot, and another, etc. The first LED is the result of an ipconfig, and the others are just pings of the expected IP addresses.

You also shouldn't need a crossover cable unless neither device implements auto-sense. Almost all laptops still running will. If they implement gig-E, it is almost guaranteed. The cRIO and camera do not, and that is the connections that requires a crossover cable.

Greg McKaskle

[jerry w]

We found that windows gets confused on which LAN port to use. If you are tethered, make sure you enable the wired LAN and turn off the wireless LAN.
the driver station will then activate the correct port. (sometimes)
You may still need to manually adjust the IP address if the wireless claimed the default earlier. Windows seems to remember that old IP assignment even when the port is disabled.

[mdrouillard]

Not likely the issue you were having , but during build season we actually had 1 bad port on our dlink. Port 2 was simply bad. So, Crio in port 1, camera into port 3, and laptop tethered on port 4 when needed. So, if none of the ideas above work, check either the port that the crio is connected, or your laptop on the dlink and make sure you have a link light on the dlink.

Keep in mind a link light only tells you that that device sees the other device. it does NOT tell you that the other device sees you. To make sure you have bi-directional communication, you need TWO link lights, one on each device facing every other connected device.





md

[Mike AA]

Don't forget that if you are trying to connect via wireless your bridge password needs to be reset and also check the switch on the back is set to access point mode when not at competition.

The manual here, page 29 explains it.

[Redstone]

Originally Posted by Mike AA

Don't forget that if you are trying to connect via wireless your bridge password needs to be reset and also check the switch on the back is set to access point mode when not at competition.

The manual here, page 29 explains it.

I forgot to mention that I can't do anything about this until the championship because the robot is still in it's Bag

[rwood359]

Originally Posted by Redstone

I forgot to mention that I can't do anything about this until the championship because the robot is still in it's Bag

At CMP, try this as soon as you can. If you can't get it working, look for a volunteer in a orange ball cap. That is the Control Systems Advisor. The CSA is tasked with helping any team that needs it.