S120 send notification to peripheral

RE: S120 send notification to peripheral

Jackxl — Thu, 23 Feb 2017 12:03:40 GMT

to sowmya: your problem BLE_DB_DISCOVERY_SRV_NOT_FOUND is wrong uuid type. If you have base of uuid equals bluetooth base (BLE_UUID_OUR_BASE_UUID), you will have to change uuid.type = 1

RE: S120 send notification to peripheral

Ole Bauck — Wed, 25 Nov 2015 13:08:43 GMT

Use ble_app_uart_c example from SDK 10 or from github here (for using s120 and SDK 9 it should be enough to change the flash and RAM memory start address and size)

RE: S120 send notification to peripheral

sowmya — Wed, 25 Nov 2015 11:38:41 GMT

Yes I have changed. One more testing I did, the same central code is working when I connect to iPad but not working with nRF51822 peripheral board. The nRF51822 peripheral board is working with BT dongle which will act as client.

RE: S120 send notification to peripheral

Ole Bauck — Wed, 25 Nov 2015 11:35:47 GMT

You have changed the UUID in both peripheral and central? The central will search for services with specific UUIDs when calling ble_db_discovery_evt_register(...).

RE: S120 send notification to peripheral

sowmya — Wed, 25 Nov 2015 09:30:32 GMT

Thank you ole. I checked the UART and HRM application and changed only the UUID and service in my application. But I am getting BLE_DB_DISCOVERY_SRV_NOT_FOUND event in db_discover_evt_handler function. But I verified the service and UUID on both master and slave and they are same. Could you please help me, how to handle service in central device?

RE: S120 send notification to peripheral

Ole Bauck — Tue, 24 Nov 2015 14:19:48 GMT

The peripheral is generally setup with the GATT server and the central as the GATT client. If this is the case, the central will have to do a write to the P2 to send data, see the Message Sequence Chart and the function API. You can also see how it is implemented in the ble_app_uart examples (peripheral and central).