Operating two Robots Simultaneously

[Qbot2640]

Originally Posted by Alan Anderson

If you're going to do it by changing the team number, you must change the number on the [robo/c]RIO as well. But that's not the easiest or most reasonable way to do it. It's best to keep the team number consistent. The only thing you need to do is to make sure the SSIDs on the D-Links are different. That way you can connect the appropriate Driver Station computer to each robot. With the two robots' networks thus separated, there is no interference.

We have done this before, and I am fairly certain we did not do anything significant to the c-RIO. In 2014 we used our 2013 robot to practice defense, and after the 2012 season we used our 2011 robot in demos to load balls into 2012.

That being said - I would much rather do this without having to change the team number, and what you're recommending sounds easy.

Originally Posted by Alan Anderson

We've always used a distinctive SSID on each robot's access point. It's easy to do. Just log into the D-Link's admin web page and change it to something that identifies that particular robot. Then you can connect your driver station computer to the wireless network corresponding to the robot you want to control.

Once again...please don't judge, but I have no idea what an SSID is. It's sounding like you want me to pull up the configuration page on the D-Link, not make my change by using the FRC bridge configuration tool. I've never done that, are there instruction somewhere for what you recommend?

Originally Posted by FrankJ

The IP of the dlink really doesn't matter unless you need to connect to its web page. The address range of the DHCP is important if you are not running static IPs. For the RoboRio bot make sure the DHCP is turned on and set for the correct range. Just changing the IP of the dlink will not do this. The Week zero page of screensteps is a good read for the Crio. The IP of the driver station for the crios needs to be 10.te.am.xx where the te.am. matches the CRio.

I'll look at the link you recommend...does this have instructions that will get someone who hates, and is awful at network configuration stuff, through the process? Like with "SSID" I have no idea what "DHCP" is either...remember...I'm the mechanical guy trying to fill a gap left by the loss of our programming mentor.