Ney Palma

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

10 years, 8 months ago.

Wifly communications not stable, Please help!!!

Hi, anyone knows why the wifly module (RXNV) dont have a stable communication? Is the Wifly Library not reliable? I make a ping to the IP assigned to the module and every time to time, i get a destination host unreachable message, and have and 11% lost packages. I dont think this is normal. I have an android client that connects to the mbed and i dont have a reliable communication because that

Greetings, i hope anyone can help me

2 Answers

David Smart
10 years, 8 months ago.

I cannot replicate your problem. To try, I was running a small web server on the mbed, using the WiFly as the network connection. The web page was scheduled to periodically reload, and while that was happening I ran 50 echo requests. My environment had zero lost packets.

>ping -n 50 192.168.1.137

...
Reply from 192.168.1.137: bytes=32 time=1ms TTL=255
Reply from 192.168.1.137: bytes=32 time=3ms TTL=255

Ping statistics for 192.168.1.137:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 5ms, Average = 1ms

My Wifly module has SW version 4.00.1. I have a couple of walls and a floor between the module and my access point, but signal strength has not been a problem for me (I haven't looked at the RSSI numbers in some time). I do have the module with the external antenna, which may help.

Suggestions:

  1. Run Wifly_configure and then while connected to the module you can issue the commands to show the signal strength ("scan" is one easy way).
  2. Move the module closer to the access point, or perhaps "away" from other nearby Wi-Fi devices (laptop, phone, etc.)
  3. Check the SW version on your Wifly module - I have no reason to think other versions would be different, but it may be worth checking.
  4. Check the quality of your power supply to the module. Normally, a weak supply would cause much greater problems, but it may be worth the check.

Vollmer Bomfim
9 years, 10 months ago.

I have the same issue. Upgraded the firmware to 4.41 and still the same problem. Big variations in replying times and sometimes it does not answer pings at all.

Pinging 192.168.1.104 with 32 bytes of data: Reply from 192.168.1.104: bytes=32 time=8ms TTL=255 Reply from 192.168.1.104: bytes=32 time=4ms TTL=255 Reply from 192.168.1.104: bytes=32 time=149ms TTL=255 Reply from 192.168.1.104: bytes=32 time=83ms TTL=255