IP Address Help

[Steve Ketron]

We are experience a windows system error, "There is an IP conflict with another system on the network", has anybody else encounter this, how can we check all of our IP addresses on the board?

[Bongle]

Originally Posted by Steve Ketron

We are experience a windows system error, "There is an IP conflict with another system on the network", has anybody else encounter this, how can we check all of our IP addresses on the board?

You probably set your static IP to that of another device. If you've got everything set up properly, the laptop should be 10.xx.yy.6, where xx is the first two digits of your team number and yy is the 2nd two digits. So in your case, 10.15.28.6.

If you look on page 6 of this, there's a table indicating all the IP addresses.

Now, if you accidentily set some other device to be 10.xx.yy.6, just change your laptop to something unused like 10.xx.yy.250, then connect to all your devices and verify they are correct.

To verify your gaming bridge is correct: browse to http://10.15.28.1, make sure the website is that of the gaming bridge
To verify your router is correct: browse to http://10.15.28.4
To verify your cRio is correct: start->run->cmd, then "ping 10.15.28.2". If you flashed it correctly, you should get a response.
To verify your driver station is correct: start->run->cmd, then "ping 10.15.28.5". If you flashed it correctly, you should get a response.
To verify your PC is correct, go to your network settings and make sure it is set to a static ip of 10.15.28.6, with a subnet mask of 255.0.0.0.

[Steve Ketron]

We set all the IP adresses as instructed in the FIRST manual. We would like to be able to view all the IP adresses while they are connected to see where the conflict is. I am most concerned about the drive station and the cRIO.

[Bongle]

Originally Posted by Steve Ketron

We set all the IP adresses as instructed in the FIRST manual. We would like to be able to view all the IP adresses while they are connected to see where the conflict is. I am most concerned about the drive station and the cRIO.

That message indicates that your PC conflicts with another device. So first, you need to know what your PC's IP address is set to.

