WiFi/Bridge/CRIO Boot Conflict

[Geek 2.0]

Originally Posted by Danny Diaz

Over the course of my FRC experience, I've learned to assume nothing.


Yes, in a manner of speaking; think of a server/client model instead. Think of the Access Point Mode as being nothing more than just a glorified wireless router (server) - it acts as a DHCP server, provides a wireless access point (broadcasts an SSID that clients can connect to) and clients connect through the router to get DHCP addresses and talk to other devices on the network. Think of the Bridge mode instead as a wireless ethernet cable (client) - it doesn't provide any wireless services for others to connect to or use, but instead looks for wireless networks to connect to; as well as providing services as a local "switch", it provides a wireless "bridge" from its network (which your cRIO and camera are sitting on) to a single wireless network (the field network) like a "wireless ethernet cable" from the DAP-1522 to the full-service network you're connecting to. In competition, your classmate will hard-wire into the field network, and the "bridge" mode of the DAP-1522 will connect your robot's local network to the field network. This way the field software controls everything going into and out of your robot. This is a crude description, but accurate in my opinion.

-Danny

As far as I know, the DAP-1522 has no DHCP. It was very annoying for us because the computers we have access to do not allow us to set a static IP, making programming a nightmare. Eventually we were allowed static IPs.