twt setup: wrong parameter count

RE: twt setup: wrong parameter count

Håkon Alseth — Fri, 13 Dec 2024 14:26:01 GMT

Have you tried updating to OpenWrt 23.05 and see if the issue persists?

Kind regards,

Håkon

RE: twt setup: wrong parameter count

ChengQing Zhao — Thu, 12 Dec 2024 15:32:11 GMT

Hi, my ap is GliNet, system is from OpenWrt R22.3.3 (Powered by LuCI Master (git-22.060.11889-fb941f7) / OpenWrt R22.3.3).

NCS v2.7.0

under your help, i try to find the problem

I change the sixth parameter <trigger:0/1> to 0

wifi twt setup 0 0 2 2 0 0 1 1 20000 100000 0

that seems work well, but still some error in the log when i input the "wifi status":

uart:~$ > wifi twt setup 0 0 2 2 0 0 1 1 20000 100000 0
wifi twt setup 0 0 2 2 0 0 1 1 20000 100000 0
TWT operation TWT setup with dg: 2, flow_id: 2 requested
TWT response: TWT accept
== TWT negotiated parameters ==
TWT Dialog token: 2
TWT flow ID: 1
TWT negotiation type: TWT individual negotiation
TWT responder: true
TWT implicit: true
TWT announce: true
TWT trigger: false
TWT wake interval: 19968 us
TWT interval: 100000 us
========================
uart:~$ > wifi status
wifi status
Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 6 (802.11ax/HE)
SSID: OpenWrt
BSSID: 94:83:C4:1F:05:DA
Band: 5GHz
Channel: 36
Security: WPA2-PSK
MFP: Optional
RSSI: -9999
Beacon Interval: 100
DTIM: 1
TWT: Supported
[00:08:29.909,057] <err> wifi_nrf: nrf_wifi_wpa_supp_signal_poll: Failed to get interface info, ret = -11
[00:08:29.909,088] <err> wpa_supp: wpa_drv_zep_signal_poll: Signal polling failed: -1

[00:08:29.909,820] <err> wpa_supp: Command failed: FAIL
[00:08:29.909,851] <wrn> wpa_supp: z_wpa_supplicant_status:Failed to read RSSI

uart:~$ > net ping 192.168.6.1
net ping 192.168.6.1
PING 192.168.6.1
28 bytes from 192.168.6.1 to 192.168.6.192: icmp_seq=1 ttl=64 time=12 ms
28 bytes from 192.168.6.1 to 192.168.6.192: icmp_seq=2 ttl=64 time=11 ms
28 bytes from 192.168.6.1 to 192.168.6.192: icmp_seq=3 ttl=64 time=12 ms
uart:~$

RE: twt setup: wrong parameter count

Håkon Alseth — Thu, 12 Dec 2024 14:46:20 GMT

Hi,

I tried both your configurations successfully against a ASUS RT-AX1800U running OpenWrt v23.05:

*** Using nRF Connect SDK v2.8.0-a2386bfc8401 ***
*** Using Zephyr OS v3.7.99-0bc3393fb112 ***
Starting nrf7002dk with CPU frequency: 128 MHz
[00:00:00.699,462] <inf> wifi_supplicant: wpa_supplicant initialized
uart:~$ 
uart:~$ wifi connect -s OpenWrt -k 1 -p mypassword
Connection requested
Connected
[00:01:49.010,589] <inf> wpa_supp: wlan0: SME: Trying to authenticate with fc:34:97:0b:f6:dc (SSID='OpenWrt' freq=5180)
[00:01:49.368,438] <inf> wpa_supp: wlan0: Trying to associate with fc:34:97:0b:f6:dc (SSID='OpenWrt' freq=5180 MHz)
[00:01:49.387,084] <inf> wpa_supp: wlan0: Associated with fc:34:97:0b:f6:dc
[00:01:49.387,268] <inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:01:49.398,681] <inf> wpa_supp: wlan0: WPA: Key negotiation completed with fc:34:97:0b:f6:dc [PTK=CCMP GTK=TKIP]
[00:01:49.398,895] <inf> wpa_supp: wlan0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:0b:f6:dc completed [id=0 id_st]
uart:~$ wifi twt setup 0 0 2 2 0 1 1 1 20000 100000 0
TWT operation TWT setup with dg: 2, flow_id: 2 requested
TWT response: TWT accept
== TWT negotiated parameters ==
TWT Dialog token: 2
TWT flow ID: 0
TWT negotiation type: TWT individual negotiation
TWT responder: true
TWT implicit: true
TWT announce: true
TWT trigger: true
TWT wake interval: 19968 us
TWT interval: 100000 us
========================
[00:01:52.413,513] <inf> net_dhcpv4: Received: 192.168.32.196
uart:~$ net ping 8.8.8.8
PING 8.8.8.8
28 bytes from 8.8.8.8 to 192.168.32.196: icmp_seq=1 ttl=54 time=130 ms
28 bytes from 8.8.8.8 to 192.168.32.196: icmp_seq=2 ttl=54 time=131 ms
28 bytes from 8.8.8.8 to 192.168.32.196: icmp_seq=3 ttl=54 time=133 ms
uart:~$ net ping 8.8.8.8
PING 8.8.8.8
28 bytes from 8.8.8.8 to 192.168.32.196: icmp_seq=1 ttl=54 time=121 ms
28 bytes from 8.8.8.8 to 192.168.32.196: icmp_seq=2 ttl=54 time=124 ms
28 bytes from 8.8.8.8 to 192.168.32.196: icmp_seq=3 ttl=54 time=125 ms
uart:~$ wifi twt tear
  teardown      teardown_all
