ARMmbed / ARMmbed/ble

"connection parameters update request" CALLBACK IS MISSING FROM MBED STACK

Open
#185 12 comments 0 reactions 0 assignees View on GitHub
mirrored
Dominant language
C++
Stars
81
Forks
71
PR merge metrics
No merged PRs in 30d

Description

in repository Bluetooth Low Energy / BLE_API the function updateConnectionParams is returning the error 3 (wrong parameters). This is needed, when in master role, to reply to the parameter update request coming from the peripherial, according to this chart: http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s130.api.v2.0.0%2Fgroup___b_l_e___g_a_p___c_e_n_t_r_a_l___c_p_u___m_s_c.html&cp=3_6_2_1_0_2_1_3_2

More big problem, is that the peripherial is sending to the master the "connection parameters update request" but the Mbed stack don't implement a callback to inform the user about this request.
I know it because I sniffed the packets.
As a result, after 1 minute the peripherial disconnects from the master.

Note: the peripherial is a Polar H7 Heart rate sensor.
The nRF51822 is the master with MBED code.

Contributor guide

Open the contributing guide

Research direction

Start by tracing updateConnectionParams in the BLE_API and compare its behavior with the Nordic connection-parameter update chart linked in the issue. Reproduce the exchange with the Polar H7 and nRF51822 if available; done means the master can handle the peripheral's request through a user-visible callback and avoids the reported disconnect.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
embedded-iot, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.