nRF5 SDK for Thread and Zigbee
nRF Thread Topology Monitor is a desktop application that helps to visualize the current network topology. The application requires a serial connection to an nRF52840 Development Kit with Nordic’s Thread solution.
Supported operating systems:
Follow these steps to install nRF Thread Topology Monitor:
After starting nRF Thread Topology Monitor, the main window of the application appears. It consists of the following elements:
nRF Thread Topology Monitor requires a serial port connection to a local nRF52840 Development Kit. The nRF SoC on the development kit is controlled by the nRF Thread Topology Monitor that sends OpenThread CLI commands to it over serial port. Therefore, it must be programmed using the OpenThread CLI example.
Note that nRF Thread Topology Monitor filters serial ports to show only those with J-Link support. Therefore, only nRF52840 Development Kits that are communicated over J-Link UART can be used with the application.
Follow these steps to set up a local device:
If the nRF SoC is the first Thread device in the network, it becomes a Leader, as shown in the figure below.
After other Thread devices have been attached to the network, nRF Thread Topology Monitor visualizes them as shown in the figure below.
The panel to the right of the main application window contains the Configuration section. Because nRF SoC acts as an OpenThread CLI device, you must configure the basic Operational Dataset. During this configuration, you can specify the following parameters of the Thread Network:
Apart from Thread network configuration, you can also specify two parameters related to polling:
nRF Thread Topology Monitor allows to select a specific node in a Thread network and perform operations on it:
threaddirectory of this SDK, LEDs on this device will start blinking.
The background process of nRF Thread Topology Monitor communicates with nRF SoC using OpenThread CLI, sending commands described in OpenThread CLI Reference.
The application first attaches the nRF SoC to the network and then periodically retrieves the current list of routers. Each router is polled by sending the standard Thread diagnostic messages (MGMT_DIAG.req). In response, routers in the network send their current link set (current connected neighbors), child table, and basic network parameters, such as Network Address or Extended MAC Address.
This section contains some known issues that you can encounter when using Thread Topology Monitor.
An nRF Thread device does not change its Radio Channel/PAN ID/Master Key.
Thread parameters listed above are a part of Operational Dataset that can be changed only after factory reset. Make sure to check the Perform factory reset checkbox to change these network parameters.
A node in the Thread network changed its name to the default one, even after I set a custom label.
Thread protocol randomly chooses a new Extended Address on the Perform factory reset procedure. Therefore, the application cannot match its Extended Address with the previously assigned label.
After being a Thread Leader, I restarted the application with the Perform factory reset checkbox checked. Now I cannot see the topology.
nRF Thread device connected to the Thread Topology Monitor has to become a Thread Router to obtain all routing information. In Thread protocol, only the Leader of the network can allow a Child to become a Thread Router. If the Leader has been restarted and some other Thread Routers exist in the network, they need to time out the previous Leader and elect a new one. This procedure may take up to two minutes.
nRF Thread Topology Monitor shows the Cannot open /dev/ttyACM0: Permission denied log under Linux OS.
The user does not have sufficient permissions to access the /dev/ttyACM0 serial port. You must add the current user to a proper group and log out to refresh the user credentials. The group name is distibution-dependent and in order to read it, run the following command:
For example, on the Ubuntu distribution, the group name is dialout.
nRF Thread Topology Monitor shows the EACCES: permission denied, open '/home/USERNAME/.config/nRF_TTM/storage/commdataset.json' log under Linux OS.
The user does not have sufficient permissions to access storage files that keep information like the last configuration and node names. nRF_TTM might have been run with sudo permissions for the first time and now the application is run without them.
On Linux platform, the libgconf library is required to run nRF Thread Topology Monitor.
Install the missing dependency using your package manager. For example, under Ubuntu, type: