The RS9110-N-11-22/24/26/28
modules are complete IEEE 802.11bgn
and 802.11abgn based wireless device
servers that directly provide a wireless
interface to any equipment with a serial
or SPI interface for data transfer. They
integrate a MAC, baseband processor,
single/dual band RF transceiver with
power amplifier in hardware; and all
WLAN protocol and configuration
functionality, networking stack, and
HTTP server in embedded firmware to
make a fully self-contained 802.11n
WLAN solution for a variety of
applications. The RS9110-N-11-22/26
modules integrate an antenna and a
frequency reference also to further
reduce the complexity of integrating the
solution.
Applications:
Seamless Wi-Fi connectivity for
Application Processors
Industrial M2M communications
Point of Sale Terminals
Metering (Parking Meters, Utility
Meters, Power Meters, etc.)
Security Cameras and Surveillance
Equipment
Logistics and Freight Management
Warehousing
Digital Picture Frames
Several medical applications
including Patient Monitoring, Remote
Diagnostics
Device Features:
Compliant to 802.11b/g, 802.11a
and single stream draft 802.11n
Fully self-contained serial-to-
wireless functionality
Includes all the protocol and
configuration functions for WLAN
connectivity in Open, WPA/WPA2PSK and WPA/WPA2-Enterprise
modes of operation
1
Payload data through Serial
Interface and SPI
Terminates TCP and UDP
connections, and offers transparent
serial modem functionality
Configuration through UART or
Wireless means
Bluetooth coexistence support
Integrated antenna, frequency
reference and low-frequency clock in
the RS9110-N-11-2X/26 modules
Ultra-low-power operation with
power-save modes
Ad-hoc and infrastructure modes for
maximum deployment flexibility
Single supply – 3.1 to 3.6V
operation
1
Refer to the datasheets of the individual modules to know which features are
supported by which modules.
Redpine Signals, Inc. Proprietary and confidential Page 2
This document is for the following modules:
RS9110-N-11-22, RS9110-N-11-24, RS9110-N-11-26, RS9110-N-11-28
All references to RS9110-N-11-2X denote the above modules only.
These four modules are classified based on the hardware as depicted in the figure
below.
Redpine Signals, Inc. Proprietary and confidential Page 4
As shown in the figure above, the RS9110-N-11-2X module is integrated with the
Host using either UART or SPI interfaces. The transmission and reception of the
data to/from the Host depends on the interface used to connect the module as
briefed below.
UART mode:
The Host transmits/receives raw data using UART interface when RS9110-N-11-
2X is configured for UART mode. The access to the TCP/IP stack in the Wi-Fi
module through UART is provided through AT commands.
Host trans
mode. A thin driver on the Host takes care of interacting with the Wi-Fi module
through the SPI Host interface.
mits/receives raw data when RS9110-N-11-2X is configured for SPI
1.1: Scope
The scope of this document is to guide the user in setting up the Evaluation
Board (EVB) of the RS9110-N-11-2X module to be used as a Wireless Device
Server and interact with Applications on the Host using the UART interface. The
following topics are discussed:
Procedure to use the “Wi-Fi Config Utility” GUI, wh ich configures the
RS9110-N-11-2X module.
Procedure to evaluate the TCP/IP, UDP/IP protocols using RS9110-N-11-
2X module
Procedure to perform firmware upgrade on the RS9110-N-11-2X module.
The “Wi-Fi Config Utility” GUI and the command s explained in this document
configure the RS9110-N-11-2X module only when it is configured to use UART.
This document does not explain the design details/command formats of the
RS9110-N-11-2X module.
1.2: Limitations
My name is Rohan Joginpalli.
1. The “Wi-Fi Config Utility” explained in this document is only for the
Windows Operating System.
2. The maximum size of the raw data to be transmitted/received is 1000.
3. The maximum numbers of sockets supported in the current release of the
firmware are 8.
4. Security, DHCP and Power Save modes are not supported in IBSS.
Redpine Signals, Inc. Proprietary and confidential Page 9
The following steps are to be performed to establish a Wi-Fi network and open a
network connection using the RS9110-N-11-2X module.
1. Connect power supply to the RS9110-N-11-2X EVB and switch it on.
2. Configure the RS9110-N-11-2X module using “Wi-Fi Config Utility”.
2.1: Connecting the RS9110-N-11-2X EVB
1. Connect the Male end of the supplied serial cable to the RS9110-N-11-2X
EVB’s serial port.
2. Connect the Female end of the DB9 serial cable to a PC’s serial COM port.
3. Connect the USB power cable to the RS9110-N-11-2X EVB and to a power
outlet and switch on the power to the EVB by toggling the Power Switch
(refer to the figures below).
DB9 Connector
RS9110-N-11-22
RS9110-N-11-24
Module
LED
Module
Figure
USB Power Supply
Power Switch
2: EVB of the RS9110-N-11-22/24 Modules2
2
The image shown here for the EVB may be different from the one delivered to the
user because of updates in design. Please follow the instructions in this document
irrespective of the image displayed here or contact Redpine Signals in case any help
is required.
Redpine Signals, Inc. Proprietary and confidential Page 10
4. Wait till the LED glows on the RS9110-N-11-2X module. This indicates the
completion of bootloading and initialization of the baseband and RF
components.
You are now ready to configure the module using the “Wi-Fi Config Utilit y”.
NOTE: Please make sure that the EVB is powered on, the LED is
glowing and the serial cable is connected before proceeding with the
steps in the following sections.
2.2: Configuring the RS9110-N-11-2X Module
The Wi-Fi Config Utility is a GUI based application used to configure the RS9110N-11-2X module. To execute this utility, double-click on the executable RS9110N-11-2X.exe found in the CD in the GUI folder.
NOTE: If a Wi-Fi connection has been configured previously and if you
wish to re-configure the RS9110-N-11-2X, please restart the procedure
explained below
The following is a screenshot of the GUI.
3
The image shown here for the EVB may be different from the one delivered to the
user because of updates in design. Please follow the instructions in this document
irrespective of the image displayed here.
Redpine Signals, Inc. Proprietary and confidential Page 11
The following are the actions that are to be performed to configure the Wi-Fi
module using the GUI above.
1. Initialize the COM port of the PC to which the RS9110-N-11-2X EVB is
connected.
2. Select the baud rate with which the COM port is configured from the drop
down menu beside the “Baud Rate” label.
NOTE: PCs and Laptops with Windows XP usually support a maximum
baud rate of 115200 bps. If a higher baud rate is selected (e.g., in a
Hyperterminal), the observation has been that the baud rate that is
actually used is 115200 bps. This will be true for the Wi-Fi Config
Utility as well. This is a limitation of the PC rather than of the RS9110N-11-2X EVB.
3. In case the user wants to connect to an Access Point or an IBSS Station
that is broadcasting its SSID, he/she will have to first scan for the list of
available Access Points/IBSS Stations and select the appropriate Access
Point/Station by clicking on it.
4. Alternatively, in case the user wants to connect to a hidden Access Point
whose SSID is known, he/she may enter the SSID in the GUI directly.
Redpine Signals, Inc. Proprietary and confidential Page 12
NOTE: In case the ABRD process fails, the GUI displays a message and
opens the COM port with the default settings. If the ABRD process
fails, it will mostly because of the connection betw een the PC and the
EVB not being proper. It’s recommended that the serial cable be used
directly without adapters like a USB-to-Serial adapter.
2.2.2: Scan
To scan for the available Access Points and IBSS Stations in all channels, click the
“SCAN” button. The list of scanned Access Points and IBSS Stations is displayed
on the GUI as shown below. The SSID corresponds to the SSID of the AP/IBSS
Station and mode is the security type. The RSSI value is also displayed as an
absolute value
4
RSSI is a negative value. The RSSI displayed on the GUI is an absolute value.
Hence, the lower the value displayed, the better is the Received Signal Strength.
4
.
Redpine Signals, Inc. Proprietary and confidential Page 15
NOTE: The present firmware requires that the module be powered off
and on if a connection to a different BSS is required. After powering on
the module, the same steps are to be followed as before.
11: Creating a IBSS Network
2.3: IP Address Configuration
The RS9110-N-11-2X has an inbuilt TCP(UDP)/IP stack and thus provides an
option for the Host to transmit only application data, which is transmitted over
WLAN after TCP/UDP packetization.
The TCP/IP stack has to be configured with the IP Address, Subnet Mask and
Gateway Address.
The Configuration can be done in two ways:
1. Manual
2. DHCP
2.3.1: Manual Configuration
The user has to perform the steps below to configure the IP parameters.
1. Select the Manual Mode from the configuration utility.
2. Enter the IP Address in the dotted decimal format.
Redpine Signals, Inc. Proprietary and confidential Page 19
NOTE: For getting the IP parameters over DHCP, the Access Point
should be configured accordingly.
NOTE: DHCP is not supported in IBSS mode.
NOTE: The parameters that are loaded using the Wi-Fi C onfig Utility
are not stored in non-volatile memory. So when the module is powered
off and then powered on, it has to be configured with the values again.
In future firmware releases this will not be required.
NOTE: The IP address, Subnet Mask and Default Gateway have to be
configured through the GUI in case of manual mode by clicking the
“OK” button prior to executing the applications used to validate the
TCP/IP stack.
2.4: Disconnect from Access Point
The “DISCONNECT” button can be used to disconnect from an Access Point to
which the EVB is associated (connected) over WLAN. This feature can be used if
the user wants to Scan and connect to another Access Point or to the same
Access Point again with different parameters. It’s expected that the Access Point
is also configured accordingly before attempting the connection again with the
changed parameters.
Redpine Signals, Inc. Proprietary and confidential Page 21
The Evaluation kit is supplied with DUT (Device Under Test) application and peer
applications for Windows OS to evaluate the (TCP) UDP/IP stack in the RS9110N-11-2X module. The source code for these applications is also supplied.
2.5.1: DUT Application
The DUT Application (RS9110-N-11-2X_DUT_App.exe) is to be executed in the PC
to which the RS9110-N-11-2X EVB is connected using the RS232 cable. It
communicates with the TCP/IP stack in the RS9110-N-11-2X module over the
UART interface through AT commands. Please refer to the programmer’s
reference manual for the description of the AT commands.
The application RS9110-N-11-2X_DUT_APP.exe in the path
Applications\DUT_Application has to be executed to interact with the DUT.
Alternatively, the DUT Application can be launched from the Configuration GUI
also by copying it to the same folder as the Configuration GUI application and
clicking on the “Launch DUT Application” button after the IP address is configured
successfully.
Redpine Signals, Inc. Proprietary and confidential Page 22
The Peer application consists of a UDP server, TCP server and a UDP client that
are run when the corresponding sockets are to be evaluated on the DUT. The
UDP Server Application (RS9110-N-11-2X_UDP_Server_App.exe), TCP server
application (RS9110-N-11-2X_TCP_Server_App.exe), and TCP client application
(RS9110-N-11-2X_TCP_Client_App.exe) are to be executed on a PC, which is
connected to the Access Point through Ethernet or Wi-Fi.
All the peer applications receive the data from the corresponding socket on the
DUT and transmit the obtained data back to the socket (application).
2.5.3: Test setup and Evaluation
The figure below illustrates the test setup.
1
TCP/UDP
Client/Ser ver PC
(Windows XP)
RS232
RS9110-N-11-22
EVB
Figure
15: Test setup for TCP (UDP)/IP Evaluation6
To run the test, please follow the steps below.
1. Make sure that the Access Point and the Server/Client PC’s are
connected properly and are on the same network. If they are on
different networks, ensure proper routing between them.
2. Make sure that the RS9110-N-11-2X module has been configured
properly and connected to the Access Point as described in the
Sections 2.1
, 2.2, and 2.3.
3. Check the wireless connection via a ‘ping’ command that can be
executed on the peer PC.
4. On PC 2, double-click the RS9110-N-11-2X_UDP_Server_App.exe,
RS9110-N-11-2X_TCP_Server_App.exe and RS9110-N-112X_TCP_Client_App.exe files to communicate with the
corresponding application (socket) on PC 1.
Access Point
10/100
TCP/UDP
2
Server /Client
(Windows XP/Linux)
PC
5. If PC 2 has a Linux OS, then execute the applications RS9110-N11-2X_UDP_Server_App, RS9110-N-11-2X_TCP_Server_App,
RS9110-N-11-2X_TCP_Client_App.
6
The test setup for the IBSS Network will not include the Access Point and the
RS9110-N-11-22 EVB will be connected to another IBSS client over WLAN through
the IBSS network.
Redpine Signals, Inc. Proprietary and confidential Page 23
NOTE 1: The Port number (1024 in the above screenshot) or the IP
address can be configured for an application to a different value by
giving the following command in a console:
On Windows
“RS9110-N-11-2X_TCP_App_Client.exe yyy.yyy.yyy.yyy xxxx”
On Linux
RS9110-N-11-2X_TCP_App_Client yyy.yyy.yyy.yyy xxxx
Where “xxxx” is the port number and yyy.yyy.yyy.yyy is the IP
address in the dotted decimal format.
NOTE 2: The TCP server and the UDP server take only the port number
as the input whereas the TCP client takes the IP address and the port
number as inputs. These parameters correspond to the IP address and
the port number of the application (socket) on the DUT.
NOTE 3: The TCP server socket on the DUT has to be created prior to
the execution of the TCP client on the peer.
6. On the PC connected to the RS9110-N-11-2X EVB, double-click the
RS9110-N-11-2X_DUT_App.exe file. A console window opens as
shown below.
Redpine Signals, Inc. Proprietary and confidential Page 24
The following sections explain the description of each choice with
shots.
2.5.3.1: Create Sockets
1. Enter
“1” (Create Sockets) as the choice.
2. The application asks to enter the type of socket as shown below.
the screen
Figure
19: Enter Socket type
3. If the choice entered is 0, a TCP client socket is created. The
application asks for the local port number of the socket, destin ation
IP address and the destination port number of the application on
the peer (TCP server).
Redpine Signals, Inc. Proprietary and confidential Page 26
4. If the choice entered is 1, a UDP socket is created. The application
asks for the local port number of the socket, destination IP address
and the destination port number of the application on the peer.
5. If the choice entered is 2, an LTCP (Listening TCP) socket is
created. This will create a TCP server socket, which will be
Redpine Signals, Inc. Proprietary and confidential Page 27
“listening” on a given port number for the connection to be
est
ablished by a TCP client. The application asks for the local port
number on which the socket should listen.
Figure
22: Socket type – LTCP
6. If the choice entered is 3, an LUDP (Listening UDP) socket is
created. This will create a listening UDP server socket, which will
be “listening” on a given port number for the data from any peer.
The application asks for the local port number on which the socket
should listen.
Redpine Signals, Inc. Proprietary and confidential Page 28
t, a valid socket descriptor
returned by the TCP/IP stack is displayed, as shown in the figure
above.
2.5.3.2: Send And Receive Data (UDP, TCP Client, LUDP)
Enter
“3” (Send Data) as a choice. The application now asks for the number of
sockets, the socket numbers, the length of the data, the destination IP address,
the destination port and the number of packets to be sent and received on each
socket.
The number of sockets specifies the total number of sockets on which the data
has to be sent and received.
The socket numbers signify the sockets on which the data has to be sent and
received. The sockets have to be created for the data transmission and reception
to happen. If a wrong socket number is entered then the user is prompted to
enter a valid socket descriptor.
Figure
24: Parameters and Result for Send and Receive Data on UDP Socket
NOTE: In case of TCP Client socket Destination IP address and
Destination port number should be zero as shown in the figure below
Redpine Signals, Inc. Proprietary and confidential Page 29
25: Parameters and Result for Send and Receive Data on TCP Socket
The application starts transmitting and receiving the data packets through the
RS9110-N-11-2X module over Wi-Fi. The application displays the statistics as
shown in the figure above.
The application compares the received data with the sent data. Any failure in the
comparison results in a packet loss and is displayed accordingly.
The application sends and receives the number of packets specified.
The server receives and transmits these packets and also displays the number of
packets received/sent.
Redpine Signals, Inc. Proprietary and confidential Page 30
a TCP server (LTCP) socket is created, the connection is est a blished only when
the TCP peer connects with the server. The DUT application queries for the
connection status on a particular TCP server socket till the connection is
established. Once the connection is established, the transmission and recept ion
of the data happens as shown in the figure below.
NOTE: In case of TCP Server Socket (LTCP) Destination IP address and
Destination port number should be zero.
Figure
27: Query Connection status and transmit/receive the data
2.5.3.4: List Sockets
st Sockets option lists the active sockets at a particular instance. The
The Li
socket descriptor and the socket type are displayed as below.
Redpine Signals, Inc. Proprietary and confidential Page 31
The DUT application issues “ACK” messages for the received “SL
this power mode for the configured number of times.
NOTE: The user should configure the sleep timer before configuring the
module for Power Mode 1.
EEP” messages in
Figure
31: Power Mode 1 - Before WLAN Connection
2.5.3.6.3 Power Mode 2 (unconnected state)
To trigger the power m
odes, enter the choice 5 in the main menu. The following
screen shot shows the menu for the Power Mode 2 (Mode 2).
There is no negotiation with the host in this power mode. Thus, th e module is in
this mode till the user switches to Power Mode 0 (Mode 0).
NOTE: The direct switching between the Power Mode 1 and Power
Mode 2 is not possible. The user has to switch back to power mode 0
before switching between the two power modes.
Redpine Signals, Inc. Proprietary and confidential Page 34
the Power Mode 1 in connected state, the module has to be connected to
an Access Point and configured with an IP address using the Configuration GUI.
After selecting the Power Mode 1 in the console, the user is prompted to “Enter
the number of ACKs to be issued for the Sleep”. The DUT application sends the
configured number of ACK messages for the obtained SLEEP messages before
sending/receiving each data packet.
The module continuously issues the SLEEP message after every DTIM period to
query the Host’s acceptance to go to sleep till the next DTIM interval expiry. The
DUT application issues the ACK message for the configured number of times
before sending or receiving data.
To send or receive data, please refer to Section 2.4.3.2
.
Redpine Signals, Inc. Proprietary and confidential Page 35
NOTE: The GUI can be used at any stage to Disconnect from the
Access Point and attempt a new connection. For this, the user need to
close the Test Applications and restart the GUI, since the COM port can
be used only by one application at any time. When the GUI is opened,
it will try to perform the ABRD process again and fail. Only after the
failure, the DISCONNECT button will be enabled.
Of course, in an embedded environment, the user can directly issue
the disconnect command (AT+RSI_DISASSOC) without attempting the
ABRD process.
Redpine Signals, Inc. Proprietary and confidential Page 37
The following steps explain the procedure for upgrading the firmware of the
RS9110-N-11-2X module.
1. Connect the power to the RS9110-N-11-2X EVB.
2. Connect one end of the supplied DB9F – DB9M null modem serial cable
to the RS9110-N-11-2X EVB’s serial port.
onnect the other end of the DB9 serial cable to a terminal or a PC’s
3. C
serial COM port.
4. Open a terminal emulation program, e.g., HyperTerminal, on Windows
XP. Configure the terminal with the following settings.
Baud Rate = 115200
Stop Bits = 1
Pari
Flow Control = No
5. Switch on the power to the EVB by toggling the Power Switch on the
EVB.
6. The module is configured for Auto Baud Rate Detection (ABRD) and
hence the module waits for approximately 40 to 50 seconds for ABRD
message exchange to be initiated by the Host as described in the
Software PRM. However, in the case of firmware upgrade through the
Hyperterminal, it’s not possible to perform the ABRD bytes’ exchange.
The user has to wait for the ABRD to fail and for the module to start
working at 115200 bps which is the baud rate that the module is
configured for if ABRD fails.
7. The user is now prompted to enter ‘y’ for a firmware upgrade or ‘n’ for
no firmware upgrade, as shown in the figure below.
ty = No
Redpine Signals, Inc. Proprietary and confidential Page 38
8. The user should enter ‘y’ to stop the boot process with the default
firmware. The RS9110-N-11-2X module waits for a few seconds for the
prompt from the user and hence the user has to enter ‘y’ as soon as
the prompt appears.
8. The user has to now transfer the firmware files. The files, viz., taim1,
taim2, tadm1 and tadm2 (present in the Firmware folder of the CD),
have to be transferred in the same order from the HyperTerminal. The
following is the procedure to send a file through the HyperTerminal.
9. Click on “Transfer” on the toolbar of the HyperTerminal window.
10. Select “Send File” on the “Transfer” menu.
11. Click the “Browse” button to point to the path of taim1/taim2/tadm in
the Host system.
12. Select the protocol as “Kermit”.
13. Click the “Send” button to start the transfer.
Redpine Signals, Inc. Proprietary and confidential Page 39
14. For each file being transferred, wait for a display on the Hyperterminal
which says “Send <nextfile>”. Please note that after a file is
transmitted, there is some delay is writing the data to the non-volatile
memory. This might take a few seconds and the user has to wait for
the prompt on the Hyperterminal for the next file.
15. Once all three files are t ransferred, the following message is displayed
on the HyperTerminal.
Redpine Signals, Inc. Proprietary and confidential Page 40
The RS9110-N-11-2X EVB has various switches and headers to enable the user to
configure it for different scenarios
components.
DB9 Connector
7
. The figure below shows the various
USB Power Supp l y
Switch SW4
RS9110-N-11-22
Header J4 (Debug)
HeaderJ7 (SPI)
Figure
Module
LED
DIP Switches
38: Components on the EVB of RS9110-N-11-22/24 Modules
Switch SW5
Power Switch
HeaderJ6 (UART)
Push Button (Reset)
7
Some of the older revisions of the EVB may not contain all the components
described in this section. Please contact Redpine Signals (with a picture of the EVB)
in case help is required to realize the functionality described in this section.
Redpine Signals, Inc. Proprietary and confidential Page 42
39: Components on the EVB of RS9110-N-11-26/28 Modules
The following sections explain these components and their configuration for the
different usage scenarios.
4.1: DIP Switches
The 4 DIP Switches on the EVB are used for the following purposes:
1. Use of Power-On Reset or Push-Button Reset
2. Select between SPI and UART modes
Power Switch
Switch SW4
Switch SW5
Header J6 (UART)
Header J7 (SPI)
Push Button (Reset)
3. Debug
DIP Switches 1 and 2 are used to configure the source of the Reset for the
module. Placing DIP Switch 1 towards the ‘ON’ label and DIP Switch 2 towards
the opposite side selects the Power-On Reset. Flipping the switches (Switch 2
towards ‘ON’ and Switch 1 in the opposite side) selects the Push-Button Reset.
DIP Switch 3 is used to select between the UART and SPI interfaces. Placin g this
switch towards the ‘ON’ label selects SPI and flipping it to the opposite side
selects UART.
NOTE: The firmware for UART and SPI interfaces (RS9110-N-11-2X
and RS9110-N-11-2X-01, respectively) are different and the user is
advised to contact Redpine Signals in order to switch between the two
interfaces.
DIP Switch 4 is used for debug purposes only and has to be placed on the side
opposite to the ‘ON’ label.
4.2: Header J4
The Header labeled J4 is used for debug purposes.
Redpine Signals, Inc. Proprietary and confidential Page 43
The Header labeled J7 is used for the SPI interface. The pin configur ation of this
header is as follows:
Figure 40: Pin Configuration of Header J7
4.4: Header J6
The Header labeled J6 is used for interfacing the EVB over UART to a second PCB
which has the Host microcontroller mounted. This header bypasses the DB9
connector and the 3.3V-5V level shifter ICs and a simple ribbon-cable can be
used for this interface. This header can be enabled/disabled by flipping the
switches SW4 and SW5. The pin configuration of this header is as follows:
Figure
41: Pin Configuration of Header J6
4.5: Switches SW4 and SW5
The Switches SW4 and SW5 are used to select between the DB9 connector and
the Header J6 for the UART interface. In the images of the EVBs shown above,
the switches are placed (to the right on the RS9110-N-11-22/24 EVB and to the
left on the RS9110-N-11-26/28 EVB) to enable the DB9 connector. If they are
flipped, the Header J6 is enabled.
Redpine Signals, Inc. Proprietary and confidential Page 44
Loading...
+ 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.