uart:~$ wifi twt teardown_all 
TWT teardown succeeded for flow ID 0
TWT operation TWT teardown all flows success
uart:~$ wifi twt setup 0 0 2 2 0 1 1 1 200000 1000000 0
TWT operation TWT setup with dg: 2, flow_id: 2 requested
TWT response: TWT reject
== TWT negotiated parameters ==
TWT Dialog token: 2
TWT flow ID: 2
TWT negotiation type: TWT individual negotiation
TWT responder: false
TWT implicit: true
TWT announce: true
TWT trigger: true
TWT wake interval: 199680 us
TWT interval: 1000000 us
========================
uart:~$ net ping 8.8.8.8
PING 8.8.8.8
28 bytes from 8.8.8.8 to 192.168.32.196: icmp_seq=1 ttl=54 time=64 ms
28 bytes from 8.8.8.8 to 192.168.32.196: icmp_seq=2 ttl=54 time=54 ms
28 bytes from 8.8.8.8 to 192.168.32.196: icmp_seq=3 ttl=54 time=66 ms
uart:~$ net ping 8.8.8.8
PING 8.8.8.8
28 bytes from 8.8.8.8 to 192.168.32.196: icmp_seq=1 ttl=54 time=57 ms
28 bytes from 8.8.8.8 to 192.168.32.196: icmp_seq=2 ttl=54 time=59 ms
28 bytes from 8.8.8.8 to 192.168.32.196: icmp_seq=3 ttl=54 time=141 ms

I am using NCS v2.8.0, completely unchanged wifi/shell sample. Which access point are you using? It could be that the timing parameters given for TWT is problematic for the AP that you're using?

Kind regards,

Håkon

RE: twt setup: wrong parameter count

ChengQing Zhao — Thu, 12 Dec 2024 02:45:34 GMT

Hi, i am try it again:

wifi twt setup 0 0 2 2 0 1 1 1 200000 1000000 0

and

wifi twt setup 0 0 2 2 0 1 1 1 20000 100000 0

are all not ok. it still can not ping.

the log is:

> wifi connect -s "OpenWrt" -p "12345678" -k 1
wifi connect -s "OpenWrt" -p "12345678" -k 1
Connection requested
Connected
[00:00:34.554,504] <inf> wpa_supp: nordic_wlan0: SME: Trying to authenticate with 94:83:c4:1f:05:da (SSID='OpenWrt' freq=5180 MHz)
[00:00:34.804,779] <inf> wpa_supp: nordic_wlan0: Trying to associate with 94:83:c4:1f:05:da (SSID='OpenWrt' freq=5180 MHz)
[00:00:34.822,967] <inf> wpa_supp: nordic_wlan0: Associated with 94:83:c4:1f:05:da
[00:00:34.823,150] <inf> wpa_supp: nordic_wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:00:34.836,517] <inf> wpa_supp: nordic_wlan0: WPA: Key negotiation completed with 94:83:c4:1f:05:da [PTK=CCMP GTK=CCMP]
[00:00:34.836,730] <inf> wpa_supp: nordic_wlan0: CTRL-EVENT-CONNECTED - Connection to 94:83:c4:1f:05:da completed [id=0 id_str=]
[00:00:37.957,916] <inf> net_dhcpv4: Received: 192.168.6.192
uart:~$ > wifi twt setup 0 0 2 2 0 1 1 1 20000 100000 0
wifi twt setup 0 0 2 2 0 1 1 1 20000 100000 0
TWT operation TWT setup with dg: 2, flow_id: 2 requested
TWT response: TWT accept
== TWT negotiated parameters ==
TWT Dialog token: 2
TWT flow ID: 1
TWT negotiation type: TWT individual negotiation
TWT responder: true
TWT implicit: true
TWT announce: true
TWT trigger: true
TWT wake interval: 19968 us
TWT interval: 100000 us
========================
uart:~$ > net ping 192.168.6.1
net ping 192.168.6.1
PING 192.168.6.1
Ping timeout
uart:~$ > wifi twt setup 0 0 2 2 0 1 1 1 200000 1000000 0
wifi twt setup 0 0 2 2 0 1 1 1 200000 1000000 0
TWT operation TWT setup with dg: 2, flow_id: 2 requested
[00:02:48.167,022] <err> wifi_nrf: nrf_wifi_wpa_supp_signal_poll: Failed to get interface info, ret = -11
[00:02:48.167,053] <err> wpa_supp: wpa_drv_zep_signal_poll: Signal polling failed: -1

