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

my bluetooth gets disconnected while sending continous stream of data

hi, i am using uart example from nrf51822 example. when i am sending continuous stream of data then my connection breaks. it disconnects from peripheral device. how should i overcome from this situation. i think i am missing some data exchange concept for sending devices based on connection interval and all different parameters.

can anyone please guide me what should i do to make connection live while sending continuous data over ble uart.

thanks!!

Parents
  • Oh, you are meaning that you continuously print debugging logs to the terminal program via UART?

    I thought you were sending BLE NUS packets to the central continuously. My mistake.

    Is the app_timer_cnt_diff_compute from SDK 10 or is it your personal function?

    I used SDK 7.2 most of the time, so it will take a while to check.

    Then what function returns an error code to make your device to reset?

    Since I don't know your purpose of your code (and will take quite a time),

    I think checking the error number will solve the problem.

    Place a breakpoint at app_error_handler to check the error number and call stack before calling NVIC reset.

    If you are using IAR EWARM, go to view -> call stack (while debugging), and it will reveal what functions are called.

    By the way, are you using a Eval board or a custom board? Also do you use the scheduler from the SDK?

Reply
  • Oh, you are meaning that you continuously print debugging logs to the terminal program via UART?

    I thought you were sending BLE NUS packets to the central continuously. My mistake.

    Is the app_timer_cnt_diff_compute from SDK 10 or is it your personal function?

    I used SDK 7.2 most of the time, so it will take a while to check.

    Then what function returns an error code to make your device to reset?

    Since I don't know your purpose of your code (and will take quite a time),

    I think checking the error number will solve the problem.

    Place a breakpoint at app_error_handler to check the error number and call stack before calling NVIC reset.

    If you are using IAR EWARM, go to view -> call stack (while debugging), and it will reveal what functions are called.

    By the way, are you using a Eval board or a custom board? Also do you use the scheduler from the SDK?

Children
No Data
Related