User manual

!
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