Weird issue with ASL3

1

The set up description:
Our Repeater is using ASL 3 and we had it split on a UHF repeater and a 2-meter remote in the same enclosure.
It had 2 seperate node numbers at first, one for the UHF side and one VHF side.
Since then we removed the main UHF node ID and made it a Hub because of a Port forwarding issue at a different location on a diffenrt IP address and Port.

Ok so the real problem:

During low or no activity times, the repeater wont key up at all like its off.
If you keep keying up on the input, about 20 times it will eventually start working.
If you go on Allmon monitor and re boot it, it starts working.

It is set up so.it re boots everyday at 5 am, but if there has been no activity after the re boot it wont key up.

The last software update was done Feb 11th.
All operations otherwise work fine, it just wont key up after low or no activity.

The VHF link for 2 Meters is linked all the time as well as a 200 Mhz Link always connected to UHF.

I have a person node as well and it never fails or stops working. The 220 Node is not failing either as a stand alone. It seems to benonly the node at the site on the UHF repeater thats failing.

Im at aloss whats goingbon why it just goes deaf and wont key up when its not used for a few hours…

Has anybody encoutered this.

Thanks
N7COX
STAR IDAHO

2

Is it a physical or software issue? By that I mean when the radio you are using to talk to the repeater transmits, does anything appear in any monitor software? e.g. In the Allmon3 Monitoring Software does the incoming signal show as ‘Transmit Local Source’. Or if you are using Supermon v7.4+ it will show as ‘COS-Detected’. Then if you go into the Asterisk CLI, do you see any ‘Hungup’ messages when the PTT is dropped.

3

Is sleep mode enabled? Your description matches going to “sleep”…
https://wiki.allstarlink.org/wiki/Sleep_Mode

It looks like the only way to enable it is via COP 51, and disable with COP 52. Maybe a startup macro or some other accidental change is issuing a COP command?

4

Piggybacking on to what G0JSV said about the problem being a physical issue, do you think it might be a ‘ground’ issue? Is the ground connection on whatever hardware that is hosting ASL3 (a Pi?), connected to the same ground as the repeater?
Just a thought.
-Shawn (N6REP)