Issues on implementing DIS client on multilink central

RE: Issues on implementing DIS client on multilink central

Petter Myhre — Tue, 23 Jan 2018 15:09:59 GMT

Sorry for the late reply, I have had the flu for some days now. Have you solved this? The end handle of primary service discovery response being 0xFFFF shouldn't be a problem, it is normal. It is not used for anything is it?

If you haven't solved it, I will try to look into the fault. Let me know.

RE: Issues on implementing DIS client on multilink central

Arthur — Wed, 17 Jan 2018 09:54:02 GMT

Hi Petter,

Thank you for your help. The fix does keep it running and the LBS works fine. However, I still see two issues even it doesn't break.

First, the end_handle for DIS is still invalid. Second, I still see a failure message (I cannot find out where the code located yet). Below is the log I've got.

app: Multilink example started.

app: Start scanning for device name Nordic_Blinky.

app: Connection 0x0 established, starting DB discovery.

ble_db_disc: Starting discovery of service with UUID 0x1523 on connection handle 0x0.

app: Start scanning for device name Nordic_Blinky.

ble_db_disc: Found service UUID 0x1523.

ble_db_disc: primary srv discovery rsp uuid 1523 handle: start B end 16

ble_db_disc: entering descriptors_discover()

ble_db_disc: leaving descriptors_discover() - return code

ble_db_disc: entering descriptors_discover()

ble_db_disc: leaving descriptors_discover() - success

ble_db_disc: Discovery of service with UUID 0x1523 completed with success on connection handle 0x0.

ble_db_disc: Starting discovery of service with UUID 0x180A on connection handle 0x0.

ble_db_disc: Found service UUID 0x180A.

ble_db_disc: primary srv discovery rsp uuid 180A handle: start 11 end 65535

ble_db_disc: entering descriptors_discover()

ble_db_disc: leaving descriptors_discover() - return code

ble_db_disc: Discovery of service with UUID 0x180A completed with success on connection handle 0x0.

app: call to ble_lbs_on_db_disc_evt for instance 0 and link 0x0!

ble_lbs_c: Led Button Service discovered at peer.

app: LED Button service discovered on conn_handle 0x0

ble_lbs_c: Configuring CCCD. CCCD Handle = 14, Connection Handle = 0

ble_lbs_c: SD Read/Write API returns Success..

ble_dis_c: Device Information Service discovery failure .

app: BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST.

ble_lbs_c: writing LED status 0x1

ble_lbs_c: SD Read/Write API returns Success..

app: LBS write LED state 1

ble_lbs_c: writing LED status 0x0

ble_lbs_c: SD Read/Write API returns Success..

app: LBS write LED state 0

app: Link 0x0, Button state changed on peer to 0x1

app: Link 0x0, Button state changed on peer to 0x0

RE: Issues on implementing DIS client on multilink central

Petter Myhre — Tue, 16 Jan 2018 13:40:37 GMT

I think this is happening because you have dis_c_init_obj.evt_handler = NULL; in dis_c_init() in main.c and when the discovery is complete the application jumps to an invalid address.

I also think that there should be something like

VERIFY_PARAM_NOT_NULL(p_ble_lbs_c_init->evt_handler);

in ble_dis_c_init() like it is in ble_lbs_c_init().

Try doing dis_c_init_obj.evt_handler = dis_c_evt_handler; and something like:

/**@brief Handles events coming from the DIS central module.
 *
 * @param[in] p_dis_c     The instance of DIS_C that triggered the event.
 * @param[in] p_dis_c_evt The DIS_C event.
 */
static void dis_c_evt_handler(ble_dis_c_t * p_lbs_c, ble_dis_c_evt_t * p_dis_c_evt)
{
    switch (p_dis_c_evt->evt_type)
    {
        case BLE_DIS_C_EVT_DISCOVERY_COMPLETE:
        {

            NRF_LOG_INFO("DIS service discovered on conn_handle 0x%x",
                         p_dis_c_evt->conn_handle);

        } break; // BLE_DIS_C_EVT_DISCOVERY_COMPLETE
        default:
            // No implementation needed.
            break;
    }
}

RE: Issues on implementing DIS client on multilink central

Petter Myhre — Mon, 15 Jan 2018 17:29:51 GMT

Thanks. I have been able to reproduce, but I'm not 100 % sure what is going on. Looking into it.

RE: Issues on implementing DIS client on multilink central

Arthur — Mon, 15 Jan 2018 10:29:20 GMT

Yes, I have added the DIS service to the ble_app_blinky example. The modified codes are uploaded in the file ble_app_blinky_dis.zip.

RE: Issues on implementing DIS client on multilink central

Petter Myhre — Thu, 11 Jan 2018 11:52:53 GMT

What do you mean by ble_app_blinky example with DIS enabled? You have added the DIS service to the ble_app_blinky example? Could you share that project as well?

RE: Issues on implementing DIS client on multilink central

Arthur — Thu, 11 Jan 2018 01:29:02 GMT

I am connecting to a board loaded with ble_app_blinky example with DIS enabled. I have tested it with nRF connect on iPhone and both LBS and DIS data show up correctly.

RE: Issues on implementing DIS client on multilink central

Petter Myhre — Wed, 10 Jan 2018 15:39:11 GMT

I think I have got it working. What should I connect it to? A standard example in the SDK or do you have a modifed peripheral example as well?

RE: Issues on implementing DIS client on multilink central

Arthur — Wed, 10 Jan 2018 03:26:50 GMT

Hi Petter,

Thanks for your help. I have uploaded the files I have added/modified as it took forever to upload the whole project. I've put ble_dis_c* under the same directory as main.c and added a few lines of codes for debugging in ble_db_discovery.c.

Arthur

RE: Issues on implementing DIS client on multilink central

Petter Myhre — Tue, 09 Jan 2018 13:16:25 GMT

Would it be possible for you to share your complete project so I can test it here?