User Manual
Table Of Contents
- About This Guide
- Introduction
- Kit Installation
- iB-5209 Network Monitor Operations
- iB-5209 Network Monitor Overview
- Setting Thread Priority
- Configuring a Node’s Operation
- Using Watch function to display current I/O information
- Configuring Sample Interval of Single Node
- Configuring Sample Interval of all Network Nodes
- Configuring Digital I/O Operation
- Configuring UART Operation
- Configuring AD (analog-to-digital) Converter Operation
- Configuring RS-232 Operation (RT-5209 only)
- Configuring RS-485 Operation (RT-5209 only)
- Labeling i-Bean Endpoint or i-Bean Router
- Creating an Event Log File
- Configure Persistence Attributes
- Configure Serial and ADC Data Formats
- Select Com Port on Host PC
- View Monitor Statistics
- View Contents of Event Log File
- Enable Multiple Capture
- API Functions
- Sample Application
3-2 EK-5209-5 Evaluation Kit User’s Guide
iB-5209 Network Monitor Operations
iB-5209 Network Monitor Overview
Millennial Net’s iB-5209 Network Monitor is a monitoring and management system for iB-5209
networks. This management tool will discover and display active i-Bean Routers in the vicinity of
the i-Bean Gateway, and i-Bean Endpoints in the range of the i-Bean Gateway and i-Bean
Routers as shown in Figure 3-1. iB-5209 Network Monitor displays the Group ID and Device ID
of the i-Bean Gateway and will display only i-Bean Endpoints and i-Bean Routers that have the
same Group ID as the i-Bean Gateway. (For information on opening a iB-5209 Network Monitor
session, see ’Launching iB-5209 Network Monitor’ on page 2-12.)
Using iB-5209 Network Monitor, a number of the monitoring features may be observed:
• Any of the i-Bean Endpoints can be moved, and as long as they are within the
range of an i-Bean Router or the i-Bean Gateway, connectivity will be maintained
seamlessly. Any of the i-Bean Routers and even the i-Bean Gateway can be moved while
operating, and all routes will automatically adapt to their new locations.
• The i-Bean network routing protocol always seeks to route data using the most
reliable RF links and using the fewest hops. The network protocol will change the
route when an RF link in the route is deemed unreliable. This can be seen in the iB-5209
Network Monitor. For example, the i-Bean Router IDs used for the first and last hops may
change from time to time even when the i-Bean Endpoint is stationary, due to
environmental interference.
• If any of the i-Bean Routers runs out of battery power or is turned off, all routes
that went through that i-Bean Router will be reconfigured—all i-Bean Endpoints
communicating with that i-Bean Router will still be connected to other i-Bean
Routers without any disruption or loss of packets. However, if an i-Bean Endpoint
exceeds the range of the network due to the loss of an i-Bean Router, then the i-Bean
Endpoint will be displayed as Offline or removed from the display (depending on how the
Persistence function is configured).
Figure 3-1. Sample iB-5209 Network Monitor window