WIFI inop

[dbmet]

Went out about 4 hours later and never reconnected..

WiFly Ver 2.36, 09-27-2012 on RN-131
Beacon=100
Probe=5
Reboot=0
OPEN=
CLOSE=
REMOTE=
FlushSize=450
MatchChar=0
FlushTimer=10
IdleTimer=3
CmdChar=$
IF=DOWN
DHCP=ON
IP=192.168.1.24:2000
NM=255.255.255.0
GW=192.168.1.1
HOST=198.171.134.6:80
PROTO=TCP,
MTU=1524
FLAGS=0x6
TCPMODE=0x0
BACKUP=0.0.0.0
DNS=208.67.222.222
Name=www.reefangel.com
Backup=backup2
FTP=208.109.14.133:21
File=wifly-GSX.img
User=roving
Pass=Pass123
Dir=public
Timeout=80
FTP_mode=0x0
SSID=angelandaryl
Chan=0
ExtAnt=0
Join=1
Auth=OPEN
Mask=0x1fff
Rate=12, 24 Mb
Linkmon=5
Passphrase=XXXXXX <---hidden
SleepTmr=3600
WakeTmr=1
Trigger=0x10
Autoconn=0
IoFunc=0x0
IoMask=0x20f0
IoValu=0x0
DebugReg=0x0
PrintLvl=0x0
TimeEna=0
TIMEADR=129.6.15.28:123
Zone=7
Baudrate=57600
Flow=0x0
Mode=0x2
Cmd_GPIO=0
JoinTmr=1000
Replace=0x24
DeviceId=ReefAngelWifi
Password=
Format=0x0
Signal=0
Average=5
BCAST=255.255.255.255:55555
Interval=0x7
Sensor=0x0
SensePwr=0x0

[rimai]

Looks like they were able to replicate the problem now:

I spoke to one of my colleagues in the Roving group this morning. They were able to reproduce a bug that is causing the module to disconnect from the AP and remain unable to reconnect until the module is rebooted. I believe this issue is related to what you are seeing when performing the unicast as well.

The engineering team is currently looking into this, but I don't know when they will be able to create a fix for it. I will update you when I have more information on this issue.

Regards,
Josh

[fatman]

That's pretty good news. Since doing the linkmon setup I have had very good luck with mine staying alive. Now I said that I'd better check on it.

[dbmet]

Yeah that good news.. I changed my router and I've been connected for 2 hours now.. Wahoo..

[fatman]

Well, about day three running like a top (I jinxed myself here) with the fresh reload to the module, firmware 2.3.6 and the linkmon setup on it. Occasionally it will miss a connection, but immediately reconnects. I'm hopeful!

[dbmet]

Wahooo made it a day with 2.3.6 and new settings and new router. Here's hoping to a few more days.

[00Warpig00]

Since the 2.23 firmware didn't show any improvements I decided to upgrade to latest firmware from Roving ftp site.
Now up to 2.36 Also decided to give the "set wlan linkmon 5" setting a go. So around midnight last night I got it back up and running. We will see how this test goes. Here is my current running test config just for reference.

WiFly Ver 2.36, 09-27-2012 on RN-131
Beacon=100
Probe=5
Reboot=0
OPEN=
CLOSE=
REMOTE=
FlushSize=1420
MatchChar=0
FlushTimer=10
IdleTimer=3
CmdChar=$
IF=UP
DHCP=ON
IP=192.168.128.200:2000
NM=255.255.255.0
GW=192.168.128.254
HOST=198.171.134.6:80
PROTO=TCP,
MTU=1524
FLAGS=0x6
TCPMODE=0x0
BACKUP=0.0.0.0
DNS=192.168.128.254
Name=www.reefangel.com
Backup=backup2
FTP=198.175.253.161:21
File=wifly-GSX.img
User=Roving
Pass=Pass123
Dir=public
Timeout=80
FTP_mode=0x0
SSID=2WIRE993
Chan=0
ExtAnt=0
Join=1
Auth=OPEN
Mask=0x1fff
Rate=15, 54 Mb
Linkmon=5
Passphrase=mywifikey
SleepTmr=1800
WakeTmr=1
Trigger=0x10
Autoconn=0
IoFunc=0x0
IoMask=0x20f0
IoValu=0x0
DebugReg=0x0
PrintLvl=0x0
TimeEna=0
TIMEADR=129.6.15.28:123
Zone=7
Baudrate=57600
Flow=0x0
Mode=0x2
Cmd_GPIO=0
JoinTmr=1000
Replace=0x24
DeviceId=ReefAngelWifi
Password=
Format=0x0
Signal=0
Average=5
BCAST=255.255.255.255:55555
Interval=0x7
Sensor=0x0
SensePwr=0x0
<2.36>


Nick

Success? Dare I say it... But I have been running the above config since Thu Oct 11, 2012 just after midnight Central Time. It will have been 9 days just after midnight tonight that I have not needed to reset my WiFi mod by unplugging and replugging it into the controller. I was out of town on business the entire week and although there were several times that I could not connect to my controller for a while I did not loose contact to the point it needed a reset. This is the FIRST time I have made it more than 4 days without a reset. Read the info above and its great to hear that it has been confirmed by Roving that there is a bug causing this. Nice to know now that there MAY be a fix in the future. Hopefully my config above may work for others. Anyone else that has to constantly reset their wiFi mod may want to give my config above a try. NOTE: My router is also set to reboot automatically every night at 04:00am. my router is a linksys with DDWRT firmware. dont know if it matters.

