Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The mote listens for advertisement messages sent by the 
    Include Page
    _def_mgr
    _def_mgr
     or 
    Include Page
    _def_mote
    _def_mote
    s already in the network.
  • Once it hears such an advertisement, in synchronizes to the network, and starts the joining process with the 
    Include Page
    _def_mgr
    _def_mgr
    . Note that this can be done even when the 
    Include Page
    _def_mgr
    _def_mgr
     is multiple hops away from the joining 
    Include Page
    _def_mote
    _def_mote
    .
  • Once the joining process is finished, the 
    Include Page
    _def_mote
    _def_mote
     is Operational. It has been assigned some "base bandwidth" from the 
    Include Page
    _def_mgr
    _def_mgr
    , allowing it to send infrequent traffic to the 
    Include Page
    _def_mgr
    _def_mgr
    .
Tip

Refer to the SmartMesh IP User's Guide for a detailed description of the joining process.

...

  • Configure the network identifier of the mote. This parameter is stored in non-volatile memory, so your application does not need to do this step every time this the device boots. In particular, during development, you can set the network identifier through the mset netid CLI command, and reboot the part.
  • Optionally, configure the join duty cycle of the mote to the appropriate trade-off point between joining speed and average power consumption during the searching process.
  • Ask the 
    Include Page
    _def_smip
    _def_smip
     stack to search for a network and join, by calling the dnm_loc_joinCmd() function.
  • Monitor the events received from the the 
    Include Page
    _def_smip
    _def_smip
     stack. The mote is joined when your application receives the DN_API_LOC_EV_OPERATIONAL event.

...