This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Thread cli

Does commands 

>Thead down           and

>Ifconfig down 

Commands are equivalent to power failure reset of node in mesh network

  • Hi,

    These commands will take down the Thread and IPv6 interfaces, so for the network, it may appear similar to a power failure of the device.

    Best regards,
    Jørgen

  • I am using eui64 commands to comission the mesh node, if power failure occurs at a node , when the node restarts , is it necessary to commission the node again or will it connect to mesh automatically??

  • The OpenThread stack stores persistent network data automatically in flash. You should not need to recommission the device after a power failure/reboot. However, you need to make sure that the firmware does not use the default masterkey and on boot (most of our examples use autocommissioning and use default masterkey from OpenThread).

  • I followed this tutorial https://codelabs.developers.google.com/codelabs/openthread-hardware/#8

    in which commissioning  the FTD joiner using eui64 command doesn't need to have same master key, 

    I repeatedly asked the same question and received the same answer,

    It would be better if someone says exactly what happens after reset , if i commission the  mesh as mentioned in above tutorial using eui64 command

    The reason is due to covid , I just theoretically studied how to develop mesh using openthead cli  to interface 30 nodes, I can't implement practically to see the results (Can't access the hardware as far now) and also time to complete the project is very less, 

  • the commands needed to commission the network as mentioned in above tutorial is shown below

    ## FTD Joiner ##
    ----------------
    
    > eui64
    2f57d222545271f1
    Done
    
    
    
    ## FTD Commissioner ##
    ----------------------
    
    > commissioner start
    Done
    > commissioner joiner add 2f57d222545271f1 J01NME
    Done
    
    
    
    ## FTD Joiner ##
    ----------------
    
    > scan
    | J | Network Name     | Extended PAN     | PAN  | MAC Address      | Ch | dBm | LQI |
    +---+------------------+------------------+------+------------------+----+-----+-----+
    | 1 | OpenThread-c0de  | c0de7ab5c0de7ab5 | c0de | 1ed687a9cb9d4b1d | 11 | -45 |  48 |
    
    
    ## FTD Joiner ##
    ----------------
    
    > ifconfig up
    Done
    > joiner start J01NME
    Done
    
    ## FTD Joiner ##
    ----------------
    
    >
    Join success
    
    
    ## FTD Joiner ##
    ----------------
    
    > thread start
    Done
    > state
    child
    Done
    > rloc16
    0c02
    Done
    
    ## FTD Joiner ##
    ----------------
    
    > ipaddr
    fdc0:de7a:b5c0:0:0:ff:fe00:c02         # Routing Locator (RLOC)
    fe80:0:0:0:e4cd:d2d9:3249:a243         # Link-Local Address (LLA)
    fdc0:de7a:b5c0:0:3e2e:66e:9d41:ebcd    # Mesh-Local EID (ML-EID)
    
    
    
    ## FTD Commissioner ##
    ----------------------
    
    > router table
    | ID | RLOC16 | Next Hop | Path Cost | LQ In | LQ Out | Age | Extended MAC     |
    +----+--------+----------+-----------+-------+--------+-----+------------------+
    |  3 | 0x0c00 |        3 |         0 |     0 |      0 |  50 | 1ed687a9cb9d4b1d |
    
    > child table
    | ID  | RLOC16 | Timeout    | Age        | LQ In | C_VN |R|S|D|N| Extended MAC     |
    +-----+--------+------------+------------+-------+------+-+-+-+-+------------------+
    |   1 | 0x0c01 |        240 |         25 |     3 |   89 |1|1|1|1| 1ae529b3a638943b |
    |   2 | 0x0c02 |        240 |         15 |     3 |   44 |1|1|1|1| e6cdd2d93249a243 |
    Done
    

Related