Delay in running default.bas
Posted: Sat Aug 27, 2016 12:33 pmI'm not sure this really counts as a bug or as a wish!
Reading the reply to another member's query, I note that the delay in running the default program on start-up is by design, so that you have the opportunity to change the program before it runs. I can see the logic of this.
However, I (and, I suspect, many others) want to use this chip to run very low-powered applications. This can be achieved by putting the chip into SLEEP, when it consumes very little, and I could do this, then wake it up every minute to run some simple checks taking a fraction of a second, then put it to sleep again - except I can't! As the system takes around half a minute to come up, I am consuming far more power than I want to - or can afford.
Could there be some way of programmatically removing the delay, so that very short bursts of activity could be enabled followed by periods of sleep? This way a system could run for days on a very small power source.
Alternatively, could there be a different form of SLEEP that does not require the system to reboot from scratch each time - a kind of LIGHT.SLEEP - so that this could be achieved?
Phil
Reading the reply to another member's query, I note that the delay in running the default program on start-up is by design, so that you have the opportunity to change the program before it runs. I can see the logic of this.
However, I (and, I suspect, many others) want to use this chip to run very low-powered applications. This can be achieved by putting the chip into SLEEP, when it consumes very little, and I could do this, then wake it up every minute to run some simple checks taking a fraction of a second, then put it to sleep again - except I can't! As the system takes around half a minute to come up, I am consuming far more power than I want to - or can afford.
Could there be some way of programmatically removing the delay, so that very short bursts of activity could be enabled followed by periods of sleep? This way a system could run for days on a very small power source.
Alternatively, could there be a different form of SLEEP that does not require the system to reboot from scratch each time - a kind of LIGHT.SLEEP - so that this could be achieved?
Phil