No I have the latest firmware and I am having the same issues! It sounds terrible
BCD325P2/BCD996P2: Multiple Units trouble with Phase 2 Audio
- Thread starter policefreak
- Start date
- Status
No I have the latest firmware and I am having the same issues! It sounds terrible
A few clarifications:
1) It has nothing whatsoever to do with multipath interference from simulcast cells
2) It has nothing whatsoever to do with "interference" or "bleed over"
3) The updated 1.04.03 firmware made no difference whatsoever
4) This issue has only been reported with TDMA talkgroups; so far it does not appear to affect FDMA talkgroups
5) We are experiencing this issue with a 700 MHz system, whereby the scanner is attempting to tune to invalid frequencies in the 78x MHz range for TDMA voice frequencies. Those frequencies have nothing to do with 800 MHz rebanding.
6) The fact that it's trying to tune to frequencies that high in the 700 MHz band indicate that it's not calculating the correct TDMA voice frequencies with any degree of consistency.
There are at least two of us in this thread who have technical knowledge and firsthand experience with these ASTRO 25 TDMA systems far beyond that of the average hobbyist. I do not say that to come across as arrogant, it's simply a fact that is important to understand before taking stabs in the dark at offering up possible causes or solutions. Rest assured that if we say there is a bug with the scanner processing the TDMA band plan, then the problem is real.
I agree! I am having the same issues here! X2tdma sounds terrible I want to listen to Pierce County Washington Sheriff and it is phase 2 x2tdma and it is useless!
ButchGone
Member
I see in the video it's in Auto decode mode and the values wildly fluctuate. What happens if you put the unit into Manual decode mode and play with the thresholds, starting around 7.or 8?
BG..
BG..
Adjusting the P25 threshold numbers does not seem to have any affect on the issue. in fact adjusting threshold seems to degrade the phase 2 audio that does pass and make it sound garbled. Trust me I've tried.
While we can appreciate your frustration, your issue isn't the same as being discussed in this thread. It appears you have a decode/signal level issue as evidenced by the control channel disappearing numerous times in your video.
Could the cause be a co-located cell phone? From what I saw on the Youtube video isn't that or close to a cell phone frequency it is stopping on?
There are a few things going on in Verhoffj1's videos. I've actually been in touch with him and there seems to be some reception issue with the P25 site named "Orting" likely not related to a problem with the scannersince this is the only site that behaves this way. However because the control channel goes in and out, you'll see a poor response time decoding the phase 2 audio. You'll hear the pops at the beginning of transmissions along with trouble tuning to the right frequency. If you look closely at the second video, right around the 2 minute mark you'll notice the control channel come back on line and Immediately a transmission comes across. But the scanner seems to skip it a couple times and it looks like one of those odd frequencies shows up at the bottom of the screen, a product of poor response time. The poor audio quality and high error rates could be bad reception, not related to a problem with the scanner. But we have seen audio quality degrade and error rates go higher on Phase 2 audio when response times are made slower by monitoring 2 p25 systems together. We found that to be true in his area by monitoring 2 phase 2 P25 sites simultaneously (ones that each had good reception). In that case (and my unit does the same thing), it doesn't jump to odd frequencies as much. Instead, a talkgroup will come up on the correct frequency, but you'll hear dead air where audio should be passing and you'll get error rates of 70+. There's a chance that could be happening here.
Well, if that's the cause someone needs to contact the FCC as the radio would be in violation of the ECPA of 1986. :wink:
I just checked the Table of Allocations for the frequency 866.3625 MHz. In the US non-fed government it is allocated for FCC Part 22, Public Mobile and FCC Part 90 Private Land Mobile. So I was wrong on it looking like a cell phone frequency.
I also checked the FCC database and there and there are no assignments on 866.3625 in NJ. DE and PA had assignments but all were expired.
I couldn't find the IF frequency for the scanner. I was trying to look and see if this problem could be an image
problem ((2*IF)+- victim frequency).
by this I mean it could well be a bug with the scanner when you are scanning in frequency range and then you add another frequency range to scan.something like the PLL not locking up correctly.
The lack of acknowledgement from Uniden that an issue exists is just ridiculous.
It isn't like it's difficult to reproduce, heck they can even do it from their office.
And it's not like we are doing anything wrong, we scan JUST a P2 system and it works, we scan the same P2 system and ANYTHING else and it acts up.
Not looking for an immediate fix, just a "We can reproduce the issue and are investigating".
It isn't like it's difficult to reproduce, heck they can even do it from their office.
And it's not like we are doing anything wrong, we scan JUST a P2 system and it works, we scan the same P2 system and ANYTHING else and it acts up.
Not looking for an immediate fix, just a "We can reproduce the issue and are investigating".
troymail
Silent Key
I suspect the first acknowledgment you'll see is a new firmware release....
And I suspected this would have been caught by someone other than consumers.:wink:
That frequency is a previous NPSPAC frequency - the band that moved to 851-854 MHz due to rebanding. If a TRS is sending a scanner there, I would check the trunking tables the system is broadcasting.
Sigh...wrong answer.
As has been stated (numerous times),the radios work fine scanning only a P2 system, as soon as you scan that same exact system and ANYTHING else it acts up. And this is without changing ANYTHING else, just scanning something else with the P2 system.
You stop scanning that "anything else" and it magically starts working again.
Maybe the scanner is logging into CSS and changing the bandplan on us...hmm...
Here is another thought. Do you have another scanner located in the same room? Are their antennas close? I have seen the interaction between scanners here at my home. The scanners were a BC786D and a BCD996T. When the BC786D stop on a frequency and the 996T would stop on a transmission at the same time I would receive intermod on the 996T.
I haven't done any tests with my 2 BCD536HPs but I think that I am seeing the same problem on them.
I haven't done any tests with my 2 BCD536HPs but I think that I am seeing the same problem on them.
It would be awesome if it was that simple, but it isn't.
Everyone can rest assured that is ISN'T caused by another radio, incorrect bandplan, weak signal, simulcast distortion or ANY operator error.
As had been stated numerous times...scan a P2 system by itself=no problems, scan that exact same system and something else=problems.
I've personally seen this happen on 4 systems located almost 300 miles apart.
We are studying.
- Status
