User`s guide

RN-WIFLYCR-UG
www.rovingnetworks.com Version 1.2r 4/30/13 page 7
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.
When the WiFly module powers up, it attempts to auto-associate with the access point
stored in its configuration settings if the auto join feature is enabled. In firmware
version 4.0 and higher, the auto join feature is disabled by default. Enable it using the
ASCII command set wlan join 1.
You can disable the auto-associate feature (default behavior) using the set wlan join 0
command. This command prevents the WiFly module from attempting to associate with
a network that does not exist.
1.2.2 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
RN134 board, GPIO9 is on pin 1 on the jumper block (J2). For the RN174 board,
GPIO9 is on the J6 connector. Upon power up with GPIO9 high, the WiFly module cre-
ates 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 set-
tings.
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.
Note: Roving Networks suggests using either the TeraTerm (Windows OS) or
CoolTerm (Mac OS-X) terminal emulator program.
NOTICE
Firmware version 4.0 and higher does not support ad hoc mode (these versions sup-
port soft AP mode). If ad hoc mode is required, use firmware version 2.38.3.