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
Hello everybody.
Our MMDVM FM/DMR/YSF repeater has the CW identification as its only beacon.
It has been connected to a YSF reflector for a few weeks and we realized that if the connection with the reflector fails, then the repeater starts transmitting a C4FM string every 12 minutes, until the connection to the reflector is restored.
(In reality, if the reflector remains off for several hours, then the repeater will not automatically reconnect, but a reboot will be required .....)
M: 2022-06-15 23:00:28.452 YSF, received network data from IR4UAV-RPT to DG-ID 0 at IR4UAV
M: 2022-06-15 23:00:28.914 YSF, received network end of transmission from IR4UAV-RPT to DG-ID 0, 0.6 seconds, 0% packet loss, BER: 0.0%
M: 2022-06-15 23:12:28.882 YSF, received network data from IR4UAV-RPT to DG-ID 0 at IR4UAV
M: 2022-06-15 23:12:29.344 YSF, received network end of transmission from IR4UAV-RPT to DG-ID 0, 0.6 seconds, 0% packet loss, BER: 0.0%
M: 2022-06-15 23:24:29.305 YSF, received network data from IR4UAV-RPT to DG-ID 0 at IR4UAV
M: 2022-06-15 23:24:29.767 YSF, received network end of transmission from IR4UAV-RPT to DG-ID 0, 0.6 seconds, 0% packet loss, BER: 0.0%
Is this functioning correct?
Is it possible to prevent this cyclic transmission from being issued?
In the various configuration files I have not found any parameter that identifies a possible C4FM identifier.
Thank you for any help.
'73 de Adam, IK4NZD
The text was updated successfully, but these errors were encountered:
Hello everybody.
Our MMDVM FM/DMR/YSF repeater has the CW identification as its only beacon.
It has been connected to a YSF reflector for a few weeks and we realized that if the connection with the reflector fails, then the repeater starts transmitting a C4FM string every 12 minutes, until the connection to the reflector is restored.
(In reality, if the reflector remains off for several hours, then the repeater will not automatically reconnect, but a reboot will be required .....)
M: 2022-06-15 23:00:28.452 YSF, received network data from IR4UAV-RPT to DG-ID 0 at IR4UAV
M: 2022-06-15 23:00:28.914 YSF, received network end of transmission from IR4UAV-RPT to DG-ID 0, 0.6 seconds, 0% packet loss, BER: 0.0%
M: 2022-06-15 23:12:28.882 YSF, received network data from IR4UAV-RPT to DG-ID 0 at IR4UAV
M: 2022-06-15 23:12:29.344 YSF, received network end of transmission from IR4UAV-RPT to DG-ID 0, 0.6 seconds, 0% packet loss, BER: 0.0%
M: 2022-06-15 23:24:29.305 YSF, received network data from IR4UAV-RPT to DG-ID 0 at IR4UAV
M: 2022-06-15 23:24:29.767 YSF, received network end of transmission from IR4UAV-RPT to DG-ID 0, 0.6 seconds, 0% packet loss, BER: 0.0%
Is this functioning correct?
Is it possible to prevent this cyclic transmission from being issued?
In the various configuration files I have not found any parameter that identifies a possible C4FM identifier.
Thank you for any help.
'73 de Adam, IK4NZD
The text was updated successfully, but these errors were encountered: