wifi_httpsrv example slow response.

[etronic_arg]

Hi,

I'm testing the wifi_httpsrv from the latest SDK_25_09.

Hardware:
MIMXRT1064-EVK
uBlox Maya-W2 EVK Rev A (IW612)

The module is connected to the EVK via SDIO.

I noticed that the Wi-Fi response speed is quite slow compared with the Ethernet version. For example, the polling demo doesn't refresh every second and ping responses occasionally time out.

Is this expected behavior or could I be missing something in the setup?

Thank you!

[DanielRuvalcaba]

Hi,

Could you please share the terminal output of your test?
How slow is the response? Do you have any measurements?
What device are you using to ping the IW612?

Regards,
Daniel.

[etronic_arg]

Hi Daniel,

This is the terminal output:

Starting httpsrv DEMO
[i] Initializing Wi-Fi connection...
STA MAC Address: 20:BA:36:53:86:F9
[i] Successfully initialized Wi-Fi module
Connecting as client to ssid: xxxxxx_2_4G with password xxxxxxxx
[i] Connected to Wi-Fi
ssid: xxxxx_2_4G
[!]passphrase: 1a2b3c4d5e
Now join that network on your device and connect to this IP: 192.168.201.226

***********************************************************
HTTP Server example
***********************************************************
IPv4 Address : 192.168.201.226
IPv4 Subnet mask : 255.255.255.0
IPv4 Gateway : 192.168.201.1
IPv6 Address0 : -
IPv6 Address1 : -
IPv6 Address2 : -
mDNS hostname : wifi-http
***********************************************************

Ready

Every seems to be fine.

After that, I enter 192.168.201.226 in a Chrome browser.
The web page takes about 10 seconds to load and sometimes the browser times out.
In the polling example, the time refreshes every 3-7 seconds.

I'm using a Windows PC on the same network to ping:

I tested the lwip_httpsrv example, and the response was significantly faster. 

Best regards,
Pablo

[DanielRuvalcaba · Accepted solution]

Hi,

I tested the wifi_httpsrv example, and it works correctly without any lag.
When I enter 192.168.137.18 in the browser, the page loads almost immediately. The polling examples refreshes every second.
I also pinged the board several times and experienced no packet loss.

FRDM-RW612: 

Starting httpsrv DEMO
[i] Initializing Wi-Fi connection...
STA MAC Address: C0:59:DB:22:53:8D
board_type: 2, board_type mapping:
0----QFN
1----CSP
2----BGA
[i] Successfully initialized Wi-Fi module
Connecting as client to ssid: AP_BS with password 12345678
[i] Connected to Wi-Fi
ssid: AP_BS
[!]passphrase: 12345678
 Now join that network on your device and connect to this IP: 192.168.137.18

***********************************************************
 HTTP Server example
***********************************************************
 IPv4 Address     : 192.168.137.18
 IPv4 Subnet mask : 255.255.255.0
 IPv4 Gateway     : 192.168.137.1
 IPv6 Address0    : FE80::C295:DAFF:FE01:557D
 IPv6 Address1    : -
 IPv6 Address2    : -
 mDNS hostname    : wifi-http
***********************************************************

Ready

PC:

PS C:\> ping 192.168.137.18 -n 30

Pinging 192.168.137.18 with 32 bytes of data:
Reply from 192.168.137.18: bytes=32 time=20ms TTL=255
Reply from 192.168.137.18: bytes=32 time=22ms TTL=255
Reply from 192.168.137.18: bytes=32 time=9ms TTL=255
Reply from 192.168.137.18: bytes=32 time=128ms TTL=255
Reply from 192.168.137.18: bytes=32 time=97ms TTL=255
Reply from 192.168.137.18: bytes=32 time=112ms TTL=255
Reply from 192.168.137.18: bytes=32 time=113ms TTL=255
Reply from 192.168.137.18: bytes=32 time=107ms TTL=255
Reply from 192.168.137.18: bytes=32 time=78ms TTL=255
Reply from 192.168.137.18: bytes=32 time=49ms TTL=255
Reply from 192.168.137.18: bytes=32 time=62ms TTL=255
Reply from 192.168.137.18: bytes=32 time=87ms TTL=255
Reply from 192.168.137.18: bytes=32 time=67ms TTL=255
Reply from 192.168.137.18: bytes=32 time=108ms TTL=255
Reply from 192.168.137.18: bytes=32 time=21ms TTL=255
Reply from 192.168.137.18: bytes=32 time=149ms TTL=255
Reply from 192.168.137.18: bytes=32 time=46ms TTL=255
Reply from 192.168.137.18: bytes=32 time=67ms TTL=255
Reply from 192.168.137.18: bytes=32 time=70ms TTL=255
Reply from 192.168.137.18: bytes=32 time=81ms TTL=255
Reply from 192.168.137.18: bytes=32 time=117ms TTL=255
Reply from 192.168.137.18: bytes=32 time=105ms TTL=255
Reply from 192.168.137.18: bytes=32 time=116ms TTL=255
Reply from 192.168.137.18: bytes=32 time=109ms TTL=255
Reply from 192.168.137.18: bytes=32 time=24ms TTL=255
Reply from 192.168.137.18: bytes=32 time=107ms TTL=255
Reply from 192.168.137.18: bytes=32 time=128ms TTL=255
Reply from 192.168.137.18: bytes=32 time=122ms TTL=255
Reply from 192.168.137.18: bytes=32 time=183ms TTL=255
Reply from 192.168.137.18: bytes=32 time=414ms TTL=255

