Hi
I have tried to run the thread topology monitor. Each attempt ends in this log message "Error - No response from Thread CLI device.".The COM-port has been chosen a dongle is available in the USB port. The software has been unpacked from nRFTTMwin32x6401201alpha.zip and execute out the unpacked folder.
Please let me know what is missing.
Hi Ryan,
How did you program the dongle ? Which dongle did you use ?
As far as I know the TTM tool is only supporting nRF52840 development kit, not the dongle (yet) . Please follow the documentation here.
Hi Hung
Hi Ryan,
To be able to use the TTM you would need the nRF52840 Development Kit, code name PCA10056 not the dongle.
Hi Hung,
Just for my understanding. Does this mean that I cannot use TTM to monitor a live mesh Thread network? Or will the development kit give access to the network.
I am asking because a seminar i December gave the impression that TTM along with nRF52840 would provide a very fine tool monitor such network.
As you have noticed am I new to this and would like to have more hints on how to actually test and monitor my network.
Thanks in advance
Hi Ryan,
The TTM can monitor a live mesh Thread network, doesn't matter if the mesh nodes running on the DK or the dongle , or can run on other 3rd party vendor.
But to be able to let the TTM running on PC to access the Thread network, you would need a backend device to talk to Thread network. And for now only the PCA10056 is compatible with the TTM software.
So in sort, you can use the dongles PCA10059 to form your network, but you need at least one PCA10056 connects to PC to use with TTM.
Hi Hung,
I am beginning to understand that I have to bite the dust and get my hands on a 52840-DK to achieve what I am trying to do.
Thank you so much for helping me so far
Hi again Ryan,
I'm sorry but I was just testing and found that actually it's possible to run the TTM with the nRF52840 dongle (PCA10059).
You just need to flash the \Thread_ZigbeeSDKv2.0\examples\thread\cli\usb_bootloader example into the PCA10059 and make sure the USB driver for it is installed correctly (you have a new COM Port ) and you can use TTM to open that COM Port to join thread network. You can use the precompiled hex in that folder.
To flash the firmware to the dongle you would need to use the nRFConnect -> Programmer app and put the dongle into bootloader mode (the LED breathing Red).
Note that the COM Port it created should be different from the COM Port that the dongle creates when in DFU mode.
If windows couldn't install the COM port, you may want to point Windows to the CDC driver at \SDKv15.2\examples\usb_drivers
Hi again Ryan,
I'm sorry but I was just testing and found that actually it's possible to run the TTM with the nRF52840 dongle (PCA10059).
You just need to flash the \Thread_ZigbeeSDKv2.0\examples\thread\cli\usb_bootloader example into the PCA10059 and make sure the USB driver for it is installed correctly (you have a new COM Port ) and you can use TTM to open that COM Port to join thread network. You can use the precompiled hex in that folder.
To flash the firmware to the dongle you would need to use the nRFConnect -> Programmer app and put the dongle into bootloader mode (the LED breathing Red).
Note that the COM Port it created should be different from the COM Port that the dongle creates when in DFU mode.
If windows couldn't install the COM port, you may want to point Windows to the CDC driver at \SDKv15.2\examples\usb_drivers
Hung,
This is indeed good. I now have my TTM running and I am able to monitor the system. :-)
Thank you very much
Regards
Ryan Pedersen
Hung,
I am running the TTM but am facing a message that I do understand. In the log I see this "Error - polling not possible due to incorrect state." It is not possible to see the origin of the error, is it in the TTM? Does one of the nodes cause this, then which one is it?
Can I enable debug or more logging?
Is v0.12.0-1.alpha the most recent TTM?
Hi Ryan,
Could you take a screenshot when the issue happens. What happened after that log appeared ? How often do you see the error ?
This is what it looks like
Hi Ryan,
I'm sorry for late response. Could you explain how often do you see this error ? It happened on any setup or in particular setup you have ?
It looks like the dongle was not in any network when the issue occurred.
