BreadCrumb® LX5 Version 11 User Guide Página 1 de 62

BreadCrumb® LX5 Version 11 User Guide

Model: BreadCrumb LX5

User Guide Version: 11.8.0 Rev E
Software Version: 11.8.0
Document Part Number: 03­100140­011

Corporate Headquarters:

Rajant Corporation
400 East King Street
Malvern, PA 19355
Tel: (484) 595­0233
Fax: (484) 595­0244
http://www.rajant.com

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 2 de 62

Table of Contents

Document Revision History

Copyright Statement
FCC, CE, IC, Anatel, ACMA and RCM Statements
Antennas
Safety
Modifications
Professional Installation Attestation
Maximum Certified Power
GNU General Public License Statement
Preface
1. Introduction to BreadCrumbs
1.1 What is a BreadCrumb?
1.2 The Mesh Network
2. Description of a BreadCrumb LX5
2.1 Radios
2.2 Enclosure
2.3 Antenna Connectors
2.4 22­Pin Amphenol Connector
2.5 LX5 Cable Assembly
2.6 Status LED
2.7 LED Configuration / Zeroize Keys and Restore Factory Defaults Switch
3. Using BC|Commander
4. Deploying a BreadCrumb Mesh Network
4.1 Addressing
4.2 Channel Assignments
4.3 Physical Placement and other Considerations
4.4 Deployment Guidelines and Methodology
5. Firmware Upgrade and Zeroize
5.1 Over The Air Firmware Upgrade
5.2 USB Firmware Upgrade
5.3 Over the Air Zeroize
5.4 USB­Based Zeroize
6. Troubleshooting
6.1 Sporadic Network Connectivity
6.2 BreadCrumb Device Cannot Connect to Mesh
6.3 BreadCrumb Power and Start­Up Issues
7. Appendices
Appendix A: Radio Channels and Frequencies
A.1 Radio: 2.4 GHz 802.11n

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 3 de 62

A.2 Radio: 5 GHz 802.11n

A.3 DFS and TPC
A.4 Radio: 4.8 GHz 802.11a
A.5 Radio: 4.9 GHz 802.11a
A.6 Radio: 900 MHz 802.11g
Appendix B: Error and Warning Codes
Appendix C: Mounting
C.1 Mounting Holes
C.2 Using a Flat Plate Mounting Kit
Appendix D: Rajant End User License Agreement
Appendix E: GNU General Public License

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 4 de 62

Document Revision History

Revision Date Changes

11.7 Rev A 05/15/2015 Initial HTML document

11.8 Rev A 10/01/2015 Update button zeroize text

11.8 Rev B 10/14/2015 DC PoE diagram, safety text

11.8 Rev C 10/30/2015 Update certifications section

11.8 Rev D 11/11/2015 Update Anatel (pending) table

11.8 Rev E 11/30/2015 Remove pending from Anatel

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 5 de 62

Copyright Statement

Rajant, the Rajant logo, BreadCrumb, InstaMesh, BC|Commander, and Bring Your Network with You!
are registered trademarks of Rajant Corp. in the United States and certain other countries.

Rajant’s patented InstaMesh® networking software enables the network to quickly adapt to rapidly‐
deployed and moving network elements. U.S. Patents 9,001,645 and US 9,001,645 B2

BreadCrumb® LX5 Version 11 User Guide

Copyright © 2009–2015 Rajant Corp. All rights reserved.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 6 de 62

FCC, CE, IC, Anatel, ACMA and RCM Statements

This 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.

This digital apparatus complies with the Australian/New Zealand AS/NZS 4268: Radiocommunications
(Short Range Devices) Standard 2004 +A1:2013 +A2:2013.

CE Declarations of Conformity may be found on the product CD.

NOTE
Please refer to the product spec sheet at http://www.rajant.com for a list of certified model
numbers.

Antennas

Antenna Installation WARNING

The installer should configure the conducted output power level according to country regulations
and the applicable EIRP limit. Professional installation of equipment is required to ensure compliance
with health and safety issues.

Required Antenna Separation

BreadCrumb LX5 antennas may not be co­located. To satisfy this requirement, each antenna must be
installed with a minimum separation distance of 20 cm from any other LX5 antenna, and the antenna
of any other radio frequency transmitter. It is permissible to direct attach no more than two antennas
to the LX5, provided that these antennas are positioned on opposite sides of the LX5 (one on the front
side of the enclosure, one on the back side of the enclosure). For installations that will experience
vibration or shock, all antennas should be externally mounted and attached to the LX5 using cables.
Low loss RF cable such as LMR­400 is recommended for cable attached antennas. If a radio port is not
required for a given application, the port should be disabled in software using BC|Commander, and a
50 Ohm terminator should be installed.

IMPORTANT: Exposure to Radio Frequency Radiation

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.

Safety

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 7 de 62

Warning
The BreadCrumb LX5 is not user serviceable. Repair must be performed at a Rajant designated
service center by trained personnel.

Warning
The BreadCrumb LX5 single board computer assembly contains a Lithium Ion battery. Replacement of
this battery should never be attempted by the user. The battery must be replaced by authorized
repair personnel trained by Rajant Corporation. CAUTION: Risk of explosion if battery is replaced by
an incorrect type. Dispose of used batteries according to the battery manufacturer’s instructions.

Warning
The enclosure of the BreadCrumb LX5 is conductive. To protect the user against the risk of electric
shock during high voltage transient events which may occur when this equipment is installed
outdoors, protective earth grounding of the BreadCrumb LX5 enclosure is required. Protective earth
grounding operations must be performed by trained personnel, and according to local electrical
codes and industry best practices, as well as Rajant’s own recommendations.

Warning
To protect the user against the risk of electric shock during high voltage transient events which may
occur when this equipment is installed outdoors, protective earth grounding of the POE power
supply is required. Case ground connections are provided on all Rajant supplied POE power supplies.
The case ground connections must be used and must be connected to a protective earth ground.
Protective earth grounding operations must be performed by trained personnel, and according to
local electrical codes and industry best practices, as well as Rajant’s own recommendations.

Modifications

CAUTION
Changes or modifications not expressly approved by Rajant Corp. could void the user’s authority to
operate the equipment.

Rajant Products are compliant and warranted against manufacturing defects only so long as authorized
Rajant­authorized accessories are used in deployment of Rajant Breadcrumbs. It is the responsibility of
the operator and the installer to insure the system as installed operates within regional requirements.

Professional Installation Attestation

Rajant Corporation addresses the following items to ensure that the above referenced equipment is
professionally installed:

The device will only be sold by Rajant Corporation or one of its authorized dealers. Rajant Corporation
and its authorized dealers will be under strict marketing control and will only market and sell the
device to professionals.

