50g Random Turn ON

[DavidM]

(12-14-2016 11:03 AM)Gerald H Wrote:  Turned on the 50g turned off in post #25.

NOTHING on the stack.

LASTARG recalled the timestring "SUN 11.12.16 09:32:31"

So if I'm understanding things correctly:

You powered down this 50g on the morning of 2016-12-07 and checked it on the morning of 2016-12-14.

Your STARTOFF should have left a string on the stack if it had run, but nothing was there. Correct? If so, either STARTOFF never ran, or something cleared what it left (or pushed a virtual stack entry and restored it, or invoked a system error, etc.).

LASTARG reports a string in the format you expected, which appears to indicate that something may have happened with STARTOFF on 2016-12-11 at 09:32:31. Kudos for checking LASTARG! I hadn't thought to do that.

Observation: <2016-12-11 09:32:31> - 2^31 ticks is approximately <2016-12-08 08:43:27>, which is about 24 hours later than would normally have been expected for the 262144-second TIMER2 reset (if I've understood your situation correctly). At a minimum, this tells me that I need to let more time pass before checking my 49g+/50g test units the next time.

Thanks for posting your results!

Also, FWIW regarding warmstarts:

WSLOG doesn't show all warmstarts. For example, manual warmstarts activated by ON-C don't create entries. There may also be other types that are excluded as well.

The usual question that comes up after mentioning WSLOG is "what are the codes at the beginning of the entries for?" This is the list of possibilities as found in the 50g Advanced Users Guide:

Code:

0: The warmstart log was cleared.
1: The interrupt system detected a very low battery condition at the battery
contacts (not the same as a low system voltage), and put the calculator in “Deep
Sleep mode” (with the system clock running). When ON is pressed after the
battery voltage is restored, the system warmstarts and puts a 1 in the log.
2: Hardware failed during transmission (timeout).
3: Run through address 0.
4: System time is corrupt
5: A Deep Sleep wakeup (for example, ON, Alarm).
6: Not used
7: A 5-nibble word (CMOS test word) in RAM was corrupt. (This word is checked
on every interrupt, but it is used only as an indicator of potentially corrupt RAM.)
8: Not used
9: The alarm list is corrupt.
A: System RPL jump to #0.
B: The card module was removed (or card bounce).
C: Hardware reset occurred (for example, an electrostatic discharge or user reset)
D: An expected System (RPL) error handler was not found in runstream.

I've seen references to codes E & F as well, though I've not seen any "official" documentation for what they mean. One post on comp.sys.hp48 lists them as:

E: Corrupt configuration table (bad checksum for table data)
F: System RAM card pulled