NRF5 SDK Thread Message Sequence Charts

[jannik1810]

Hello,

I started developing a Thread-Solution with my NRF52840-DK. Now I'm searching if there is a Message Sequence Chart (like for the BLE solution) also for the Thread SDK. I already started with the examples but they don't really offer an detailed overview like the sequence charts. Does anyone know if there are some available (maybe also from OpenThread or Thread Group)?

Thanks, Jannik

[Edvin]

Hello,

Most of the Thread documentation is available from IEEE's website, but you have to log in to see it.

https://ieeexplore.ieee.org/document/8373620

Is it something in particular you are looking for?

The Thread protocol is not as time sensitive as the BLE protocol. This is why we can support BLE + Thread multiprotocol applications. Please see the multiprotocol information page on infocenter.

You can also find a lot of information on openthread's website.

Best regards,

Edvin

[jannik1810]

Thanks for the fast reply! I tried to access the document but you have to be paying member. I was searching for at particular kind of flowchart which describes all steps I have to make to create a thread device (full function router with coap). The examples consists of these functions but they are just in one kind used and the api reference shows only all available functions. Is there anythink like this?

[Edvin]

Hello,

Well. I can't give out anything that isn't public available.

Have you looked at the documentation for our coap examples?

http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.thread_zigbee.v2.0.0%2Fthread_client_server_example.html

Best regards,

Edvin

[jannik1810]

Hello,

I already saw the example description. It consists of basic information but not of a progress diagram like:

1. Call xxx_init()
2. Call xxx_register...
3. ...

Is there something like this or do I have to extract the progress from the examples?

Best regards, Jannik

[Edvin]

Hello,

I am sorry. We don't have any posts or tutorial like this. 

The only thing I found was something like this on OpenThreads website.

But I think the best approach would be to look at an example that somewhat resembles what your final application will look like, and try to understand what's going on.

Maybe if you go through the testing of this example, and look at the source code of the project to understand what's going on.

BR,

Edvin