Wow, thanks for the fast response.
As a seperate check I used zterm (Mac) to access the Arduino, but that did not work either. $$$ resulted in nothing coming back. On a completely seperate topic, I found another WiFLy terminal test harness, but it uses stdio.h, which is not in my library list, or appears to be installed. Do I need to download this?
@Static, if I make progress I will keep you posted.
@Philip, thanks for the quick response!
The code to detect connection failure hasn't been written--the code is just hanging because it's not getting the expected response. If it gets as far as the join method call then I would think it is actually communicating with the module okay.
Good point, if it does not receive the "Associated!" command its going to run until it get to EOM. Would that not return a false to :join() and fall through?
My suggestion is to remove the call to join entirely and just let the code fall through to the loop(). At that point you should be able to send commands directly from the serial console.
I will try this, its interesting you note this, as the module should be in 'command mode'. Does the module remain in command mode across reboots?
Also, to make things easier to track I suggest unpowering the Arduino and WiFly shield after uploading a sketch until you sort things out.
Sorry not sure what you mean by 'unpowered', it needs to be powered in order to send serial commands? Do you have suggestions on how to track this, I have been using simple Serial.print messages to debug, are there other approaches?