You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi everyone.
I have installed the FM branch on our repeater for a few days, and I must say that it works quite well.
However, I want to point out that after this new installation the issue of the CW identifier becomes inaccurate.
[CW Id]
Enable = 1
Time = 10
#Callsign =
I use this configuration in MMDVM.ini and with previous releases the identifier timing had always been correct.
Now it happens that it is emitted at often different intervals, 10 minutes, then 4 minutes, then 12 minutes, then 8 minutes, without a logic criterion, even if the repeater has not had any traffic.
I understand that this is a small anomaly, compared to the great work you are doing for us, but I thought to report it just in case.
'73 de Adam, IK4NZD
This is a part of my log
M: 2020-05-03 20:18:19.226 Debug: Message created with length 73
M: 2020-05-03 20:29:05.957 Debug: Message created with length 73
M: 2020-05-03 20:39:06.335 Debug: Message created with length 73
M: 2020-05-03 20:49:40.466 Debug: Message created with length 73
M: 2020-05-03 20:54:06.316 Debug: Message created with length 73
M: 2020-05-03 20:58:25.105 Debug: Message created with length 73
M: 2020-05-03 21:01:39.261 Debug: Message created with length 73
The text was updated successfully, but these errors were encountered:
Hi everyone.
I have installed the FM branch on our repeater for a few days, and I must say that it works quite well.
However, I want to point out that after this new installation the issue of the CW identifier becomes inaccurate.
[CW Id]
Enable = 1
Time = 10
#Callsign =
I use this configuration in MMDVM.ini and with previous releases the identifier timing had always been correct.
Now it happens that it is emitted at often different intervals, 10 minutes, then 4 minutes, then 12 minutes, then 8 minutes, without a logic criterion, even if the repeater has not had any traffic.
I understand that this is a small anomaly, compared to the great work you are doing for us, but I thought to report it just in case.
'73 de Adam, IK4NZD
This is a part of my log
M: 2020-05-03 20:18:19.226 Debug: Message created with length 73
M: 2020-05-03 20:29:05.957 Debug: Message created with length 73
M: 2020-05-03 20:39:06.335 Debug: Message created with length 73
M: 2020-05-03 20:49:40.466 Debug: Message created with length 73
M: 2020-05-03 20:54:06.316 Debug: Message created with length 73
M: 2020-05-03 20:58:25.105 Debug: Message created with length 73
M: 2020-05-03 21:01:39.261 Debug: Message created with length 73
The text was updated successfully, but these errors were encountered: