On Thu, Jul 26, 2018 at 12:14 PM, Joel Force <email@example.com> wrote:
> When the software froze, could you access anything on the menus of the UI or
> activate the refresh button? Or was the UI totally locked up?
To build on Joel's questions:
Did the UI just stop doing what it's supposed to do but was otherwise
responsive to UI input?
Did it freeze hard and kill the UI (e.g. white window / greyed out
buttons/text, etc.) with Windows reporting that the program had
Worst-case, did it crash the OS and generate a blue screen of death (BSOD)?
If the application crashed "gently" you should be able to find a
record of it in Windows' Event Logs (probably under the Application
subitem). It might give you (and Dave) a clue as to the nature of the
The UI also has its own logging file... (See
C:\ProgramData\Reyware\Amr-100\logs for starters)
Generally, a "keepalive" or "watchdog" routine has to be built into a
program to enable something external to react to a crash of some sort.
Without that, you'd have to externally monitor the program's behavior
to determine if it's "normal."
A quick sniff with the Wireshark and Process Hacker programs shows
that the AmbOS UI software program polls the AMR-100 receiver at least
twice every minute (once for time at the top of each minute) and once
to retrieve RF Stats, etc., and then of course there's the periodic
poll of the baselist.txt file on the receiver that lists all the
contents of the AMR-100's audio files.
So, one thing you could search for is a program that can sniff network
traffic to a certain IP address and alert you if it doesn't see
traffic within a certain time window. (Sorry, but I don't have any
quick results from Google on such a program for Windows. Linux would
be a different story...)
If you're the programmer type, you could use a command-line packet
capture utility (like 'tshark' - a command-line interface that's part
of the Wireshark family) in a timed loop that gets reset each time a
new packet is received. A PowerShell script would do the trick of
launching commands and allowing emails to be sent easily from within
the script with no external mail programs required.
Some other things to check:
* Run a memory tester on the computer. Maybe you're hitting some bad
RAM and the program/OS are getting unstable?
* Bad caps on an older motherboard causing general flakiness on the computer?
* Network connections good and reliable?
* AMR-100 receiver having issues?
Just some ideas...