[00:02:48.167,785] <err> wpa_supp: Command failed: FAIL
[00:02:48.167,816] <wrn> wpa_supp: z_wpa_supplicant_status:Failed to read RSSI

uart:~$ > wifi twt teardown_all
wifi twt teardown_all
TWT teardown succeeded for flow ID 1
TWT operation TWT teardown all flows success
uart:~$ > wifi twt setup 0 0 2 2 0 1 1 1 200000 1000000 0
wifi twt setup 0 0 2 2 0 1 1 1 200000 1000000 0
TWT operation TWT setup with dg: 2, flow_id: 2 requested
TWT response: TWT accept
== TWT negotiated parameters ==
TWT Dialog token: 2
TWT flow ID: 1
TWT negotiation type: TWT individual negotiation
TWT responder: true
TWT implicit: true
TWT announce: true
TWT trigger: true
TWT wake interval: 49920 us
TWT interval: 1000000 us
========================
uart:~$ > net ping 192.168.6.1
net ping 192.168.6.1
PING 192.168.6.1
Ping timeout
uart:~$ > wifi twt teardown_all
wifi twt teardown_all
TWT teardown succeeded for flow ID 1
TWT operation TWT teardown all flows success
uart:~$ > wifi status
wifi status
Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 6 (802.11ax/HE)
SSID: OpenWrt
BSSID: 94:83:C4:1F:05:DA
Band: 5GHz
Channel: 36
Security: WPA2-PSK
MFP: Optional
RSSI: -39
Beacon Interval: 100
DTIM: 1
TWT: Supported
uart:~$ > net ping 192.168.6.1
net ping 192.168.6.1
PING 192.168.6.1
28 bytes from 192.168.6.1 to 192.168.6.192: icmp_seq=1 ttl=64 time=202 ms
28 bytes from 192.168.6.1 to 192.168.6.192: icmp_seq=2 ttl=64 time=8 ms
28 bytes from 192.168.6.1 to 192.168.6.192: icmp_seq=3 ttl=64 time=11 ms
uart:~$

RE: twt setup: wrong parameter count

Håkon Alseth — Wed, 11 Dec 2024 11:53:58 GMT

[quote user="ChengQing Zhao"]TWT wake interval: 9984 us[/quote]

Set the wake interval to >20000 us, and retry. Your current wake interval is too low.

Kind regards,

Håkon

RE: twt setup: wrong parameter count

ChengQing Zhao — Wed, 11 Dec 2024 09:05:17 GMT

OK， I see， what I want to do is to prove twt not better than dtim mode. if it is not can set 100ms, how can I prove it?

because of the most of the device default value is 100ms.

RE: twt setup: wrong parameter count

Håkon Alseth — Wed, 11 Dec 2024 08:46:57 GMT

Hi,

[quote user="ChengQing Zhao"]TWT wake interval: 9984 us
TWT interval: 100000 us[/quote]

Try setting the wake interval higher, for instance 20000 us.

You are using a TWT interval of 0.1 seconds, which is very low. It does not make sense to use it with such a low period, it is then better to use DTIM/Listen_interval.

Kind regards,

Håkon

RE: twt setup: wrong parameter count

ChengQing Zhao — Tue, 10 Dec 2024 18:26:28 GMT

Thank you, Håkon Alseth.

I run Zperf successfully. But I have a new question as the log shows:

