Difference between revisions of "Mesh network"
From AMTech WikiDocs
(→Configuration) |
(→Configuration) |
||
| Line 9: | Line 9: | ||
*set baud rate to 230400 [8] | *set baud rate to 230400 [8] | ||
*set API enable to API mode without Escapes [1] | *set API enable to API mode without Escapes [1] | ||
| − | *[[File:Digi-serial-configuration.png| | + | *[[File:Digi-serial-configuration.png|850px|thumbnail|center|serial configuration]] |
*make sure that all the bridges participating in the same mesh network have the same network identifier | *make sure that all the bridges participating in the same mesh network have the same network identifier | ||
**multiple mesh network can operate in the same zone as long they have different network id | **multiple mesh network can operate in the same zone as long they have different network id | ||
| − | *[[File:Mesh-networkid.png| | + | *[[File:Mesh-networkid.png|850px|thumbnail|center|network identifier]] |
*assumptions | *assumptions | ||
Revision as of 17:10, 25 May 2017
Powerful way to route observations. Range is extended by allowing data to hop node to node and reliability is increased by “self healing,” the ability to create alternate paths when one node fails or a connection is lost
- Network setup is simpler
- More flexibility to expand the network
- Increased reliability in environments where routers may come and go due to interference or damage
Configuration
- Digi XBee radio configuration
using digi xctu tool https://www.digi.com/products/xbee-rf-solutions/xctu-software/xctu
- set baud rate to 230400 [8]
- set API enable to API mode without Escapes [1]
- make sure that all the bridges participating in the same mesh network have the same network identifier
- multiple mesh network can operate in the same zone as long they have different network id
- assumptions
- the XBee 900HP radio has been configure with digimesh firmware
- the XBee 900HP radio must be connected to /dev/ttyUSB0 with the following configuration
- 230400/8/N/1/N - API 1
