'996 stops on control channel

[W4KRR]

I programmed my '996 with the UASD software. I opened a file that came from my '396 in the UASD software for the '996, so basically I have a clone of my '396.

It works perfectly except for one thing: There's one Motorola trunked system that keeps stopping on the control channel. It's the Coral Springs, Fla. system. It acts as if the system were programmed as a conventional system.

I manually went in the 996 menu and deleted the site, created another site as a Motorola type II standard, and it fixed the problem, it trunked perfectly.

Now, the next morning, it's doing the same thing again. It's stopping on the control channel and passing the control channel audio. (It's the same control channel from last night). All my other systems are working fine. It must be a setting I'm overlooking, but I've never had this occur on my '396, '246, or any other scanner. I can't figure it out.

 

[RISC777]

Wild guess...Control Channel Only on/off?

 

[W4KRR]

Wild guess...Control Channel Only on/off?

Control Channel only is on. I have the four control channels programmed, it stops on the active one and stays there. System is programmed as Motorola type II Standard.

 

[DaveIN]

I see your in Broward County. What system are you trying to monitor? Maybe you can upload the UASD file for us to look at?

 

[SCPD]

What is the hold time on the system set at?

 

[GrayWolfSA58]

I programmed my '996 with the UASD software. I opened a file that came from my '396 in the UASD software for the '996, so basically I have a clone of my '396.

It works perfectly except for one thing: There's one Motorola trunked system that keeps stopping on the control channel. It's the Coral Springs, Fla. system. It acts as if the system were programmed as a conventional system.

I manually went in the 996 menu and deleted the site, created another site as a Motorola type II standard, and it fixed the problem, it trunked perfectly.

Now, the next morning, it's doing the same thing again. It's stopping on the control channel and passing the control channel audio. (It's the same control channel from last night). All my other systems are working fine. It must be a setting I'm overlooking, but I've never had this occur on my '396, '246, or any other scanner. I can't figure it out.

Now Why do you have to download the uasd software?? what does that do for you? I don't understand will I have to do this also? thanks for any help

 

[scanjunkie]

Now Why do you have to download the uasd software?? what does that do for you? I don't understand will I have to do this also? thanks for any help

The UASD software is FREE from Uniden and it is used to program the scanner. You don't have to use it, you can program it by hand and go completely insane if you would rather!!:lol:

 

[GrayWolfSA58]

so it's not software so the scanner can be used on the computer?how do you get the software from the computer to the scanner? thank-you

 

[Al42]

You don't "get the software from the computer to the scanner", you run the UASD on the computer, to enable you to program frequencies (and other things) into the scanner by computer.

 

[cristisphoto]

Try this:

FYI
Twak the bases ,steps, and offsets
see if that makes any difference..
Itactually helps especially when using UHF trunked and Digital UHF trunked....

 

[DaveIN]

I programmed my '996 with the UASD software. I opened a file that came from my '396 in the UASD software for the '996, so basically I have a clone of my '396.

It works perfectly except for one thing: There's one Motorola trunked system that keeps stopping on the control channel. It's the Coral Springs, Fla. system. It acts as if the system were programmed as a conventional system.

I manually went in the 996 menu and deleted the site, created another site as a Motorola type II standard, and it fixed the problem, it trunked perfectly.

Now, the next morning, it's doing the same thing again. It's stopping on the control channel and passing the control channel audio. (It's the same control channel from last night). All my other systems are working fine. It must be a setting I'm overlooking, but I've never had this occur on my '396, '246, or any other scanner. I can't figure it out.

Sorry, did not see the reference link until now http://radioreference.com/modules.php?name=TRSDB&sid=209. Nothing special it's an analog system. You did program it as a Type II 800, right? It sould be working ok. Can you upload your UASD file?

 

[W4KRR]

Sorry, did not see the reference link until now http://radioreference.com/modules.php?name=TRSDB&sid=209. Nothing special it's an analog system. You did program it as a Type II 800, right? It sould be working ok. Can you upload your UASD file?

I will have to wait until I get back home; I'm away out of state on vacation, and didn't bring the '996 !

Anyway, it's the Coral Springs, Florida, system in Broward County. Nothing unusual about it, it's Motorola type II standard. All my other scanners have no problems with it.

It seems to work fine for a couple of minutes, then it stops on the control channel and stays there. If I manually hold on a talkgroup, it works fine.

If the radio were defective, I would think all Moto systems would be affected. I think it may be some setting or something that's wrong. I'll have to wait until Friday to check it again.

 

[DaveIN]

Is a talkgroup displayed when it's stuck on the control channel? Do you have I-Call on?

I saw this on an Indiana SAFE-T tower (3600 baud mixed mode) and an I-Call individual radio ID was displayed. I locked out the ID and the 996 continued on to scan. I had seen this on the 396 also and it did the same thing.

 

[W4KRR]

Is a talkgroup displayed when it's stuck on the control channel? Do you have I-Call on?

I saw this on an Indiana SAFE-T tower (3600 baud mixed mode) and an I-Call individual radio ID was displayed. I locked out the ID and the 996 continued on to scan. I had seen this on the 396 also and it did the same thing.

When manually held on a talkgroup, it seems to work normally. I-Call is set to "on". If I lock out the control channel, the remaining frequencies behave as if it were programmed as a conventional system. If I unlock the control channel, and hit scan, it works normally for a few minutes, then it will again stop on the control channel and stay there until I do something.

 

[spooney]

My Fix For Same Problem

When scanner stops on control channel press E and you will see menu. Select EDIT SITE, then EDIT TGID, then you should see a bogus three digit ID (mine was 128) Press and hold .NO key until TGID disappears. Now press scan to resume normal scanning. Let me know if this works for You. E-mail me at spooney@sigecom.net

 

[W4KRR]

When scanner stops on control channel press E and you will see menu. Select EDIT SITE, then EDIT TGID, then you should see a bogus three digit ID (mine was 128) Press and hold .NO key until TGID disappears. Now press scan to resume normal scanning. Let me know if this works for You. E-mail me at spooney@sigecom.net

So you had the same problem? It will be late Friday before I can test this, as I am away on vacation and didn't bring the '996.

 

[spooney]

Ken, you should be smiling your on vacation. I hope I remembered all the steps because it doesn't work the same if you press HOLD and lock onto control channel. It has to be when it is in normal scan mode and it stops and every time you press scan it just keeps stopping on the control channel. Looks like something UNIDEN needs to investigate.
Greg

 

[spooney]

Forget my previous post. The problem keeps coming back. Just by accident I discovered the problem went away when I wasn't scanning a system I had programmed using Quick Key 0. I have since changed that system to a different Quick Key and the problem has stopped. I'm thinking something is wrong when 0 is used.

 

[W4KRR]

Forget my previous post. The problem keeps coming back. Just by accident I discovered the problem went away when I wasn't scanning a system I had programmed using Quick Key 0. I have since changed that system to a different Quick Key and the problem has stopped. I'm thinking something is wrong when 0 is used.

My system in question is using Quick Key 88. I have no systems that use Quick Key zero.

 

[clayman]

I've tried not using QK 0, and changing QK's when the problem occurs. What happens when I change the QK, the problem pops up on another sytem. So I change that QK, and it pops up on another system, and so on. It is doing it on LTR, Moto Type 2, and 700 Mhz P25 systems. It is usually only 1 system at a time, it may start in the morning when I first turn it on, or it may wait until the middle of the day to start acting up. As much as I hate to, I guess I should send it back and try another one.
Clayton