when I change to TWT mode, nRF7002-DK can not even ping the server.

uart:~$ > wifi connect -s "OpenWrt" -p "12345678" -k 1
wifi connect -s "OpenWrt" -p "12345678" -k 1
Connection requested
Connected
[00:00:42.920,135] <inf> wpa_supp: nordic_wlan0: SME: Trying to authenticate with 94:83:c4:1f:05:da (SSID='OpenWrt' freq=5180 MHz)
[00:00:43.171,142] <inf> wpa_supp: nordic_wlan0: Trying to associate with 94:83:c4:1f:05:da (SSID='OpenWrt' freq=5180 MHz)
[00:00:43.184,265] <inf> wpa_supp: nordic_wlan0: Associated with 94:83:c4:1f:05:da
[00:00:43.184,356] <inf> wpa_supp: nordic_wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:00:43.194,274] <inf> wpa_supp: nordic_wlan0: WPA: Key negotiation completed with 94:83:c4:1f:05:da [PTK=CCMP GTK=CCMP]
[00:00:43.194,427] <inf> wpa_supp: nordic_wlan0: CTRL-EVENT-CONNECTED - Connection to 94:83:c4:1f:05:da completed [id=0 id_str=]
[00:00:43.203,948] <inf> net_dhcpv4: Received: 192.168.6.192
[00:00:43.204,010] <inf> net_config: IPv4 address: 192.168.6.192
[00:00:43.204,010] <inf> net_config: Lease time: 43200 seconds
[00:00:43.204,010] <inf> net_config: Subnet: 255.255.255.0
[00:00:43.204,040] <inf> net_config: Router: 192.168.6.1
uart:~$ > wifi status
wifi status
Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 6 (802.11ax/HE)
SSID: OpenWrt
BSSID: 94:83:C4:1F:05:DA
Band: 5GHz
Channel: 36
Security: WPA2-PSK
MFP: Optional
RSSI: -43
Beacon Interval: 100
DTIM: 1
TWT: Supported
uart:~$ > net ping 192.168.6.118
net ping 192.168.6.118
PING 192.168.6.118
28 bytes from 192.168.6.118 to 192.168.6.192: icmp_seq=1 ttl=64 time=12 ms
28 bytes from 192.168.6.118 to 192.168.6.192: icmp_seq=2 ttl=64 time=10 ms
28 bytes from 192.168.6.118 to 192.168.6.192: icmp_seq=3 ttl=64 time=11 ms
uart:~$ > zperf tcp upload 192.168.6.118 5001 10 1K 5M
zperf tcp upload 192.168.6.118 5001 10 1K 5M
Remote port is 5001
Connecting to 192.168.6.118
TCP upload will ignore <baud rate> argument
Duration: 10.00 s
Packet size: 1000 bytes
Rate: 5000 kbps
Starting...
-
Upload completed!
Duration: 10.00 s
Num packets: 19276
Num errors: 0 (retry or fail)
Rate: 15.42 Mbps
uart:~$ > wifi twt setup 0 0 2 2 0 1 1 1 10000 100000 0
wifi twt setup 0 0 2 2 0 1 1 1 10000 100000 0
TWT operation TWT setup with dg: 2, flow_id: 2 requested
TWT response: TWT accept
== TWT negotiated parameters ==
TWT Dialog token: 2
TWT flow ID: 1
TWT negotiation type: TWT individual negotiation
TWT responder: false
TWT implicit: true
TWT announce: true
TWT trigger: true
TWT wake interval: 9984 us
TWT interval: 100000 us
========================
uart:~$ > net ping 192.168.6.118
net ping 192.168.6.118
PING 192.168.6.118
Ping timeout

RE: twt setup: wrong parameter count

Håkon Alseth — Mon, 25 Nov 2024 08:09:14 GMT

Hi,

Click button "Add extra fragment" - then select the file "overlay-zperf.conf", and click "OK".

It should then look like this:

[quote user="ChengQing Zhao"]Yes, twt example seem to give another way, but it can not set DTIM mode, i want to compare the throughput under DTIM and TWT, so, i think zperf is more simple and flexible.[/quote]

DTIM is enabled by default. The nrf7002 will follow what is set by the access point.

Kind regards,

Håkon

RE: twt setup: wrong parameter count

ChengQing Zhao — Fri, 22 Nov 2024 16:48:57 GMT

Thank you Håkon Alseth, Wi-Fi:Shell example is seem already include "overlay-zperf.conf", as shown in the picture.

