master mode can't find a device

RE: master mode can't find a device

Hung Bui — Wed, 13 May 2020 14:16:56 GMT

From this you would need to define 5 UUID bases the way I suggested in the last reply.

RE: master mode can't find a device

Mario — Wed, 13 May 2020 13:56:18 GMT

I do not have 3 services I have one with 4 characteristics two of them are TX and RX and also I do not have the source of the other chip I can only change the source of the nrf52832

the screenshot is from the second chip(not nrf52832) do not know the manufacture.

RE: master mode can't find a device

Hung Bui — Wed, 13 May 2020 13:43:37 GMT

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.

RE: master mode can't find a device

Mario — Wed, 13 May 2020 12:38:27 GMT

Just to be clear the module is not made by nordic

RE: master mode can't find a device

Mario — Wed, 13 May 2020 12:10:13 GMT

Base UUID - 49535343 FE7D 4AE5 8FA9 9FAFD205E455
RX - 49535343 6DAA 4D02 ADF6 19469ACA69FE
TX - 49535343 ACA3 481C 91EC D85E28A60318

(5343) is the 12 13 byte of the UUID

RE: master mode can't find a device

Hung Bui — Wed, 13 May 2020 11:45:48 GMT

Hi Mario,
Could you post the UUID of the TX and RX characteristic (and the service as well) of the module you are connecting to ?

Note that by spec, the UUID of a characteristic is formed by the Base UUID and only byte 12 and 13 is customized by a 16 bit UUID. So it's not suggested to have a customized UUID that doesn't follow this rule.