How to find source/destination address within mesh model callback function?

RE: How to find source/destination address within mesh model callback function?

choehyunho — Tue, 10 Mar 2020 12:02:19 GMT

Mistake is mine.

I have confused with other callbacks in SDK.

access_message_rx_meta_t has the required information in it.

Thank you.

RE: How to find source/destination address within mesh model callback function?

Hung Bui — Tue, 10 Mar 2020 10:24:54 GMT

Ah sorry I miss understood your question. In that case, yes you can modify the code inside p_rx_msg. As long as it doesn't change the behavior of the module (regarding Mesh activity), it's fine.

RE: How to find source/destination address within mesh model callback function?

Hung Bui — Tue, 10 Mar 2020 10:23:37 GMT

You can get the src and dst of any message regardless which model it is. Please check the p_rx_msg for example in the model call back handler. It's the variable with access_message_rx_t format:

It's inside p_rx_msg ->meta_data

RE: How to find source/destination address within mesh model callback function?

choehyunho — Tue, 10 Mar 2020 03:21:56 GMT

I know.

I meant, if I want to get addresses when I use BT SIG model implementation in Mesh SDK, I should modify SDK code.

I just want to know whether there is no other way.

RE: How to find source/destination address within mesh model callback function?

Hung Bui — Mon, 09 Mar 2020 16:00:00 GMT

Hi,

You can find the meta information (source, destination) inside access_message_rx_meta_t struct this struct is inside access_message_rx_t p_message that you get in the call back for message in the model.