nRF52840 Dongle TX and RX with python

RE: nRF52840 Dongle TX and RX with python

Alvin_99 — Fri, 21 Oct 2022 01:04:19 GMT

Hi tesc,

Thanks for responding.

If that is the case how should I set the SIG UUID in the python and what is the driver I should use since self.adapter.write_req is for GATT UUID as the script that you provided does not share how we should place the UUID in.

Just a question is there any documentation that specify the function of each driver?

Regards,

Emin

RE: nRF52840 Dongle TX and RX with python

tesc — Thu, 20 Oct 2022 16:54:53 GMT

Hi,

For manually checking, it's enough to use the nRF Connect for Desktop BLE app. It shows the name of the service or characteristic if it is known to the application, otherwise it just shows the UUID. In the case of your screenshot it shows 1400, which means it sees the SIG defined UUID of 0x1400.

There is some usage of standard UUIDs like this in the heart rate collector example, although it uses predefined values from the driver libraries.

Regards,
Terje

RE: nRF52840 Dongle TX and RX with python

Alvin_99 — Wed, 19 Oct 2022 08:50:30 GMT

Hi Tesc,

I'm quite new to nrf bluetooth so I'm not quite sure how to obtain the UUID service and characteristics. Do you mind to share to me the method to obtaind the UUID for GATT Services and characteristics?

RE: nRF52840 Dongle TX and RX with python

tesc — Tue, 18 Oct 2022 16:06:27 GMT

Hi,

What are the full UUIDs for your service and charactersitics?

Based on the UUIDs shown in the screenshot, it may look like you use the SIG defined UUIDs 0x1400, 0x1401 and 0x1402, but those are not UUIDs for GATT Services or GATT Characteristics. (Those UUIDs are for HDP related service classes and profiles, see the "16-bit UUIDs" document available from the Bluetooth assigned numbers page.)

Regards,
Terje