Professional installation is required for this device and will be performed only by someone
knowledgeable of its use. Rajant Corporation will ensure that the device is only marketed and sold to
professionals.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 8 de 62

The device is not sold to the general public and is sold only for industrial or commercial use by
professional installers.

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.

Maximum Certified Power

ISM band radio modules may be operated at full certified power when configured with the granted
antenna type. Operation of a radio at power levels that exceed the equivalent EIRP of the granted
configuration is prohibited. See the tables below.

Table: Maximum Certified Power: FCC (United States), IC (Canada)

Maximum Certified Total Maximum

Frequency Peak Conducted Channel Antenna Antenna Certified EIRP
Range (MHz) Power (dBm) Type Gain (dBi) (dBm)

Omni­
907­922 29.7 5 34.7
directional

Omni­
2412­2462 26.2 2 28.2
directional

Omni­
5745­5825 27.9 2 29.9
directional

Table:Maximum Certified Power: CE (Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic,
Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Liechtenstein, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania,
Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey, United Kingdom)

Maximum Certified Total Maximum

Frequency Mean Conducted Channel Antenna Antenna Certified EIRP
Range (MHz) Power (dBm, peak burst) Type Gain (dBi) (dBm)

Omni­
2412­2462 15 5 20
directional

Omni­
5180­5320 16 7 23
directional

Omni­
5500­5700 23 7 30
directional

Omni­

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 9 de 62

5745­5825 27 directional 6 33

Table: Maximum Certified Power: RCM (Australia, New Zealand)

Maximum Certified Total Maximum

Frequency Peak Conducted Channel Antenna Antenna Certified EIRP
Range (MHz) Power (dBm) Type Gain (dBi) (dBm)

Omni­
2412­2462 26.2 2 28.2
directional

Omni­
5745­5825 27.9 2 29.9
directional

Table: Maximum Certified Power: ANATEL (Brazil)

Maximum Certified Maximum

Frequency Total Conducted Antenna Antenna Certified EIRP
Range (MHz) Channel Power Type Gain (dBi) (dBm)

Omni­
917­927 30 dBm peak 5 35
directional

Omni­
2402­2482 28 dBm peak 5 34
directional

Omni­
5490­5710 23 dBm average 6 30
directional

Omni­
5735­5835 30 dBm peak 6 36
directional

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 10 de 62

GNU General Public License Statement

Certain 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.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 11 de 62

Preface

Purpose and Scope

This manual provides information and guidance to all personnel who are involved with and use Rajant
Corporation’s BreadCrumb LX5.

This manual begins with an introduction to the BreadCrumb Kinetic Mesh Network. It then
characterizes the features of the BreadCrumb LX5. 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 LX5 and BreadCrumb are used to refer
to Rajant BreadCrumb LX5.

Feedback Welcome

The 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 and revision number of the manual or product you are using as well as the
relevant document section numbers if appropriate.

Related Documentation

For additional information, refer to these documents:

BC|Commander® Version 11 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® Networks
BreadCrumb® Security Technical Brief

These documents are available in the support section of Rajant’s website at http://www.rajant.com.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 12 de 62

1. Introduction to BreadCrumbs

Rajant 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 and 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 with 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 Networks: Networks that must be established quickly and with
minimal effort for short‐term use (e.g., a network established to provide a temporary
network in a tactical situation).
Mobile Wireless Networks: Networks 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 Extension: Networks 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 Extension: Networks 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 Above: Most 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.

Note
Although 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.

1.2 The Mesh Network

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 13 de 62

The key component of a BreadCrumb Mesh 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 Definition

A 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 Connections

In 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:

Network Name (simply a configurable name for the network, default is “Rajant Mesh
Network”)
Network Key (a passphrase or key used for establishing mesh connections and obfuscating
unencrypted network management traffic)
Packet cipher setting
MAC cipher setting
Per‐hop verification setting
Key Sequence Number (defaults to 0)

To modify these settings via BC|Commander, the administrator must be logged in using the Crypto
Officer credentials.

1.2.3 Compatibility with v10

It is possible to have a mesh with both v10 and v11 BreadCrumbs. This is useful while upgrading a
network from v10 to v11. The following settings must be configured on the v11 BreadCrumbs in order
to establish mesh links with v10 BreadCrumbs:

Access Point: Enable Access Point must be checked, and Access Point: ESSID must match
the primary ESSID of the v10 BreadCrumb on at least one radio of the same frequency.
Version 10 firmware uses the BreadCrumb’s primary ESSID instead of the Network Name.
Security: Version 10 Network Authentication Key and Security: Version 10 Network
Encryption Key must match the NAK and NEK of the v10 BreadCrumb. Both v10 and v11
have the same default values.
InstaMesh: Enable v10 Compatibility must be checked.

Note

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 14 de 62

Because the crypto settings between v10 and v11 are different, the v10 Compatibility mode will only
work if ALL crypto settings are disabled on both the v10 and v11 BreadCrumbs.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 15 de 62

2. Description of a BreadCrumb LX5

The Rajant BreadCrumb LX5 is a rugged, portable wireless device that forms a mesh network when
used in conjunction with other BreadCrumb devices. The BreadCrumb LX5 contains up to four
transceivers, six external antenna ports, and supports IEEE 802.11a/b/g/n protocols to enable data,
voice, and video applications. This device can operate in extreme conditions and has several mounting
options. The BreadCrumb LX5 must be powered by an external source.

2.1 Radios

The BreadCrumb LX5 contains three or four 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 LX5, each with a different combination of
radios. See Appendix Radio Channels and Frequencies for a list of the channels and frequencies
supported by each of the radios.

2.2 Enclosure

