• State Not Answered
  • Replies 63 replies
  • Subscribers 63 subscribers
  • Views 12443 views
  • Users 0 members are here
Attachments (3) Download All
Nordic Case Info
  • Case ID: 252243
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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.

Parents
  • 0

    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

  • 0 in reply to Jørgen Holmefjord

    Hi Jørgen:

    How are you today!

    Is there any update?

    Pls kindly help advise how to solve it?

    Best Regards,

    Rick.

  • 0 in reply to Jørgen Holmefjord

    Hi Jørgen

    How are you today!

    Thanks for your explanation.

    But I have a case that needs to use the mobile phone or PC control the Thread Device. Pls kindly advise how can get the IP address of Thread Device from a mobile phone or PC?

    Or you have any advice can be using a mobile phone or PC control Thread Device?

    Best Regards,
    Rick.

  • 0 in reply to Jørgen Holmefjord


    Hi Jørgen:

    How are you today!

    Are you have any advice?

    Pls kindly help advise how to solve it?

    Best Regards,

    Rick.

  • 0 in reply to Rick

    Hi Rick,

    I can't think of any simple way to do that. Does the phone/PC have IPv6 connectivity? Is the border router and the phone/PC in the same local network?

    The nodes would somehow have to communicate with a central server/point, where the phone/PC could get their IP from a database. If the nodes and the phone/PC both have global IPv6 connectivity, it is possible to communicate directly between the nodes once the phone/PC get hold of the IPv6 addresses.

    If you can provide more details about your use-case, we may be able to help you with finding the best approach and/or alternative solutions.

    Best regards,
    Jørgen

  • 0 in reply to Jørgen Holmefjord

    Hi Jørgen,

    My case The border router and the phone/PC in the same local network, and is supported IPv6.

    The premise Phone/PC does not know the Thread Network Device IP now.

    So I need to search the Thread Device IP address from Phone/PC.

    Best regards,
    Rick

    This is my case framework.

  • 0 in reply to Rick

    Hi,

    I consulted with some colleagues and we can't think of any other solution to this than the one I already suggested in my previous post.

    Neither the phone, nor the AP router is aware of the Thread network's presence. The Border Router is aware of the network and can do a multicast ping as I described before, in order to get IPv6 addresses of the Thread nodes. This can be stored in a known location where the phone can query the list of know devices. The nodes in the Thread network can also advertise themselves to a network/cloud server, where the phone can get the list of attached devices. This is not solutions that we provide today, but is something you need to implement as part of your system/solution.

    Best regards,
    Jørgen

Reply
  • 0 in reply to Rick

    Hi,

    I consulted with some colleagues and we can't think of any other solution to this than the one I already suggested in my previous post.

    Neither the phone, nor the AP router is aware of the Thread network's presence. The Border Router is aware of the network and can do a multicast ping as I described before, in order to get IPv6 addresses of the Thread nodes. This can be stored in a known location where the phone can query the list of know devices. The nodes in the Thread network can also advertise themselves to a network/cloud server, where the phone can get the list of attached devices. This is not solutions that we provide today, but is something you need to implement as part of your system/solution.

    Best regards,
    Jørgen

Children
Related