50g Random Turn ON

[DavidM]

(12-23-2016 04:05 PM)Gerald H Wrote:  { "SUN 18.12.16 13:55:27" "THU 22.12.16 15:00:29" }. Does this seem to make sense? Is any pet theory confirmed?

Well at the very least it seems to coincide nicely with other reports of ARM-based systems turning themselves on at intervals of 97 hours ( + the appropriate auto-shutdown period for your calculator).

(12-23-2016 06:17 PM)Paul Berger (Canada) Wrote:  4 Days 1 Hour and 5 minutes, almost exactly what I got in my first run on my 49G+ . I have 4 calculators set up right now 2 ARM based and 2 Saturn. I heard at least one of them go off at about 3 days and another one the next day but I want to leave them until after the new year.

Which fits with the above for the ARM systems, and also the previously-discussed 262144-second interval for non-ARM RPL systems.

Also for what it's worth:

I put together a Saturn code object to return the value of TIMER2 as a test, and ran it on a couple different systems in different scenarios.

On a 48gx:
- With the running clock turned off, pressing the key to get TIMER2 returns a value just a few ticks shy of 1-hour. That seems to coincide with the comments from comp.sys.hp48 made by Dan Kirkland that pressing a key would set TIMER2 to a 1-hour value.
- With the running clock turned on, the reported TIMER2 value was always just shy of 1 second (8192 ticks). So pressing a key also resets that timer value, but obviously at the lower value. This wasn't a surprise, but it was nice to confirm expectations.

On a 50g:
- With the running clock turned on, the behavior was the same as the 48gx.
- With the running clock turned off, the returned TIMER2 value was always just shy of 72 hours. This was much higher than I expected, but I see no inherent problems with that value.

All of this did cause me to doubt the concept of the "auto-off" timeout being serviced by TIMER2, though. If it was, there should never be a value greater than the remaining time before shutoff in TIMER2. Also, the above values weren't impacted at all when I changed the TOFF value. That implies that the auto-off timeout is serviced by some other means (TIMER1? Display refresh? Something else?).