SPWF04SA DHCP Server problem

[bernd sch�nlebe]

Posted on August 01, 2017 at 11:31

I have setup the module as miniAP with following script: (

http://elektronikab2b.pl/technika/32973-spwf04sa-miniaturowy-modul-wi-fi-z-oferty-stmicroelectronics---przyklady-zastosowan

)

AT+S.WIFI=0

AT+S.FCFGAT+S.SSIDTXT=test_apAT+S.SCFG=wifi_priv_mode,1AT+S.SCFG=wifi_mode,3AT+S.SCFG=wifi_wep_keys[0],76543210abAT+S.SCFG=wifi_wep_key_lens,05AT+S.SCFG=wifi_auth_type,0AT+S.SCFG=ip_ipaddr,192.168.0.1AT+S.SCFG=ip_use_dhcpc,2AT+S.WIFI=1AT+S.WCFGAT+S.RESET

once it restarts, this is what I get:

Port opened

SPWF04SA WIFI test program start.Setup SPI done.Reset module...Start module...Done.RX:02 10 07 02 00 AT+S.WIND:7:Configuration Failure:<wifistate=Hardware power up>:10RX:02 10 01 16 00 AT+S.WIND:1:Poweron:<wifistate=Hardware power up>:170726-b7ac1ba-SPWF04SRX:02 10 0D 08 00 AT+S.WIND:13:Copyright:<wifistate=Hardware power up>:SPWF04SARX:02 10 03 02 00 AT+S.WIND:3:Watchdog Running:<wifistate=Hardware power up>:20RX:02 10 00 00 00 AT+S.WIND:0:Console active:<wifistate=Hardware power up>:RX:02 13 20 00 00 AT+S.WIND:32:WiFi Hardware Started:<wifistate=Radio idle>:RX:02 13 1A 07 00 AT+S.WIND:26:Started AP:<wifistate=Radio idle>:test_apRX:02 19 18 0D 00 AT+S.WIND:24:WiFi Up:<wifistate=802.11 handshake complete>:0:192.168.0.1RX:02 1A 18 1C 00 AT+S.WIND:24:WiFi Up:<wifistate=Ready to TX>::fe80:0:0:0:280:e1ff:febd:39

now, just to be sure, here the entire config printout:

TX:02 00 02 09 00 //AT+S.GCFG

nv_manuf=STMicroelectronics Inc.nv_model=SPWF04SAnv_serial=17111984nv_wifi_macaddr=00:80:E1:BD:00:39standby_time=10standby_enabled=0sleep_enabled=0etf_mode=0blink_led=1ext_volume=3ramdisk_memsize=16aes128_key=00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00user_desc=anonymouspython_script=3:/uPython_test.pypython_memsize=32console_enabled=1console_speed=115200console_hwfc=0console_echo=1console_errs=2console_winds=2console_verbose=1console_repeater=0x21console_delimiter=0x2Cconsole_wind_off_low=0x00000000console_wind_off_medium=0x00000000console_wind_off_high=0x00000000wifi_tx_msdu_lifetime=0wifi_rx_msdu_lifetime=0wifi_operational_mode=0x00000011wifi_beacon_wakeup=1wifi_beacon_interval=100wifi_listen_interval=0wifi_rts_threshold=3000wifi_ssid=74:65:73:74:5F:61:70:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00wifi_ssid_len=7wifi_txfail_thresh=5wifi_dtim_period=1wifi_add_tim_ie=0wifi_region=1wifi_ht_mode=1wifi_channelnum=6wifi_opr_rate_mask=0x003FFFCFwifi_bas_rate_mask=0x0000000Fwifi_mode=3wifi_auth_type=0wifi_atim_window=0wifi_powersave=0wifi_tx_power=18wifi_rssi_thresh=0wifi_rssi_hyst=0wifi_ap_idle_timeout=120wifi_beacon_loss_thresh=10wifi_priv_mode=1wifi_wep_keys[0]=76:54:32:10:AB:00:00:00:00:00:00:00:00:00:00:00wifi_wep_keys[1]=00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00wifi_wep_keys[2]=00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00wifi_wep_keys[3]=00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00wifi_wep_key_lens=05:00:00:00wifi_wep_default_key=0wifi_wpa_psk_raw=00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00wifi_wpa_psk_text=wifi_eap_identity=identitywifi_eap_anon_identity=anonymous@identity.orgwifi_eap_passwd=passwordwifi_eap_type=0wifi_eap_skip_datechecks=0wifi_wps_walk_time=120wifi_wps_pin=1234567ip_sock_memsize=1ip_sock_threshold=0ip_dhcp_lease_time=120ip_macfilter=00:00:00:00:00:00ip_num_clients=5ip_allow_port_scans=1ip_use_v6=1ip_use_dhcpd=1ip_use_httpd=1ip_use_tftpd=1ip_use_dhcpc=2ip_hostname=iwm-BD-00-39ip_apdomainname=captiveportal.netip_apredirect=firstset.htmlip_ipaddr=192.168.0.1ip_netmask=255.255.255.0ip_gw=192.168.0.1ip_dns1=192.168.0.1ip_dns2=208.67.220.220ip_local=0:0:0:0:0:0:0:0ip_dns1v6=0:0:0:0:0:0:0:0ip_dns2v6=0:0:0:0:0:0:0:0ip_dhcp_timeout=20ip_ntp_server1=ptbtime1.ptb.deip_ntp_server2=ntp0.ipv6.fau.deip_ntp_refresh=3600ip_ntp_startup=1ip_mdns_domain_name=SPWF04S-Defaultip_mdns_device_name_ttl=120ip_mdns_services_name=SPWF04S-WebSrv SPWF04S-TFTPSrvip_mdns_services_prot=_http._tcp _tftp._udpip_mdns_services_keys=dev1 dev2ip_mdns_services_vals=number1 number2ip_mdns_services_port=80 69ip_mdns_services_ttl=120 60ip_mdns_startup=01:01

