Thread commisioning

[Martijn Jonkers]

Hi,

We are evaluating thread. And would like to build a basic demo app using a thread border router and a few sensors. We got the border router working with the coprocessor demo, it seems, and a rpi. And we got a coap-client application compiled and running.

But now we have a dataset retrieved from the border router, but how do we set this info in the client? We are not interested in dynamic complicated commisioning right now. We just want some hard coded authentication to be able to setup a working thread network (do we even need the dataset?)

Static networkid and authentication codes are not a problem as of right now. We just want some data transfer from a node to a remote coap server (I understand this should be possible).

We are using the NCS 1.9.0 and the nrf dongle with the nrf52840.

Thank you.

[Sigurd Hellesvik]

Hi

For the nRF52840, you can configure the Thread connection parameters using Kconfig (usually in prj.conf):
See Customizing pre-built libraries for configuration options.

Is this what you are looking for?

Regards,
Sigurd Hellesvik

[Martijn Jonkers]

sort of. I found that already. But it doesn't tell me how to use it. I am completely new to thread and this coap-client example and also that page does not really help. The thread border router gives me a dataset. What am I supposed to do with that? The coap-client examples only sets a networkkey. I do not have a network key. Do I need a networkkey? Do I need the dataset? What is a dataset? 

I know how to change configuration, but I do not know what it is supposed to be set to.

[Sigurd Hellesvik]

Martijn Jonkers said:

The thread border router gives me a dataset.

To avoid misunderstandings, could you show how such a dataset looks?

How do you get the dataset, through a Command Line Interface or the Web GUI?

Are you running the docker version or the manual install of the OpenThread Border Router (OTBR)?

Regards,
Sigurd Hellesvik

[Martijn Jonkers]

I myself did not implement the border router, I belief it is the docker version and the data set is retreived using the command line interface. 

This what I got, a large hex string: 0e080000000000010000000300001335060004001fffe00208ba4e7e231d7cdac00708fdbebfc27c9a2ce4051077d3802cc0b15639ae9a627f466c1025030f4f70656e5468726561642d643031340102d0140410c066dd368fdaae8a0a6e654c3162b0f40c0402a0fff8

[Sigurd Hellesvik]

Martijn Jonkers said:

the data set is retreived using the command line interface. 

Which command did you use to retrive the dataset?

Regards,
Sigurd Hellesvik

[Martijn Jonkers]

we used this guide. https://openthread.io/codelabs/openthread-border-router#3

sudo ot-ctl dataset active -x

[Sigurd Hellesvik]

Hi

From the OpenThread CLI documentation, the "-x" appended to the dataset will make it return hex. Try to do the same command without the "-x".

Also, I can recommend our guide on the Thread Border Router. Still, both would be the OpenThread Border Router, so should not really be a difference.

Regards,
Sigurd Hellesvik