Hi Simon, On Thu, Jun 09, 2016 at 02:53:14PM -0700, Simon Ratner wrote: [...] > The above doesn't seem to have an effect on the contents of the advertising > packet; it still advertises 0dBm. The comment in > https://github.com/apache/incubator-mynewt-core/blob/master/net/nimble/host/src/ble_hs_adv.c#L188 > implies that this should be handled automatically, and the provided value > is ignored. Is this implemented as described, or am I doing something wrong? > > The actual tx power does change, for what it's worth - I see the expected > difference in received signal between +4, 0, -12, -20.
As currently implemented, the nimble controller always indicates an advertising power of 0. I don't want to speak for Will who is more familiar with this part of the code, but I believe this is intentional, as the nimble link layer does not expect the transmit power to be changed "behind its back." Apps are not expected to make direct calls to the BLE drivers. Rather, the intended client is the BLE link layer. Since an interface into the transmit power has not been added to the Nimble API yet, I don't blame you for trying! I imagine that when a transmit power interface is added to nimble, the adverising power setting will get reported as configured. Chris
