loumaag
Silent Key - Aug 2014
I have found what I think is a decoding error in my BCD396T radio dealing with private calls (I-Calls) on a P25 system. I suspect that it would exist on BCD996T also.
Background -- There is a new P25 system going on line here in the Amarillo area and since there are no other trunking systems to speak of here I have been spending a lot of time on it the past several days. While commenting on I-Calls in another thread I found an inconsistency dealing with what I was seeing on the screen of my BCD396T and what I knew to be accurate.
The radio techs are programming the radios with the individual unit numbers of the people who have the radio (or the other way around I don't know which). The bottom line is that using Pro96Com software on with my Pro-96 locked on the CCh, I see various radio ID's talking and the radio ID always matches the call sign of the individual. For example Unit 225 would be using radio 703225, Unit 124 would have radio 701124, etc.
Problem -- At first I didn't notice this until I had started assigning ID's to Radio ID's in Pro96Com to match the actual unit number, where it was working out of and if possible the individual's name. Using my BCD396T with I-Call On (no wild card set) I was seeing private calls showing up like "745678-734567" and didn't notice that the ID's didn't match the actual radios until I glanced down when a guy who is on all the time was talking and his radio ID wasn't showing on the display.
I waited until I could get two people I had previously ID'd talking in a private call and recorded the information this is what I found (previously mentioned in this post):
Analysis -- I have been working on this on and off since then and I think I have figured out the problem. It would appear that the BCD396T is treating these private call ID's like it would a Motorola radio ID, making the (incorrect) assumption that all radio ID's start with 7 and have the individual ID behind it. Like for example 748544 is a radio, so subtract 700000 from the ID leaving 48544 as the actual ID. This may have worked for Motorola systems but it doesn't work for P25 systems.
Using the above example see this:
It would appear that Uniden is ignoring the most significant word (hex) of the RID.
Verification -- I would like anyone with both a Pro-96/2096 and a BCD996T that has a P25 system that makes use of private call to see if this holds true for the 996T also. Of course I would appreciate anyone else looking this over to see if my conclusion makes sense.
----------------
If we determine this is a problem (and I analyzed it correctly) then I guess we can see if Uniden can do anything about it.
Background -- There is a new P25 system going on line here in the Amarillo area and since there are no other trunking systems to speak of here I have been spending a lot of time on it the past several days. While commenting on I-Calls in another thread I found an inconsistency dealing with what I was seeing on the screen of my BCD396T and what I knew to be accurate.
The radio techs are programming the radios with the individual unit numbers of the people who have the radio (or the other way around I don't know which). The bottom line is that using Pro96Com software on with my Pro-96 locked on the CCh, I see various radio ID's talking and the radio ID always matches the call sign of the individual. For example Unit 225 would be using radio 703225, Unit 124 would have radio 701124, etc.
Problem -- At first I didn't notice this until I had started assigning ID's to Radio ID's in Pro96Com to match the actual unit number, where it was working out of and if possible the individual's name. Using my BCD396T with I-Call On (no wild card set) I was seeing private calls showing up like "745678-734567" and didn't notice that the ID's didn't match the actual radios until I glanced down when a guy who is on all the time was talking and his radio ID wasn't showing on the display.
I waited until I could get two people I had previously ID'd talking in a private call and recorded the information this is what I found (previously mentioned in this post):
- Unit 904 called Unit 902.
- In Pro96Com this showed up as 703904 under TG and 703902 under radio id in a private call.
- The BCD396T showed 748544-748542 on the display.
Analysis -- I have been working on this on and off since then and I think I have figured out the problem. It would appear that the BCD396T is treating these private call ID's like it would a Motorola radio ID, making the (incorrect) assumption that all radio ID's start with 7 and have the individual ID behind it. Like for example 748544 is a radio, so subtract 700000 from the ID leaving 48544 as the actual ID. This may have worked for Motorola systems but it doesn't work for P25 systems.
Using the above example see this:
Code:
Actual P25 Data | Uniden interpretation
DecRID HexRID | DecDisplay - 700000 HexOfResult
703904 0x0ABDA0 | 748544 48544 0xBDA0
703902 0x0ABD9E | 748542 48542 0xBD9EVerification -- I would like anyone with both a Pro-96/2096 and a BCD996T that has a P25 system that makes use of private call to see if this holds true for the 996T also. Of course I would appreciate anyone else looking this over to see if my conclusion makes sense.
----------------
If we determine this is a problem (and I analyzed it correctly) then I guess we can see if Uniden can do anything about it.
