• State Not Answered
  • Replies 13 replies
  • Subscribers 63 subscribers
  • Views 4111 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 120678
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Slave latency & communication speed Nordic's trick?

Valer_I

Hello, I use nRF51822 based device with s110 softdevice. I noticed that data exchange is different on different connected centrals. For test I used Windows and Android powered central. The task is to send request and receive responce in notification from the device. After connection I request similar connection parameters (conn interval 30ms, slave latency 16) and they are accepted by both centrals. The speed results are different. Data exchange with windows is about 10 times faster than with Android. After sniffing I noticed that softdevice send Empty PDU after each notification packet and then enables slave latency functionality (i.e. skipping n central's packets). Windows driver in some way send next write request just after notification sent. And communication is very fast, like with slave latency = 0. In case of Android the driver send Empty PDU after notification from peripheral and than write request, but soft device do not react for it fot slave latency number times. Windows:

M->S  Write Command  (request1)
S->M  Empty PDU
M->S  Empty PDU
S->M  Notification  (responce1)
M->S  Write Command  (request2)      !!!
S->M  Empty PDU
M->S  Empty PDU
S->M  Notification  (responce2)

Android:

M->S  Write Command  (request1)
S->M  Empty PDU
M->S  Empty PDU
S->M  Notification  (responce1)
M->S  Empty PDU     <- This makes data exchange slow 
S->M  Empty PDU
M->S  Write Command  (request2)      !!!
M->S  Write Command  (request2)
M->S  Write Command  (request2)
...
M->S  Write Command  (request2)
S->M  Empty PDU
M->S  Empty PDU
S->M  Notification  (responce2)

I feel the softdevice has some pause after sending the packet before enabling slave latency function. Am I right? If yes what exact pause time is?

Thanks

UPDATED:

Android: from line 730 ANDROID_CAP

Windows: from line 851 WINDOWS_CAP

Parents
  • 0

    Yes, you can send empty payload notification, but it's not empty packet, it's a normal notification with empty payload.

    I don't really understand, why don't you avoid slave latency at the first place, if you simply want to keep the chip awake ? Or you only request slave latency when you need to.

    Note that from S132 v3.0.1 we provided a option api sd_ble_opt_set() to allow application on the nRF52 to disable and enable slave latency on its own. This mean even if the central reject to accept to change slave latency value, the nRF5 can choose to sleep or stay up on its own. But this is only for NRF52 with S132 v3.0.1 and later.

Reply
  • 0

    Yes, you can send empty payload notification, but it's not empty packet, it's a normal notification with empty payload.

    I don't really understand, why don't you avoid slave latency at the first place, if you simply want to keep the chip awake ? Or you only request slave latency when you need to.

    Note that from S132 v3.0.1 we provided a option api sd_ble_opt_set() to allow application on the nRF52 to disable and enable slave latency on its own. This mean even if the central reject to accept to change slave latency value, the nRF5 can choose to sleep or stay up on its own. But this is only for NRF52 with S132 v3.0.1 and later.

Children
No Data
Related