Mesh - Daisy Chain Networks

This page describes using Air-Frame 100 models in Mesh, Daisy-chain or Relay network configurations. Mesh networks are cost effective when:

• When one or more locations are out of cost-effective or 'legal' range.
• When you do not have line-of-sight to a client location from an Access Point but one or more of the clients have a line-of-sight (a 'dog-leg' configuration).
• When climatic or other conditions mean that you have a 'marginal' link to a client at certain times of the day or even from season to season.
• During network build-out when it is not cost-effective to immediately install an new Access Point.
• As a natural 'dual-route' solution i.e. clients can be multi-routed - in the event of a failure they will automatically pick up the alternate location.

Mesh Network Diagram

Description:

Daisy Chain (or Relay) networks are typically used when remote locations are either difficult or not cost-effective to reach in a single 'hop'. The diagram shows two Daisy-chained client networks:

Net A	Access Point 1 (AP1) can see Client 1 (C1) but not Client 2 (C2) or Client 3 (C3).
Net B	Client 1 can see AP1 and Client 2 (C2) but not Client 3 (C3).
Net C	Client 2 can see Client 1 (C1) and Client 3 (C3) but not AP1.
Net D	Access Point 2 (AP2) can see Client 4 (C4).

In the above network if all the Clients are left in 'auto-route' mode (the default) the following will occur:

• C1 would find the shortest way home via AP1
• C2 would find equal hopping to AP1 and AP2 and would select the strongest signal.
• C3 would find the shortest way home via C4 to AP2.
• C4 would find the shortest way home via AP2.

In all cases the clients can be configured to use a specific route e.g. C3 MUST use path via C2 -> C1 -> AP1. Finally the clients can be configured to 'roam' finding the best way at user defined intervals or 'always-on' mode in which case they will find any alternate route in the event of a failure in their primary route. For further explanation of Air-Frame route finding capabilities.

Daisy chaining Notes

The following notes apply when designing for Daisy-Chain networks:

1. The total latency at each Air-Frame 100 Client in Daisy Chaining mode is ~2 ms.
2. Any bandwidth limits placed on the Access Point to visible client e.g. (AP1 to C1 in above diagram) will apply to all data arriving via the Client including ALL Daisy Chained nodes.
3. There is no theoretical limit to the depth of Daisy Chaining but a practical limit is likely around three hops.

If you have any questions or comments contact info@steampacketradio.com