Hello, I am a novice wifi person in need of some help. I am trying to send data via UDP from a Wifly 174p development module to a specific iPhone app. The app author provided the following information:
“UDP packets using the local subnet to port 43211”
I have successfully connected to the iPhone and sent data via a telnet app, but cant seem to get the app to see the UDP heartbeat.
So far I have successfully configured the Wifly in adhoc mode and successfully configured it to send data via UDP. See below.
I also Tried connecting via both static and auto IP. Tried various combinations of ip address and subnets.
The iPhone connects to the Wifly’s adhoc network, but the app does not see the heartbeat message.
Any suggestions on how to proceed would be appreciated.
Thanks,
Chuck
831-325-3131
Configuration adhoc mode (from manual page 70):
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
Configuration for UDP (manual page 49)
The commands to enable UDP data transfer are:
Associate to a network:
set wlan ssid // set the network name
set wlan phrase // set the passphrase for WPA and WPA2 modes
Set up the protocol and port number
set ip proto 1 // enable UDP as the protocol
set ip host // set the IP address of remote host
set ip remote // set the remote port number on which the host is listening
set ip local // set the port number on which the WiFly module will listen
save // saves the settings in config file
reboot // reboots the module so that the above settings take effect