There have been many problems reported where a system restart, with or without a database reset, has "corrected" the problem; as in the problem does not reappear. This does not capture information for true problem correction.
Premise: One: There is non-volatile memory available on the hardware, such as where the database is stored and this memory may be selectively reset.
Two: A button combination or on the 6300 such as "power button double click" that may be recognized by a high priority error thread.
Idea: The internal software may self detect a major failure OR be externally signaled by a method to be determined (front or rear panel) that will record software status and trace information as well as database status into non-volatile memory.
AND: A method to make a standardized copy of the latest information on a file (SSDR or specialized GUI using the API) that can be recorded and/or forward the contents to a FRS support site.
AND: A method within FRS to analyze the captured trace information.
I suspect you have diagnostic trace information inside your software that would be useful for both in-house or in-customer detected errors.
Stan Williams - VA7NF
Be the first to post a reply!