Alert notification on nrf51822

RE: Alert notification on nrf51822

Sigurd — Tue, 22 Aug 2017 11:41:45 GMT

The ble_app_alert_notification example implements the client role on a peripheral device. Note that MCP(Master Control Panel) is deprecated, and nRF-Connect could instead be used for testing this example(running the server role as a central). See this page. If you download SDK 13, you can find the .ncs file for nRF-Connect in the ble_app_alert_notification example folder.

See this answer regarding the different BLE role of the devices runing this example.

RE: Alert notification on nrf51822

Rahul Sahu — Tue, 22 Aug 2017 05:42:28 GMT

Thank you for your reply. Do you know any central code for alert notification that i can use on another nrf51822 module. my purpose is to send alert between two PTR5518A modules using alert notification profile. Any suggestion for central code will be helpful.

RE: Alert notification on nrf51822

Sigurd — Mon, 21 Aug 2017 14:52:00 GMT

nrf_log is used for printing logs over the UART and/or Segger RTT SWD interface. You can enable/disable this by setting the NRF_LOG_ENABLED in sdk_config.h. app_uart is a library used together with the uart drivers.

RE: Alert notification on nrf51822

Rahul Sahu — Sat, 19 Aug 2017 13:09:17 GMT

Hi, This problem is happening with alert notification example only. I have tried ble_app_uart example and it is working on PTR5518A module. After porting alert notification to ble_app_uart example, this is working. Still trying to find the original problem. Do you know what is the use of nrf_log in alert notification example. It seems that if I close the uart and then if I try to connect my module gets disconnected. What is the role of app_uart in alert notification service ?

RE: Alert notification on nrf51822

Sigurd — Fri, 18 Aug 2017 14:46:40 GMT

Hi,

Do you have the same problem with other BLE examples also? e.g. ble_app_uart ? What revision is the nRF51 chip used on the PTR5518A module ? Note that revision 1 of the nRF51-series have anomalies that will give issues with newer softdevices(such as the one used in SDK 12). You should also try to debug the nRF51 and see if you are running into the error-handler. See this post about debugging.