Fortress Technologies BreadCrumb Wireless Network manual Device power To Device power Distance

Page 24

Chapter 4. Deployment Considerations

Unobstructed LOS is not necessary from every BreadCrumb device and wireless client to every other BreadCrumb device and wireless client. However, each device must have unobstructed LOS to the previous and subsequent device.

Distance

Many factors determine acceptable distances between BreadCrumb devices when deploying a BCWN.

If many devices are placed too closely together, it is possible that interference will degrade the performance of the system.

Devices that are placed too far away or in RF "shadows" may experience total loss of connection.

Device power is important in determining distances over which the device will be effective.

The following table can be used as a guide to determine best-case distances between devices with regard to their power:

 

Device (power)

 

To Device (power)

 

Distance

* 1

BreadCrumb device (200mW)

 

BreadCrumb device (200mW)

 

Up to 5km (3.1 miles)

with external antenna

 

with external antenna

 

 

 

BreadCrumb device (200mW)

 

BreadCrumb device (1W)

 

Up to 10km (6.2 miles)

with external antenna

 

 

 

 

 

BreadCrumb device (1W)

 

BreadCrumb device (1W)

 

Up to 15km (9.3 miles)

Notes:

 

 

 

 

 

 

a. These distances are representative of optimal deployment settings:

 

 

Optimal antenna selection

 

 

 

 

Clear, unobstructed LOS between devices

 

 

Absence of other RF interference

 

 

Full battery power

 

 

 

 

Clear weather

 

 

 

 

 

 

 

 

 

 

 

Table 4-1. Best-Case Distances by Radio Power

Tip: It is recommended when deploying a BCWN that you choose initial distances between devices that are half the distance as quoted in Table 4-1.

When placing a BreadCrumb device, check the connection status to the nearest available device using either the BreadCrumb device’s status LED (described in Appendix A), or BCAdmin (described in Chapter 5). If the connection is poor or non-existent, attempt to relocate the BreadCrumb device closer to another device until an acceptable connection is obtained. If a poor connection or no connection is made at even relatively close distances, you should refer to Chapter 7.

18

Image 24
Contents For the BreadCrumb Wireless Network Release Rajant CorporationPage Table of Contents Using BCAdmin TroubleshootingConfiguration Examples List of Tables List of FiguresPreface Purpose and ScopeUser Information What is a BreadCrumb? IntroductionMobility through Meshing Mesh a DefinitionBreadCrumb Devices Mesh by Channel and Essid ExampleMeshing Example 1 Full Connectivity New Features Performance / Process Improvements Issues ResolvedKnown Issues Upgrading to VersionInstalling / Upgrading BCAdmin Upgrading BreadCrumb FirmwareUpgrading to Version Flash Update Procedure for Version 2 and Version 3 Systems Version 3 Power InputUpgrading to Version Models XLV XLEBreadCrumb ME ModelsAvailable BreadCrumb Models External Connectors BreadCrumb WEBreadCrumb WE External Connectors BreadCrumb SEBreadCrumb SE External Connectors BreadCrumb XLBreadCrumb XL External Connector BreadCrumb XLVBreadCrumb XLV External Connectors BreadCrumb XLE BreadCrumb XLE External Connectors front Deployment Considerations AddressingChannel Assignments BreadCrumb Device AddressesPhysical Placement and Other Considerations Line Of SightDeployment Considerations Device power To Device power Distance Best-Case Distances by Radio PowerDistance Weather InterferenceAltitude Using BCAdmin Screen LayoutUsing BCAdmin Topology AreaAnatomy of the BreadCrumb Box BreadCrumb Device NameTime Since Last Update Anatomy of the Client BoxNumber of Peers Number of ClientsAnatomy of a Connection Line 802.11b Channel Line ColorBCAdmin Line Styles Legend Info Area Redundant Connection ExampleConfiguring Individual BreadCrumbs Link Detail TabsGeneral Settings NameType LocationUsing BCAdmin Color Battery Warning minutesManual GPS Settings Latitude and Longitude AirFortress Encryption AES-256 and Set Access IDRadio Settings Access PointChannel MeshReachback Settings Reachback InterfaceNone EthernetUsing BCAdmin Radio Radio 2 ad hocMode AutomaticUsing BCAdmin Gateway Ingress DisabledAlternate Gateway WEP KeyForwarding Settings 11. BreadCrumb Properties Forwarding TabSecurity Example Port Forwarding Configuration for a Web ServerAccess Control Lists ACLs WEPKey Deny by default allow only permitted devices Allow by default deny only forbidden devicesAES-256 Encryption with AirFortress Registering AirFortressSetting the Access ID 14. Set Access ID WindowEncrypting Wired Traffic Zeroizing the Access IDHarris SecNET11 Enabling/Disabling AirFortress EncryptionBCAdmin Preferences SecNet11 Key FillingBreadCrumb inactivity threshold seconds Mapping with Fugawi Tracker Connecting Remote Wired LANs Configuration ExamplesUnencrypted Point-to-Multipoint Encrypted Point-to-PointConvoy with UAV-Based Camera for Forward Observation Configuration ExamplesEncrypting a Video Feed Configuration Examples Troubleshooting BreadCrumb Wireless NetworkIndividual BreadCrumbs Sporadic Network ConnectivitySporadic Network Connectivity Issues BreadCrumb Device Cannot Connect to BcwnBCAdmin Restoring Default Settings Factory ResetTroubleshooting BreadCrumb-BCWN Connectivity IssuesFactory Reset Button Case Study Military Exercise in Thailand Joint Exercise NetworkBCAdmin screen during exercise showing BreadCrumb network Case Study Military Exercise in ThailandBalloon with Camera and BreadCrumb BCAdmin Glossary802.11b BreadCrumb / BreadCrumb DeviceMAC Address PeerPending peer Reachback Appendix A. Status Indicator LED Color Blinking/Solid StatusTable A-1. LED Status Indications Appendix B. Radio Frequencies 802.11b Channel Frequency GHzTable B-1 .11b Channel Frequency Table Appendix C. Customer Service