TX power of received advertising packet in NCS

RE: TX power of received advertising packet in NCS

Remo — Fri, 05 Jul 2024 13:30:51 GMT

Thank you for the clarification.

Best regards

Remo

RE: TX power of received advertising packet in NCS

Elfving — Fri, 05 Jul 2024 12:38:46 GMT

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

RE: TX power of received advertising packet in NCS

Remo — Tue, 02 Jul 2024 07:44:47 GMT

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

RE: TX power of received advertising packet in NCS

Elfving — Mon, 01 Jul 2024 13:38:39 GMT

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

[quote user="Remosennhauser"]

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

[/quote]

That makes more sense. Sorry about the confusion.

[quote user="Remosennhauser"]

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.

[/quote]

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

RE: TX power of received advertising packet in NCS

Remo — Thu, 27 Jun 2024 05:58:33 GMT

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

RE: TX power of received advertising packet in NCS

Elfving — Wed, 26 Jun 2024 07:34:45 GMT

Hi again,

What sample where you using for this?

Regards,

Elfving

RE: TX power of received advertising packet in NCS

Elfving — Tue, 25 Jun 2024 14:52:37 GMT

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.

[quote user=""]

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

[/quote]

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

[quote user=""]

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?

[/quote]

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

Regards,

Elfving