OpenThread
Device responding to ff03::1 and not responding to its address fd8f:c605:8837:1:1e6b:88bb:80cc:fb76 #7670
Replies: 1 comment 9 replies
-
|
The route tables on beaglebone look all good. I think we need to capture Thread traffic to diagnose this issue. Thread info on SS4 can also be helpful:
|
Beta Was this translation helpful? Give feedback.
-
On SS4 I'm using Thermostat example provided ty TI in simplelink_cc13xx_cc26xx_sdk_5_30_01_01 (when I print Thread version on CLI example provided on the same sdk it showed me Thread 1.2.24 ). I notice one directional arrows aswell on Thread Topology Monitor software Unfortunately SS4 don't have CLI which I can access, so only diagnostic information's I have are that one which I'm sending through Coap message (EUI64, ipaddr). What might be reason for asymetrical links? Whay its happen? |
Beta Was this translation helpful? Give feedback.
-
|
If the border router's router table continues to show that the link quality is 3 in one direction but 0 in another direction, then there seems to be an issue with establishing that link. One reason could be that the RSSI is significantly different send sending from A -> B than from B -> A. Without some additional visibility into SS4, it's difficult to determine the root cause. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, now I named all devices in Thread Topology Monitor so it will help. I have turned off all devices and turned on only SS4 which has a problem. Below information's from BR: Position of devices havent changed. Only change was disconnecting devices from power. As seen SS4 established link and LQ In is 3 and LQ Out is 1. Ping response is OK. So next test would be turning on Thread Topology Monitor and showing all this data again below ot-ctl router table Done Done Done root@beaglebone:/home# ot-ctl ipaddr root@beaglebone:/home# ot-ctl netdata show root@beaglebone:/home# ot-ctl neighbor table root@beaglebone:/home# ping fd8f:c605:8837:1:1e6b:88bb:80cc:fb76 Looks like LQ Out for 0xa400 after turning on Thread Topology Monitor has changed from 1 to 0 and I'm able to see ping response. I will be appreciated for comment to that and if you see any sense in that? |
Beta Was this translation helpful? Give feedback.
-
|
Link Quality value 1 indicates a poor link quality. For reference, Thread uses 3 to indicate the highest link quality and 0 to indicate no usable link. If the Link Quality value is 1, then it likely indicates that the received signal strength at SS4 from the border router is very low, which means small environmental factors can easily affect whether or not the border router and SS4 can successfully communicate. |
Beta Was this translation helpful? Give feedback.
-
|
I changed Texas Instruments SDK from 5.30.00.3 to 6.10.00.29 and since then I haven't had problems with asymmetrical links. Thank you Jonathan and Simon for help with that! |
Beta Was this translation helpful? Give feedback.
-
Hi, I lost ideas to find reason of described below issue.
I was running whole night 3 devices SS1, SS4, SS7 connected to Border Router (Beagle Bobne with Nordik nRF52840 USB dongle).
As you can see they was working over night quite stable. At 7.05 there is system reboot done by crone so I think SS7 not join network immediately after reboot.
Anyway my major problem is that just before 10 I lost communication with SS4 - just before PB1, PB2, PB3 was swich on.
SS4 device has ip address: fd8f:c605:8837:1:1e6b:88bb:80cc:fb76 and when I ping ff03::1 I see that this device replay
but when I ping with device ip address it don't respond
Below infomation which I collected on BR.
As end devices I'm using CC1352 TI LPSTK's. I have done test with more than 50 devices in network and this issue is seen since I moved from Thread 1.1. I'm loosing any idea how to find what is the reason that device responding to broadcast address but not responding to his unique IP address.
Beta Was this translation helpful? Give feedback.
All reactions