Wifi AP connection to bot

[Mark McLeod]

Is the security code still set?
In other words, have you used the DLink since you playing on an official field last year?

You can check by browsing to the DLink and checking the bottom of the Wireless menu.
If security is still set, just turn it off.

[sebflippers]

Originally Posted by Mark McLeod

Is the security code still set?
In other words, have you used the DLink since you playing on an official field last year?

You can check by browsing to the DLink and checking the bottom of the Wireless menu.
If security is still set, just turn it off.

Just reset it with no encryption. Can I just connect any router I have lying around (assuming I set it correctly)? Assuming this fixes things we will buy a new dap1152.

[Mark McLeod]

Most wireless routers will work. They do need to have compatible bands/frequencies to the PC/Driver station (for that matter you can double-check the DLink settings to see that they match your PC's wireless card specs.

Do double-check the voltage requirements if you plan to plug it into the robot power system. For a quick test though just use the wall outlet to see if it

[sebflippers]

how about that old linksys thing that we used a few seasons ago. you know, that little black box with one ethernet port.

edit: never mind, I think that is only a bridge.

[sebflippers]

does anybody else have any ideas as to what might be causing this? We can still connect to the access point when it is mounted on the bot in the developer account.

[sebflippers]

I've got the box here in front of me. I just reset it and I am redoing everything. I noticed that I might have missed a step, namely disabling "wifi protected setup" (wcn2). I don't have anything to test it on until Monday, but could that be what is causing the problem?

[Mark McLeod]

Yes, any security setting that's not matched by the PC will prevent wireless communication.

[Chiller]

Originally Posted by sebflippers

I've got the box here in front of me. I just reset it and I am redoing everything. I noticed that I might have missed a step, namely disabling "wifi protected setup" (wcn2). I don't have anything to test it on until Monday, but could that be what is causing the problem?

If you can connect to the router through the dev user then it will work, the reason it is most likely not working is because when in driver it is not connected to the router/bridge, which means no robot communication. What I figured out is that if you go into the dev user and connect to your bridge you have to check the box that says connect automatically, or else when in driver it will have no clue which thing to connect to. But if this does not work then when in driver you have to Ctrl+Shift+Esc it and exit the driver station then connect to the bridge in there then in start you can start back up the driver station. And that should do the trick!