After enabling TWT power save, the client only sends PS-Poll frames

[Naveen Pyda]

We are using the Nordic Semiconductor nRF7002-DK. In this board, both PS-Poll and No-PS-Poll power-saving modes are working as expected. However, when running in TWT (Target Wake Time) power mode using the following command:-wifi twt setup 0 0 1 0 0 0 1 1 10000 1000000 100, the client does not enter sleep mode as expected. Both the AP and client exchange TWT request and TWT accept packets; however, after that, the client sends only PS-Poll frames.

Applications Versions: 

1. nRF connection Desktop v5.2.0
2. Toolchain Manager v1.6.0
3. nRF connect SDK v2.9.2
4. Visual studio code
5. Windows 11 pro Platform

Please find the attached PCaps and screenshot for your reference.

https://drive.google.com/file/d/1H2-U1TbJMtUYYoJxIF3my1jbIpdYBWpn/view?usp=sharing

Thanks & Regards,

Naveen P

[Amanda Hsieh]

Hi, 

TWT connection established is with flow type announced and no Trigger enabled. 

Nordic STA sends PS poll for every wake up to inform AP since TWT connection is announced with trigger disabled.

This is expected behaviour after every warm boot.

Are you sure DK is not entering in to sleep? You can take a look at this course: https://academy.nordicsemi.com/courses/wi-fi-fundamentals/lessons/lesson-2-wifi-fundamentals/topic/lesson-2-exercise-1-2/ 

-Amanda H.

[Naveen Pyda]

Hi Amsnda,

As you advised, we followed this guide (https://academy.nordicsemi.com/courses/wi-fi-fundamentals/lessons/lesson-2-wifi-fundamentals/topic/lesson-2-exercise-1-2/), but we are facing the issue 'Wi-Fi interface not up'.

Please find the attached screenshot for your reference.

While adding the build configuration, it is asking for some options. Could you please suggest which options we need to provide?

Please find the attached screenshot for your reference.

Thanks & Regards,

Naveen P

[Amanda Hsieh]

Hi, 

Just found that this case is a duplicate of this one The client does not enter sleep mode as expected, and my colleague is working on your case. Please continue the discussion in that case, and don't duplicate support cases for the same issue. 

Regards,
Amanda H.