TWT wake duration is not the setup value

[woody.chen]

Hi team,

1.I set up the TWT parameter as following, the TWT wake duration is 8ms.

2.I don't transmit any packet from or to nRF7002DK, nRF7002 just join the AP, firmware is ncs 2.3.0 shell.

3.use the ppk2 to measure the current of nRF7002-DK, the ppk2 screenshot as following.

4.according to the screenshot, the nRF7002-DK wake duration is about 49.23ms, not the value I setup 8ms. what's the nRF7002 doing? why the TWT wake duration is 49ms not the 8ms?

5.nRF7002 Average current consumption (5GHz, TWT, target wake interval 1 min) is 28.9uA, except for TWT wake duration 8.192ms, target wake interval 1min, transmit packet duration 100us, do we have other conditions?

thanks.

            

[Marte Myrvold]

Hi,

Which AP are you using when testing? I have seen a big difference in TWT behavior depending on the AP.

Best regards,
Marte

[woody.chen]

AP: AUSU RT-AX56U V2

[Marte Myrvold]

Hi,

Are you able to get a sniffer log? Make sure that the sniffer log includes the initial connection of the device where the key is exchanged, as well as the TWT setup and some time after.

Best regards,
Marte

[woody.chen]

sorry, I couldn't get a wifi6 sniffer log

[Marte Myrvold]

Hi,

I have asked about this internally, but I am still waiting on a response. I will let you know when I have an update.

Best regards,
Marte

[Marte Myrvold]

Hi,

I got a response from the developers. Early wake-up and late sleep techniques are implemented to compensate for PPM. The first wake up after TWT is configured, the wake duration will be the same as configured. For each consequent wake up, the wake duration will increase. After 5 minutes the device will resynchonize with the AP, and the next wake duration will go back to what it was in the beginning, before it will start increasing again. This is repeated, with new resynchronization every 5 minutes.

Best regards,
Marte

[woody.chen]

thanks