This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Not able to connect device to Linux Machine

Hello,

I am pretty new the BLE development stuff and was mostly working on an application that works with an existing connection. But because my colleagues are not able to work on the problem at the moment, I had to ask here.

The problem I am facing right now is, that I am not able anymore(!) to connect our device running an nRF52820 chip to an Raspberry Pi (4) running Raspbian (Kernel version: 4.19)

I already opend a private ticket and one of the Nordic Members, Kenneth, helped me interpret the log files. He came to the following conclusion:

Kenneth said:
Looking close at the sniffer log I can see the raspberry connect with a very, very slow connection interval of 697.5ms (frame #2085 in muse log file). In addition it seems that the raspberry after a while simply stop sending any packets, the last packet from the raspberry is frame 3190, this is acknowledged at frame 3191 by the peripheral. After this the raspberry just stop communication for unknown reason.

 Has anyone an idea whats causing the slow connection interval? Or had anyone a similar problem?

Any help is much appreciated. Thanks in advance

Simon

Parents
  • Hi again,

    I don't have any suggestion for your problem with slow interval initially, however you may on the peripheral handle this in some way. You should find BLE peripheral examples that include conn_params_init(), this module can initiate a connection parameter update if the interval is outside of the preferred connection parameters. Maybe you can try to give that a go to see if that may workaround your problem?

    Kenneth

Reply
  • Hi again,

    I don't have any suggestion for your problem with slow interval initially, however you may on the peripheral handle this in some way. You should find BLE peripheral examples that include conn_params_init(), this module can initiate a connection parameter update if the interval is outside of the preferred connection parameters. Maybe you can try to give that a go to see if that may workaround your problem?

    Kenneth

Children
No Data
Related