The LX5 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 is designed for IP67 ingress
protection. The enclosure dimensions are 197 mm x 220 mm x 29 mm (7.750" x 8.665" x 1.125"). The
external features of the enclosure are shown in the following figures.

Figure: BreadCrumb LX5 Enclosure Features (Front)

Figure: BreadCrumb LX5 Enclosure Features (Back)

2.3 Antenna Connectors

The BreadCrumb LX5 provides up to six Type N female antenna connectors. The antenna connectors
are labeled with letters on the top of the enclosure. Three connectors (D, E, F) are located on the front
of the enclosure with the power switch and LED switch, and the other three connectors (A, B, C) are
located on the back of the enclosure with the two Amphenol connectors (see the Enclosure figures
above and the Enclosure top view below).

Some configurations only utilize one antenna port per radio. Some 802.11n configurations 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 LX5 models available, each with a different
configuration of radios and antennas. The letters “A” through “F” refer to the position of an antenna
connector and these letters are marked on the enclosure. Each antenna connector will also be labeled
with the frequency of its corresponding radio.

Important

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 16 de 62

BreadCrumb LX5 antennas may not be co­located. To satisfy this requirement, each antenna must be
installed with a minimum separation distance of 20 cm from any other LX5 antenna, and the antenna
of any other radio frequency transmitter. It is permissible to direct attach no more than two antennas
to the LX5, provided that these antennas are positioned on opposite sides of the LX5 (one on the
front side of the enclosure, one on the back side of the enclosure). For installations that will
experience vibration or shock, all antennas should be externally mounted and attached to the LX5
using cables. Low loss RF cable such as LMR­400 is recommended for cable attached antennas. If a
radio port is not required for a given application, the port should be disabled in software using
BC|Commander, and a 50 Ohm terminator should be installed.

Most of Rajant’s standard antennas are characterized by high­gain and therefore small vertical
beamwidth. Antennas in fixed locations should be installed plumb and at the same elevation so that
BreadCrumbs 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 turn off power to the BreadCrumb
before connecting or disconnecting external antennas.

The following figure shows the positions of the BreadCrumb LX5 antenna connectors.

Figure: BreadCrumb LX5 Enclosure (Top)

The following table lists the radio band and antenna port(s) for each wlan of current BreadCrumb LX5
models. This information is also available in the Details panel of BC|Commander.

Table: BreadCrumb LX5 Radios and Antenna Ports

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 17 de 62

Model Number wlan0 wlan1 wlan2 wlan3

LX5­2255A 2.4 GHz: F+A 5 GHz: B 5 GHz: E 2.4 GHz: C+D

LX5­2255B 5 GHz: F+A 2.4 GHz: B 2.4 GHz: E 5 GHz: C+D

LX5­2255C 2.4 GHz: F+B 5 GHz: A 2.4 GHz: D 5 GHz: C+E

LX5­2295A 2.4 GHz: F+A 5 GHz: B 900 MHz: E 2.4 GHz: C+D

LX5­2295C 2.4 GHz: F+A 5 GHz: E+B 900 MHz: D 2.4 GHz: C

LX5­2455D 5 GHz: F+A 2.4 GHz: E+B 5 GHz: C+D

LX5­2955B 5 GHz: F+A 2.4 GHz: B 900 MHz: E 5 GHz: C+D

LX5­2955C 2.4 GHz: E+B 5 GHz: F+A 900 MHz: D 5 GHz: C

2.4 22­Pin Amphenol Connector

The majority of the signals and features of BreadCrumb LX5 can be accessed through the two 22­pin
Amphenol connectors on the enclosure (see the Enclosure Back figure, and the the 22­pin connector
figure and table below). Each 22­pin Amphenol connector can interface to an optional LX5 cable
assembly that provides access to one Ethernet and one USB port of the device.

The BreadCrumb LX5 has two 22­pin Amphenol Connectors. The Amphenol connectors are labeled on
the LX5 case as 0 and 1. Connector 0 contains the first instance of each device (eth0, usb, serial port 0).
Connector 1 is rotated 180 degrees relative to connector 0 and contains the second instance of each
device (eth1, usb, serial port 1).

The Amphenol 22­pin connector in this figure is Connector 0 on the case of the LX5.

Figure: 22-Pin Amphenol Connector 0

Table: 22-pin Connector Pin Assignments

Pin Signal Cable Color Pin Signal Cable Color

RS­232

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 18 de 62

1 POE V­ Ethernet brown 12 TxD

RS­232
2 POE V­ Ethernet white/brown 13
RxD

3 POE V+ Ethernet blue 14 GND

4 RX1 + Ethernet white/green 15 POE V+ Ethernet white/blue

5 TX1 + Ethernet white/orange 16 RX1 ­ Ethernet green

6 GND USB black 17 TX1 ­ Ethernet orange

7 VIN + 18 GND

8 VIN + 19 GND

9 USB 5V+ USB red 20 GND

USB DATA
10 USB green 21 GND
+

USB DATA
11 USB white 22 GND
­

2.4.1 Power Requirements

The input power interface to the BreadCrumb LX5 resides on the 22­pin Amphenol connector (see the
Enclosure Back figure, and the the 22­pin connector figure and table above). The device accepts
external power in the range of 24 to 48 VDC. The average idle power consumption of BreadCrumb LX5
at 24 VDC is 7 W with three radios and 8 W with four radios. The maximum peak power consumption
of BreadCrumb LX5 at 24 VDC is is 26 W with three radios and 33 W with four radios. Up to 5 additional
watts of power will be needed if peripherals are being powered by USB (2.5 W available at each port).

Table: BreadCrumb LX5 Power Supply Options

Max.
Rajant Output Output
Part Voltage Current Ethernet Link
Model Number Type (V) (A) Speed (Mbps) Environmental

TP­POE­ 25­ AC
HP­ 100153­ to 48 1.04 10/100/1000 Non­sealed
48G­RC 001 DC

VHDC­ 01­ DC Sealed (IP67:

24V­ 000029­ to 24 2.08 10/100 dust­tight,
50W 01 DC waterproof)

VHDC­
24V­ 01­ DC Sealed (IP66:

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 19 de 62

50W­ 000037­ to dust­tight, water­

24 2.08 10/100/1000
GbE 002 DC resistant)

VHDC­ 01­ DC
24V­ 000033­ to 24 2.08 10/100 Non­sealed
50W­LC 01 DC

VHDC­ 01­ DC Sealed (IP67:

48V­ 000029­ to 48 1.04 10/100 dust­tight,
50W 48 DC waterproof)

Power for the BreadCrumb LX5 is typically provided by a Passive PoE (Passive Power over Ethernet)
injector. See the section Power and Ethernet below for more information. Additional information
about Rajant power supply accessories can be found in the Power Accessories product spec sheet at
www.rajant.com.

2.4.2 Power and Ethernet

The optional LX5 cable assembly plugs into either one of the 22­pin Amphenol connectors and
provides a standard RJ­45 Ethernet connector for easy access to an LX5 Ethernet port. Ethernet port
eth0 can be accessed through the 22­pin Amphenol connector labeled 0 on the enclosure and eth1 can
be accessed through the 22­pin Amphenol connector labeled 1 (see the Enclosure Back figure and 22­
pin Connector figure and table).

Both Ethernet ports (eth0, eth1) on the BreadCrumb LX5 support 10 Base­T, 100 Base­TX or 1000 Base­
T configuration. 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.

Either Ethernet port, when accessed through an LX5 cable assembly (see LX5 Cable Assembly), also
supports Passive Power over Ethernet (Passive PoE), and therefore acts as a dual function Ethernet and
DC power input port for the BreadCrumb LX5. An external inline injector is used to merge DC power for
the BreadCrumb LX5 with data from a LAN port or a wired client (see the PoE figures below).

To ensure proper operation of the BreadCrumb LX5, the inline injector must output a DC voltage
between 24 VDC to 48 VDC @ 26 W (three radio operation) or 33 W (four radio operation) minimum
and up to 5 W more if any peripherals are powered by USB. Using a higher output voltage facilitates
longer cable runs between the inline injector and the Ethernet port on the BreadCrumb LX5. For details
on Rajant’s VHDC­Series power accessories, please refer to the VHDC­Series spec sheet.

Warning
In order to avoid sparking and possible damage to the unit, connect the powered Ethernet cable to
the BreadCrumb LX5 before applying power to the power supply.

Figure: BreadCrumb LX5 Ethernet and Passive PoE AC Connections

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 20 de 62

Figure: BreadCrumb LX5 Ethernet and Passive PoE DC Connections

Warning
To protect the user against the risk of electric shock during high voltage transient events which may
occur when this equipment is installed outdoors, protective earth grounding of the POE power
supply is required. Case ground connections are provided on all Rajant supplied POE power supplies.
The case ground connections must be used and must be connected to a protective earth ground.
Protective earth grounding operations must be performed by trained personnel, and according to
local electrical codes and industry best practices, as well as Rajant’s own recommendations.

Multiple PoEs
If needed for redundancy or other reasons, a Passive PoE injector may be used on each of the two
Ethernet ports. If both injectors supply the same voltage then each will provide half of the current. If
one supplies a higher voltage, then that one must provide all of the current. For battery­powered
installations, the non­PoE power pins on the Amphenol connectors have a lower voltage drop and
are more suitable for a battery input. However, the customer would be accepting the risk of using a
custom power regime instead of a Passive PoE injector.

2.4.3 USB

The LX5 contains two USB ports, one on each of the 22­pin Amphenol connectors. One USB port can be
accessed with an optional LX5 cable assembly connected the 22­pin Amphenol connector labeled 0 on
the enclosure. The other USB port can be accessed on the 22­pin Amphenol connector labeled 1 using
an optional second LX5 cable assembly (see the Enclosure Back figure and 22­pin Connector figure and
table). The USB ports are compliant to the USB 2.0 specifications. The ports support all three standard
data transfer rates of low speed (1.5 Mbps), full speed (12 Mbps), and high speed (480 Mbps). The
data signals and power outputs include transient protection to the IEC61000­4­2­ESD and IEC61000­4­
4­EFT standards. The two USB ports each provide current limited 5 V, 500 mA to power a USB
peripheral.

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 or to an optional USB audio
device headset with microphone to use TRoIP (Tactical Radio over IP) on the BreadCrumb LX5.

2.5 LX5 Cable Assembly

An optional LX5 cable assembly can connect to one of the BreadCrumb’s 22­pin Amphenol connectors.
The cable assembly includes one Ethernet port and one USB port (see the cable drawing below).

Figure: BreadCrumb LX5 Cable Assembly Drawing

2.6 Status LED

The Status LED (see the Enclosure Front figure) 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

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 21 de 62

(switchable), OFF (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 the following table

Table: Status LED Color Codes

Color Status

White (red, green and blue LEDs together;

Powered on; start of boot process
may appear pale blue or pale green)

Red­Blue­Green scrolling in succession End of successful boot process

Ready, but no connected Mesh peers (unit may

Solid Blue
have Ethernet peers)

At least one connected Mesh peer; all peers are

Blinking Green
connected at less than 24 Mbps

At least one connected Mesh peer; one or more

Solid Green
peers are connected at 24 Mbps or faster

Blinking Yellow (with short and long pauses

Numeric warning code
between blinks)

Blinking Red (with short and long pauses

Numeric error code
between blinks)

Blinking Yellow (blinking at an increasing BreadCrumb is in the process of installing

rate) firmware

All LED colors scrolling in rapid succession

Successful firmware installation; ready to reboot
(with a short pause between every cycle)

All LED colors scrolling in rapid succession

Identify mode is ON
(with no pause)

For more information on BreadCrumb Status LED numeric codes see Appendix Error and Warning
Codes.

2.7 LED Configuration / Zeroize Keys and Restore Factory Defaults Switch

The LED Configuration / Zeroize Keys and Restore Factory Defaults Switch (see the Enclosure Front
figure) has two modes of operation. The modes are set by the length of time the switch is asserted.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 22 de 62

The modes are:

LED Configuration
Zeroize Keys and Restore Factory Defaults

2.7.1 LED Configuration

This 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 Version 11 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.

The following table lists the possible configured and corresponding alternate display states of the
Status LED.

Table: Configured and Alternate Display States of the Status LED

Configured State Alternate State

On (switchable) Off

Off (non­switchable) N/A

Alerts Only (switchable) On

Off (switchable) On

Note 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 LX5 is On.

Note
There 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 Defaults

This mode is is used to erase the security protocol keys of a BreadCrumb LX5 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.
Press and hold the switch until the Status LED changes to blinking yellow (approximately 10

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 23 de 62

seconds), then release the switch.

The Status LED will flash the yellow warning code “321” (BreadCrumb is being zeroized)
then flash rapidly yellow. This indicates that the Zeroize Keys and Restore Factory Defaults
operation has been initiated and is in progress.
The Status LED should flash the red error code “32” (BreadCrumb has been zeroized). This
error code will flash for up to 30 seconds.
The BreadCrumb will then automatically reboot using the factory default configuration.

See Appendix Error and Warning Codes for a description of blinking LED numeric codes.

Warning
Do 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.

Tip
The 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 Version 11 User Guide.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 24 de 62

3. Using BC|Commander

BC|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 both version 10 and version 11 firmware 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 Version 11 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.

Important
It 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 Version 11 User Guide.

Note
Some portions of the BC|Commander Version 11 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.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 25 de 62

4. Deploying a BreadCrumb Mesh Network

There are many factors which need to be taken into account when deploying a BreadCrumb mesh
network. This chapter describes the addressing scheme of the mesh, channel assignments and some of
the most commonly occurring environmental factors that will have a major impact on the performance
of the mesh. The final section details guidelines and methodology needed to follow when deploying
the mesh.

4.1 Addressing

When 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.

Note
Any 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 Version 11 User Guide
document for the details of the BreadCrumb IP address configuration.

4.1.1 BreadCrumb Device Addresses

Each 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 DHCP

Each BreadCrumb device includes an embedded DHCP server. You may safely enable the DHCP servers
of multiple BreadCrumb devices simultaneously. 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 BreadCrumb’s IPv4 address.
Add a low‐byte range of 10 to 210.

4.2 Channel Assignments

BreadCrumb radios have default channels assigned, based on the frequency and type of the radio. See
the following table for a list of radio frequencies and their default channel assignments. When more
than one radio of the same frequency is present, there may be default channels for the additional
radio(s). This table includes radios that may be found in different BreadCrumb models, not one specific
model.

Table: Default Channel Assignments

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 26 de 62

Radio Card Frequency and Type Default Channel Second Default Third Default

900 MHz 802.11g 5

2.4 GHz 802.11n 11 1

2.4 GHz 802.11g 11 1

4.8 GHz 802.11a 164 184 174

4.9 GHz 802.11a 20

5 GHz 802.11a 153 161

5 GHz 802.11n FCC:157, CE:136 FCC:149, CE:100

In 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 Version 11 User Guide for the details of BreadCrumb channel
configuration.

4.3 Physical Placement and other Considerations

Commonly 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­Sight

Unobstructed 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.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 27 de 62

4.3.2 Distance

Many 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.
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 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 the chapter 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 Weather

Precipitation 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 Interference

RF 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 Components

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 28 de 62

The 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 range. Elevating a device above the ground dramatically increases the maximum effective
range. Rajant recommends elevating the components a minimum of 6 ft. above the surrounding
surface.

4.4 Deployment Guidelines and Methodology

This 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 Guidelines

Follow these guidelines when deploying the mesh:

1. Placement of BreadCrumbs
a. Elevate the BreadCrumbs whenever possible.
1. 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.
2. 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 Methodology

The steps detailed in this section should assist you in successfully deploying the mesh.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 29 de 62

1. Scan the terrain on which the mesh will be deployed.

a. Determine the initial distances between BreadCrumb devices. Refer 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.
b. 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.
1. At this point, you may choose to proceed farther in an attempt to
make optimal use of the available BreadCrumbs.
2. 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.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 30 de 62

5. Firmware Upgrade and Zeroize

Each 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 Version 11 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 Upgrade

One 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 Version 11 User Guide (Administrative Tasks – Over­the­Air
(OTA) firmware upgrade) to perform the firmware upgrade process.

5.2 USB Firmware Upgrade

Another 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 Version 11 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 version 11, 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.
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.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 31 de 62

Take note of the error code (see Appendix Error and Warning Codes) 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 Over the Air Zeroize

If it is necessary to erase all settings of a BreadCrumb, the BreadCrumb…Zeroize feature of

BC|Commander can be used. Note that this will likely make that BreadCrumb unable to connect to
your mesh due to incompatible settings so it is best to use this feature only on BreadCrumbs that can
be physically accessed.

5.4 USB­Based Zeroize

Version 11 firmware includes 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 zeroize
process, follow these procedures:

1. Prepare a USB storage device using BC|Commander by selecting the “Zeroize (Do Not
Upgrade)” option in the USB Flash Manager. Please see the BC|Commander Version 11
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 version 11, 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.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 32 de 62

6. Troubleshooting

Note
Battery tips apply to any BreadCrumb that is powered by batteries, solar power or any power source
that may become irregular or weak.

DFS and Troubleshooting

When troubleshooting problems with a BreadCrumb radio on a 5 GHz DFS channel, remember that
radio must listen for radar and not transmit (or mesh) for typically 1 minute after is it fully booted.
Channels in the frequencies 5600­5650 MHz, if available, may have a 10 minute wait. In addition, if a
radar­like noise pattern is detected on the channel, the radio will shut down for 30 minutes. For
more information including some potential causes of false radar detections, see this section: DFS and
TPC.

6.1 Sporadic Network Connectivity

a. If a BreadCrumb is powered by a battery, as the battery approaches exhaustion, network

connectivity will become sporadic for the BreadCrumb device and its associated wireless
clients.
Monitor battery usage and charge or replace batteries as necessary.
b. 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.
c. As a mobile wireless client moves around through the coverage area, LOS (line of sight) to
the BreadCrumb device can become obstructed resulting in sporadic network connectivity
for this wireless client.
Train mobile wireless client 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.
d. A mobile 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.
e. A wireless client cannot join the network.
Ensure that BreadCrumb devices are powered on.
Ensure that the BreadCrumb configuration has Enable Access Point checked.
This is off by default.
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 client’s wireless card is in “Infrastructure” or “Access Point”
mode, and not in “Ad Hoc” mode. Scan for the default ESSID “rajant” (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 client device and BreadCrumb devices
match.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 33 de 62

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 Version 11 User Guide for more information.

6.2 BreadCrumb Device Cannot Connect to Mesh

a. A new BreadCrumb or a BreadCrumb reset to factory defaults is running with settings

which do not match those of the network to be joined.
Configure the BreadCrumb settings to match those of the network to be joined.
b. Discharged batteries can cause the BreadCrumb device to appear to power up, but not be
able to establish connectivity to the mesh.
When deploying any battery­powered BreadCrumbs to the mesh, ensure that
the batteries are fully charged.
c. 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 Issues

a. Discharged external batteries can cause a BreadCrumb to appear to power up(“PWR” LED is
lit), but fail to start­up.
Monitor battery usage and charge/replace batteries as necessary.
b. Electrostatic 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.

Caution
In order to avoid sparking and possible damage to the device, be sure to
connect the power cable to the BreadCrumb before applying power to the
power supply.

­­­

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 34 de 62

7. Appendices

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 35 de 62

Appendix A: Radio Channels and Frequencies

Rajant BreadCrumbs contain from one to four radios, depending on the model. 802.11g radios are
used in the 900 MHz and 2.4 GHz bands. 802.11a radios are used in the 4.8 GHz, 4.9 GHz and 5 GHz
bands. 802.11n radios are used in the 2.4 GHz and 5 GHz bands. Each BreadCrumb model supports its
own specified radio or combinations of radios.

The radios support the channels and frequencies listed in the following tables. Which channels are
available for use depends on country and regulatory agency.

Note
Not 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.

Caution
Since 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.

A.1 Radio: 2.4 GHz 802.11n

Table: 2.4 GHz 802.11n Radio Channels and Frequencies

Channel Number Center Frequency (MHz) HT40 Capability

1 2412 HT40 +

2 2417 HT40 +

3 2422 HT40 +

4 2427 HT40 +

5 2432 HT40 +, HT40 ­

6 2437 HT40 +, HT40 ­

7 2442 HT40 +, HT40 ­

8 2447 HT40 +, HT40 ­

9 2452 HT40 +, HT40 ­

10 2457 HT40 ­

11 2462 HT40 ­

12 2467 HT40 ­

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 36 de 62

13 2472 HT40 ­

14 2484 HT20 only

The default channel and channel mode for a BreadCrumb 2.4 GHz 802.11n radio is 11 (2462 MHz) and
HT20. If a second 2.4 GHz 802.11n radio is present, its default channel and channel mode is 1 (2412
MHz) and HT20.

2.4 GHz channels support HT40 mode. In this mode, the radio binds two standard 20 MHz channels to
obtain a wider bandwidth 40 MHz channel. The + or ­ designation describes if the second channel is
above or below the base channel. Plus (+) indicates that the additional 20 MHz occurs above (at a
higher frequency than) the first 20 MHz while minus (­) indicates that the additional 20 MHz occurs
below (at a lower frequency than) the first 20 MHz. Note, the frequency noted is the center frequency
of the base 20 MHz channel. This is different from 802.11a turbo mode where the frequency was the
center of a single 40 MHz wide channel. HT40 operation (+ or ­) is compatible with 802.11a 20 MHz
and 802.11n HT20 modes. HT40 operation is NOT compatible with 802.11a turbo mode.

A.2 Radio: 5 GHz 802.11n

Table: 5 GHz 802.11n Radio Channels and Frequencies

Channel Number Center Frequency (MHz) HT40 Capability

36 5180 HT40 +

40 5200 HT40 ­

44 5220 HT40 +

48 5240 HT40 ­

52 5260 HT40 +

56 5280 HT40 ­

60 5300 HT40 +

64 5320 HT40 ­

100 5500 HT40 +

104 5520 HT40 ­

108 5540 HT40 +

112 5560 HT40 ­

116 5580 HT40 +

120 5600 HT40 ­

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 37 de 62

124 5620 HT40 +

128 5640 HT40 ­

132 5660 HT40 +

136 5680 HT40 ­

140 5700 HT20 only

149 5745 HT40 +

153 5765 HT40 ­

157 5785 HT40 +

161 5805 HT40 ­

165 5825 HT20 only

The default channel and channel mode for a BreadCrumb 5 GHz 802.11n radio in the US and Canada is
157 (5785 MHz) and HT40+. If a second 5 GHz 802.11n radio is present, its default channel and channel
mode is 149 (5745 MHz) and HT40+. In most European countries, the default channel and mode is 136
(5680 MHz) and HT40­, and if a second radio is present, its default channel and mode is 100 (5500
MHz) and HT40+. In other countries the default channels may differ based on local regulations.

Note
If the default channels aren’t available, the default will instead be the first valid channel (in order of
channel number) with the largest bandwidth (up to 20 MHz) that doesn’t conflict with other radios. If
that fails, meshing will be disabled on that radio.

Some 5 GHz channels support HT40 mode. In this mode, the radio binds two standard 20 MHz
channels to obtain a wider bandwidth 40 MHz channel. The + or ­ designation describes if the second
channel is above or below the base channel. Plus (+) indicates that the additional 20 MHz occurs above
(at a higher frequency than) the first 20 MHz while minus (­) indicates that the additional 20 MHz
occurs below (at a lower frequency than) the first 20 MHz. Note, the frequency noted is the center
frequency of the base 20 MHz channel. This is different from 802.11a turbo mode where the frequency
was the center of a single 40 MHz wide channel. HT40 operation (+ or ­) is compatible with 802.11a 20
MHz and 802.11n HT20 modes. HT40 operation is NOT compatible with 802.11a turbo mode.

Caution
Most 5 GHz antennas only support a subset of the 802.11n 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.

A.3 DFS and TPC

DFS and TPC for 5 GHz Channels

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 38 de 62

Many channels in the 5 GHz band are subject to regulations that require active avoidance of
interference with weather radar and other radars (Dynamic Frequency Selection aka DFS). In many
countries, regulations also require lower transmit power for nearby wireless connections (Transmit
Power Control aka TPC) on the same channels. These DFS channels may be available for use in some
countries on BreadCrumbs with 5 GHz radios that provide hardware support for radar detection.

The list of 5 GHz channels that are subject to DFS and TPC depends on the regulatory domain of the
region of operation. In many regions any available channels from 5260­5700 MHz require DFS, or DFS
and TPC. In some regions, additional channels require DFS and TPC.

DFS channels will not be available immediately upon startup and will become non­operational for a
fixed period of time after radar or any radar­like pulse of noise is detected.

BreadCrumb DFS Behavior

After power­on or restart, all transmits on a DFS channel will be disabled for 1 minute
(typical) while the radio pre­checks for radar on that channel (the Channel Availability
Check aka CAC). If the 1 minute completes without detecting radar, the radio can then start
normal operation on the channel while still continuously checking for radar. Note: Channels
from 5600 MHz to 5650 MHz, if available, may have a 10 minute CAC period.
If radar detection is triggered on a DFS channel, that radio will stop transmitting for 30
minutes (the Non­Occupancy period aka NOP). Warning code 382 “Radar detection paused
radio: wlanN (wlanN …)” will be displayed in BC|Commander if the affected unit was able
to report its warning status over another radio or over ethernet.
When the 30 minute NOP period of not transmitting completes, before reusing the DFS
channel, the radio must not transmit for 1 additional minute (may be 10 minutes for
5600­5650 MHz) while pre­checking for radar (a CAC period). If no radar is detected during
the CAC period, normal radio operation is resumed with continuous checking for radar.
When resuming normal operation after a radar detection, the radar detection warning
382 will be removed from the radio and a warning 383 “Radio resumed from radar pause:
wlanN (wlanN, …)” will be added. This 383 “unpaused” warning will remain up for 12 hours
so that personnel will know what radios were affected by DFS stoppages. Warning 383 will
be removed when all listed radios have been aged out.

About Radar Detection

Radar is detected as pulses (spikes) of radio frequency (RF) noise. If pulses of noise make it past several
range checks, and the pattern of pulses is sufficiently similar to a radar pattern, a radar detection event
will occur. False detections may be caused by anything that creates RF interference including electrical
equipment, improperly positioned antennas, nearby wireless radio devices and RF reflections caused
by antennas too close to the ground, walls or other RF­reflecting surfaces.

If possible, use of DFS channels should be avoided for critical network paths, especially if the
BreadCrumb has no other wired or wireless network connections to the mesh.

Note: Two new DFS­related fields can be examined in BCAPI Explorer. For wireless DFS channels, these
fields will indicate the count of RF interference pulses encountered as well as a count of how many
were deemed sufficiently similar to radar by the radar pattern detector.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 39 de 62

state.wireless[n].stats.pulseEvents – Raw count of interference pulses detected by the

radio
state.wireless[n].stats.radarDetections – Count of pulses that triggered radar detector

TDWR

Terminal Doppler Weather Radar (TDWR) operates in the frequencies 5600­5650 MHz. TDWR helps
protect airplanes from hazardous weather such as wind shear and gusts. Wireless network installations
within 35 km of or in line­of­sight of a TDWR must not use TDWR frequencies and should avoid using
channels within 30 MHz of the TDWR frequencies. A list of U.S. TFDR radar coordinates may be found
at WISPA.org: WISPA.org ­ see TDWR Resources

Warning
Operating this equipment in violation of Local, Regional or National Standards, including interfering
with radar, is likely to result in substantial sanctions to the User, including fines, imprisonment,
confiscation of equipment, and other penalties as determined by your local regulatory authorities.

A.4 Radio: 4.8 GHz 802.11a

Table: 4.8 GHz 802.11a Radio Channels and Frequencies

Channel Number Center Frequency (MHz) Channel Number Center Frequency (MHz)

162 4810 175 4875

163 4815 176 4880

164 4820 177 4885

165 4825 178 4890

166 4830 179 4895

167 4835 180 4900

168 4840 181 4905

169 4845 182 4910

170 4850 183 4915

171 4855 184 4920

172 4860 185 4925

173 4865 186 4930

174 4870

The default channel for a BreadCrumb 4.8 GHz radio is 164 (4820 MHz). If a second 4.8 GHz radio is
present, its default channel is 184 (4920 MHz). If a third 4.8 GHz radio is present, its default channel is

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 40 de 62

174 (4870 MHz).

A.5 Radio: 4.9 GHz 802.11a

Table: 4.9 GHz 802.11a Radio Channels and Frequencies

Channel Number Center Frequency (MHz) Channel Bandwidth

5 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 BreadCrumb 4.9 GHz radio is 20 (4950.0 MHz). If a second 4.9 GHz radio is
present, its default channel is 80 (4980.0 MHz). If a third 4.9 GHz radio is present, its default channel is
40 (4960.0 MHz).

A.6 Radio: 900 MHz 802.11g

Table: 900 MHz 802.11g Radio Channels and Frequencies

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 41 de 62

Channel Number Center Frequency (MHz) Channel Bandwidth

4 907 Half (10 Mhz)

5 912 Full (20 Mhz)

6 917 Full (20 Mhz)

7 922 Half (10 Mhz)

The default channel for a BreadCrumb 900 MHz 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.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 42 de 62

Appendix B: Error and Warning Codes

All possible BreadCrumb error and warning codes are listed below.

Numeric error codes are displayed as groups of red (error) or yellow (warning) LED blinks. For example,
a meshed BreadCrumb displays a green LED. If the BreadCrumb starts to display warning 37, the
following would be seen: green (link state), yellow blinks 3 times, short pause, yellow blinks 7 times,
long pause of green (link state), yellow blinks 3 times, short pause, yellow blinks 7 times, etc.

Code 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 Unable to retrieve next boot image number.

16 Unable to set fail safe boot mode.

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 Flash unbundle 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.

BreadCrumb will be in failsafe mode and unable to communicate with other

123
BreadCrumbs after next reboot.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 43 de 62

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.

129 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 copy init image.

136 Failed to copy bootloader image.

137 This flash image may not be installed onto this BreadCrumb.

138 Failed to copy failsafe file system.

141 Error retrieving flash file.

142 The version you are installing does not support the configured Packet Cipher

143 The version you are installing does not support the configured MAC Address Cipher

The version you are installing does not support the configured Per­hop Authentication
144
algorithm

145 The version you are installing does not support the configured security policy

146 Failed to verify consistent country settings

147 The configured countries are not consistent

151 Pre­manufacturing install process failed

152 Firmware install failed

153 Post­manufacturing install process failed

154 The autorun is missing required symbols

145 The version you are installing does not support the configured security policy

Recovery log detected. To clear this message, please take a diagnostic snapshot and
21
upload to https://secure.rajant.com.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 44 de 62

Internal error detected. Please take a diagnostic snapshot and upload to

22
https//secure.rajant.com. This message will be cleared on the next reboot.

Code 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(s) not detected.

331 Radio in MANUAL compliance mode is violating country regulation.

333 Low Battery

334 Gas gauge not initialized. To initialize, please power off unit and fully charge.

34 Cannot read /dev/nand6 information, or cannot resize or format /dev/nand6.

36 Hardware monitor missing.

37 Failed to configure ethernet port

38 Resetting radio due to error.

381 Noise floor threshold exceeded

382 Radar detection paused radio

383 Radio resumed from radar pause

384 Spectrum Access not granted

385 Radio(s) failed to initialize

Code FIPS Codes (4*)

41 FIPS Power­on self­tests failed.

411 FIPS DRBG power­on self test failed.

412 FIPS DRBG continuous test failed.

413 FIPS DRBG health check failed.

414 Kernel integrity check failed.

415 Filesystem integrity check failed.

416 FIPS USB test vector data missing.

417 FIPS Invalid configuration.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 45 de 62

418 Flash image may not be installed while in FIPS mode.

42 Mixed SecNet/Non­SecNet configuration.

43 Rekeying error.

44 Rekeying error.

45 Rekeying error.

46 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).

Code Fatal and Serious Codes (5*)

51 instamesh fatal error.

52 hostapd fatal error.

521 disabling HT40 operation to prevent conflict with a nearby BSS

522 IEEE 802.11 TKIP countermeasures initiated

53 cvm fatal error.

54 fatal error.

541 Software error

55 Low memory ­ automatic reboot scheduled.

56 APT peer bridge settings do not match

57 logwatcher start timeout

Code Battery Gas Gauge Codes (6*)

61 Battery gas gauge i2c device could not be found.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 46 de 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.

66 Incorrect ME3 gas gauge revision 0 EEPROM settings.

67 Internal battery charger disabled.

Code Other Codes (7, 8, 9*)

71 Host flapping detected.

72 Critical I2C failure.

73 Invalid channel configured.

74 Bad factory configuration.

741 Signing key installation failure.

75 Unsupported hardware component.

76 Potential loop detected, turned off port

77 Model is not supported in this version of firmware. Contact support.

81 reserved

811 Default Network Key is in use.

82 reserved

83 reserved

84 reserved

85 reserved

86 reserved

87 reserved

88 reserved

89 reserved

91 Invalid SSL Handshake Priority String:

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 47 de 62

Appendix C: Mounting

C.1 Mounting Holes

The following figure shows the size and spacing of the BreadCrumb LX5 mounting holes. The depth of
the LX5 case is 29 mm (1.125 inch).

C.2 Using a Flat Plate Mounting Kit

An LX5 Flat Plate Mounting Kit can be used mount the BreadCrumb LX5.

Use the four (4) supplied bolts to attach the BreadCrumb LX 5 to the Flat Plate.

The Flat Plate can be used with Rajant LX4 Pole Mounting Brackets to mount the BreadCrumb LX5 on a
pole.

Use the two (2) supplied U­bolts and four (4) nuts to secure the Flat Plate and BreadCrumb
assembly to a pole.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 48 de 62

Appendix D: Rajant End User License Agreement

The BreadCrumb® Wireless LAN System

Rajant Corporation End User License Agreement

IMPORTANT: 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 © 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 SOFTWARE, 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

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 49 de 62

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 Rajant
equipment, and Customer acknowledges that any attempted transfer, assignment, sublicense or use

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 50 de 62

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

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 51 de 62

limitations of liability and 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

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 52 de 62

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 which 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.

No representation or other affirmation of fact, including but not limited to statements regarding
capacity, suitability for use or performance of Software, whether made by Rajant employees or
otherwise, shall be deemed to be a warranty for any purpose or give rise to any liability of Rajant
whatsoever unless contained in this Agreement.

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, © is assembled or deployed with non­authorized Rajant accessories;
(d) has been subjected to abnormal physical or electrical stress, abnormal environmental conditions,
misuse, negligence, or accident; or (e) is licensed for beta, evaluation, testing or demonstration
purposes. The Software warranty also does not apply to (f) any temporary Software modules; (g) any
Software not posted on RAJANT’s Software Center; (h) any Software that RAJANT expressly provides
on an “AS IS” basis on RAJANT’s Software Center; (i) 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

THE BREADCRUMB WIRELESS LAN UNITS (“BREADCRUMB”), EXCLUSIVE OF THE JR­2 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.

JR­2 BREADCRUMBS ARE WARRANTED ONLY AGAINST DEFECTIVE WORKMANSHIP FOR 90 DAYS WHEN
DELIVERED NEW. RAJANT MAKES NO WARRANTY, AND DISCLAIMS ANY WARRANTY, EXPRESS OR
IMPLIED AT LAW, ON JR­2 BREADCRUMBS' FITNESS FOR A PARTICULAR PURPOSE OR
MERCHANTABILITY. MANUFACTURER’S RMA POLICIES AND PROCEDURES APPLY.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 53 de 62

RAJANT PRODUCTS CLASSIFIED AS ACCESSORY ON MANUFACTURER’S PRICE LIST ARE WARRANTED

AGAINST DEFECTS FOR A PERIOD OF 90 DAYS FROM DATE OF DELIVERY.

THE RAJANT HARDWARE LIMITED WARRANTY ONLY APPLIES WHEN GENUINE RAJANT HARDWARE
AND AUTHORIZED ACCESSORIES ARE USED BY THE INSTALLER AND END USER. USE OF ANY NON­
AUTHORIZED ACCESSORIES OR PERIPHERAL EQUIPMENT VOIDS THE RAJANT LIMITED 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; © 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.

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 Warranty

Rajant 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.

DISCLAIMER OF WARRANTY

EXCEPT AS SPECIFIED IN THIS WARRANTY SECTION, ALL EXPRESS OR IMPLIED CONDITIONS,

REPRESENTATIONS, AND WARRANTIES INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTY

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 54 de 62

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 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).

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.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 55 de 62

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, EMPLOYEES, AGENTS, SUPPLIERS AND
LICENSORS, BE LIABLE FOR ANY LOST REVENUE, LOST PROFIT, OR LOST OR DAMAGED DATA, BUSINESS
INTERRUPTION, LOSS OF CAPITAL, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL, OR
PUNITIVE DAMAGES, HOWSOEVER ARISING, INCLUDING, WITHOUT LIMITATION, IN CONTRACT, TORT
(INCLUDING NEGLIGENCE) OR WHETHER ARISING OUT OF THE USE OF OR INABILITY TO USE THE
SOFTWARE, EVEN IF, IN EACH CASE, RAJANT, ITS AFFILIATES, OFFICERS, DIRECTORS, EMPLOYEES,
AGENTS, SUPPLIERS AND 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 FULLY APPLY TO YOU.
THE FOREGOING EXCLUSION SHALL NOT APPLY TO ANY LIABILITY ARISING OUT OF OR IN CONNECTION
WITH: (I) DEATH OR PERSONAL INJURY, (II) FRAUDULENT MISREPRESENTATION, OR (III) RAJANT’s
LIABILITY IN CONNECTION WITH ANY TERMS THAT CANNOT BE EXCLUDED UNDER APPLICABLE LAW.

Customer acknowledges and agrees that RAJANT has set its prices and entered into the Agreement in
reliance upon the disclaimers of warranty and the limitations of liability set forth herein, that the same
reflect an allocation of risk between the parties (including the risk that a contract remedy may fail of its
essential purpose and cause consequential loss), and that the same form an essential basis of the
bargain between the parties.

Controlling Law, Jurisdiction. Customer agrees that all sales occurred, and contracts entered into at
Malvern, Pennsylvania, notwithstanding the location of any affiliate or Customer’s location or principal
place of business. All contracts for the license of software and/or purchase of hardware are deemed to
have occurred at Malvern, Pennsylvania and the Agreement and warranties (“Warranties”) are
controlled by and construed under the laws of the Commonwealth of Pennsylvania, United States of
America, notwithstanding any conflicts of law provisions; and the state and federal courts of
Pennsylvania shall have exclusive jurisdiction over any claim arising under the Agreement or
Warranties.

The parties specifically disclaim the application of the UN Convention on Contracts for the
International Sale of Goods. Notwithstanding the foregoing, either party may seek interim injunctive
relief in any court of appropriate jurisdiction with respect to any alleged breach of such party’s
intellectual property or proprietary rights. If any portion hereof is found to be void or unenforceable,
the remaining provisions of the Agreement and Warranties shall remain in full force and effect. Except
as expressly provided herein, the Agreement constitutes the entire agreement between the parties
with respect to the license of the Software and Documentation and supersedes any conflicting or
additional terms contained in any Purchase Order or elsewhere, all of which terms are excluded. The

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 56 de 62

Agreement has been written in the English language, and the parties agree that the English version will
govern.

Product warranty terms and other information applicable to RAJANT products are available at the
following URL: www.rajant.com

RAJANT and the RAJANT Logo are trademarks of RAJANT Corporation and/or its affiliates in the U.S.
and other countries. Third party trademarks mentioned are the property of their respective owners.
The use of the word partner does not imply a partnership relationship between RAJANT and any other
company.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 57 de 62

Appendix E: GNU General Public License

Version 2, June 1991

Copyright © 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.

PREAMBLE

The 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.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 58 de 62

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

1. 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”, below, 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.

1. 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

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 59 de 62

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.

1. 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.

1. 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.
2. 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

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 60 de 62

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.
3. 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.
4. 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. For 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.

1. 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.
2. 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.

1. 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

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 61 de 62

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

1. 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.
2. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL 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 CONDITIONS

HOW 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 © 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,

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016
BreadCrumb® LX5 Version 11 User Guide Página 62 de 62

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 © 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.

You 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.

file:///O:/Andamento/OCD/R/Rajant/28972_14/28972_14.1/Contratos/Manual/Enviad... 05/04/2016