TX power of received advertising packet in NCS

[Remo]

Hi

We are using the NCS V2.6.99 for a sample project which scans for peripheral devices.

I've seen that the scan-callback-function return the struct bt_le_scan_recv_info (in bt_scan_device_info) which consists of the parameter "tx_power".

I wanted to check this TX-power value for the received advertising packet, but I always get the value 127.
But I know that the peripheral device is transmitting the TX power value in its advertising data.
Under what circumstances does the NCS set the tx_power in this struct?

Many thanks in advance.

Best regards, Remo

[Elfving]

Hello again, hope you've had a good week-end!

Remo said:

No, I don't get an error. Just the parameter tx_power in bt_le_scan_recv_info is set to 127.

That makes more sense. Sorry about the confusion.

Remo said:

I'm not sure if I can switch to a tagged version of NCS because I'm using the nRF54L. According to a mail from Nordic, the branch v2.6.99-cs1 should be used for the nRF54L.

Ah yes, that is correct. The nRF54 series is a bit of an exception as of now.

I'm looking into it, unfortunately things take a bit more time during the summer due to people taking time off. 

Regards,

Elfving

[Remo]

Thank you. Hope you've had a nice weekend, too.

Ok, thank you. No problem. I'm looking forward to hearing from you :-)

Best regards, Remo

[Elfving]

Hello again,

So this field is something the advertiser can use to advertise, similar to a advertising name, service UUIDs, etc. For more information, see Core Specification Supplement 10.

Likely if the value is 127, then the tx-power is not actually being advertised. You could do bt_data_parse() and check if BT_DATA_TX_POWER is included in the advertising data or not.

Regards and have a good week-end,

Elfving

[Remo]

Hi

Thank you for the clarification.

Best regards

Remo