AsyncLabs Forums

[russk]

This week got a WiShield 2.0 and connected it to my new Arduino Duemilanove (Atmega328). I modified the WebServer.pde file per AsyncLabs' instructions, changing just the IP and SSID for my network, which is open. No red LED. Tried several more times, and suddenly the light came on and stayed on long enough for me to access WebServer and get the hello world message. Then the light went off. Later that day and many tries later, the light came on briefly and then went out and would not come back.

After searching thru this forum, I contacted Brad (via Justin at liquidware), who was very patient and very helpful. I mentioned I had an AirPort Express AP. After a few emails and a new WiShield, he suggested I create an ad hoc network, using a non-existent SSID. He felt the Express might be blocking the WiShield from joining the network. Bingo! Red LED is on and stays on!

I have two APs in my house, an Apple Time Capsule and a Airport Express. They're at opposite ends of my house. The Time Capsule, which I'm weakly in range of while I'm developing, was set to "802.11n (802.11b/g compatible)", but the Express, which I'm more strongly in range of, was set to "802.11n only". As soon as I set it to "802.11b/g compatible" and restored my SSID and infrastructure mode, that LED lit right back up again and stayed on.

I'm guessing the flashing LED I saw twice yesterday was the WiShield shifting from one AP to the other. Lesson learned. Make sure your access points are set for compatibility with 802.11b/g.

-Russ