Here is the. This script is just a mini protocol I set up to test. Once connected with the wifly module you can send text such as "get" "hello" or "quit" and the wifly module should respond back. Using Telnet I can successfully connect the first time and send commands to the Arduino including "quit" to terminate the connection calls the client.
But when I try to reconnect though Telnet , it says the connection was successful, but on the Arduino it's still looping thinking the client is still false. I know right, I'm getting mixed messages from Telnet vs Arduino. None of the commands work obviously since the Ardunio is still looping waiting for a client that evaluates to true. I'm going to take a look at WiFlyServer from the library I imported and see if I can dig up the problem, because somehow that server.
So I found the reason for the problem. It was in the WiFlyServer. The code that was causing the reconnect issue was in fact the server. Right at the top of the method, there is a check:.
For some reason when I comment this out, I can connect and reconnect perfectly fine and everything works as it should. I will now dive into the library and see if I can fix this, I'm not exactly sure what this is doing, but it gets called when the server connection is not active and is somehow blocking subsequent connections. The problem with this solution is that the Arduino always thinks it has found a client since client and client. Even client.
Even with this flaw it still picks up a new client when it comes along which is why it works. Well, when you're calling client. Have you tried to include the following code in your loop to tell the Arduino to create the WiFly AdHoc network again?
This may or may not work. I don't have one myself and haven't played with the Wifly shield but it's worth a try. Only for the ethernet shield. Upvote 0. Erel said:. Last edited: Apr 3, Computersmith64 said:. Actually - I think this one is the same as the one you are using:. You must log in or register to reply here. Similar Threads. Hating it. Help please. Tronak Dec 1, B4R Questions. Replies 3 Views 1K. Dec 2, Erel. Erel May 1, B4R Questions. Replies 14 Views 6K.
After a few seconds, the WiFly should print out its IP address. In your browser, type the IP address that was printed out in the Terminal into the address bar.
After a few seconds, you should see a web page with these three buttons load. As long as everything is connected correctly, each button on the website should light up the corresponding LED when clicked. The change will not be instantaneous as the commands need to propagate from the browser, through the network, and to your WiFly shield. You can even control it from your smart phone as long as it's connected to the same wireless network as the WiFly shield.
It is also worth noting that the sketch prints data to the terminal by default. This will add some time to this delay. If the red or yellow LED on the WiFly shield are blinking continuously, it is having a problem connecting to your wireless network.
See the datasheet for more info on LED statuses. If you have a steady blinking green LED and your Arduino is printing out a valid IP address but you are not seeing a webpage load, then the problem is most likely in the code or in your wireless network settings. Makes sure you selected the correct security settings and make sure you save your settings to the WiFly config file after you have set all the necessary settings. Try changing up the code to add different colors and more buttons.
You can also take a look at the server example that comes with the WiFly library. This example reads the analog inputs on the Arduino and posts them to a webpage. See if you can add digital inputs and analog outputs to the same webpage. The firmware for the WiFly module is updated occasionally.
Luckily for you, there is a simple way to update your module to the latest version. To check which version of the firmware your WiFly shield is running, upload the Terminal sketch, enter command mode, and enter this command:. Before we update the firmware, let's go over the configuration files stored within the WiFly and how to add other config files. Using the terminal sketch mentioned on the WiFly Library page , create a connection to the module, and enter command mode.
Depending on what firmware version you have, you should see something like this:. One great feature of the WiFly is its ability to store multiple configuration files.
For instance, if you wanted to use the WiFly at both your home and your work, you could create two separate config files, each with the correct settings for both locations. To do so, set all the settings for one location such as SSID, pasphrase, security. Then use the save command followed by the name you want to call that configuration.
Notice that there is now two config files named home and work. Now, to use one of those config files, simply issue the load command followed by the name of the file. It's impotant to note that even though there are separate config files, the WiFly always uses what is stored in the default config file, so after you load a config file, it's best to save it to the default config file using just the save command.
Now, even after a firmware update, you should be able to load all of the settings you had before. You can delete a config file using the del command. Directions on how to update the firmware can be found on Microchip site , but we will also go over the process here. Again, use the terminal sketch to enter command mode.
You must be connected to the Internet in order to get the firmware update from Roving Networks, so follow the directions on the Connecting to a Network page to connect to your wireless network.
While you are connected, you should still be able to issue commands. We now need to set the FTP settings on the module and point it to the correct website from which to retrieve the new firmware.
Depending on 1 how old your module is and 2 how many settings you have changed, you may need to change several settings. To get the update, you must make sure the FTP address is the correct one. The Roving Networks page say the the firmware must be pulled from rn. Now, set the FTP address to the one returned during the ping, if it does not match the one stored in memory. Also make sure the user name and password match the ones in the image below. These should be the default values unless you changed them in your configuration.
Once the update has finished, you need to reboot the module, give it a factory RESET, and then reboot it again. Now, using the ls command, we can see the new firmware. The old firmware is still stored in the module in case you need to revert back to an older version. To boot from an older firmware version, use the boot image command. In the image above, you can see that the older firmware 2. So we issue the boot image 11 command to get back to that version. As of this writing, the most up to date version of the firmware that will be downloaded with this process is Ver 4.
This is just the basc hookup of the WiFly Shield. The shield works very well as a host or client. To use it as a host, many projects also include an SD Shield to hold large amounts of data to be served, rather than save them on the Arduino chip. Check out the other examples you downloaded with the WiFly Shield library. There are some great web client and server examples as well as a lot of other great info on using the shield.
To get the most out of your shield, be sure to read the reference guides and datasheets. Here are links to all the most important ones. Need Help? Mountain Time:
0コメント