Repository navigation
Replies: 1 comment
|
Merged in PR #409 and will be available on next release (v1.9.20) which will come very soon, please help to test it and submit new issue if found. Thank you very much for your suggestion! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
At present, when Mercury decodes a message that is not directed at the user, we get a printout such as:
I think it would be great to show more of the signal that is decoded, such as the callsign of the person sending it and the callsign of the intended recipient. Depending on a user-defined level of verbosity it could even dump the raw decoded bytes into the log.
In this way, one can monitor the traffic on a given channel and see who is connecting to whom, for example to check whether a given Winlink RMS is busy or whether the channel is being occupied by other users.
All reactions