Well, I'm still unsure of the power fluctuations as a cause, mainly because I haven't been able to correlate to external sources of such fluctuations.
What I do see, on occasion, is nevertheless strange: here's an example:
Code: Select all
: : : :
M: 2023-02-03 14:13:14.088 DMR Slot 1, received network voice header from N0VZC to TG 31990
E: 2023-02-03 14:13:14.464 DMR Slot 1, overflow in the DMR slot RF queue
: : : :
E: 2023-02-03 14:13:14.464 DMR Slot 1, overflow in the DMR slot RF queue
M: 2023-02-03 14:13:14.464 DMR Slot 1, received network end of voice transmission from N0VZC to TG 31990, 8.5 seconds, 0% packet loss, BER: 0.0%
M: 2023-02-03 14:13:19.114 DMR Slot 1, received network voice header from N0VZC to TG 31990
M: 2023-02-03 14:14:03.178 DMR Slot 1, received network end of voice transmission from N0VZC to TG 31990, 44.3 seconds, 0% packet loss, BER: 0.0%
M: 2023-02-03 14:14:08.018 DMR Slot 1, received network voice header from N0VZC to TG 31990
M: 2023-02-03 14:14:35.373 DMR Slot 1, received network end of voice transmission from N0VZC to TG 31990, 27.7 seconds, 0% packet loss, BER: 0.0%
M: 2023-02-03 14:14:46.295 DMR Slot 1, received network voice header from N0VZC to TG 31990
M: 2023-02-03 14:14:47.609 DMR Slot 1, received network end of voice transmission from N0VZC to TG 31990, 1.6 seconds, 0% packet loss, BER: 0.0%
M: 2023-02-03 14:14:58.193 DMR Slot 1, received network voice header from N0VZC to TG 31990
M: 2023-02-03 14:15:05.427 DMR Slot 1, received network end of voice transmission from N0VZC to TG 31990, 7.5 seconds, 0% packet loss, BER: 0.0%
M: 2023-02-03 14:15:10.229 DMR Slot 1, received network voice header from N0VZC to TG 31990
M: 2023-02-03 14:15:10.707 DMR Talker Alias (Data Format 3, Received 3/10 char): 'N0V'
M: 2023-02-03 14:15:11.391 DMR Talker Alias (Data Format 3, Received 6/10 char): 'N0VZC '
M: 2023-02-03 14:15:12.127 DMR Talker Alias (Data Format 3, Received 10/10 char): 'N0VZC Mike'
M: 2023-02-03 14:15:24.906 DMR Slot 1, received network end of voice transmission from N0VZC to TG 31990, 14.9 seconds, 0% packet loss, BER: 0.0%
M: 2023-02-03 14:15:28.908 DMR Slot 1, received network voice header from N0VZC to TG 31990
M: 2023-02-03 14:16:09.139 DMR Slot 1, received network end of voice transmission from N0VZC to TG 31990, 40.5 seconds, 0% packet loss, BER: 0.0%
M: 2023-02-03 14:16:11.754 DMR Slot 1, received network voice header from N0VZC to TG 31990
M: 2023-02-03 14:16:51.206 DMR Slot 1, received network end of voice transmission from N0VZC to TG 31990, 39.7 seconds, 0% packet loss, BER: 0.0%
M: 2023-02-03 14:16:58.261 DMR Slot 1, received network voice header from N0VZC to TG 31990
M: 2023-02-03 14:17:29.096 DMR Slot 1, received network end of voice transmission from N0VZC to TG 31990, 31.4 seconds, 5% packet loss, BER: 0.0%
M: 2023-02-03 14:17:45.649 DMR Slot 1, received network voice header from N0VZC to TG 31990
E: 2023-02-03 14:18:27.761 DMR Slot 1, overflow in the DMR slot RF queue
: : : :
E: 2023-02-03 14:18:27.761 DMR Slot 1, overflow in the DMR slot RF queue
E: 2023-02-03 14:18:27.762 DMR Slot 1, overflow in the DMR slot RF queue
: : : :
E: 2023-02-03 14:18:27.762 DMR Slot 1, overflow in the DMR slot RF queue
E: 2023-02-03 14:18:27.762 DMR Slot 1, overflow in the DMR slot RF queue
M: 2023-02-03 14:18:27.762 DMR Slot 1, received network end of voice transmission from N0VZC to TG 31990, 51.7 seconds, 0% packet loss, BER: 0.0%
M: 2023-02-03 14:18:31.985 DMR Slot 1, received network voice header from N0VZC to TG 31990
: : : :
A series of transmissions (QSO's), except:
1) for those QSO's that log an overflow, the timings (length of the QSO) don't add up, start-to-end. The rest do.
2) not all QSO's log Alias Talker info, even though they're all from the same ID. (Presumably they are all from the same radio).
What it looks like is that the Alias Talker data is either 1) being logged as expected, or 2) being dropped all together, or 3) getting garbled and logged as overflows. Perhaps the route each QSO takes through the network is effecting the outcomes here. The intermittent overflows/talker data and possible routing variations: are they related?
Any thoughts, gentlemen?