P25 decode issues in the upper part of the VHF band

[JoeBearcat]

We are investigating a hardware or firmware issue that affects P25 decode above 171.200 MHz. (the cutoff could be lower)

So far, this seems to affect only the BCD996P2 and BCD536HP, but may affect other models as well.

For anyone who has the issue and is willing to help, do you have an older unit that only recently developed this issue or are all the units with issues recently purchased? (after say last fall)

In general, please list any models that are experiencing the issue (especially if they are not already reported in this thread), and the approximate age of the unit.

Please post only in this thread, as there are several threads that have brought up this issue. I would like to gather the relevant info in this one.

 

[Reconrider]

What type of issues have you noticed?
I know a some people with the models you mentioned but they haven't asked me yet so I'd like to ask them and see if maybe they've noticed it.

 

[MStep]

We are investigating a hardware or firmware issue that affects P25 decode above 171.200 MHz. (the cutoff could be lower)

So far, this seems to affect only the BCD996P2 and BCD536HP, but may affect other models as well.

For anyone who has the issue and is willing to help, do you have an older unit that only recently developed this issue or are all the units with issues recently purchased? (after say last fall)

In general, please list any models that are experiencing the issue (especially if they are not already reported in this thread), and the approximate age of the unit.

Please post only in this thread, as there are several threads that have brought up this issue. I would like to gather the relevant info in this one.

It's encouraging that you've taken the bull by the horns Joe. However, may I suggest that one of the most definitive ways to identify the models and units involved would be by serial number. The information that you requested will give you an "overview", but may not pinpoint the cause of the problems because recently purchased items might be from older inventory, etc.

It is also interesting that you want to know if older units owned by folks here have suddenly developed the problem--- that could indicate that something has changed in the configuration of P25 protocols that Uniden may not be aware of yet.

For safety, security, or privacy issues, some folks may not feel comfortable posting the serial numbers of their units online. In addition to posting their general information here, they should be encouraged to privately email you the serial number of units involved. In lieu of that, Uniden might consider setting up a page on their own site where folks can report directly to them in a more private manner, giving the model and the serial number and thus have official confirmation in event that future hardware changes covered by warranty may be required. Folks who are buying units and sending them back for replacement is not going to resolve the issue. It's just going to cause additional burdens for dealers who sell Uniden products.

I am not discouraging members from posting reports of their issues here--- we are all interested, especially those who are sitting on the sidelines and holding off on purchases of the 996, 536, and other Uniden units, pending resolution of the issue.

Keep up the good work.

 

[Radio99]

My 996P2 (purchased one month ago) will not decode P25 audio above 171.2 MHz. On the other hand my 996T decodes audio above 171.2 MHz with no issues.

The 996P2 is running firmware 1.10.01

 

[JoeBearcat]

Actually, I am trying to isolate if this is a 'new hardware' issue or 'new firmware issue' or something else, so serials really are not relevant yet.

I'm not disagreeing with you, but I don't think serials will be that helpful at this point. And as you suggested, some may not want to post theirs.

The 'older units' question is to determine if this a firmware issue caused by the latest firmware. If the issue just started in older units (post-update), that would point directly to a firmware issue which is much more easily resolved (and might be motivation to get some engineering time in). Unfortunately, few members of the beta team have new units (including myself), hence the need for public input.

I have already alerted HQ to the issue, but would like to give them more details about it.

Fortunately, few systems use frequencies in the band segment involved. Of course, that also means fewer people to test.

 

[JoeBearcat]

My 996P2 (purchased one month ago) will not decode P25 audio above 171.2 MHz. On the other hand my 996T decodes audio above 171.2 MHz with no issues.

The 996P2 is running firmware 1.10.01

Thanks for the input.

What is the highest known VHF frequency that *does* work? (on the 996P2)

 

[JoeBearcat]

What type of issues have you noticed?
I know a some people with the models you mentioned but they haven't asked me yet so I'd like to ask them and see if maybe they've noticed it.

Non-decode of P25 above 171.200 MHz.

 

[Radio99]

Thanks for the input.

