what is the channel id different from other ruturn value,

RE: what is the channel id different from other ruturn value,

Hung Bui — Thu, 10 Aug 2017 11:38:39 GMT

@happykelvin: If you want us to be able to help you, you really need to improve the way you ask the question. You need to provide us enough information, and let us know what you are talking about. Which channel id you were talking about ? Are they L2CAP channel IDs?

RE: what is the channel id different from other ruturn value,

endnode — Wed, 09 Aug 2017 17:14:50 GMT

But rest of your question about "what's the return value when packet send fail and what is the channel id different from other return value" really doesn't make sense in the context of Nordic Soft Device API. Please read the documentation, see SDK examples for inspiration and then rephrase.

RE: what is the channel id different from other ruturn value,

endnode — Wed, 09 Aug 2017 17:14:21 GMT

Sorry Kelvin but your question doesn't make sense. ble_evt_t structure you get in Soft Device event handler callback function upon triggering by SD on any event differs event per event. You need to first see what event it is and then parse it accordingly. All is very well described in SoftDevice API on Infocenter (and in SD release), just read it. SD event handler typically calls several handlers from each module (like BLE Security Manager layer implementation = peer_manager, ble_db_discovery if you use it on GATT Client side etc.) and these filter just events they are interested in (rule is that none of the modules should catch and process the same event as it would be processed twice which would most probably cause some failure down the road...)