Imp goes unresponsive after 57 seconds

Hi,

I am working through an ac dimmer project. Everything works great for the first 57 seconds, then the imp seems to shut down. My output pin (pin 2) goes high, I no longer see any updates in the log window, and the imp is unresponsive to any uploading of new code.

I am able to restart the imp by disconnecting and reconnecting the power. Or… I can wait until 3 minutes have elapsed when I get an “imp crashed, reason: wifi error” message, and the device reboots.

I am transmitting info throughout (server.show() messages every second).

Any ideas as to what’s going on here?

I’ve tried two different external power supplies and my laptop as a power source.

Thanks!

Robert

That’s kinda strange and unexpected. Release-14 is out likely tomorrow and that may help (a lot has changed) - can you wait and see how the new release works for you?

Monday, January 14, 2013 10:20:38 PM: Device configured to be "Irrigation"
Monday, January 14, 2013 10:20:58 PM: Power state: online=>offline
Monday, January 14, 2013 10:26:49 PM: Device booting
Monday, January 14, 2013 10:26:50 PM: Device configured to be "Irrigation"
Monday, January 14, 2013 10:27:19 PM: show: value3
Monday, January 14, 2013 10:27:19 PM: show: valve2
Monday, January 14, 2013 10:27:19 PM: show: triac4
Monday, January 14, 2013 10:27:33 PM: show: value4
Monday, January 14, 2013 10:27:33 PM: show: valve3
Monday, January 14, 2013 10:27:33 PM: show: triac8
Monday, January 14, 2013 10:28:45 PM: show: value7
Monday, January 14, 2013 10:28:45 PM: show: valve6
Monday, January 14, 2013 10:28:45 PM: show: triac64
Monday, January 14, 2013 10:29:37 PM: Power state: online=>offline

As I show IMP goes off line with no change in my software

We believe we’ve worked this one out. Power cycle your imp and things (NAT timeouts excepted) should be ok.