Hi there,
I’m using WiFly shield and Arduino UNO to query a page every 5 seconds after a successful connection. Everything work as expected but after rough 43 minutes stop working, and green led on pin04 starts blinking fast indicating WiFly has no ip? (or it hangs?). Unplug and plug again and everything work fine again until next 43 minutes.
Have you experienced similar issues?
Thanks
As a search through these forums will reveal, you are lucky to get 43 minutes out of the bug-infested firmware on these devices!
First, I’d update the firmware to the latest version - V2.36 as of 9/14/2012. It would be useful to see the data coming from the module to see what messages it’s outputting before it hangs. I’ve been using this module in commerical applications for about 18 months, and while I’ve experienced several different problems, I haven’t had it hang on me.
I have a similar issue. I’ve got an RN-171 using the HTTP GET command to link short data strings from a logger to a web page at the rate of 1/s via a smartphone tether. But it never holds up for more than a few hours. I’m reluctant to upgrade the WiFly firmware because they have ditched adhoc mode in the latest version & adhoc mode is the only sure way for me to connect to this embedded device.
This is my setup
set opt deviceid Scooter
set ip proto 18
set ip host 0
set ip remote 80
set uart mode 0x12
set option format 11
set com match 10
set wlan rate 0
set w s Skynet
set w p 1234567890
set comm remote GET$/server.php?value=
set dns name www.frontiermedia.net.au
and this is what comes out after the ‘get e’ command
WiFly Ver 2.23, 04-26-2011 on RN-171
Beacon=100
Probe=5
OPEN=OPEN
CLOSE=CLOS
REMOTE=GET /server.php?value=
FlushSize=75
MatchChar=10
FlushTimer=10
IdleTimer=0
CmdChar=$
IF=UP
DHCP=ON
IP=192.168.43.38:2000
NM=255.255.255.0
GW=192.168.43.1
HOST=202.60.66.172:80
PROTO=TCP,HTTP,
MTU=1524
FLAGS=0x7
BACKUP=0.0.0.0
DNS=192.168.43.1
Backup=backup2
FTP=208.109.78.34:21
File=wifly-EZX.img
User=roving
Pass=Pass123
Dir=public
Timeout=40
FTP_mode=0x0
SSID=Skynet
Chan=0
ExtAnt=0
Join=1
Auth=WPA2
Mask=0x1fff
Rate=0, 1 Mb
Linkmon=0
Passphrase=1234567890
TxPower=0
SleepTmr=0
WakeTmr=0
Trigger=0x1
Autoconn=0
IoFunc=0x0
IoMask=0x21f0
IoValu=0x0
PrintLvl=0x1
TimeEna=0
TIMEADR=129.6.15.28:123
Zone=7
Baudrate=9600
Flow=0x0
Mode=0x12
JoinTmr=1000
Replace=0x24
DeviceId=Scooter
Password=
Format=0xb
Signal=0
Average=5
BCAST=255.255.255.255:55555
Interval=0x7
Sensor=0x0
SensePwr=0x0
Does anyone see any optimisations I could make to enhance reliability? Is there a firmware version with adhoc mode more reliable than 2.23?
I was having similar problems with the WiFly RN-XV. My setup would run for a few minutes to a few hours then communications would stop. I don’t know that my setup is exactly like yours but based on an app note on the Roving Networks site I added the following.
set wlan linkmon 5
Now my setup is much more solid.
YMMV
Good luck!
Same problems here. Actually I have been having a long fight with the WiFly over a variety of issues, including the integrity of the packets going into and out of it.
But more recently I’ve been having network drops that have been tough to figure out.
I’ve tried both the 2.383 firmware and the newer 4.00(1) firmware.
Interestingly, even if you set linkmon value to 30, in the 4.0x series the default value for Join is 0. Join has to be set to 1 for it to auto associate if the linkmon detects an issue. This was confirmed to me by tech support at roving.
I’ve gone the further route to make an expensive check (timewise) to get the connection status flags of the wifly chip every 5 seconds and check to see if the tcp status equals 3, meaning it doesn’t have a valid connection, and then I execute a join to try to reconnect the network.
At my office, the wifly is dropping randomly but frequently (like every 5 to 15 minutes)
At home, I’m running the same exact config as i type this and it’s been running for quite a while and no drops are occurring.
I’m at a loss why the exact same config drops so often at work but not at home. But it’s getting frustrating.