Installation of nRF Thread Topology Monitor on Raspberry Pi.

[Sohaib]

Hello, 

I have created a thread network using Raspberry Pi's and nRF52840 dongles. I want to monitor the topology using the nRF tool, I have installed the Segger J-link packages and the other required commands as per this tutorial. https://infocenter.nordicsemi.com/pdf/nRF_Thread_Topology_Monitor_User_Guide_v1.0.pdf 

But still I am not able to open the executable file. Please help me out with this. 

 

Secondly, I want to measure the network performance of the thread network, is there any dedicated software or tool for that from nordic. 

[Charlie]

Hi Sohaib,

1) Did you follow chapter 3 exactly? I tested on a Ubuntu 20.04 PC. After running "sudo apt-get install libgconf-2-4", I can successfully run the executable file. Please also remember to enable execute permission for it.

2) I am not sure which kind of performance you expect to check. Please search through the following places to get some inspiration.

devzone.nordicsemi.com/

Issues · openthread/openthread (github.com)

openthread-users - Google Groups

Best regards,

Charlie

[Sohaib]

Thanks Charlie for your reply. Yes I went through all the steps, but as I mentioned I was doing it on Raspberry Pi where Raspbian was installed, does it make any difference if the OS is not Ubuntu but Raspbian. 

About the network performance, I meant to say, as I have a thread network developed using nRF52 dongles, and they are communicating together over MQTT. How can I measure the End-to-end Latency, Time for Complete Coverage, Packet Delivery Ratio, Node Reception Rate etc. 

[Charlie]

Hi Sohaib,

1) Sorry for miss understanding, I thought you use Raspberry Pi and nRF52840 dongle as OTBR to form a thread network. nRF Thread Topology Monitor only support X86 Linux. Rapsbain is a special version of Linux running on ARM processors, so it does not work.

2) I search through the thread communities and there is no specific guidance for performance tests, but you can find some discussion about latency. For the items you mentioned, I believe you would be able to design tests based on NCS thread samples and log outputs from the devices. UDP/CoAP is typically used on top of Thread since TCP/MQTT need much more resources. CoAP can request a response to ensure the packet is successfully delivered.

Best regard,

Charlie

[Sohaib]

Thanks a lot Charlie.