Flakey and unreliable WizFi220

Wi-Fi Module WizFi210/220
1

Bought a WizFi 220 demo & eval board recently from Mouser but just can’t get it to work reliably. Specifically the ATA command will sometimes work, but mostly it doesn’t, either erroring out or hanging or not reporting the IP address etc but otherwise working. When it does work it often stops within seconds or minutes, again either erroring out or just hanging. It did one time work for nearly half an hour but that was the exception. ALL other AT commands seem to work fine. I’m running with an open AP (no encription) in infrastructure mode on Channel 11 with DHCP, AP is just 2 metres away. Have tried several different USB power supplies and a 5v bench PSU - all the same. Have also tried upgrading the firmware to 1.1.1.0 still no different.
Please help.
Thanks for listening.
Steve.

2

Some further info:
I set up the default configuration as follows:
ATV1
[OK]
AT+WM=0
[OK]
AT+NDHCP=1
[OK]
AT+XDUM=0
[OK]
AT+NAUTO=1,1,8011
AT+WS
BSSID SSID Ch Type RSSI Security
00:30:ab:0a:ee:84, WirelessX , 11, INFRA , -39 , NONE
No.Of AP Found:1
[OK]
AT+WAUTO=0,WirelessX
[OK]
AT&W0
[OK]
ATA
[ERROR: IP CONFIG FAIL]

IP    SubNet   Gateway

0.0.0.0: 0.0.0.0: 0.0.0.0

Now when I reset it attempts to connect and reports its results, this is a typical session with multiple resets

Serial2WiFi APP-Ext.PA (WIZnet Co.Ltd)
[ERROR: IP CONFIG FAIL]
IP SubNet Gateway
0.0.0.0: 0.0.0.0: 0.0.0.0

Serial2WiFi APP-Ext.PA (WIZnet Co.Ltd)
[ERROR: IP CONFIG FAIL]
IP SubNet Gateway
0.0.0.0: 0.0.0.0: 0.0.0.0

Serial2WiFi APP-Ext.PA (WIZnet Co.Ltd)
[ERROR: IP CONFIG FAIL]
IP SubNet Gateway
0.0.0.0: 0.0.0.0: 0.0.0.0

Serial2WiFi APP-Ext.PA (WIZnet Co.Ltd)
IP SubNet Gateway
192.168.0.89: 255.255.255.0: 192.168.0.1

As you can see it’s struggling to to perform DHCP in fact it’s only about one in 10 attemps that work.
Also when connection is established it is jerky, delayed and unreliable.
Do I have faulty hardware?
Please Help.

3

Hello fishbeetle…

I couldn’t find any problem about RSSI and AT-command-sets(which you used).
But, it’s a little strange that dhcpd(router) retrun <192.168.0.89>.
Of course, it is not wrong, but, there is a possibility of dhcpd’s overload or problem.

Please try it as below and let me know it.

  • test it again after resetting router
  • using instead of
  • test it again with another router

Regards.