Rajant ME4-2450 Long Range Mobile Broadband Communications Device User Manual

Rajant Corporation Long Range Mobile Broadband Communications Device

UserManual.wiki >

ME4 2450 User Manual

User Manual

BreadCrumb® ME4v11 User GuideUser Guide Version: 11.0.0Software Version: 11.0.0Date: January 22, 2013Corporate Headquarters Rajant Corporation 400 East King Street Malvern, PA 19355 Tel: (484) 595-0233 Fax: (484) 595-0244 http://www.rajant.comDocument Part Number: 03-100126-011

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0FCC and IC StatementsThis equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the device is operated in a commercial environment. This device generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with this instruction manual, may cause harmful interference to radio communications. Operation of this device in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at their own expense.This Class A digital apparatus complies with Canadian ICES-003 and RSS-210 rules.Cet appareil numérique de la classe A est conforme à la norme NMB-003 et CNR-210 du Canada.Required Antenna SeparationThe FCC/IC wireless approval for this product is conditional on maintaining at least 20cm separation between the antennas. At least one of the antennas must be connected to the BreadCumb with 50 ohm coaxial cable. Low loss LMR400 cable is recommended for this application.WARNING: To satisfy FCC RF exposure requirements a minimum safe distance of 20 cm must be maintained between this device and all persons while the device is operating.CAUTION: To reduce potential radio interference to other users, the antenna type and its gain should be chosen so that the equivalent isotropically radiated power (EIRP) is not more than that permitted for successful communication.CAUTION: Changes or modifications not expressly approved by Rajant Corp. could void the user's authority to operate the equipment.3

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0GNU General Public License StatementCertain components of the Rajant BreadCrumb firmware are subject to the GNU General Public License Version 2, or other so-called open source licenses ("Open Source Software"). In compliance with the terms of certain Open Source Software licenses like the GNU General Public License Version 2 ("GPLv2"), Rajant makes certain modifications to Open Source Software that Rajant uses, modifies and distributes pursuant to such licenses available to customers in source code form upon request. You are free to use, modify and distribute Open Source Software so long as you comply with the terms of the relevant Open Source Software license. In particular, the GPLv2 is available in the appendix of this manual or at www.gnu.org/copyleft/gpl.html.4

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0Table of ContentsCopyright Statement.....................................................................................................................2FCC and IC Statements................................................................................................................3GNU General Public License Statement......................................................................................4Preface..........................................................................................................................................71 Introduction to BreadCrumbs................................................................................................81.1 What is a BreadCrumb?.....................................................................................................81.2 Mobility through Meshing...................................................................................................91.2.1 Mesh – A Definition.....................................................................................................91.2.2 BreadCrumb Mesh Connections................................................................................92 Description of a BreadCrumb ME4......................................................................................102.1 Radios...............................................................................................................................102.2 Enclosure..........................................................................................................................102.3 Antenna Connectors.........................................................................................................112.4 26-Pin Amphenol Connector............................................................................................122.4.1 Power........................................................................................................................122.4.2 Ethernet....................................................................................................................122.4.3 USB...........................................................................................................................122.5 ME4 Cable Assembly.......................................................................................................122.6 Status LED.......................................................................................................................122.7 LED Configuration / Zeroize Keys and Restore Factory Defaults Switch .......................132.7.1 LED Configuration....................................................................................................142.7.2 Zeroize Keys and Restore Factory Defaults............................................................143 Using BC|Commander...........................................................................................................164 Deploying a BreadCrumb Mesh Network............................................................................174.1 Addressing........................................................................................................................174.1.1 BreadCrumb Device Addresses...............................................................................174.1.2 DHCP........................................................................................................................174.2 Channel Assignments.......................................................................................................174.3 Physical Placement and other Considerations................................................................184.3.1 Line-of-Sight.............................................................................................................184.3.2 Distance....................................................................................................................184.3.3 Weather....................................................................................................................194.3.4 Interference...............................................................................................................194.3.5 Placement of Mesh Components.............................................................................194.4 Deployment Guidelines and Methodology.......................................................................204.4.1 Deployment Guidelines............................................................................................204.4.2 Deployment Methodology.........................................................................................205

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.05 Firmware Upgrade.................................................................................................................225.1 Over The Air Firmware Upgrade......................................................................................225.2 USB Firmware Upgrade...................................................................................................225.3 USB-Based Zerioze..........................................................................................................236 Troubleshooting.....................................................................................................................246.1 Sporadic Network Connectivity........................................................................................246.2 BreadCrumb Device Cannot Connect to Mesh................................................................256.3 BreadCrumb Power and Start-Up Issues.........................................................................25Appendix A: Radio Channels and Frequencies....................................................................27Appendix B: Error and Warning Codes..................................................................................32Appendix C: Using Pole Mount Bracket.................................................................................36Appendix D: Rajant End User License Agreement...............................................................37Appendix E: GNU General Public License.............................................................................45Index of FiguresFigure 1: BreadCrumb ME4 Enclosure Features (Front)...........................................................10Figure 2: BreadCrumb ME4 Enclosure Features (Back)............................................................11Figure 3: ME4 Pole Mounted Bracket.........................................................................................36Figure 4: ME4 Mounted to Pole..................................................................................................36Index of TablesTable 1: Status LED Color Codes...............................................................................................13Table 2: Configured and Alternate Display States of the Status LED........................................14Table 3: Default Channel Assignments.......................................................................................18Table 4: Sporadic Network Connectivity Issues.........................................................................24Table 5: BreadCrumb to BCWN Connectivity Issues.................................................................25Table 6: BreadCrumb Power and Start-Up Issues.....................................................................25Table 7: 900 MHz Radio Channels and Frequencies.................................................................27Table 8: 2.4 GHz Radio Channels and Frequencies..................................................................27Table 9: 4.8 GHz Radio Channels and Frequencies..................................................................28Table 10: 4.9 GHz Radio Channels and Frequencies................................................................30Table 11: 5 GHz Radio Channels and Frequencies...................................................................316

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0PrefacePurpose and ScopeThis manual provides information and guidance to all personnel who are involved with and use Rajant Corporation’s BreadCrumb ME4. This manual begins with an introduction to the BreadCrumb Kinetic Mesh Network. It then characterizes the features of the BreadCrumb ME4. Finally, it describes common deployment scenarios and provides concise step-by-step instructions for each scenario.Note Throughout this document, unless otherwise stated, the terms ME4 and BreadCrumb are used to refer to Rajant BreadCrumb ME4.Feedback WelcomeThe user of this manual is encouraged to submit comments and recommended changes to improve this manual and all Rajant products. Please send your feedback to support@rajant.com. Please be sure to include the version number of the manual or product you are using as well as the relevant page numbers if appropriate.Related DocumentationFor additional information, refer to these documents: ●BC|Commander® v11 User Guide: This document contains information on the BC|Commander management application, which is used to configure BreadCrumbs before or during a deployment.●BreadCrumb® Video Guide●Rajant Troubleshooting Range User Guide●RF Component Installation and Verification in BreadCrumb® Networks7

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.01 Introduction to BreadCrumbsRajant Corporation's (http://www.rajant.com) BreadCrumbs utilize the 802.11 wireless networking standards to form a wireless mesh network. The network is mobile, self-integrating, self-meshing, self-healing, and secure. The focus is on flexibility, adaptability, and simplicity.The BreadCrumb Kinetic Mesh Network is intended for rapid deployment of a broadband wireless network into a situation or “hot zone.” The network can be deployed as a stand-alone wireless network, or bridged to another network (such as the Internet) utilizing available reach-back communication links (such as a DSL, cable, or satellite modem).BreadCrumbs provide high bandwidth for applications to stream video, audio as well as data over large distances. The network traffic can be secured by using different security features available on the BreadCrumb. This makes the network optimal for tactical deployments as well as emergency response situations since it offers robustness, stability and ease of setup in mission critical activities.1.1 What is a BreadCrumb?A BreadCrumb is an IEEE 802.11 (Wi-Fi) and Ethernet compatible networking device which has the ability to connect to other BreadCrumbs or networking devices to form a BreadCrumb network. The BreadCrumb is specifically designed for the following scenarios:Temporary Wireless NetworksNetworks that must be established quickly and with minimal effort for short-term use (e.g., a network established to provide First Responder support at the site of a disaster).Mobile Wireless NetworksNetworks in which the network infrastructure itself is mobile, in addition to client devices (e.g., a convoy viewing a video stream from a UAV).Wireless Network ExtensionNetworks in which a wireless network must be quickly extended around or through obstacles that block wireless communications (e.g., urban canyon networks, tunnels/caves, etc.)Wired Network ExtensionNetworks in which two or more wired LANs at different locations must be connected wirelessly (e.g., to securely connect combat service support computers with logistics bases)Any Combination of the AboveMost BreadCrumb deployments include elements from more than one of the above scenarios.In many cases, BreadCrumbs will perform all of these tasks as shipped with no configuration necessary at all, providing an instant TAN (Tactical Area Network). Moreover, because BreadCrumbs use industry-standard 802.11 communications, client devices such as laptops, or cell phones require no special hardware, software, and little or no configuration to access a BreadCrumb network.NoteAlthough all BreadCrumbs can be access points, most access points do not provide mesh capability. Traditional access points simply allow wireless devices within range to connect to a wired network; they do not extend range through other access points.8

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.01.2 Mobility through MeshingThe key component of a BreadCrumb network is the ability for BreadCrumbs to connect, or Mesh with each other. While this is generally handled automatically by BreadCrumbs, complex deployment scenarios require a basic understanding of how BreadCrumbs establish and maintain a mesh.1.2.1 Mesh – A DefinitionA Mesh is a collection of BreadCrumbs (or other network devices), each of which is linked to one or more other BreadCrumbs. Data can move between BreadCrumbs via these links, possibly passing through several intermediate BreadCrumbs before arriving at its final destination.The intelligence of a BreadCrumb network is in how it adapts rapidly to the creation or destruction of the links in the mesh as devices are moved, switched OFF or ON, blocked by obstructions, interfered with by other devices, or otherwise affected. This adaptation takes place automatically and immediately as needed.1.2.2 BreadCrumb Mesh ConnectionsIn order for two BreadCrumbs to establish a mesh link to each other, they must be set to the same radio channel, and have the same Network ID. The Network ID is computed from the BreadCrumb's Network Name, Network Key, and a collection of Crypto settings. The Network Name is simply a name for a Mesh network. By default, BreadCrumbs use the Network Name "Rajant Mesh Network”. The Network Key is a passphrase or key used to secure the network. The Crypto settings include a packet cipher, MAC cipher, per-hop authentication, and a key sequence number. All of these settings on the BreadCrumbs can be configured using BC|Commander v11. The Crypto settings can only be configured if the application is logged into the BreadCrumbs using Crypto Officer credentials.Note Version 10 firmware uses the BreadCrumb's primary ESSID instead of the Network Name to form Mesh links.9

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.02 Description of a BreadCrumb ME4BreadCrumb ME4 is a portable, wireless device deployable in almost any environment. It is light in weight, supports up to 4 external antennas and is designed to be completely mobile as worn by an individual. The BreadCrumb ME4 must be powered by an external source.2.1 RadiosThe BreadCrumb ME4 contains two radios in the 900 MHz, 2.4 GHz, 4.9 GHz or 5 GHz bands. Custom radio configurations, including a mix of licensed, military or unlicensed frequencies are available upon request. There are several different models of ME4, each with a different combination of radios. See Appendix A for a list of the channels and frequencies supported by each of the radios.2.2 EnclosureThe ME4 enclosure has been designed to operate in extreme conditions, with protection against ingress of dust as well as protection against immersion in water. The enclosure dimensions are 189 mm x 95 mm x 51 mm (7.46” x 3.75” x 2.00”). The external features of the enclosure are shown in Figure 1 and Figure 2.Figure 1: BreadCrumb ME4 Enclosure Features (Front)10

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0Figure 2: BreadCrumb ME4 Enclosure Features (Back)2.3 Antenna ConnectorsThe BreadCrumb ME4 provides up to four Type N female antenna connectors. Two connectors are located on the top side of the enclosure (see Figure 1), the other two connectors are located on the bottom side of the enclosure (see Figure 2). In general, only one antenna port per radio is utilized. Some BreadCrumb models offer antenna diversity or Multiple-Input and Multiple-Output (MIMO) features, in which case two antenna ports per radio are utilized. There are many different ME4 Models available, each with a different configuration of radios and antennas. Each antenna connector will be labeled with the frequency of its corresponding radio. Important Most ME4 models do not support directly attaching antennas under FCC regulations.When using the pole mount option for deploying the ME4, care should be taken to make sure the antennas, and therefore the pole is mounted plumb. This is because most of Rajant's standard antennas are characterized by high-gain and therefore small vertical beamwidth. The small vertical beamwidth necessitates the antennas to be plumb, so that units using these antennas will see each other without a significant loss of signal strength. Warning To avoid possible damage to the BreadCrumb radio(s), always connect or disconnect external antennas with the power to the BreadCrumb ME4 turned off. 11

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.02.4 26-Pin Amphenol ConnectorThe majority of the signals and features of BreadCrumb ME4 can be accessed through the 26-pin Amphenol connector on the enclosure (see Figure 2). The most important of these interfaces are external power, Ethernet, and USB, which are described in more detail in the following sections. The 26-pin Amphenol connector interfaces to the ME4 cable assembly that provides access to input power, Ethernet and USB ports of the device.2.4.1 PowerThe input power interface to the BreadCrumb ME4 resides on the 26-pin Amphenol connector (see Figure 2). The device accepts external power in the range of 8 to 48 VDC. The average idle power consumption of BreadCrumb ME4 is 5.5 W at 24 V. The maximum peak power consumption of BreadCrumb ME4 is 19 W at 24 V.2.4.2 EthernetThe first Ethernet port (eth0) on the BreadCrumb ME4 supports 10 Base-T, 100 Base-TX or 1000 Base-T configuration. The second Ethernet port (eth1) supports 10 Base-T, or 100 Base-TX configuration. Both Ethernet ports can be accessed through the 26-pin Amphenol connector on the enclosure (see Figure 2). Both ports support Auto MDI/MDIX allowing the use of either straight-through or crossover data cables for connections. The data interface includes electrostatic discharge, and electrical fast transient/burst immunity compliant to the IEC 61000-4-2, and IEC 61000-4-4-EFT standards, respectively.The ME4 cable assembly plugs into the 26-pin Amphenol connector and provides two standard RJ-45 Ethernet connectors for easy access to the the ME4 Ethernet ports.2.4.3 USBThe ME4 contains one USB port, which can be access through the 26-pin Amphenol connector on the enclosure (see Figure 2). The port is compliant to the Enhanced Host Controller Interface (EHCI) and USB Transceiver 2.0 Macrocell Interface (UTMI+) Level 2 specifications. The port supports all three standard data transfer rates of low speed (1.5Mbps), full speed (12Mbps), and high speed (480Mbps). The power switch for the port includes over current protection, thermal protection, in-rush current limiting, and hot-plug noise filtering.The USB port can be used to perform BreadCrumb firmware upgrades and USB-based zeroize. It can also interface to an optional GPS receiver accessory available from Rajant.2.5 ME4 Cable AssemblyThe ME4 comes with a standard cable assembly that connects to the BreadCrumb's 26-pin Amphenol connector. The cable assembly includes two Ethernet ports and one USB port.2.6 Status LEDThe Status LED (see Figure 1) is capable of displaying warning and error codes, and link states. The LED Mode can be configured in BC|Commander to be ON (switchable), ALERTS ONLY (switchable), 12

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0OFF (non-switchable), or OFF (switchable). When the LED Mode is ON, the BreadCrumb LED alternates between displaying the link state and any warnings or errors. When the LED Mode is OFF, the BreadCrumb LED does not display any warnings, errors, or the link state. When the LED Mode is set for ALERTS ONLY, the BreadCrumb LED alternates between displaying the link state and any warnings or errors only if there are warnings or errors to report. If there are no warnings or errors, the LED displays nothing.The Status LED combines the three base colors of red, green and blue to display a broader spectrum of colors which indicate the current status of a BreadCrumb. The meanings of the color code indicators are given in Table 1.Table 1: Status LED Color CodesColor StatusWhite(red, green and blue LEDs together;may appear pale blue or pale green)Powered, early boot processRed-Blue-Green scrolling in succession Success, end of boot processSolid Blue Ready, but no peersBlinking Green At least one peerSolid Green At least one 24 Mbps or higher peerBlinking Yellow(at a constant rate) ProgressBlinking Yellow1(with short and long pauses between blinks) WarningBlinking Red1(with short and long pauses between blinks) ErrorAll Status LED colors scrolling in succession Success/Completion2.7 LED Configuration / Zeroize Keys and Restore Factory Defaults Switch The LED Configuration / Zeroize Keys and Restore Factory Defaults Switch (see Figure 1) has two modes of operation. The modes are set by the length of time the switch is asserted. The modes are:●LED Configuration1 For a list of error and warning codes refer to Appendix B at the end of this document.13

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0●Zeroize Keys and Restore Factory Defaults2.7.1 LED ConfigurationThis mode is used to control the display states of the Status LED. The LED Configuration function is accessed by pressing the switch and releasing it after a two second hold. The configured display state of the Status LED is dictated by the LED Mode setting that is configured from BC|Commander (please refer to the BC|Commander v11 User Guide for a more detailed description of the LED Mode setting). The user can toggle between the configured state and an alternate state of the Status LED by pressing the switch and activating the LED Configuration function.Table 2 lists the possible configured and corresponding alternate display states of the Status LED.Table 2: Configured and Alternate Display States of the Status LEDConfigured State Alternate StateOn OffAlerts Only OnOff (non-switchable) N/AOff (switchable) OnNote that state changes can occur only between options in the same rows of the table above. For example, it is possible to toggle the state back and forth between Alerts Only and On, but not between Alerts Only and Off. Transitioning from Alerts Only to Off would require changing the LED mode setting in BC|Commander.The default LED Mode for the ME4 is On.NoteThere are two different configurable Off states: Off (switchable), which toggles to On, and Off (non-switchable), which has no alternate state. If the LED Mode is set to Off (non-switchable), the Configuration Switch will NOT turn it on.2.7.2 Zeroize Keys and Restore Factory DefaultsThis mode is is used to erase the security protocol keys of a BreadCrumb ME4 and to restore its software configuration to the factory default state. To operate this switch follow these procedures:●Ensure that the BreadCrumb is powered on, has fully booted-up and its Status LED color is green or blue (see Table 1).●Press and hold the switch for approximately 10 seconds until the Status LED changes to blinking yellow (see Table 1). This indicates that the Zeroize Keys and Restore Factory Defaults operation has been initiated and is in progress.14

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0●Release the switch. The Status LED should change to display the blinking red error code 32. See Appendix B for a description of the blinking red color sequence. The BreadCrumb will then reboot using the factory default configuration. WarningDo NOT turn off or reboot a BreadCrumb that is being zeroized. An interruption to power during the zeroization process can result in the BreadCrumb being unable to boot properly.TipThe process of zeroizing keys and restoring factory defaults can also be performed remotely with the BC|Commander management software or with a properly prepared USB drive. For more information, refer to the BC|Commander v11 User Guide.15

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.03 Using BC|CommanderBC|Commander is Rajant’s BreadCrumb administration software package used for monitoring the status of BreadCrumbs and mesh links. BC|Commander is also used for configuring BreadCrumbs, upgrading BreadCrumb firmware, and graphically displaying the network topology.BC|Commander can be run on any computer that has access to the BreadCrumb network. Versions of the software package are available for Microsoft Windows® or Linux.BC|Commander includes an option called v10 Compatibility Mode. This allows a user to run a mixture of BreadCrumbs with firmware version 10 and firmware version 11 within the same mesh network. This is very useful when BreadCrumbs in a very large network are being upgraded from version 10 to version 11 firmware.Rajant periodically releases updated BC|Commander software. The updated software must be obtained from Rajant. Refer to Rajant’s most recent BC|Commander v11 User Guide for instructions on how to install the latest version of BC|Commander on your computer and how to use BC|Commander with Rajant’s BreadCrumbs. ImportantIt is recommended that the BC|Commander version used be equal to or greater than the firmware version running on any administered BreadCrumbs in order to administer all BreadCrumb firmware features covered in Rajant’s BC|Commander v11 User Guide.NoteSome portions of the BC|Commander v11 User Guide assume a working knowledge of TCP/IP networking, including DHCP, NAT and DNS. While the network lay person may be able to perform some mesh network management tasks, it is recommended that network configuration be performed by experienced network administrators.16

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.04 Deploying a BreadCrumb Mesh NetworkThere are many factors which need to be taken into account when deploying a BreadCrumb mesh network. Section 4.1 describes the addressing scheme of the mesh. Section 4.2 discusses channel assignments. Section 4.3 details some of the most commonly occurring environmental factors that will have a major impact on the performance of the mesh. Finally, section 4.4 details guidelines and methodology needed to follow when deploying the mesh.4.1 AddressingWhen in gateway mode or when using its own embedded DHCP servers, the BreadCrumb mesh requires that wireless devices use IPv4 addresses in the Class A network 10.0.0.0/8 (that is, any address that begins with ‘10.’). If you are not connected to another network, or if you are bridging to one rather than routing to it, your wireless client devices may have any address whatsoever.NoteAny computers running the BC|Commander management application must have an address in the same range as the BreadCrumbs they manage. Refer to the BC|Commander v11 User Guide document for the details of the BreadCrumb IP address configuration.4.1.1 BreadCrumb Device AddressesEach BreadCrumb radio has one IPv4 address in the Class A network 10.0.0.0/8. Rajant ensures during manufacturing that the default addresses are not duplicated between any two BreadCrumb devices. Addresses assigned to BreadCrumb devices can be viewed using BC|Commander. They can be configured manually, or set to DHCP.4.1.2 DHCPEach BreadCrumb device includes an embedded DHCP server. You may safely enable the DHCP servers of multiple BreadCrumb devices simultaneously, and it is in fact the most common case that all BreadCrumb devices in a mesh run DHCP servers. Address conflicts among DHCP clients are prevented by using the unique BreadCrumb device addresses assigned at the factory as a base.A BreadCrumb device determines its DHCP range as follows:●Start with the first three bytes of the first radio’s IPv4 address.●Add a low-byte range of 10 to 210.4.2 Channel AssignmentsBreadCrumb radios have default channels assigned, based on the frequency of the radio. See Table 3 for a list of available radios and their default channel assignments.17

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0Table 3: Default Channel AssignmentsRadio Card Frequency Default Channel900 MHz 52.4 GHz 114.9 GHz 205 GHz 153In some cases, it may be necessary to manually set the radios to specific channels to provide critical links within a mesh. This can be especially important when using single-radio BreadCrumb devices. Refer to the BC|Commander v11 User Guide for the details of BreadCrumb channel configuration.4.3 Physical Placement and other ConsiderationsCommonly occurring environmental factors have a significant impact on performance and behavior of the BreadCrumb Wireless Network. Line-of-sight (LOS) obstructions, distance, weather, and device placement should all be considered when deploying a wireless network.IEEE 802.11 wireless operation degrades gradually as distance increases between nodes or as interference becomes prominent. This manifests as a data rate reduction between nodes.The goal in planning and deploying a BreadCrumb mesh network is to maximize both coverage and the data transfer rate between devices. These can be maximized by taking into consideration all of the contributing factors described in this section.4.3.1 Line-of-SightUnobstructed line-of-sight (LOS) is critical for optimal performance of the mesh. Partial LOS obstruction results in noticeable network performance degradation. Total LOS obstruction can result in complete loss of network connectivity.Elevating the device and external antenna will assist in providing better LOS. This can allow the radio waves to propagate over some possible obstructions.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.Client connectivity will degrade and drop if LOS to a BreadCrumb device can not be maintained.4.3.2 DistanceMany factors determine acceptable distances between BreadCrumb devices when deploying a mesh:●If many devices are placed too closely together, it is possible that interference will degrade the performance of the system.18

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0●Devices placed too far away or in RF “shadows” may experience total loss of connection.●RF transmit power and receive sensitivity are important in determining the distances over which the device will be effective.●When placing a BreadCrumb device, check the connection status to the nearest available device using either the BreadCrumb device’s status LED (described in section 2.6 Status LED), or the BC|Commander management application. 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 6 Troubleshooting.●When the connection quality is found to be acceptable from BC|Commander, the distance of the BreadCrumb device from the network can be increased until an optimal balance between distance, connectivity and tactical placement is achieved.4.3.3 WeatherPrecipitation and fog also act as obstructions blocking the propagation of the wireless network’s radio waves.Light fog or precipitation may result in noticeable degradation of wireless network performance. Heavy precipitation or fog may result in severe performance degradation and possible loss of network connectivity.If the performance of a well functioning network is degraded by worsening weather conditions, it may be advisable to add BreadCrumb devices into the network to act as short haul repeaters to counteract the effects of the weather. An alternative is to move the devices closer together.4.3.4 InterferenceRF interference can degrade network performance and can come from many different sources, including:●Other BreadCrumb devices that are placed too closely together.●Other RF devices such as microwave devices, cordless phone base stations, radio transmitters, other wireless networks, jamming devices, etc.●Metal surfaces such as fences and building can cause radio waves to be reflected, causing multipath interference. Caution Plan the BreadCrumb Wireless Network to minimize the effects of RF interference.4.3.5 Placement of Mesh ComponentsThe placement of BreadCrumb devices has a major impact on maximum effective range, and therefore network performance. The components must be elevated above the surrounding terrain to allow for adequate wave propagation. A device placed directly on the ground has a significantly reduced effective 19

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0range. Elevating a device above the ground dramatically increased the maximum effective range. Rajant recommends elevating the components a minimum of 6 ft. above the surrounding surface.4.4 Deployment Guidelines and MethodologyThis section addresses the actual on-site deployment of the mesh. While by no means an exhaustive treatise, it is intended as a good source of guidelines and methodology for the successful deployment of a mesh in the field.4.4.1 Deployment GuidelinesFollow these guidelines when deploying the mesh: 1. Placement of BreadCrumbs(a) Elevate the BreadCrumbs whenever possible. i. Directly on the ground, the maximum distance between any two BreadCrumbs is approximately 300 ft. Also, the maximum distance between a wireless client and the nearest BreadCrumb is approximately 300 ft. ii. Rajant recommends elevating each BreadCrumb a minimum of 6 ft. above the surrounding terrain for maximum range. Elevating the BreadCrumbs, as little as 14 inches, has proven to increase the range out to approximately 600 ft. 2. Distance(a) If you cannot elevate the BreadCrumbs, they can only be approximately 300 ft. apart. Also, any wireless clients can be no farther than approximately 300 ft. from a BreadCrumb. 3. Line of sight(a) Obstructions to line-of-sight block/absorb/deflect the wireless network’s radio waves, resulting in poor network performance or total loss of network connectivity.(b) When placing the BreadCrumbs, scan the area for LOS obstructions. Envision the BreadCrumb’s radio waves as a light beam. Look for obstructions that would result in shadows in the light beam, they will most likely weaken or block the BreadCrumb’s radio waves. 4. Weather(a) Light precipitation will reduce the range and performance of the BreadCrumb and wireless clients.(b) Heavy precipitation or fog will most likely result in extremely reduced range and frequent or total loss of network connectivity.4.4.2 Deployment MethodologyThe steps detailed in this section should assist you in successfully deploying the mesh. 1. Scan the terrain on which the mesh will be deployed.(a) Determine the initial distances between BreadCrumb devices.20

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0Refer to Rajant Troubleshooting Range User Guide for more information.(b) Note any LOS obstructions, and plan BreadCrumb placement to work around them. 2. Identify the PC on which BC|Commander will be run.(a) This PC should have a wireless NIC, as you will need to carry it with you as you deploy the mesh. i. Alternatively, the BC|Commander PC can be stationary with one person monitoring BC|Commander while another deploys the BreadCrumbs. This method requires some form of communication (radio, cell phone, etc.) between the two persons. 3. Determine the location for the first BreadCrumb. 4. Power ON the device. 5. Wait approximately 90 seconds for the device to boot. 6. Power ON the BC|Commander PC. 7. Start BC|Commander. 8. The BC|Commander console should display the first BreadCrumb. 9. Determine the approximate location for the next BreadCrumb. 10.Proceed to the location for this BreadCrumb, observing the network in BC|Commander as you progress.(a) If the BreadCrumb loses network connectivity before you reach its destination, backtrack until network connectivity is restored. The point at which network connectivity for this BreadCrumb is restored is most likely the farthest point in this direction at which you will be able to place this BreadCrumb.(b) If you reach the destination without losing connectivity you can place it there. i. At this point, you may choose to proceed farther in an attempt to make optimal use of the available BreadCrumbs. ii. If so, proceed until network connectivity is lost and then backtrack until network connectivity is restored for this BreadCrumb. The point at which network connectivity is restored for this BreadCrumb is most likely the farthest point in this direction at which you will be able to place this BreadCrumb. 11.Repeat steps 9 and 10 for any remaining BreadCrumbs.21

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.05 Firmware UpgradeEach BreadCrumb relies on low-level software known as firmware for proper execution. For a BreadCrumb to communicate with other BreadCrumb devices or a BC|Commander client, the firmware version of the device must be compatible with the firmware versions of all other devices within the network, and with the version of BC|Commander running on the client computer.Note For procedures to install and upgrade the BC|Commander management application, refer to the latest BC|Commander v11 User Guide.The firmware is routinely updated by Rajant Corporation to add new product features, support new applications, and to fix reported problems. To upgrade the firmware on a BreadCrumb, you must obtain the appropriate firmware file for your BreadCrumb model from Rajant. Save the file on a computer on which the BC|Commander management application has been installed.5.1 Over The Air Firmware UpgradeOne method of upgrading the firmware is a process called “Over-the-Air (OTA) firmware upgrade”. This is a remote process, controlled and initiated by a system administrator using BC|Commander. Follow the instructions in the BC|Commander v11 User Guide (Administrative Tasks – Over-the-Air (OTA) firmware upgrade) to perform the firmware upgrade process.5.2 USB Firmware UpgradeAnother method is the USB firmware upgrade. This process takes place at the BreadCrumb's location and requires a properly prepared USB storage device. To perform the firmware upgrade process, follow these procedures: 1. Prepare a USB storage device with the appropriate firmware file using BC|Commander. Follow the instructions in the BC|Commander v11 User Guide (Administrative Tasks – USB Firmware Upgrade). 2. Connect the USB storage device to the BreadCrumb's USB port and turn on the BreadCrumb.Note With v11, the USB drive can be connected to a live BreadCrumb and the upgrade process will begin automatically. 3. The firmware upgrade process will take several minutes. Observe the BreadCrumb's Status LED to monitor progress.(a) When the USB firmware upgrade begins, the Status LED will start blinking yellow, which indicates progress. When the process nears completion, the blink rate will increase from once per second to several times per second.(b) If the firmware upgrade completes successfully, the Status LED will rapidly rotate between red, green, blue, cyan, magenta, yellow and white colors.22

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0(c) If an error condition is encountered, the Status LED will start repeating a particular sequence of long and short blinks in red, indicating the error code. Take note of the error code (see Appendix B for an explanation of error codes). Leaving the USB storage device connected, turn power to the BreadCrumb OFF and then ON again. Observe the Status LED to monitor progress. If, during this second firmware upgrade attempt, another error occurs, take note of the new error code and then apply for technical support. 4. When complete, turn power to the BreadCrumb OFF, disconnect the USB storage device, then turn power to the BreadCrumb back ON.5.3 USB-Based ZeriozeAs of firmware version 10.27, there is a USB-based Zeroize feature. This feature does not upgrade or in any other way affect the firmware version running on the BreadCrumb. This process takes place at the BreadCrumb's location and requires a properly prepared USB storage device. To perform the firmware upgrade process, follow these procedures: 1. Prepare a USB storage device using BC|Commander by selceting the “Zeroize (Do Not Upgrade)” option in the USB Flash Manager. Please see the BC|Commander v11 User Guide (Administrative Tasks – USB-Based Zeroize) for more detailed instructions on how to properly prepare the USB storage device. 2. Connect the USB storage device to the BreadCrumb's USB port and turn on the BreadCrumb.Note With v11, the USB drive can be connected to a live BreadCrumb and the zeroize process will begin automatically. 3. The USB-based Zeroize process will take less than a minute. Observe the BreadCrumb's Status LED to monitor progress. Wait for the LED to flash error code 32 “BreadCrumb has been zeroized.” 4. Turn power to the BreadCrumb OFF, disconnect the USB storage device, then turn power to the BreadCrumb back ON.23

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.06 Troubleshooting6.1 Sporadic Network ConnectivityTable 4: Sporadic Network Connectivity IssuesProblem ResolutionAs a BreadCrumb device’s battery approaches exhaustion, network connectivity will become sporadic for the BreadCrumb device and its associated wireless clients.Monitory battery usage and charge/replace batteries as necessary.Light precipitation or fog beginning after initial deployment of the mesh can result in sudden sporadic network connectivity for BreadCrumb devices and their associated wireless clients.Increase the density of the network by adding more BreadCrumb devices or by moving existing BreadCrumbs closer together.As a wireless client moves around through the coverage area, LOS to the BreadCrumb device can become obstructed resulting in sporadic network connectivity for this wireless client.Train users to maintain LOS to known BreadCrumb device locations. Place BreadCrumb devices strategically to ensure coverage of areas through which users are expected to move.A wireless client that moves beyond the range of the mesh will experience sporadic, and eventually complete, loss of network connectivity.Drop more BreadCrumb devices as necessary to increase range.A wireless client cannot join the network. ●Ensure that BreadCrumb devices are powered on.●Ensure that the wireless card in the client device (laptop) is enabled. This is usually indicated with a blinking light on the card.●Ensure that the wireless card is in "Infrastructure" or "Access Point" mode, and not in "Ad Hoc" mode. Scan for the default ESSID "breadcrumb54-v10" (or the ESSID that you set for the network) using the software accompanying your wireless card.●Ensure that the wireless client’s IP address settings are configured properly.●Ensure that the security settings on the 24

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0Problem Resolutionclient device and BreadCrumb devices match.●Ensure that the client device is not prevented from connecting by an ACL.●Ensure that the VLAN settings for the BreadCrumb allow clients of the ESSID being used to communicate to the Local Port of the BreadCrumb. See the VLAN section of the BC|Commander manual for more information.6.2 BreadCrumb Device Cannot Connect to MeshTable 5: BreadCrumb to BCWN Connectivity IssuesProblem ResolutionDischarged batteries can cause the BreadCrumb device to appear to power up, but not be able to establish connectivity to the mesh.When deploying the mesh, ensure that the batteries are fully charged.When using external antennas, faulty cable connections or crimped cables can result in difficulty establishing and maintaining network connectivity.Check antenna cables and their connections to the BreadCrumb device.6.3 BreadCrumb Power and Start-Up IssuesTable 6: BreadCrumb Power and Start-Up IssuesProblem ResolutionDischarged external batteries can cause a BreadCrumb to appear to power up(“PWR” LED is lit), but fail to start-up.Monitory battery usage and charge/replace batteries as necessary.25

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0Problem ResolutionElectrostatic Discharge can cause a BreadCrumb to appear to power up (Status LED indicates power is on with a white light, which can sometimes appear pale blue or pale green), but fail to start-up.Manually reboot the device by turning off or disconnecting power to the device and turning power back on.For BreadCrumbs powered by PoE, in order to avoid sparking and possible damage to the device, be sure to connect the powered Ethernet cable to the BreadCrumb before applying power to the power supply. Rapid power cycling can cause a BreadCrumb JR to appear to power up (“PWR” LED is lit) but fail to start-up.Turn off power to the device, wait at least 10 seconds and turn power back on. The BreadCrumb should start-up normally.Connecting a cable assembly which has an active power source (like a battery pack) to a BreadCrumb JR can cause the power to fluctuate at startup if it is connected with an unsteady hand. This can cause the BreadCrumb to appear to power up (“PWR” LED is lit), but fail to start-up.●Disconnect the cable assembly, wait 10 seconds, and try to make the connection again more smoothly.●Try connecting the cable assembly to the BreadCrumb before connecting or applying power to the power supply.26

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0Appendix A: Radio Channels and FrequenciesRajant's BreadCrumbs can contain up to four radios. 802.11g radios are used in the 900 MHz and 2.4 GHz bands, and 802.11a radios are used in the 4.8 GHz, 4.9 GHz and 5 GHz bands. The radios support the channels and frequencies listed in the following tables for use in the United States and Canada.NoteNot all channels are allowed for use everywhere around the world. Check with the corresponding wireless spectrum regulatory body to determine the subset of channels authorized for use in your country. CautionSince the radios operate at different frequencies, you must be careful to use the correct type of antenna with each radio. As an example, a 2.4 GHz antenna will not work with a 5 GHz radio and vice versa.Table 7: 900 MHz Radio Channels and FrequenciesChannel Number Center Frequency (MHz) Channel Bandwidth4 907 Half (10 Mhz)5 912 Full (20 Mhz)6 917 Full (20 Mhz)7 922 Half (10 Mhz)The default channel for a 900 MHz BreadCrumb radio is 5 (912 MHz). Half (10 MHz) and Quarter (5 MHz) bandwidth support is available on all 900MHz channels.Note Channels 4 and 7, as well as Half (10 MHz) and Quarter (5 MHz) bandwidth may not be supported on some BreadCrumbs with 900MHz radios.Table 8: 2.4 GHz Radio Channels and Frequencies27

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0Channel Number Center Frequency (MHz)1 24122 24173 24224 24275 24326 24377 24428 24479 245210 245711 2462The default channel for a 2.4 GHz BreadCrumb radio is 11 (2462 MHz).Table 9: 4.8 GHz Radio Channels and Frequencies28

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0ChannelNumberCenter Frequency (MHz)ChannelNumberCenter Frequency (MHz)162 4810 175 4875163 4815 176 4880164 4820 177 4885165 4825 178 4890166 4830 179 4895167 4835 180 4900168 4840 181 4905169 4845 182 4910170 4850 183 4915171 4855 184 4920172 4860 185 4925173 4865 186 4930174 4870The default channel for a 4.8 GHz BreadCrumb radio is 164 (4820 MHz). If a second 4.8 GHz radio is present, it's default channel is 184 (4920 MHz). If a third 4.8 GHz radio is present, it's default chanel is 174 (4870 MHz)29

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0Table 10: 4.9 GHz Radio Channels and FrequenciesChannel Number Center Frequency (MHz) Channel Bandwidth5 4942.5 Quarter (5 Mhz)10 4945.0 Half (10 Mhz)15 4947.5 Quarter (5 Mhz)20 4950.0 Full (20 Mhz)25 4952.5 Quarter (5 Mhz)30 4955.0 Full (20 Mhz)35 4957.5 Quarter (5 Mhz)40 4960.0 Full (20 Mhz)45 4962.5 Quarter (5 Mhz)50 4965.0 Full (20 Mhz)55 4967.5 Quarter (5 Mhz)60 4970.0 Full (20 Mhz)65 4972.5 Quarter (5 Mhz)70 4975.0 Full (20 Mhz)75 4977.5 Quarter (5 Mhz)80 4980.0 Full (20 Mhz)85 4982.5 Quarter (5 Mhz)90 4985.0 Half (10 Mhz)95 4987.5 Quarter (5 Mhz)The default channel for a 4.9 GHz BreadCrumb radio is 20 (4960.0 MHz).30

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0Table 11: 5 GHz Radio Channels and FrequenciesBand Channel Center Frequency (MHz) Turbo CapabilityU-NII Upper Band (5725 - 5825 MHz)/ ISM Band(5725 - 5875 MHz)149 5745 No152 5760 Static Turbo153 5765 No157 5785 No160 5800 Static Turbo161 5805 No165 5825 NoThe default channel for a 5 GHz BreadCrumb radio is 153 (5765 MHz). Some 5 GHz channels support Static Turbo mode. In this mode, the radio binds two standard 20 MHz channels to obtain a wider bandwidth 40 MHz channel. The end result is improved throughput and/or communication range for the radio. Users should refer to the applicable compliance regulations in the intended region of deployment for use of these frequencies. CautionMost 5 GHz antennas only support a subset of the 802.11a 5 GHz frequency channels the Rajant radio is capable of operating at. Before changing the channel of a 5 GHz radio, verify that the channel is supported by the connected antenna.31

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0Appendix B: Error and Warning CodesAll possible BreadCrumb error and warning codes are listed below:JR/LX/LX3/ME3/UX2400 Firmware Upgrade Codes (1*)11 Flash image file does not exist. 12 Current flash image version is greater than versions of files found on USB drive. 13 No flash image files found. 14 Unable to mount USB drive. 15 Unlocking of /dev/mtd0 failed. 16 fconfig for SetFailsafeBoot failed. 17 Unlocking of /dev/mtd0 failed. 18 fconfig for SetMainBoot failed. 19 Copying of zImage failed. 111 Copying of ramdisk failed. 112 FIS directory update of ramdisk failed. 113 Copying of etc failed. 114 FIS directory update of /etc failed. 115 Copying failed. 116 flashunbundle failed. 117 Version information in flash file name and breadcrumb-buildinfo.conf do not match. 1171 Platform information in flash file name and breadcrumb-buildinfo.conf do not match. 118 Untar failed. 119 FIS directory update of kernel failed. 121 Failed to unmount /etc. 122 In Failsafe mode, but no USB drive detected. 123 BreadCrumb will be in failsafe mode and unable to communicate with other BreadCrumbs after next reboot. 124 Failed to suspend bcconfigd. 125 Failed to set boot path to next image. 126 Failed to erase end of next file system image. 127 Failed to copy file system image. 128 Failed to checksum file system image. 32

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0129 Failed to create directory for next file system image. 131 Failed to mount next file system image. 132 Failed to create directory for settings. 133 Failed to copy current settings to next file system image. 134 Failed to unmount next file system image. 135 Failed to mount /etc. 141 Error retrieving flash file. Self-Test Codes (3*)31 Hardware configuration not set. Factory initialization required. 311 InstaMesh license update required. 32 BreadCrumb has been zeroized. 321 BreadCrumb is being zeroized. 33 Radio not detected. Turn the unit off, and then back on. If the problem persist, contact technical support. 333 Low Battery. 334 Gas gauge not initialized. Please fully charge unit turned off to initialize. 34 Cannot read /dev/nand6 information, or cannot resize or format /dev/nand6. 36 Hardware monitor missing. 37 Failed to add ethernet port to bridge. 38 Resetting radio due to error. FIPS Codes (4*)41 FIPS self-tests failed. 411 OpenSSL FIPS vector test programs not found. 412 OpenSSL FIPS vector test hash mismatch. 413 802.11i AES-CCMP test vectors failed. 414 Unable to use FIPS CCMP encryption. 415 Kernel integrity check failed. 416 Filesystem integrity check failed. 42 Mixed SecNet/Non-SecNet configuration. 43 Rekeying error. 44 Rekeying error. 45 Rekeying error. 33

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.046 Rekeying error. 47 Rekeying error. 48 Rekeying error. 49 Rekeying error. 431 Rekeying error. 432 Rekeying error. 433 Rekeying error. 434 Rekeying error. 435 Rekeying error. 436 Rekeying error. 441 Status override CPLD feature not available (wrong CPLD version). Fatal Codes (5*)51 instamesh fatal error. 52 hostapd fatal error. 53 cvm fatal error. 54 fatal error. 55 Low memory - automatic reboot scheduled. UX Battery Fault Codes (51*)See BC|Commander System Alerts for more detailed information. 511 Pack 1: does not exist|charge fault|charge gauge fault|discharge fault. 512 Pack 2: does not exist|charge fault|charge gauge fault|discharge fault. 513 Pack 3: does not exist|charge fault|charge gauge fault|discharge fault. 514 Pack 4: does not exist|charge fault|charge gauge fault|discharge fault. 515 Pack 5: does not exist|charge fault|charge gauge fault|discharge fault. 516 Pack 6: does not exist|charge fault|charge gauge fault|discharge fault. Battery Gas Gauge Codes (6*)61 Battery gas gauge i2c device could not be found. 62 Incorrect gas gauge revision 1 EEPROM settings. 63 Incorrect gas gauge revision 2 EEPROM settings. 64 Incorrect gas gauge revision 3 EEPROM settings. 65 Unknown gas gauge revision. 34

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.066 Incorrect ME3 gas gauge revision 0 EEPROM settings. 67 Internal battery charger disabled. Other Codes (7*, 8*)71 Host flapping detected. 72 Critical I2C failure. 81 <Username>@<IP address> issued reboot on <date> <time>35

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0Appendix C: Using Pole Mount Bracket●Use the two (2) supplied U-bolts and four (4) nuts to secure the Pole Mount Bracket to a pole up to 3” in diameter (See Figure 1 below).●Use the eight (8) supplied screws to attach the BreadCrumb ME4 to the Pole Mount Bracket (See Figure 2 below).Figure 3: ME4 Pole Mounted Bracket Figure 4: ME4 Mounted to Pole36

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0Appendix D: Rajant End User License AgreementIMPORTANT: PLEASE READ THIS END USER LICENSE AGREEMENT CAREFULLY. IT IS ENCLOSED IN THE SOFTWARE PACKAGE AND /OR PRESENTED ELECTRONICALLY WHEN ACCESSING THE SOFTWARE. BY CLICKING “I AGREE”, YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS LICENSE. IT IS VERY IMPORTANT THAT YOU CHECK THAT YOU ARE PURCHASING RAJANT SOFTWARE OR EQUIPMENT FROM AN APPROVED SOURCE AND THAT YOU, OR THE ENTITY YOU REPRESENT (COLLECTIVELY, THE "CUSTOMER") HAVE BEEN REGISTERED AS THE END USER FOR THE PURPOSES OF THIS RAJANT END USER LICENSE AGREEMENT. IF YOU ARE NOT REGISTERED AS THE END USER YOU HAVE NO LICENSE TO USE THE SOFTWARE AND THE LIMITED WARRANTY IN THIS END USER LICENSE AGREEMENT DOES NOT APPLY. ASSUMING YOU HAVE PURCHASED FROM AN APPROVED SOURCE, DOWNLOADING, INSTALLING OR USING RAJANT OR RAJANT-SUPPLIED SOFTWARE CONSTITUTES ACCEPTANCE OF THIS AGREEMENT. RAJANT CORPORATION OR ITS AFFILIATE LICENSING THE SOFTWARE ("RAJANT") IS WILLING TO LICENSE THIS SOFTWARE TO YOU ONLY UPON THE CONDITION THAT YOU PURCHASED THE SOFTWARE FROM AN APPROVED SOURCE AND THAT YOU ACCEPT ALL OF THE TERMS CONTAINED IN THIS END USER LICENSE AGREEMENT PLUS ANY ADDITIONAL LIMITATIONS ON THE LICENSE SET FORTH IN A SUPPLEMENTAL LICENSE AGREEMENT ACCOMPANYING THE PRODUCT OR AVAILABLE AT THE TIME OF YOUR ORDER (COLLECTIVELY THE "AGREEMENT"). TO THE EXTENT OF ANY CONFLICT BETWEEN THE TERMS OF THIS END USER LICENSE AGREEMENT AND ANY SUPPLEMENTAL LICENSE AGREEMENT, THE SUPPLEMENTAL LICENSE AGREEMENT SHALL APPLY. BY DOWNLOADING, INSTALLING, OR USING THE SOFTWARE, YOU ARE REPRESENTING THAT YOU PURCHASED THE SOFTWARE FROM AN APPROVED SOURCE AND BINDING YOURSELF TO THE AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THE AGREEMENT, THEN RAJANT IS UNWILLING TO LICENSE THE SOFTWARE TO YOU AND (A) YOU MAY NOT DOWNLOAD, INSTALL OR USE THE SOFTWARE, AND (B) YOU MAY RETURN THE SOFTWARE (INCLUDING ANY UNOPENED PACKAGE AND ANY WRITTEN MATERIALS) FOR A FULL REFUND, OR, IF THE SOFTWARE AND WRITTEN MATERIALS ARE SUPPLIED AS PART OF ANOTHER PRODUCT, YOU MAY RETURN THE ENTIRE PRODUCT FOR A FULL REFUND. YOUR RIGHT TO RETURN AND REFUND EXPIRES 30 DAYS AFTER PURCHASE FROM AN APPROVED SOURCE, AND APPLIES ONLY IF YOU ARE THE ORIGINAL AND REGISTERED END USER PURCHASER. FOR THE PURPOSES OF THIS END USER LICENSE AGREEMENT, AN "APPROVED SOURCE" MEANS (A) RAJANT; OR (B) A DISTRIBUTOR OR SYSTEMS INTEGRATOR AUTHORIZED BY RAJANT TO DISTRIBUTE / SELL RAJANT EQUIPMENT, SOFTWARE AND SERVICES WITHIN YOUR TERRITORY TO END USERS; OR (C) A RESELLER AUTHORIZED BY ANY SUCH DISTRIBUTOR OR SYSTEMS INTEGRATOR IN ACCORDANCE WITH THE TERMS OF THE DISTRIBUTOR'S AGREEMENT WITH RAJANT TO DISTRIBUTE / SELL THE RAJANT EQUIPMENT, SOFTWARE AND SERVICES WITHIN YOUR TERRITORY TO END USERS. THE FOLLOWING TERMS OF THE AGREEMENT GOVERN CUSTOMER'S USE OF THE SOFTWARE (DEFINED BELOW), EXCEPT TO THE EXTENT: (A) THERE IS A SEPARATE SIGNED CONTRACT BETWEEN CUSTOMER AND RAJANT GOVERNING CUSTOMER'S USE OF THE 37

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0SOFTWARE, OR (B) THE SOFTWARE INCLUDES A SEPARATE "CLICK-ACCEPT" LICENSE AGREEMENT OR THIRD PARTY LICENSE AGREEMENT AS PART OF THE INSTALLATION OR DOWNLOAD PROCESS GOVERNING CUSTOMER'S USE OF THE SOFTWARE. TO THE EXTENT OF A CONFLICT BETWEEN THE PROVISIONS OF THE FOREGOING DOCUMENTS, THE ORDER OF PRECEDENCE SHALL BE (1)THE SIGNED CONTRACT, (2) THE CLICK-ACCEPT AGREEMENT OR THIRD PARTY LICENSE AGREEMENT, AND (3) THE AGREEMENT. FOR PURPOSES OF THE AGREEMENT, "SOFTWARE" SHALL MEAN COMPUTER PROGRAMS, INCLUDING FIRMWARE AND COMPUTER PROGRAMS EMBEDDED IN RAJANT EQUIPMENT, AS PROVIDED TO CUSTOMER BY AN APPROVED SOURCE, AND ANY UPGRADES, UPDATES, BUG FIXES OR MODIFIED VERSIONS THERETO (COLLECTIVELY, "UPGRADES"), ANY OF THE SAME WHICH HAS BEEN RELICENSED UNDER THE RAJANT SOFTWARE TRANSFER AND RE-LICENSING POLICY (AS MAY BE AMENDED BY RAJANT FROM TIME TO TIME) OR BACKUP COPIES OF ANY OF THE FOREGOING. License. Conditioned upon compliance with the terms and conditions of the Agreement, RAJANT grants to Customer a nonexclusive and nontransferable license to use for Customer's internal business purposes the Software and the Documentation for which Customer has paid the required license fees to an Approved Source. "Documentation" means written information (whether contained in user or technical manuals, training materials, specifications or otherwise) pertaining to the Software and made available by an Approved Source with the Software in any manner (including on CD-Rom, or on-line). In order to use the Software, Customer may be required to input a registration number or product authorization key and register Customer's copy of the Software online at RAJANT’S website to obtain the necessary license key or license file. Customer's license to use the Software shall be limited to, and Customer shall not use the Software in excess of, a single hardware chassis or card or such other limitations as are set forth in the applicable Supplemental License Agreement or in the applicable purchase order which has been accepted by an Approved Source and for which Customer has paid to an Approved Source the required license fee (the "Purchase Order"). Unless otherwise expressly provided in the Documentation or any applicable Supplemental License Agreement, Customer shall use the Software solely as embedded in, for execution on, or (where the applicable Documentation permits installation on non- RAJANT equipment) for communication with RAJANT equipment owned or leased by Customer and used for Customer's internal business purposes. No other licenses are granted by implication, estoppel or otherwise. For evaluation or beta copies for which Rajant does not charge a license fee, the above requirement to pay license fees does not apply. General Limitations. This is a license, not a transfer of title, to the Software and Documentation, and Rajant retains ownership of all copies of the Software and Documentation. Customer acknowledges that the Software and Documentation contain trade secrets of Rajant or its suppliers or licensors, including but not limited to the specific internal design and structure of individual programs and associated interface information. Except as otherwise expressly provided under the Agreement, Customer shall only use the Software in connection with the use of Rajant equipment purchased by the Customer from an Approved Source and Customer shall have no right, and Customer specifically agrees not to: (i) transfer, assign or sublicense its license rights to any other person or entity (other than in compliance with any Rajant relicensing/transfer policy then in force), or use the Software on Rajant equipment not purchased by the Customer from an Approved Source or on secondhand 38

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0Rajant equipment, and Customer acknowledges that any attempted transfer, assignment, sublicense or use shall be void; (ii) make error corrections to or otherwise modify or adapt the Software or create derivative works based upon the Software, or permit third parties to do the same; (iii) reverse engineer or decompile, decrypt, disassemble or otherwise reduce the Software to human-readable form, except to the extent otherwise expressly permitted under applicable law notwithstanding this restriction or except to the extent that Rajant is legally required to permit such specific activity pursuant to any applicable open source license; (iv) publish any results of benchmark tests run on the Software; (v) use or permit the Software to be used to perform services for third parties, whether on a service bureau or time sharing basis or otherwise, without the express written authorization of Rajant; or (vi) disclose, provide, or otherwise make available trade secrets contained within the Software and Documentation in any form to any third party without the prior written consent of Rajant. Customer shall implement reasonable security measures to protect such trade secrets. To the extent required by applicable law, and at Customer's written request, Rajant shall provide Customer with the interface information needed to achieve interoperability between the Software and another independently created program, on payment of Rajant’s applicable fee, if any. Customer shall observe strict obligations of confidentiality with respect to such information and shall use such information in compliance with any applicable terms and conditions upon which Rajant makes such information available. Software, Upgrades and Additional Copies. NOTWITHSTANDING ANY OTHER PROVISION OF THE AGREEMENT: (1) CUSTOMER HAS NO LICENSE OR RIGHT TO MAKE OR USE ANY ADDITIONAL COPIES OR UPGRADES UNLESS CUSTOMER, AT THE TIME OF MAKING OR ACQUIRING SUCH COPY OR UPGRADE, ALREADY HOLDS A VALID LICENSE TO THE ORIGINAL SOFTWARE AND HAS PAID THE APPLICABLE FEE TO AN APPROVED SOURCE FOR THE UPGRADE OR ADDITIONAL COPIES; (2) USE OF UPGRADES IS LIMITED TO RAJANT EQUIPMENT SUPPLIED BY AN APPROVED SOURCE FOR WHICH CUSTOMER IS THE ORIGINAL END USER PURCHASER OR LESSEE OR OTHERWISE HOLDS A VALID LICENSE TO USE THE SOFTWARE WHICH IS BEING UPGRADED; AND (3) THE MAKING AND USE OF ADDITIONAL COPIES IS LIMITED TO NECESSARY BACKUP PURPOSES ONLY. Proprietary Notices. Customer agrees to maintain and reproduce all copyright, proprietary, and other notices on all copies, in any form, of the Software and Documentation in the same form and manner that such copyright and other proprietary notices are included on the Software. Except as expressly authorized in the Agreement, Customer shall not make any copies or duplicates of any Software without the prior written permission of Rajant. Term and Termination. The Agreement and the license granted herein shall remain effective until terminated. Customer may terminate the Agreement and the license at any time by destroying all copies of Software and any Documentation. Customer's rights under the Agreement will terminate immediately without notice from RAJANT if Customer fails to comply with any provision of the Agreement. Upon termination, Customer shall destroy or return to RAJANT all copies of Software and Documentation in its possession or control. All confidentiality obligations of Customer, all restrictions and limitations imposed on the Customer under the section titled "General Limitations" and all limitations of liability 39

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0and disclaimers and restrictions of warranty shall survive termination of this Agreement. In addition, the provisions of the sections titled "U.S. Government End User Purchasers" and "General Terms Applicable to the Limited Warranty Statement and End User License Agreement" shall survive termination of the Agreement. Customer Records. Customer grants to RAJANT and its independent accountants the right to examine Customer's books, records, accounts, and network configuration(s) during Customer's normal business hours to verify compliance with this Agreement. In the event such audit discloses non-compliance with this Agreement, Customer shall promptly pay to RAJANT the appropriate license fees, plus the reasonable cost of conducting the audit. Export, Re-Export, Transfer and Use Controls. The Software, Documentation and technology or direct products thereof (hereafter referred to as Software and Technology), supplied by RAJANT under the Agreement are subject to export controls under the laws and regulations of the United States ("U.S.") and any other applicable countries' laws and regulations. Customer shall comply with such laws and regulations governing export, re-export, import, transfer and use of RAJANT Software and Technology and will obtain all required U.S. and local authorizations, permits, or licenses. RAJANT and Customer each agree to provide the other information, support documents, and assistance as may reasonably be required by the other in connection with securing authorizations or licenses. Information regarding compliance with export, re-export, transfer and use. U.S. Government End User Purchasers. The Software and Documentation qualify as "commercial items," as that term is defined at Federal Acquisition Regulation ("FAR") (48 C.F.R.) 2.101, consisting of "commercial computer software" and "commercial computer software documentation" as such terms are used in FAR 12.212. Consistent with FAR 12.212 and DoD FAR Supp. 227.7202-1 through 227.7202-4, and notwithstanding any other FAR or other contractual clause to the contrary in any agreement into which the Agreement may be incorporated, Customer may provide to Government end user or, if the Agreement is direct, Government end user will acquire, the Software and Documentation with only those rights set forth in the Agreement. Use of either the Software or Documentation or both constitutes agreement by the Government that the Software and Documentation are "commercial computer software" and "commercial computer software documentation," and constitutes acceptance of the rights and restrictions herein. Identified Components; Additional Terms. The Software may contain or be delivered with one or more components, which may include third-party components, identified by RAJANT in the Documentation, readme.txt file, third-party click-accept or elsewhere (e.g. on www.rajant.com) (the "Identified Component(s)") as being subject to different license agreement terms, disclaimers of warranties, limited warranties or other terms and conditions (collectively, "Additional Terms") than those set forth herein. You agree to the applicable Additional Terms for any such Identified Component(s). Limited Warranty Subject to the limitations and conditions set forth herein, RAJANT warrants that commencing from the date of shipment to Customer (but in case of resale by an Approved Source other than RAJANT, commencing not more than ninety (90) days after original shipment by RAJANT), and continuing for a period of the longer of (a) ninety (90) days or (b) the warranty period (if any) expressly set forth as applicable specifically to software in the warranty card accompanying the product of which the Software is a part (the "Product") (if any): (a) the media on which the Software is furnished will be free of defects in materials and workmanship under normal use; and (b) the Software substantially conforms to the Documentation. The date of shipment of a Product by RAJANT is set forth on the packaging material in 40

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0which the Product is shipped. Except for the foregoing, the Software is provided "AS IS". This limited warranty extends only to the Software purchased from an Approved Source by a Customer who is the first registered end user. Customer's sole and exclusive remedy and the entire liability of RAJANT and its suppliers under this limited warranty will be (i) replacement of defective media and/or (ii) at RAJANT’s option, repair, replacement, or refund of the purchase price of the Software, in both cases subject to the condition that any error or defect constituting a breach of this limited warranty is reported to the Approved Source supplying the Software to Customer, within the warranty period. RAJANT or the Approved Source supplying the Software to Customer may, at its option, require return of the Software and/or Documentation as a condition to the remedy. In no event does RAJANT warrant that the Software is error free or that Customer will be able to operate the Software without problems or interruptions. In addition, due to the continual development of new techniques for intruding upon and attacking networks, RAJANT does not warrant that the Software or any equipment, system or network on which the Software is used will be free of vulnerability to intrusion or attack. Restrictions. This warranty does not apply if the Software, Product or any other equipment upon which the Software is authorized to be used (a) has been altered, except by RAJANT or its authorized representative, (b) has not been installed, operated, repaired, or maintained in accordance with instructions supplied by RAJANT, (c) has been subjected to abnormal physical or electrical stress, abnormal environmental conditions, misuse, negligence, or accident; or (d) is licensed for beta, evaluation, testing or demonstration purposes. The Software warranty also does not apply to (e) any temporary Software modules; (f) any Software not posted on RAJANT’s Software Center; (g) any Software that RAJANT expressly provides on an "AS IS" basis on RAJANT’s Software Center; (h) any Software for which an Approved Source does not receive a license fee; and (i) Software supplied by any third party which is not an Approved Source. Hardware Limited Warranty Unless otherwise listed on this Warranty Schedule, Rajant warrants to the purchaser that the Products will perform in all material respects in accordance with their written specifications for a period of ninety (90) days from the date the Products are shipped by Rajant. Reseller and purchaser’s sole and exclusive right and remedy, and Rajant’s sole and exclusive obligation and liability, with respect to any breach of the foregoing warranty shall be that, upon receipt by Rajant from Reseller or purchasers of written notice of the breach in reasonable detail so as to permit Rajant to duplicate the failure to so perform, which notice is received by Rajant within thirty (30) days after Reseller or purchaser discovers the failure, Rajant shall – after duplicating the failure – exercise its commercially reasonable efforts to deliver to Reseller or purchaser a replacement or repaired Product at Rajant’s discretion. Rajant replacement parts used in such replacement may be new or equivalent to new. Rajant's obligations hereunder are conditioned upon the return of the affected Product in accordance with Rajant's then-current Return Material Authorization (RMA) procedures. This warranty shall not apply to any Product that has been subjected to unusual physical, environmental or electrical stress. The warranty shall not apply to any problems or non-performance directly resulting from Reseller or purchaser’s hardware, software, network(s) and/or host system(s) or the combination, operation or use of the Product with such hardware, software, network(s) and/or host system(s), or which results from any alteration or modification to the Product or its components by anyone other than Rajant. The warranty also does not cover any (a) Product for which the serial number has been removed or made illegible; (b) freight costs to the repair center; (c) scratches or other cosmetic damage to Product surfaces that do not affect the operation of the Product; and (d) normal and customary wear and tear. 41

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0 The date of shipment of a Product by Rajant is set forth on the packaging material in which the Product is shipped. This limited warranty extends only to the original user of the Product. Replacement, Repair or Refund Procedure for Products Covered by WarrantyRajant will use commercially reasonable efforts to ship a repaired or replacement part within fifteen (15) working days after receipt of the RMA request. Actual delivery times may vary depending on Reseller’s or purchaser’s location. To Receive a Return Materials Authorization (RMA) Number Please contact the party from whom you purchased the Product. If you purchased the Product directly from Rajant, contact your Rajant Sales and Service Representative or email support@rajant.com. Additional Limited Warranties Notwithstanding the generality of the foregoing, Rajant provides the following additional warranties to the Reseller or purchaser, subject to the terms and conditions in the Reseller Agreement, End User Agreement. The BreadCrumb Wireless LAN units (“BreadCrumb”) provided under this Agreement are provided with a 1-year warranty from the date the BreadCrumb is shipped by Rajant against defects in workmanship or material under ordinary use. Such warranty applies only to the BreadCrumb device and does not extend to any other Products, products or services, including but not limited to power supplies, cables, antennas, and mounting brackets, even if packaged or sold with the BreadCrumb. DISCLAIMER OF WARRANTY EXCEPT AS SPECIFIED IN THIS WARRANTY SECTION, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS, AND WARRANTIES INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTY OR CONDITION OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, SATISFACTORY QUALITY, NON-INTERFERENCE, ACCURACY OF INFORMATIONAL CONTENT, OR ARISING FROM A COURSE OF DEALING, LAW, USAGE, OR TRADE PRACTICE, ARE HEREBY EXCLUDED TO THE EXTENT ALLOWED BY APPLICABLE LAW AND ARE EXPRESSLY DISCLAIMED BY RAJANT, ITS SUPPLIERS AND LICENSORS. TO THE EXTENT THAT ANY OF THE SAME CANNOT BE EXCLUDED, SUCH IMPLIED CONDITION, REPRESENTATION AND/OR WARRANTY IS LIMITED IN DURATION TO THE EXPRESS WARRANTY PERIOD REFERRED TO IN THE "LIMITED WARRANTY" SECTION ABOVE. BECAUSE SOME STATES OR JURISDICTIONS DO NOT ALLOW LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY LASTS, THE ABOVE LIMITATION MAY NOT APPLY IN SUCH STATES. THIS WARRANTY GIVES CUSTOMER SPECIFIC LEGAL RIGHTS, AND CUSTOMER MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM JURISDICTION TO JURISDICTION. This disclaimer and exclusion shall apply even if the express warranty set forth above fails of its essential purpose. Disclaimer of Liabilities—Limitation of Liability. IF YOU ACQUIRED THE SOFTWARE IN THE UNITED STATES, LATIN AMERICA, CANADA, JAPAN OR THE CARIBBEAN, NOTWITHSTANDING ANYTHING ELSE IN THE AGREEMENT TO THE CONTRARY, ALL LIABILITY OF RAJANT, ITS AFFILIATES, OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, SUPPLIERS AND LICENSORS COLLECTIVELY, TO CUSTOMER, WHETHER IN CONTRACT, TORT (INCLUDING NEGLIGENCE), BREACH OF WARRANTY OR OTHERWISE, SHALL NOT EXCEED THE PRICE PAID BY CUSTOMER TO ANY APPROVED SOURCE FOR THE 42

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0SOFTWARE THAT GAVE RISE TO THE CLAIM OR IF THE SOFTWARE IS PART OF ANOTHER PRODUCT, THE PRICE PAID FOR SUCH OTHER PRODUCT. THIS LIMITATION OF LIABILITY FOR SOFTWARE IS CUMULATIVE AND NOT PER INCIDENT (I.E. THE EXISTENCE OF TWO OR MORE CLAIMS WILL NOT ENLARGE THIS LIMIT). IF YOU ACQUIRED THE SOFTWARE IN EUROPE, THE MIDDLE EAST, AFRICA, ASIA OR OCEANIA, NOTWITHSTANDING ANYTHING ELSE IN THE AGREEMENT TO THE CONTRARY, ALL LIABILITY OF RAJANT, ITS AFFILIATES, OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, SUPPLIERS AND LICENSORS COLLECTIVELY, TO CUSTOMER, WHETHER IN CONTRACT, TORT (INCLUDING NEGLIGENCE), BREACH OF WARRANTY OR OTHERWISE, SHALL NOT EXCEED THE PRICE PAID BY CUSTOMER TO RAJANT FOR THE SOFTWARE THAT GAVE RISE TO THE CLAIM OR IF THE SOFTWARE IS PART OF ANOTHER PRODUCT, THE PRICE PAID FOR SUCH OTHER PRODUCT. THIS LIMITATION OF LIABILITY FOR SOFTWARE IS CUMULATIVE AND NOT PER INCIDENT (I.E. THE EXISTENCE OF TWO OR MORE CLAIMS WILL NOT ENLARGE THIS LIMIT). NOTHING IN THE AGREEMENT SHALL LIMIT (I) THE LIABILITY OF RAJANT, ITS AFFILIATES, OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, SUPPLIERS AND LICENSORS TO CUSTOMER FOR PERSONAL INJURY OR DEATH CAUSED BY THEIR NEGLIGENCE, (II) RAJANT’s LIABILITY FOR FRAUDULENT MISREPRESENTATION, OR (III) ANY LIABILITY OF RAJANT WHICH CANNOT BE EXCLUDED UNDER APPLICABLE LAW. Disclaimer of Liabilities—Waiver of Consequential Damages and Other Losses. IF YOU ACQUIRED THE SOFTWARE IN THE UNITED STATES, LATIN AMERICA, THE CARIBBEAN OR CANADA, REGARDLESS OF WHETHER ANY REMEDY SET FORTH HEREIN FAILS OF ITS ESSENTIAL PURPOSE OR OTHERWISE, IN NO EVENT WILL RAJANT OR ITS SUPPLIERS BE LIABLE FOR ANY LOST REVENUE, PROFIT, OR LOST OR DAMAGED DATA, BUSINESS INTERRUPTION, LOSS OF CAPITAL, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL, OR PUNITIVE DAMAGES HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY OR WHETHER ARISING OUT OF THE USE OF OR INABILITY TO USE SOFTWARE OR OTHERWISE AND EVEN IF RAJANT OR ITS SUPPLIERS OR LICENSORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME STATES OR JURISDICTIONS DO NOT ALLOW LIMITATION OR EXCLUSION OF CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU. IF YOU ACQUIRED THE SOFTWARE IN JAPAN, EXCEPT FOR LIABILITY ARISING OUT OF OR IN CONNECTION WITH DEATH OR PERSONAL INJURY, FRAUDULENT MISREPRESENTATION, AND REGARDLESS OF WHETHER ANY REMEDY SET FORTH HEREIN FAILS OF ITS ESSENTIAL PURPOSE OR OTHERWISE, IN NO EVENT WILL RAJANT, ITS AFFILIATES, OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, SUPPLIERS AND LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT, OR LOST OR DAMAGED DATA, BUSINESS INTERRUPTION, LOSS OF CAPITAL, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL, OR PUNITIVE DAMAGES HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY OR WHETHER ARISING OUT OF THE USE OF OR INABILITY TO USE SOFTWARE OR OTHERWISE AND EVEN IF RAJANT OR ANY APPROVED SOURCE OR THEIR SUPPLIERS OR LICENSORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IF YOU ACQUIRED THE SOFTWARE IN EUROPE, THE MIDDLE EAST, AFRICA, ASIA OR OCEANIA, IN NO EVENT WILL RAJANT, ITS AFFILIATES, OFFICERS, DIRECTORS, 43

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0Appendix E: GNU General Public LicenseVersion 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. PREAMBLEThe licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The “Program”, 45

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0below, refers to any such program or work, and a “work based on the Program” means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term “modification”.) Each licensee is addressed as “you”. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 46

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.03. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. 47

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the FreeSoftware Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 48

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONSHOW TO APPLY THESE TERMS TO YOUR NEW PROGRAMS If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. one line to give the program's name and an idea of what it does. Copyright (C) yyyy name of author This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. 49

Rajant Corporation BreadCrumb® ME4 v11 User Guide03-100126-011 Version 11.0.0You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. signature of Ty Coon, 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License.50