Terrible P25 performance on certain systems after FW upgrade.

[SnakeEater9920]

I just updated last night, and I'm getting absolutely terrible P25 performance after the 1.11.31 update for the 436HP. I'm now getting error rates going above 100 at times. Never changed any settings, always keep everything on Auto with a setting of 8 and It was fine. Now, I can barely hear a thing. I'm mostly monitoring the Somerset County P25 system in NJ. I'm very close to the system, get five bars and always hear it perfectly.

Anybody have the same issues? And if there is anyway to fix this, the help would be appreciated. P25 shows up, and right in the middle of the audio it cuts out and goes back to DAT. No close call on, no priority or anything.

Oddly enough, the NJICS system as usual gives me mostly 0 error even with the new update applied. Sounds beautiful. On the Somerset County system with the threshold on Auto, It's jumping from 7 to 8 to 13 to 12 back to 7 and you get the point. NJICS is staying on 7 or 8.

Realized I might have posted this in the wrong section. Sorry!

 

[garys]

If you set it to "Auto", I'm pretty sure that the level setting doesn't do anything. Set it to "Manual" and 8 and see if that helps. The vast majority of systems I have programmed into my x36Hp scanners work better with manual settings.

 

[jonwienke]

Level setting is ignored in Auto mode. Change to manual and then set Level to the value that gave lowest decode error rate when in Auto mode. (7-8 for Somerset County system)

And pics on decode error rate>100 or it didn't happen.

 

[SnakeEater9920]

Level setting is ignored in Auto mode. Change to manual and then set Level to the value that gave lowest decode error rate when in Auto mode. (7-8 for Somerset County system)

And pics on decode error rate>100 or it didn't happen.

Yeah, I know how hard that would be to believe, but it happened. And if the radio is still acting up today, I'll see if I can record it if it gets that high again. I also never saw it go above 100 either, so I was just as surprised as you.

 

[Ensnared]

Auto?

I am terribly confused here. Are you talking about the "digital threshold mode" or "digital threshold level." My threshold mold is set on "auto" while my threshold remains on "8."

 

[jonwienke]

When "Digital Threshold Mode" is set to Auto, the "Digital Threshold Level" setting is ignored. The scanner dynamically adjusts Level as it sees fit.

When "Digital Threshold Mode" is set to Manual, the "Digital Threshold Level" setting is used and not changed by the scanner.

Decode error is the percentage of the decoded data with checksum errors. It should never go above 100% for obvious reasons.

 

[Ensnared]

Auto-8

When "Digital Threshold Mode" is set to Auto, the "Digital Threshold Level" setting is ignored. The scanner dynamically adjusts Level as it sees fit.

When "Digital Threshold Mode" is set to Manual, the "Digital Threshold Level" setting is used and not changed by the scanner.

Decode error is the percentage of the decoded data with checksum errors. It should never go above 100% for obvious reasons.

I have never ever set this threshold. However, when I looked at my local P25 trunking system and several others, I observed the following: auto for threshold mode and 8 for threshold level. Does this setting occur when you load the Favorites from the Master list?

On very rare occasions, rarely, portable radios will start to skip out. Would adjusting this to manual and then 7 or 8 help matters? I know this is a very general question.

 

[jonwienke]

When Mode is set to Auto, the Level value is ignored. It's only used when you set Mode to Manual. It doesn't matter whether you're in the Main Database or a Favorite List.

Auto generally is best, unless you're having trouble with simulcast, and the radio can't figure out the best threshold value on its own.

 

[SnakeEater9920]

Okay, so It seems that there's some work being done on the system/towers. Other people have reported they were experiencing the same issue.

That might have been my problem. I'm currently receiving the system fine from where I am currently. I figured It might have been something to do with the FW update since I updated it two nights ago and then the problems started.

Thanks for the replies. Currently 0 error on Somerset County.