This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

service data advertisement and 128 uuid

Hi,

I searched through the devzone but I cannot find a answer on this question but the question has been asked before. Some background. I have a working solution from another vendor and I want to switch to Nordic. In this solution I use service data to advertise our product including some data about the product. I am now looking in the SDK to see how I can implement this with Nordic. Ok, so the ble_advdata_service_data_t structure needs a uint16_t for de uuid. I use 128 bits uuid's. I can add them with sd_ble_uuid_vs_add. This returns a UUID type. Now the question is. How do I match the UUID type return from sd_ble_uuid_vs_add to the service_uuid field in ble_advdata_service_data_t structure.

Cheers, Marcel

Parents
  • There are examples code from this blog use custom UUID. You can see how it's done. embeddedsoftdev.blogspot.ca/.../ehal-nrf51.html

  • Thank you for bearing with me. The problem is there is already an implementation using a different vendor and there is already an iOS app in the field. That 's why I have to use this type: BLE_GAP_AD_TYPE_SERVICE_DATA_128BIT_UUID of advertisement. I think I can solve te problem by extending service_data_encode function or create my own encoder but I did not tried that yet. I personally find it strange how Nordic implemented it and deals with 128 uuid's. Most people, I think, wil not make products which already have a Bluetooth SIG profile and therefore must use 128 uuid's. You are right that the Nordic SDK may have different ways and that only the transmitted packet is important. But sadly enough the forgot to implement 128 uuid service data type of advertisement. I will make a case out of this because Nordic is not responding here. It would be really nice if it is added to the SDK

Reply
  • Thank you for bearing with me. The problem is there is already an implementation using a different vendor and there is already an iOS app in the field. That 's why I have to use this type: BLE_GAP_AD_TYPE_SERVICE_DATA_128BIT_UUID of advertisement. I think I can solve te problem by extending service_data_encode function or create my own encoder but I did not tried that yet. I personally find it strange how Nordic implemented it and deals with 128 uuid's. Most people, I think, wil not make products which already have a Bluetooth SIG profile and therefore must use 128 uuid's. You are right that the Nordic SDK may have different ways and that only the transmitted packet is important. But sadly enough the forgot to implement 128 uuid service data type of advertisement. I will make a case out of this because Nordic is not responding here. It would be really nice if it is added to the SDK

Children
No Data
Related