Reading vendor specific characteristics from Thingy52

[tom8421]

Hi,

I'm using an nRF52840 dongle with pc-ble-driver on Linux. It has connectivity 6.0.0 with S140. I tried the heart rate collector/monitor example pair (I have two dongles) and it works fine.

I modified the example to try to read the temperature sensor on the Thingy (which is unmodified):

#define BLE_UUID_HEART_RATE_SERVICE 0x0200

#define BLE_UUID_HEART_RATE_MEASUREMENT_CHAR 0x0201

and I added the following in main() just before the start_scan() call to add the base UUID that the Thingy uses:

ble_uuid128_t base_uuid = {{0x42,0x00,0x74,0xa9,0xff,0x52,0x10,0x9b,0x33,0x49,0x35,0x9b,0x00,0x00,0x68,0xef}};

ble_uuid_t test = {

.uuid = 0x0000,

.type = BLE_UUID_TYPE_BLE

};

error_code = sd_ble_uuid_vs_add(m_adapter, &base_uuid, &test.type);

if (error_code != NRF_SUCCESS)

{

printf("Failed to add custom uuid.");

return error_code;

}

No other modifications to the source code were done. It compiles with no warnings or errors. Once the Thingy is found and connected to, I get this message:

Discovering primary services
Received service discovery response
Service discovery failed. Error code 0x10A

Any idea what I'm doing wrong? Thanks.

[Marjeris Romero]

Hi Tom,

I would recommend taking a look at this github link. There is an example which show how you can transmit enviroment sensor data from the Thingy to a nRF52 DK. You may need to made some small modifications to the code to get it working on the nRF5240 dongle.

Kind Regards,

Marjeris

[tom8421]

Will this example work with the pc-ble-driver project and the dongle running the connectivity firmware, or must I put it directly onto the dongle?

Thanks!

[Marjeris Romero]

Hi,

To run the example out of the box you will need to flash the code to a nRF52 DK. But you can follow the nRF52xx to Thingy:52 example step by step guide to read the Thingy:52 sensor variables.

Best Regards,

Marjeris