[quote userid="2115" url="~/f/nordic-q-a/116014/twt-setup-wrong-parameter-count/511714"]In order to add zperf to the wifi/shell sample, you need to append the "overlay-zperf.conf" to your sample.[/quote]

Yes, that is my question, i am sorry. thank you for your guidance

[quote userid="2115" url="~/f/nordic-q-a/116014/twt-setup-wrong-parameter-count/511714"]Which example is this based on? The command should be "wifi twt" if you are using the wifi/shell.[/quote]

Yes, twt example seem to give another way, but it can not set DTIM mode, i want to compare the throughput under DTIM and TWT, so, i think zperf is more simple and flexible.

[quote userid="2115" url="~/f/nordic-q-a/116014/twt-setup-wrong-parameter-count/511714"]

Have you had a look at the twt sample? it includes a way to generate traffic to the device:

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/wifi/twt/README.html

[/quote]

RE: twt setup: wrong parameter count

Håkon Alseth — Fri, 22 Nov 2024 15:24:03 GMT

Hi,

In order to add zperf to the wifi/shell sample, you need to append the "overlay-zperf.conf" to your sample.

[quote user="ChengQing Zhao"]uart:~$ > twt
twt
twt: command not found[/quote]

Which example is this based on? The command should be "wifi twt" if you are using the wifi/shell.

Have you had a look at the twt sample? it includes a way to generate traffic to the device:

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/wifi/twt/README.html

Kind regards,

Håkon

RE: twt setup: wrong parameter count

ChengQing Zhao — Thu, 21 Nov 2024 17:57:44 GMT

I find the throughput example, zperf command is ok, but it can not set TWT mode, as shown in the log.

So, i do not know how to run iperf under TWT and DTIM mode, i want to test the performance under this two save power mode, can you give some help, thank you very much!

uart:~$ > zperf
zperf
zperf - Zperf commands
Subcommands:
connectap : Connect to AP
setip : Set IP address
<my ip> <prefix len>
Example setip 2001:db8::2 64
Example setip 192.0.2.2

tcp : Upload/Download TCP data
udp : Upload/Download UDP data
version : Zperf version
uart:~$ > twt
twt
twt: command not found
uart:~$

RE: twt setup: wrong parameter count

ChengQing Zhao — Thu, 21 Nov 2024 17:36:53 GMT

Thank you Håkon Alseth, i am sorry so late to reply to you, it is run ok now, but i meet a new question, how can i run iperf on the TWT mode and DTIM mode by the nRF7002-DK.

As you can see the log below, there is no zperf command.

uart:~$ > wifi twt teardown_all
wifi twt teardown_all
TWT teardown succeeded for flow ID 1
TWT operation TWT teardown all flows success
uart:~$ > wifi twt setup 0 0 2 2 0 1 1 1 20000 60000000 0
wifi twt setup 0 0 2 2 0 1 1 1 20000 60000000 0
TWT operation TWT setup with dg: 2, flow_id: 2 requested
TWT response: TWT accept
== TWT negotiated parameters ==
TWT Dialog token: 2
TWT flow ID: 1
TWT negotiation type: TWT individual negotiation
TWT responder: true
TWT implicit: true
TWT announce: true
TWT trigger: true
TWT wake interval: 19968 us
TWT interval: 60030000 us
========================
uart:~$ > zperf
zperf
zperf: command not found

RE: twt setup: wrong parameter count

Håkon Alseth — Fri, 08 Nov 2024 14:39:00 GMT

Hi,

My apologies for missing this.

[quote user="ChengQing Zhao"]
uart:~$ > wifi twt setup 0 0 2 2 0 1 1 1 20 60000 0
wifi twt setup 0 0 2 2 0 1 1 1 20 60000 0
TWT setup with TWT individual negotiation failed. reason : Pe[/quote]

In previous SDK versions, the intervals were given in milliseconds, while in newer versions; it is given in microseconds for setting a more accurate resolution.

Try to send 20000 instead.

To maintain the twt_interval to 1 minute (60 seconds), the "60000" (60*1000 ms) need to be changed to 60000000.

Kind regards,

Håkon

RE: twt setup: wrong parameter count

ChengQing Zhao — Fri, 08 Nov 2024 07:36:54 GMT

Thank you for your prompt response, Håkon Alseth, i think the router is support TWT, the log as follow,

and the command "wifi twt setup 0 0 1 1 0 1 1 1 65000 524000 0" is ok

but why “wifi twt setup 0 0 2 2 0 1 1 1 20 60000 0 ” from https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/target-wake-time-on-the-nrf7002-dk

