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

Having problem with NUS Central & Client

Hello All,

I have been using this NRF52 DK board with KEIL for like 2 weeks. I read the all the document regarding BLE 5 protocol and followed the DIY codes step by step. I understand how the ble_blinky code works for both client and the server side I guess. But that particular example seems like not good enough for transferring array data to another BLE device.

So I read the threads and forum people saying that NUS example is the excellent one to perform this application. Generally, before I dig down into the code, I test the code on the boards for if it's working or how it's working. So the main purpose from what I expected was sending some packages of data from Server to Client.

CLIENT Device's firmware is nRF5_SDK_15.0.0\examples\ble_peripheral\ble_app_uart

SERVER Device's firmware is nRF5_SDK_15.0.0\examples\ble_central\ble_app_uart_c

What I do was uploading those codes to the 2 separate nRF52 DK boards and I opened 2 terminal program to see and send data packages to be transferred. The problem started from the beginning. I could see that those two boards are connecting to each other (from the LED's - The status has changed) But when I type a string from the Peripheral device's terminal software no any data has sent to the Client side. Because I check the terminal program on the receiver side as well.

But I managed to test the ble_Peripheral firmware by sending data from my phone through nrf Toolkit&nRF connect software and could see the coming data on the Terminal.

Eventually, I have to be able to communicate 2 boards over BLE. Could any of you tell me what could be the problem I faced and Is there any other 2 way of communication test codes for custom service that sending a simple string or any type of data?

Many Thanks

REE

Related