Appendix D: Utilizing the USB Interface with Win/XP ...................................... 131
Appendix E: Utilizing the USB Interface with Vista and Win/7 ......................... 139
Appendix F: Creating a New Audio Clip File ..................................................... 145
Page 11
EWB100 Usage and Deployment Guide Rev 1.15
Revision
Description
Editor
0.0
Initial Draft
Bob Beach
1.0
Updates from reader comments
Bob Beach
1.1
Additional review comments
Linda Billhymer
1.2
Additional updates
Bob Beach
1.3
Added Appendix C and D
Bob Beach
1.4
Added screen updates to Appendix D
Bob Beach
1.5
Additional corrections/additions
Bob Beach
1.6
Version released for final review
Linda Billhymer
1.7
Final release
Linda Billhymer
1.8
Add information on Rev H, J, and K
Bob Beach
1.9
Cleanup from v1.8
Bob Beach
1.10
Changes for Rev K release
Bob Beach
1.11
Move some items from K to J
Bob Beach
1.12
Document Release for Rev J
Linda Billhymer
1.13
Update to Document fo r Rev J
Linda Billhymer
1.14
Fix typos, add v1281 features, Rev K
Bob Beach
1.15
Cleanup
Bob Beach
1.16
Removed company specific information.
Corrections by Ed.
Bob Greenway
Revision History
Page 12
EWB100 Usage and Deployment Guide Rev 1.15
Page 13
EWB100 Usage and Deployment Guide Rev 1.15
1 Introduction
1.1 The EWB100
The EWB100 is a compact Voice over wireless LAN (VoWLAN) communications
device designed to operate throughout the wireless local area network of an
enterprise environment. The EWB 100 provides Push-to-Talk style
communications, similar to any normal Push-to-Talk radio. EWB100 badges
enable instant employee accessibility through a simultaneous call to a group of
workers and a person-to-person reply call from a group member. They can
communicate with other mobile computers and enterprise devices
communicating over Wi-Fi.
The EWB 100 can be clipped onto clothing, worn on a lanyard, or slipped inside
a pocket and can be deployed either as a personal or shared device. In
environments where workers change shifts daily, an employee can select any
available badge.
1.2 This Document
This document is intended for those who select, configure, deploy, and support
the EWB100 device. It is not directed at those who are the end users of it. The
EWB100 Quick Start Guide is intended for such users.
This document describes the capabilities of the EWB100 and how the device can
be configured to take advantage of those capabilities. While the EWB100 is
typically used for its “Walkie talkie” like functions it is capable of much more and
this document describes those capabilities.
This document also describes how the device can be deployed and updated over
time. It does not describe the “Deployment Application” but instead describes
how many of the same functions can be achieved with existing network software
packages.
Also included in this document is a description of the mechanisms that are
available to diagnose and fix problems that may arise during deployment or in an
installation. The EWB100 has a number of powerful mechanisms that will allow
on-site or remote maintenance.
Finally this document will describe enough of the internal architecture so as to
make the process of configuring, optimizing, and supporting the device an easier
task.
Page 14
EWB100 Usage and Deployment Guide Rev 1.15
2 EWB100 User Overview
2.1 The Physical Device
The image below shows the EWB100 with the important user elements identified
2.2 The User Interface
The user interface of the EWB100 is very simple, consisting of 5 buttons,a
tricolor LED, a microphone, and a speaker. There are also optional headsetsthat
can substitute for the microphone and/or speaker. There is not a screen of any
type. This means that most of the user interactions take the form of audio (mostly
output) and button presses, perhaps supplemented by LED blink patterns.
Furthermore two of the buttons (VOLUP and VOLDN) are usually reserved for
volume control functions (although they can be used for certain other tasks). That
leaves 3 application oriented buttons: PTT, FAPP, and SAPP. The PTT button is
used almost exclusively as a “”push to talk” trigger;there are really only two
“application oriented” buttons.
The EWB gets around this limitation by two mechanisms: the first is to define
certain button actions beyond just press and release. The first is a “single click”,
which is a quick press and release. The second is a “double click” which is two
quick press and release sequences. The third is a sustained press and hold. The
EWB 100 treats each of these as a distinct event from a UI perspective.
Page 15
EWB100 Usage and Deployment Guide Rev 1.15
The second mechanism is by multiple button sequences. At this time only two
button sequences are used but potentially there could be three and four button
sequences but they would be very awkward to use. There are currently 3 two
button sequences defined:
PTT + FAPP => Power off
PTT + SAPP => Status/configuration
VOLDN + SAPP (while in the cradle) => set to factory defaults
The LEDs are used mostly to indicate general device state. Blinking Green
means everything is working properly. Blinking Red means something is wrong.
Amber is not used at the moment.
Most of the use oriented “feedback” to the user is via the speaker. The EWB 100
uses a combination of tones and voice responses to indicate state and events to
the user. All of these tones and voice responses can be replaced with silence or
different audio sequences, including different languages.
2.3 Voice Modes
There are two primary voice modes. One is a walkie talkie (one to many) type.
One user presses the PTT button and talks and lots of people hear. Just like
more traditional walkie talkies, there are multiple channels available and users
can pick which ones they want to use by switching between them.
The second mode is for private point to point calls. This is called Private Replyand keeps the same “push to talk” modality of the walkie talkie mode except that
it is a private session between two users. Such a session is setup after the
conclusion of a walkie talkie session via a simple button press sequence.
There are other voice modes beyond these two that will be described later in this
document.
Page 16
EWB100 Usage and Deployment Guide Rev 1.15
3 Internal Elements of the EWB100
This section introduces some of the more important internal aspects of the
EWB100 as well as some features beyond just the voice modes mentioned in the
previous section.
3.1 Two software subsystems
There are two software systems that run on the EWB100 device. The first is the
“mini-kernel”or “boot loader” which runs right after power on or reset. This
system does not have a lot of functionality but exists mostly to handle the
reloading of the main system when needed. This software has a limited set of
commands available but for the most part cannot examine or alter the system
configuration (although it can erase it entirely!). The minikernel’s commands are
documented in a separate section of this document
The second software system is the actual runtime code that has lots of
functionality and an extensive set of commands. Most of the commands in this
document apply only to the runtime software.
3.2 Configuration Data Base
There are many configuration parameters for the EWB100 device. Almost all
aspects of the behavior of the device may be altered by configuration
parameters. All configuration parameters have a default value that is part of the
runtime image and cannot be changed by the user except for some limited
values via the “User Defined Defaults” mechanism.
3.3 802.11 Radio
The ewb100 contains an 802.11 radio that operates in the 2.4GHz band. It
supports both 802.11b and 802.11g. The radio has been highly optimized to
reduce power consumption both when operating and when in standby mode.
3.4 IP Stack
The ewb100 contains an IPv4 protocol stack. It supports DHCP for obtaining IP
addresses. It also includes a simple Telnet server that can be used for diagnostic
and maintenance purposes.
3.5 Command Line Interpreter
There is a command line interpreter in the ewb100 that provides a means to
configure, update, monitor, and diagnose it. It provides complete access to the
configuration data base and so is used whenever the device needs to be
configured.
There are two versions of the CLI, one for the miniKernel and one for the runtime
code.
Page 17
EWB100 Usage and Deployment Guide Rev 1.15
3.6 Profiles
A profile is a set of configuration variables that control the user interface and
overall functionality of a EWB100 device. Different profiles are simply different
sets of the same configuration variables. Profiles define what functions are
associated with particular buttons, the alerts and notifications associated with UI
events, walkie talkie channels, etc. Virtually all user visible configuration
parameters are part of a profile. There are current 8 profiles per EWB100 and
they are accessed by selecting from profile numbers 0 to 7. Users select the
desired profile from the user interface.
3.7 Airbeam
Airbeam may be used to update the runtime code and configuration elements of
the EWB100. All updates are performed over the 802.11 network using the FTP
network protocol. Updates are described in files called “packages” and the EWB
looks for new packages on a regular Audio Clips and Default Dictionary
The EWB does not contain a text to speech engine but rather has a dictionary of
audio files called ”clips”. The device combines these clips into a meaningful
verbal phrase as needed. Some clips are tones while others are words. There
are about 500 audio clips stored in the “default dictionary” of the device by
default. New clips can be added to the device to enhance or replace the contents
of the default dictionary. These clips may be in other languages.
3.8 Web Server
The Ewb100 also contains a simple web server. External applications can use
this web server to command the device to perform simple tasks such as to play
one or more audio clips, flash the LEDs, and reset the device. The CLI is also
available using the Web Server.
Page 18
EWB100 Usage and Deployment Guide Rev 1.15
4 The Command Line Interpreter
4.1 Basic Concepts
The CLI on the ewb100 is used for a wide variety of functions including
configuration, updates, diagnostics, and maintenance. Its primary use, though, is
for configuring the device. The interface is very simple; it features one line
commands consisting of a key word and zero or more parameters. Most
commands take effect immediately.
The CLI is always available on the device and can be reached from a variety of
sources:
USB
Telnet
HTTP
Command Files
MSP
The CLI is the key to configuring the device since it is the only way to access the
configuration data base. Configuration commands may be entered one at a time
or in a sequence. This later technique is used in conjunction with the Airbeam or
MSP client.
4.2 The CLI and the ConfigurationData Base
The Configuration data base contains all the configuration information for the
EWB100 device. It is stored in a special area of flash memory. Configuration
changes are stored as changes from the default value. When the configuration
data base is erased, the system returns to the default values for all the
configuration parameters.
There are three different configuration areas in flash: two for user defined
information and one for manufacturing information. Multiple changes to the same
configuration value will result in prior values in the flash being invalidated and
new entries being created. Hence configuration areas can “fill up” with invalidated
data. Only one of the user defined areas is used at a time. When one area
becomes full (usually because to too many invalidated values), all the valid data
in it will be copied to the other area, which then becomes the current
configuration data base and the other area erased. No such mechanism exists
for the manufacturing area, since the data values are seldom altered. The state
of configuration memory is shown via the “st cfg” command.
User Defined Defaults is a mechanism by which the default values of certain
configuration parameters may be set by the user. These user defined defaults
will override the runtime default values when the device is restored to “factory
defaults.” They are limited to a few subsystems and parameters within those
subsystems. The goal of this feature is to allow a device to upload new
Page 19
EWB100 Usage and Deployment Guide Rev 1.15
configuration information from a remote server even if the current configuration
has been corrupted. The “existing” configuration can be deleted and the “user
defined defaults” will be used to access the update server.
4.3 Accessing the CLI
As noted above, CLI is always available on the device and can be reached from
a variety of sources:
USB
Telnet
HTTP
“Command Files”
MSP
There is a USB interface on the device that also serves at the headset jack.
When used with the proper connector and with a driver on the PC, the CLI can
be accessed via HyperTerm on a Windows PC. The details on how to use the
USB connection is described in Appendix E
The Telnet and HTTP interfaces are available over the network.
Command Files are used to deliver a sequence of CLI command lines to the
device. These are downloaded by the Airbeam or MSP client from a server. They
are typically used to configure the device when there are more than just a few
configuration settings or when there are many devices to be configured.
The input model is very simple. When looking for the next character input, the
CLI routines examine 4 different input buffers. Each of these buffers corresponds
to one of the 4 above sources. The drivers for these sources simply deposit
characters into their buffer and the CLI will pull them out accordingly. With this
model one can mix input from different sources, although in practice this seldom
happens as only one interface is generally active at a time.
Output is directed to whatever source from which the last input character came.
The CLI syntax is simple and consists of a command followed by a number of
parameters. There is a help facility that can be accessed at any time by entering
a “?” (i.e. “set ?)” will display all the possible inputs to the set command). The
help facility is present on most but not all commands. All commands must be
entirely lower case.
Page 20
EWB100 Usage and Deployment Guide Rev 1.15
Most input parameters can be shortened to the minimally unique string. Hence:
“set” can be “se”
“statistics can be “st”
“key” can be “ke” or even “k”
The key to using to the shortened format is that what is entered must be unique
among the possible options for the command.
4.4 CLI Access Control
4.4.1 Basic Concept
A password may be defined that will control access to the CLI via all
mechanisms. If a password is defined, the user must enter the password when
prompted (or must be included in CLI script files). If no password is defined,
access to the CLI is unrestricted. By default access control is disabled.
If access control is enabled, the user must login in using the following command:
login x
Where x is the password. The means to specify the password is defined below.
4.4.2 Configuration Commands
4.4.2.1 set Password Command
This command defines a Customer defined CLI password. If a password is
defined, it must be entered before access the CLI is granted. If no password is
defined, access is unrestricted. By default no password is defined. The command
to set the password is:
set misc clipwd x
Where x is the password. If a password exists and the user wants to disable it,
then x should be set to “none”.
4.4.2.2 Encrypted Customer CLI Password Command
This command defines the Customer defined CLI password, using an encrypted
string. The string must be created using the clientencrypttool program found on
the online support site. If a password is defined, it must be entered before access
to the CLI is granted. If no password is defined, access is unrestricted. By default
no password is defined. The command to set the password is:
set misc eclipwd x
Page 21
EWB100 Usage and Deployment Guide Rev 1.15
Where x is the encrypted version of the password. Note that x must be a multiple
of 32 hex digits up to a maximum of 128 hex digits. If a password exists and the
user wants to disable it, then x should be “none” (in encrypted form).
Page 22
EWB100 Usage and Deployment Guide Rev 1.15
4.5 Encrypted Configuration Parameters
Certain Configuration Parameters may be sent to the device in an encrypted form
that uses AES encryption. The parameters are:
WPA Passphrase and User Default WPA Password
WPA Key and User Default WPA key
Airbeam Password and User Default Airbeam Password
This mechanism allows sensitive information to be placed into CLI files without a
concern that the information will be compromised.
4.6 “new”, “new2”, and “new3” parameters
There is one set of configuration parameters that is somewhat different than most
of the others. These are the “new” configuration items under the “misc”
subsystem tag (i.e. “set misc new xx” and “show misc”). These three values
(new, new2, new3) are defined as bit maps in which each bit controls a particular
element of a particular subsystem. These were added as shortcuts to prevent the
proliferation of many “on/off” configuration variables however they do introduce a
different class of configuration variable. The general format used to set these
commands is:
set misc xx yy
Where xx is “new”, “new2”, or “new3” and yy is a hex value containing the
representation of all the bits that are to be set. If a user wants to change a bit
configuration value, a “show misc” command should be executed to display the
current value of the bit field. Whatever changes (set or clear) should take into
account the currently set bits and not change other bit map settings. One should
only change the bit fields of interest.
Certain bit fields are set by default and should be changed only when directly
instructed by qualified service personnel.
In the rest of this document, those configuration items that utilize the “new” fields
will indicate it and will specify the “new” field and the bit location within that field
that is to be set/cleared.
4.7 Undocumented commands and parameters
This document does not describe all commands and configuration variables that
are available on the EWB100 and so users will encounter such items when using
commands such as “show x” and “set ?”. Many of these items are for developer
or internal support use only and altering them may result in the EWB100
operating incorrectly or not at all. Hence only the commands and parameters that
are defined in this document should be used or altered; executing any CLI
commands not documented in this guide can cause unpredictable behavior and
voids the product warranty.
Page 23
EWB100 Usage and Deployment Guide Rev 1.15
4.8 CLI Commands Commands
There are the following commands in the runtime software CLI:
set : set configuration
show : show configuration
stat : system status
system : system control
notify : performs a notify op
roam : roam History
cfg : configuration operations
help : display general user interface help
clear : clear stats
ping : ip ping
version : version of software
4.8.1 set
This command is used to assign values to various configuration parameters.
There will always be at least 2 parameters and can be as many as 5 or 6.
Parameters are grouped into categories associated with various subsystems on
the device. The current set of parameters is described in this document and is
associated with the subsystem description. It should be noted that there is a
default value for every configuration parameter. Using the set command will
override the default value and result in the value being written to flash. Changes
for many of the parameters will take effect immediately while others will require a
reboot. If in doubt, reset the device after changing any parameter or set of
parameters.
4.8.2 show
This command is used to display the current value of the configuration settings
for the various subsystems. There is generally only one parameter associated
with a Show command which is the name of the subsystem. All configuration
settings for a particular subsystem will be shown. It is generally not possible to
display only one configuration parameter in a subsystem.
4.8.3 help
This command is used to display the syntax for the various commands. It takes
no parameters.
4.8.4 clear
This command is used to clear all counters in all subsystems. It takes no
parameters. It is not possible to clear the counters of only one subsystem.
4.8.5 stat
This command is used to display counters, statistics, and the contents of various
dynamic tables. There is usually only one or two parameters associated with a
Statistics command. Depending on the particular subsystem, the output can be a
Page 24
EWB100 Usage and Deployment Guide Rev 1.15
list of counters (simple incrementing values), statistics (values that have been
computed based upon various internal variables), or the contents of tables that
have been built dynamically
4.8.6 notify
This command is used to play various audio phrases and to control the 3 LEDs.
There are between 3 and 10 parameters associated with this command. The
user can either specify a list of words from the Phrase Book that are to be played
or can cause an LED to display a particular “blink” pattern. It is used primarily by
developers and others who may alter the phrasebook contents.
This command is also used to alter the intensity of the LEDs.
4.8.7 cfg
This command is used to control and monitor the configuration subsystem. It
takes one or two parameters that define the operation. The user can display
various statistics, return the configuration to its default state, etc.
4.8.8 version
This command is used to display the software version as well as certain
hardware information.
version
CA10 Version 1.1.1077 Realtime-CA10 No external mem used Mar 14 2012 08:52:24
This command takes no parameters. It displays the roam history for the EWB100
device.
4.8.10 ping
This command performs an ICMP ping to a device.
4.8.11 notes
Notes are a means of adding information to a device that is stored in
configuration memory. Notes are text strings that are not used by the device in
anyway but are meaningful in some way to users, support personal, or
developers. Information may include customer details, past history, known
issues, etc.. Notes can be set and displayed. There can be up to 16 lines of
notes.
Page 25
EWB100 Usage and Deployment Guide Rev 1.15
5 802.11 Interface
5.1 Basic Radio Functionality
The following describes the 802.11 related features of the EWB 100.
It is an 802.11 b/g compatible device. As such it operates only in the
2.4GHz band.
It supports operation on channels 1-11 in the US and 1-14 on a worldwide
basis. By default it will assume channels 1-11 are operational. For
operation on other channels, contact support.
To minimize power consumption it will scan only channels 1, 6, and 11.
Other channels are ignored. This may be changed by a configuration
command.
Output power is typically 15dbm or greater.
Receive sensitivity is typically greater than -85dbm for 802.11b packets.
It supports OPEN, WEP, TKIP, and AES encryption.
It supports WPA-PSK and WPA2-PSK authentication
It supports WMM and will use it if supported by the AP. Voice traffic is
sent on AC=0, data traffic is on AC=3.
DTIM = 2 must be used for the device. Other settings will result in
unreliable operation.
The network should be configured to use as low a basic rate for beacons
and broadcast packets as possible. Ideally 2 Mbits should be Due to a
lack of antenna diversity, the EWB100 does not operate well at 5.5 and
11Mbits basic rate. Pure 11g operation is supported but again the lowest
acceptable rate should be used.
To increase receive range the device will associate at lower than the
highest (54Mbits) 802.11g rates, usually 24 Mbits. It will transmit at any
rate supported by the AP.
Page 26
EWB100 Usage and Deployment Guide Rev 1.15
The device operates primarily in PSP mode, even during voice packet
transfers. As such the EWB is very sensitive to variations in Beacon
delivery times. If an infrastructure is configured to support multiple BSS,
the one the EWB uses should be the first one if secondary ones
experience significant variability in delivery times.
Roaming/scanning is triggered primarily by missed consecutive beacons
or by sudden and significant drops in the RSSI value. By default 5 missed
consecutive beacons will trigger a scan.
The device discovers APs only by active scanning use probe requests. It
does not perform “background” or passive discovery of APs.
The device will filter APs based on the RSSI and ignore those with RSSI
below a threshold. This may be changed by a configuration command.
For best performance the network should be designed to support signal
strength of -70dbm or better.
The device maintains a list of 16 APs. It refreshes this list entirely on each
scan.
5.2 Radio Configuration Commands
This section describes the configuration commands associated with the radio.
5.2.1 Ess
This command sets the ess for the radio. The format is:
set radio ess xyz
Where xyz is a string that defines the ess for the radio. It can be from 1 to 31
ASCII characters. This value does not take effect until the device is reset.
The default is “motorola”.
5.2.2 User Default Ess
This command sets the “user default” ess. This value is used when the system
configuration is returned to “system defaults”. It has the same syntax and default
value as the ess command:
set radio defess xyz
The default is “motorola”.
Page 27
EWB100 Usage and Deployment Guide Rev 1.15
5.2.3 Security modes
This command defines the acceptable security modes for the radio. The format
is:
set radio security xyz
Where xyz is a string that defines the target security mode. Acceptable values
are:
none
wep 64 (40 bit wep)
wep128 (128 bit wep)
tkip
aesccmp
The default is “none”
5.2.4 User Default Security Mode
This command sets the “user default” security mode. This value is used when the
system configuration is returned to “system defaults”. It has the same syntax and
default values as the security mode command:
set radio defsecurity xyz
5.2.5 WEP Security Key
This command sets the key values when WEP is used. The format is:
set radio key x abcd
Where x is the WEP key index (0-3) and abcd is a WEP key value associated
with the index..It is either 10 or 26 hex digits depending on the WEP option
selected.
5.2.6 WEP index
This command sets which WEP key will be used for data transfers. The format is
set radio index x
Where x defines the WEP key index to be used. Its values are from 0 to 3.
The default is 0.
Page 28
EWB100 Usage and Deployment Guide Rev 1.15
5.2.7 WPA Password
This command sets the WPA/WPA2 PSK Password . The format is:
set radio password xyz
Where xyz is the password string. It may range from 8 to 63 ASCII characters.
This password must be set only after the ESS for the device has been specified.
This parameter cannot be displayed after being entered.
There is no default value for this parameter
5.2.8 User Default WPA Password
This command sets the “user default” wpa pasword. This value is used when the
system configuration is returned to “system defaults”. It has the same syntax as
the wpa passworde command:
set radio defpassword xyz
5.2.9 Encrypted WPA Password
This command sets the WPA password using an encrypted value. The password
must have been encrypted using the cliencrypttool program with an identical key.
The command format is:
set radio epassword xxx
Where xxx is the encrypted password. Note that xxx must be a multiple of 32 hex
digits up to a maximum of 128 hex digits.
There is no default value for this parameter.
5.2.10 Encrypted User Default WPA Password
This command sets the “user default” WPA password using an encrypted value.
The password must have been encrypted using the cliencrypttool program with
an identical key. The command format is:
set radio edefpassword xxx
Where xxx is the encrypted password. Note that xxx must be a multiple of 32 hex
digits up to a maximum of 128 hex digits.
There is no default value for this parameter.
5.2.11 Wpakey
This command sets the security key when TKIP or AESCCMP are used. It
contains 64 hex digits to create the 256 bit key. The command is
set radio wpakey xyz
Where xyz is the security key.
There is no default value for this parameter.
Page 29
EWB100 Usage and Deployment Guide Rev 1.15
5.2.12 User Default Wpakey
This command sets the user default security key when tkip or aesccmp are used.
It contains 64 hex digits to create the 256 bit key. The command is
set radio defwpakey xyz
Where xyz is the security key.
There is no default value for this parameter.
5.2.13 Encrypted Wpakey
This command sets the security key when tkip or aesccmp are used. It contains
64 hex digits to create the 256 bit key. The WPA key must have been encrypted
using the cliencrypttool program with an identical key. The command is
set radio ewpakey xyz
Where xyz is the security key.
There is no default value for this parameter.
5.2.14 Encrypted Default Wpakey
This command sets the default security key when TKIP or AESCCMP are used.
It contains 64 hex digits to create the 256 bit key. The WPAkey must have been
encrypted using the cliencrypttool program with an identical key. The command
is
set radio edefwpakey xyz
Where xyz is the security key.
There is no default value for this parameter.
5.2.15 Minrssi
This command defines the minimum measured RSSI for AP to be considered
acceptable. APs with a measured RSSI below this number will not be considered
for association, even if they are the only APs that are visible. The command is:
set radio minrssi x
Where x is the RSSI value as a positive, decimal number. Internally the value will
be converted to a negative number (i.e. -78dbm).
The default is -80dbm.
It should also be noted that when this value is displayed using the “show radio”
command, it will be displayed as 65535-x where x is the value that was entered.
The display routines do not handle negative numbers properly and so the value
is displayed as a large positive number.
Page 30
Loading...
+ 117 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.