Do start->run->cmd. Type 'ipconfig' (minus quotes). Write that number down (it should be 10.15.28.6, or else your PC's IP address was wrong). Change your PC's IP address to something else that won't have a conflict. Then browse to the IP address your PC just had to see what device is occupying it.

To check all the devices, try the verification steps I edited into my first post. Keep in mind that the DS and cRio's IP addresses are hardcoded when you set your team number, so as long as you can ping them at the IP where they are supposed to be, you can be fairly sure that they are on the correct IPs.

[Mark McLeod]

Originally Posted by Steve Ketron

We set all the IP adresses as instructed in the FIRST manual. We would like to be able to view all the IP adresses while they are connected to see where the conflict is. I am most concerned about the drive station and the cRIO.

That's what Pinger does: http://www.chiefdelphi.com/media/papers/2177

[Joe Ross]

Originally Posted by Mark McLeod

That's what Pinger does: http://www.chiefdelphi.com/media/papers/2177

Unfortunately, pinger won't work in this case, as the computer it runs on needs to have a valid network address. Since there is a conflict, you won't have any networking.

It also won't tell you what is at each address, just that something is at the address that each device is supposed to be at.

[Jon Stratis]

Network issues abound... and they can be pretty frustrating. Having dealt with a lot of networking in the past, i can certainly give some tips.

First, a little networking background. Every device on a network has an IP - basically, an address that's composed of 4 parts, separated by a period. Each part contains a number 0-255. On a single network (a home network, one you set up for your team, etc) the first, second, and third numbers are going to be the same between all devices. So setting up a network like the instructions say means everything will be 10.tt.tt.xxx, where tttt is your team number. For the Robettes, it's 10.21.77.xxx.

Now, most of the time, computers on a network will get their ID address dynamically from a DHCP server (something that is included in every router). That means you plug it in, it automagically figures out a legal IP, and sets itself. you're done! Unfortunately, a DHCP server most often assigns IP's starting at the low end of the scale - it'll start with 1, then 2, then 3, etc. With FIRST having chosen to give all the devices low numbered IP addresses, conflicts like this are bound to happen - other laptops and wireless devices you connect to your network can get assigned those IP's before you have a chance to connect the proper device to them!

Now with a FIRST network, you want to set static (not dynamic) IP addresses for certain devices, as dictated by page 6 of http://www.usfirst.org/uploadedFiles...ation-0-5c.pdf

for the router, you need to visit it's webpage, which is simply http:// followed by it's IP address. If your computer obtains it's IP dynamically, the first three numbers will be the same for the router, while the last one is usually a 1, unless you've already changed it. You can browse around on that, and finding where to set a static IP is pretty straight forward.

Setting the static IP address for different devices is done in different ways. follow these instructions for you computer, based on your OS: http://portforward.com/networking/staticip.htm

For problems with your computer connecting to a specific IP, i would highly recommend setting it to a dynamic IP (if you follow the link above, basically select "obtain IP address automatically" instead of specifying one. do the same for the DNS servers). That will at least allow you to get on the network, although your IP address won't be what you want. From there, you can log into the router, and most routers have a status page that will show all connected clients and their IP's. If you don't know what's what, the easiest way is to disconnect items and see what disappears.

The camera is set up in a very similar manor to the router - you visit it's webpage and can change the settings there. Unfortunately, this is where things get tricky - the instructions tell you that the camera should be 192.168.0.90, while your computer is 10.tt.tt.6. Those addresses won't talk to each other, even if they're plugged in directly to each other. You'll have to change the computers address to 192.168.0.xx in order to get them to talk over the orange cable. For our team, we found it simplest to connect the computer to the router over the wireless (so that adapter has an IP of 10.21.77.6), and the camera directly (with that adapter having an IP of 192.168.0.3). This ensures that the camera is always set to the IP it needs to be set to.

Our team is going to be getting everything else properly configured tomorrow, but the best advice is to follow the instructions for all of that.


When dealing with networks and IP issues, expect problems. Also don't expect to be able to solve them easily right off the bat. Last night, we were having problems with the camera IP and getting everything talking properly - 1 mentor and 2 students were ready to throw the computer out the window, because they didn't have much experience with it all. When they called me over, i could solve the problems for them, but that's only because i've been setting up and administrating networks of various sizes for 7+ years (there are currently 8 computers in my house, all running different OS's.... yikes!). There is a very steep learning curve when dealing with networks, especially on windows - at least, i've always found windows to be the most confusing platform.

[roboengr]

Warning this must be said. This is in respects to Cisco device setup of the control system.

when following First's documents on seting up the wireless devices. First has you set up the gaming adaptor... When saving the setting of the new IP address to the game adaptor(robot unit), you will not be able to see it any more. DO not be alarmed This is due to the fact that the DHCP of the 4 port router has a subnet mask and an ip address in another class then the game adaptor. Set the ip address of the Router then renew the computers ehternet to get a new ip address. when this is done you can see all the web pages again. Hope this helps.

*****
Reason is the subnet mask of the default settings on the router is set as such the 10.xx.yy.zz subnet is not visable to the pc anymore through the router.

******
Alernative is to multi-home the PC's network adaptor. To do this set a static ip address to 192.168.1.240. then press advance and add another ip address of 10.xx.yy.10 and this will allow a work around to see all the devices with out messing with the subnet mask.

Use a command prompt <start><run> type cmd. use the command ping /? to see if the device is at the address you expect. this is a good troubleshooting tool! Explorer can fool you into falsely showing a cached page. Vista can give trouble with firewalls turned on.

Good luck!

[roboengr]

When will first tell us to turn on the security for the wireless network devices? I am advising my team to turn it on if it will function.

I hope we have profesionalism and no dishonest people. I know setting up the security will cause some initial setup and troubleshooting errors for a lot of the teams not understanding networking well.

The ssid will not prevent anything but make wrong do'ers know whos network it is. Not brodcasting the ssid will help for security.

what would prevent someone from down loading thier program to another robot?


Lets talk about it?