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

    Okay, it seems I misunderstood the initial question. Sorry about that. This delay happens after the devices have connected, right? Can you provide a sniffer log so we can take a look at what happens? You can do this either by using an Ellisys sniffer (if you have one available) or by using an extra nRF52 DK and the nRF Sniffer to sniff the connection.

    You can also try setting NRF_LOG_DEFERRED to 0 in order to minimize the delay from an event until it is printed, as the terminal log might not be the most reliable way to measure the time it takes to get a service.

    Best regards,

    Simon

Reply
  • Hi

    Okay, it seems I misunderstood the initial question. Sorry about that. This delay happens after the devices have connected, right? Can you provide a sniffer log so we can take a look at what happens? You can do this either by using an Ellisys sniffer (if you have one available) or by using an extra nRF52 DK and the nRF Sniffer to sniff the connection.

    You can also try setting NRF_LOG_DEFERRED to 0 in order to minimize the delay from an event until it is printed, as the terminal log might not be the most reliable way to measure the time it takes to get a service.

    Best regards,

    Simon

Children
Related