• State Not Answered
  • Replies 17 replies
  • Subscribers 64 subscribers
  • Views 20490 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 109417
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

how to change the service name?

MARTIN FR

image description

Hello everyone

i have created one custom service and i succed to compiled then i checked my service via master control panel it is showing unknown service but i named it as buzzer service can anyone guide me where i went wrong or suggest me how to change the service name.

Parents
  • 0

    Hi,

    Let me answer your question. There is a database in the nRF MCP app with all (almost all?) services, characteristics and descriptors assigned by Bluetooth SIG (developer.bluetooth.org/.../ServicesHome.aspx) + some with open specification, like Nordic UART service, DFU, Eddystone Beacon Config service etc. If the UUID of a service/char/descr matches the one I have in the database locally in the app I display the name of it.

    If I don't have in the database I write Unknown Service/Characteristic/Descriptor. One can easily rename such item by long pressing it and selecting EDIT option in the top menu. There you may provide your own name that will be stored locally on your device. You should do this for each Android device you use as this is not synchronized with any server. You may only rename an unknown service/char/descr. If you long press a known item there will be no EDIT icon but you still can for example copy its UUID etc.

    I guess this is the solution the guys from GitHub made, that's why they had LEDBUTTON visible there.

    image description

    Hope I helped, Aleksander

  • 0 in reply to Aleksander Nowakowski

    The procedure of adapting a service is very long, requires a lot of people from different companies and you don't do it for a custom service, rather for a use case, like battery service etc. But you don't need to do so. A service name is something that users don't see, they event don't care. You are just using the UUID. If you develop an app that works with your device you use the same UUID on both sides, that's how app can 'understand' the device. A name in the nRF MCP is just for making easier working with some common services.

    Also, what do you mean by saying that you have named your service Buzzer service etc. If you have written such in the code of your application on nRF, as a comment or a constant name, this does not mean this information is propagated to other devices, for example the phone. It's just a name you have there. You may rename the service, like I've shown in the MCP

Reply
  • 0 in reply to Aleksander Nowakowski

    The procedure of adapting a service is very long, requires a lot of people from different companies and you don't do it for a custom service, rather for a use case, like battery service etc. But you don't need to do so. A service name is something that users don't see, they event don't care. You are just using the UUID. If you develop an app that works with your device you use the same UUID on both sides, that's how app can 'understand' the device. A name in the nRF MCP is just for making easier working with some common services.

    Also, what do you mean by saying that you have named your service Buzzer service etc. If you have written such in the code of your application on nRF, as a comment or a constant name, this does not mean this information is propagated to other devices, for example the phone. It's just a name you have there. You may rename the service, like I've shown in the MCP

Children
No Data
Related