www.rovingnetworks.com
Version 1.0r 9/21/2012
6
RN -W IFLYCR -U M
•
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
