Re: SPWF01 : can't connect to the mini AP - Page 2 - STMicroelectronics Community

Posted on January 04, 2017 at 09:52

Hello,

I'am using this module to connecte my borad to Internet.

This module can create a mini AP so a user can connect its laptaop or smartphone to the SPWF01 and configure the WIFI connexion (SSID and pass).

I have no problÃ¨me to connect to the mini AP with an old WIKO smartphone but I can't connect with a newer smartphone (Huawei P9 lite).

I have also discover a weird thing : If I first connect anything (old WIKO or laptop) to the mini AP, and then try with the P9 lite, it can connect to the mini AP.

thanks for your help.

Marc G

17 REPLIES 17

Posted on February 08, 2017 at 18:26

Hi Marc,

I suspect this is something added to miniAP after v3.5 (traffic information map bytes inside beacons). I can give you an updated FW, for a test. Send me a private message...

Posted on February 10, 2017 at 12:43

hello,

have you received my message with my Email address ?

regards.

Marc

Posted on February 10, 2017 at 14:36

yes

Posted on October 13, 2017 at 09:22

Hi Gerardo,

I have a similar problem with HUAWEI P8 Lite (2015).

It connects and disconnects continuously in a loop.

Can You help me?

I download and installed the app WIFI FIXER from Play store and I monitorized the thing.

You can find the logs of the SPWF01 and of the app below. the firmware is 3.5 and the O.S. of the smartphone in Android 6.0.

Best regards.

This is the log from the of the SPWF01:

+WIND:72:Station 5C:03:39:54:92:CC Disassociated:2

+WIND:28:Station 5C:03:39:54:92:CC Associated:0

+WIND:29:DHCP reply for 172.25.103.2/5C:03:39:54:92:CC

+WIND:72:Station 5C:03:39:54:92:CC Disassociated:2

+WIND:28:Station 5C:03:39:54:92:CC Associated:0

+WIND:29:DHCP reply for 172.25.103.2/5C:03:39:54:92:CC

+WIND:72:Station 5C:03:39:54:92:CC Disassociated:2

+WIND:28:Station 5C:03:39:54:92:CC Associated:0

+WIND:29:DHCP reply for 172.25.103.2/5C:03:39:54:92:CC

+WIND:72:Station 5C:03:39:54:92:CC Disassociated:2

+WIND:28:Station 5C:03:39:54:92:CC Associated:0

+WIND:29:DHCP reply for 172.25.103.2/5C:03:39:54:92:CC

+WIND:72:Station 5C:03:39:54:92:CC Disassociated:2

+WIND:28:Station 5C:03:39:54:92:CC Associated:0

And this is the log of the APP:

Build:1.0.5:1165

ALE-L21

6.0

2017-10-10 10:05:16: Network Check:

2017-10-10 10:05:20: Network check failed: Trying again

2017-10-10 10:05:20: I/O Exception172.25.103.1:HTTP_FAIL:4007ms

2017-10-10 10:05:20: Current dBm:-56

2017-10-10 10:05:20: WFMonitor Acquiring Wake Lock

2017-10-10 10:05:20: Running Wifi Repair

2017-10-10 10:05:20: Reassociating

2017-10-10 10:05:20: WFMonitor Releasing Wake Lock

2017-10-10 10:05:20: Fix Algorithm1

2017-10-10 10:05:20: Supplicant State:ASSOCIATING

2017-10-10 10:05:20: Supplicant State:ASSOCIATED

2017-10-10 10:05:20: 'WIFI_TEC' : Network Disconnected

2017-10-10 10:05:20: Supplicant State:COMPLETED

2017-10-10 10:05:21: 172.25.103.1:HTTP_OK:1003ms

2017-10-10 10:05:21: Current dBm:-56

2017-10-10 10:05:21: WFMonitor Acquiring Wake Lock

2017-10-10 10:05:21: Network Check:

2017-10-10 10:05:21: 172.25.103.1:HTTP_OK:8ms

2017-10-10 10:05:22: Current dBm:-56

2017-10-10 10:05:22: WFMonitor Releasing Wake Lock

2017-10-10 10:05:28: Demoting network'WIFI_TEC' to 61

2017-10-10 10:05:36: Network Check:

2017-10-10 10:05:36: 172.25.103.1:HTTP_OK:40ms

2017-10-10 10:05:36: Current dBm:-56

2017-10-10 10:05:36: Alarm Intent

2017-10-10 10:05:56: Network Check:

2017-10-10 10:05:56: 172.25.103.1:HTTP_OK:8ms

2017-10-10 10:05:56: Current dBm:-56

2017-10-10 10:06:16: Network Check:

2017-10-10 10:06:16: 172.25.103.1:HTTP_OK:41ms

2017-10-10 10:06:16: Current dBm:-57

2017-10-10 10:06:36: Network Check:

2017-10-10 10:06:36: 172.25.103.1:HTTP_OK:39ms

2017-10-10 10:06:36: Current dBm:-56

2017-10-10 10:06:56: Network Check:

2017-10-10 10:06:56: 172.25.103.1:HTTP_OK:7ms

2017-10-10 10:06:56: Current dBm:-56

2017-10-10 10:07:16: Network Check:

2017-10-10 10:07:20: Network check failed: Trying again

2017-10-10 10:07:20: I/O Exception172.25.103.1:HTTP_FAIL:4007ms

2017-10-10 10:07:20: Current dBm:-56

2017-10-10 10:07:20: WFMonitor Acquiring Wake Lock

2017-10-10 10:07:20: Running Wifi Repair

2017-10-10 10:07:20: Reassociating

2017-10-10 10:07:20: WFMonitor Releasing Wake Lock

2017-10-10 10:07:20: Fix Algorithm1

2017-10-10 10:07:20: Supplicant State:ASSOCIATING

2017-10-10 10:07:20: Supplicant State:ASSOCIATED

2017-10-10 10:07:21: 'WIFI_TEC' : Network Disconnected

2017-10-10 10:07:21: Supplicant State:COMPLETED

2017-10-10 10:07:21: 172.25.103.1:HTTP_OK:1004ms

Posted on October 29, 2017 at 13:04

Please test the FW3.5.3 (latest, online), and use the wifi_add_tim_ie/wifi_dtim_period variables (0/1 to dis/enable traffic information map information element).

If also this release is not working, I assume it's something related to powersave of P8. SPWF01 miniAP is not currently supporting powersaving STAs.

Posted on October 30, 2017 at 10:42

Thank You very much but I've just tested the 3.5.3 changing the variables above, but without results.

The distributor sent me a beta versione of firmware: SPWF01S-170213-7f49131-RELEASE-main and it works very well with P8 Lite but I'm waiting for the official release of it (I've some dubts with samsung galaxy S7). What's the differences between the two.

Thank You in advance

Posted on October 30, 2017 at 11:50

I'll be waiting for next release. I hope as soon as possible please.

Thank you very much.

Posted on October 30, 2017 at 11:21

You got a beta version of next release, allowing the module in miniAP to support powersaving STAs. Stay tuned.