Connectivity and Configuration Q&A

You are here:
Estimated reading time: 2 min
I want to commission a KTDG102 Dongle to a Thread Network, what should I do?

To add a KTDG Dongle to the list of nodes entitled by the Commissioner to join the specific network you are interested in, you simply have to provide the Commissioner the KTDG Dongle EUI64 and Joining Credentials. By default the Joiner Credential is the same as the EUI64, but as a string of ASCII characters, for easier retrieving of the commissioning information from the sticker placed on the enclosure of the KTDG Dongle. However, it can be modified at any time.
To get the KTDG Dongle EUI64 and Joining Credentials do the following:

kinos@local:~$ show eui64
kinos@local:~$ show joincred


I tried to configure a KTDG102 Dongle, command syntax is OK, but it still doesn’t allow it. What’s happening ?

As required by Thread network self-healing feature, the dongle is designed to store its last network configuration and to load it up at power on to be able to re-join the network it was participating in. Therefore, if there is a valid network configuration stored in non volatile memory, the network configuration commands are disabled to avoid overwriting it.

To verify if the dongle has a valid network configuration ask the device for its status.

kinos@local:~$ show status
none – saved configuration

To be able to configure again the dongle you MUST clear its current configuration with the clear command.

Another scenario in which the KTDG102 Dongle won’t allow configuration is while its Thread interface is up and running. Once the interface up command has been sent to the dongle, it is not possible to configure it again.


I want a KTDG102 Dongle to automatically boot at power on without any command. Is it possible ?

Yes. The USB dongle is designed to showcase the full potential of the KTWM102 module, which is designed to be controlled by host processors as a NCP. Therefore, thinking in standalone devices we offer the possibility to boot up and re-join your old network. To enable this feature configure the KTDG102 device as follows.

kinos@local:~$ config autojoin on
Once this feature is enabled, the device will start network connection and joining processes automatically at each power on. To stop it from running, send the interface down command. This will stop the KTDG USB Dongle while connecting to the network but will not disable the automatic joining feature. To do so revert the command shown above (config autojoin off).
I configured a KTDG102 Dongle as Thread End Device. Configuration is correct but when I boot the device it doesn’t connect to any network. What’s happening ?

Thread End devices do not have the ability of building a standalone network. They always require the presence of at least one router. Therefore if you boot up an End Device but there is no router in the network , the device will fail in its attempt to connect to a network.

Another scenario is related to Commissioning Credentials. To be able to connect to a network the device must be among the ones entitled by the Commisioner. Check that the Commissioner of the network you are interested in has the KTDG Dongle Joiner Credentials stored.


I want a KTDG Dongle to work as Border Router. Do I need some special settings ?

To be able to run as a Border Router the Ethernet interface of the KTDG Dongle must be enabled. Request the device´s hardware configuration to check it.

kinos@local:~$ show hwconfig
USB Interface
Serial       : on
DFU          : on
Ethernet     : on
UART Interface : off
Activity LED   : on
Low-Power Mode : off

In case the USB Ethernet interface is not enabled, it can be enabled as follows.

kinos@local:~$ config hwmode 4

Once the KTDG Dongle has been connected to the network and it is working as active router, the border router functionality can be enabled as follows.

kinos@local:~$ config brouter on