Wireless Deployment / Ipconfig

[p00rleno]

Hey everyone, here's a quick heads-up.

As far as LabVIEW is concerned, it is possible to deploy over the robot's own wireless network, and without manually configuring your IP. The only drawback to not manually setting your IP to 10.xx.yy.6 is that you cannot use the dashboard VI, however wireless settings always work. Rough steps are below:

1: Enable the Linksys router's B/G bands to broadcast, without security of course.
2: Set the router up to DHCP addresses from 10.xx.yy.10 and up.
3: Connect your wireless PC or laptop to the network.
4: Deploy as usual! It's really that easy

This works because the cRio could care less about what IP it's receiving the program from, and it is unable to distinguish between a wireless communication as compared to plugging in.

This will save LOTS of time if you haven't caught on already. Nobody likes messing with ipconfig and all that, so just don't!

[Mike Betts]

Andy,

Just because you can do something, does not mean you should...

Think for a second of a competition where scores (if not many hundreds in Atlanta) of teams do as you suggest...

The unique IP address tied to your team number is mandatory.

Regards,

Mike

[diviney]

Andy is not violating the principal of unique team IP addressing. His resulting IP's are constrained to 10.xx.yy.10-254 which is still completely unique to his team.

You do have a legitimate point from an RF interference standpoint, and wireless operation in the pits at competitions will likely be prohibited for that reason.

At your home base however, this is highly valuable. It allows multiple development stations to "share" the robot without plugging / unplugging. We have always done this, but we are "wired" to a small local network. We can share the robot through a tether, or through it's wireless link. A simple consumer router (in combination with a hub/switch if more ports are needed) can facilitate this. You could use this at a competition (tethered to the robot to avoid RFI), but then agtain, the pits are so crowded that you may not want a team of programmers huddled around hacking at the software!

-Tom

[p00rleno]

Originally Posted by diviney

You do have a legitimate point from an RF interference standpoint, and wireless operation in the pits at competitions will likely be prohibited for that reason.

Yeah, this is meant for your at-home code tinkering, not competitions, sorry for not clarifing.

~Andy