Strange Trunked System Behavior
Posted: Mon Aug 14, 2006 5:14 am
Repost from rr.com:
This is a federal system (Sheppard AFB to be exact). I am using a BCD396T and a Pro-96 and everything goes okay for the most part, but sometimes it seems as though the system dies. The signal strength indicator on the 396 is still full bars, but only carrier is detected. Basically there is no data on the control channel, just an open carrier. Scanning through the other control channels gives a very strange data sound that I've never heard before. It is constant just like a control channel would do, but a very distinct sound. It almost sounds like an old Type I system, but as I said, it's on every channel that the system uses (except the CC that was in use before this "problem" takes place).
UniTrunker just shows "No Signal" while this is going on even while parked on one of the mysterious data channels..
This has happened a few times in the past couple of days.
Is this the system going into "FailSoft"? I've never seen or heard a system go into "FailSoft" before, so I'm leaning towards that.
This is a federal system (Sheppard AFB to be exact). I am using a BCD396T and a Pro-96 and everything goes okay for the most part, but sometimes it seems as though the system dies. The signal strength indicator on the 396 is still full bars, but only carrier is detected. Basically there is no data on the control channel, just an open carrier. Scanning through the other control channels gives a very strange data sound that I've never heard before. It is constant just like a control channel would do, but a very distinct sound. It almost sounds like an old Type I system, but as I said, it's on every channel that the system uses (except the CC that was in use before this "problem" takes place).
UniTrunker just shows "No Signal" while this is going on even while parked on one of the mysterious data channels..
This has happened a few times in the past couple of days.
Is this the system going into "FailSoft"? I've never seen or heard a system go into "FailSoft" before, so I'm leaning towards that.