MNZB-DKL-900 MeshNetics, MNZB-DKL-900 Datasheet - Page 36

• Manufacturer Part Number: MNZB-DKL-900
• Description: KIT DEV ZIGBIT 900 LITE 45DAYS
• Manufacturer: MeshNetics
• Type: 802.15.4/Zigbeer

Specifications of MNZB-DKL-900

• Frequency: 868MHz, 915MHz
• For Use With/related Products: MNZB-900-B0
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Other names: 758-1010

© 2008 MeshNetics
4.6. Running WSNDemo
4.6.1. Starting WSNDemo on MeshBean2 nodes
4.6.2. Setting up node timeouts
Notice: the full path to the file depends on the root directory which has been specified
during installation of the Development Kit (see Section 3.3).
NodeNames.txt contains one “-- NodeNames --” header string which is followed by a
number of strings each of which contains 64-bit MAC address and the title of each node.
For example, see Figure 9.
If the NodeNames.txt file is not found or its format is not recognized, the WSN Monitor
designates the titles named by default.
Figure 9. Example of file containing the node titles
First, connect the coordinator node to the USB or to serial port, in accordance with the J3
jumper setting (see Table 7). Next, run the WSN Monitor application on your PC. At
startup, WSN Monitor will attempt using the default COM port to connect to coordinator.
The WSN Monitor screen pops up but the coordinator node icon would not yet appear on
the Network Topology Pane (see Figure 8). You have to set a proper COM port via
Connection/Settings menu (see Figure 10). Restart the program if the icon would not
appear.
The Connection/Settings menu contains a number of parameters. Timeouts are
used to tune up visualization for coordinator, routers and end devices because they
disappear from the network each time when link drop, power down, or reset occur. A node
timeout means the waiting period, during which the WSN Monitor is expecting to receive
data packet from that node, which would update the network Topology tree. To get
smooth topology visualization, setting timeouts to 3 sec is recommended for coordinator
and router and 30 sec is recommended for end device. Those timeouts cover 3 periods
between packet sending.
Z I G B I T ™ 9 0 0 D E V E L O P M E N T K I T 1 . 3
U S E R ’ S G U I D E
Page 36/56