I have set up my wifly to manually start in ad-hoc mode so i can configure it, but using the default address and port when telnetting to it, i get a connection refused error. I can ping the wifly and get a valid response so I know it is there. Right before this happened, i had configured it to auto join my network, but i had used a wrong ip, so i needed to reconfigure it. Since putting pio9 high at start gives a default ip and port, I thought I would have no problem, but for some reason I cant telnet to it anymore.
I can connect to it from my PC, so I know the network is being created, and I can ping it. I tested the voltage at each pin and ~3.3v is being output, so i dont think that is a problem either. Anyone else have this problem and fix it or have an idea on how to fix it? thanks in advance.
This actually worked, I had opened a ticket with their support and they suggested the same thing. During this process I also think I found out why i could not telnet into my device. I still needed to update the firmware on it and since i dont have a serial connection all I could do was telnet to it. To be able to telnet to my wifly on my own network I had to download portpeeker and change my tcp port to 5000. Once i did this i could telnet to my device with the ip and port 192.168.X.X 2000. From there I was able to update my firmware to the soft ap one. Now i can power up my device like I would with ad-hoc mode except its in soft-ap mode. I can telnet to it with the ip and port 1.2.3.4 2000.