|
|
|
@ -1,6 +1,6 @@
|
|
|
|
|
---
|
|
|
|
|
layout: page2
|
|
|
|
|
title: Log4OM UDP Display
|
|
|
|
|
title: Log4OM Web Status
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
[Git Repository](https://git.pickmy.org/nq4t/Log4OM-WebStatus)
|
|
|
|
@ -35,9 +35,8 @@ My version has CSS applied to match my website. The default version does not.
|
|
|
|
|
Log4OM sends packets to my server's IP. Python picks these up, parses the required information out, and stuffs them in to
|
|
|
|
|
some HTML it saves directly to the server. This file is set to auto-refresh every 5 seconds.
|
|
|
|
|
|
|
|
|
|
A monitoring thread checks every few seconds to see when the last packet was received. If it doesn't see any in about 15
|
|
|
|
|
seconds; it changes the status to indicate this. In this state, it only checks for updates every 30 seconds.
|
|
|
|
|
If the UDP monitor doesn't get any packets within 6 seconds, it executes a routine to see what's up. This function merely sends the
|
|
|
|
|
"Alive" command over the UDP Remote Port. Any response will indicate the radio is off; but a lack of response within 2 seconds assumes
|
|
|
|
|
that Log4OM is not running on the shack PC.
|
|
|
|
|
|
|
|
|
|
The thread listening for UDP always runs. When UDP starts streaming in, it immedately executes.
|
|
|
|
|
|
|
|
|
|
It can be considered real-time to within 30 seconds or so.
|
|
|
|
|
When the radio is off or Log4OM is not loaded; the code only sends the remote request every 60 seconds.
|
|
|
|
|