Can't connect over Telnet to Wifly

Wireless & IoT
1

I have problems to connect to my WiFly GSX over telnet.

Yesterday it work without problems. I tried to connect the Wifly to my access point, but something went wrong.

I set GPIO 9 high to reset my configuration and set the Wifly in adhoc mode.

I can ping the Wifly over cmd, but I can’t connect over telnet to configure.

I tried it with the standard IP adress (169.254.1.1) and the standard port (2000), but there´s no response.

I set the IP adress of my computer in the same range (169.254.1.x)

Does someone can help me?

Sorry about my bad english :slight_smile:

Thanks!

moe_joe

2

I think my problem is:

I set up a host ip (192.168.2.55:2000), but the IP of the Wifly is 169.254.1.1:2000. So the host ip is in the false range.

I think the host ip won’t reset when I set GPIO9 to high.

How can I fix this problem?

3

i am having the same problem. I run my wifly in ad-hoc mode and connect my computer to the ad-hoc network. I can ping my wifly but for some reason i can not telnet to it. Also moe_joe the address range is right because the default subnet mask is 255.255.0.0, so the last 2 numbers of the ip do not matter. I was able to connect to mine, but as soon as i used a bunch of configuration commands and saved then rebooted is when i ran into this error. If anyone knows what could be causing this, any help would be much appreciated… also here are my telnet and ping commands:

C:\Users\Ramrod>telnet 169.254.1.1 2000
Connecting To 169.254.1.1...Could not open connection t
 Connect failed

C:\Users\Ramrod>ping 169.254.1.1

Pinging 169.254.1.1 with 32 bytes of data:
Reply from 169.254.1.1: bytes=32 time=1ms TTL=255
Reply from 169.254.1.1: bytes=32 time=7ms TTL=255
Reply from 169.254.1.1: bytes=32 time<1ms TTL=255
Reply from 169.254.1.1: bytes=32 time=1ms TTL=255

Ping statistics for 169.254.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 7ms, Average = 2ms
4

If Wifly module is in ad hoc mode, it is nothing to do with your pc ip setting.

But pc or laptop having the terminal program must connect to ad hoc network.

The procedure is:

Put Wifly module in ad hoc mode

PC or laptop having Terminal (telnet program) must connect to Wifly network.

Wifly network name is Wifly EZX-xx where xx can be any number between

00 to 99 as per your module MAC.

Open Terminal, key in relevent info.

Sometime it may take 2 to 3 times to get connected

Once connected, you will see HELLO and green light on module is

permenrly ON from blinking.

Good luck.

5

stogeybrown:
I was able to connect to mine, but as soon as i used a bunch of configuration commands and saved then rebooted is when i ran into this error. If anyone knows what could be causing this, any help would be much appreciated…

You may need to do a “Factory Reset” by sending it the “factory RESET” command or by toggling the GPIO9 pin (see page 84 of the manual).