another problem occurred :). i can now get all the responses from the module, so far so good. the next thing i tried was to execute the “scan” command with the wifly Rn133-g module. but what i get back was “SCAN: Found 0…”. after that i activated the external antenna and it worked. i now get the local servers (look at screenshot 1 and screenshot 2).
The problem is that the internal wlan module from ym laptop doesnt “see” the wifly module in the list of available access points. how can configure the module so that my laptop will recognize it?
ive attached a few more screenshots of my wlan settings, sorry that they are in german if somebody needs translation just ask me, hope somebody can help me thanks in advance
im good with electronics but not with wlan specifications. what exactly is ad hoc mode? what im trying to do is this:
develop a java programm that uses the internal wlan module from my laptop to search the area for access points, and so he must find the wifly module rn131-g and establish a connection. so my question is how can i configure the module as an access point? so that my laptop will “see” it in the list of available access points .
Ad hoc mode would be what you are hoping for. The card by default is a client (not an access point) so it wouldn’t accept connections or send out a connection beacon.
In ad hoc mode it can present itself and accept connection.
To enable ad hoc mode, you can place pin IO9 high (3.3V) at power up.
You can also configure it via the standard WLAN serial commands.
Check out the set wlan join command and read the section on ad hoc networking (15 I believe, page 44 numbered)
From command mode, the module is configured for adhoc mode using the join command. You will also
need to set the ssid and channel.
set wlan join 4
set wlan ssid my_adhoc_network
set wlan chan 1
Turn off DHCP and set the IP address and netmask so other devices know where to connect to the adhoc
WiFly GSX. Since auto IP fixes the first two bytes of the IP address you want to use the netmask of
255.255.0.0 so that other device connecting to the module can be reached. Alternatively you can set the
netmask to a smaller subnet if the other device’s IP addresses are begin statically to the same subnet as the
adhoc device
set ip address 169.254.1.1
set ip netmask 255.255.0.0
set ip dhcp 0
Be sure to save your configuration, then upon reboot the module will be in adhoc mode.