- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We are working on CYW43907 Platform application development.
Evaluating the powersave mode, monitoring the Current prover.
CYW43907 shows the different Beacon reception time.
sometime, it takes around 10msec. but other time , it takes around 1-2msec (short time !!!)
<PS1> allways 10msec
<PS2> allways 1-2msec
<PS3> conbination of 10msec and 1-2msec
Is there any reason why?
We need to know why it behave like this.
In order to save battery power, of course we prefer to have 1-2msec reception time.
Is ther anyway to get shorter Beacon recpton time.
We are quite uergenty clarify this issue , your quick advise.comment will be very apreciated.
BRDs.,
Keith
Solved! Go to Solution.
- Labels:
-
WICED Studio
-
Wireless MCU
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
The RX window will widen if we miss a beacon. Potential reasons for beacon loss are:
1. Interference
2. Range
3. AP clock is drifting and so the board is out of sync.
10ms is the default value set in firmware for which the device keeps on listening for beacon.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
As per powersave feature, the AP is aware of the sleep time of every STA. The STA wakes up periodically as per its sleep cycle and If the AP has some data for the STA, the AP sends a beacon frame with a TIM(Traffic indication map) information element. By examining the TIM, the station can determine if the access point has buffered traffic on its behalf. The station then receives the buffered data using PS poll frames. This could be possible reason of prolonged beacon reception time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Riya
Basically, we understand it beacon reception time might be changed
by DTIM of AP and the buffered Data to STA that you explained.
However, in our case,
- AP DTIM is never changed
- STA side never send any data by itself
=> STA is just waiting for the unicast packet event to itself
In this situation, why it shows such different beacon reception time?
That is our question.
BRDs,
Keith
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Woops,
Sorry I made Typo.
DTIM -> TIM
BRDs,
Keith
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What is the difference between the Power save modes, PS1, PS2 and PS3?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Riya
Thanks for your consideration,
PS1: WiFi = Power SaveMode , ApplicationCPU=Active mode
in this case, Beacon Reception time is always 10msec
This is OK.
Both PS2 & PS3 : WiFi = Power SaveMode , ApplicationCPU=Sleep mode
PS2-> Beacon Reception time is 1msec
PS3-> Beacon Reception time saometime 1msec/ other time 10msec
We would like to know, why beacon reception time is changed
on WiFi =PS & ApplicationCPU =sleep mode.
10 msec Beacon Reception time will be preety much affect to the power consumption.
We would like to keep it always 1msec as much as possible.
BRDs,
K.Hirayama
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Riya
Any Update on this?
BRDs,
Keith
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
The RX window will widen if we miss a beacon. Potential reasons for beacon loss are:
1. Interference
2. Range
3. AP clock is drifting and so the board is out of sync.
10ms is the default value set in firmware for which the device keeps on listening for beacon.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Riya
Thanks for your advise.
We will discuss internally.
BRDS,
Keith