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 Remo, and sorry about the wait.

So you check the parameter tx_power in bt_le_scan_recv_info, which gives you error 127? 127 is EISCONN: Socket is already connected. So that sounds a bit strange to me.

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

Could you try this again in a tagged version of NCS? There could be issues with the main branch.

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?

I'll have to get back to you on this tomorrow.

Regards,

Elfving

[Elfving]

Hi again,

What sample where you using for this?

Regards,

Elfving

[Remo]

Hi Elfving

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

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.

I used the sample "central_and_peripheral_hr" and adjusted it for our needs.

Best regards, Remo