After the light turns green indicating that the connection to the cloud is successful, the imp shows up in the planner as blank, as it should. I can click on the grey settings button on the upper left of the imp in the planner, get the list of available firmware, and select one, as I should be able to.
The hope-crushing, anger-inciting despair sets in when I dutifully sit there waiting for the blue imp rectangle do something as I had told it do with
imp.configure("Do something please,", [],[]); server.show("for the love God, do anything!);.
Despite toggling from different firmware, deleting all my firmware,decommissioning my imp, re-ccommissioning it, powering up and down, the server log just keeps looping between booting, going online, going offline, then back to booting.
This has happened before. After performing those steps again in no real particular order, I eventually get past it and can start writing code again. Then after the however-so-many uploads to my imp, it will get in this lockdown loop.
To be honest, I don’t really know what I’m doing because my background is in art but I have been doing some slightly advanced work in Arduino and processing for the past three years. I’ve never really coded out side those environments. I understand that the imp is a significantly more complex platform than Arduino, but it does Arduino-like things with the Internet at a price well, well bellow an Ardy w/ wifi options. This is what attracted me to it.
This is also why I can understand this issue of mine occurring after I upload some egregiously buggy code, or do something like :
`
function breakEverthing(onButton) {
while(onButton==1){
server.log(hardware.millis());
}
}
breakEverything(1);`
may cause things to stop working because unlike Arduino, the connection between the imp and console must go through the many tubes that is the Internet.
I’m curious if any one else out there has run into this, and what their magic dance of glory was to fix it.
Impin’ it in San Diego,
-Mike