cancel
Showing results for 
Search instead for 
Did you mean: 

WICED Studio Bluetooth

GrCa_1363456
Contributor II

When a CYW20719 device is running, we frequently get this event:
BTM_POWER_MANAGEMENT_STATUS_EVT

in the app_management_callback() function.

And the p_power_mgmt_notification->status is a value of 2.

If I'm reading the documentation correctly, this status is WICED_POWER_STATE_SNIFF

Two questions:

  1. What causes it to go into this mode?
  2. How can we prevent it, if we think it might be causing connectivity problems?

There is a similar discussion on the community:

https://community.cypress.com/thread/42098

and a suggested solution.  But to the final question in the thread:

    Yes,it works
     but every few seconds it enter  WICED_POWER_STATE_SNIFF again.
     how to keep in WICED_POWER_STATE_ACTIVE?

No answer is given.

Any answer given would be appreciated.

0 Likes
Reply
1 Solution
SheetalJ
Moderator
Moderator

Hi GrCa_1363456​,

I tested the default bt.spp demo app in WICED SDK 6.2.1, device goes in sniff mode once connected as it is a power save mode. But again enters the active mode after transmission starts and does not enter sniff mode again. You can find more details on low power sniff and active mode in Bluetooth spec or articles available online.

To answer your queries:

1. Sniff mode is a power saving mode, device automatically enters in it after some time.

2. There are no connectivity issues because of this.

View solution in original post

1 Reply
SheetalJ
Moderator
Moderator

Hi GrCa_1363456​,

I tested the default bt.spp demo app in WICED SDK 6.2.1, device goes in sniff mode once connected as it is a power save mode. But again enters the active mode after transmission starts and does not enter sniff mode again. You can find more details on low power sniff and active mode in Bluetooth spec or articles available online.

To answer your queries:

1. Sniff mode is a power saving mode, device automatically enters in it after some time.

2. There are no connectivity issues because of this.

View solution in original post