Reef Angel Forum

You are probably over 3G. You need to connect through wifi to be able to use the internal ip address.

No i m on wifi thats why its strange

How do i turn off DHCP on the module?

ahmedess wrote:How do i turn off DHCP on the module?

set ip dhcp 0
other relevant cmds;
set dns address
set ip address
set ip gateway
set ip netmask

I was also having issues with my wifi module disconnecting from my access point so I factory reset my module, gave it a static address and I also set the module to operate at 54mbps as I noted that the default is 1 & 2 mbps.

The command to set the data rate to 54 is set wlan rate 15

The module was disconnecting every day and it has now been connected for 2+ days. (fingers crossed)

Roberto,

It seems somehow that when the devices are using DHCP they keep loosing connection. I set mine to static at home and it was stable for a week. I put it back to DHCP and it lost connection within 2 days. Back to static and it has been stable again. I'm wondering if it might have something to do with the lease expiry? I'll see if I can set my DHCP server to extend the ip address lease for longer than a day and see if that makes any difference.

Justin

That's very good information. I'll pass it on to the manufacturer along with the logs you sent me.

Mine stopped working again
Should I send you a "get e" as well ?

Yes please

rimai wrote:Yes please

pmed me get e

cheers
Andy

Disabling DHCP does not make any difference for my case the module still times out

I have reserves an internal IP on my router for the RA wifi. It helps a lot, however every couple of days I lose connection. Can't ping it or anything. Pulled it off the cable, gave it a few minutes and plugged it back in and it worked. All this time flashing a nice steady slow green light.

Did you ever try the host set to 0.0.0.0??
I wanted to see if that really solves the problem or not.
That would make your controller not send data to the Portal though, but we would have concrete evidence to provide the manufacturer. I haven't heard anything from them yet.

I'll give it a try and let you know.

has anyone that experianced this issue managed to sort it out.

i have noticed that at least once that my access point has reported that the module is still
associated but its not ping able.
the leds on the module were blinking green but none of the orange leds were blinking.

the module does not re associate to the access point if i manually clear the associate table.

This is giving me a hard time to, mine use to work for a few days and later it just blinks blue, before i just have to unplug the adapter to make it work again, but now i doesn't work i have to set the parameters every couple of days, it is even turning off, i have found the adapter with all the leds off.

Hope to find a solution for this, cause this is really annoying.

Have you updated to 2.35 firmware?
Let's try a different setup method.

Use the wifi utility to restore factory settings.
Unzip the content of the attached zip file in your desktop or any other folder you prefer.
Open the file "wifi attachment.ttl" on notepad or your prefered text editor and change the SSID and passphrase.
Open Tera Term and conenct to your wifi attchment using the correct serial port.
Go to menu Control->Macro and browse the unzipped file from above.
Follow the prompts.

I have just run this macro and after running it noticed that my module was still on version 2.3.2 (I was certain that I ran the update via the utility and it was successful 2x )

I had to manually run the ftp u wifly-235.img , ftp r wps.img cmds as it timed out when the macro ran it for some reason.

Anyhow I guess I should pay more attention to when I am doing ....

You are right.
I forgot to mention that their server does time out sometimes.
It does happen to me too every now and then.
They keep changing servers too. It's the third time in the past few months.
The company got bought out by Microchip and I guess they are in the middle of organization restructure.
I havent't got any response from the ticket I have placed with them in weeks.

so far so good seems version 2.3.5 and maybe the macro above helped as my wifis been up for 24+ hours which is the longest yet...so hopefully me issue is sorted

How do i verify the version that my wifi have?

You need to use Tera Term.
Check the manual for instructions.

I just tried updating to version 2.35. I get the following error message.

CMD
ftp update wifly-235.img

<2.32> FTP connecting to 208.109.14.133
530 Login authentication failed

FTP ERR
530 You aren't logged in

FTP ERR

They changed their server once again
http://www.rovingnetworks.com/FAQs/I_ge ... Fly_module
This is probably going to mess with the remote connection to the reefangel server after you update the firmware.
So, after successful upgrade, please return the dns back to www.reefangel.com with this command:

Tried the instructions you provided rimai and am getting:

<2.35> FTP connecting to 198.171.134.6
530 User roving cannot log in.

FTP ERR

That ip address is the wrong ip address, which indicates you did not follow the above instructions properly.
You have to make sure you set the dns name and ftp address according to their instructions, update the firmware and then return back to reefangel.com dns name.

I ran the commands on the page you specified:

set ftp address 0

AOK
<2.35> set dns name www.neelum.com

AOK
<2.35> save

Storing in config
<2.35> ftp update

<2.35> FTP connecting to 198.171.134.6
530 User roving cannot log in.

FTP ERR

Try sending "reboot" after you save.
Then connect again and try updating.
To make sure that the command was really saved, use command "get d" and it should display what's stored in the module.

Same:

CMD
set ftp address 0
AOK
<2.35> set dns name www.neelum.com
AOK
<2.35> save
Storing in config
<2.35> get d
DNS=192.168.1.2
Name=www.neelum.com
Backup=backup2
<2.35> reboot
*Reboot*CMD
get d
DNS=192.168.1.2
Name=www.neelum.com
Backup=backup2
<2.35> ftp update
<2.35> FTP connecting to 198.171.134.6
530 User roving cannot log in.
FTP ERR

Maybe it's getting the ip address from host instead then.
Let's clear the host too.
Try this: