IP Keeps Changing

[Haragorn]

Our Classmate was having trouble connecting to our robot. So, we checked a few things, and found out that the Classmate's IP Address had changed to 10.8.88.5, instead of 10.8.88.10. We changed it back, logged out, logged into our Driver account, and couldn't connect again. When we logged back into our Developer Account and found that the IP Address had changed back to .5. We tried setting the address to automatic instead of manual. We logged out and back in, and checked it out. It had changed to0 manual settings, with 10.8.88.5 as the address. We were able to connect through LabVIEW, after changing the IP to automatic. Any ideas why this might be happening, or how to fix it?

[Racer26]

...Its happening because the Classmate's IP is SUPPOSED to be 10.x.y.5. This is where the cRIO is going to try to communicate to the Driver's Station, is by sending packets to 10.x.y.5

Why do you want it to be .10?

[jhersh]

Originally Posted by Haragorn

Our Classmate was having trouble connecting to our robot. So, we checked a few things, and found out that the Classmate's IP Address had changed to 10.8.88.5, instead of 10.8.88.10. We changed it back, logged out, logged into our Driver account, and couldn't connect again. When we logged back into our Developer Account and found that the IP Address had changed back to .5. We tried setting the address to automatic instead of manual. We logged out and back in, and checked it out. It had changed to0 manual settings, with 10.8.88.5 as the address. We were able to connect through LabVIEW, after changing the IP to automatic. Any ideas why this might be happening, or how to fix it?

The driver station application sets your IP address to the correct one for you automatically so that you don't have to. It's not a problem that needs fixing... it's a feature.

[jahuber]

Originally Posted by jhersh

The driver station application sets your IP address to the correct one for you automatically so that you don't have to. It's not a problem that needs fixing... it's a feature.

Why does 2.10.3 step 8.a (pg 52) instruct to set the IP for the computer to be used to end in 10?

While I agree the manual 2.6 step 6 (pg 31) does state that the Classmate IP should end in 6, I find the Control Systems Manual confusing on this point, as the step-by step instructions for 2.10.3 step 8.a (pg 52) instructs to set the IP for the computer to be used to end in 10, which one assumes to be the drivers station (classmate) since all of the preceding steps are about setting wireless communications with the robot. For a rookie team having connection problems and trying to follow instructions to the letter, a very unfortunate diversion from discovering the "real" problem.

[jhersh]

Originally Posted by jahuber

Why does 2.10.3 step 8.a (pg 52) instruct to set the IP for the computer to be used to end in 10?

While I agree the manual 2.6 step 6 (pg 31) does state that the Classmate IP should end in 6, I find the Control Systems Manual confusing on this point, as the step-by step instructions for 2.10.3 step 8.a (pg 52) instructs to set the IP for the computer to be used to end in 10, which one assumes to be the drivers station (classmate) since all of the preceding steps are about setting wireless communications with the robot. For a rookie team having connection problems and trying to follow instructions to the letter, a very unfortunate diversion from discovering the "real" problem.

If the documentation says to set the classmate to .6, then it is wrong, plain and simple. The selection of .10 is just some number that won't conflict, assuming it's not a computer that it already on the subnet (such as the classmate). The real problem appears to be that the documentation about this topic was not updated from last year very successfully.

[Racer26]

The classmate's IP is supposed to be 10.x.y.5. This is because it is the driverstation, and the driverstation MUST be at 10.x.y.5 for the cRIO to talk to it. The control system manual tells you to set up the router to hand out DHCP addresses starting at 10.x.y.10, and the first development PC (assuming you're not using the classmate for development) would get 10.x.y.10 from the router. I suspect that this is what the manual meant for you to do. It was however, a bit ambiguous in how it explained it.

[jhersh]

Originally Posted by 1075guy

This is because it is the driverstation, and the driverstation MUST be at 10.x.y.5 for the cRIO to talk to it.

It is actually so that the FMS can talk to the DS, not so that the DS can talk to the cRIO.