This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Throughput NCS example and SDK 14.2.0 - proper speed cannot be achieved

Dear All,

I am using 2 development boards NRF52DK with NRF52832.
I changed in throughput example ( ncs/v1.7.0/nrf/samples/bluetooth/throughput ) characteristics to custom 128 bit and replaced filter to find proper MAC address.

When I testing it with example software ( central and peripheral ) I can achieve speed of ~1292 kbps


The issue appears when I test the same setup with S132 and SDK 14.2, I cannot achieve more than 4 kbps. I am writing to the same characteristics.

I can observe that PHY and ATT MTU are being changed.

Zephyr Central (ncs example):

==== Starting throughput test ====
PHY update pending
LE PHY updated: TX PHY LE 2M, RX PHY LE 2M
LE Data length update pending
LE data len updated: TX (len: 251 time: 1314) RX (len: 251 time: 1314)
                                                                                
                    ^.-.^                               ^..^                    
                 ^-/ooooo+:.^                       ^.--:+syo/.                 
              ^-/oooooooooooo+:.                 ^.-:::::+yyyyyy+:^             
           ^-/+oooooooooooooooooo/-^          ^.-::::::::/yyyyyyyhhs/-          
        ^-:/++++oooooooooooooooooooo+:.   ^.-::::::::::::/yyyyyyyhhhhhho:^      
      ^::///++++oooooooooooooooooooooooo//:::::::::::::::/yyyyyyyhhhhhddds      
      -::://+++ooooooooooooooooooooooooooooo+/:::::::::::/yyyyyyyhhhhhdddd^     
      -::::::/++ooooooooooooooooooooooooooooooo+/::::::::/yyyyyyyhhhhhdddd^     
      -:::::::::/+ooooooooooooooooooooooooooooossso+/::::/yyyyyyyhhhhhDisconnected (reason 0x13)
W: Disconnected while allFilter not match. Address: 54:13:54:4F:44:B8 (random) connectable: 1
ocating context
dGATT write failed (err -128)

Done
[local] sent 195200 bytes (190 KB) in 340312 ms at 4 kbps

Peripheral S132 SDK 14.2:

BLE_CONN_PARAMS_EVT_SUCCEEDED
Connection interval: 400, timeout 4000 ms
CONNECTED @ 42
Changing state: Advertising -> Connected
Peer on connection 0x0 requested an ATT MTU of 247 bytes.
Updating ATT MTU to 247 bytes (desired: 247) on connection 0x0.


I set on S132 SDK 14.2 peripheral board:
NRF_SDH_BLE_GAP_DATA_LENGTH 251
NRF_SDH_BLE_GATT_MAX_MTU_SIZE 247


I have followed:
https://devzone.nordicsemi.com/f/nordic-q-a/44169/default-phy
https://devzone.nordicsemi.com/f/nordic-q-a/54295/how-to-enable-2mbps
https://devzone.nordicsemi.com/f/nordic-q-a/51082/can-t-enable-dle

https://devzone.nordicsemi.com/f/nordic-q-a/39787/verifying-connection-event-length-extension-and-data-length-extension

I have no clue, what could be cause of such different behavior and low throughput using S132 and SDK14.

Could you give any suggestions what more can be changed?

Parents Reply Children
No Data
Related