Roving Networks RN-131, RN-171 User Manual
!
www.rovingnetworks.com 1
RN-WIFLYCR-UM-.01
! !
RN-WIFLYCR-UM
WiFly Command Reference,
Advanced Features & Applications
USER MANUAL
© 2012 Roving Networks. All rights reserved.
RN-WIFLYCR-UM Version 1.0r 9/21/2012
!
www.rovingnetworks.com Version 1.0r 9/21/2012 2
RN-WIFLYCR-UM
Contents
Introduction ....................................................................................................................... 5!
Features ....................................................................................................................................... 5!
Configuration ................................................................................................................................ 6!
Entering Command Mode ........................................................................................................... 6!
Remote Configuration Using Ad Hoc Mode ................................................................................... 7!
Command Reference ........................................................................................................... 8!
Command Syntax .......................................................................................................................... 8!
Command Organization .................................................................................................................. 8!
Set Commands ............................................................................................................................. 9!
Get Commands ........................................................................................................................... 33!
Status Commands ....................................................................................................................... 35!
Action Commands ....................................................................................................................... 37!
File I/O Commands ...................................................................................................................... 40!
Advanced Features & Settings ........................................................................................... 42!
Access Point (AP) Mode ............................................................................................................... 42!
Enabling AP mode ................................................................................................................... 43!
Enable in Hardware .............................................................................................................. 43!
Enable in Software ............................................................................................................... 43!
Using AP Mode ....................................................................................................................... 44!
Connect to the Module ......................................................................................................... 44!
Check for the Last Connected Device over TCP ....................................................................... 44!
View Associated Devices ....................................................................................................... 45!
Enable the Link Monitor ....................................................................................................... 45!
Route Data between Clients .................................................................................................. 45!
GPIO4, 5 & 6 Alternative Functions ...................................................................................... 45!
Putting the Module to Sleep & Waking It ....................................................................................... 46!
System & Auto-Connect Timers .................................................................................................... 48!
UDP Sleep & Connection Timers ............................................................................................... 48!
TCP Connection Timers ............................................................................................................ 49!
Opening a TCP Connection ................................................................................................... 49!
Closing the TCP Connection .................................................................................................. 49!
Wake on Sensor Input ................................................................................................................. 49!
Wake on UART Activity ................................................................................................................ 50!
UART Receiver & RTS/CTS Hardware Flow Control ...................................................................... 50!
Setting GPIO Direction, Alternate Functions & Disabling LEDs ..................................................... 51!
Setting the Alternate GPIO Functions .................................................................................... 53!
Controlling Connections with GPIO Pins ................................................................................. 54!
Setting Debug Print Levels ........................................................................................................... 56!
Scan Output Format ................................................................................................................ 56!
Firmware Version 2.36 & 2.45 .............................................................................................. 56!
Firmware Version 2.22 through 2.30 ..................................................................................... 58!
!
www.rovingnetworks.com Version 1.0r 9/21/2012 3
RN-WIFLYCR-UM
UART Heartbeat Messages ....................................................................................................... 58!
Using the Real-Time Clock Function ............................................................................................. 59!
Time Stamping Packets ............................................................................................................... 60!
Advanced Applications ..................................................................................................... 61!
Sending Data using UDP ............................................................................................................. 61!
UDP Auto Pairing .................................................................................................................... 62!
UDP Retry .............................................................................................................................. 62!
UDP Broadcast ........................................................................................................................ 62!
Joining Networks & Making Connections ........................................................................................ 63!
Associate with an Access Point ................................................................................................. 63!
Making Connections ................................................................................................................ 64!
Setting Up Automatic Connections ............................................................................................ 65!
Controlling Connections using GPIO5 & GPIO6 ........................................................................... 65!
Using DNS Settings ................................................................................................................. 66!
Using the Backup IP Address/Connect Function ......................................................................... 66!
Using the HTML Client Feature .................................................................................................... 66!
Built-In HTML Client Modes ..................................................................................................... 67!
Connect to a Web Server Automatically ...................................................................................... 67!
Connect to a Web Server Automatically when UART Data Is Received ........................................... 68!
Post Binary Data ..................................................................................................................... 68!
Post Sensor Data Automatically ................................................................................................ 69!
HTML Client Example: Posting Sensor Data Automatically ........................................................... 69!
HTML Client Example: Posting UART Data to a Web server .......................................................... 70!
Upgrading Firmware Via FTP ........................................................................................................ 71!
FTP Client .................................................................................................................................. 72!
Connect to an FTP Server ......................................................................................................... 72!
Creating Files on the FTP Server ............................................................................................... 72!
Retrieving Files from the FTP Server ......................................................................................... 73!
Wi-Fi Protected Setup (WPS) ....................................................................................................... 73!
Launching a WPS Application ................................................................................................... 75!
Status LEDs during WPS Process .............................................................................................. 75!
Scan Output Format Showing WPS-Enabled Access Point ........................................................... 75!
Ad hoc Networking Mode ............................................................................................................. 77!
Configuring Ad Hoc Mode ......................................................................................................... 77!
Enable Ad Hoc Mode in Hardware ......................................................................................... 77!
Enable Ad Hoc Mode in Software .......................................................................................... 77!
Scanning for Access Points in Ad Hoc Mode .............................................................................. 78!
Analog Sensor Capability ............................................................................................................. 79!
Sampling Sensor Pins Automatically ......................................................................................... 79!
Using the Built-In Sensor Power ............................................................................................... 80!
Default Configuration ........................................................................................................ 81!
ADHOC PARAMETERS ................................................................................................................ 81!
BROADCAST PARAMETERS ........................................................................................................ 81!
!
www.rovingnetworks.com Version 1.0r 9/21/2012 4
RN-WIFLYCR-UM
COMM PARAMETERS ................................................................................................................. 81!
DNS PARAMETERS .................................................................................................................... 81!
FTP PARAMETERS ..................................................................................................................... 81!
IP PARAMETERS ........................................................................................................................ 82!
OPTIONAL PARAMETERS ........................................................................................................... 82!
SYSTEM PARAMETERS ............................................................................................................... 82!
TIME SERVER PARAMETERS ...................................................................................................... 82!
UART PARAMETERS ................................................................................................................... 83!
WLAN PARAMETERS .................................................................................................................. 83!
String Variable Sizes ................................................................................................................... 83!
Restoring Default Configuration Settings ....................................................................................... 84!
Boot-up Timing Values ...................................................................................................... 85!
Supported Access Points .................................................................................................. 86!
Command List ................................................................................................................... 87!
Known Problems ............................................................................................................... 92!
Current Firmware Features & Fixes .................................................................................... 93!
Version 2.36/2.45 9/14/2012 ...................................................................................................... 93!
Version 2.30 10/26/2011 ............................................................................................................ 94!
Version 2.27 09/08/11 ................................................................................................................ 94!
Version 2.23 04/03/2011 ............................................................................................................ 94!
Version 2.21 07/11/2010 ............................................................................................................ 95!
Version 2.20 06/14/2010 ............................................................................................................ 95!
Fixes ...................................................................................................................................... 95!
Features ................................................................................................................................. 95!
!
www.rovingnetworks.com Version 1.0r 9/21/2012 5
RN-WIFLYCR-UM
INTRODUCTION
The Roving Networks WiFly radio module is a complete, standalone embedded wireless LAN access device. The device
has an on-board TCP/IP stack and applications, and in the simplest configuration only requires four pins (power, TX, RX,
and ground). Once you have performed the initial configuration, the device automatically accesses a Wi-Fi network and
sends/receives serial data over the UART.
This user manual is applicable to standalone RN-131 and RN-171 modules, as well as Roving Networks hardware that
includes these modules. Although there are some differences, the RN-131 and RN-171 modules support the same ASCII
command set. The RN-XV device incorporates the RN-171 module; therefore, all RN-171 hardware features apply to the
RN-XV. Table 1 compares the RN-131 and RN-171 module features.
Table 1. Comparing the RN-131 & RN-171
Feature
RN-131
RN-171
Output power
18 dBm (fixed)
12 dBm (programmable)
Lowest power
18 dBm
0 dBm (< 100 mA Tx current)
On-board antenna
Yes
No
Accurate sleep timer
Yes (32 kHz)
No (+/- 10% error)
GPIO pins available
10, GPIO4 – 13 (GPIO1 – 3 are not available for use)
14, GPIO1 – 14
Default firmware
WiFly_GSX-<version>.img
WiFly_EZX-<version>.img
Refer to the RN-131 and the RN-171 data sheets on the Roving Networks website at http://www.rovingnetworks.com for
more details on their hardware differences and for detailed hardware specifications.
FEATURES
• Fully qualified and Wi-Fi certified 2.4-GHz IEEE 802.11 b/g transceiver
• FCC, CE, ICS certified, and RoHS compliant
• Ultra-low power:
o Intelligent, built-in power management with programmable wakeup
o Accepts 3.3-V regulated or 2- to 3-V battery with on-board boost regulators
o IEEE 802.11 power save and roaming functions
o RN-131: 4 uA sleep, 35 mA Rx, 210 m Tx at 18 dBm (Tx power not configurable)
o RN-171: 4 uA sleep, 35 mA Rx, 185 mA Tx at 12 dBm (Tx power configurable)
• Antenna options:
o RN-131: On-board ceramic chip antenna and U.FL connector for external antenna
o RN-171: RF pad
!
www.rovingnetworks.com Version 1.0r 9/21/2012 6
RN-WIFLYCR-UM
• Hardware:
o 8-Mbit flash memory and 128-Kbyte RAM, 2-Kbyte ROM, 2 Kbyte battery-backed memory
o 10 general-purpose digital I/O pins (RN-131)
o 14 GPIO pins (RN-171)
o 8 analog inputs (14 bits, 1.2 V)
o UART (1 Mbps host data rate) and SPI slave (2 Mbps host data rate) hardware interfaces
o Real-time clock for wakeup and time stamping/data logging; auto-sleep and auto-wakeup modes
• Network support:
o Supports ad hoc and infrastructure mode connections
o Push-button WPS mode for easy network configuration
o On-board TCP/IP stack
o Over the air firmware upgrade (FTP) and data file upload support
o Secure Wi-Fi authentication via WEP-128, WPA-PSK (TKIP), and WPA2-PSK (AES)
o Configuration over UART or wireless interfaces using simple ASCII commands
o Built in networking applications: DHCP client, DNS client, ARP, ICMP ping, FTP client, TELNET, HTTP,
UDP, and TCP
CONFIGURATION
The WiFly module operates in two modes: data mode and command mode. In data mode, the module can accept
incoming connections or initiate outgoing connections. To configure parameters and/or view the current configuration, you
must put the module into command mode (also called configuration mode).
Entering Command Mode
By default, the module is in data mode. Sending the escape sequence $$$ causes the module to enter command mode.
You must send $$$ together quickly with no additional characters before or after. You must not send a carriage return
(<cr>) or line feed after the $$$ to enter command mode. The module replies with CMD to indicate it is in command
mode. Once in command mode, you can configure the WiFly device using simple ASCII commands; each command ends
with a carriage return <cr>. Most valid commands return AOK; invalid ones return an ERR description. To exit command
mode, send exit <cr>. The module responds with EXIT, indicating that it has exited command mode and entered data
mode.
NOTE: There is a 250-ms buffer before and after the $$$ escape sequence. If characters are sent before or after the
escape sequence within this 250-ms interval, the WiFly module treats them as data and passes them over the
TCP or UDP socket, and the module will not enter command mode.
You can view various parameters, such as the SSID, channel, IP address, serial port, and other settings, and configure
them in command mode. You send commands to the module through the UART or via remotely via telnet. When using the
UART interface, the communications settings should match the WiFly module’s stored settings. The default is 9,600 baud,
8 bits, no parity, 1 stop bit, and hardware flow control disabled. You can enter command mode locally over the UART
interface at any time irrespective of an active TCP connection.
NOTE: Roving Networks suggests using either the TeraTerm (Windows OS) or CoolTerm (Mac OS-X) terminal
emulator program.
When the WiFly module powers up, it attempts to auto-associate with the access point stored in its configuration settings. If
the module cannot find the access point, it enters auto association mode, and scans and attempts to join a network. This
!
www.rovingnetworks.com Version 1.0r 9/21/2012 7
RN-WIFLYCR-UM
mode may cause the UART to become unresponsive briefly. To avoid configuration problems, the auto-associate feature is
disabled when the module is in command mode, making it easy to configure the module. The auto-associate mode turns
on when you exit command mode.
NOTE: If your module is running firmware version 2.20 or lower, the auto-associate feature is NOT disabled when the
module is in command mode. Therefore, you may lose data sent to the module while it is unassociated,
making it difficult enter command mode and configure the module.
You can disable the auto-associate feature using the set wlan join 0 command. This command prevents the WiFly module
from attempting to associate with a network that does not exist. Alternatively, enable ad hoc mode upon power up using
the GPIO9 ad hoc/factory reset jumper. If this jumper is high on power up, the module does not associate with a network.
While in ad hoc mode, you can configure the network settings.
Remote Configuration Using Ad Hoc Mode
Using ad hoc mode to configure the device eliminates the need for the module to be associated with a network access
point. In ad hoc mode, the module creates it’s own “on demand” network to which you can connect via your computer as
you would with any other network.
To enable ad hoc mode using hardware, set GPIO9 high (3.3 V) at power up. For the RN-134 board, GPIO9 is on pin 1 on
the jumper block (J2). For the RN-174 board, GPIO9 is on the J6 connector. Upon power up with GPIO9 high, the WiFly
module creates an ad hoc network with the following settings:
SSID: WiFly-GSX-XX, where XX is the final two bytes of the devices MAC address
Channel: 1
DHCP: Off
IP address: 169.254.1.1
Netmask: 255.255.0.0
With the ad hoc jumper in place, these settings override any saved configuration settings.
From your computer, connect to the WiFly-GSX-XX network. This open network does not require a pass phrase or pass
key. Currently the WiFly module only supports OPEN mode for creating ad hoc networks.
It may take a few minutes for Windows to assign an IP address and connect to the network. You can check your
computer’s IP address by running the ipconfig command in the Command Window. If connected, this command displays
your computer’s IP address and netmask.
NOTE: The automatically assigned IP address must be on the 169.254.x.y subnet, otherwise the WiFly module will
not be accessible. If your computer has both wireless and wired interface hardware, you may need to disable
the wired LAN interface hardware before connecting to the ad hoc network. If the wired LAN is enabled, the
computer may assign an IP address that is not on the same subnet as the WiFly module.
Once connected with an appropriate IP address, telnet into the WiFly module on port 2000 using the following command:
telnet 169.254.1.1 2000
The module issues the response *HELLO*. You can now enter command mode using the escape sequence $$$ and
configure the module.
In firmware versions 2.28 and higher, you can disable remote configuration, e.g., for security. To disable remote
configuration, use bit 4 in the TCP mode register by issuing the command:
set ip tcp-mode 0x10
!
www.rovingnetworks.com Version 1.0r 9/21/2012 8
RN-WIFLYCR-UM
COMMAND REFERENCE
Roving Networks WiFly modules support a variety of commands for configuration. This section describes these commands
in detail and provides examples.
COMMAND SYNTAX
To issue commands to the module, you send a keyword followed by optional parameters. Commands are case sensitive,
and you cannot use spaces in parameters. Use a $ to indicate a space, e.g., MY NETWORK should be written as
MY$NETWORK. Hex input data can be uppercase or lowercase. String text data, such as the SSID, is case sensitive.
You can use shorthand for the parameters. For example, the following commands are equivalent:
• set uart baudrate 115200
• set uart b 115200
• set u b 15200
NOTE: You cannot use shorthand for command keywords. For example, s uart baudrate 115200 is illegal.
You can type numbers in decimal (e.g., 115200) or hexadecimal. To enter a number in hex, use 0x<value>. For example,
the hex value FF would be entered as 0xFF.
COMMAND ORGANIZATION
There are five general command categories, as shown in Table 2.
Table 2. Command Types
Command Type
Description
Set commands
Set commands take effect immediately and are stored to memory when the save command is issued.
Get commands
These commands retrieve the stored information and display it.
Status commands
These commands display the interface status, IP status, etc.
Action commands
Use these commands to perform actions such as scanning, connecting, disconnecting, etc.
File I/O commands
Use these commands to upgrade, load and save configuration, delete files, etc.
NOTE: You must save any changes you make using the save command or the module will load the previous settings
upon reboot or power up.
!
www.rovingnetworks.com Version 1.0r 9/21/2012 9
RN-WIFLYCR-UM
When the system boots, all configuration data is loaded into RAM variables from the config file. The set commands only
modify the RAM copy of the system variables. In general, the IP, WLAN, and UART settings require you to save and reboot
before they take effect because they operate upon power up. For example, you only associate, set the channel, and obtain
an IP address once at power up. Most of the other commands, e.g., COMM settings and timers, take effect immediately,
allowing you to change parameters on the fly, minimizing power usage, and saving flash re-write cycles.
Once configuration is complete, you must save the settings to store the configuration data, otherwise it will not take effect
upon reboot or reset. You can store multiple configurations using the save <filename> command, and you can load them
using the load <filename> command.
SET COMMANDS
These commands begin with the set keyword and include the categories shown in Table 3:
Table 3. Set Commands
Parameter
Description
adhoc
Controls the ad hoc parameters.
broadcast
Controls the broadcast hello/heartbeat UDP message.
comm
Sets the communication and data transfer, timers, and matching characters.
dns
Sets the DNS host and domain.
ftp
Sets the FTP host address and login information.
ip
Specifies the IP settings.
option
Supports optional and infrequently used parameters.
sys
Sets system settings such as sleep and wake timers.
time
Sets the timer server settings.
uart
Specifies the serial port settings such as baud rate and parity.
wlan
Sets the wireless interface settings, such as SSID, channel, and security options.
set adhoc beacon <value>
This command sets the ad hoc beacon interval in milliseconds, where <value> is a decimal number from 0 to 65,436.
Default: 100
Example: set adhoc beacon 120 // Beacons are sent every 120 ms
!
www.rovingnetworks.com Version 1.0r 9/21/2012 10
RN-WIFLYCR-UM
set adhoc probe <value>
This command sets the ad hoc probe timeout in seconds, where <value> is the number of seconds. The probe
timeout is the number of seconds the module waits for probe responses before declaring, “ADHOC is lost,” and
disabling the network interface.
Default: 5
Example: set adhoc probe 80 // Sets the ad hoc probe timeout to 80 s
set broadcast address <address>
This command sets the address to which the UDP hello/heartbeat message is sent, where <address> is an IP address
in the form <value>.<value>.<value>.<value> with <value> being a number between 0 and 255.
Default: 255.255.255.255
Example: set broadcast address 255.255.255.255 // Sets the broadcast address to 255.255.255.255
set broadcast interval <mask>
This command sets the interval at which the hello/heartbeat UDP message is sent and is specified in seconds. The
value is a mask that is ANDed with a free running seconds counter; if the result is all 0s, a packet is sent. For
example:
• If the interval is 0x1, the module sends one packet every 2 seconds.
• If the interval is 0x2. The module sends two packets every 4 seconds.
• If the interval is 0x3, the module sends one packet every 4 seconds.
• If the interval is 0x6, the module sends two packets every 8 seconds.
• If the interval is 0x7, the module sends one packet every 8 seconds.
The minimum interval value is 1 (every 2 seconds) and the maximum value is 0xff (every 256 seconds). Setting the
interval value to zero disables UDP broadcast messages.
Default: 7
Example: set broadcast interval 6 // Sets the heartbeat UDP message interval to 6 seconds
set broadcast port <value>
This commands sets the port to which the UDP hello/heartbeat message is sent, where <value> represents the port
number.
Default: 55555
Example: set broadcast port 55555 // Sets the port to which the UDP heartbeat is sent to
// 55555
!
www.rovingnetworks.com Version 1.0r 9/21/2012 11
RN-WIFLYCR-UM
set comm $ <char>
This command sets character used to enter command mode to <char>. You typically use this setting when $$$ (the
default string used to enter command mode) is a possible data string. You must carefully note the new character.
After you save this setting, upon every subsequent reboot the module ignores $$$ and looks for <char><char><char>
to enter command mode.
Default: $
Example: set comm $ w // Sets the string to enter command mode to www
set comm close <string>
This command sets the ASCI string that is sent to the local UART when the TCP port is closed, where <string> is one
or more characters up to a maximum of 32 (32 bytes). If you do not wish to use a string, use a zero (0) as the <string>
parameter.
Default: *CLOS*
Example: set comm close *port closed* // Set the string to *port closed*
set comm open <string>
This command sets the ASCI string that is sent to the local UART when the TCP port is opened, where <string> is one
or more characters up to a maximum of 32 (32 bytes). If you do not wish to use a string, use a zero (0) as the <string>
parameter.
Default: *OPEN*
Example: set comm open *port open* // Set the string to *port open*
set comm remote <string>
This command sets the ASCI string that is sent to the remote TCP client when the TCP port is opened, where <string>
is one or more characters up to a maximum of 32 (32 bytes). If you do not wish to use a string, use a zero (0) as the
<string> parameter.
Default: *HELLO*
Example: set comm remote *welcome* // Set the string to *welcome*
set comm idle <value>
This command sets the idle timer value, where <value> is a decimal number representing the number of seconds.
The idle timer value is the number of seconds during which no data is transmitted or received over TCP before the
connection is closed automatically. Setting the timer to 0 (the default) means the module never disconnects when
idle.
Default: 0
Example: set comm idle 25 // Set the idle timer value to 25 s
!
www.rovingnetworks.com Version 1.0r 9/21/2012 12
RN-WIFLYCR-UM
set comm match <value> | <hex>
This command sets the match character, where <value> is a decimal number from 0 to 127 or a hex number from 0
to 7F. When this configuration option is set, the module sends an IP packet each time the match character appears in
the data. You enter <value> either as the decimal (e.g., 13) or hex (e.g., 0xd) equivalent of the of the ASCII character.
Setting the match character to 0 disables matching.
A match character is one of three available methods you can use to control TCP/IP packet forwarding. The other
methods are set comm size and set comm time. For more information refer to “UART Receiver & RTS/CTS Hardware
Flow Control” UART Receiver on page 50.
Default: 0
Example: set comm match 13 // Set the match character to a carriage return
set comm size <value>
This commands sets the flush size in bytes, where <value> is a decimal number from 0 to 1,420 (at 9600 baud).
When this configuration option is set, the module sends an IP packet each time <value> bytes are received. Roving
Networks recommends that you set this value as large as possible to maximize TCP/IP performance.
NOTE: To optimize the link, this value is set automatically when the baud rate is set. It is assumed that higher
baud rates equate to more data, hence the flush size is increased.
Flush size is one of three available methods you use to control TCP/IP packet forwarding. The other methods are set
comm match and set comm time. For more information refer to “UART Receiver & RTS/CTS Hardware Flow Control”
UART Receiver on page 50.
Default: 64
Example: set comm size 1420 // Set the flush size to 1,420 bytes
set comm time <value>
This command sets the flush timer, where <value> is a decimal number representing milliseconds. When this
configuration option is set, the module sends an IP packet if no additional bytes are received for <value> ms. Setting
this value to 0 disables forwarding based on the flush timer.
The flush timer is one of three available methods you can use to control TCP/IP packet forwarding. The others are set
comm match and set comm size. For more information refer to “UART Receiver & RTS/CTS Hardware Flow Control”
UART Receiver on page 50.
Default: 10
Example: set comm time 20 // Set the flush timer to 20 ms
!
www.rovingnetworks.com Version 1.0r 9/21/2012 13
RN-WIFLYCR-UM
set dns address <address>
This command sets the IP address of the DNS sever, where <address> is an IP address in the form
<value>.<value>.<value>.<value> with <value> being a number between 0 and 255. This address is automatically set
when using DHCP; you must set the DNS IP address for static IP or automatic IP modes.
Default: 0.0.0.0
Example: set dns address 169.64.1.1 // Set the DNS server address to 169.64.1.1
set dns name <string>
This command sets the name of the host for TCP/IP connections to <string>, where <string> is up to 32 characters
(32 bytes).
Default: server1
Example: set dns name roving1 // Set the DNS host name to roving1
set dns backup <string>
This command sets the name of the backup host for TCP/IP connections to <string>, where <string> is up to 32
characters (32 bytes). The FTP client uses the backup string to download the firmware via the ftp update command.
Default: rn.microchip.com
Example: set dns backup roving2 // Set the DNS host name to roving2
set ftp addr <address>
This command sets the FTP server’s IP address of the FTP server, where <address> is an IP address in the form
<value>.<value>.<value>.<value> with <value> being a number between 0 and 255.
Default: 0.0.0.0
Example: set ftp addr 66.35.227.3 // Set the FTP server to 66.35.227.3
set ftp dir <string>
This command sets the starting directory on the FTP server, where <string> is up to 32 characters. To read/write to
subfolders, use the \ character. To indicate the root directory, use a period.
Default: public
Example: set ftp dir demo // Sets the FTP server starting directory to demo
set ftp dir demo\test // Sets the FTP server starting directory to demo\test
set ftp dir . // Sets the FTP server starting directory to the root
// directory
!
www.rovingnetworks.com Version 1.0r 9/21/2012 14
RN-WIFLYCR-UM
set ftp filename <filename>
This command sets the name of the file that is transferred when issuing the ftp u command, where <filename> is the
firmware image. If you specify any file other than the firmware image, the WiFly module downloads the file and issues
the UPDATE FAIL=3 error.
Default: wifly_GSX-<version>.img (RN-131), wifly_EZX-<version>.img (RN-171)
Example: set ftp filename my_data // Sets the firmware image to be retrieved via FTP as
// my_data
set ftp mode <mask>
This command sets the ftp mode, where <mask> indicates active or passive mode.
Default: 0x0
Example: set ftp mode 0x1 // Enables active FTP mode
set ftp remote <value>
This command sets the FTP server’s remote port number, where <value> is the port number.
Default: 21
Example: set ftp remote 25 // Sets the FTP server’s remote port to 25
set ftp time <value>
The command sets the FTP timeout value, where <value> is a decimal number that is five times the number of
seconds required. The module uses this timer to close the FTP connection automatically after the specified time.
Default: 200
Example: set ftp timer 40 // Sets a 5-second timer
set ftp timer 80 // Sets a 10-second timer
set ftp user <string>
This command sets the user name for accessing the FTP server, where <string> is up to 16 characters (16 bytes).
Default: roving
Example: set ftp user my_username // Sets the user name to my_username
set ftp pass <string>
This command sets the password for accessing the FTP server, where <string> is up to 16 characters (16 bytes).
Default: Pass123
Example: set ftp user my_password // Sets the user name to my_password
!
www.rovingnetworks.com Version 1.0r 9/21/2012 15
RN-WIFLYCR-UM
set ip address <address>
This command sets the WiFly module’s IP address, where <address> is an IP address in the form
<value>.<value>.<value>.<value> with <value> being a number between 0 and 255. If DHCP is turned on, the IP
address is assigned and overwritten when the module associates with an access point. IP addresses are “.” delimited.
Default: 0.0.0.0
Example: set ip a 10.20.20.1 // Sets the WiFly module’s IP address to 10.20.20.1
set ip backup <address>
This command sets a secondary host IP address, where <address> is an IP address in the form
<value>.<value>.<value>.<value> with <value> being a number between 0 and 255. If the primary host IP is
unreachable, the module attempts to reach the secondary IP address (if set).
Default: 0.0.0.0
Example: set ip a 10.20.20.2 // Sets the WiFly module’s secondary IP address to
// 10.20.20.2
set ip dhcp <value>
This command enables/disables DHCP mode, where <value> is a decimal number shown in Table 4. If you set this
parameter, the module requests and sets the IP address, gateway, netmask, and DNS server upon association with an
access point. Any previously set IP information is overwritten.
Table 4. DHCP Modes
Mode
Protocol
0
Turns DHCP off. The module uses its stored static IP address.
1
Turns DHCP on. The module attempts to obtain an IP address and gateway from the access
point.
2
Enables automatic IP, which is generally used with ad hoc networks.
3
Turns on DHCP cache mode. The module uses a previously set IP address if the lease is not
expired (or the lease survives reboot).
4
Enables DHCP server in soft AP mode.
Using DHCP cache mode can reduce the time the module requires to wake from deep sleep, which saves power. The
module checks the lease time; if it is not expired, the module uses the previous IP settings. If the lease has expired,
the module attempts to associate and uses DHCP to obtain the IP settings. The DHCP cached IP address does not
survive a power cycle or reset.
Default: 1
Example: set ip dhcp 0 // Turns DHCP off
!
www.rovingnetworks.com Version 1.0r 9/21/2012 16
RN-WIFLYCR-UM
set ip flags <mask>
This commands sets the TCP/IP functions, where <mask> is a hex number referring to a bit-mapped register. See
Figure 1.
Figure 1. set ip flags Command Bit-Mapped Register
!
Notes:
1. If the module loses the link to an associated access point while a TCP connection is active, the TCP connection may hang or be
in an inconsistent state. In some cases, the TCP connection will not recover. In firmware version 2.20 and higher, if the module
regains the link to the access point within 60 seconds, the TCP connection will survive.
2. In firmware prior to version 2.20, bit 0 specified the TCP copy function.
If bit 0 is set (the default), TCP connections are kept open when the connection to the access point is lost.
If bit 0 is cleared (e.g., by sending set ip flags 0x6), if the module loses the access point connection while TCP is
connected, the connection is closed.
Default: 0x7
Example: set ip flags 0x6 // Clear bit 0
set ip gateway <address>
This command sets the gateway IP address, where <address> is an IP address in the form
<value>.<value>.<value>.<value> with <value> being a number between 0 and 255. If DHCP is turned on, the
gateway IP address is assigned and overwritten when the module associates with the access point.
Default: 0.0.0.0
Example: set ip gateway 169.254.1.1 // Sets the IP gateway to 169.254.1.1
set ip host <address>
This command sets the remote host’s IP address, where <address> is an IP address in the form
<value>.<value>.<value>.<value> with <value> being a number between 0 and 255. You use this command to make
connections from the WiFly module to a TCP/IP server with the IP address <address>.
Default: 0.0.0.0
Example: set ip host 137.57.1.1 // Sets the remote host’s IP address to 137.57.1.1
12345670
TCP connection status. See Notes (1), (2).
Bypass Nagle algorithm and use TCP_NODELAY.
TCP retry enabled (for a total of 96 packet retries).
UDP RETRY (attempts retry if no ACK from UDP).
DNS host address caching enabled.
ARP table caching enabled.
UDP auto pairing enabled.
Add 8-byte timestamp to UDP or TCP packets.
!
www.rovingnetworks.com Version 1.0r 9/21/2012 17
RN-WIFLYCR-UM
set ip localport <value>
This command sets the local port number, where <value> is a decimal number representing the port.
Default: 2000
Exampl: set ip localport 1025 // Sets the local port to 1025
set ip netmask <address>
This command sets the network mask, where <address> is an IP address in the form
<value>.<value>.<value>.<value> with <value> being a number between 0 and 255. If DHCP is turned on, the
netmask is assigned and overwritten when the module associates with the access point.
Default: 255.255.255.0
Example: set ip netmask 255.255.0.0 // Sets the netmask to 255.255.0.0
set ip protocol <flag>
This command sets the IP protocol, where <flag> is a bit-mapped register as shown in Figure 2. To be able to connect
to the WiFly module over TCP/IP (for example using telnet), you must set bit 2 of the IP protocol register. For the
module to accept both TCP and UDP set bits 1 and 2 (value = 3).
Figure 2. set ip protocol Command Bit-Mapped Register
!
Default: 2
Example: set ip protocol 18 // enables TCP and HTTP client mode
set ip remote <value>
This command sets the remote host port number, where <value> is a decimal number representing the port.
Default: 2000
Example: set IP remote 1025 // Sets the remote host port to 1025
set ip tcp-mode <mask>
This command controls the TCP connect timers, DNS preferences, and remote configuration options. <mask> is a hex
number referring to a bit-mapped register as shown in Figure 3.
NOTE: The TCPMODE register is available in firmware version 2.27 and higher.
12340
UDP.
TCP server and client (default).
Secure mode (only receive packets form an IP address that matches the stored host IP).
TCP client only.
HTTP client mode.
!
www.rovingnetworks.com Version 1.0r 9/21/2012 18
RN-WIFLYCR-UM
Figure 3. set ip tcp-mode Command Bit-Mapped Register
!
Default: 0x0
Example: set ip tcp-mode 0x4 // Forces the module to use DNS
set ip tcp-mode 0x10 // Disables remote configuration
set opt jointmr <value>
This command sets the join timer, which is the length of time (in ms) the join function waits for the access point to
complete the association process. <value> is a decimal number representing the number of ms. This timer is also
used as the timeout for the WPA handshaking process.
Default: 1000
Example set opt jointmr 1050 // Sets the join timer to 1,050 ms
set opt format <flag>
The command sets the HTTP client/web server information, where <flag> is a bit-mapped register as shown in Figure
4. See “Using the HTML Client Feature” on page 66 for more details.
Figure 4. set opt format Command Bit-Mapped Register
!
Default: 0x00
Example: set opt format 0x7 // The module sends sensor values
12340
Shorten the TCP connect timer (use with bit 1).
Shorten the TCP connect timer (use with bit 0).
Forces the module to use DNS rst to resolve the IP address, even if the host IP is set.
Reserved.
Disables remote conguration for security purposes.
12340
Automatically send an HTML header-based broadcast interval.
Send users binary data (converted to ASCII hex).
Sample the GPIO and ADC pins and format to ASCII hex.
Appends &id=<value>, where <value> is the device ID string that was set using set opt device <string>.
Appends the following key/value pairs to the HTTP message: &rtc=<time>, &mac=<address>,
&bss=<access point address>, &bat=<battery voltage>, &io=<GPIO in hex>, &wake=<wake reason>,
&seq=<sequence value>, where <time> is the realtime clock value in the message as a 32-bit hex value in
format aabbccddee and <sequence value> is a rolling counter of how many web posts have been sent.
!
www.rovingnetworks.com Version 1.0r 9/21/2012 19
RN-WIFLYCR-UM
set opt replace <char>
This command sets the replacement character you use to indicate spaces in the SSID and pass phrases, where
<char> is a single character. Each occurrence of the replacement character is changed into a space. Only the WiFly
command parser uses this replacement character.
Default: $ (0x24)
Example: set opt replace % // Sets the replacement character to %
set opt deviceid <string>
This command sets the configurable device ID, where <string> is up to 32 bytes long. You can use <string> for serial
numbers, a product name, or to show other device information. The module sends the device ID as part of the UDP
broadcast hello packet. You can view the device ID’s current value with the get option or show deviceid commands.
Default: WiFly-GSX
Example: set opt deviceid my_wifly // Sets the device ID to my_wifly
set opt password <string>
This command sets the TCP connection password, where <string> is up to 32 bytes long. This setting provides
minimal authentication by requiring any remote device that connects to the module to send and match the challenge
<string>. When a connection is opened, the module sends the string PASS? to the remote host. The remote host must
reply with the exact characters that match the stored password in one TCP packet; otherwise, the module closes the
connection. To disable the password feature, use 0 (the default).
Default: “” (no password required)
Example: set opt password my_password // Sets the TCP connection password to my_password
set q sensor <mask>
This command specifies which sensor pins to sample when sending data using the UDP broadcast packet or the
HTTP auto sample function, where <mask> is a bit-mapped register.
NOTE: In versions of firmware prior to 2.23, this command is named set option sensor.
Default: 0
Example: set q sensor 0xff // Enables all sensor inputs
!
!
www.rovingnetworks.com Version 1.0r 9/21/2012 20
RN-WIFLYCR-UM
set q power <value>
This register automatically turns on the sensor power, where <value> is shown in Table 5. This parameter sets an 8-bit
register with two 4-bit nibbles. If the top nibble is set, power is applied upon power up and removed upon power down
or sleep. If the bottom nibble is set, power is applied when a sampling event occurs such as:
• UDP broadcast
• Automatic web posting of sensor data
• Power is removed immediately after sampling is complete
Table 5. set q power Command Sensor Pin Voltage Settings
Value
Sensor pin voltage
0
Turn off the sensor power.
1
Ground the sensor pin.
2
1.2-V internal regulated reference.
3
VBATT input pin.
4
3.3-V output of on board regulator.
Default: 0
Example: set q power 0x20 // Sets power to 1.2 V automatically upon power up
set q power 0x02 // Sets power to 1.2 V when a sampling event occurs
set q power 0x40 // Sets power to 3.3 V automatically upon power up
set q power 0x04 // Sets power to 3.3 V when a sampling event occurs
!
!
www.rovingnetworks.com Version 1.0r 9/21/2012 21
RN-WIFLYCR-UM
set sys autoconn <value>
This command sets the auto-connect timer in TCP mode, where <value> is a decimal number from 0 to 255 as shown
in Table 6. Setting this parameter causes the module to connect to the stored remote host periodically as specified by
<value>.
NOTE: To use the auto-connect timer, you must store the remote host’s IP address and port in the WiFly module
using the set ip host <address> and set ip remote <value> commands.
Table 6. Auto-Connect Timer Settings
Value
Description
0
Disable the auto-connect timer (default).
1
Connect to the stored remote host IMMEDIATELY upon power
up or when waking from sleep.
2 - 254
Connect to a stored remote host every <value> seconds.
255
Connect to a stored host IMMEDIATELY upon power up or when
waking from sleep and go back to sleep IMMEDIATELY as soon
as the TCP connection closes.
Default: 0
Example: set sys autoconn 5 // The module connects to the host every 5 seconds
set sys autosleep <value>
This command sets the auto-sleep timer in UDP mode, where <value> is a decimal number. If the protocol is set to
UDP ONLY, this timer acts as a quick sleep function. The module sleeps <value> ms after transmission of the first
UDP packet. Setting <value> to 0 disables the auto-sleep timer.
Default: 0
Example: set sys autosleep 2 // Sets the timer to sleep after 2 ms
set sys iofunc <mask>
This command sets the I/O port alternate functions, where <mask> is a hex number referring to a bit-mapped register.
For more details see “Setting GPIO Direction, Alternate Functions & Disabling LEDs” on page 51.
Default: 0x0
Example: set sys iofunc 0x7 // Disables the WiFly evaluation board LEDs
!
www.rovingnetworks.com Version 1.0r 9/21/2012 22
RN-WIFLYCR-UM
set sys mask <mask>
This command sets the I/O port direction, where <mask> is a hex number referring to a bit-mapped register. For more
details see “Setting GPIO Direction, Alternate Functions & Disabling LEDs” on page 51.
NOTE: To set the GPIO pins as inputs or outputs instantly, use the set sys mask 0xABCD 1 command, which does
not require a reboot.
Default: 0x20F0 (for RN-131)
0x21F0 (for RN-171)
Example: set sys mask 0x0 // Sets all pins as inputs
set sys printlvl <value>
This command controls the debug print messages printed by the WiFly module on the UART, where <value> is one of the
values shown in Table 7. Refer to “Setting Debug Print Levels” on page 56 for more information.
Table 7. Debug Print Message Settings
Value
Description
0
Quiet mode. Messages are not printed when the module wakes up or powers up.
1
Print all status messages.
2
Print only critical network access point connection level status, e.g., Associated! or Disconnect from <SSID>.
4
Print the DHCP and IP address status information. After you have verified the module’s configuration, you can
turn off this option so that the messages do not interfere with the data.
0x4000
Change the scan format output to an MCU friendly format.
0x10
Enables the UART heartbeat message. See “UART Heartbeat Messages” on page 58 for more details.
Default: 0x1
Example: set sys printlvl 2 // Sets the debug print messages to only critical network
// connection status
set sys output <mask> <mask>
This command sets the output GPIO pins high or low, where <mask> is a hex number referring to a bit-mapped
register. The optional <mask> sets a subset of the pins.
Default: None
Example: To toggle GPIO8, use the following commands:
set sys mask 0x21f0 // Set GPIO8 as output
set sys output 0x0100 0x0100 // Drives GPIO8 high
set sys output 0x0000 0x0100 // Drives GPIO8 low
!
www.rovingnetworks.com Version 1.0r 9/21/2012 23
RN-WIFLYCR-UM
set sys sleep <value>
This command sets the sleep timer, where <value> is a decimal number. The sleep timer is the time (in seconds)
after which the module goes to sleep. This timer is disabled during an open TCP connection. When the TCP
connection is closed, the module counts down and puts the module to sleep after <value> seconds. Setting the value
to 0 disables the sleep timer, and the module will not go to sleep based on this counter.
NOTE: Be sure to set the wake timer before issuing the sleep timer if you are not using an external wake up
signal; otherwise, the module will never wake up.
See “System & Auto-Connect Timers” on page 48 for more details on using system timers.
Default: 0
Example: set sys sleep 5 // Module sleeps 5 s after TCP connection closes
set sys trigger <flag> or <mask>
With this parameter setting, the module wakes from sleep state using the sensor input 0, 1, 2, and 3, where <flag> is
a decimal number referring to a bit-mapped register as shown in Table 8 and <mask> is a hex number. You use
either <flag> or <mask> with this parameter setting. This command sets the sensor input(s) to wake on (0 to 3).
Setting <flag> to 0 disables wake on sensor inputs.
Table 8. set sys trigger Command Bit-Mapped Register
Bit Position
Description
0
Trigger sensor input 0.
1
Trigger sensor input 1.
2
Trigger sensor input 2.
3
Trigger sensor input 3.
4
Enable WPS function.
5
Enable sleep on GPIO8.
Table 9 describes how you can wake the module using sensor input.
Table 9. Sensor Input Trigger Values
Wake on Sensor Input
Value
Command
0
1
set sys trigger 1
1
2
set sys trigger 2
2
4
set sys trigger 4
3
8
set sys trigger 8
NOTE: Setting the system trigger value to 0x10 enables WPS functionality. WPS is disabled by default.
!
www.rovingnetworks.com Version 1.0r 9/21/2012 24
RN-WIFLYCR-UM
Setting the trigger value to 0x20 (i.e., using <mask>) puts the module to sleep when GPIO8 is pulled high. To enable
this feature, use the set sys trigger 0x20 command. This command makes GPIO8 an interrupt pin and puts the
module to sleep as soon as it is pulled high, regardless of the module’s state; the module goes to sleep even if it is
associating with a network or has an open, active TCP connection.
This command is useful for when the module is failing to associate with network because it is out of range (or for any
other reason), or if the module must be put to sleep quickly.
NOTE: GPIO8 must be low on power up and stay low until you want to put the module to sleep.
Default: 0x1
Example: set sys trigger 0x10 // Enable WPS functionality
set sys value <mask>
This command sets the default value of the GPIO pins’ outputs upon power-up, where <mask> is a hex number
representing a bit-mapped register. The GPIO pins that are configured as outputs can be driven high or low on powerup or when the module wakes from sleep. The default power-up states can be set ONLY for the GPIO pins that are set
as outputs. Setting the value to 1 makes the default power-up state high; setting the value to 0 makes the default
power-up state low.
To configure GPIO pins as outputs, use the set sys mask <value> command.
NOTE: GPIO pins 4, 5, and 6 are used by the firmware to blink the status LEDs. To set the default power up
states for these GPIO pins, you must first disable their use by the firmware using the set sys iofunc 0x7
command.
Default: 0x0
Example: To configure power-up states of GPIO8 (output by default):
set sys value 0x0100 // Sets GPIO8 high upon power-up
set sys value 0x0000 // Sets GPIO8 low upon power-up
set sys wake <value>
This command sets the automatic wake timer, where <value> is a decimal number representing the number of
seconds after which the module wakes from sleep. Setting <value> to 0 disables. See “System Timers & Auto-Connect
Timers” on page 48 for more details.
Default: 0
Example: set sys wake 5 // The module wakes after 5 seconds
set time address <address>
This command sets the time server address, where <address> is an IP address in the form
<value>.<value>.<value>.<value> with <value> being a number between 0 and 255. This command applies to SNTP
servers.
Default: 129.6.15.28
Example: set time address 208.109.78.52 // Sets the time server address as 208.109.78.52
!
www.rovingnetworks.com Version 1.0r 9/21/2012 25
RN-WIFLYCR-UM
set time port <value>
This command sets the time server port number, where <value> is a decimal number. 123, the default, is typically the
SNTP server port.
Default: 123
Example: set time port 1052 // Sets the time server port to 1052
set time enable <value>
This parameter tells the module how often to fetch the time from the specified SNTP time server, where <value> is a
decimal number representing minutes. The default (0) disables time fetching. If <value> is 1, the module fetches the
time only once on power up. If <value> is greater than 1, the modules fetches the time every <value> minutes.
Default: 0
Example: set time enable 5 // The module fetches the time every 5 minutes
set time raw <value>
This parameter setting allows you to set the RTC raw value from the console, where <value> is a decimal number in
seconds. The RTC ticks at 32,768 Hz.
Default: None
Example: set time raw 1 // Set to 1 second
set uart baud <value>
This command sets the UART baud rate, where <value> is 2400, 4800, 9600, 19200, 38400, 57600, 115200,
230400, 460800, or 921600.
NOTE: The RN-134 evaluation board’s RS-232 interface cannot exceed 230,400 baud.
Default: 9600
Example: set uart baud 19200 // Sets the baud rate to 19,200 baud
set uart flow <value>
This command sets the flow control mode and parity, where <value> is a hex number. The setting is in the upper nibble of
the hardware flow control setting. The default is flow control disabled with parity set to none/no parity.
NOTE: Once flow control is enabled, it is important to drive the CTS pin properly (i.e., active-low enabled). If CTS
is high, the module does NOT send data through the UART and further configuration in command mode
is problematic because no response is received.
Default: 0
Example: set uart flow 0x21 // Even parity with flow control
set uart flow 0x20 // Even parity without flow
set uart flow 0x31 // Odd parity with flow control
set uart flow 0x30 // Odd parity without flow control
!
www.rovingnetworks.com Version 1.0r 9/21/2012 26
RN-WIFLYCR-UM
set uart instant <value>
This command immediately changes the baud rate, where <value> is 2400, 4800, 9600, 19200, 38400, 57600,
115200, 230400, 460800, or 921600. This command is useful when testing baud rate settings or when switching the
baud rate “on the fly” while connected over TCP via telnet. Using this command does not affect configuration. The
module returns the AOK response, and then the module exits command mode.
NOTE: In firmware version 2.22 and lower, the module does NOT return an AOK over telnet before exiting
command mode.
If used in local mode, the baud rate changes and the module sends AOK using the new baud rate. If the host
switches to the new baud rate immediately, the host may see the AOK string at the new baud rate. Depending on the
baud rate, it takes at least ten times the bit rate for the module to issue the first character.
Default: Not applicable
Example: set uart instant 19200 // Sets the baud rate to 19,200 baud
set uart mode <mask>
This command sets the UART mode register, where <mask> is a hex number masking a bit-mapped value as shown
in Figure 5.
Figure 5. set uart mode Command Bit-Mapped Register
!
Notes:
1. With firmware version 2.27 and higher, bit 4’s functionality has changed. When a TCP connection is closed, if there is RX data
in the UART receiver, it is flushed by default.
When you enable bit 4 using the set uart mode 0x10 command, the module holds the UART data in the buffer until:
• More characters come in, after which the buffer is flushed.
• No characters come in and a new connection is made, after which the characters are forwarded.
Default: 0
Example: set uart mode 0x10 // Enable the UART data buffer
!
12340
NOECHO. Disables RX data echoing while in command mode.
DATA TRIGGER. Makes a connection on RX data.
Reserved.
Enable sleep on RX BREAK signal.
UART RX data buer, Note (1).
5
The version string <x.xx>\r\n is replaced with the replace character in the command prompt ($ by default)..
!
www.rovingnetworks.com Version 1.0r 9/21/2012 27
RN-WIFLYCR-UM
set uart raw <value>
This command sets a raw UART value, where <value> is a decimal number representing the baud rate. You use this
command to set non-standard baud rates. The lowest possible baud rate is 2,400.
Using non-standard raw baud rates with hardware flow control can be more useful at speeds as the microcontroller
interfaced to the module may be able to better match the UART speed and get better results.
Table 10 shows the supported raw baud rates:
Table 10. Supported Raw Baud Rates
Raw Baud Rate
Comment
458,333
This is 460,800.
500,000
Raw baud rate.
550,000
Raw baud rate.
611,111
Raw baud rate.
687,599
Raw baud rate.
785,714
Raw baud rate.
916,667
This is 921,600.
1,100,000
Raw baud rate.
Default: Not applicable
Example: set uart raw 7200 // Sets the baud rate to 7,200 baud
set uart tx <value>
This command disables or enables the UART’s TX pin (GPIO10), where <value> is 1 or 0. Disabling the pin
(<value> = 0) sets GPIO10 as an input with a weak pull down.
NOTE: Firmware version 2.36/2.45 and higher supports parity with the set uart flow command.
Default: Not Applicable
Example: set uart tx 1 // Enable the UART’s TX pin
!
!
www.rovingnetworks.com Version 1.0r 9/21/2012 28
RN-WIFLYCR-UM
set wlan auth <value>
This command sets the authentication mode, where <value> is shown in Table 11. You only need to set this
parameter if you are using automatic join mode 2, i.e., the set wlan join 2 command.
NOTE: During association the module interrogates the access point and automatically selects the authentication
mode.
The firmware supports he following security modes:
• WEP-64 and WEP-128 (open mode only, NOT shared mode)
• WPA2-PSK (AES only)
• WPA1-PSK (TKIP only)
• WPA-PSK mixed mode (some access points, not all are supported)
Table 11. set wlan auth Command Authentication Modes
Value
Authentication Mode
0
Open (Default)
1
WEP-128
2
WPA1
3
Mixed WPA1 and WPA2-PSK
4
WPA2-PSK
5
Not used
6
Ad hoc mode (join any ad hoc network)
8
WPE-64
Default: 0
Example: set wlan auth 4 // Use WPA2-PSK authentication
!
www.rovingnetworks.com Version 1.0r 9/21/2012 29
RN-WIFLYCR-UM
set wlan channel <value> <flag>
This command sets the WLAN channel, where <value> is a decimal number from 1 to 13 representing a fixed
channel and <flag> is the optional character i (meaning immediate). If you set the channel to 0, the modules performs
a scan using the SSID for all the channels set in the channel mask. The i flag allows you to create a temporary AP
mode setup without having to reboot or save the settings. See Example 2.
Default: 0
Example 1: set wlan channel 2 // Set the WLAN channel to 2
Example 2: set wlan channel 1 i
set wlan join 7
set ip address 1.2.3.4
set ip gateway 1.2.3.4
set ip netmask 255.255.255.0
set ip dhcp 4 // Use DHCP server
join <SSID> // Module goes into AP mode
set wlan ext_antenna <value>
This commands determines which antenna is active, where <value> is 0 (use the chip antenna) or 1 (use the U.FL
connector). Only one antenna is active at a time and the module must be power cycled after changing the antenna
setting.
NOTE: This command applies only to the RN-131 module; it is not applicable to the RN-171. If you send this
parameter to the RN-171, it issues an error message ERR: Bad Args.
Default: 0
Example: set wlan ext_antenna 1 // Use the U.FL antenna
!
Loading...