now my problem is this: once I try to connect with my phones wifi f.e., it does recognize that a station gets associated, but it does not give out an IP, what do I have to setup for it to work?

RX:02 1A 1C 13 00 AT+S.WIND:28:Station Associated:<wifistate=Ready to TX>:00:16:EA:E5:89:FE:0

RX:02 1A 1C 13 00 AT+S.WIND:28:Station Associated:<wifistate=Ready to TX>:00:16:EA:E5:89:FE:0RX:02 1A 48 13 00 AT+S.WIND:72:Station Disassociated:<wifistate=Ready to TX>:00:16:EA:E5:89:FE:1

PS: I see the 'Configuration Failure' but its non-halting and I dunno what HW pullup resistor is meant here. This all worked fine before I upgraded the firmware (SPWF04S-170726-b7ac1ba)

PPS: if I downgrade back (firmware SPWF04S-170216-fd39c59), it works but all the fixed problems (with SPI communication) are back, so this has to be a firmware issue

[brianshankland9]

Posted on May 23, 2018 at 11:54

I'm also seeing the same problem.

When using Mini-AP mode with the ip_use_dhcpd=1 I'm not seeing the Win29 DHCP Reply messages, only the Wind 28 Station Associated messages.

When connecting to an old XP machine it works every time, but with Win10 its less than 10%, and instead of getting a DHCP allocated IP address it uses its Alternative address instead.

Unable to tell if its Win10 not sending a DHCP request or the SPWF04 not servicing the request correctly.

Maybe Win10 is not being told that a DHCP server is available in the device so it doesn't make a request.

All very frustrating so any insight appreciated.

[Elio Cometti]

Posted on May 23, 2018 at 17:16

Hello,

if you are not sure about Win10 DHCP settings, please verify that 'Obtain an IP address automatically' is checked in IPV4 dialog of your wireless network adapter.

Then, if not already done, please reboot the SPWF04 (either AT+S.RESET or HW reset) and then try associating the PC again.

If this does not make the things better, please attach your module's configuration (AT+S.GCFG) and status (AT+S.STS) to this topic.

[brianshankland9]

Posted on May 24, 2018 at 10:32

Thanks for getting back to me so quickly.

Yes the Win10 machines are all looking for DHCP allocated addresses across wifi.

I've loaded Wireshark onto one laptop so I can see if a message is not being handled, unfortunately since that time I've not had a failure on that computer (sometimes can work for hours at a time then fail for equally long times).

Since the firmware is not changing in this time I'm sure it must be a timing and/or network thing.

I'll add in option to dump out the variable and status and post up soonest, and if I get a failure on wireshark will post this as well.

Thanks

[brianshankland9]

Posted on May 25, 2018 at 11:54 The original post was too long to process during our migration. Please click on the provided URL to read the original post. https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006I6oY&d=%2Fa%2F0X0000000bw5%2FTP.7qmpV2QxGxVqbZreDm2C7KLBeO7p6860CeCRjk8o&asPdf=false