BLE nano 33 does not report or disconnect from centra

[Russell108]

When using for example the button peripheral and central examples in the arduinoBLE library
If for example the central is a MKR1010 powered by usb and the peripheral is a nanoBLE 33 then if I remove the power from the central the peripheral still reports it as connected.

If instead of a Nano BLE 33 I use a Nano IOT33 then when the central is de powered the peripheral reports it as being disconnected.

there are several issues regarding disconnection & this library when using the Nana BLe 33.

Arduino support said the following

================================================================

Hello Russell,

Thank you for reporting us this issue,

We request you to open an issue on Github here and our developers will provide you further guidance.

Have a nice day!

Best Regards,
Sravya Amirisetti

[sandeepmistry]

@Russell108 thanks for the issue report! I was able to reproduce here.

@facchinm it seems the Cordio stack is not generating the HCI disconnect event when power is cut to the central.

If I add BLE.debug(Serial); and using the MKR WiFi 1010 as the BLE peripheral + Nano 33 BLE as the central, on the peripheral side I get the following event:

HCI EVENT RX <- 04050400000008

... but if the roles are reversed, nothing ...

[sandeepmistry]

I tried lowering the supervision timeout from 0xc8 to 0x14 on the central side, this did not have any impact.

[ixj111]

Hello, any update on this issue? Still exists

[harpop]

Hello, just received my nano 33 ble devices. Stumbled on the same issue. As always lost a few hours! Any update?

[Russell108]

Ive gone back to a nano iot 33 & wifi

…

On 13 Nov 2019, at 21:48, Harry ***@***.***> wrote: Hello, just received my nano 33 ble devices. Stumbled on the same issue. As always lost a few hours! Any update? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#33?email_source=notifications&email_token=AAEYL36QR5CD27CZOUHOTWLQTRY3DA5CNFSM4I4WOLT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED7ZAEY#issuecomment-553619475>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEYL37B4TKDYOBO4AOP3S3QTRY3DANCNFSM4I4WOLTQ>.

[sandeepmistry]

Hi @ixj111 @Russell108 @harpop @alexisicte,

Pull request #44 should fix this, if you have some time to try out the changes and provide your feedback that would be great.

[alexisicte]

Hi @sandeepmistry,
Before your last changes when an "unnormal" disconnect issue occurs ble debugging returns nothing. After your changes we get on the serial monitor:

11:04:18.535 -> HCI EVENT RX <- 04050400000008
11:04:18.535 -> HCI COMMAND TX -> 010A200101
11:04:18.535 -> HCI EVENT RX <- 040E04010A2000

When "normal" disconnect procedure occurs the output is:

10:55:22.611 -> HCI EVENT RX <- 04050400000013
10:55:22.611 -> HCI COMMAND TX -> 010A200101
10:55:22.646 -> HCI EVENT RX <- 040E04010A2000

While BLE.adverise() is called the output is the following in an infinite loop:

10:54:18.858 -> HCI EVENT RX <- 040E040106200C
10:54:18.858 -> HCI COMMAND TX -> 0106200FA000A0000000000000000000000700
10:54:18.858 -> HCI EVENT RX <- 040E040106200C
10:54:18.858 -> HCI COMMAND TX -> 0106200FA000A0000000000000000000000700
10:54:18.891 -> HCI EVENT RX <- 040E040106200C
10:54:18.891 -> HCI COMMAND TX -> 0106200FA000A0000000000000000000000700
10:54:18.891 -> HCI EVENT RX <- 040E040106200C

but, after an "unnormal" disconnect issue occurs the above output is not displayed. Actually the serial monitor is idle. When i try to reconnect after an "unnormal" disconnect issue, i get:

11:05:29.198 -> HCI EVENT RX <- 043E13010000000101E397B78CE96128000000F40101
11:05:29.467 -> HCI ACLDATA RX <- 0200200B0007000400100100FFFF0028
11:05:29.834 -> HCI EVENT RX <- 043E0A0300000006000000F401
11:05:34.444 -> HCI ACLDATA RX <- 0200200B0007000400100100FFFF0028
11:05:39.459 -> HCI ACLDATA RX <- 0200200B0007000400100100FFFF0028

AND

11:05:44.468 -> HCI EVENT RX <- 04050400000013
11:05:44.468 -> HCI COMMAND TX -> 010A200101
11:05:44.468 -> HCI EVENT RX <- 040E04010A2000

where the second part is the same as "normal" disconnect output.
Then the serial monitor is idle as before.
According to BLE.debug it seems that the device is not advertising because i dont get the advertise debug output, but central devices can see the peripheral.

[JGronholz]

This issue persists as of 05/20/2020, library version 1.1.2.
If I disconnect power from my Nano 33 Sense peripheral, my Nano 33 Sense central remains unaware and connected.

Edit: I haven't tried creating a disconnect by moving the two out of range, only sudden loss of power.

This event never fires on my Nano 33 Sense:
BLE.setEventHandler(BLEDeviceEvent::BLEDisconnected, disconnectedHandler);

From this thread, almost a month ago:
(https://forum.arduino.cc/index.php?topic=645907.0)

Klaus_K appears to have done everything but fix the code:

The behavior for them is different. I guess they both use the same BLE library but there might be differences in the integration with mbedOS on the Nano 33 BLE.

The Arduino Nano 33 BLE does not set the central.connected correctly when the connection is lost. It returns central.rssi() = 0 a couple of times when the connection is about to get lost. But it can recover from that when the connection gets better. But when the connection is lost it cannot recover without reset.

The Arduino Nano 33 IoT does set central.connected correctly so the sketch can get back to a state where it waits for connections. The central.rssi never gets to 0, but gets to some maximum negative value around -128 or so as expected.

Thanks, Jon!

Edit: I will check tonight whether my peripheral can detect when my central loses power.