How to interact with connected devices through the device manger

RE: How to interact with connected devices through the device manger

Petter Myhre — Mon, 10 Oct 2016 13:45:44 GMT

I'm not aware of any side effects, other than requiring more RAM.

RE: How to interact with connected devices through the device manger

Andreas — Fri, 07 Oct 2016 14:03:27 GMT

So, I am now able to discover all characteristics from the peripheral. Also I am able to write a charactersitic. Surprisingly this works only after a complete discover. Even if I hardcode the characteristics handle!?

By implementing this, I found out, that BLE_DB_DISCOVERY_MAX_CHAR_PER_SRV is set to 3. In my application I have 19 characteristics in one service. Is it enough to change 3 to 19? I did this for the moment. And it seems to work. Does this have any side effects to the discovery module?

RE: How to interact with connected devices through the device manger

Petter Myhre — Thu, 06 Oct 2016 13:28:41 GMT

I don't know what you have to do. I don't know what your application is. For a client to be able to access a characteristic value, descriptor++ on a server it needs to have the attribute handles of these. These are normally obtained by doing a service discovery. If you know the attribute handles, you could also hack it and hard code the them. Yes, there are several examples, in \examples\ble_central

RE: How to interact with connected devices through the device manger

Andreas — Thu, 06 Oct 2016 08:36:50 GMT

Ok, after looking into the multilink example, I am pretty sure that I have to discover all the services and characteristics that are available on the connected peer. Right!? Normally I would say this doubles the work. Because I know with what kind of device I am connected. So I should know which, services and characteristics are available. For example, I know, that the device I want to interact with, has two services, one with 20 characteristics, and one with 4 characteristics. Which data fields do I have to adjust when looking at the multilink example? Or will all these information be stored in the m_client[].srv_db data field when doing a discover? Is there an example, how to set up a propper communication to a peripheral on the central side?

Regards, BTprogrammer

RE: How to interact with connected devices through the device manger

Petter Myhre — Wed, 05 Oct 2016 14:21:36 GMT

Well, yes, it handles multiple connections, but only the pairing and bond information aspect. You get the connection handle with the BLE_GAP_EVT_CONNECTED event. Then you can use the handle do identify events on that connection, and do operations, like write, on that connection. In ble_app_multilink_central you can see that connection handle is assigned with ble_lbs_c_handles_assign() when you get the BLE_GAP_EVT_CONNECTED in on_ble_evt().

RE: How to interact with connected devices through the device manger

Andreas — Wed, 05 Oct 2016 14:07:18 GMT

Hi Petter, thanks for your reply. Yes, in my understanding, the device manager handles multiple connections to more than one peripheral at the same time. Right!? I had a deeper look into the S120 multilink example. There I found, that the interaction is done by the client_handling.c file/functions. Yes, I mean the connection handle. I found out that it seems to work with sd_ble_gap_disconnect(m_client[systemID].srv_db.conn_handle, BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);. So the connection handle is part of the m_client array. Right!? Regards

RE: How to interact with connected devices through the device manger

Petter Myhre — Wed, 05 Oct 2016 13:40:16 GMT

Why are you mixing device manager into this? Device manager handles pairing and bond information, it is not used for writing to a characteristic value. You are correct about sd_ble_gattc_write(). What handle do you mean? The connection handle or the attribute handle?