A terminal that can not communicate.

RE: A terminal that can not communicate.

zkt-1400 — Tue, 25 Jun 2019 00:07:15 GMT

Thank you for your detailed answer.
I think that I would like to use s132_nrf52_6.1.1_softdevice because I think it has been changed to not disconnect.

Current
s132_nrf52_6.0.0_softdevice + SDK15
↓
plans
s132_nrf52_6.1.1_softdevice + SDK15

RE: A terminal that can not communicate.

Sigurd — Fri, 14 Jun 2019 14:14:33 GMT

[quote user="zkt-1400"]Whether to execute Data Length Extension (DLE) is judged from the result of the following dialogue.[/quote]

Yes, the FeatureSet(LL_FEATURE_REQ/LL_FEATURE_RSP) can be used for that, from the Bluetooth spec we have the following:

If the peer Link Layer has indicated either during a feature exchange procedure
or by responding with an LL_UNKNOWN_RSP PDU that it does not support a
procedure, then the Link Layer shall not use that procedure.

But if the FeatureSet have not be been exchanged yet, it's still allowed to use the DLE procedure (LL_LENGTH_REQ/LL_LENGTH_RSP), and if the other peer does not support DLE, it should respond with LL_UNKNOWN_RSP PDU.

RE: A terminal that can not communicate.

zkt-1400 — Fri, 14 Jun 2019 08:48:13 GMT

Thank you for your response.

I have a question.

Here is my recognition.
Whether to execute Data Length Extension (DLE) is judged from the result of the following dialogue.
・ LL_VERSION_IND
・ LL_FEATURE_REQ and LL_FEATURE_RSP
(Confirmation that the other party supports DLE)

Why is softdevice running DLE without this interaction?

RE: A terminal that can not communicate.

Sigurd — Tue, 28 May 2019 08:19:58 GMT

Hi,

[quote userid="27086" url="~/f/nordic-q-a/47188/a-terminal-that-can-not-communicate/189432"]What does this change mean?
Is the parameter different from MTU?[/quote]

Yes, NRF_SDH_BLE_GAP_DATA_LENGTH is different from ATT MTU. DLE / (NRF_SDH_BLE_GAP_DATA_LENGTH ) is the on-air packet size.

I took a closer look at the HRM_xperia log, and I see that the xperia is not following the Bluetooth specification. In HRM_xperia.pcapng, the xperia sends a LL_LENGTH_RSP packet where Max RX time is set to 256 microseconds. This is not allowed according to the Bluetooth spec.

From the spec:

" BLUETOOTH SPECIFICATION Version 4.2 [Vol 6, Part B] page 57 , chapter

2.4.2.21 LL_LENGTH_REQ and LL_LENGTH_RSP

The MaxRxTime field shall have a value in the range of 328 to 2120 microseconds".

I therefore suggest setting NRF_SDH_BLE_GAP_DATA_LENGTH to 27 if you want to workaround this issue that the xperia has.

RE: A terminal that can not communicate.

zkt-1400 — Tue, 28 May 2019 02:52:53 GMT

From the sniffer log, the phone is transmitting several packet 2 times, without waiting for response.

→
This phenomenon may occur with any mobile phone connected.
It can also occur when using the sample without changing it.

1) Does the issue disappear if you set NRF_SDH_BLE_GAP_DATA_LENGTH in sdk_config.h to 27 ?

→
I was able to connect.
What does this change mean?
Is the parameter different from MTU?

I will attach the log.
・HRM_DATA_LENGTH_27_iPhoneSE.pcapng
・HRM_DATA_LENGTH_27_xperia.pcapng

2) Does the issue disappear if you set NRF_SDH_BLE_GATT_MAX_MTU_SIZE in sdk_config.h to 23 ?

→
I was able to connect.
If this change is made, the MTU of all devices will be 23.
So it is not suitable for me.
When the communication partner is Bluetooth 4.2 or later, I want to extend the MTU and communicate.

I will attach the log.
・HRM_MAX_MTU_SIZE_23_iPhoneSE.pcapng
・HRM_MAX_MTU_SIZE_23_xperia.pcapng

devzone.nordicsemi.com/.../HRM_5F00_DATA_5F00_LENGTH_5F00_27_5F00_iPhoneSE.pcapng

devzone.nordicsemi.com/.../HRM_5F00_DATA_5F00_LENGTH_5F00_27_5F00_xperia.pcapng

devzone.nordicsemi.com/.../HRM_5F00_MAX_5F00_MTU_5F00_SIZE_5F00_23_5F00_iPhoneSE.pcapng

devzone.nordicsemi.com/.../HRM_5F00_MAX_5F00_MTU_5F00_SIZE_5F00_23_5F00_xperia.pcapng

RE: A terminal that can not communicate.

Sigurd — Mon, 27 May 2019 13:42:56 GMT

From the sniffer log, the phone is transmitting several packet 2 times, without waiting for response.

1) Does the issue disappear if you set NRF_SDH_BLE_GAP_DATA_LENGTH in sdk_config.h to 27 ?

2) Does the issue disappear if you set NRF_SDH_BLE_GATT_MAX_MTU_SIZE in sdk_config.h to 23 ?

RE: A terminal that can not communicate.

zkt-1400 — Thu, 23 May 2019 02:51:17 GMT

I will attach a new sniffer log.
Xperia Z4 SO-03G <---> sample HRM

The target terminal is Bluetooth 4.1.
The OS of the target device is Android 7.0.

Why is MTU exchange successful for devices other than 23 on Bluetooth 4.1 devices?
Will it succeed if the OS is Android 7.0?
devzone.nordicsemi.com/.../HRM_5F00_xperia.pcapng

RE: A terminal that can not communicate.

Sigurd — Thu, 16 May 2019 11:10:09 GMT

It does not work with NRF_SDH_BLE_GATT_MAX_MTU_SIZE?

Does the device disconnect?

Could you upload a sniffer log captured with nRF-Sniffer v2?

RE: A terminal that can not communicate.

zkt-1400 — Thu, 16 May 2019 09:55:03 GMT

Why is it that I can not communicate even though the MTU exchange on Xperia is successful?
Why does it work for default values?

RE: A terminal that can not communicate.

Sigurd — Tue, 14 May 2019 08:18:50 GMT

Hi,

[quote user=""]1. What is the difference between making MTU by default and turning it off?[/quote]

If you turn it off, i.e. remove the gatt module initialization, you will then not handle MTU requests from the central at all. If the MTU requests are not handled, you will get a GATT procedure timeout on the link, and the link will disconnect.

Leaving it at default, you will just respond back to the central that you support the default value of 23.

[quote user=""]2. If MTU is the default, will the communication speed be slower if the data size is large?[/quote]

You could get a higher throughput with larger MTU, but DLE(data length/NRF_SDH_BLE_GAP_DATA_LENGTH) have a greater impact on throughput than MTU.

Also, If you are using nRF-Sniffer v1, I would recommend upgrading to nRF-Sniffer v2.