I will continue to keep an eye on this, but now it's time to move on to my next RA+ issue my IO Module.

Nick

[rimai]

Here is the response from the manufacturer:

It sounds like this is a complex issue for the engineering team to solve, and they do not yet have an estimated date of completion. Because of this, I am marking this ticket resolved with the following suggestions. Please check back in a few weeks for an update on this issue.

There are a few options available to customers who are experience this error.
1. Monitor the output(TX) of the module and reboot the module upon hearing the “Disconnect” message from the module. A reboot can be done through entering command mode and issuing a “reboot” command. It can also be done by using the Reset pin of the module.
2. The customer can implement the band aid function below and enable a periodic reboot of the module, regardless of what is going on.
Here are the commands for the band aid:
Set system debug 0x80
Set adhoc reboot <time in seconds> //must be greater that 60 secs
Note: The customer will need ver 2.36 for the above commands to work. It will not work with the 2.45 version (AP mode).

3. The firmware could be downgraded to the previous version of firmware (v2.32). I haven’t heard report of this issue in v2.32.

[fatman]

Roberto,

Thanks to you for following this up. Shame on Roving for not providing a solution.

Fat

[dbmet]

What's the easiest way to downgrade firmware?

[rimai]

You will need a serial terminal software like coolterm on mac or putty/tera term on pc.
These are the commands you need to send:

Code: Select all

$$$
ftp update wifly-232.img
save
reboot

For more info on how to enter command mode and sending commands, please refer to the manual.

[dbmet]

Aha Thanks
d

[rimai]

Here is the response from the manufacturer:

Hello,

Our engineering team believes they have fixed this issue in a beta release of firmware. If you would like to evaluate this interim beta ver 2372 of firmware, please use the following commands to update the module. Currently, this is only for the Ad Hoc version of firmware. They are still working on the AP mode version.

ftp u wifly-2372.img

Please let me know any feedback you have for this firmware and I can pass it along to the Roving team. Note that this is a beta version in which we are trying to fix this issue. An official production release will be out soon.

[00Warpig00]

cool, sounds like progress is being made at least...

Nick

[dbmet]

Cool my wifi has been running great for two weeks. The portal has stopped updating the graphs. The portal lets me turn stuff off and on. My iPhone app has been working great.

[dbmet]

Looks like theres a typo in the above command when trying to update..

This worked better
ftp u wifly-2372.img

Guess I'll try it and report back
d

[symon_say]

I had the same problem with 2372, it works for a few days, but lat night start losing connection, I rolled back to 232.

[symon_say]

Do they change the ftp address?? i'm trying to go back to 232 and i get FTP error

[rimai]

This is the ftp address: 198.175.253.161
It's a resolution of rn.microchip.com
Roving Networks was bought out by Microchip and that's why there is a lot of delay and confusion with their products right now.

[daniella3d]

Any fix yet? Mine is also disconnecting after some time with the blue blinking light. Good thing I don't have any trip planned so I cen test it well for now.

It disconnected once yesterday and once tonight, and I have to unplug and plug it back to make it work. It reconnect instantly when I do this.

[dbmet]

Daniella what version of wifi software are you using?

[grafspee1217]

Has there been any resolution to this issue? I occasionally follow this thread to see if the manufacturer has solved the issue with the wifi module. I've had the wifi module disconnected from the reef angel for quite some time and havent had any issues with the ports arbitrarily turning on and off. It only happens when the wifi module is plugged in. Would be nice to be able to use the darn thing.

[dbmet]

I loaded the latest beta software with no problems. I also added and external antenna and it has been working great as well.

[grafspee1217]

Beta software from the reef angel site?

[dbmet]

Look up about 6 messages and its the beta software from the manufacturer.

[daniella3d]

The problem is still there. Disconnected twice yesterday. I either have to unplug and replug the reef angel or disconnect the wifi and reconnect it to make it resume connection.

Where is the link to download the proper software?

[fatman]

Those using the beta firmware: Have you had success with it?

[dbmet]

Mines been working great for many weeks. I tried it for a couple weeks and it was fine. Then I added an external antenna to improve signal and its still working. I also reset the wifi module back to factory settings and then I upgraded to the beta firmware.

[daniella3d]

what's the instructions for this and where to download the working software?

This is a real hassle. disconnected 3 times today and when I got home from work it was still blinking blue. When I unplugged the wifi then the reef angel shut down for a few seconds and went back on, metal halide went off, aquarium in total darkness, corals really upset, fish dashing everywhere!!!...what the heck??? why is the Reef angel shut down if I unplug the wifi??

If this is not working well soon I will be unplugging the wifi module for good.

[dbmet]

I reset my module to factory settings. Then you need to use a program like terraterm or coolterm to update the wifi module. I also had to change the ftp settings since the manufacturer changed their site.. Cant remember where I found them but there on here somewhere..

$$$
ftp u wifly-2372.img
save
reboot

Then you can plug the wifi module back into the Reef angel Head unit