MeshDynamics' MD4000 Modular MeshTM
houses 4 high power (400 mw) Wi-Fi radios in one enclosure.
Slots 0, 1 are as uplink and downlink for our Structured MeshTM backhaul.
All MD4000 nodes, when wired to an Ethernet switch, automatically self configure to
become root nodes. Other (wire-less) nodes then connect to
them and a tree-like topology is formed.
The secure backhaul frequency band is typically 5.8GHz or 4.9GHz. 2.4GHz may also be used.
Slots 0,1 provide the tree-like meshed backhaul. The remaining 2 slots
are configured to support these application categories
: For stationary or slowly changing RF environments [More]
: Intended for dynamic RF environments and/or mobile vehicles. [More
Radio Edge Nodes
. (Software) For OEM CPE devices or mobile man
wearable units (e.g. for Military, Public Safety)
Contact us to discuss your custom configuration and application.
See: MeshDynamics Model
Static Mesh Nodes do NOT have a mobility scanner. They are not intended for
mobile scenarios. Standard models are:
Click on an image to access application
notes on that configuration.
Note: 2.4Ghz, 4.9Ghz backhauls also supported
0-AAxx is the bare bones 2
-radio model Structured Mesh 5
backhaul. The backhaul
capacity is 22 Mbps TCP/IP or 44 Mbps TCP/IP in Turbo Mode (54 Mbps Raw, 108
It is used where no client access is required. e.g. Video surveillance
cameras plug into the Ethernet Port
as shown here
The 4250 is
also used to connect two remote sub trees, as shown here
B. The MD4350-AAIx
is a 3
GHz backhaul, with a 2.4GHz (802.11b/g) AP in slot
3 for client access. It is our most popular static node configuration.
Note that there is only one AP radio, if more power or focused beams are
need, consider the 4458
C. When more backhaul capacity is needed
is a 4
-radio model with 2
provides twice the downlink capacity: 44 Mbps TCP/IP or 88 Mbps Turbo TCP/IP
(108 Mbps raw, 216 Mbps Turbo). Intended to backhaul traffic from two forks
of the tree, may be used either a root or a relay (it has an uplink). It is therefore fault tolerant: if the Ethernet connection
fails it will become a relay and connect to another sub tree in
the network. The MD4454-AAAA
provides up to 88 Mbps/176 Mbps
Turbo TCP/IP but all
four radios are downlinks. Since it has no uplink it is always
used as a high
capacity root supporting up to four forks
and their sub trees.
D. When more client Access Points are needed:
MD4350, MD4452, MD4454
all have one 2.4GHz client radio and
hence one antenna,
generally omni-directional. To provide
more focused beams, MD4458-AAII and MD4458-AIII
two and three client radios. Using sectored antennas more focused power can reach occluded areas.
Multiple AP radios are also needed to point the RF bean in different
directions or inclinations: Example: The MD4458-AAII is
used in underground mining- the inclined tunnel shaft requires two service radios each connected to 180 degree inclined panel antennas facing opposite directions of the mine shaft.
Other products with a single AP proved inadequate - their single radio antenna could not be
inclined in two directions.
E. 2.4GHz Stationary Nodes Options
radios have almost twice the range
as 5.8GHz radios but the 2.4GHz RF space is generally congested and
no-interfering channels is limited to three. 2.4GHz backhauls are
best used to as edge nodes. [More
Two all-2.4GHz nodes are shown above. The MD4424-IIII is a 2.4GHz variant of MD4454.
It has 4X the radio energy of a single 2.4 AP and is intended for
directed beams at hot spots. All
four downlinks may also feed mesh chains using the MD4220-IIxx. The
MD4220-IIxx is a 2.4GHz variant of MD4250.
downlink is a 2.4 radio, provides client access and
between 5.8GHz and 2.4GHz Meshed Backhauls
is supported, as shown here
Beyond using 2.4GHz nodes at the edges of the network, 2.4GHz backhauls should be avoided:
there are only three non interfering channels and sharing Backhaul and
Client RF space undermines the effectiveness of Dynamic Channel Management [More
G. Additional Information
: regarding 4.9GHz
, FIPS 140/2, P3MTM Persistent
is located here
Intended for dynamic RF environments, mobility nodes use a
dedicated mobility scanner radio to monitor the RF environment and adapt to
a dynamic network topology. Think of the 5 in MD4455
as an "S", for scanner.
Click on an image above to access application notes on that
configuration. Note: 4.9Ghz backhauls also supported
MD4355 and MD4455 are "mobile" versions of the MD4250 and MD4350
The scanning radio in slot 3 "listens" to the RF environment and helps
the node make judicious parent node selections in a high speed mobility
environment. The MD4325 is a 2.4GHz scanner equipped version of the MD4220.
It will interoperate with the 4455: its 2.4GHz uplink will connect to the
most suitable 4455 using the 2.4GHz Client Access Point on the 4455 as a
parent's downlink [Illustration
: A cluster of mobile nodes will automatically form a
network with each other. If the cluster physically
separates into two smaller clusters, each will then become
its own independent network. If two separate
clusters/networks physically come together, one single
network will form and all nodes + associated clients will
then be able to share data. In a
deployed combat environment in Iraq, MD4325 and MD4455 and vehicle-mounted nodes
demonstrated reliable connectivity between convoy vehicles in
simultaneous motion. Networks split and reformed dynamically
and in real time. Applications supported by MeshDynamics
systems operated flawlessly as vehicles moved through rugged
], [Military Solutions
B. Additional Information
: regarding 4.9GHz
104/2, P3MTM Persistent
is located here
List for Standard Configurations
List of Standard Configurations, 5.8GHz backhauls
1. 4250-AAxx: 2 radios, 11a uplink, downlink, slots 0,1. Intended as static
backhaul, no AP for clients. Example
2. 4350-AAIx: 3 radios, 11a uplink, downlink, slots 0,1. Both 11b and 11g
service available on slot 2 Slot 3 empty..
3. 4452-AAIA: 4 radios, 11a uplink, downlink, slots 0,1. Both 11b and 11g
service available on slot 2. Second downlink in 3.
4. 4454-AAAA: 4 radios, All 11a downlinks, slots 0,1,2,3. Intended as a root
node, with four sectored antennas. .
5. 4458-AAII: 4 radios, 11a uplink, downlink, slots 0,1. Both 11b and 11g
service available on sectored antennas, slots 2, 3
6. 4458-AIII: 4 radios, 11a uplink in slot 0, no downlink. Slots 1,2,3 are
sectored service 11b+11g radios for client access.
7. 4455-AAIA: 4 radios, 11a uplink, downlink, slots 0,1. Both 11b and 11g
service in slot 2. 11a scanning radio in slot 3.
8. 4355-AAxA: 3 radios, 11a uplink, downlink, slots 0,1, No client AP, wireless
backhaul only. 11a scanning radio in slot 3.
9. 4000-FIPS: 4-radio modules, radio functions configured per military
customer requirements. Support: 5.8GHz, 4.Ghz, 2.4GHz.
List of Standard Configurations, 2.4GHz Backhauls
1. 4220-IIxx: 2 radios, 11b+11g uplink, downlink, slots 0,1. Used as 11b+11g
long range backhaul, sectored links, rural areas.
2. 4424-IIII: 4 radios, ALL downlinks, slots 0,1,2,3. Supports 11b and 11g.
Intended as root, with four sectored services.
3. 4325-IIxI: 3 radios, 11b uplink, downlink, slots 0,1. 11b scanning radio in
slot 3. Longer range edge mobility node
1. All models use 400 mw 802.11a/b/g Mini-PCI AtherosTM
based field replaceable radio cards. See: Cover
2. All models support three backhaul frequencies: 5
.9GHz (e.g. MD424
0) and 2.4GHz (e.g. 422
3. All models are remotely configurable
. Models may be field
upgraded through the NMS and inserting additional radio cards
4. All models support an internal GPS Radio
. Must be factory installed, requires modifications to enclosure.
5. All models may be ordered in an Intrinsic Safe enclosure powered by 3.3VDC
. Must be factory
6. All models may be ordered to be FIPS 140/2
. Must be factory
installed, requires modifications to enclosure.
7. All models support P3MTM Persistent
. The Factory default setting is P3M disabled. User enables
through the NMS.