Cannot alter MTU after connecting a peripheral device using the python library "pc_ble_driver_py"

[uri_ee]

Hello, 

I'm using the nRF device to communicate with a peripheral device I get some characteristic notifications but only 20 bytes for a packet.

When using the 'nRF connect' GUI I manage to update the MTU from 23 to any larger value and get the full notification.

But I cannot alter MTU after connecting a peripheral device using the python library "pc_ble_driver_py".

Iv'e tried many ways like setting the default_mtu and the att_mtu on adapter initialization:

driver = BLEDriver(
    serial_port=port,
    auto_flash=auto_flash,
    baud_rate=baud_rate,
    retransmission_interval=retransmission_interval,
    response_timeout=response_timeout,
    log_severity_level=driver_log_level,
)
driver.ble_gattc_exchange_mtu_req
adapter = BLEAdapter(driver)
adapter.default_mtu = 247
adapter.driver.open()
gatt_cfg = BLEConfigConnGatt()
gatt_cfg.att_mtu = adapter.default_mtu
adapter.driver.ble_cfg_set(BLEConfig.conn_gatt, gatt_cfg)
adapter.driver.ble_enable()


And to use the adapter.att_mtu_exchange function to but for no avail.
when i execute tyhe command : 
self.ble_adapter.att_mtu_exchange(self.conn_handler, 23)
 

it's running fine but when i try to increece the mtu to a different level like:
self.ble_adapter.att_mtu_exchange(self.conn_handler, 247)
 (or any number greater then 23)

it allways raise the folowing exception:

NordicSemiException: MTU exchange request failed. Common causes are: missing att_mtu setting in ble_cfg_set, different config tags used in ble_cfg_set and connect.

Is there any way to overcome this hurdle?

Thanks,
Uri

[Hieu]

Hi uri_ee,

I will support you with this case. However, I will need to do some investigation, while there is a bit too much on my schedule at the moment; so I cannot give you an answer right away.

I'm sorry for the inconvenience. Unless someone from the community already helped you then, I will return by the end of Friday Mar 17

Hieu

[Hieu]

Hi uri_ee,

My apology but I have still been occupied and haven't been able to start looking into this yet. I will try to get to it within next week, likely before Wednesday.

Hieu

[Hieu]

Hi Uri,

I looked into it finally understood (maybe) everything. 

On the Peripheral/nRF device side, the ble_app_hrs example by default initiates the MTU exchange first because NRF_BLE_GATT_MTU_EXCHANGE_INITIATION_ENABLED is set.

If you set that config to 0, then the Peripheral will not initiate the negotiation, and from the Python side, you can initiate the negotiation. I did this with:

    if conn is not None:
        try:
            adapter.driver.ble_gattc_exchange_mtu_req(conn_handle=conn, mtu=129)
        except Exception as ex:
            logger.exception("Exception ble_gattc_exchange_mtu_req: {}".format(ex))

You cannot see the final MTU, but you can derive it by looking into parameters of certain functions using breakpoints.

Note that breakpoints can break a connection depends on where it is set. If you don't want to have to think too much about it, just restart the experiment from the beginning after each "sampling" using breakpoints.

If the nRF device side initiates the negotiation,

• Set a breakpoint in ble_driver.py#ble_gatts_exchange_mtu_reply() to see the preferred MTU of the Python device side.
• Set a breakpoint in observers.py#on_gatts_evt_exchange_mtu_request() to see the preferred MTU of the nRF device side.

If the Python side initiates the negotiation,

• Set a breakpoint in ble_driver.py#ble_gattc_exchange_mtu_req() to see the preferred MTU of the Python device side.
• Set a breakpoint in observers.py#on_gattc_evt_exchange_mtu_rsp() to see the preferred MTU of the nRF device side.

Then the MTU will be decided as the minimal between both sides' preferred MTUs. 

[uri_ee]

Hello Hieu,

Unfortunately, we are unable to modify or access the code and configuration of the Peripheral device.

I've already went over all the functions you mentioned. I examined the values and also tried to manipulate then with no avail.

We are still in need for a solution.

As a reminder, using the GUI app we manage to change the MTU and get the full notification. we need to be able to do the same from a python script.

Thank you.

[Hieu]

Hi Uri,

uri_ee said:

I've already went over all the functions you mentioned. I examined the values and also tried to manipulate then with no avail.

The functions I mentioned is a part of the library and should not be manipulated. I just asked you to examine what the parameter values of those functions are.

What values did you see?

uri_ee said:

As a reminder, using the GUI app we manage to change the MTU and get the full notification. we need to be able to do the same from a python script.

Is your issue that MTU exchange did not happen, or is it something about the notification?