can not set TWT.

the the log as follow：

uart:~$ > wifi status
wifi status
Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 6 (802.11ax/HE)
SSID: OpenWrt_1F05DA_5G
BSSID: 94:83:C4:1F:05:DA
Band: 5GHz
Channel: 36
Security: WPA2-PSK
MFP: Optional
RSSI: -42
Beacon Interval: 100
DTIM: 1
TWT: Supported
uart:~$ > wifi twt setup 0 0 1 1 0 1 1 1 65000 524000
wifi twt setup 0 0 1 1 0 1 1 1 65000 524000
setup: wrong parameter count
setup - Start a TWT flow:
<negotiation_type, 0: Individual, 1: Broadcast, 2: Wake TBTT>
<setup_cmd: 0: Request, 1: Suggest, 2: Demand>
<dialog_token: 1-255> <flow_id: 0-7> <responder: 0/1> <trigger: 0/1>
<implicit:0/1> <announce: 0/1> <twt_wake_interval: 1-262144us>
<twt_interval: 1us-2^31us>.
<twt_wake_ahead_duration>: 0us-2^31us>

uart:~$ > wifi twt setup 0 0 1 1 0 1 1 1 65000 524000 0
wifi twt setup 0 0 1 1 0 1 1 1 65000 524000 0
TWT operation TWT setup with dg: 1, flow_id: 1 requested
TWT response: TWT accept
== TWT negotiated parameters ==
TWT Dialog token: 1
TWT flow ID: 1
TWT negotiation type: TWT individual negotiation
TWT responder: true
TWT implicit: true
TWT announce: true
TWT trigger: true
TWT wake interval: 65024 us
TWT interval: 524000 us
========================
uart:~$ > wifi twt setup 0 0 2 2 0 1 1 1 20 60000 0
wifi twt setup 0 0 2 2 0 1 1 1 20 60000 0
TWT setup with TWT individual negotiation failed. reason : Peer not TWT capable
[00:03:27.207,946] <err> wifi_nrf: nrf_wifi_wpa_supp_signal_poll: Failed to get station info, ret = -11
[00:03:27.207,977] <err> wpa_supp: wpa_drv_zep_signal_poll: Signal polling failed: -1

[00:03:27.208,679] <err> wpa_supp: Command failed: FAIL
[00:03:27.208,709] <wrn> wpa_supp: z_wpa_supplicant_status:Failed to read RSSI

[00:03:32.210,510] <err> wifi_nrf: nrf_wifi_supp_get_conn_info: Timeout: failed to get connection info, ret = -11
[00:03:32.211,303] <err> wpa_supp: wpa_drv_zep_get_conn_info: Failed to get connection info: -1

[00:03:32.211,425] <wrn> wpa_supp: z_wpa_supplicant_status: Failed to get connection

RE: twt setup: wrong parameter count

Håkon Alseth — Fri, 01 Nov 2024 10:23:40 GMT

Hi,

[quote user="ChengQing Zhao"]TWT setup with TWT individual negotiation failed. reason : Peer not TWT capable[/quote]

This means that the AP is not capable of TWT. Which access point specifically are you using? If it is wifi 6 capable, it might be that you need to enable Target Wake Time specifically in the router web UI.

Kind regards,

Håkon

RE: twt setup: wrong parameter count

ChengQing Zhao — Fri, 01 Nov 2024 09:36:47 GMT

Thank you H å kon Alseth for your prompt response. I have encountered a new issue again, as you provided. I added 0 at the end, but still cannot negotiate successfully.

The command comes from the blog：

https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/target-wake-time-on-the-nrf7002-dk

The log print as:

uart:~$ > wifi twt setup 0 0 2 2 0 1 1 1 20 60000 0
wifi twt setup 0 0 2 2 0 1 1 1 20 60000 0
TWT setup with TWT individual negotiation failed. reason : Peer not TWT capable
[02:19:52.113,739] <inf> wpa_supp: nordic_wlan0: WPA: Group rekeying completed with 94:83:c4:1f:05:da [GTK=TKIP]
uart:~$

RE: twt setup: wrong parameter count

Håkon Alseth — Fri, 01 Nov 2024 08:50:54 GMT

Hi,

There was a new addition to the twt command in wifi/shell, which is the last parameter:

[quote user=""]

<twt_wake_ahead_duration>: 0us-2^31us>

[/quote]

You can set this to '0' if you want.

Another tip is to use the wifi/twt sample as well for evaluation of this power saving feature.

Kind regards,

Håkon