- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi BCM,
We want to config the BCM20736 RF TX power in some work mode, but we do not know how to call the APIs in WICED, especially the parameter. And we do not find any description about the RF TX power configuration.
Is there any detail introduction about this part ?
Many thanks...
Solved! Go to Solution.
- Labels:
-
BLE_PROFILE_CFG
-
MasterSlave
-
SDK 2.X
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
With reference to hello_sensor app, look for
blecm_setTxPowerInADV(0)
Check out this thread too...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi BCMs,
Exactly questions as below:
1. In WICED, is the function of blecm_setTxPowerInADV() used to set the RF Power ?
2. What type of this function parameter, db? the parameter unit is db ?
3. When to call this function? before ADV start or after ?
tks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So what are you getting? One problem I see with this implementation is that it rounds up to the next 4dB. And so if you really want low Tx power, set much lower and verify it with an SA.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Boont,
We study the thread U recommand, and we have succeed to set the TX power lower than default.
Tks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
With reference to hello_sensor app, look for
blecm_setTxPowerInADV(0)
Check out this thread too...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have also tried moderating the advertising power by using this method and found that it had no effect as measured by scope showing current draw during advertising events.
With the above thread, and the thread referenced by Boont's reply above, that makes at least three users who have demonstrated that the function does not work as advertised. Can we get some developers to concur on this, and commit to fixing it, or else provide instructions on how to control advertising power? Because the function provided has no effect on advertising power.
We are trying hard to extend battery life and we have no need to advertise 30 meters away. Our device pairing takes place at very close proximity and excessive advertising power only wastes precious energy.
Thanks,
eric