Public · Operating profile
Flex Log
When the radio is actually in use, so two operators on opposite
sides of the clock can share it without walking on each other. Transmit sessions only
— times, bands and modes. Nothing about content.
Checking…
Reading the latest push from the site.
When the radio is used
busiest hours (60%+ of the peak)
some activity
nothing logged
hover any bar for the exact minutes
Recent sessions
| Started (local) |
On air |
Keyed |
Keys |
Band | Mode | Frequency | From |
What the columns mean
- On air
- Wall clock from the first key-down of the session to the last — the gaps
between overs included. This is “the radio was in use for this long”.
- Keyed
- Only the part of that where the transmitter was actually up. Always less than
on air, and much less in CW. The difference is listening time.
- Keys
- How many separate bursts of transmit were seen. Not a count of
Morse characters: the radio’s state is sampled four times a second, so anything
faster than a quarter of a second merges into one burst. At 38 WPM a dit is
about 30 ms, so a “key” is roughly a word or a group of them, not a
dit. Treat it as texture — a high count means break-in CW, a count of 1 means a
single unbroken transmission such as SSB or a tune-up.
Everything comes from the radio’s own transmit interlock, pushed over the Flex
API to the Pi at OTAMA — nothing is inferred or estimated. A session closes
after thirty seconds of silence, which is why a break-in ragchew is one row and not
hundreds.
← Back to Stats