This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

master mode can't find a device

Hello, 

I am trying to connect NRF52832 with another Bluetooth module using custom characteristics. I was able to connect two NRF52832 modules but I can't connect to another module.

The module that I am trying to connect have identical 12 and 13 bytes

for TX and RX characteristic and the Base UUID.

The first 4 bytes are the same for the Base uuid and for the characteristics. The nordic's examples the 12 and 13 bytes are use for identification of the characteristic.

Is there any way to pass this identification somehow?
For example to used the whole 128 bits uuid for identification

The softdevice is 2.0.1 nRF52832_xxaa_s132 board pca10040 and the example that i used is based on ble_app_multirole_lesc.

Parents Reply
  • I assume by "Base UUID" here you meant the service UUID ? 

    In your case, you are having 3 base UUIDs. You would need to declare them as 3 different base UUID (in the code the byte endian is reverted):
    49530000 FE7D 4AE5 8FA9 9FAFD205E455

     49530000 6DAA 4D02 ADF6 19469ACA69FE

    49530000 ACA3 481C 91EC D85E28A60318

    And in your code you define the Service, TX characteristic, and the RX characteristic all with the same value: 0x5343 

    Then you need to add the 3 base UUIDs in using sd_ble_uuid_vs_add(), each of this will give you different uuid_type, use the specific type match with the UUID base when you call sd_ble_gatts_service_add() and sd_ble_gatts_characteristic_add(). 
    This way you will have the UUID matched for each of the service and characteristics. 

Children
Related