Added detection of timed out DMR calls in getHeardList() #118
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
as seen in Issue #117 "TX Duration continues to increment even though DMR TX has stopped." the dashboard isn't able to recognize timed out DMR calls. So the TX timer in the dashboard is counting tx time to infinity.
My change adds detection of those timed out DMR calls, because they are creating a line like this in the logfile:
M: 2020-09-25 17:00:33.659 DMR Slot 2, network watchdog has expired
Now those calls are showed in the dashboard with "TOut" in the "Dur" column when the log message appears.
73s de Thomas, DG0OFZ