You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
26 lines
1.3 KiB
Markdown
26 lines
1.3 KiB
Markdown
2 years ago
|
# Log4OM Web Status
|
||
|
|
||
|
This python program will take UDP messages blasted at it from Log4OM and will write it to a HTML file. It will
|
||
|
continually update this file as messages come in. It requires you to let Log4OM automatically send status packets.
|
||
|
|
||
|
### Usage
|
||
|
|
||
|
Place the script on a system that can hear UDP from Log4OM and has a way of putting the resulting HTML file on a webserver
|
||
|
as fast as possible.
|
||
|
|
||
|
### Basic Operation
|
||
|
|
||
|
Log4OM has a feature that has it send out UDP messages automatically as long as specific conditions are met. This python
|
||
|
script/program will take in the messages sent at it's IP and parse a few things out of the XML. It writes this to an
|
||
|
HTML file every time a message comes in; so the HTML generated is set to auto-reload every 5 seconds. It currently displays
|
||
|
the following in a very basic way:
|
||
|
|
||
|
- Your current VFO frequency and opearating mode.
|
||
|
- Your TX offset/split if it exists
|
||
|
|
||
|
If no data is received from Log4OM, because you turned your rig off or shutdown Log4OM; it will indicate your radio is
|
||
|
off and wait for data to come back. Support is planned to show if rig is in transmit.
|
||
|
|
||
|
The "Radio Off" message happens after 15 seconds of no data. This is done by checking the elapsed time since the timestamo
|
||
|
was last updated; which happens every time a message comes in.
|