Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added detection of timed out DMR calls in getHeardList() #118

Merged
merged 1 commit into from
Oct 20, 2020

Conversation

thovoigt
Copy link
Contributor

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

@AndyTaylorTweet AndyTaylorTweet merged commit cf36796 into AndyTaylorTweet:master Oct 20, 2020
@AndyTaylorTweet
Copy link
Owner

Thank you for this 👍

@AndyTaylorTweet
Copy link
Owner

This impacted YSF connections, for some reason all FCS connections always show timed out in the log, so I revised this code a little (see here: 7a13634) please make sure this still works the way you intended it....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants