I am having difficulties getting a WiFly GSX connected to my wireless network which uses DHCP. I have tried using two different LinkSys WRT-54G routers (one the actual access point using security and another running dd-wrt in open mode) and observe similar results. My connections are RX, TX, GND, and a regulated 3.3v supply connected to VDD-BAT & VDD-IN. I have VREG-IN connected to ground.
It seems that I can associate with either access point, but I cannot get DHCP information from either. After the successful association, the GSX reports “DHCP: Start” and that’s it. I stay associated, but no IPs are passed to the module. If I assign an IP, gateway, mask, etc. From the GSX standpoint it appears that I’m connected and the module says it is listening on port 2000. However, I am unable to connect to the module or make outgoing connections from the module. That leads me to believe that it really isn’t connected.
I have run out of ideas. Has anyone seen this before and found out what the problem is?
Here is some of the output from TerraTerm along with some comments:
--after factory RESET and set wlan join 0
get everything
Beacon=100
Probe=5
OPEN=*OPEN*
CLOSE=*CLOS*
REMOTE=*HELLO*
FlushSize=64
MatchChar=0
FlushTimer=10
IdleTimer=0
CmdChar=$
IF=UP
DHCP=ON
IP=0.0.0.0:2000
NM=255.255.255.0
GW=0.0.0.0
HOST=0.0.0.0:2000
PROTO=TCP,
MTU=1460
FLAGS=0x7
BACKUP=0.0.0.0
DNS=0.0.0.0
Name=server1
Backup=backup2
FTP=208.109.78.34:21
File=wifly-GSX.img
User=roving
Pass=Pass123
SSID=roving1
Chan=0
ExtAnt=0
Join=0
Auth=OPEN
Mask=0x1fff
Rate=12, 24 Mb
Linkmon=0
Passphrase=rubygirl
SleepTmr=0
WakeTmr=0
Trigger=0x1
Autoconn=0
IoFunc=0x0
IoMask=0x20f0
PrintLvl=0x1
TimeEna=0
TIMEADR=129.6.15.28:123
Zone=7
Baudrate=9600
Flow=0x0
Mode=0x0
JoinTmr=1000
Replace=0x24
DeviceId=WiFly-GSX
Password=
BCAST=255.255.255.255:55555
Interval=0x7
<2.15>scan
<2.15>
SCAN:Found 1
Num SSID Ch RSSI Sec MAC Address Suites
1 dd-wrt 03 -35 Open 00:14:bf:09:95:e9 104 4
join # 1
Auto-Assoc dd-wrt chan=3 mode=OPEN SCAN OK
Joining dd-wrt now..
<2.15> Associated!
DHCP: Start
(nothing is returned, even after several minutes)
show net
SSid=dd-wrt
Chan=3
Assoc=OK
Rate=12, 24Mb
Auth=OK
Mode=OPEN
DHCP=FAIL
Time=OK
Links=1
<2.15>show connection
8333
Given that the other odd WiFly behaviour that’s been mentioned on the forums recently was apparently solved with a factory reset you might want to try that.
And now it works with WEP. The problem was that WiFly only supports 128-bit WEP keys (not 64-bit). Just type set wlan key XXXXXXXXXXXXXXXXXXXXXXXXXX and the above example works with encrypted wifi.
follower:
Are you able to view the logs on your Access Point to see if it provides an error message and/or indicates that the WiFly has connected?
Given that the other odd WiFly behaviour that’s been mentioned on the forums recently was apparently solved with a factory reset you might want to try that.
–Philip;
Good point about checking the logs on the router. I hadn’t thought about that. I did try a factory RESET with the same results.
The good news is that I did get things to work, although I’m not entirely certain why it works. I am using the WiFly GSX breakout board and had the board plugged into a protoboard. A 78M33 provides the 3.3v regulated voltage for the module. I didn’t bother to connect the four LEDs, but thought it would be helpful have them in place for further diagnostics. To that end, I took the breakout board and plugged it into the pcb that I’m going to use for the project which does have the LEDs and current limiting resistors. I used the SAME regulator that I used in the protoboard. After applying the power, the LEDs flashed as expected. It also was able to associate AND get DHCP data.
I measured the power in both scenerios and it was clean, so I really don’t know why connecting the LEDs would make a difference. As far as I can tell, there isn’t anything wrong with the protoboard, so it must have been one of those things.
Anyway, I’m able to move forward and things are working very well now.
Thanks for updating the thread with what has worked.