RN-171-PICTAIL

    RN -13 1/1 71 -PICT AIL-U M RN-131-PICTAIL & RN-171-PICTAIL Evaluation Boards © 2012 Roving Networks. All rights reserved. RN-131/171-PICTAIL-UM Version 1.1 9/20/2012 USER MANUAL RN -13 1/1 71-PICT AIL-U M   OVERVIEW The RN-131 and RN-171 WiFly radio modules are complete, standalone wireless LAN access devices. Each module contains a TCIP/IP stack and related applications. After the module is configured, the radio can access the Wi-Fi network automatically, and transmit and receive data over a UART. General Description The RN-131-PICTAIL and RN-171-PICTAIL evaluation boards work seamlessly with the Microchip Technology PIC18 Explorer Development Board. The evaluation boards plug into the PICtail™ modular connector on the PIC18 Explorer Board, and add wireless functionality to PIC18-based microcontroller designs. The evaluation boards are preloaded with firmware to simplify integration and minimize application development. In the simplest configuration, the hardware only requires four connections (PWR, TX, RX, and GND) to create a wireless data connection. The microcontroller can communicate with the boards via the UART and SPI interfaces, and can drive LEDs, wake the boards, and reset them. The evaluation boards are updated and controlled with a simple ASCII command language. Once the boards are set up, they can scan to find an access point, associate, authenticate, and connect over any Wi-Fi network. The PIC18 Explorer Board (DM183032) is a development platform equipped with a 28-pin PICtail connector and PIM that can accommodate various versions of the 8-bit PIC16 and PIC18 microcontroller families. The PIC18 Explorer Board’s 8-bit microcontroller communicates with the RN-131-PICTAIL/RN-171-PICTAIL evaluation board via the PICtail connector. This document describes how to use the RN-131-PICTAIL/RN-171-PICTAIL evaluation board connected to a PIC18 Explorer Board to associate with a Wi-Fi network and communicate with other devices within a LAN. Communication with other LAN devices is performed using telnet. RN-131-PICTAIL/RN-171-PICTAIL Module Features • FCC/CE/IC certified 2.4-GHz IEEE 802.11b/g transceiver • Plugs into the PICtail Plus connector on the PIC18 Explorer and Explorer 16 Development Boards • Adds wireless capability to designs targeting the PIC18 Explorer and Explorer 16 boards • Configurable transmit power: 0 to 10 dBm (RN-171-PICTAIL) • PCB trace antenna (RN-171-PICTAIL) and on-board ceramic chip antenna (RN-131-PICTAIL) • Ultra-low power o 4-uA sleep, 38-mA Rx, 120-mA Tx at 0 dBm (RN-171-PICTAIL) o 4 uA sleep, 40 mA Rx, 210 mA Tx (RN-131-PICTAIL) • High throughput: 921 Kbps TX, 500 Kbps RX data rate with TCP/IP and WPA2 over UART, up to 2 Mbps over SPI slave • UART interface with hardware flow control • SPI interface with slave interrupt • Real-time clock for wakeup and time stamping • 3 status LEDs (2 configurable) • Powered by PIC18 Explorer and Explorer 16 boards • Supports ad hoc and infrastructure networks • Wi-Fi Alliance certified for WPA2-PSK • Complete on-board TCP/IP networking stack • Environmentally friendly: RoHS compliant www.rovingnetworks.com Version 1.1 9/20/2012 2 RN -13 1/1 71-PICT AIL-U M   Demo Applications The example applications provided with this document include an MPLAB X project and 2 pre-compiled .hex files. • The MPLAB X project files provide a sample 8-bit application framework that you can customize to configure and control the RN-131/RN-171 from an 8-bit Microchip microcontroller. • You use the pre-compiled sample application ConfigureInCmdMode.hex to configure the RN-131/RN-171 module. • SampleTelnetApp.hex accepts specific telnet commands from a remote device and turns on/off the LEDs on either the RN-131/RN-171 module or the PIC18 Explorer Development Board. The following sections describe these applications in detail. GETTING STARTED This section describes how to setup up the PIC18 Explorer Board and to run the sample demo applications. Hardware Requirements To run the demo applications, you need the following hardware: • RN-131-PICTAIL or RN-171-PICTAIL evaluation board • PIC18 Explorer Development Board equipped with a PIC18F87J11 PIM (MA180020) • Microchip programmer (e.g., ICD3 or Real Ice) • 2 jumper wires to configure jumpers J4 and J13 on the PIC18 Explorer Board NOTE: You cannot use the default jumper settings for J4 and J13. Instructions for configuring the jumpers are provided in “Demo Setup” on page 4. • 802.11b/g-compliant Wi-Fi access point • Serial cable or USB-to-serial converter cable Software Requirements You need the following software tools/applications to run the demo applications: • Terminal emulator application such as TeraTerm or CoolTerm—You will use the terminal emulator to send configuration commands to the module over a UART interface. The emulator also displays information transmitted from the module. • MPLAB X version 1.2 or higher—You will use this application with the programmer to load the application into the PIC, and to modify and customize the application. • XC8 v1.10 compiler—You will use the compiler to build a customized application. Sample Application Code You can obtain the sample application code described in this user manual at www.microchip.com/wireless. www.rovingnetworks.com Version 1.1 9/20/2012 3 RN -13 1/1 71-PICT AIL-U M   Demo Applications This section demonstrates how to use the demo applications to accomplish the following tasks: • Configure the module to join a known, user-specified access point automatically. • Communicate with the module via a telnet session to turn on/off LEDs using a command set that the application running on the PIC recognizes. Set Up Hardware Perform the following steps to set up the hardware and prepare it for configuration: 1. Plug the RN-131-PICTAIL/RN-171-PICTAIL evaluation board into the PIC18 Explorer Board’s PICtail connector. See Figure 1. Figure 1. Modules Connected to PIC18 Explorer Board RN-171-PICTAIL Connected to the PIC18 Board RN-131-PICTAIL Connected to the PIC18 Board     2. Configure the PIC18 Explorer Board’s J4 and J13 jumpers as shown in Figure 2. This configuration is for command mode operation. www.rovingnetworks.com Version 1.1 9/20/2012 4 RN -13 1/1 71-PICT AIL-U M   Figure 2. Jumper Selection for Command Mode Operation   3. Connect a serial cable from the PIC18 Explorer Board’s DE9 connector to the PC. If you are using a laptop that does not have a serial connector, use a USB-to-serial converter cable to connect the serial cable to the laptop’s USB port. 4. Connect the programmer to the PIC18 Explorer Board and apply power. Program the PIC18F87J11 & Configure the RN-131/RN-171 In this step you configure the RN-131/RN-171 modules so that they automatically search for, and join, a preferred access point. First, you use the following steps to program the PIC18F87J11 with software that allows the RN-131/RN-171 to be configured for its current operating environment. These steps are specific to the PIC18 Explorer Board because of the way in which the UARTs are connected on the board. 1. 2. Using the MPLAB X IDE and the programmer, load the ConfigureInCmdMode.hex file into the PIC18F87J11. This application performs two important tasks: • It configures the PIC18F8i7J11 I/O pins appropriately. • It allows the UART signal to traverse from the Explorer 18 board’s DE9 connector to the RN-131-PICTAIL/RN-171-PICTAIL, temporarily bypassing the PIC (this step is specific to the PIC18 Explorer Board). Open your terminal emulator to the COM port of the PIC18 Explorer Board/RN-131-PICTAIL/RN-171-PICTAIL. The serial port settings are 9600 baud, 8-bits data, no parity, 1-stop bit, and no flow control. www.rovingnetworks.com Version 1.1 9/20/2012 5 RN -13 1/1 71-PICT AIL-U M   3. Type the following commands in the console of your terminal emulator: $$$ This command places the RN-131/RN-171 module in command mode. scan The device scans for networks and produces a list of available access points (see Figure 3 for an example). The access point to which you wish to connect should be listed. If it is not, repeat the scan command. join # XX Associate with the access point, where XX is the access point’s number interest as shown in the scan report. leave This command asks the device to leave the network. Figure 3. Access Point List   4. Store the parameters from step 3 into the RN-131/RN-171 module’s non-volatile memory so that they can be used in the next application you run on the PIC18F87J11. Type the following commands in the console of your terminal emulator: set wlan ssid RovingNET). Set the network’s SSID where is the SSID (e.g., set wlan ssid set wlan pass Set the passphrase to use when joining where is the passphrase (e.g., set wlan pass duckmauifries). save Save the settings to persistent storage; reused when joining. reboot Reboot the module so that the settings take effect. Data Mode Operation In the following steps you load an application into the PIC18F87J11 that allows the RN-131/RN-171 module to operate in data mode and accept a telnet connection request. Additionally, the application lets you control the module’s LEDs by sending specific PIC commands. 1. Configure the jumpers J4 and J13 as shown in Figure 4. This setting allows the PIC’s UART to communicate with RN-131/RN-171 module’s UART via the PICtail connector, and also allows the module’s transmitted data to echo back to the terminal emulator’s console. (This setting is specific to the PIC18 Explorer Board.) www.rovingnetworks.com Version 1.1 9/20/2012 6 RN -13 1/1 71-PICT AIL-U M   Figure 4. Data Mode Operation Jumper Selection   2. Use the MPLAB X IDE and the programmer to load the SampleTelnetApp.hex demo application into the PIC18F87J11. 3. Press the MCLR reset button on the Explorer 18 board and observe the output transaction on the terminal emulator console. A normal sequence is similar to that shown in Figure 5, i.e., the device is associated with the designated access point, and the yellow LED on the RN-131-PICTAIL/RN-171-PICTAIL is illuminated. www.rovingnetworks.com Version 1.1 9/20/2012 7 RN -13 1/1 71-PICT AIL-U M   Figure 5. RN-131/RN-171 Association Start-Up Sequence   4. NOTE: In the console, note the IP address that the access point assigns to the RN-131/RN-171 module. The IP is unique to each wireless environment’s DHCP server. You will use this IP address to open a telnet session with the device. The application source code includes a file called ConfigApp.h. Two parameters in this file establish which SSID and passphrase is used if the default access point cannot be found: #define NETWORK_SSID "xxxstringxxx" #define NETWORK_PASS "yyystringyyy" You can change these parameters to match your local network environment. Then, rebuild and re-load the updated application. The application then uses these settings to search for the access point to join, in case the default device parameters stored in the device cannot be found or if found, they do not allow association. www.rovingnetworks.com Version 1.1 9/20/2012 8 RN -13 1/1 71-PICT AIL-U M   The RN-131/RN-171 module is now associated to an access point and is operating in data mode. Use the following steps to open a telnet session with the device and send it commands: 1. Associate your computer’s Wi-Fi connection with the same access point as the RN-131/RN-171 module. 2. On your computer, open a command line session and type the command: telnet 2000, where is the IP address of the RN-131/RN-171 module. For example: telnet 192.168.1.50 2000 2000 is the port number on which the RN-131/RN-171 module listens for telnet session commands. 3. The telnet console should display the echoed response *HELLO*. 4. Anything you type in the telnet console, followed by a , is echoed on the RN-131/RN-171 module’s console. Type some random strings and observe the echoing. 5. The PIC18F87J11 connected to the RN-131/RN-171 module can recognize and act on the following commands: MOD_TON_GRN MOD_TOFF_GRN EXP_TON_LED1 EXP_TOFF_LED1 EXP_TON_LED2 EXP_TOFF_LED1 Turn on module’s green LED. Turn off module’s green LED. Turn on Explorer Board’s D8 LED. Turn off Explorer Board’s D8 LED. Turn on Explorer Board’s D7 LED. Turn off Explorer Board’s D7 LED. Type one of these commands in the telnet console, either by itself or embedded in a longer string, followed by a . Observe that you can turn on or off the appropriate LEDs on either the evaluation board or the PIC18 Explorer Board. You have completed the application demonstration. The next section describes how the software is designed for PIC18 microcontroller. www.rovingnetworks.com Version 1.1 9/20/2012 9 RN -13 1/1 71-PICT AIL-U M   SAMPLE APPLICATION DESIGN This chapter provides a high-level overview of how the sample demo application was designed, and shows some of the APIs you can use to communicate with RN-171 module. Demo Application Flow Diagram Figure 6 shows the demo application flow diagram. Figure 6. Flow Diagram Power Up Initialize Explorer 18 Hardware Initialize PIC18 UART Reset RN-171 Module Check RN-171 Status no Associated? yes Set Command Mode Enable RCV INT Configure & Save Process Commands Reboot   Initialize the PIC18 Explorer Board Hardware During this processing stage, the void BoardIint(void) API function performs the following tasks: • Chooses the external 10-MHz crystal as the clock source. • Configures the ports/pins as digital and selects their direction to match the functional requirements of the PICtail connector. • Turns off the LEDs. • Clears the interrupt flags. • Disables the peripheral interrupts. www.rovingnetworks.com Version 1.1 9/20/2012 10 RN -13 1/1 71-PICT AIL-U M   Initialize the PIC’s UART The void ConsoleInit(void) API function initializes the PIC’s UART1, which communicates with the RN-131/RN-171 module. It sets the UART’s baud rate to 9600 baud, 8 bits data, 1 stop bit, no parity, and no flow control. These settings are the default for the RN-131/RN-171 module. To change the baud rate, modify the #define BAUD_RATE 9600 macro in the console.h header file, and re-initialize the UART. The ConsoleInit( ) function enables both transmit and receive UART capabilities, but their respective interrupts are disabled until the application is prepared to receive them. Later, receive interrupts are enabled. Transmit interrupts remain disabled. Reset the RN-171 Module The PICtail connector has an active-low reset pin (RB1) that is used to reset the RN-131/RN-171 module after the PIC18 Explorer Board and UART are properly initialized. The void rn_reset_wifi(void) API function is used for this reset operation. It transitions the reset pin from high to low, holds the pin low for 10 ms, and then returns it high. This reset action triggers the module to begin its joining procedure. Check Module’s Status Immediately after resetting the module, the PIC’s UART receiver interrupt is enabled. This process prepares the PIC to receive the information that is transmitted from the RN-171’s UART as it goes through its start up procedure. The PIC18 parses the RN-171 output and searches for the module’s IP address if it was successful in associating with an access point. If a valid IP address is received, the assumption is made that the device is safely on a network and is in data mode. In this case, the PIC18 waits to receive commands from the RN-131/RN-171 module in an endless loop. The PIC18 acts on each valid command as it receives it. Command Mode If the PIC18 application detects that the RN-171 module was not successful in its start-up attempt to associate with an access point, the PIC’s application attempts to instruct the module to associate with a specific access point. The PIC18 application sends the following commands to the module in sequence: $$$ Put the module into command mode. set wlan ssid Set the network’s SSID where is the SSID. set wlan pass Set the passphrase to use when joining where is the passphrase. save Save the settings to persistent storage; reused when joining. reboot Reboot the module so that the settings take effect. When successful, the module reboots and associates with the specified access point. The following section describes the APIs used to carry out these operations. www.rovingnetworks.com Version 1.1 9/20/2012 11 RN -13 1/1 71-PICT AIL-U M   Primary Module Communications API Functions The API function that tells the device to go into command mode is: err_t module_send_cmd(const char *response, const char *fmt, ...) This function accepts 2 or more parameters (i.e., a variable length parameter list). The first parameter, response, is the reply expected from the RN-171 module after it has processed the command. The command is carried in the fmt parameter. For example, if the function is called as follows: retValue = err_t module_send_cmd(“CMD”, “$$$”); The command is $$$ and the expected return is CMD. For a more complex instantiation such as: retValue = module_send_cmd(CMD_AOK, "set wlan ssid %s", NETWORK_SSID) The variable parameter list is essential to properly resolve the %s into the value of the NETWORK_SSID macro. The next API demonstrates how you can combine individual commands inside a single function to carry out a more complex operation, such as joining a network. The following API function forces the device into command mode, saves the SSID and passphrase, and reboots the module. err_t module_network_connect(void); Internally, it sends a total of 5 commands.: module_send_cmd("CMD", "$$$") module_send_cmd(CMD_AOK, "set w s %s", NETWORK_SSID) module_send_cmd(CMD_AOK, "set w p %s", NETWORK_PASS) module_send_cmd(NULL, "save") module_send_cmd(NULL, "join") This function represents a typical API that sends a sequence of commands to the module to carry out a complex task. Most applications follow a similar pattern. RESOURCES & RELATED DOCUMENTS For more information, refer to the following sources, which are available on the Support page on the Roving Networks website at http://www.rovingnetworks.com/support.php: • RN-171 Data Sheet • RN-131 Data Sheet • Advanced User Manual • WiFly Training Presentation • Drivers, tools, and utilities www.rovingnetworks.com Version 1.1 9/20/2012 12 RN -13 1/1 71-PICT AIL-U M   BOARD SCHEMATICS Figures 7 and 8 show the schematics for the RN-131-PICTAIL and RN-171-PICTAIL evaluation boards, respectively. Figure 7. RN-131-PICTAIL Board Schematic Vin U2 UART_TX 1 SEN3 32 33 SEN0 TC1262- 3.3V Vin C4 10uF 3k3 31 Vout 34 VDD3V3 3 i Power Net C3 10uF GPIO_5 29 GPIO_4 30 SENSOR_1 31 SENSOR_2 32 SENSOR_3 33 SENSOR_POWER 34 SENSOR_0 SUPERCAP_BAL ANCE 8 EPC_B 7 EPC_A 6 RESET 5 MI SO 100k R15 SI RQ 100k R13 R21 3 SENSOR_4 2 SENSOR_6 1 PI C_CTS 9 WAKEUP 8 7 6 5 RESET 4 3 2 1 D6 D5 1 3 5 7 2 4 6 8 PI C_TX RESET UART_TX J3 ISP Connector D4 SS 100k PI C_TX Green L E D Y ellow L E D R16 ISP_ T X WAKEUP ISP_ R X ST A T US_L E D 100k PIC_L E DR MOSI PIC_L E DY R17 4 SENSOR_5 PI C_RTS 10 VDD3V3 STATUS_L ED 100k R ed L E D R14 SENSOR_7 PI C_TX 11 i Power Net S2 VDD3V3 14 14 SPI_MOSI 16 15 SPI_SCK 15 16 SPI_MISO 17 17 SR E G_OUT 19 18 19 18 GND SR E G_IN 21 20 28 UART_TX 44 GND Vin i Power Net SEN2 GPIO_6 9 13 12 44 29 27 FORCE_AWAKE 43 GND 28 MOSI GPIO_7 42 GND MI SO 26 UART_RTS(GPI O_13) 10 43 R12 PI C_RX PI C_TX SEN2 SEN3 1 2 3 4 27 30 2 ISP_TX ISP_RX SI RQ PI C_RTS PI C_CTS SS PI CTAI L 28 Pin 26 GPIO_8 41 GND J1 MOSI MI SO SCK T ab PI C_L EDR PI C_L EDY WAKEUP RESET SI RQ STATUS_L ED 2 4 6 8 10 12 14 16 18 20 22 24 26 28 GND PI C_RX PI C_TX RA5 RA4 RA3 RC5 RC4 RC3 RA0 RA1 RA2 RC0 RC1 RC2 V_VAR GND 25 UART_CTS(GPI O_12) 11 4 1 RE2 3 RE3 5 RA7/OSC1 7 RA6/OSC2 9 RC7 11 RC6 13 RB7 15 RB6 17 RB5 19 RB4 21 RB3 23 RB2 25 RB1 27 RB0 25 GPIO_9 41 SS UART_RX(GPI O_11) 12 24 42 24 M2 RN131 Module UART_TX (GPI O_10) 13 SP_RX I 40 GND SCK 23 39 GND 23 38 GND ISP_RX 39 PI CTAI L PLUS 30 Pin 40 RESET WAKEUP B A T T 20 22 ISP_T X VDD3V3 V DD 21 22 PI C_L EDR SI RQ PI C_RTS 38 J2 VDD3V3 ISP_TX 36 GND PI C_CTS VDD3V3 PI C_RX PI C_TX 37 GND PI C_L EDY 2 RF2/U1RX_E 4 RF3/U1TX_E 6 RG2/SCL 1 8 RG3/SDA1 10 GND 12 RB1/AN1 14 RB4/AN4 16 GND 18 RE8/I NT1 20 RD15/U1RTS_E 22 3.3V 24 5V 26 9V 28 RF0 30 RF1 36 1 RB2/SS1/AN2 3 RF6/SCK1 5 RF7/SDI 1_E 7 RF8/SDO1_E 9 GND 11 RB0/AN0 13 RB3/AN3 15 GND 17 RE9/I NT2 19 RD14/U1CTS_E 21 3.3V 23 5V 25 9V 27 RG0 29 RG1 37 SS SCK MI SO MOSI SEN0 220k www.rovingnetworks.com R22 R20 220R R19 220R R18 220R 100k   Version 1.1 9/20/2012 13 RN -13 1/1 71-PICT AIL-U M   Figure 8. RN-171-PICTAIL Board Schematic VDD3V3 2 4 6 8 A1 PI C_TX RESET UART_TX 31 SEN3 32 33 PI CTAI L PLUS 30 Pin 34 VDD3V3 35 36 1 RE2 3 RE3 5 RA7/OSC1 7 RA6/OSC2 9 RC7 11 RC6 13 RB7 15 RB6 17 RB5 19 RB4 21 RB3 23 RB2 25 RB1 27 RB0 PI C_RX PI C_TX PI C_L EDR PI C_L EDY WAKEUP RESET SI RQ RA5 RA4 RA3 RC5 RC4 RC3 RA0 RA1 RA2 RC0 RC1 RC2 V_VAR GND J1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 PI CTAI L 28 Pin 37 38 MOSI MI SO SCK 39 PI C_RTS PI C_CTS SS RESET 40 WAKEUP 41 42 Vin i Power Net PI C_CTS 43 PI C_RTS 44 PI C_TX 45 UART_TX 46 UART_TX VDD3V3 R2 SI RQ 100k 2 R1 VDD3V3 SS D3 100k 3 T ab GND Vout 4 C2 10uF TC1262- 3.3V C1 10uF PI C_TX R6 220k SEN0 R7 Green L E D Y ellow L E D R3 Vin R11 220R D2 R10 220R 21 23 22 21 GND GND GND 22 23 24 24 25 GND SENSOR_1 SPI _MOSI 18 31 SENSOR_2 32 SENSOR_3 33 SENSOR_POWER 34 VDD_3V3_RF 35 SENSOR_4 GPI O_1 13 36 SENSOR_5 GPI O_2 12 37 SENSOR_6 GPI O_3 11 38 SENSOR_7 39 GND GPI O_4 9 40 RESET GPI O_5 8 41 FORCE_AWAKE GPI O_6 7 42 GPIO_14 GPI O_7 6 GND 20 SPI _MI SO 16 GND 14 10 GPIO_13 (UART_RTS) GPI O_8 5 44 GPIO_12 (UART_CTS) GPI O_9 4 45 GPIO_11 (UART_RX) 46 GPIO_10 (UART_TX) 47 GND 19 18 16 15 FL ASH_CS 15 VDD_3V3 20 17 SPI _SCK 17 43 ST A T US_L E D MI SO 100k PIC_L E DR MOSI R5 U1 30 STATUS_L ED 100k 1 19 100k R4 S1 Vin VDD_3V3_SW 49 R8 3k3 PIC_L E DY PI C_RX PI C_TX SEN2 SEN3 1 2 3 4 R ed L E D ISP_TX ISP_RX SENSOR_0 49 47 GND 29 3V 3_R E G_CT R L RESET WAKEUP SEN2 28 ISP_RX 3 ISP_TX 2 GND 1 14 13 12 11 10 VDD3V3 9 MOSI 8 MI SO 7 SI RQ 6 STATUS_L ED 5 SS 4 SCK 3 ISP_RX 2 ISP_TX 1 48 VDD3V3 A NT E NNA 27 30 SI RQ PI C_RTS 26 29 V BATT J2 28 SEN0 PI C_L EDR M1 RN171 Module 48 PI C_CTS VDD3V3 PI C_RX PI C_TX 27 PI C_L EDY 2 RF2/U1RX_E 4 RF3/U1TX_E 6 RG2/SCL1 8 RG3/SDA1 10 GND 12 RB1/AN1 14 RB4/AN4 16 GND 18 RE8/I NT1 20 RD15/U1RTS_E 22 3.3V 24 5V 26 9V 28 RF0 30 RF1 GND 1 RB2/SS1/AN2 3 RF6/SCK1 5 RF7/SDI 1_E 7 RF8/SDO1_E 9 GND 11 RB0/AN0 13 RB3/AN3 15 GND 17 RE9/I NT2 19 RD14/U1CTS_E 21 3.3V 23 5V 25 9V 27 RG0 29 RG1 GND SS SCK MI SO MOSI 25 RF Net i J3 ISP Connector 26 1 3 5 7 ISP_ T X WAKEUP ISP_ R X VDD3V3 D1 R9 220R 100k     www.rovingnetworks.com Version 1.1 9/20/2012 14 RN -13 1/1 71-PICT AIL-U M   NOTES   www.rovingnetworks.com Version 1.1 9/20/2012 15 RN -13 1/1 71-PICT AIL-U M   Copyright © 2012 Roving Networks. All rights reserved. Roving Networks is a registered trademark of Roving Networks. Apple Inc., iPhone, iPad, iTunes, Made for iPhone are registered trademarks of Apple Computer. Roving Networks reserves the right to make corrections, modifications, and other changes to its products, documentation and services at any time. Customers should obtain the latest relevant information before placing orders and should verify that such information is current and complete. Roving Networks, Inc. 102 Cooper Court Los Gatos, CA 95032 +1 (408) 395-5300 www.rovingnetworks.com www.rovingnetworks.com Roving Networks assumes no liability for applications assistance or customer’s product design. Customers are responsible for their products and applications which use Roving Networks components. To minimize customer product risks, customers should provide adequate design and operating safeguards. Roving Networks products are not authorized for use in safety-critical applications (such as life support) where a failure of the Roving Networks product would reasonably be expected to cause severe personal injury or death, unless officers of the parties have executed an agreement specifically governing such use. Version 1.1 9/20/2012 16