Page 1 of 1

System Saber III

Posted: Fri May 26, 2006 9:20 am
by Radio Intelligence Agency
I just noticed that my SSIII wouldn´t send ack when checked by the command console on the repeater channel which has a hang time. On a simplex frq it goes smooth. How come?
Second: all my SSIII chare the same problem unmuting in analog. They need a sec or two every time before they will finally unmute.
Third: when they scan they go crazy giving me white noise only how come?
Fourth: one of them seems to give me hell when disabled and enabled. Could there be a thin red line I´ve crossed somewhere during programing?

Hope there´s a System guro out there, thanks.

Posted: Fri May 26, 2006 5:56 pm
by AEC
What is/are the exact commands you are sending through the console?

QC-II, MDC, Sel-Call.....??

How are your mute/unmute timers set...value?

Do you use status messages or remote monitor on your system?

Secure?

Do you or have you changed the MDC variable unit ID?

I need a little more in-depth information in order to help.

I'll be happy to work with you in real time if you have Yahoo messenger, my IM ID is: AEC9823, send a request and I'll authorize you and we can work the problem out as you are working onn it.

I'll have Yahoo active and hope to see your request.

Posted: Sat May 27, 2006 6:55 am
by Radio Intelligence Agency
Thank you.

I do use mdc and they are all secure equipped :)

The radio has the mdc id yes. Unmute/mute is set to "or". DOS is enabled.

Posted: Sat May 27, 2006 8:07 am
by Rick Rock
They take longer to unmute on clear traffic because they're checking for secure key first. We ran into this same problem @ Dayton hamfest this year.

Posted: Sat May 27, 2006 8:13 am
by Radio Intelligence Agency
Okay, that sounds interesting. But the saber dosn´t seem to have this problem switching from clear to secure. I wonder if there´s something more to it? I´ve experienced the problem both with single and multikey modules.But only with the system sabers.

Posted: Sat May 27, 2006 8:17 am
by Rick Rock
Right- it checks for the secure key first, so it unmutes quickly for secure, but if it doen't receive the secure key, then it looks for coded squelch (or carrier, as the case may be) before it unmutes. It's a quirk with the sabers.

Posted: Sat May 27, 2006 8:31 am
by Radio Intelligence Agency
I would very much like to hear if anyone ever found a way around this irritating problem.
Funny how the M radioes have their differences but I havn´t found the final package yet :D

By the way where did a "WHCA" radio come from anyway?

Posted: Sat May 27, 2006 8:34 am
by FireCpt809
WHCA White House Communications Agency

Posted: Sat May 27, 2006 8:38 am
by Radio Intelligence Agency
Gee, thanks.
And that includes Secret Service agents as well or?
This one had plain des multikey in it on arrival.

Posted: Mon May 29, 2006 12:29 am
by AEC
You might try setting your unmute to: 'AND', this does have an effect on the decoding process as different signalling requires different unmuting times to be decoded properly, like status messages and QC-II and the like....as well as MDC.

Posted: Mon May 29, 2006 11:27 am
by Radio Intelligence Agency
Okay, I´ll try that.

By the way I´ve added you on yahoo but you´re never online. :-?

Posted: Tue May 30, 2006 9:53 pm
by AEC
Radio Intelligence Agency wrote:Okay, I´ll try that.

By the way I´ve added you on yahoo but you´re never online. :-?


First contact a success!

We're chattin' 8)