Device manager timeout handler and related event

RE: Device manager timeout handler and related event

ppatierno — Tue, 28 Jul 2015 12:54:45 GMT

Thank you very much Aryan !

RE: Device manager timeout handler and related event

Susheel Nuguru — Tue, 28 Jul 2015 12:51:05 GMT

I think the security of the link does not effect the service discovery. you can do a service discovery on both secure and open link. This is ok as service discovery information is meant to be public. After having some thinking, I am not really sure for the reason of this delay. I will have to dig more into apple specifications. I do not have the setup to try it here, my opinion is it should just work fine if you do not use this delay and start the security setup immediately

RE: Device manager timeout handler and related event

ppatierno — Tue, 28 Jul 2015 11:48:28 GMT

I lost this point ... it means that the service discovery starts and is executed before the link is secure ? If I avoid the delay and execute setup security without time what happens to the service discovery ?

RE: Device manager timeout handler and related event

Susheel Nuguru — Tue, 28 Jul 2015 11:44:40 GMT

it usually suggested to delay sending security request because we should allow the client to finish service discovery, I am actually not sure why this example has made it as a requirement, I will have to dig into it.

RE: Device manager timeout handler and related event

ppatierno — Tue, 28 Jul 2015 11:43:02 GMT

Just because I'm so curious but why in this example the security setup was delayed ? You said it's a mistake but IMHO setup a timer and execute security inside it seems to be an action that the developer wanted (not just a mistake).

RE: Device manager timeout handler and related event

Susheel Nuguru — Tue, 28 Jul 2015 11:38:49 GMT

I see your point, The security setup was delayed by 1500ms (SECURITY_REQUEST_DELAY) and luckily the m_conn_handle was updated before the app_timer call back was called. This is a mistake (not a bug) in ANCS example but this but will never get triggered because m_conn_handle gets updated in time. Like I said, you can fix this by updating the m_conn_handle in DM_EVT_CONNECTION.

RE: Device manager timeout handler and related event

ppatierno — Tue, 28 Jul 2015 11:32:38 GMT

Thanks for the reply Aryan !

I started from ANCS example and the code is made in this way (you know it better than me) : dm_event_handler that starts timeout timer (in the DM_EVT_CONNECTION event) to setup the security on the link instead of execute it in the dm_event_handler itself.

Why ?

RE: Device manager timeout handler and related event

Susheel Nuguru — Tue, 28 Jul 2015 11:29:12 GMT

Hi ppatierno,

In most of our examples we did not have the dependency of the order in which the event_handlers for modules are called. If your example needs that m_conn_handle needs to be update in dm_event_handler then you can update it by just adding something like this

case DM_EVT_CONNECTION:
    m_conn_handle = p_event->event_param.p_gap_param->conn_handle;

The requirement of the order in examples is depending on particular use case.

or even change the order in which the event handlers are called inside ble_evt_dispatch