Network configurations
Routing
XBee/XBee-PRO DigiMesh 2.4 RF Module User Guide
56
DigiMesh throughput
Throughput in a DigiMesh network can vary due to a number of variables, including:
n
The number of hops.
n
If you enable or disable encryption.
n
Sleeping end devices.
n
Failures and route discoveries.
Our empirical testing shows the following throughput performance in a robust operating environment
with low interference.
Configuration
Data throughput
1 hop, encryption disabled
27.0 kb/s
3 hop, encryption disabled
10.9 kb/s
6 hop, encryption disabled
5.78 kb/s
1 hop, encryption enabled
20.5 kb/s
3 hop, encryption enabled
9.81 kb/s
6 hop, encryption enabled
4.70 kb/s
We performed data throughput measurements with the serial interface rate set to 115200 b/s, and
measured the time to send 100,000 bytes from the source to the destination. During the test, there
were no route discoveries or failures.
Transmission timeouts
When a device in API operating mode receives a Transmit Request (0x10, 0x11) frame, or a device in
Transparent operating mode meets the packetization requirements (
RO
,
RB
), the time required to
route the data to its destination depends on:
n
A number of configured parameters.
n
Whether the transmission is a unicast or a broadcast.
n
If the route to the destination address is known.
Timeouts or timing information is provided for the following transmission types:
n
Broadcast transmission
n
Unicast transmission on a known route
n
Unicast transmission on an unknown route
n
Unicast transmission on a broken route
Note
The timeouts in this documentation are theoretical timeouts and are not precisely accurate.
Your application should pad the calculated maximum timeouts by a few hundred milliseconds. When
you use API operating mode, use
as the primary method to determine if
a transmission is complete.