What is the highest known VHF frequency that *does* work? (on the 996P2)

170.8125 MHz

 

[Ubbe]

Actually, I am trying to isolate if this is a 'new hardware' issue or 'new firmware issue' or something else, so serials really are not relevant yet.

It's difficult to see it as being hardware related. There's no bandplan switch at 171.200 and IFX has been used and it has been tested by fulkg1 using a real P25 radio set to different frequencies to check at what frequency the problem starts. The datasignal are heard so the receiver is still working but there's no detection of the P25 signaling.

/Ubbe

I have tested on a SECOND P2 (replacement from Scanner Master), using a Motorola XPS5000 VHF P25 portable with front panel programming enabled. The bottom line is that these current P2's (the two we have tried at least) STOP decoding P25 audio above 171.200 MHz. Have tried even doing the IF shift ON / OFF on these frequencies, just as a try, no good.

Tested every 200 KHz or so, all the way to 172.450. Will NOT decode P25. Works fine at 171.200 and below.

It does receive signal on 172.450, full scale meter, and in ALL audio mode the digital rumble can be heard fine, just no P2 audio decode.

 

[enosjones]

Does this include 400mhz p25 too or strictly 171.200 to 174? Like 380mhz to 415ish?

 

[enosjones]

I only pick up a beacon on 167.4125, not much p25 where I'm at

 

[bearcat]

BCD536HP running FW 1.26.00 it decodes 172.6875 P25 fine. This radio is 3 - 5 years old. I can update to 1.28.14 and try again if Bearcat Joe thinks that is valuable?

For your information a 2014 BCD436 with FW 1.28.14 will decode 172.6875 P25

 

[JoeBearcat]

BCD536HP running FW 1.26.00 it decodes 172.6875 P25 fine. This radio is 3 - 5 years old. I can update to 1.28.14 and try again if Bearcat Joe thinks that is valuable?

For your information a 2014 BCD436 with FW 1.28.14 will decode 172.6875 P25

That would be good info, but I don't really want anyone to 'break' their unit. I can check to see if I have a file you can 'downgrade again'.

(side note, the 1.28.14 in the 436 is the latest version as of this post. I don't seem to have v1.26.00 available for the 536)

 

[bearcat]

That would be good info, but I don't really want anyone to 'break' their unit. I can check to see if I have a file you can 'downgrade again'.

(side note, the 1.28.14 in the 436 is the latest version as of this post. I don't seem to have v1.26.00 available for the 536)

Hopefully someone will chime in with an older 536 running 1.28.14

 

[JoeBearcat]

So far, it appears to be limited to the BCD536HP and BCD996P2 'newer hardware' models. I suspect it is something in the firmware that is not addressing the new hardware correctly, but have yet to confirm that.

Yes, hearing from someone with an older (1 year old or older) 536 and/or 996P2 who is running 1.28.14 (the latest FW) would be ideal.

Also hearing from someone with a 2022-purchase 436 or 325P2 who is running the latest FW would be nice. (someone who can test above 171.200 MHz)

 

[dispatch235]

The 2 latest 536's I bought withing the last 2 months neither would decode 171.4375; both running current firmware.
My older 536's are approx 1yr and 2yrs old respectively, running current firmware and decode just fine...
I sent the first new 536 back but still have the second one

 

[werinshades]

Here's an idea...how about those with an issue create a debug file so engineering can review?

 

[ofd8001]

I have the 1.28.14 firmware on probably what was one of the original 536 production units. I'm decoding 453.850 just fine - no complaints. It is conventional.

 

[JoeBearcat]

The 2 latest 536's I bought withing the last 2 months neither would decode 171.4375; both running current firmware.
My older 536's are approx 1yr and 2yrs old respectively, running current firmware and decode just fine...
I sent the first new 536 back but still have the second one

Thank you for confirming that. Do you have a newer 325P2 or 436 to test?

 

[JoeBearcat]

Here's an idea...how about those with an issue create a debug file so engineering can review?

If engineering wants that, I will. So far it seems to be pretty easy to replicate.