Please read the "group post" I made above.
croyles wrote: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?
follower wrote: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?
If the code had been written, yes. But it hasn't been written so it just gets into an infinite loop and never fails. The troubleshooting tool I mentioned in the post above avoids any configuration of the WiFly module itself entirely.
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?
If only the Arduino is reset (via reset button or auto-reset from IDE) then the WiFly module stays in its current state. If the WiFly module is *actually* rebooted/reset (which doesn't normally happen) then it should exit command mode. If the power is removed from the Arduino and the module and then replugged (one of the required troubleshooting steps) then the WiFly module should no longer be in command mode when power is applied. (I say "should" because I've had a situation where a (I think) beta firmware caused command mode to sometimes be entered into automatically after an upgrade and/or power was applied--can't remember the specifics but hopefully it shouldn't happen to you.
follower wrote: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?
That should have been "unpowered and then repowered" (i.e. unplugged and then plugged in).
I have been using simple Serial.print messages to debug, are there other approaches?
Hopefully this post and the troubleshooting tool will help isolating the issue you're having with the board.
Thanks for your patience with this.