Wifi loosing connectivity

[Sebyte]

It has been recently, since around the last three weeks.

[Sebyte]

Just been looking at the Roving Network site and Wifly info.

I don't know how you pass data from head unit to Wifly, but I suspect it may be via some UART configuration or at TCP level? I was wondering if an out of range variable was passed to the wifly buffer could it cause an overflow and hang the connection.

If so is the following of any relevance.

set sys sleep
<value>
sets the sleep timer. The sleep timer is the time in seconds after which the module goes to sleep. This timer is disabled during an open TCP connection. When the TCP connection is closed, the module counts down and puts the module in sleep state based on the value (in seconds). Setting the value= 0 disables the sleep counter and the module will not go into sleep based on this counter.
NOTE: Be sure to set the wake timer if not using an external wake up signal before issuing the sleep timer or the module will never wake up.
See section 10.1 for more details on using system timers
The WiFly modules can wake up from sleep state using the sensor input 0, 1, 2 and 3. This command sets the sensor input(s) to wake on (0-3). This is a bit-mapped value. Setting the value=0 disables wake on sensor inputs.

10.1.2. TCP Connection Timers Opening a TCP Connection:
In TCP-Client mode, the auto-conn timer controls the establishment of a socket connection. When set, the device automatically periodically attempts to establish a connection when the timer expires.
set sys autoconn <secs>
This command causes the module periodically connect to the host. The timer <secs> determines how often to connect to the stored remote host. If set to 1, the module will only make one attempt to auto connect upon power up. If set to 2 or greater auto connect will re-open the connection after the connection is closed. Default=0 disables.

10.3. Wake on UART
When the module is in sleep mode, the UART itself is disabled. However, wake on UART can be accomplished by connecting the SENSE pins to the RX data or CTS pin. (Using the appropriate divider resistors mentioned above)

I may be well off track and if so sorry for a Red Herring!

[rimai]

Could be...
Did you try factory reset and setting it up again?

[Sebyte]

No, but I will give it a try and let you know.

[Sebyte]

Hi Roberto

Yesterday morning I did a factory reboot and reloaded the software to the wifi. It shows that I am on v2.3.

The wifi dropped at 9:25 pm according to my web banner when I looked at it this morning.

Banner

09-01-12 21-25.JPG (24.16 KiB) Viewed 4789 times

I tried to ping the wifi and could not get a reply. I was surprised that the wifi had not come back at 6am when the RA should have rebooted using the code you gave me (see above).

I had to hard reboot the system by un-plugging and re-plugging into the mains socket.

You will see from the banner that the room temperature was 58.6. On previous times when the wifi has dropped the room has been cold. When we go away for example we turn down the heating to around 45f to stop the pipes freezing.

Last night and being an outcast, I fancied smoking one of my cigars. The rules are smoke only with the balcony doors open (and a Parker on as it gets very cold in Toronto!). The room temperature obviously dropped. Then closed the doors and put the heating back on. I did not check the tank readings before I turned in.

The coincidental thing is that I finished my smoke around 9:15 - 9:30 pm from what I can remember, the time the wifi died .

This morning I have tried to simulate the event by placing the temperature probe in a pan of water around 75f, then lowering the temperature by placing an ice pack in the water. The temperature got to 46f, then I removed the probe and let it return to room temperature. Unfortunately the fault did not show up.

So what now, two options

1. wait and see if the wifi drops again under similar circumstances.

2. Give up smoking cigars

[mineman@mac.com]

I'm having the same issue, was there a resolution? I don't think it's a temperature issue as I'm in San Diego.