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

nrf52840 slow rx characteristic time

The nRF52840 has a longer rx characteristic reception time than the nRF51822.

  --> android terminal log

first and second line nRF52840 , It takes almost 1.2 seconds to get the rx characteristic.

below nRF51822, It takes almost 0.4 seconds.

why It happens? What should I do to improve the performance?

NRF52840 -

SDK 15.3.0, with buttonless dfu service

NRF51822 - 

SDK 12.3.0 - w/o buttonless dfu service

Other application layer are almost same.

Parents
  • Hi

    I believe this might be due to different connection parameters (intervals, etc.) in the two SDKs. I think this was done to minimize the current consumption, which causes events to be a bit longer. You can try setting the same connection parameters for both devices and compare, to see if this is correct.

    Best regards,

    Simon

Reply
  • Hi

    I believe this might be due to different connection parameters (intervals, etc.) in the two SDKs. I think this was done to minimize the current consumption, which causes events to be a bit longer. You can try setting the same connection parameters for both devices and compare, to see if this is correct.

    Best regards,

    Simon

Children
  • ... I did double check. connection parameter is same.... and I tested ble app uart example in sdk. It also takes 1 sec. I think that there are big different nrf51 and nrf52. for now I dont have idea. parameter... or etc...

  • galaxy note 4

    It takes almost 1.1 sec.

    It takes almost 0.3 sec.

    *different phone, More recent model. galaxy note 10

    It takes almost 0.5 sec.

    It takes almost 0.8 sec.

    note10 is faster than note4 in average time, but the pair of galaxy note 4 & nrf51 is fastest speed to discover service.

    and nrf52 is slow for all. Is it normal?