Raspberry bluetooth problem

[navarrocantero]

Hello, I have a problem with my nrf52832 customised board

It has loaded the ble_app_uart example of the  15.2_SDK and It have the correct pinout from my board, These are almost all my changes in the code.

I connect it with a raspberry pi3 (the last available model too) and a BLE dongle installed with a code based on node and using the noble library . (Otherwise I have tested python with another library called bluepy and It generate the same behavior) 

In raspberry pi3 I have a node server running, which communicates with another node server, both have the bluetooth code to connect with the customs boards.

When I have more than one raspberry or more than one custom boards turned on  , the customs boards becomes more unstable, and I get the feeling that it is because of the negotiation parameters about the connection.

I have followed the next ( docs.mbed.com/.../ ) to understand each parameter and can change it adequately but the same behavior has received. For these reason I let the parameters like the ble_app_uart from SDK_15.2

What can do I ? Thanks !

So the general schema will be :

1-Custom board emit SSID

2- Raspberry (with noble or bluepy or whatever)  connect to the SSID

3- and that's all

[Vidar Berg]

Hello,

It's interesting that you seem to get the same behavior with both Noble and Bluepy. Have you tried using the built-in BT device on the Raspberry Pi as well?

The sniffer trace is shows that the central terminates the link, so I think the you need to debug this on the Raspberry side. The central should generally not disconnect because of connection parameters requested by the peripheral.  

[awneil]

Vidar Berg said:

The central should generally not disconnect because of connection parameters requested by the peripheral

Indeed - they are just a request.

Certainly Android will make the connection - even when it does not grant the requested connection parameters.