Thread Border Router networking fail

[Rick]

Hello Nordic Taam:

I follow the WEB steps below

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_tz_v4.1.0%2Fthread_ot_performance_measurement.html

Software Development Kit > nRF5 SDK for Thread and Zigbee v4.1.0 > Thread > Thread tools > Thread Border Router

nRF52840 DK Version：nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\ncp\ftd\uart\hex

Raspberry Pi 3 Version：RaspPi_OT_Border_Router_Demo_v4.1.0-1.alpha

Use nRF52840 DK UART connect Raspberry Pi 3 to get the following information

wpan0 => [
"NCP:State" => "associating"
"Daemon:Enabled" => true
"NCP:Version" => "OPENTHREAD/20191113-00534-gc6a258e3; NRF52840; Apr 5 2020 21:51:18"
"Daemon:Version" => "0.08.00d (; Apr 21 2020 19:11:43)"
"Config:NCP:DriverName" => "spinel"
"NCP:HardwareAddress" => [F4CE363EC3C45B0E]
]

pi@raspberrypi:~ $ sudo wpanctl status
wpan0 => [
"NCP:State" => "uninitialized"
"Daemon:Enabled" => true
"NCP:Version" => ""
"Daemon:Version" => "0.08.00d (; Apr 21 2020 19:11:43)"
"Config:NCP:DriverName" => "spinel"
"NCP:HardwareAddress" => [F4CE363EC3C45B0E]
]

If I have the wrong steps or have not completed, please give me some pointers, thank you.

Also, can you teach me how to set up the Thread Border Router successfully on Raspberry Pi 3?

Best Regards

Rick.

[Jørgen Holmefjord]

Hi,

The instructions on Thread Border Router is the latest and should be correct. It also looks like you are using the correct versions of the firmware and border router image. 

I have tested this multiple times before, and have not had any issues with getting the network up and running.

Are you using a revision 1 DK or later? Did you have the DK connected to the RPi before you booted it? Did you run 'erase all' command on the DK before flashing the NCP FW? You did not run any other commands on the border router prior to the "sudo wpanctl status" command?

If nothing works, I would suggest that you start over and flash the DK and border router image again to the devices to see if that solves any issues.

Best regards,
Jørgen

[Rick]

Hi Jørgen:

How are you today!

Is there any update?

Pls kindly help advise how to solve it?

Best Regards,

Rick.

[Rick]

Hi

OK, I will try this example  "Thread thethings.iO Cloud CoAP Client Example".

"simulate it" is I want to use this example.

 

Pls Could you view the case and reply, Thanks.

 Thread device can't join the Thread network in Thread Google Cloud Platform CoAP Example

Best Regards,

Rick.

[Rick]

Hi Jørgen

 I try this example  "Thread thethings.iO Cloud CoAP Client Example".

but it get the error response "HTTP/1.1 400 Bad Request" and {"status":"error","code":400,"message":"Unexpected token '"}

curl -i -H "Accept: application/json" -H "Content-Type: application/json" -d '{"values":[{"key":"temp","value":"0"},{"key":"counter","value":"0"}]}' -X POST "">api.thethings.io/.../GITM86uZNPu9Ukmja16PM-X-enajMxP01PODgS3tYVI" -k

following is my thethings.iO information

Pls kindly help advise how to solve it!

Best Regards,

Rick.

[Rick]

Hi Jørgen

I try this example "Thread thethings.iO Cloud CoAP Client Example".

I can post commands to thething.io from my PC, Dashboard page can show my send data.

but CoAP Client can't send to thething.io.

my version is :
nRF52840 DK Version：v3.2.0

nRF5_SDK_for_Thread_and_Zigbee_v3.2.0_9fade31 --> CoAP client node
Raspberry Pi 3 Version：RaspPi_OT_Border_Router_Demo_v4.1.0-1.alpha --> Border Router

1. My CoAP client node RTT show " DNS response error 28." and " DNS response error 1".

Pls kindly help advise how to solve it!

2. I only have IPv4, and I ues CLI send "dns resolve ipv4.google.com", it response error"DNS response for ipv4.google.com - Error 28: ResponseTimeout".

I can ping the PC directly from the border router.

3. My NAT64 feature can work properly?

4. Is this description setting from Raspberry Pi or CLI device?

Best Regards,

Rick,

[Jørgen Holmefjord]

It looks like you are able to ping Google DNS from the CLI, so that indicates that the connection should be ok. 

Can you try to do the DNS resolve command from the CLI, to check if you are able to get the IP from thethings.IO cloud solution, or if it is somehow blocked? I tested this on my setup right now, and it worked:

dns resolve coap.thethings.io fdaa:bb:1::2
> DNS response for coap.thethings.io - 64:ff9b:0:0:0:0:68c7:55d3 TTL: 299
Done

You should also make sure to use the examples from the latest SDK version (v4.1.0), and not the older v3.2.0.

[Rick]

Hi Jørgen

Thanks for your help.

My nRD52840 DK boards is revision 0.9.0 and 0.9.2. so I use SDK 2.0 and My phone share AP to Raspberry Pi, It can send data to thething.io. 

after SDK 3.1 to 4.2 version is not successfully work.
I will buy new boards to try the new versions.

BTW:

SDK can mixing use?
ex:
SDK 2.0 example thething for cloud is the device.
SDK 3.2 Border Router + RaspPi_OT_Border_Router_Demo_v4.1.0-1.alpha
or
SDK 3.2 example thething for cloud is device.
SDK 2.0 Border Router + RaspPi_OT_Border_Router_Demo_v2.0.0-1.alpha

Best Regards,

Rick.

[Jørgen Holmefjord]

Hi,

Using example applications from older SDKs should work in general. For the cloud examples, external things outside our control can change over time, making the documentation outdated.

Regarding the border router, there can be small changes in semantics between releases, breaking compatibility if you mix the versions. I would highly recommend using the NCP firmware from the corresponding SDK to the Border Router image used (i.e. nRF5 SDK for Thread and Zigbee v4.1.0 together with RaspPi_OT_Border_Router_Demo_v4.1.0-1.alpha, etc).

Best regards,
Jørgen