Warnings call attention to a procedure or practice that could result in
personal injury if not correctly performed. Do not proceed until you fully
understand and meet the required conditions.
Cautions call attention to an operation procedure or practice that could
damage the product, or degrade performance if not correctly performed.
Do not proceed until understanding and meeting these required
conditions.
Notes provide information that can be helpful in understanding the
operation of the product.
___________________________________________________________________________ 2
User’s Guide, WhereLAN III draft D1675 rev F
This document describes the basic configuration and recommendations on
physical installation of the WhereLAN III product, which is part of the
Location Sensor product line. The site design and placement is detailed in the
Location Sensor Placement Guide D0406 and WhereLAN III Instruction
Sheet (26913), provide with each unit.
2 PRODUCT DESCRIPTION AND FEATURES
The WhereLAN III is the next generation of WhereLAN product that receives
the signals transmitted by WhereTags (ISO 24730-2), and provides data to the
Location Algorithm processor. The received tag blinks are decoded, time
stamped, and routed to a Windows Server or ZLA (Zebra Location Appliance)
for additional processing. The locate algorithm running on the Windows
Server or ZLA calculates the tag position based on the time stamps of multiple
Location Sensors, and reports that position to the database where it is
displayed by Resource Manager.
The WhereLAN III Location Sensor supports the same Real Time Locating
System (RTLS) functions as the previous sensor, known as the WhereLAN
Location Sensor (LOS). WhereLAN III is fully backwards compatible and
may be used, as outlined herein, as a drop-in replacement for any existing
LOS. However, the WhereLAN III incorporates modern and patent-pending
techniques that result in superior accuracy performance over the current LOS
product. In addition, WhereLAN III supports a number of other value-added
features, as follows:
Time Synchronization: Like the LOS, WhereLAN III supports wireless and
wired time synchronization. However, the product can operate in two distinct
time synchronization modes, known as “Legacy” and “Time Synch II” As
shipped, the product defaults to Legacy time synchronization. In Legacy
mode, WhereLAN III is drop-in compatible with LOS and is backwards
compatible with VSS release 3.8. The Legacy Time service relies on various
user-defined entities, such as Line-of-Sight lists and Timing Islands. Time
Synch II no longer exposes these entities to the end user. A site must run
either the Legacy Time service or the Time Synch II service, but not both. In
Time Synch II mode, WhereLAN III furnishes additional data required by a
new Time Synchronization Process, scheduled for release in Q4 2012, which
runs on the Windows Server or ZLA. The Time Synch II service reduces site
design complexity and post-install support. It accomplishes this by being
“self-configuring” and “self-adjusting”; it hides its configuration details from
___________________________________________________________________________ 8
User’s Guide, WhereLAN III draft D1675 rev F
the end user, automatically self configures and automatically adjusts to a wide
range of Radio Frequency environmental changes. The new Time Synch II
service is substantially different from and is not backwards compatible with
the Legacy Time Synch service. In Legacy mode, the embedded wireless time
beacons are transmitted over the right channel whereas both the left and right
channels are used in Time Synch II mode. Time Synch II can operate in an all
WhereLAN IIIs network, an all LOSs network, or a network with mixed
WhereLAN IIIs and LOSs. However, in order for Time Synch II to work with
LOSs, they must operate in “dual-posting” mode.
Wi-Fi: A variant of the LOS, known as a Locating Access Point (LAP),
supports an integral 802.11 b/g/a Access Point. WhereLAN III does not
support an integral Access Point. Instead, a variant of WhereLAN III supports
establishing an 802.11 b/g Wi-Fi client side connection to any industrystandard Access Point. Unlike WhereLAN III, the LOS does not support
establishing Wi-Fi client side connections.
Network Auto-Configuration (DHCP) and IPv6: The WhereLAN III, with the
release of VSS 4.0.5.2 support both DHCP IP and IPv6 address assignment.
However, the methods used by system software to establish connectivity with
the sensors on start-up preclude the full use of (dynamic) DHCP IP addresses.
This restriction is being eliminated, in the VSS 4.0.5.2 release, for WhereLAN
III sensors by a new process, referred to as Network AutoConfig. This
process conveys the IP address of the RTLS server to the WhereLAN IIIs as
part of the standard DHCP IP address assignment message exchange. In turn,
the WhereLAN IIIs “check-in” with the RTLS server by passing it the MAC
address of their Ethernet port. The RTLS server uses the MAC address to
“authenticate” the identity of the WhereLAN IIIs by checking for the MAC
addresses to be present in the site configuration file.
IEEE 802.3af Power of Ethernet (PoE): WhereLAN III supports industrystandard PoE. This allows for easier installation as it removes the need to run
DC power cabling to the unit. PoE may be supplied by any standardscompliant network switch. Alternatively, Zebra offers a single-line PoE
injector.
Power Consumption: WhereLAN III consumes just 12 watts, a 31% and 57%
reduction relative to the LOS and LAP, respectively.
___________________________________________________________________________ 9
User’s Guide, WhereLAN III draft D1675 rev F
The WhereLAN III product line contains the following product skews:
LOS-5000-00AA: This is a “base” WhereLAN III unit, with an integral
802.3af compliant Ethernet interface, supporting wireless and wired timing
options.
LOS-5000-00AB: This version adds 802.11 b/g Wi-Fi support, in client
mode, to the base unit. This part number is approved for sale to U.S. Federal
Government procurements.
LOS-5000-00CA: This is a “base” WhereLAN III unit approved for sale to
U.S. Federal Government procurements.
LOS-5000-01AA: This is a “base” WhereLAN III unit incapable of
transmitting a wireless time beacon and is approved for sale to U.S. Federal
Government procurements.
___________________________________________________________________________ 10
User’s Guide, WhereLAN III draft D1675 rev F
Antenna (2): MCX (Jack)
DC Power: 2.5 ID/ 5.5 OD mm (Jack)
Opt. Wi-Fi Antenna: SMB (Jack)
Ethernet: RJ45 (Jack) 10/100 and 802.3af POE
Timing (3): RJ-22 (4 wire telephone handset, Jack)
With the exception of the LOS-5000-00AB model (Wi-Fi backhaul), the
WhereLAN III must be wired to a nearby 10/100BaseT Ethernet switch or
hub. In addition, the network to which the switch or hub connects must allow
full access to a number of standard communication protocols and port ranges
(TCP/IP, UDP, ftp, etc). See the Zebra VSS Software Installation Guide for
further detail on the interconnecting network requirements. The maximum
Ethernet cable run is 328 ft (100 m). If additional distance is required, hubs,
repeaters, and fiber (with 10baseT converters) can be used to extend the
distance. Refer to IEEE guidelines for Ethernet cabling. The LOS-500000AB must be configured to connect to an IEEE 802.11 b/g Wi-Fi network, as
outlined in this document.
___________________________________________________________________________ 12
User’s Guide, WhereLAN III draft D1675 rev F
Upon power up, WhereLAN III executes a self-boot process. The boot
process takes between 45 to 60 seconds. If a fault occurs during the boot
process, the unit may reset and restart the boot process. During that process,
the four LEDs blink in a sequence to indicate the current stage of the power
up boot process. The LED Process is as follows after initial power is applied.
• 1 LED (Power): The Boot Loader is loading the Kernel.
• 4 LED’s : The Kernel is initialized and is loading the applications,
JFFS2 and CRAM File system
• 1 LED (Power): The Application is loading the FPGA’s and DSP’s
• 2 LED’s (Power and Tag Reception): The unit is initializing the
FPGA’s and DSP’s.
• 1 LED (Power): Unit is booted and ready for operations.
Location Sensor
ower/
ealth
Tag
Reception
Ethernet
WLAN
Outdoor
Omni
Antenna
Figure 1 LOS-5000 LED's
___________________________________________________________________________ 14
User’s Guide, WhereLAN III draft D1675 rev F
Once the boot process is complete, the LEDs revert to their standard
functions indicating power/health, tag status, Ethernet, and Wi-Fi.
Power
Ethernet
Tag Reception
WLAN
•Power/Health LED: Indicates unit has power and general health of
unit.
o State 1 Steady ON: When the Power LED is steady on, the
unit is healthy and sitedata has been received and is correct.
o State 2 80% Duty Cycle: The Power LED is ON for close to
80% of the time and OFF for a brief period. This indicates
either sitedata has not been received or that there is a
problem with site data.
o State 3 50% Duty Cycle: The Power LED blinks ON for 1
Second and OFF for 1 Second. This indicates a health check
has failed and possible hardware problem. For example, the
unit is either not blinking its embedded tag or is not receiving
its embedded tag.
• Tag Reception LED: Blinks when WhereTag signals are received.
• Ethernet LED:Is on solid when has connection to an Ethernet
network.
• WLAN LED:Is on solid when Wi-Fi connection is established.
See Appendix F
: For Complete Boot Sequence details.
___________________________________________________________________________ 15
User’s Guide, WhereLAN III draft D1675 rev F
After the WhereLAN III has completed its boot process, it is possible to
communicate with the unit via the following methods.
____________
Note
____________
Do not attempt to communicate with the WhereLAN III it has completed
the first stage of the boot process (i.e., left LED is solid). Doing so will
stop the boot process. The unit must be reset to clear this condition.
These units are configured using:
• SSH (Secure Shell 2) via Ethernet (preferred)
____________
Note
____________
• WhereWand
• Hyperterminal (or any terminal emulation software) via serial port
SSH is the preferred method of communicating with the WhereLAN III.
Use the HyperTerminal is for initial set-up before being installed on a
network for setting static IP addresses, if DHCP is not used. In addition
to SSH, WhereLAN III also supports Telnet, but this protocol is disabled
by default. To use Telnet, you must first enable it via accessing the
WhereLAN III configuration menu via SSH or a serial port connection.
However, enabling Telnet is not recommended as it sends user name and
passwords across the network in the clear.
The Ethernet Communication Parameters are:
• 10/100 Mb/s
• CAT 5 cable/ RJ-45 plug
___________________________________________________________________________ 16
User’s Guide, WhereLAN III draft D1675 rev F
• 8 data bits, 1 stop bit, no parity, no hardware flow control
HyperTerminal may be used to configure the sensor before connecting it to a
network with a DHCP server, or when a rare fault occurs during the first stage
of the boot process, or if visibility to the boot process is needed for debugging
installation problems.
5.2.1 Establishing an SSH Connection
WhereLAN III supports Secure Shell (SSH), SSH2 being preferred over
SSH1. Either the IP address or host name of the unit must be known in order
to establish an SSH session.
An SSH session may be established using a freely available application called
OpenSSH (supplied by your Zebra Professional Services staff or visit
http://openssh.com for further details, but requires the ssh_zebra_rsa_key
available from Professional Services). Alternatively, other applications, such
as PuTTY, may be used as well, but will require the conversion on the
ssh_zebra_rsa_key into the appropriate format.
To establish the SSH session, you must use Zebra-supplied key, called
“ssh_host_rsa_key” and the “blowfish” passphrase.
The following section shows how to use the OpenSSH application.
___________________________________________________________________________ 17
User’s Guide, WhereLAN III draft D1675 rev F
4. WhereLAN III then presents secure access to its Configuration menu.
5.2.2 Enabling Telnet
The WhereLAN-III comes shipped with Telnet Disabled as added network
security. However for certain installation and/or customers Telnet may be
Enabled via the Menu System.
The enabling of Telnet is done via the numbered menu system either through
HyperTerminal or SHH, either will method will provide the same Menu
structure. The following example is shown using a direct connection with a
Null Modem Serial cable and HyperTerminal Session.
• From the Main Menu select the number that corresponds to ‘Ethernet
Settings’. The WhereLAN III application shows the following submenu:
___________________________________________________________________________ 20
User’s Guide, WhereLAN III draft D1675 rev F
Press the ESC key and enter the “ff2” password when prompted. The unit
will update NVRAM, save your changes, and ask if you wish to reset the unit.
After reset, the unit will boot with Telnet support.
Note Telnet User and Password are as follows.
User: root
Password: password
___________________________________________________________________________ 22
User’s Guide, WhereLAN III draft D1675 rev F
WhereLAN IIIs connect to an IP network over an Ethernet or Wi-Fi interface
using TCP/IP, UDP, and other standard network protocols. For the LOS5000-00AB, both the Location Sensor and the embedded Client Card must be
independently configured with its own unique IP addresses or for DHCP
address assignment. The IP address of each LS must be recorded and entered
into the site configuration file, which contains the configuration information
for each LS, including its location, and MAC address. This is for versions of
VSS prior to the 4.0.5.2 release.
5.3.1 Activating IPv6 Transport
The WhereLAN-III device, running appropriate firmware V5.0.1 or later, will
automatically generate a link-local IPv6 address after booting up. However,
in order to acquire a global IPv6 address, which is needed for IPv6
communication with the VSS server, there must be an IPv6 router on the
network having the following configuration:
• Allow local IPv6 traffic with a global.
• IPv6 network prefix (such as, for example, 2001:470:87c4:1000::/64)
NOTE: The global IPv6 network prefix is a globally unique address and
can be used inside or outside of internal networks. You need to apply for
and obtain a global IPv6 network prefix for your network (for example,
see www.tunnelbroker.net
personnel responsible for the network.
If additionally you would like to assign a fixed IPv4 address to a
WhereLAN-III, you can do so via the sensor menu, which can be accessed
via Telnet (if enabled) or SSH client, or direct connect with serial cable.
). This is a task typically performed by IT
___________________________________________________________________________ 23
User’s Guide, WhereLAN III draft D1675 rev F
In order to have IPv6 network traffic (blinks, status information, etc.) between
the WhereLAN-III devices and the VSS server, the following requirements
must be fulfilled:
• The WhereLAN-III device must be able to acquire a global IPv6
address as described above.
• IPv6 must be enabled in the operating system (Windows) on the VSS
server.
• The following steps must be followed in System Builder, which is the
tool that generates the sitedata.dat configuration file parsed by the VSS
services and the WhereLAN-III devices:
• Activate IPv6 in the ‘Change Site Attributes’ dialog window and enter the
global IPv6 network prefix that the IPv6 router on that network is using:
___________________________________________________________________________ 25
User’s Guide, WhereLAN III draft D1675 rev F
The resulting sitedata.dat generated by System Builder will include the following:
o A site define ipv6prefix specifying the global IPv6 network prefix used by
the IPv6 router on that network
o 0 (zero) IP address for all WhereLAN-III units that will communicate using IPv6
An example sitedata.dat is shown in the screenshot below:
NOTE: As usual, you need to restart the VSS services on the VSS server for
changes in sitedata.dat to take effect. Some changes require rebooting the
WhereLAN-III devices as well.
___________________________________________________________________________ 27
User’s Guide, WhereLAN III draft D1675 rev F
Once IPv6 transport between the VSS server and the WhereLAN-III devices
has been activated as described above, you can use the VSS diagnostics and
status tools as usual, but you will notice that the IPv6 address is used for
devices configured with the IPv6 option in System builder, as shown in the
Sensor Analyzer screenshot below:
___________________________________________________________________________ 28
User’s Guide, WhereLAN III draft D1675 rev F
5.3.3 IPv4 DHCP Dynamic IP for WhreLAN-III Devices
It is possible to have a WhereLAN-III device automatically acquire an IPv4
address from a DHCP server. This IP assignment is dynamic and therefore the
assigned IP may change the next time the device is rebooted. To enable the
device to do so, the following steps are required:
o The DHCP option in the sensor menu needs to be turned ON:
o On the DHCP server, add scope option 151 (IP Address type) and point it to the IP
address of the VSS server:
___________________________________________________________________________ 29
User’s Guide, WhereLAN III draft D1675 rev F
5.3.4 SNMP and DNS Support in WHERELAN-III Devices
The WhereLAN-III firmware version 5.0.1 includes support for the SNMP
and DNS network protocols. The ‘Ethernet Settings’ menu in the sensor menu
includes menus to enable and configure these protocols, as shown in the
screenshots below:
___________________________________________________________________________ 31
User’s Guide, WhereLAN III draft D1675 rev F
The WhereLAN-III MAC address is not directly compatible for replacing a
WhereLAN-II at an existing site that is running a version of VSS prior to
4.0.5.2, and WhereWAND’s that are running software that is from VSS prior
to 4.0.5.2.
Location Sensors use 4 unique embedded tags id’s, for Timing and Health.
These 4 unique embedded tag Id’s correspond to the Rf Transmit and TIC
ports (1, 2, and 3). The upper 32 bits of these four tag-ID’s MATCH bits 31
down to 2 of the unit’s MAC address. For this reason MAC addresses of
Location Sensor with, WhereLAN-II or WhereLAN-III, skip in a modulus of
4.
• For Example: In a WhereLAN-2 a MAC address might look like
0004F1AAA120, then the next MAC address of a WhereLAN-2,
in sequence, would be 0004F1AAA124.
• So this means for a WhereLAN-2 that there MAC address will
always end in either a 0, 4, 8, or C.
• For the above Example: Embedded tags for 0004F1AAA120:
WhereLAN-III MAC addresses now ends in either 2, 6, A, and E. This new
MAC scheme allows more efficient use of the MAC space defined for this
product and easy recognition by users and the system in identify a unit as a
WhereLan-III or II by just looking at its MAC.
• However the embedded tags still follow the format of the WhereLAN-
II, meaning they MATCH bits 31 down to 2 of the unit’s MAC address
in order of RF Tag thru wired time ports.
• Older versions of the WhereWand FW assume that the lower 32-bits
MATCH between the MAC and the RF tag-ID. To fit WhereLan-III
into the MAC space it is now that sensors MATCH bits 31 down to 2.
• The embedded tags not matching the MAC address is causing issues,
because the WhereWAND uses the Rf embedded tag id to
communicate with the Location sensor.
The differences described above cause three main issues with the WhereLANIII MAC address and running an older version of VSS prior to VSS 4.0.5.2,
cause.
1. The Blink Service auto-generates a list of expected/known system
embedded tags based on the MAC address in SiteData. Entering the
MAC as listed on the unit, a legacy BlinkService will not generate a
proper list of embedded reference tags, and the Time Service will not
receive the embedded tag blinks it needs from the WhereLAN-III.
2. iSensor validates the MAC addresses in sitedata.dat match the MAC of
the Location sensors. With legacy iSensor, this causes red-lights on
the health and status display.
3. The WhereWAND’s download of the site configuration contain the
MAC addresses of each Location Sensor. The WhereWAND must use
the Rf embedded tag Id to communicate with the location sensor and
legacy WhereWand FW calculates the tag-ID incorrectly, resulting in
no-response from the specific sensor.
___________________________________________________________________________ 33
User’s Guide, WhereLAN III draft D1675 rev F
1. The best is to have the customer site upgrade to VSS 4.0.5.2 or later,
which has the tools and system builder that take care of the issues
directly.
2. The next best is to see if the customer will allow new tools to be
loaded onto their system, if they require an approval time for full VSS.
The tools will be the System Builder and iSensor from the VSS 4.0.5.2
release. This will work with legacy version of VSS.
a. With this the MAC of the WhereLAN-III can be entered
accurately (as it is shown on the WHERELAN-III label) into
system builder, in the Location Sensor, WLN3 of the tree view.
Under the ‘Site Attributes’ tab, make sure the 4.0.5.2 VSS
Compatibility box is unchecked for legacy VSS systems. This
will save and publish the sitedata.dat in the correct form.
___________________________________________________________________________ 34
User’s Guide, WhereLAN III draft D1675 rev F
This will allow the WhereLAN-III’s to function in the Blink Service and have
the Time Service looking for the correct embedded tag Id’s. However with
legacy iSensor this will still display the unit as Red in Health and Status, for
the MAC mismatch. To fix the health indicator, you can consider just
replacing the iSensor executable with the one from VSS 4.0.5.2.
____________
Note
____________
Failure to configure the WhereLAN III prior to operation may result in
an inoperative unit. Ethernet connected units installed on an operational
and reliable network with DHCP IP address assignment may be
configured post installation. All Wi-Fi connected units must be
configured with the appropriate Wi-Fi network parameters before
installation.
___________________________________________________________________________ 35
User’s Guide, WhereLAN III draft D1675 rev F
Each WhereLAN III is shipped with a label set containing one label (Figure 2)
with the bar coded MAC address of the unit and its Wi-Fi client (as
applicable) and three labels with the last six characters of the Location
Sensor’s MAC address in large type. Ensure that the label is correct by
matching the MAC address(es) on the loose label set with the MAC
address(es) listed on the back of the unit. Place the loose bar code label in the
site design document where indicated, and place one or more of the large type,
six character labels on the exterior of the Location Sensor in positions that are
visible after installation.
____________
Note
The MAC address label must be clearly marked on the exterior of the
Location Sensor housing in a position visible after installation.
____________
Last 6 LS
MAC digits
Location Sensor
Serial Number
Wi-Fi Client
MAC Address
Location Sensor
`
MAC Address
Figure 2 Example of LOS-5000-00AB Label
___________________________________________________________________________ 36
User’s Guide, WhereLAN III draft D1675 rev F
While there is no restriction to the IP address, it must match the address in the
Site file for that particular WhereLAN III. The IP address(es) can be static
assigned, or dynamically assigned via DHCP. If assigned through DHCP, the
DHCP server must contain the MAC address and corresponding IP address for
each of the Location Sensors (and Wi-Fi Client).
____________
Note
For networks utilizing DHCP, the IP address or host name of the site’s
RTLS server must be entered in the DHCP server. See the VSS User
Guide for more details on Network Autoconfig.
____________
To configure the IP address of the Location Sensor:
Note the following configuration examples are done thru HyperTerminal.
• Connect to the Location Sensor using SSH, or HyperTerminal.
• Select the number that corresponds to ‘Ethernet Settings”1 and
confirm the unique MAC address for the Location Sensor.
___________________________________________________________________________ 37
User’s Guide, WhereLAN III draft D1675 rev F
The Wi-Fi client card embedded in the WhereLAN III must be configured
with the proper IP address or for DHCP set and the Interface must be ON. In
addition, the Wi-Fi network parameters, such as the SSID, and authentication
and encryption methods, must be configured in the wpa_supplicant, (See
sections 5.4.2 Configuring the Wi-Fi Network Parameters and 5.4.3
WPA_Supplicant Cautions)
From the Main Menu:
• Select Ethernet Settings.
• Under Ethernet Menu select 3 WLAN.
• Set 1. Interface to ON, then IP/DHCP settings.
___________________________________________________________________________ 39
User’s Guide, WhereLAN III draft D1675 rev F
• Save the configuration changes by using ESC key entering the
password “ff2”.
• Select either ‘yes’ or ‘no’ at this point, depending on if further
configuration needs to take place.. (A reset/reboot will be required thought for all the changes to take effect.)
Note: Although the LOS-5000-00AB has two network interfaces (its Ethernet
and Wi-Fi ports) in the vast majority of cases, only its Wi-Fi port is actually
connected to an operational network. If enabled, the Ethernet port must be
configured to be on a different subnet than the Wi-Fi port. In this case, it is
recommended that a non-routable IP address be used such as
192.168.5.0/255.255.255.0, to enable local diagnostics via the Ethernet port.
5.4.1 Setting Wi-Fi Antenna Type
The Wi-Fi antenna setting is available in firmware versions V5.0.2 or later
(Build Date Apr 30 2012 or later). The antenna selection is set under
802.11Client Menu, which is reached from the Main Menu via the
Diagnostics Menu. There are currently three antenna choices to select from,
and these match the Wi-Fi antennas that are offered on the marketing price
list. The selection is entered under the “Select Antenna” menu item.
From the Main Menu, select Diagnostics, and from the Diagnostics Menu select
802.11 Client. Then, in the 802.11 Client Menu, select the number that
corresponds to “Select Antenna”, and enter the value that corresponds to the
antenna that will be attached to the WhereLAN-III.
Escape “ESC” to save selection, ‘ff2’ is the password. The unit will need to be
rebooted for the setting to take effect.
5.4.2 Configuring the Wi-Fi Network Parameters
All the Wi-Fi network parameters are under the control of a file called
wpa_supplicant.conf. In order to configure the WhereLAN III Wi-Fi client
card to access your network, you must first edit or create this file to match
your Wi-Fi network configuration and then upload the file onto the
WhereLAN III unit. The wpa_supplicant.conf file must be created or edited
with a Linux friendly text editor. Do not use Notepad or similar. A popular
free Linux editor is called VIM and is found at http://vim.sourceforge.net/.
___________________________________________________________________________ 41
User’s Guide, WhereLAN III draft D1675 rev F
Create your wpa_supplicant.conf file with your Linux-friendly editor and
place a copy of it on the RTLS Server’s ftproot directory. Placing the file in
this directory facilitates the upload process.
Uploading the wpa_supplicant.conf file onto the WhereLAN III Unit.
5.4.3 WPA_Supplicant Cautions
___________________________________________________________________________ 42
User’s Guide, WhereLAN III draft D1675 rev F
Important: The wpa_supplicant file, which controls security of the wireless
client card, is currently over written when upgrading the firmware on a
WhereLAN-III.
• Over writing the wpa_supplicant file can lead to loss of network
connection if the WhereLAN-III is wirelessly connected to the
network.
• Once upgraded the wpa_supplicant file will revert to its original
configuration.
• Recovery WILL require direct connection to the unit.
Solution: The issue of over writing the wpa_supplicant file can be avoided by
editing the WhereLAN-III ‘upgrade.txt’ script file that is distributed with the
WhereLAN-III firmware files. The files will be located in a directory under the
/inetpub/ftproot/server\G3v501.
• The script file is the first to be read by the WhereLan-III and is
subsequently used by the WhereLan-III to control which of the four
firmware files (bootloader.bin, uImage, rootfilesys, and JFFS2) are to
be uploaded to the WhereLan-III during the upgrade process.
• The wpa_suplicant.conf file is stored within the JFFS2 image. When
JFFS2 is upgraded, the site specific wpa_suplicant.conf file is replaced
with the default found in the released JFFS2 image.
• Modifications to the upgrade.txt script file are supported to enable the
WhereLan-III to temporarily save the site specifc wpa_supplicant.conf
file and restore it after the upgrade of JFFS2 completes.
• The necessary command line for saving and restoring the
wpa_suplicant.conf file is present in the upgrade.txt script, but is
commented out and therefore causes no effect.
• Modifying the wpa_supplicant.conf file can be done by removing the
“#” (indicator for a comment line)from in front of the
F1=”wpa_supplicant/conf” line.
o Note ‘#’ is the script’s language for indicating the line is a
comment and contains no instructions. Removing the ‘#’
causes the script to execute the instruction on that line.
o The upgrade.txt file must be edited with a Linux friendly text
editor. Do not use Notepad or similar as it WILL corrupt the
___________________________________________________________________________ 43
User’s Guide, WhereLAN III draft D1675 rev F
file. A popular free Linux editor is called VIM and is found at
http://vim.sourceforge.net/ .
Example excerpt from a default upgrade.txt script file:
###############################################################
# List JFFS2 files and/or directories (F0-FN, N<10) to be restored
###############################################################
#F0="wpa_supplicant.conf_reference"
#F1="wpa_supplicant.conf"
Modified example excerpt from a default upgrade.txt script file to cause the
wpa_supplicant.conf file to be save d and later restored:
###############################################################
# List JFFS2 files and/or directories (F0-FN, N<10) to be restored
###############################################################
#F0="wpa_supplicant.conf_reference"
F1="wpa_supplicant.conf"
NOTE the removed “#” (from the fourth line) in front of the F1 as shown above.
Engineering is in planning on how to deliver a standard set of firmware files and
scripts that may default to automatic save/restore.
5.5 WPA Supplicant Upload
The following instructions will demonstrate on how to upload a
wpa_supplicant.conf file to the WhereLAN-III.
From the Main Menu, select the number that corresponds to ‘Firmware
Upgrade’.
___________________________________________________________________________ 44
User’s Guide, WhereLAN III draft D1675 rev F
Now Select the ‘Transfer Protocol’ (either TFTP default, FTP, or NFS) and set
the ‘Server IP Address’ of the server where the files are locate. Ensure the
tftp and/or ftp service is enabled on the computer that contains the
wpa_supplicant.conf file.
Now, select the item number that corresponds to ‘Advanced’, and enter the ff2
password. The WhereLAN II present the following menu.
___________________________________________________________________________ 45
User’s Guide, WhereLAN III draft D1675 rev F
• Now, select 7, ‘Get remote file’. The WhereLAN III asks for the path
to the remote file. As you have placed the file in the server’s root
directly, simply enter ‘wpa_supplicant.conf’.
• Now, the WhereLAN III asks for a local path, i.e., where the file
should be placed in the WhereLAN III itself. Enter
‘/mnt/jffs2/wpa_supplicant.conf’. Be sure to enter the path and file
names correctly, as an error here will prevent normal Wi-Fi operations.
WhereLAN III asks you to confirm before the file is uploaded. Accept
by entering y. When the operation completes, your screen should
look like this.
• Now, that the wpa_supplicant.conf file has been uploaded, you must
enable wpa_supplicant processing on the WhereLAN III itself.
___________________________________________________________________________ 47
User’s Guide, WhereLAN III draft D1675 rev F
Read Installation and Instruction sheet included with the Location Sensor as
well as all Safety and Installation Warnings/Cautions before installing. Follow
the Site Design document for installed location.
6.1 Safety and Installation Warnings and Cautions
Warning - Warning - Electrical Shock: A protective earthing
conductor with green and yellow insulation, minimum of 18 AWG, shall be
installed to the protective earthing terminal of the metal enclosure when I/O or
power cables are routed outdoors. National electrical codes shall be followed
to install facility protective earthing conductor to the protective earthing
terminal.
Earth Ground Locations.
Bolt Size 8mm. Max
Length 25mm.
Figure 3 Safety and
Warnings
Warning - Electrical Shock: No operator serviceable parts inside. Refer
servicing to qualified personnel. To prevent electrical shock, do not remove
covers.
Caution - The Location Sensor hardware must be installed by a qualified
service technician
Caution - Use of Zebra external power supply is limited to indoor use
and a max 40° C environment. Only use Zebra approved power supplies.
Caution - The Timing Sync cable use is limited to indoor only.
___________________________________________________________________________ 50
User’s Guide, WhereLAN III draft D1675 rev F
The site design specifies the location of the Location Sensor(s) to provide
optimum system performance. It is critical that the Location Sensor is
mounted in a position which provides good RF visibility to the tracked assets.
Thus the Location Sensor must be mounted exactly in the position specified in
the site design document
The Location Sensor has two methods of mounting .The first can be hung
using nut pocket on top for attachment to accept a 3/8 in (10 mm) threaded
rod and jam nut, useful when using a beam clamp type of hanger. The second
method of mounting is a pole mount hardware kit is available separately, ZES
Part Number RM-510-00 Mounting Bracket, Pole Mount.
____________
Note
Nut Pocket
Safety Lanyard Points
Mounting Bracket Points
Figure 4 Mounting Points
Failure to mount the Location Sensor in the exact position specified in the
site design will result in erroneous or non-locates of the tracked assets.
___________________________________________________________________________ 51
User’s Guide, WhereLAN III draft D1675 rev F
For safety it is strongly recommend that a Safety Lanyard be employed with
either mounting method. The Safety Lanyard points are large enough to
accept a 3/16” loop style wire rope. Stainless Steel Rope is recommended.
____________
Figure 5 Safety Lanyard
___________________________________________________________________________ 52
User’s Guide, WhereLAN III draft D1675 rev F
The Location Sensor can be hung via a 3/8 inch (10 mm) threaded rod per the
following instructions. This type of mounting is intended for indoor
installations only, if mounting outdoors use the Pole Mount Kit described in
Sections 6.4. The required supports, threaded rod, nuts, etc., are not included.
• Cut the threaded rod to the desired length and install it directly above
the desired Location Sensor position.
• Thread one nut up 2 in (50 mm) from the bottom of the threaded rod,
with Lock Washer and Washer.
• Place the second nut onto threaded rod, flush with the end of the
threaded rod and install the Location Sensor.
• Tighten the upper nut down on top of the Location Sensor housing.
Figure 6 Threaded-Rod
___________________________________________________________________________ 53
User’s Guide, WhereLAN III draft D1675 rev F
For Location Sensor installation using the Threaded Rod Mounting, it must
also be secured to the building infrastructure with a safety lanyard through the
one of the rectangular loops on top the casting. See below in Figure 7 Safety
Lanyard.
Figure 7 Safety Lanyard
___________________________________________________________________________ 54
User’s Guide, WhereLAN III draft D1675 rev F
The pole mount kit, catalog number RM-510-00, must be ordered separately.
The pole mount kit will allow the Location Sensor to be mounted to either a
pole or 1-1/4” metal channel framing, per the instructions included with the
pole mount kit.
Top of Bracket
Figure 8 Pole
Mount Kit
___________________________________________________________________________ 55
User’s Guide, WhereLAN III draft D1675 rev F
First mount bracket to metal frame in location, orientation and height
specified in the site design, with support hooks up and retaining slots down,
using supplied clamp.
Figure 9 Bracket Mount
___________________________________________________________________________ 56
User’s Guide, WhereLAN III draft D1675 rev F
Hang the Location Sensor on the bracket and tighten retaining blots securely.
Next install safety lanyard through one of the Location Sensor’s lanyard
points, and the other end of the lanyard to a point above the Location Sensor.
Figure 11 Location Sensor Mounted
___________________________________________________________________________ 58
User’s Guide, WhereLAN III draft D1675 rev F
First mount bracket to Pole at height location, orientation and height specified
in the site design, with support hooks up and retaining slots down, using
supplied clamp.
Figure 12 Pole mount on Pole
Loosen the retaining bolts on each side of the Location Sensor, but do not
remove them (See Figure 10 Retaining Bolts).
___________________________________________________________________________ 59
User’s Guide, WhereLAN III draft D1675 rev F
Hang the Location Sensor on the bracket and tighten retaining blots securely.
Next install safety lanyard through one of the Location Sensor’s lanyard
points, and the other end of the lanyard to a point above the Location Sensor.
Figure 13 Location Sensor on Pole
___________________________________________________________________________ 60
User’s Guide, WhereLAN III draft D1675 rev F
As its name suggests, the All Weather Omni provides omni-directional
coverage and is suitable for outdoor environments. It should be attached
directly to the Location Sensor housing, and therefore requires no additional
mounting. For this reason, it is the preferred antenna for the Location Sensor.
Because it is an omni-directional antenna, the coverage pattern of the All
Weather Omni can be degraded if mounted too close to metallic structures.
Therefore, the All Weather Omni must be mounted a minimum 12 inches (305
mm) from nearby metallic structures.
_____________
_____________
Min 12 inches
IBeam
(305 mm) from
metal wall
Left
antenna
Figure 16 Minimum clearance to metallic structures
The All Weather (and Indoor Office) Omni antennas must be mounted a
minimum of 12 inches (305 mm) away from metal walls.
Right
antenna
___________________________________________________________________________ 62
User’s Guide, WhereLAN III draft D1675 rev F
For best diversity reception, the Location Sensor should be mounted in an
orientation in which the antennas are at a diagonal (45 deg) orientation with
respect to surrounding walls and aisles. The RM-250 Wall Mount Bracket
can be utilized to provide the necessary clearance from nearby metallic
surfaces.
Wall
Mount
Bracket
Location
Sensor
Min 12 inches
(305 mm) from
metal wall
Right
Antenna
Left
Antenna
Figure 17 Corner mount industrial application
___________________________________________________________________________ 63
User’s Guide, WhereLAN III draft D1675 rev F
The indoor omni is designed to be mounted directly to the ceiling. It has a
small profile designed to be unobtrusive in an office environment. Like the
All Weather Omni antenna, it must be mounted a minimum of 12 inches from
metal walls. There is no spacing requirement for drywall or other nonmetallic walls. For best diversity reception, mount the antennas in a diagonal
orientation 24 in (610 mm) from each other, in the center of the corridor (if
applicable), as shown in Figure 18 below. Be certain to note which antenna is
on the left, and which is on the right, and connect them to the appropriate
ports on the Location Sensor during installation.
M
17 in
(432 mm)
24 in
(610 mm)
Figure 18 Office omnidirectional in corridor
(305 mm) clearance
to metalwalls
Ceiling tile
Diagonal orientation
of antennas
___________________________________________________________________________ 64
User’s Guide, WhereLAN III draft D1675 rev F
Outdoor installations requiring the maximum location accuracy and
consistency should use vertical and horizontal diversity for antenna placement
should be implemented. This applies to most Yard and Marine Terminal
Sites. Zebra offers three different vertical diversity cable kits for installation.
For all installations, it is recommended that the Right antenna be higher than
the Left Antenna. Consult instruction sheet included in each kit and
____________
____________
WhereLAN III Installation Guide D1677 for further installation information.
1) Antenna Extension Cable Kit,
CBL-010-10
, which is a 5ft cable kit is
typically used for Yard Sites.
2) Antenna Extension Cable Kit, CBL-015-10 a 15ft. standard cable kit is
used for Marine Terminals.
3) Cable Kit CBL-015-11, Low Loss Antenna Extension, Location Sensor,
15ft may be used for Marine Terminals.
The most critical item in placing and installing the Location Sensors is to
ensure that the antennas are not blocked by nearby structures. Detailed
instructions with several examples are provided in the Location Sensor
Placement Guide D0406.
For accurate locate performance, the position of the left and right antennas
must be individually specified in the site design. System Builder requires the
center point and orientation of the antennas.
The left and right antenna must be correctly oriented per the site design.
Inadvertently reversing the left and right antennas results in a two foot
location error in standard diversity configurations and greater error in
vertical diversity configurations.
___________________________________________________________________________ 65
User’s Guide, WhereLAN III draft D1675 rev F
Below is a picture of a ZES Location Sensor installed on a 100’ light pole.
Note the Vertical Diversity (“VD”) created by extended antennas above and
below the Location Sensor. The installer will have to achieve at a minimum
the vertical distance of 11’ see below, the VD can be greater than 11’. This
installation calls for 12’ of diversity. The picture shows ¾” electrical
metallic tubing extending the “bullhorn” antennas (white).
Figure 20 Vertical Diversity +11ft.
___________________________________________________________________________ 67
User’s Guide, WhereLAN III draft D1675 rev F
Make appropriate connection to the Location Sensor, as shown below.
Figure 21 Vertical Diversity Connections
7.3 Wi-Fi 802.11 b/g Antennas
There are three antenna options for Wi-Fi network connectivity of the for the
LOS-5000-01AB.In addition, the CBK-020-00 allows you to connect to the
smb Wi-Fi port aon the unit and must always be separately procured. See
instruction sheet included with cable mounting bracket kit regarding
installation. See Site Design for specifics of WLAN antenna choice and
orientation.
• Wi-Fi Antenna Indoor 2.2dBi
• Wi-Fi Antenna Outdoor Omni
5.2dBi
• Wi-Fi Antenna Outdoor
AK-170-00
AK-151-00
AK-153-00
Directional 13.5dBi
___________________________________________________________________________ 68
User’s Guide, WhereLAN III draft D1675 rev F
The figure below, labels the appropriate connections which must be made to
the Location Sensor in normal operation. The connector types and
recommended cable types are detailed in Section 3.
Figure 22 Location Sensor Connections
For all Outdoor installations:
•Use part GS-888-00 grease (supplied with unit) in ALL Connecter
Jacks. Fill each of the following connections, with Nyogel Weather
Sealant, these include the Left and Right antenna, Timing connections,
Wi-Fi Client, Ethernet, Serial interface, and Power connection. This is
to help weather proof the connections from water and corrosion.
• Routing the cables through the Drip Plug, supplied with unit, plug
cables into units and fully (carefully) fully install Drip Plug into
connector well.
Figure 23 Drip Plug
___________________________________________________________________________ 69
User’s Guide, WhereLAN III draft D1675 rev F
The WhereLAN III location sensor can be powered via IEEE 802.3af POE or
directly with a standalone DC power supply.
If the standalone DC power supply is option is used, the customer must
provide 100-240 VAC 50/60 Hz power to the specified Location Sensor
position. The Location Sensor units require DC 36-57V, 250mA for operation
(12 Watts). The recommended power supply (PS-040-00), which must be
purchased separately, has a 6 ft (2 m) AC cable and a 6 ft (2 m) dc cable. For
longer cabling runs, the recommended power supply is the PS-045-00. The
electrician should verify that the AC power is available within 2 m of the
position of the power supply. The Location Sensor itself may be installed up
to 20 m and 100 m from the PS-040-00 and PS-045-00 power supplies,
respectively. . This allows a 6 ft (2 m) “service loop” margin if the Location
Sensor position must be readjusted after the AC power is installed.
_____________
_____________
The WhereLAN III must always be used with the specified power supply.
The use of a different power supply could result in equipment damage
and/or electric shock or fire hazard.
Two optional 50 ft (15 m) dc power extension cables are available for
installations in which it is not desirable to rout the AC power within 6 ft (2 m)
of the WhereLAN III. One is for indoor use only and is Plenum Rated, ZES
Part Number PX-010-00. The other is an outdoor rated (UV stable), ZES
Part Number PX-050-00. Consult your ZES Account Manager for
recommended wire size if additional lengths are required for a particular
installation.
_____________
Power Supplies have a limited safe operating temperature rating, please
check with the account representative concerning limitations or
availability of extend temperature range power supply, such as PS-040-
_____________
00. In outdoor installations the power supply must be installed within a
suitable waterproof housing per applicable building codes. The use of a
non qualified housing could result in equipment damage and/or electric
shock or fire hazard.
___________________________________________________________________________ 70
User’s Guide, WhereLAN III draft D1675 rev F
The WhereLAN III utilizes standard 10/100 802.3 Ethernet connectivity via
cat 5 cables. The Location Sensor must be wired to a nearby hub, which is in
turn connected to the network containing the database CPU. The maximum
Ethernet cable run is 328 ft (100 m). If additional distance is required, hubs,
repeaters, and fiber (with 10/100BaseT converters) can be used to extend the
distance. Refer to IEEE guidelines for Ethernet cabling.
____________
Do not exceed the maximum Ethernet cabling length of 328 ft (100 m).
____________
8.2 Wi-Fi Antenna Kit
The LOS-5000-00AB WhereLAN-III with Wi-Fi has the option of adding on
an antenna cable and mounting bracket kit CBK-020-00. This kit is intended
to work with any of the three Wi-Fi antenna Accessories.
The kit consist of the mounting bracket, 4 screws, and the SMB to RP-TNC
cable.
Figure 24 CBK-020-00
___________________________________________________________________________ 71
User’s Guide, WhereLAN III draft D1675 rev F
3. Now install the Wi-Fi cable bracket on the rear side of the unit, as
shown below, using the supplied hardware. The hinged portion of the
clamp should be facing the front of the unit. Recommended torque for
mounting screws is 6 in-lbs (0.68Nm).
Mounting Holes
Wi-Fi
Figure 27 Wi-Fi Bracket
___________________________________________________________________________ 74
User’s Guide, WhereLAN III draft D1675 rev F
4. Installing the Wi-Fi antenna.
a. Option 1 for the AK-170-00 2.2dBi Dipole Antenna (Rubber
Duck Style). Slide the antenna, with the antenna straight,
through the Wi-Fi bracket and tighten onto the RP-TNC
connector. Recommend 12 to 15 in-lbs of torque (1.4 to 1.7
Nm).
Figure 28 2.2 dBi Dipole
Then slip the knurled part of the antenna connector back into the Wi-Fi
Bracket clamp, and tighten the retaining screw to 2 in-lbs (0.23Nm).
Then articulate the antenna downward.
Knurled Sectio
Retaining Screw
Figure 29 2.2 dBi Installed.
___________________________________________________________________________ 75
User’s Guide, WhereLAN III draft D1675 rev F
b. Option 2 is for either the AK-151-00 Cisco 5.2dBi Omni or the
AK-153-00 Cisco 13.5 dBi Yagi antenna. These are both
remotely mounted antenna. Slide the antenna connector
through the Wi-Fi Bracket Clamp and tighten onto the RPTNC connector. Recommend 12 to 15 in-lbs of torque (1.4 to
1.7 Nm).
Knurled Sectio
Figure 30 Wi-Fi Bracket Remote Antenna
Then slip the knurled part of the antenna connector back into the Wi-Fi
Bracket clamp, and tighten the retaining screw to 2 in-lbs (0.23Nm).
Mount the antenna according to the recommend instructions provided
with the antenna and in the site design document.
Retaining Screw
Figure 31 Remote Antenna Clamp
Note: For all outdoor installations use the connector grease supplied with
the unit for this connection.
___________________________________________________________________________ 76
User’s Guide, WhereLAN III draft D1675 rev F
In certain cases, the WhereLAN III may require a timing cable to be
connected to other nearby WhereLAN III units. In general, the use such wired
timing links should not be necessary with a good site design, but may be
necessary in select cases. The site design document, provided by the site
designer, will specify which Location Sensors will be connected together.
Each of the three timing ports on the Location Sensor is an identical bidirectional link. The cable and connector types are specified in section 4
above.
The following rules must be applied when connecting timing cables between
the Location Sensors:
____________
Note
____________
____________
Note
____________
• Do not connect the timing cable from one Location Sensor back to the
same Location Sensor.
• Do not connect two timing cables between the same two Location
Sensors.
• The maximum timing cable length is 1000 feet (305 m).
Do not exceed the maximum timing cabling length of 1000 ft (305 m).
Install the Location Sensor timing cables from one unit to the next, as
specified in the site design document, using the specified 2 pair or 4 pair*
cable and RJ22 (telephone handset 4c4p) connectors. (* see 8.2.1). Incorrect
routing of the timing cables between the Location Sensors may result in
decreased location accuracy.
___________________________________________________________________________ 77
User’s Guide, WhereLAN III draft D1675 rev F
The timing cables must be properly wired in order for the timing signal to be
transmitted from one Location Sensor to the other. It is recommended that
this test be completed on each cable by the installer prior to operation. This
test requires quantity 2 four pair to two pair connector adapters ZES p/n
21204, and a Fluke 620 CableMeter. Brief instructions are provided below;
consult the Fluke CableMeter instruction manual for detailed instructions.
Setup
Connect adapter #1 between the Fluke 620 CableMeter and the near end of the
cable to be tested. Connect the Fluke Cable ID unit and adapter #2 to the far
end of the cable to be tested using a RJ-45 coupler.
2 pair adapters
Cable
under test
Figure 38 Test setup for CAT5 cable
using Fluke 620
___________________________________________________________________________ 82
User’s Guide, WhereLAN III draft D1675 rev F
Use the SETUP to select cable type, wire standard, category and wire size on
the Fluke CableMeter:
• Cable: UTR
• Wiring: 10BaseT 2PR
• Category: Cat5
• Wire Size: AWG24
Turn the Fluke CableMeter rotary switch to WIRE MAP. The correct readout
when testing 2 pair cable is shown in Figure 39 below. If a different readout
appears, the cable was not constructed properly and must be corrected.
12 36 ID
12 36 #1
Figure 39 Correct readout when testing 2 pair cable.
___________________________________________________________________________ 83
User’s Guide, WhereLAN III draft D1675 rev F
Prior to optimizing locate performance, the operation of the Location Sensor
must be verified. The checklist below specifies the verification of the
configuration and basic operation.
Location Sensor
ower/
ealth
Tag
Reception
WLAN
Ethernet
Outdoor
Omni
Antenna
Figure 40 Location Sensor LED indicators
Verify that each Location Sensor is operational by verifying that the
left Power/ Health LED is illuminated solid red.
For wired 802.3 Location Sensors, verify that the Ethernet LED is
solid red when connected and blinking red when activity is present.
Verify that the RX detects LED is blinking red indicating reception of
tag blinks.
For wireless LOS-5000-00AB Location Sensors, verify that the
WLAN activity LED is blinking red during power up state and solid
red otherwise.
Confirm that the site Location Sensor channel assignment is correct by
running “display locate” from the Blink Console under the Blink
Service Diag window, with a tag placed directly under each LS.
Verify that the nearest Location Sensor, as indicated by a “0” in the
display locate report, is that Location Sensor nearest the tag.
___________________________________________________________________________ 84
User’s Guide, WhereLAN III draft D1675 rev F
Verify that detects are received by the Location Sensor using Blink
Consoles when, a tag is placed at a distance from each Location
Antenna equivalent to the maximum required range from that Location
Antenna. Typical tag to Location Antenna range is 1000 ft (305 m)
(Unobstructed/ outdoor), 350 ft (107 m) Minimally Obstructed (indoor
office/ light commercial), 250 feet (76 m) Significantly Obstructed
(heavy industrial).
Section Signoff
Initial Date Comments/ Exceptions
Note See Blink Console User’s Guide.
___________________________________________________________________________ 85
User’s Guide, WhereLAN III draft D1675 rev F
This device complies with FCC Part 15.247.
Operation is subject to the following two conditions:
(1) This device may not cause harmful interference
(2) This device must accept any interference which may cause undesired operation
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 equipment is
operated in a commercial environment. This equipment generates, uses, and can radiate
radio frequency energy and, if not installed and used in accordance with the instruction
manual, may cause harmful interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful interference in which case the
user will be required to correct the interference at his own expense.
RF Notice
Any changes or modifications to equipment not expressly approved by Zebra
Technologies Corporation could void the user’s authority to operate the equipment.
FCC Radiation Exposure Statement
This equipment complies with FCC radiation exposure limits set forth for an
uncontrolled environment. This equipment should be installed and operated with
minimum distance 20cm between the radiator and your body. This transmitter must not
be co-located or operating in conjunction with any other antenna or transmitter.
Industry Canada Compliance Statements
Operation is subject to the following two conditions: (1) this device may not cause
interference, and (2) this device must accept any interference, including interference
that may cause undesired operation of the device.
Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils
radio exempts de licence. L'exploitation est autorisée aux deux conditions suivantes :
(1) l'appareil nedoit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit
accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en
compromettre le fonctionnement.
___________________________________________________________________________ 86
User’s Guide, WhereLAN III draft D1675 rev F
This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.
This device and its antenna(s) must not be co-located or operating in conjunction with
any other antenna or transmitter.
Cet appareil et son antenne (s) ne doit pas être co-localisés ou fonctionnant en
conjonction avec une autre antenne ou transmetteur.
This equipment should be installed and operated with a minimum distance of 20cm
between the radiator and your body
Cet équipement doit être installé et utilisé à une distance minimale de 20cm entre le
radiateur et votre corps.
It is the responsibility of the installer to ensure that when using the outdoor antenna
kits, only those antennas certified with the product are used. The use of any antenna
other than those certified with the product is expressly forbidden by FCC rules 47 CFR
part 15.204 and IC RSS standards.
Il est de la responsabilité de l'installateur de s'assurer que lorsque vous utilisez les kits
d'antennes extérieures, seules les antennes certifiés avec le produit sont utilisés.
L'utilisation d'une antenne autre que ceux qui sont certifiés avec le produit est
expressément interdite par la réglementation FCC partie 47 CFR 15.204 et IC normes
RSS.
___________________________________________________________________________ 87
User’s Guide, WhereLAN III draft D1675 rev F
The WhereLAN-III’s firmware can be upgraded manually without the use of
iSensor or similar tool set. The upgrade can take place through the Menu
system on the WhereLAN-III, and a network connection supporting either
FTP or TFTP must be present. The following examples are done using an SSH
connection. However any of the way to get to the WhereLAN-III Menu
system is valid. All the same generation location sensors on site must have
same Firmware Build Date. (All WhereLAN-III’s must have same WhereLAN-III firmware and all WhereLAN-2’s must have same WhereLAN-2 firmware).
Note the upgrade files must be placed in the ftp root directory on the
server machine. (Files: initrd.boot, jffs2_ls.img, u-boot.bin, uImage_ls,
and upgrade.txt)
Figure 41 Ftproot Directory
With the release of VSS 4.0.5.2, the firmware files for the WhereLAN-III
will be included now as a standard part of VSS. The files will be under
the / inetpub\ftproot\WhereNet\Server\G3v501 directory.
___________________________________________________________________________ 93
User’s Guide, WhereLAN III draft D1675 rev F
3. Now select the number that corresponds to ‘Upgrade’, and type
‘upgrade.txt’ at the prompt (enter/return) if files are located directly under
the ftproot directory (See Reference 1below). (OR) If the files located in
the inetpub/ftproot/WhereNet/Server/G3v501 directory (See Reference
2 below), then type “/wherenet/server/G3v501/upgrade.txt”, note the
direction of the slashes.
Then confirm to overwrite the flash, ‘yes’ (enter/return). The unit responds
with Operation Complete confirming that is has downloaded the firmware
files and has started the Flash Memory upgrade process.
Reference 1
Reference 2
___________________________________________________________________________ 95
User’s Guide, WhereLAN III draft D1675 rev F
4 LED’s : The Kernel is initialized and is loading the applications, JFFS2 and CRAM
File system.
****** 4LED ******
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 2074K
NET: Registered protocol family 16
PCI: bus0: Fast back to back transfers disabled
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
Initializing Cryptographic API
g3wdt version 1.0.0.0, 2007: margin 60 sec
RAMDISK driver initialized: 16 RAM disks of 5800K size 1024 blocksize
g3dev version 1.0.0.1, 2006
g3rtc version 1.0.0.1, 2011
i2c /dev entries driver
i2c_adapter i2c-0: found 2048 byte 24c16 I2C EEPROM (writable)
i2c_adapter i2c-0: found DS1780 CPU monitor
Serial: Micrel Centaur UART driver version: 2.6.1.0
ttyAM0 at MMIO 0x3ff0000 (irq = 8) is a KS8695
Serial: g3-8250/16x50 driver version: 1.00, IRQ sharing enabled
ttyS1 at MMIO 0x3200100 (irq = 5) is a 16550A
eth info: Micrel KS8695P Ethernet Network Driver, version 1.0.0.21, Copyright (c) 2002-2005 Micrel, Inc.
eth info: Icache mode = roundrobin
eth info: VA = 0xf03ff000, PA=0x03ff0000
eth info: VA = 0xf03ff000, PA=0x03ff0000
Using deadline io scheduler
physmap flash device: 800000 at 2000000
phys_mapped_flash: Found 2 x16 devices at 0x0 in 32-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cmdlinepart partition parsing not available
RedBoot partition parsing not available
Using physmap partition definition
Creating 5 MTD partitions on "phys_mapped_flash":
0x00000000-0x00020000 : "bootloader”
0x00020000-0x001a0000 : "kernel"
0x001a0000-0x00400000 : "ramdisk"
0x00400000-0x007e0000 : "jffs2"
0x007e0000-0x00800000 : "cramfs"
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET: Registered protocol family 1
___________________________________________________________________________ 99
User’s Guide, WhereLAN III draft D1675 rev F
Continued 4 LED’s : The Kernel is initialized and is loading the
applications, JFFS2 and CRAM File system.
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
ath_rate_amrr: 0.1 (0.9.4)
ath_pci: 0.9.4.5 (0.9.4)
ath_pci: No devices found, driver not installed.
ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413,RF5413, REGOPS_FUNC)
wlan: 0.9.4wlan: mac acl policy registered
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
init started: BusyBox v1.2.1 (2011.11.15-16:42+0000) multi-call binary
Disabled Privacy Extensions on device c028dbf0(lo)
BusyBox v1.2.1 (2011.11.15-16:42+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
WhereLan-III: Mar 19 2012 19:05:04
embedded tag rx service
started rx diagnostic receive process started
1 LED (Power): The Application is loading the FPGA’s and DSP’s