WiFi/Bridge/CRIO Boot Conflict

[Danny Diaz]

Originally Posted by WizenedEE

I'm sure that the field personnel are aware of this problem, if it exists, and will know what to check/reboot if your robot doesn't connect.

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

Originally Posted by WizenedEE

For a slightly off-topic question, am I right in saying that bridge mode connects to one wireless source and Access Point mode connects to many wireless sources?

I prefer to think of a client/server model instead. Look at the DAP-1522 as two devices; a wired switch connected to a wireless device. In the Access Point Mode, the wireless device is 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 it to get DHCP addresses and talk to other devices on the network. In Bridge Mode the wireless device is nothing more than a wireless ethernet cable (client) - it provides a wireless "bridge" from its switch component (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 field network. 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