Ping statistics for 192.168.137.18:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 9ms, Maximum = 414ms, Average = 97ms
PS C:\>

I believe the issue is not with the RW612 or the example, but rather with your network. It might be congested, experiencing interference, or there could be a configuration on the access point causing the lag. Please try connecting to a different AP and test again.

Regards,
Daniel.

[etronic_arg]

Thank you for testing it!

I will try it on another router; however, I don’t have speed issues when I use my smartphone on the same network in the same position.
I located the boards right beside the router and it improves a little:

d:\>ping -t 192.168.201.226

Pinging 192.168.201.226 with 32 bytes of data:
Reply from 192.168.201.226: bytes=32 time=104ms TTL=255
Reply from 192.168.201.226: bytes=32 time=147ms TTL=255
Reply from 192.168.201.226: bytes=32 time=127ms TTL=255
Reply from 192.168.201.226: bytes=32 time=124ms TTL=255
Reply from 192.168.201.226: bytes=32 time=121ms TTL=255
Reply from 192.168.201.226: bytes=32 time=136ms TTL=255
Reply from 192.168.201.226: bytes=32 time=127ms TTL=255
Reply from 192.168.201.226: bytes=32 time=224ms TTL=255
Reply from 192.168.201.226: bytes=32 time=136ms TTL=255
Reply from 192.168.201.226: bytes=32 time=108ms TTL=255
Reply from 192.168.201.226: bytes=32 time=382ms TTL=255
Reply from 192.168.201.226: bytes=32 time=132ms TTL=255
Reply from 192.168.201.226: bytes=32 time=130ms TTL=255
Reply from 192.168.201.226: bytes=32 time=119ms TTL=255
Reply from 192.168.201.226: bytes=32 time=285ms TTL=255
Reply from 192.168.201.226: bytes=32 time=196ms TTL=255
Reply from 192.168.201.226: bytes=32 time=159ms TTL=255
Reply from 192.168.201.226: bytes=32 time=137ms TTL=255
Request timed out.
Reply from 192.168.201.226: bytes=32 time=1653ms TTL=255
Reply from 192.168.201.226: bytes=32 time=464ms TTL=255
Reply from 192.168.201.226: bytes=32 time=161ms TTL=255
Reply from 192.168.201.226: bytes=32 time=200ms TTL=255
Reply from 192.168.201.226: bytes=32 time=371ms TTL=255
Reply from 192.168.201.226: bytes=32 time=156ms TTL=255
Reply from 192.168.201.226: bytes=32 time=114ms TTL=255
Reply from 192.168.201.226: bytes=32 time=259ms TTL=255
Reply from 192.168.201.226: bytes=32 time=221ms TTL=255
Reply from 192.168.201.226: bytes=32 time=221ms TTL=255
Reply from 192.168.201.226: bytes=32 time=262ms TTL=255
Reply from 192.168.201.226: bytes=32 time=169ms TTL=255
Reply from 192.168.201.226: bytes=32 time=19ms TTL=255
Reply from 192.168.201.226: bytes=32 time=164ms TTL=255
Reply from 192.168.201.226: bytes=32 time=91ms TTL=255
Reply from 192.168.201.226: bytes=32 time=135ms TTL=255
Reply from 192.168.201.226: bytes=32 time=106ms TTL=255
Reply from 192.168.201.226: bytes=32 time=4ms TTL=255
Reply from 192.168.201.226: bytes=32 time=112ms TTL=255
Reply from 192.168.201.226: bytes=32 time=79ms TTL=255
Reply from 192.168.201.226: bytes=32 time=19ms TTL=255
Reply from 192.168.201.226: bytes=32 time=217ms TTL=255
Reply from 192.168.201.226: bytes=32 time=76ms TTL=255
Reply from 192.168.201.226: bytes=32 time=79ms TTL=255
Reply from 192.168.201.226: bytes=32 time=164ms TTL=255
Reply from 192.168.201.226: bytes=32 time=120ms TTL=255
Reply from 192.168.201.226: bytes=32 time=14ms TTL=255
Reply from 192.168.201.226: bytes=32 time=86ms TTL=255
Request timed out.
Reply from 192.168.201.226: bytes=32 time=1114ms TTL=255
Reply from 192.168.201.226: bytes=32 time=20ms TTL=255
Reply from 192.168.201.226: bytes=32 time=104ms TTL=255
Reply from 192.168.201.226: bytes=32 time=114ms TTL=255
Request timed out.
Reply from 192.168.201.226: bytes=32 time=509ms TTL=255
Reply from 192.168.201.226: bytes=32 time=129ms TTL=255
Request timed out.
Reply from 192.168.201.226: bytes=32 time=3341ms TTL=255
Reply from 192.168.201.226: bytes=32 time=2ms TTL=255
Reply from 192.168.201.226: bytes=32 time=17ms TTL=255
Reply from 192.168.201.226: bytes=32 time=45ms TTL=255
Reply from 192.168.201.226: bytes=32 time=131ms TTL=255
Reply from 192.168.201.226: bytes=32 time=108ms TTL=255
Reply from 192.168.201.226: bytes=32 time=216ms TTL=255
Reply from 192.168.201.226: bytes=32 time=89ms TTL=255
Reply from 192.168.201.226: bytes=32 time=227ms TTL=255
Reply from 192.168.201.226: bytes=32 time=111ms TTL=255
Reply from 192.168.201.226: bytes=32 time=124ms TTL=255
Reply from 192.168.201.226: bytes=32 time=122ms TTL=255
Request timed out.
Reply from 192.168.201.226: bytes=32 time=70ms TTL=255
Reply from 192.168.201.226: bytes=32 time=122ms TTL=255
Reply from 192.168.201.226: bytes=32 time=169ms TTL=255
Reply from 192.168.201.226: bytes=32 time=140ms TTL=255
Reply from 192.168.201.226: bytes=32 time=153ms TTL=255
Reply from 192.168.201.226: bytes=32 time=58ms TTL=255
Reply from 192.168.201.226: bytes=32 time=159ms TTL=255
Reply from 192.168.201.226: bytes=32 time=197ms TTL=255
Reply from 192.168.201.226: bytes=32 time=113ms TTL=255
Reply from 192.168.201.226: bytes=32 time=77ms TTL=255
Reply from 192.168.201.226: bytes=32 time=84ms TTL=255
Reply from 192.168.201.226: bytes=32 time=63ms TTL=255
Reply from 192.168.201.226: bytes=32 time=96ms TTL=255
Reply from 192.168.201.226: bytes=32 time=70ms TTL=255
Reply from 192.168.201.226: bytes=32 time=244ms TTL=255
Reply from 192.168.201.226: bytes=32 time=99ms TTL=255
Reply from 192.168.201.226: bytes=32 time=199ms TTL=255
Reply from 192.168.201.226: bytes=32 time=172ms TTL=255
Reply from 192.168.201.226: bytes=32 time=118ms TTL=255
Request timed out.

Ping statistics for 192.168.201.226:
    Packets: Sent = 89, Received = 83, Lost = 6 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 3341ms, Average = 211ms

Just to confirm:

1. Although I am using the UBlox Maya W2 module, the configuration should be WIFI_IW612_BOARD_MURATA_2EL_USD?

2. The firmware used is sduart_nw61x.bin.se.inc, however I found that there is a version V1:
https://github.com/nxp-imx/imx-firmware/tree/lf-6.12.34_2.1.0/nxp/FwImage_IW612_SD
Should it work with the original?

3. Is there a way to configurate the output power?

Thanks.

[DanielRuvalcaba]

Hi,

Are you using EVK-MAYA-W276 or MAYA-W271?

Do you have an external antenna connected to the module?

There is no need to get the firmware binary from the GitHub repo. This step is usually for the i.MX processor family, not i.MX RT since the example already includes the binary.

If you still finding issues, I will try tomorrow with the RT1064.

Regards,
Daniel.

[etronic_arg]

Hello Daniel,

I changed the router, and everything started to work.
I don't understand why the other router works well with the cellphone but no with the IW612.
Anyway, that’s not our concern.
Thank you for your help.

Best regards,
Pablo