If your issue is with the notification, are you certain that the cause is with MTU?

All this time, we have been so invested into checking if MTU is exchanged, but are we certain that the full notification wasn't sent successfully, and the problem isn't somewhere else?

Could the problem be in your notification handling code?

From what we have seen, I think the MTU should be exchanged correctly if you are setting things up similar to the Heart Rate example. Furthermore, if the MTU is insufficient, it usually resulted in the message just cannot be sent.

Can you get me a sniffer trace of a test? It will reveal whether MTU was successfully exchanged, and whether the notification was sent in full or shortened.

If you need instruction on getting a sniffer trace, please refer to Lesson 6 of our BLE Fundamentals online course.

Hieu

[uri_ee]

Hi Hieu,

Following the teams conversation we purchased and installed the BLE sniffer. Attached below is the wireshark trace logs. We connected to the device and changed the MTU. Once connected we see nothing else from this device.


GodHelpMe_Two.pcapng

You can filter with out MAC address that we are trying to connect to.

C6:D8:48:B4:61:7C

Thanks

[Hieu]

Hi Uri,

uri_ee said:

GodHelpMe_Two.pcapng

Haha, unfortunately, I am no god. But the reason I cannot provide help with this file is not because of that, but because there is no connection in your sniffer trace. There are only ADV_NONCONN_IND packets in the trace, which is non-connectable advertising. There is also no scan request or response, no connection establishment packet, no sign of the central in the trace. The device c6:d8:48:b4:61:7c is not in the trace at all.

Please go over the Bluetooth Low Energy Fundamentals lesson I linked earlier for details on how to run a sniffer properly.

By the way, here is a sample project from me. I made it two months ago, so I don't remember the details very well. However, I am fairly certain that it should be able to negotiate MTU successfully whether the peripheral initiate the negotiation or not. It is made to work with the ble_app_uart example.

main.py_230503_01.zip

Regards,

Hieu

[uri_ee]

Hi Hieu!

We went over the exercises and ran it successfully. Please find attached files "three" and "four" where we connected to an nRF52840DK over a mobile phone and nRF52840 Dongle.

"five" file is trying to connect with the pc-ble-drive-py code with our peripheral device.

HieuHelpMe_Four.pcapngHieuHelpMe_Three.pcapngHieuHelpMe_Five.pcapng

[Hieu]

Hi Uri,

Did you try the sample I sent in my last reply?

I am out of office now, but I will check the traces when I return next week. Meanwhile, please give the sample I sent a try.

[uri_ee]

Hi Hieu,

Yes I tried the sample and I have managed to get the full length message from the peripheral device. At this time I am trying to update my code to match the sample you provided. Now I am having a new problem. When I try any other value than 23 I get this error:

NordicSemiException ble_gattc_exchange_mtu_req: Failed to ble_gattc_exchange_mtu_req. Error code: NRF_ERROR_INVALID_PARAM

[Hieu]

Hi Uri,

Have you noted the comments I wrote in the code? Duplicating it here for reference:

        # If the peer (peripheral device) initiates the MTU exchange, this value will be automatically used
        # as this device (Python/interface device) preferred MTU.
        # By default, the Heart Rate Collector example also uses this value to configure the
        # SoftDevice/interface device. See further notes in open()
        self.adapter.default_mtu = 111

        self.mtu_exchanged = False
        self.nus_tx_uuid = None
        self.peer_mtu = 0

    def open(self):
        self.adapter.driver.open()
        if config.__conn_ic_id__.upper() == "NRF51":
            raise AssertionError ("NOT SUPPORTED: config.__conn_ic_id__.upper() == ""NRF51""")
        elif config.__conn_ic_id__.upper() == "NRF52":
            gatt_cfg = BLEConfigConnGatt()

            # In this configuration, we are configuring the MAXIMUM value that the SoftDevice/interface device can
            # ever support. It can only be reconfigured after driver.ble_disable().
            # See: https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s140.api.v7.2.0/structble__gatt__conn__cfg__t.html#a3fac0ed97a3a75cf21e9ed8432b95193
            gatt_cfg.att_mtu = self.adapter.default_mtu
            gatt_cfg.tag = CFG_TAG
            self.adapter.driver.ble_cfg_set(BLEConfig.conn_gatt, gatt_cfg)

            self.adapter.driver.ble_enable()

Another source of that error is, as we explained before, if the negotiation already happened. Which brings us to the sniffer traces.

Are you certain that the device in trace Three and Four is the same as in trace Five?

In trace Three and Four, we can see that the peripheral device initiate the MTU negotiation:

However, that didn't happen in trace Five.