HP1 squelch tail on Moto Trunking systems

[rfradioconsult]

Looking back on RR this was discussed before but no resolution was mentioned. When monitoring our OKWIN system my HP1 will most of the time have a very annoying squelch tail. This occurs when the channel drops and the radio reverts to the control channel. Setting the squelch level has no effect nor does turning on the attenuator. Listening alongside my 106 the problem is on my HP1.

 

[Jay911]

You can try changing the "End Code" option, but I've had 3 HP1s, and in my experience, the 800 MHz range started behaving this way on trunked systems on two of them, after about a year's use. Only on analog systems/talkgroups, not on digital transmissions. I just retasked those radios to roles that don't involve 800 MHz.

I don't know how successful you'd be in sending it in for repair. When my first HP1's stock antenna failed, it was sent for repair (before I figured out that it was the antenna at fault - all I knew was the radio had gone 'deaf') and the diagnosis on the ticket was "ATTEN TURNED ON". That implies to me that the diagnostic process is not always thorough.

 

[W8RMH]

I get this on my HP-2 every once in a while on Motorola Type II systems so it is not that annoying, and I believe it is end code related, but I don't recall an End Code setting on the HPs.

 

[rfradioconsult]

I turned the power save function off and hear a definite improvement.

 

[Voyager]

I've never liked the power save functions - on any scanner or radio.

 

[Otto]

I am experincing the same issue with my two week old HP2. Turning off the power save feature did not resolve the issue. The squelch trail was not audible when I first started using the scanner, and it's only happening randomly on various voice channels.

Like th OP, it also only happens on Motorola type II systems.
I am anxious to see if there is a fix for this , otherwise I think I will probably return the scanner for a refund.

 

[Otto]

Ok, so I got the squelch trail to go away, for now.

I reloaded an updated database via sentinel, and as of now the squelch trail is no longer present.

For what it's worth (not a Uniden slam, sort of) I posted this same question on the Homepatrol site and emailed Uniden about the problem. uniden never responded to the emails. , and just one short question from the Homepatrol forum admin, and no response after that. Kind of disappointing customer service on a $500 scanner.

 

[UPMan]

Since your answer was provided by the community, I felt no need to add to their solution. If I had to validate every correct post, I wouldn't have time to handle other posts (or the rest of my job).

By the way, it is "squelch tail", not "trail". (I followed behind editing all your posts on HomePatrol.com changing that .)

 

[jackj]

Once again, Uniden's customers are supplying free quality control testing to Uniden.

 

[UPMan]

I have always relied on customer reports to roll updates into current products and improvements into new products. Are you suggesting that I should be ignoring them? The products are complex, the usage scenarios are broad, and we can't possibly test every case before release. So, yes, we do rely on and listen to customers so that we can respond to things when they come up.

 

[jackj]

Good recovery attempt UPMan. Are you saying that your product testers don't have time to turn on the scanner or attempt to use it as it was designed to be used? I bought a 996T new several years ago that didn't work on digital systems. It is working now after either 3 or 4 firmware updates obviously it was never tested or a decision was made to sell a defective product. I won't buy another Uniden, screw me once, shame on you. Screw me twice, shame on me.

 

[phask]

Another poster that has no idea of production, testing and variables.

996T - that was several, several years ago.

Good recovery attempt UPMan. Are you saying that your product testers don't have time to turn on the scanner or attempt to use it as it was designed to be used? I bought a 996T new several years ago that didn't work on digital systems. It is working now after either 3 or 4 firmware updates obviously it was never tested or a decision was made to sell a defective product. I won't buy another Uniden, screw me once, shame on you. Screw me twice, shame on me.

 

[phask]

Just think, if you had kept the database even remotely up to date it would have been a non-issue.

Ok, so I got the squelch trail to go away, for now.

I reloaded an updated database via sentinel, and as of now the squelch trail is no longer present.

For what it's worth (not a Uniden slam, sort of) I posted this same question on the Homepatrol site and emailed Uniden about the problem. uniden never responded to the emails. , and just one short question from the Homepatrol forum admin, and no response after that. Kind of disappointing customer service on a $500 scanner.

 

[Otto]

Just think, if you had kept the database even remotely up to date it would have been a non-issue.

Wow. Ok. I updated the database when I first bought it like the setup screen recommend. Then barely two weeks later the problem appeared. How often do I need to update the database? Daily? Weekly? I mean really? I figured that the database was pretty remotely up to date.

 

[Otto]

Since your answer was provided by the community, I felt no need to add to their solution.

In fact, no one from the community answered the question. I posted what I found to the community, just like I did here, since apparently others have experienced the same issue.

 

[Voyager]

How often do I need to update the database? Daily? Weekly? I mean really? I figured that the database was pretty remotely up to date.

It is, but there are two caveats:

1. Update frequency depends on how often your system changes. Some change quite often. Others haven't changed in years.

2. The RR database is updated by users, and relies on admins to process the submissions. These both are usually not immediate upon a system changing. There will be some lag until the data is known, submitted, then approved.

There are also times when the data isn't approved for one reason or another.

 

[Otto]

It is, but there are two caveats:

1. Update frequency depends on how often your system changes. Some change quite often. Others haven't changed in years.

2. The RR database is updated by users, and relies on admins to process the submissions. These both are usually not immediate upon a system changing. There will be some lag until the data is known, submitted, then approved.

There are also times when the data isn't approved for one reason or another.

Well, I know all this. I was being a snark at the person for admonishing me for not doing enough updates to my three week old scanner.