Anaren Integrated Radio AIR BoosterPack Users Manual

Anaren Integrated Radio
AIR BoosterPack Users
Manual
Release Date 1/18/12
THIS PAGE LEFT INTENTIONALLY BLANK
iii
USERS MANUAL
AIR BoosterPack
Contents
1.
2.
3.
4.
5.
AIR BoosterPack Overview ...........................................................................................................................5
1.1. Overview ....................................................................................................................................................5
1.2. Kit Contents ...............................................................................................................................................6
Getting Started with the AIR BoosterPack ...................................................................................................7
2.1. Hardware Installation ............................................................................................................................... 8
2.1.1. AIR BoosterPack with LaunchPad ......................................................................................................8
2.1.2. AIR BoosterPack Standalone Operation .............................................................................................9
2.2. Software Installation ............................................................................................................................... 10
2.3. IMPORTANT: Required Radio Setup .................................................................................................. 14
2.4. Using the Demo Application ................................................................................................................. 14
AIR BoosterStack Software Application .................................................................................................... 15
3.1. AIR BoosterStack Firmware ................................................................................................................... 16
3.1.1. Low-Power Sensor Application ......................................................................................................... 16
3.1.2. Hub Application ................................................................................................................................ 18
3.1.3. Device Pairing ................................................................................................................................... 20
3.1.4. Configuration Change ....................................................................................................................... 21
3.1.5. Remote Control Applications ............................................................................................................ 24
3.1.6. Additional Features ........................................................................................................................... 24
3.2. Transceiver Configurations ................................................................................................................... 25
3.3. AIR BoosterStack GUI ............................................................................................................................ 27
AIR BoosterPack Hardware ......................................................................................................................... 50
4.1. Electrical Characteristics ........................................................................................................................ 50
4.1.1. Absolute Maximum Ratings ............................................................................................................. 50
4.1.2. Recommended Operating Conditions ................................................................................................ 50
4.2. Connector Pinout .................................................................................................................................... 51
4.3. Jumper Settings ....................................................................................................................................... 52
4.4. Schematics ................................................................................................................................................ 55
4.5. PCB Layout .............................................................................................................................................. 56
4.6. Bill of Materials (BOM) ........................................................................................................................... 58
Range Test ...................................................................................................................................................... 59
THIS PAGE LEFT INTENTIONALLY BLANK
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 5 of 62
1. AIR BoosterPack Overview
1.1. Overview
The AIR BoosterPack is a low-power wireless transceiver extension module for use with the
Texas Instruments MSP-EXP430G2 LaunchPad development kit. Based on the CC110L
device, the on-board A110LR09A radio module with integrated antenna operates in the
European 868-870MHz and US 902-928MHz ISM bands. The included AIR BoosterPack
software application, called AIR BoosterStack, demonstrates an example sensor network as
well as network status reporting.
Figure 1 - AIR BoosterPack with LaunchPad
Page 6 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
AIR BoosterPack Hardware Features:







1.8 to 3.6 V operation
Low Power Consumption
SPI Interface
Prototyping area
Footprints for adding a microcontroller, pushbutton switch, and LED for standalone
operation
ROHS Compliant
See A110LR09x Users Manual for radio specific features
AIR BoosterStack Software Features:






Low-power temperature sensor application
Star network topology with one hub node and up to four sensor nodes
Graphical User Interface provides network control and displays key radio parameters
Ability to change radio settings locally and/or remotely
Remote control feature to turn on/off LaunchPad green LED
Node ID, operating state, and radio settings restored at power-up
1.2. Kit Contents
The AIR BoosterPack kit includes the following:




Two AIR BoosterPack modules
Two MSP430G2553 devices (preloaded with a sample program)
Quick Start Guide
CD containing AIR BoosterStack demo application software, USB UART device driver,
and supporting documentation
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 7 of 62
2. Getting Started with the AIR BoosterPack
The following sections describe the necessary steps to get the AIR BoosterPack hardware and
BoosterStack software up and running with the LaunchPad.
Figure 2 - AIR BoosterPack Overview
1
AIR Radio Module.
2
Signal Path Jumpers. See section 4.3 for details on changing jumper settings.
3
Prototyping Area. Add your own circuit to this area. These pads have no electrical
connection to the AIR radio module, LaunchPad interface connectors, or power/ground.
4
Pads for LED Expansion.
5
Pads for Pushbutton Switch Expansion.
6
Range Test Orientation Indicator. Optimum RF performance is achieved when the
BoosterPack module is oriented vertically with the arrow pointing upward.
7
Pads for MCU expansion. Add a microcontroller for standalone operation without the
LaunchPad board. See section 2.1.2 for details.
8
Pads for External Power Source. Supply power from a battery for standalone operation
without the LaunchPad board. See section 2.1.2 for details.
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 8 of 62
2.1. Hardware Installation
2.1.1. AIR BoosterPack with LaunchPad
The following steps need to be performed on each LaunchPad to be used with a BoosterPack:
1) If not already populated, solder both 10-pin male headers provided in the LaunchPad kit
onto the LaunchPad‟s J1 and J2 breakout connections.
2) For LaunchPad Rev1.4 and earlier, remove jumpers TXD and RXD from J3 and install
crossover jumpers (not included) onto the same group of pins to make the following
connections:
a. Connect J3.3 to J3.6
b. Connect J3.5 to J3.4
3) Ensure the VCC jumper is populated on J3. Jumpers RST and TEST also need to be
installed when programming the microcontroller or debugging software using IAR
Embedded Workbench.
4) Replace the existing MSP430 device on the LaunchPad with a preprogrammed
MSP430G2553 device provided in the AIR BoosterPack kit. Be sure the microcontroller
is oriented properly by ensuring the pin 1 indicator on the device matches the indicators
on the socket and LaunchPad silkscreen.
5) Install the AIR BoosterPack onto the LaunchPad board. Ensure the BoosterPack is
oriented correctly. The text on both boards should be in the same direction and the
rocket logo on the BoosterPack should be directly above the rocket on the LaunchPad
board.
Figure 3 – Installed BoosterPack
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 9 of 62
2.1.2. AIR BoosterPack Standalone Operation
The BoosterPack comes with expansion pads for upgrading to a standalone configuration that
allows operation without the need for the LaunchPad board. Follow the directions below to
upgrade the BoosterPack for standalone operation. See section 4.6 for a complete component
listing.
1) Install pushbutton tactile switch S1 (not provided). The button is needed to pair the radio
with another radio.
2) Install LED D1 and resistor R2 (all not provided). This step may be skipped if a visual
indicator is not required.
3) Install a 20-pin DIP socket at U2 (not provided). Ensure the pin 1 indicator notch on the
socket aligns with the BoosterPack silkscreen. This step may be skipped if a
microcontroller is to be soldered directly to the board.
4) Install capacitors C1, C2 and resistor R1 (all not provided). These components are
required for power supply decoupling and generating reset during power-up.
5) Insert a preprogrammed MSP430G2553 device (provided in the AIR BoosterPack kit)
into the socket installed in step 3 above. Be sure the microcontroller is oriented properly
by ensuring the pin 1 indicator on the device matches the indicators on the socket and
BoosterPack silkscreen. If a socket is not desired, solder the MSP430 device to the
board at U2.
6) Solder power supply wires or a power connector (all not provided) to the VDD and GND
connections on the BoosterPack board. The BoosterPack does not provide any
protection against reverse polarity or overvoltage, so it is up to the user to ensure an
external supply is properly connected and stays within the operating range specified in
section 4.1 Electrical Characteristics.
Figure 4 - Standalone BoosterPack
Page 10 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
2.2. Software Installation
System Requirements
- Microsoft Windows XP SP3 or later operating system (32-bit and 64-bit supported)
- At least 100MB HDD space available
- CD drive
Follow the instructions below to install the BoosterStack software.
1) Insert the BoosterStack CD provided in the Anaren BoosterPack kit. The AIR
BoosterStack Lite Install utility should automatically open. If it does not, browse to the
CD drive and double-click on AutoRun.exe to run the installer.
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 11 of 62
2) Click on „Install LaunchPad USB Driver‟ to install the MSP430 Application UART driver
needed to communicate with the LaunchPad board via serial COM port (USB virtual
COM port). Click „Next‟ in the Device Driver Installation Wizard to install the driver. The
installer will automatically detect whether the operating system is 32-bit or 64-bit and
install the appropriate device driver. Click „Finish‟ when the installation has completed.
3) Click on „Install ATC-BoosterStack GUI‟ to install the application software. Click „Next‟ in
the ATC - BoosterStack Lite InstallShield Wizard.
Page 12 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
Read the Anaren BoosterStack software license agreement, click the „I accept the terms
in the license agreement‟ button to acknowledge you have read and agree to the license,
and then click „Next‟.
Click „Next‟ to accept the Third-Party license agreement.
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 13 of 62
Click „Install‟ to start the software installation.
Click „Finish‟ when the installation has completed.
Installation of the BoosterStack software is now complete. Please refer to section 3.3 for details
on using the GUI.
Page 14 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
2.3. IMPORTANT: Required Radio Setup
The AIR BoosterPack must be operated in accordance with local regulations. The firmware
preloaded in the MSP430G2553 devices provided with the AIR BoosterPack kit offers two radio
operation options; ETSI (default) and FCC/IC. If your location is not covered by either ETSI or
FCC/IC then you must check local regulatory codes for how to obtain permission to operate the
modules prior to using them.
If covered under FCC/IC regulations you must first connect each module to the PC/laptop and
use the GUI to change the "Logical Radio" to "1, A110LR09A, FCC" and click the "Apply
Configuration Changes" button. Be sure the “Apply Changes To” pull-down menu is set to
option 0 to apply the changes only to the local radio and not option 1 which is for “Remote +
Local”. The new settings are stored in non-volatile (i.e. Flash) memory and the devices will
continue to power-up with FCC/IC compliant settings. See section 3.3 for more information on
using the GUI.
2.4. Using the Demo Application
Follow these directions to start using the demo application.
1) Connect the LaunchPad/BoosterPack assemblies to USB ports.
2) Launch the ATC – BoosterStack Lite software. The GUI screen will appear and the GUI
will attempt to connect to the COM port. Once the connection is established, the GUI will
populate all the tabs and will be ready to use. A trace for the node temperature will
appear for the node itself (see section 3.3 for further details).
3) To identify a particular node, click on „Green LED‟ check box, which will send a
command to that module to illuminate the Green LED on its Launchpad.
4) Change one of the module‟s „Application State‟ to Sensor (by default, both the modules
will be Hub).
5) Pair the Sensor and Hub modules. This will display the information of the paired module
into the „Available Node List‟ of the corresponding module (see section 3.1.3 for further
details).
6) The traces for Local RSSI, Remote RSSI and Chip Temperature will appear for the
paired node.
7) Perform necessary changes to the configuration settings using the populated tabs (see
section 3.3 for further details).
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 15 of 62
3. AIR BoosterStack Software Application
The software application provided with the AIR BoosterPack kit, called AIR BoosterStack,
demonstrates an example sensor network as well as network status reporting. The sensor
network uses a star topology with one hub node and up to four sensor nodes. Temperature
information from each sensor is periodically transmitted to the hub which forwards the data to a
Graphical User Interface (GUI) running on a PC/laptop. The GUI displays the temperature
readings from each sensor as well as Received Signal Strength Indicator (RSSI) values for each
radio link.
Sensor
1
PC
Hub
Sensor
4
Sensor
2
Sensor
3
Figure 5 - Network Topology
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 16 of 62
3.1. AIR BoosterStack Firmware
3.1.1. Low-Power Sensor Application
The sensor is intended to be a low-power device capable of long-term operation while powered
from a battery. To achieve this goal, the radio and microcontroller are placed into sleep mode
whenever possible. The AIR BoosterStack demo application is configured to periodically
(approximately once every second) wake up the processor, perform a temperature
measurement, wake up the radio, transmit the data, wait for an acknowledgement, and then
finally go back to sleep. For maximum battery life, the debug circuitry on the LaunchPad board
needs to be powered down. This can be accomplished by removing the VCC jumper from
LaunchPad J3 and applying power to LaunchPad J6. As an alternative, the AIR BoosterPack
module can be operated in a standalone mode (see section 2.1.2 for details).
Since it spends the majority of its time in sleep mode, the sensor is responsible for initiating all
data transfers to/from the hub. After transmitting its data, the sensor switches to receive mode
to listen for an acknowledgement from the hub. The hub may also send any pending messages
to the sensor at this time. If data or a command is received from the hub, the sensor will send
an acknowledgement and then go back to sleep. If the sensor receives an acknowledgement
only (i.e. no payload data) or doesn‟t receive anything at all within a predefined timeout period it
will terminate the communication cycle and go back to sleep. See Figure 6 and Figure 7 for flow
diagrams depicting the sensor‟s behavior.
SENSOR
NO
GET
DATA
YES
PAIRING
COUNT?
BUTTON PRESS
FOR PAIRING?
NO
YES
NO
SET PAIRING
COUNT DOWN
MAP INPUT TO
HUB SPOT
COPY
APPLICATION
STATE TO
FLASH
PAIRING
MASK SET?
YES
REMOVE NODE
FROM NETWORK,
SET PAIRING
MASK
YES
TEMPERATURE
DATA
AVAILABLE?
NO
MAP RECEIVED
DATA TO
HARDWARE
NO
YES
SENSOR
OPERATION
SUCCESSFUL?
Figure 6 - Sensor Application Flow Diagram
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 17 of 62
SENSOR
OPERATION
DATA EXCHANGE
SUCCESSFUL?
RADIO
IN
SLEEP
MODE?
NO
NO
YES
NETWORK
VALIDATION
SUCCESSFUL?
YES
RETURN 0
YES
RETURN 1
WAKE UP THE
RADIO
PAYLOAD
RECEIVED?
NO
YES
CHANGE
CYCLE
TIME?
DATA EXCHANGE
CONFIG
REQUEST TO BE
SENT?
YES
CONFIG CHANGE
SEQUENCE,
RETURN
CHECK FOR
CONFIG CHANGE
YES
NO
NO
NO
FRAME SENT
SUCCESSFULLY?
YES
FRAME RECEIVED
SUCCESSFULLY?
YES
SET CYCLE
TIME
NO
NO
RETURN 1
RETURN 0
Figure 7 - Sensor Operation and Data Exchange Function Flow Diagrams
Sensor Operation: The sensor initiates a data transfer and if the data exchange is successful,
it proceeds with network validation to see if pairing is needed or whether the replying hub node
is already in its network. Upon a successful network validation, the sensor checks if the hub is
requesting a change to the sensor‟s data acquisition rate and if so adjusts its timer to the new
value and returns true.
Data Exchange: If necessary, the sensor wakes its radio from sleep mode. If a configuration
change request is to be sent, it continues with the configuration change sequence and returns.
Otherwise it sends the data frame to the hub and waits for a response. If a configuration change
request is received from the hub, the sensor follows the configuration change sequence and if
payload data is received, it returns true.
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 18 of 62
3.1.2. Hub Application
The primary function of the hub node is to provide an interface between the GUI running on a
PC/laptop and all sensor nodes within the network. The hub has basic network routing
functionality built-in which allows pairing with up to four sensors (limited only by available
microcontroller resources). Unlike the sensors, it is assumed that the hub is always powered by
a USB cable plugged into the LaunchPad board. Data transfers from each sensor are
asynchronous events, so the hub spends most of its time with its radio in receive mode listening
for packets from the sensor nodes. In general the hub will only transmit a packet after it has
received a message from one of the sensors. The only exception to this is when it is in the
middle of a configuration change sequence and it sends ping messages to the sensor in order
to determine if the configuration change was successful. Figure 8 and Figure 9 show the hub
application software flow diagrams.
HUB
REPORT
TEMPERATURE
DATA
HUB OPERATION
SUCCESSFUL?
YES
STORE THE
RECEIVED
DATA
NO
YES
NO
TEMPERATURE
DATA
AVAILABLE?
Figure 8 - Hub Application Flow Diagram
Hub Operation: If the hub successfully completes the Listen operation, it proceeds to network
validation (see section 3.1.3 for details) to see if pairing is needed or whether the node is
already in its network. If network validation is successful, it returns true.
Listen Function: When the hub receives a valid frame from a paired sensor it checks to see if
the frame contained a payload. If so, it creates a frame with its own payload data (if any) and an
acknowledgement to the payload received from the sensor. If there is a request for a
configuration change, either from the sensor or the GUI, it enters the configuration change
sequence (see section 3.1.4). Otherwise it sends its frame, enters into receive mode to listen
for an acknowledgement from the sensor, then returns to the application.
If it receives just an acknowledgement from the sensor (i.e. no payload), then it does not create
a frame in response. Instead, it enters into receive mode to listen for the next frame from the
sensor and returns to the application.
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 19 of 62
If neither payload nor acknowledgement is received within a specified timeout period, the radio
is checked to see if it is still in receive mode. If not in receive, the radio is commanded to go to
receive mode. In either case the hub returns to the application to listen for the next frame from
the sensor.
Along with the temperature data, the hub receives the following information from the sensor and
sends the same information about itself back to the sensor. Thus for status updates, the hub
provides both the local and remote information to the GUI. It also reports its own temperature
data to the GUI at regular intervals.
1. Received Signal Strength Indicator (RSSI)
2. Link Quality Index (LQI)
3. Frequency Offset
4. Power
5. Last Used Channel
6. Frame Counter
HUB
OPERATION
LISTEN
YES
LISTEN
SUCCESSFUL?
YES
NO
GET
DATA
FRAME
RECEIVED?
NO
RETURN 0
CONFIG
TIMEOUT?
PAYLOAD??
NETWORK
VALIDATION
SUCCESSFUL?
YES
RETURN 1
NO
YES
NO
RESET
RETURN
VALUE
YES
CHECK FOR
CONFIG CHANGE,
SEND ACK AND
DATA, SET RETURN
VALUE
CHECK FOR
CONFIG CHANGE,
RESET RETURN
VALUE
RECEIVE
ON
NO
YES
RECEIVE
ON??
ABORT
CONFIG
CHANGE
YES
NO
RETURN
VALUE
Figure 9 - Hub Operation and Listen Function Flow Diagrams
FRAME
TIMEOUT?
NO
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 20 of 62
3.1.3. Device Pairing
The protocol is started by pairing the hub with the sensor node(s). Although the hub stays in
receive mode to listen for frames from sensors, it will not respond to a frame that is sent from a
non-paired sensor. The only exception to this is during the pairing mode when it receives a
frame from a sensor requesting to join the network.
The following steps are used to pair a sensor with the hub:
1. For the hub, ensure the App State is set to Hub and then press the „Discover Nodes‟
button in the GUI. The hub will search for sensor nodes requesting to join the network
for approximately 10 seconds. During this time, most of the GUI controls are disabled
(i.e. grayed out) preventing other user commands from being issued to the BoosterPack.
The controls are re-enabled at the end of the node discovery sequence.
2. The sensor has two methods for pairing with the hub. While the hub is scanning for
sensor nodes:
a. Press and hold the pushbutton switch on the sensor (S2 on LaunchPad) for at
least 2 seconds as described in section3.1.6. If the pairing was successful, the
sensor will be added to the hub‟s Available Node List.
-ORb. Open a second session of the ATC BoosterStack Lite GUI for the sensor node
and ensure the App State is set to Sensor. Press the „Discover Nodes‟ button in
the GUI. As with the hub, the sensor will request to join a network for
approximately 10 seconds and the controls will be disabled. If the pairing was
successful, the hub will be added to the sensor‟s Available Node List.
3. Once the modules are paired, the RSSI and temperature from each radio will be
displayed in their respected graphs in the GUI.
BUTTON
PRESS
DISCOVER
NODES
SENSOR
RED LED TOGGLE
SENSOR DATA
HUB ACK + HUB DATA
SENSOR ACK
RED LED TOGGLE
SENSOR DATA
HUB ACK + HUB DATA
SENSOR ACK
Figure 10 - Pairing Diagram
HUB
BUTTON PRESS
SENSOR DATA
DISCOVER NODES
SENSOR DATA
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 21 of 62
Sensor Pairing Mechanism: The sensor is placed into pairing mode by pressing the button
switch on the module. The pairing mask is set to zero by default; the button press assigns it a
pairing mask of 0xFFFFFFFF. The user can manually set the pairing mask if desired. If the
pairing mask is set, a pairing-bit is set in the frame indicating that this node requesting to join
the network and the data exchange is initiated by the sensor. If the hub is discovering nodes at
the same time, it will respond to the frame sent by the sensor. The sensor validates the received
frame and proceeds with “Network Validation”.
Hub Pairing Mechanism: The hub is placed into pairing mode by pressing the “Discover
nodes” button on the GUI. The pairing mask is set to zero by default; the button press assigns it
a pairing mask of 0xFFFFFFFF. The user can manually set the pairing mask if desired. When
the hub receives a frame from the sensor, it checks if the pairing-bit is set in the received frame.
If so, it marks that frame as valid, sets the pairing-bit in its acknowledgement frame and sends it
back to the sensor. The hub then proceeds with “Network Validation”.
Network Validation: If the pairing-bit is set in the received frame, it indicates that the pairing is
requested. Each device then checks if the other node is currently in its own network. If not, the
node ID of the node to be paired with is validated. The node ID cannot have content outside the
mask, but it must have content within the mask. If the condition is satisfied, it (Sensor/Hub)
finds a spot for the node to be added in the network, and adds it in. The module pairing is now
complete. The sensor is allowed to pair with only one hub, whereas the hub can pair with more
than one sensor (up to four).
The sensor sets its mask back to the default value (zero) to prevent pairing with other nearby
hubs, and stores it‟s Application State (Sensor) into flash to keep it in sensor mode as the
pairing has been successful. The hub reports the change in the network to the GUI.
3.1.4. Configuration Change
The AIR BoosterStack software is capable of changing radio configuration settings on the local
node connected to the GUI as well as any paired remote nodes. The remote node does not
need to be connected to a computer to make the change. A configuration change can be
initiated from either the hub or a sensor. In either case, the change is applied to only a single
RF link. That is, if a hub has multiple sensors paired with it, only the selected sensor will make
the change. Note that this will effectively disconnect all other sensors paired with the hub.
There are two options for making the changes on the remaining sensors. The first method
requires that each sensor node be connected to a GUI. At that point each node can be
manually changed locally to the new settings. The second option, which can be done
wirelessly, requires the hub to be locally changed back to the same settings as the sensor to be
changed. Then both hub and sensor can be updated with new settings that match those of the
first sensor changed. At this point all three nodes should have the same settings. These steps
can be repeated for any remaining sensors paired with the hub until all nodes in the network
have been updated.
Figure 11 shows the handshaking involved in the configuration change sequence. The
sequence is explained below in two parts based on the Initiator operation (requests a change)
and Receiver operation (receives change request).
Page 22 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
Initiator Operation: It starts the configuration change sequence by sending out a „Config
Change Request‟ with the information of the intended new configuration. It waits for „Config
Change Request-ACK‟. This is shown in the diagram with the solid green arrows (labeled). The
green color represents the case where the request/ACK is received successfully, while the red
arrows represent the failure. If the acknowledgement is not received within the specified timeout
period, it concludes that the Receiver never received the „Config Change Request‟, so it aborts
the configuration change sequence and returns „failure‟ (red dotted arrow). If „Config Change
Request-ACK‟ is received, it switches to the new configuration itself and sends out a „Config
Change Ping‟. It awaits the response to the ping, a „Config Change Ping-ACK‟. If the
acknowledgement is received within specified timeout, it concludes that the configuration
change went through as intended and returns a „success‟ (green dotted arrow). This „Ping-ACK‟
handshake is again shown in solid green arrows, which represent that both are received
successfully by Initiator/Receiver. Red arrows under either of them represent the case of failure.
If „Config Change Ping-ACK‟ is not received within specified timeout, the Initiator starts a „Config
Ping Sequence‟. It keeps sending the „Config Change Ping‟ until the specified configuration
timeout occurs or it receives the „Config Change Ping-ACK‟, whichever is the earliest. If the
„Config Change Ping-ACK‟ is received, it concludes that either the first „Config Change Ping‟ or
first „Config Change Ping-ACK‟ did not go through as expected, but did work during the „Config
Ping Sequence‟, and returns a „success‟ (green dotted arrow). The „Config Ping Sequence‟ is
represented by green dotted lines (success/failure cannot be guaranteed at given time) in the
diagram.
If „Config Change Ping-ACK‟ is not received and the specified configuration timeout occurred, it
assumes that the Receiver never switched to the new configuration in the first place, so it
switches to the old(previous) configuration itself to try to establish the communication again. It
again starts a „Config Ping Sequence‟, now on the old (previous) configuration. This „Ping-ACK‟
handshake is again shown in solid green arrows, which represent that both are received
successfully by Initiator/Receiver. Red arrows under either of them represent the case of failure.
It keeps sending the „Config Change Ping‟ until the specified configuration timeout occurs or it
receives the „Config Change Ping-ACK‟, whichever is the earliest. If the „Config Change PingACK‟ is received, it concludes that the receiver never even switched to the new configuration for
some reason. So it stays on the old (previous) configuration to continue the communication, and
returns a „failure‟ (red dotted arrow). The „Config Ping Sequence‟ is represented by green dotted
lines (success/failure cannot be guaranteed at given time) in the diagram.
If „Config Change Ping-ACK‟ is not received and specified configuration timeout occurred even
at this time, it assumes that the Receiver did switch to the new configuration but the first „Config
Ping Sequence‟ did not go through for some reason. So in order to try to establish the
connection again, it switches to the new configuration itself, and concludes that the intended
configuration change went through and returns „success‟ (green dotted arrow).
Receiver Operation: At the receiving end, the configuration change sequence begins when a
„Config Change Request‟ is received from the Initiator. It sends „Config Change Request-ACK‟
as a response, and changes to the new configuration based on the information received from
the Initiator. It awaits the „Config Change Ping‟, or the specified configuration timeout to occur,
whichever is the earliest. If it receives „Config Change Ping‟, it sends out a „Config Change PingACK‟ and returns to application with „success‟ (red dotted arrow).
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 23 of 62
RETURN 0
If „Config Change Ping‟ is not received within specified configuration timeout, it concludes that
the Initiator never received the „Config Change Request-ACK‟, so it must not have switched to
the old(previous) configuration. The Receiver then reverts back to the old (previous)
configuration and waits for the „Config Change Ping‟ or the specified configuration timeout to
occur, whichever is the earliest. In either case, it returns to the application with „failure‟ (red
dotted arrow).
CONFIG CHANGE REQUEST
CONFIG CHANGE REQUEST-ACK
RETURN 1
RETURN TO APP
CONFIG
CHANGE
(NEW)
CONFIG
CHANGE
(NEW)
CONFIG CHANGE PING
CONFIG CHANGE PING
CONFIG CHANGE PING-ACK
CONFIG CHANGE PING
CONFIG CHANGE PING-ACK
CONFIG
CHANGE
(OLD)
CONFIG
CHANGE
(OLD)
CONFIG CHANGE PING
RETURN TO APP
INITIATOR
CONFIG CHANGE PING
CONFIG CHANGE PING-ACK
RECEIVER
RETURN 0
CONFIG TIMEOUT
CONFIG TIMEOUT
CONFIG CHANGE PING-ACK
CONFIG TIMEOUT
CONFIG CHANGE PING-ACK
CONFIG CHANGE PING
CONFIG CHANGE PING-ACK
CONFIG CHANGE PING
CONFIG CHANGE PING-ACK
CONFIG
CHANGE
(NEW)
Figure 11 - Configuration Change Diagram
RETURN TO APP
RETURN 1
CONFIG CHANGE PING
CONFIG CHANGE PING-ACK
Page 24 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
3.1.5. Remote Control Applications
Green LED: A basic remote control function is provided which allows turning on/off the green
LED on the LaunchPad board for any node in the network. From the GUI for the hub, clicking
the “GreenLED” checkbox for a node in the “Available Node List” will turn the LED on (box
checked) or off (box not checked) at the selected node.
Similarly, this feature can also be used from the GUI attached to a sensor. The only limitation is
that a sensor cannot turn on the LED of another sensor in the network. It can only control its
own LED and that of the hub it is paired with.
Since multiple nodes can be connected to a single PC/laptop with as many GUIs running
simultaneously, this feature can be used as an identifier for determining which node is
connected to a specific GUI.
Red LED: Momentarily pressing the pushbutton switch (S2) on the LaunchPad board will cause
the red LED on that node to toggle. It will also change the status of the “RedLED” checkbox for
the chosen node in the “Available Node List”.
3.1.6. Additional Features
Pushbutton Switch: The pushbutton switch (S2) on the LaunchPad board supports multi-click
and press-hold capabilities.
1) Single Click: This toggles the red LED as stated in section 3.1.5. The duration of the
button press must be less than approximately 500 milliseconds.
2) Double Click: Rapidly pressing the switch twice will indicate the current application
state of the node by blinking the red LED twice for the hub and three times for the
sensor. The duration of each button press and the time between them must be less
than approximately 500 milliseconds.
3) Triple Click: Rapidly pressing the switch three times will toggle between hub and
sensor modes. The red LED will blink after the transition to indicate the new application
state. The duration of each button press and the time between them must be less than
approximately 500 milliseconds.
4) Hold 2 Seconds: Press and hold the switch for two seconds to have the node enter
pairing mode. The red LED will blink at approximately 2Hz rate and 10% duty cycle to
indicate the button was held long enough. At this point the button may be released.
The node will continue to scan for other nodes for approximately 10 seconds.
5) Hold 5 Seconds: Press and hold the switch for five seconds to have the node change
to sensor mode followed by pairing mode. The red LED will blink at approximately
10Hz rate and 50% duty cycle to indicate the button was held long enough. At this point
the button may be released. The node will continue to scan for other nodes for
approximately 10 seconds.
6) Hold 15 Seconds: Press and hold the switch for 15 seconds to have the node clear all
of its stored settings. The red LED will blink at approximately 1Hz rate and 50% duty
cycle to indicate the button was held long enough and may be released. This sets all
values to factory default, including application state and virtual radio selection (i.e.
frequency band). The required radio setup as described in section 2.3 must be
performed again after clearing the node’s settings.
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 25 of 62
3.2. Transceiver Configurations
The Boosterpack uses the Anaren A110LR09A module, which is based on the TI CC110L chip. The
Anaren module has been certified for use under FCC/IC and ETSI using specific register settings within
the transceiver chip. The registers are shown in Figure 12. Please note that BoosterStack does not allow
any modifications of these, but instead only allows a choice of predefined values. The register settings
used in the predefined sets are provided for information only in Table 1. In addition to these settings,
predefined limits for RF output power settings (PATABLE) and maximum duty cycle settings are used
for the ETSI configurations to be compliant with the duty cycle requirements of ETSI. Note that
BoosterStack does not use listen before talk (LBT).
Register Name
Register Address (Hex)
Retained during sleep
Legend:
IOCFG2
IOCFG1
IOCFG0
FIFOTHR
SYNC1
SYNC0
PKTLEN
PKTCTRL1
PKTCTRL0
ADDR
CHANNR
FSCTRL1
FSCTRL0
FREQ2
FREQ1
FREQ0
MDMCFG4
MDMCFG3
MDMCFG2
MDMCFG1
Not Used
DEVIATN
MCSM2
MCSM1
MCSM0
FOCCFG
BSCFG
AGCCTRL2
AGCCTRL1
AGCCTRL0
Not Used
Not Used
Reserved
FREND1
FREND0
FSCAL3
FSCAL2
FSCAL1
FSCAL0
RCCTRL1
RCCTRL0
Reserved
Reserved
Reserved
TEST2
TEST1
TEST0
Not Used
PARTNUM
VERSION
FREQOFF_EST
CRC_REG
RSSI
MARC_STATE
Reserved
Reserved
PKTSTATUS
Reserved
TXBYTES
RXBYTES
Reserved
Reserved
PATABLE
FIFO
00
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
11
12
13
14
15
16
17
18
19
1A
1B
1C
1D
1E
1F
20
21
22
23
24
25
26
27
28
29
2A
2B
2C
2D
2E
2F
30
31
32
33
34
35
36
37
38
39
3A
3B
3C
3D
3E
3F
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0
0
0
0
0
0
Use the provided
Use sets of values
Any modification of this value is a
Unused/undocumented function. The
Certification is valid
certified settings as provided, others are
violation of the certification and the
provided default value must be written.
for any value
other may degrade
a violation of
customer is responsible for optaining their No assumption should be made on the
choosen
performance
certification
own certification
value read from this field
7
0
GDO_DS
0
Reserved
6
GDO2_INV
GDO1_INV
GDO0_INV
ADC_RETENTION
0
2
1
0
GDO2_CFG
GDO1_CFG
GDO0_CFG
CLOSE_IN_RX
PQT
WHITE_DATA
0
Bit Fields Within Register
4
3
5
Read only register
(burst mode read
only, command
strobes otherwise).
PKT_FORMAT
FIFO_THR
SYNC_MSB
SYNC_LSB
PACKET_LENGTH
0
CRC_AUTOFLUSH
0
DEVICE_ADDR
CHANNR
APPEND_STATUS
CRC_EN
0
ADR_CHK
LENGTH_CONFIG
FREQ_IF
FREQOFF
FREQ[23:22]=0
FREQ[21:16]
FREQ[15:8]
FREQ[7:0]
CHANBW_E
CHANBW_M
DEM_DCFILT_OFF
0
MOD_FORMAT
NUM_PREAMBLE
0
DEVIATION_E
0
0
0
0
BS_PRE_K
MAX_DVGA_GAIN
0
AGC_LNA_PRIORITY
HYST_LEVEL
DRATE_E
DRATE_M
MANCHESTER_EN
0
DEVIATION_M
RX_TIME_RSSI
RX_TIME_QUAL
7
CCA_MODE
RXOFF_MODE
TXOFF_MODE
FS_AUTOCAL
PO_TIMEOUT
0
XOSC_FORCE_ON
FOC_BS_CS_GATE
FOC_PRE_K
FOC_POST_K
FOC_LIMIT
BS_PRE_KP
BS_POST_K
BS_POST_KP
BS_LIMIT
MAX_LNA_GAIN
MAGN_TARGET
CARRIER_SENSE_REL_THR
CARRIER_SENSE_ABS_THR
WAIT_TIME
AGC_FREEZE
FILTER_LENGTH
31 (11111)
LNA2MIX_CURRENT
LODIV_BUF_CURRENT_TX
CHP_CURR_CAL_EN
VCO_CORE_H_EN
LNA_CURRENT
0
FSCAL3[7:6]
0
0
SYNC_MODE
0
0
LODIV_BUF_CURRENT
0
WOR_RES
MIX_CURRENT
PA_POWER
FSCAL3[3:0]
FSCAL2
FSCAL1
0
0
0
FSCAL0
RCCTRL1
RCCTRL0
FSTEST
PTEST
AGCTEST
TEST2
TEST1
TEST0[7:2]
1
1
0
0
CRC_OK
0
0
0
0
0
CRC_OK
0
0 TXFIFO_UNDERFLOW
0 RXFIFO_OVERFLOW
0
0
1
0
VCO_SEL_CAL_EN
TEST0[0]
PARTNUM
VERSION
FREQOFF_EST
Reserved
RSSI
MARC_STATE
CS
CCA
SFD
GDO2
NUM_TXBYTES
NUM_RXBYTES
PATABLE
TXFIFO/RXFIFO
Figure 12 - A110LR09A Transceiver Registers
GDO0
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 26 of 62
ETSI
Item Number
Adr
Register Name
M7_GFSK_38kB_18kHz
Dev_70kHzRxBW
M12_GFSK_4.8kB_13k
HzDev_60kHzRxBW
ML4_2FSK_1_2kB_237k
HzDev_675kHzRxBW
ML5_2FSK_38kB_237k
HzDev_675kHzRxBW
ML6_2FSK_100kB_237
kHzDev_675kHzRxBW
ML7_2FSK_250kB_237
kHzDev_844kHzRxBW
Allow Mask
FCC/IC
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
00
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
11
12
13
14
15
16
17
18
19
1A
1B
1C
1D
1E
1F
20
21
22
23
24
25
26
27
28
29
2A
2B
2C
2D
2E
2F
IOCFG2
IOCFG1
IOCFG0
FIFOTHR
SYNC1
SYNC0
PKTLEN
PKTCTRL1
PKTCTRL0
ADDR
CHANNR
FSCTRL1
FSCTRL0
FREQ2
FREQ1
FREQ0
MDMCFG4
MDMCFG3
MDMCFG2
MDMCFG1
MDMCFG0
DEVIATN
MCSM2
MCSM1
MCSM0
FOCCFG
BSCFG
AGCCTRL2
AGCCTRL1
AGCCTRL0
WOREVT1
WOREVT0
WORCTRL
FREND1
FREND0
FSCAL3
FSCAL2
FSCAL1
FSCAL0
RCCTRL1
RCCTRL0
FSTEST
PTEST
AGCTEST
TEST2
TEST1
TEST0
0
29
2E
06
07
D3
91
FF
04
05
00
00
06
00
20
25
ED
EA
71
13
20
F8
33
07
30
18
16
6C
43
4F
91
00
00
F8
56
10
E9
2A
00
1F
00
00
59
7F
3F
81
35
09
00
29
2E
06
07
D3
91
3D
04
05
00
00
05
00
20
25
ED
F7
75
13
20
F8
30
07
30
18
16
6C
04
4F
91
00
00
FB
56
10
E9
2A
00
1F
00
00
59
7F
3F
81
35
09
00
29
2E
06
07
D3
91
3D
04
05
00
00
0C
00
21
6B
24
15
75
03
21
E5
71
07
30
18
1D
1C
47
40
B0
00
00
F8
B7
10
E9
2A
00
1F
00
00
59
7F
3E
88
31
09
00
29
2E
06
07
D3
91
FF
04
05
00
00
0C
00
21
6B
24
1A
71
03
21
E5
71
07
30
18
1D
1C
47
40
B0
00
00
F8
B7
10
E9
2A
00
1F
00
00
59
7F
3F
88
31
09
00
29
2E
06
07
D3
91
FF
04
05
00
00
0D
00
21
6B
24
1B
E5
03
21
E5
71
07
30
18
1D
1C
47
40
B0
00
00
F8
B7
10
EA
2A
00
1F
00
00
59
7F
3F
88
31
09
00
29
2E
06
07
D3
91
3D
04
05
00
00
0D
00
21
6B
24
0D
2F
03
21
E5
71
07
30
18
1D
1C
C7
40
B0
00
00
F8
B7
10
EA
2A
00
1F
00
00
59
7F
3C
88
31
09
00
FF
FF
FF
FF
FF
FF
FF
FF
8F
FF
FF
FF
FF
00
00
00
F0
00
07
FC
00
88
FF
FF
FF
FF
FF
FF
FF
FF
FF
FF
FF
FF
FF
FF
FF
FF
FF
FF
FF
00
7F
0
FF
FF
FF
0
Table 1 -Transceiver configuration settings used in BoosterStack
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 27 of 62
3.3. AIR BoosterStack GUI
At Startup, the GUI scans for the available COM Ports and establishes a connection with one. It
starts sending commands to the module through the COM Port for the following:
Information:
1. Application Information.
2. Configuration Information.
3. Current Configuration Settings Indices.
4. Node IDs of all the nodes in the network.
5. Definitions for each data channel.
Settings:
1. Default Application State.
2. Default Pairing Mask.
3. Response Flags to get serial output from the module
The GUI displays the responses from the module on the Serial Data tab. Once the connection
with the module is validated, the COM Port number shows up in the tab „Current COM Port‟ (3).
The „Reset Serial Communications‟ (4) tab breaks the connection with the current COM port and
scans again for the available COM Ports and goes through the startup procedure again with the
module corresponding to that COM port.
Figure 13 - GUI at Startup
Page 28 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
Note: Occassionally the LaunchPad will lose communication with the PC (due to an issue with
COM port assignments), resulting in loss of communication between the BoosterStack GUI and
BoosterPack module. If this occurs, simply reboot the PC and retry communication.
Until the connection is established between the GUI and the module, none of the GUI tabs are
populated. Once the connection is established, all the tabs come up and are ready to use.
Figure 14 - GUI Populated with all the tabs
AIR BoosterPack – Users Manual
Release Date 1/18/12
No.
1
Tab Title
Embedded Versions
2
3
4
5
GUI Version
Current Com Port
Reset Serial
Communication
Pairing Help
6
7
Enable hover Options
Chart Legend
8
9
10
Hide Serial Data
Available Node List
Node Index
11
12
13
14
15
16
AIN
DIN
ID
AOUT
DOUT
App State
17
Logical Radio
18
Configuration
19
Channel#
20
RF Power
21
Apply Changes To
22
23
24
Apply Configuration
Changes
Discover Nodes
Remove Node
25
Set Node ID
Page 29 of 62
Tab Description
Current Versions of Embedded code in the sequence:
Application Level, Protocol Level, Hardware Level.
Current Version of GUI.
Current COM Port to which the GUI is connected.
Reset the current COM Port Connection.
Opens a popup window to display the text for Pairing
Help.
Enables the Hover options for the tabs.
Choose which information to show on the chart. Check
boxes appear under each Node in the current network.
Hide/Unhide the serial data window.
List of all the nodes in the network.
Node Index (Index 0 is the node itself, Index > 0 is for
the nodes connected to it in the network.)
Analog Data In (Temperature Data).
Digital Data In (Red LED).
Node ID (Generated randomly at each node).
Analog Data Out (Unused).
Digital Data Out (Green LED).
Application State Drop Down Menu (Displays current
Application State by default).
Logical Radio List Drop Down Menu (Displays current
Radio by default). Shows current Radio Index in the tab
to its left.
Configuration List Drop Down Menu (Displays current
Configuration Information by default). Shows current
Configuration Index in the tab to its left.
Channel List (Specific to each Configuration) Drop Down
Menu (Displays current Channel Information by default).
Shows current Channel Index in the tab to its left.
RF Power List (Specific to each Configuration and
corresponding Channel) Drop Down Menu (Displays
current RF Power Settings Information by default).
Shows current RF Power Index in the tab to its left.
Node ID list Drop Down Menu to decide, which node to
apply the Configuration changes to. Shows the Local (its
own) and Remote (Node connected to it) node IDs.
Apply all the Configuration changes chosen from the
Drop Down Menus.
Discover Nodes for Pairing.
Select the node from the „Available Nodes List‟ and
remove it from the Network.
Opens up a pop up box to set the desired Node ID to the
local node.
Page 30 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
Application State: At initial startup, the default application state of the module is set as „Hub‟.
The tab „App State‟ opens the drop down menu for application states (Sensor and Hub). The
chosen entry from the drop down menu is set as the current application state and is displayed in
the tab. Subsequent startups will continue to use the state selected.
Figure 15 - Application State
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 31 of 62
Set Node ID: This tab opens a popup window and allows setting the Node ID for the local node.
It takes 8 Hex characters as the Node ID.
Figure 16 - Set Node ID (Local only)
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 32 of 62
Pairing: The following section describes the pairing of two modules connected to the GUI.
Hub: The Hub is placed into pairing mode by pressing the tab „Discover Nodes‟.
Figure 17 - Discover Nodes
This sets the pairing mask on the Hub and it starts scanning for the available sensors that are in
pairing mode themselves. If the Hub establishes a connection with the Sensor, it updates its
network (node list as shown by (a)). The paired Sensor (b) shows up in the „Available Node
List‟.
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 33 of 62
Figure 18 - Hub in Pairing
Page 34 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
Figure 19 - Hub paired up with the Sensor
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 35 of 62
Sensor: The Sensor is placed into pairing mode by 2 methods:
1) By pressing the button switch on the module: This sets the pairing mask on the Sensor
and if a Hub happens to be in pairing mode at the same time, the Sensor gets paired up
with the node. It updates its network (node list as shown by (a)).
Figure 20 - Sensor in Pairing
Page 36 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
Once the Sensor is paired up with the Hub, it displays the information of the paired Hub (b) in
the „Available Node List‟, by pressing the tab „Discover Nodes‟.
Figure 21 - Sensor paired up with Hub using switch button on the module
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 37 of 62
2) By pressing the tab „Discover Nodes‟: This sets the pairing mask on the Sensor and if a
Hub happens to be in pairing mode at the same time, the Sensor gets paired up with the
node. It updates its network (node list as shown by (a)), and displays the information of
the paired Hub (b) in the „Available Node List‟.
Figure 22 - Sensor paired up with Hub using the ‘Discover Nodes’ tab
Page 38 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
Available Node List: This tab (9) shows the information about the node itself and all the nodes
it is connected to.
Figure 23 - Available Node List
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 39 of 62
DOUT: The checkbox allows the GUI to send a command to the module to toggle its Green
LED. This is to figure out which module is connected to the GUI. This is to be used only for the
local module. The following picture shows the Green LED tab checked, and remote control data
(DIN) on Red LED tab.
Figure 24 - DIN and DOUT tab Operation
Page 40 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
DIN: When the button switch is pressed on the module, it reflects the data on to the GUI and
checks the box next to Red LED. This is the remote control application where it also sends the
data to the connected remote module and checks the box corresponding to its DIN tab in the
node‟s information.
The following picture shows that the button switch has been pressed on the Sensor so the box
is checked against DIN tab. The picture above reflects this on the Sensor‟s data in the Hub‟s
node list.
Figure 25 - DIN tab Operation
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 41 of 62
Remove Node: This tab removes the paired up node from the „Available Node List‟. This
necessarily loses the pairing and removes the node from the network. (This has to be done on
both the GUIs to take effect.)
Figure 26 - Remove Node
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 42 of 62
Configuration Settings:
Logical Radio: This tab displays the information about current Logical Radio. The drop down
menu shows all the Logical Radios available. The Current Index tab represents the index of the
current radio based on the list of radios available with the module.
Figure 27 - Logical Radio
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 43 of 62
Configuration: This tab displays the information about the current Configuration of the current
Logical Radio. The drop down menu shows all the configurations available corresponding to the
Logical Radio. The Current Index tab represents the index of the current Configuration based on
the list of configurations available with the Logical Radio.
Note: When operating as a star network (more than one sensor node), a data rate greater than
1.2kBuad should be used. This is to avoid unreliable performance that can occur from a
potential data timing issue.
Figure 28 - Configuration
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 44 of 62
Channel#: This tab shows the information about the current Channel and the maximum power
level tolerable with it. The drop down menu displays all the channels available with the
corresponding to the current Configuration, corresponding to the current Logical Radio. The
Current Index tab shows the index of the current Channel# based on the ascending values of
the frequency.
Figure 29 - Channel#
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 45 of 62
RF Power: This tab shows the information about the current RF Power settings. The drop down
menu displays all the power settings tolerable to the current Channel# corresponding to the
current Configuration, corresponding to the current Logical Radio.
Figure 30 - RF Power
Page 46 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
Apply Changes To: This tab shows the chosen Node ID to which to apply the chosen
configuration settings of Logical Radio, Configuration, Channel#, RF Power. The drop down
menu shows the local Node ID and the combination of local and remote ID, for each connected
node in the network.
Figure 31 - Apply Changes To
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 47 of 62
Apply Configuration Changes: This tab is responsible for sending the command to change
the configuration settings on the nodes based on the „Apply Changes To‟ tab. If any of the
Logical Radio, Configuration, Channel# or RF Power options are changed with their drop down
menus, „Apply Configuration Changes‟ tab turns yellow to indicate that the command is to be
sent by pressing the tab.
Figure 32 - Changing Configuration Settings
Page 48 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
When the tab is pressed, it send the command to the module and based on the module‟s
response, the tab turns Red : if the Configuration Change failed, Green: if the Configuration
Change succeded. Pressing the tab again will display the current indices of the configuration
settings in the serial data tab.
Figure 33 - Configuration Change Successful
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 49 of 62
Hide Serial Data: This tab hides the serial data window. At that time, the text on the tab
changes to „Show Serial data‟ and pressing that makes the serial data window show up again.
Figure 34 - Show Serial Data
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 50 of 62
4. AIR BoosterPack Hardware
4.1. Electrical Characteristics
4.1.1. Absolute Maximum Ratings
Under no circumstances shall the absolute maximum ratings given in Table 2 be violated.
Stress exceeding one or more of the limiting values may cause permanent damage to the
device.
Caution!
ESD sensitive device. Precaution should be
used when handling the device in order to
prevent permanent damage.
Parameter
Supply Voltage
Voltage On Any
Digital Pin
Input RF Level
Storage Temperature
Range
Min
-0.3
-0.3
-50
Max
3.9
VDD + 0.3
max 3.9
+10
dBm
150
°C
Condition
V
According to JEDEC STD 22,
method A114, Human Body Model (HBM)
According to JEDEC STD 22,
400
V
C101C,Charged Device Model (CDM)
Table 2 - Absolute Maximum Ratings
750
ESD
Unit
V
V
4.1.2. Recommended Operating Conditions
Parameter
Min
Max
Unit Condition
Operating Supply Voltage
1.8
3.6
V
Operating Temperature
-40
85
°C
Table 3 - Recommended Operating Conditions
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 51 of 62
4.2. Connector Pinout
Pin
J1-1
J1-2
J1-3
J1-4
J1-5
J1-6
J1-7
J1-8
J1-9
J1-10
Name
VDD
P1.0
P1.1
P1.2
P1.3
P1.4
P1.5
P2.0
P2.1
P2.2
I/O
O
-
Pin
J2-1
J2-2
J2-3
Name
P2.3
P2.4
P2.5
J2-4
P1.6
J2-5
P1.7
I/O
O
I
I
O
Function
NC
NC
NC
MISO
Alt MOSI
MOSI
Alt MISO
I
NC
I
NC
J2-6
J2-7
J2-8
J2-9
J2-10
RST/
SBWTDIO
TEST/
SBWTCK
XOUT
XIN
GND
-
I
O
-
Function
Description
Power
Supply voltage
GDO2
Radio GDO2 output
Alt GDO0 Alternate connection to GDO0 (see Jumper Settings)
Alt CSN Alternate connection to CSN (see Jumper Settings)
Alt GDO0 Alternate connection to GDO0 (see Jumper Settings)
Alt CSN Alternate connection to CSN (see Jumper Settings)
SCLK
SPI clock
NC
NC
NC
Table 4 – J1 Connector Pinout
Description
SPI data output (master in, slave out)
Alternate connection to MOSI (see Jumper Settings)
SPI data input (master out, slave in)
Alternate connection to MISO (see Jumper Settings)
CSn
SPI chip select (active low)
GDO0
Radio GDO0 output
GND
Ground reference
Table 5 - J2 Connector Pinout
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 52 of 62
4.3. Jumper Settings
The AIR BoosterPack board provides the ability to remap several of the radio‟s I/O pins to
different MSP430 pins. JP1 thru JP5 consist of one or more 0603 SMT pads which allow a zero
Ohm resistor to be soldered in place to select the desired jumper position. The default signal
routing is determined by a small trace between one set of pads. To change jumper positions,
this trace needs to be cut and a zero Ohm resistor soldered in the new position.
Radio LaunchPad
Jumper Position Signal
Signal
Name
Name
Description
The radio‟s GDO2 pin is connected to MSP430
P1.0 by default. This pin is shared with the red
LED on the LaunchPad board.
JP1
1
GDO2
P1.0
The Demo Application does not use the GDO2
functionality and instead uses the red LED. During
the boot sequence, the radio‟s GDO2 pin is
initialized to a high-impedance state and then the
microcontroller pin is set to an output.
To use the GDO2 signal as an interrupt/status flag
from the radio, the microcontroller pin must be set
as an input. The LED will no longer be under
processor control but is still connected to the
GDO2 pin and therefore will turn on when GDO2 is
driven high by the radio. Depending on the
selected output function for GDO2, the LED may
or may not be visible or may appear to flicker.
Table 6 - JP1 Jumper Settings (GDO2)
AIR BoosterPack – Users Manual
Release Date 1/18/12
Radio LaunchPad
Jumper Position Signal
Signal
Name
Name
1
JP2
2
3
JP3
2
3
Description
The radio‟s GDO0 pin is connected to MSP430
XIN (P2.6) by default. This pin is shared with the
XIN
crystal on the LaunchPad board. If the crystal is
installed, a different jumper setting must be used.
Use this setting for GDO0 if the crystal is used and
UART functionality is required. This pin is shared
GDO0
P1.3
with the pushbutton switch, so the switch should
not be pressed with this setting unless GDO0 has
been configured as a high-impedance output.
Use this setting for GDO0 if the crystal is used and
the pushbutton switch is needed. This pin is
P1.1
shared with RXD, so the UART will be unavailable
with this setting.
Table 7 - JP2 Jumper Settings (GDO0)
Radio LaunchPad
Jumper Position Signal
Signal
Name
Name
1
Page 53 of 62
Description
The radio‟s CSN pin is connected to MSP430
XOUT (P2.7) by default. This pin is shared with
XOUT
the crystal on the LaunchPad board. If the crystal
is installed, a different jumper setting must be
used.
CSN
Use this setting for CSN if the crystal is used and
P1.4 is used for another function. This pin is
P1.2
shared with TXD, so the UART will be unavailable
with this setting.
Use this setting for CSN if the crystal is used and
P1.4
UART functionality is required.
Table 8 - JP3 Jumper Settings (CSN)
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 54 of 62
Radio LaunchPad
Jumper Position Signal
Signal
Name
Name
1
JP4
2
Use this setting for MSP430 microcontrollers with
a Universal Serial Interface (USI) that output serial
P1.6
data on P1.6 (SDO) when communicating via the
SPI bus.
The radio‟s MOSI pin is connected to MSP430
MOSI
P1.7 by default. Use this setting for MSP430
microcontrollers with a Universal Serial
P1.7
Communication Interface (USCI) that output serial
data on P1.7 (MOSI) when communicating via the
SPI bus.
Table 9 - JP4 Jumper Settings (MOSI)
Radio LaunchPad
Jumper Position Signal
Signal
Name
Name
1
JP5
2
Description
Description
The radio‟s MOSI pin is connected to MSP430
P1.6 by default. Use this setting for MSP430
microcontrollers with a Universal Serial
P1.6
Communication Interface (USCI) that input serial
data on P1.6 (MISO) when communicating via the
MISO
SPI bus.
Use this setting for MSP430 microcontrollers with
a Universal Serial Interface (USI) that input serial
P1.7
data on P1.7 (SDI) when communicating via the
SPI bus.
Table 10 - JP5 Jumper Settings (MISO)
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 55 of 62
4.4. Schematics
Figure 35 - Schematics
Page 56 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
4.5. PCB Layout
Figure 36 - PCB Layout Top Layer
Figure 37 - PCB Layout Bottom Layer
AIR BoosterPack – Users Manual
Release Date 1/18/12
Figure 38 - PCB Layout Top Silkscreen
Figure 39 - PCB Layout Bottom Silkscreen
Page 57 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 58 of 62
4.6. Bill of Materials (BOM)
Item
1
2
3
Ref Des
C1,C3
C2
C4
Qty
1/1 NP
1 NP
1
Description
CAP CER .1UF 16V 10% X7R 0603 SMD
CAP CER 1000PF 50V 10% X7R 0603 SMD
CAP CER 10UF 6.3V X5R 0603 SMD
Comment
C1 not populated
Not populated
Not populated
4
D1
1 NP
LED 0603 RED SMD
5
6
7
8
9
10
J1,J2
JP1
JP2,JP3
JP4,JP5
R1
R2
2
1 NP
2 NP
2 NP
1 NP
1 NP
CONN SOCKET 10POS 2.54MM SINGLE ROW
RES 0.0 OHM 1/10W 0603 SMD
RES 0.0 OHM 1/10W 0603 SMD
RES 0.0 OHM 1/10W 0603 SMD
RES 47K OHM 1/10W 5% 0603 SMD
RES 150 OHM 1/10W 5% 0603 SMD
11
S1
1 NP
SWITCH TACT SPST NO SMD
12
U1
1
RADIO MMODULE LR09A SMD
OSRAM
LS L29K-G1J2-1-Z
(or equivalent)
Not populated
Not populated
Not populated
Not populated
Not populated
Not populated
Omron
B3U-1000P
Not populated
13
U2
1 NP
SOCKET DIP20
Table 11 - Bill of Material
Aries
20-3518-10
(or equivalent)
AIR BoosterPack – Users Manual
Release Date 1/18/12
5. Range Test
Page 59 of 62
AIR BoosterPack – Users Manual
Release Date 1/18/12
Page 60 of 62
HISTORY
Date
10/16/11
12/14/11
1/18/12
Author
Change Note No./Notes
Initial Draft
Added multi-purpose pushbutton controls.
Pairing method changed.
Improved green LED remote control function.
Added section for radio register settings.
Added notes on radio operation and
LaunchPad COM port.
THIS PAGE LEFT INTENTIONALLY BLANK
Thank you for learning more about the
Anaren Integrated Radio (AIR) module line.
If you have additional questions,
need samples, or would like a quote –
please do not hesitate to email the AIR team
at AIR@anaren.com or contact any of these
authorized distributors of the AIR product line.
Worldwide
North America
Anaren Microwave, Inc.
6635 Kirkville Road
East Syracuse, NY 13057
Tel: +1 315 432 8909
+1 800 411 6596
Fax: +1 315 432 8970
Anaren Microwave (Europe), Inc.
12 Somerset House, Suite 16 & 17
Hussar Court, Waterlooville
Hampshire, England P07-7SG
Tel: +44 2392 232392
Fax: +44 2392 251369
Worldwide
Anaren Communication Suzhou Co. Ltd.
No. 5 Chun Hui Road
Wei Ting, Suzhou Industrial Park
Suzhou 215122, PR China
Tel: +86 512 6287 6400
Fax: +86 512 6274 9283