Hi All,
Has anyone been able to get the WiFly shield to show that it has a DHCP address issued by a LinkSys WRT54G
router when using WEP (I know, I should switch to a newer security protocol…) and the alpha Ardunio Library for the
board?
I have the WiFly WebServer example sketch loaded, and the WiFly is definitely associating with the router, but
the WiFly reports an IP address of 0.0.0.0. The router indicates the WiFly’s MAC address has been given an IP
address, but I can’t communicate with the WiFly at that address from any computer on the network.
Thanks,
Paul
Hi Paul…
Thanks for your question.
pbender:
I have the WiFly WebServer example sketch loaded, and the WiFly is definitely associating with the router, but
the WiFly reports an IP address of 0.0.0.0. The router indicates the WiFly’s MAC address has been given an IP
address, but I can’t communicate with the WiFly at that address from any computer on the network.
Remote network troubleshooting is...challenging, but let's try this. :)
My first suggestion would be to start with the WiFly_Autoconnect_Terminal example which–once it’s connected–should drop you into a “command shell” type environment where you can type commands directly to the WiFly. Unfortunately it doesn’t work with the Arduino IDE serial console so you’ll need to find a serial console for your Operating System that allows you to send newline characters (which pretty much any should). If you let us know what OS you’re running we’ll be able to make some suggestions.
Once you’re connected you should be able to send the following command:
get ip
You should get a response which includes a line that starts with:
IP=
If the value there is 0.0.0.0 then the issue is probably with something other than the library code (which I’d be happy about 
).
If you can report back with your results from this we can decide where to go from there. Any additional specific information is helpful.
–Philip;
Ok, here is the response from get ip:
IF=UP
DHCP=ON
IP=192.168.1.25:80
NM=255.255.255.240
GW=192.168.1.30
HOST=0.0.0.0:2000
PROTO=TCP,
MTU=1460
BACKUP=0.0.0.0
<2.10>
So it looks like the parameters are being set…
Is the 2.10 at the end here the firmware version? If that’s the case, that could be the problem (I know the library was written for 2.18).
Paul
<2.10>
[…]
Is the 2.10 at the end here the firmware version? If that’s the case, that could be the problem (I know the library was written for 2.18).
Yeah, good spotting. :)
Even if that’s not the specific problem in this case, I looked at the change log for the firmware and there are a number of post-2.10 features that the library relies on.
I’ve not actually performed a firmware update yet but that would be my suggestion.
As a matter of interest, how long ago did you acquire the WiFly module?
–Philip;
follower:
Even if that’s not the specific problem in this case, I looked at the change log for the firmware and there are a number of post-2.10 features that the library relies on.
I’ve not actually performed a firmware update yet but that would be my suggestion.
Ok, I’ll see if I can do that.
Do you know where I can find instructions on how to do that through the WiFly Shield?
As a matter of interest, how long ago did you acquire the WiFly module?
Sparkfun’s order history shows the WiFly Shield was part of an order I made on January 7th,2010.
Paul
pbender:
follower:
Even if that’s not the specific problem in this case, I looked at the change log for the firmware and there are a number of post-2.10 features that the library relies on.
I’ve not actually performed a firmware update yet but that would be my suggestion.
Ok, I’ll see if I can do that.
Do you know where I can find instructions on how to do that through the WiFly Shield?
Never mind, I found the instructions in the reference manual.
After the firmware update, everything seems to be working correctly.
Paul
pbender:
Sparkfun’s order history shows the WiFly Shield was part of an order I made on January 7th,2010.
Thanks, I was curious because I wondered if it was an older firmware that had slipped through recently or not.
pbender:
pbender:
Do you know where I can find instructions on how to do that through the WiFly Shield?
Never mind, I found the instructions in the reference manual.
Great, thanks for saving me the trouble. :D
After the firmware update, everything seems to be working correctly.
Great, please to hear to went smoothly and things are working again. Did you upgrade to 2.18 or 2.19 (or something else? :) )?
Thanks for letting me know how it went.
–Philip;
follower:
pbender:
After the firmware update, everything seems to be working correctly.
Great, please to hear to went smoothly and things are working again. Did you upgrade to 2.18 or 2.19 (or something else? :) )?
The automatic FTP downloaded 2.20.
Paul
pbender:
The automatic FTP downloaded 2.20.
Cheers, thanks for letting me know.
I had a look at the changelog and it seems like there’s no significant incompatibilities so will keep the library targeted at 2.18 for the moment.
–Philip;