BC250D and Fleetnet...WhitbyTower/Durham Area

[MetalCarnage]

Woohoo, i am back home from the cold north, anyways, i just finished programming in all of Zone 1, TPS and Durham Fire and was wondering if anyone else in the durham area uses a 250D...if so i am curious what Audio Settings they use for P25...i know the 250D is not known for awesome digital, but i would like to get as close as i can and was wondering what others were using...thanks

 

[DaveH]

Tried the Uniden DSP codes listed in the main table of the
Database record (SysID 782d)?

Dave

 

[MetalCarnage]

i have set everything to the way it should be, but when side by side with my 796D the 250D is pretty badly garbled (am gettting a sound quality reading of 0006 so it should be pretty clear) any tricks which i am missing, i knew that the 250D was not the best when it came to digital but i didnt expect it to be so bad that some stuff was so garbled that i cant even understand it (no, it is not encrypted, since as explained, i was running my 796D beside ti with crystal clear reception....plz help

 

[Wreckmaster]

just a thought,....could it possibly be in the baud rate, with the 796 having a faster and more variable rate ?

 

[MetalCarnage]

just a thought,....could it possibly be in the baud rate, with the 796 having a faster and more variable rate ?

Ummm, what baud rate would u be referring too for clarification?

BTW, for some reason it only seems to be certain radio ID's that come in crappier....Aurora5Bravo is always crystal clear yet whitby units come in 50% clear 50% garbled....anyways that can give me some hints it is appreciated...

 

[MetalCarnage]

Adding on to my last message i keep getting ID's like 8273 and 8663 which are not in the talkgroup ID listing, wondering if anyone could let me know how to identify them....

 

[MetalCarnage]

Adding on to my last message i keep getting ID's like 8273 and 8663 which are not in the talkgroup ID listing, wondering if anyone could let me know how to identify them....

 

[mciupa]

ID 8273 is in reality 8272 + 1 ( Essex) and 8663 is really 8656 + 7 (Aurora) , read up on status bits to see why your scanner is showing these ID's.

 

[MetalCarnage]

I just heard over Whitby5Kilo chatter that they are doing radio maintenance and that yesterday and today the radio system has been up and down, think maybe the tower is just screwed right now?

 

[mikewazowski]

Read the post above yours. There's nothing wrong with the tower.

 

[MetalCarnage]

Read the post above yours. There's nothing wrong with the tower.

The post above mine has nothing to do with whether or not the tower is working properly, so if u would care to explain what u meant that would be great

 

[mikewazowski]

mciupa explained to you why you were getting id's in that are not in the database.

You seemed to reply back that they're doing radio maintenance and the tower might be screwed up.

Most people would put two and two together and come up with the theory that you believe you are seeing these weird id's because the tower is screwed up.

So are you saying the tower is screwed up but that's not why you are seeing id's that aren't in the database or are you saying the tower is screwed up and that's why you are seeing weird id's?

 

[mciupa]

Just to expand on what I was saying , check this out from the WIKI , it takes a little digging
to find but it's there:

The Trunktracker scanners however interpret these special talkgroup status bits as different talkgroups entirely. Below is the conversion chart for these special status bits.



TTID + # Usage
ID+0 Normal Talkgroup
ID+1 All Talkgroup
ID+2 Emergency
ID+3 talkgroup patch to another
ID+4 Emergency Patch
ID+5 Emergency multi-group
ID+6 Not assigned
ID+7 Multi-select (initiated by dispatcher)
ID+8 DES Encryption talkgroup
ID+9 DES All Talkgroup
ID+10 DES Emergency
ID+11 DES Talkgroup patch
ID+12 DES Emergency Patch
ID+13 DES Emergency multi-group
ID+14 Not assigned
ID+15 Multi-select DES TG
Therefore, if a user was transmitting a multi-select call on talkgroup 1808, the trunktracker would actually receive those transmissions on 1815. Some common uses of these status bits are as follows: When a user hits their emergency button, all conversations on the talkgroup revert to the Emergency status talkgroup (ID+2) until the dispatch clears the emergency status. Therefore, if someone hit their emergency button and their radio was on talkgroup 16, all communications would switch to talkgroup 18. A lot of Fire and EMS departments dispatch tone-outs and alarms as Multi-select communications (ID+7). Therefore, if your fire department dispatch talkgroup is 1616, and they do dispatch tone-outs and alarms as Multi-selects, then those communications will be on talkgroup 1623. This could be a problem, because you will miss communications if you don't have those talkgroups programmed, or your scanner in search mode.

 

[EJB]

And Metal Carnage. It is very common on Fleetnet to have talkgroups patched.
I.E. Whitby and Downsview would show up 8723.
Port Credit and Camebridge on Port Credits talkgroup and Bruce Co. Grey and South Bruce on 8400.
It is a good chance that when you are listening to the OPP you are listening to a patched t/g.

We are saying just for you to check your status bit.
Simple.
E

 

[MetalCarnage]

mciupa explained to you why you were getting id's in that are not in the database.

You seemed to reply back that they're doing radio maintenance and the tower might be screwed up.

Most people would put two and two together and come up with the theory that you believe you are seeing these weird id's because the tower is screwed up.

So are you saying the tower is screwed up but that's not why you are seeing id's that aren't in the database or are you saying the tower is screwed up and that's why you are seeing weird id's?

LOL, wow, ppl get confused easily, since the topic is about how P25 audio quality is bad on my 250D one might assume that i am referring to the P25 audio on some units being crappy due to the maintanence they are currently doing....i only asked a brief question about the ID's because i didnt want to start a new thread, either way, my comment is related to the audio quality and how the tower maintenance and the fact the dispatcher said they were having radio problems over the airwaves may be why my P25 is coming in weird....for some reason Aurora units still come in clear as a bell and other units like whitby come in all digitized

EDIT: So no one else splurges on the ID topic, i understood status bit in the first place, it had just slipped my mind at the moment

 

[I_10_92]

My 250D does the same thing every now and then. Nothing too major. The audio quality isnt all that bad, if you are blasting the volume then it will be more distorted. The lower the volume, the better. That's what I've noticed anyway, there is a 'sweet spot' in the volume that is perfect for hearing OPP and digital transmissions.

I've never really noticed any specific talkgroup coming in all garbbled, since it doesnt happen all that often.

Hope that helps.

 

[MetalCarnage]

My 250D does the same thing every now and then. Nothing too major. The audio quality isnt all that bad, if you are blasting the volume then it will be more distorted. The lower the volume, the better. That's what I've noticed anyway, there is a 'sweet spot' in the volume that is perfect for hearing OPP and digital transmissions.

I've never really noticed any specific talkgroup coming in all garbbled, since it doesnt happen all that often.

Hope that helps.

Hmmm, well hopefully mine will stop doing it too....ya, i will take your tips on the volume, makes a big difference]

 

[IdleMonitor]

Sorry for hijacking this thread here. It took me a bit to learn about status bits etc...with fleetnet, but I was wondering, if I found the tg's with the status bit turned on, logged them, and put them in with the rest that I have, then turned the status bit off, would I still miss those calls? Ever since learning about these, I've been keeping the status bit on ignore. Am I missing much? I generally listen to MTO & EMS on fleetnet. Btw, good list to have kicking around just in case too.

Just to expand on what I was saying , check this out from the WIKI , it takes a little digging
to find but it's there:

 

[EJB]

Metal Carnage: You are leading these posts around and around in circles.
First you asked about a tower and audio settings then you mention about wierd talkgroups.
When you are told how and why : Then al of a sudden you complain that the thread is off topic, when YOU moved it from topic to topic.
You dont thank anyone.
Mcuipa goes out of his way to help anyone. You dont even give the man a thank you.
N/C

 

[jellotor]

Sorry for hijacking this thread here. It took me a bit to learn about status bits etc...with fleetnet, but I was wondering, if I found the tg's with the status bit turned on, logged them, and put them in with the rest that I have, then turned the status bit off, would I still miss those calls? Ever since learning about these, I've been keeping the status bit on ignore. Am I missing much? I generally listen to MTO & EMS on fleetnet. Btw, good list to have kicking around just in case too.

I think most of those would be picked up with a scanner whose status bit is set to 'on.' I'm not sure of the DES stuff, however, but patches, multiselects and emergency patches I have all seen/heard on trunked systems with a scanner whose status bit is on.

Sometimes it's just a matter of how the scanner interprets the status bit information, I suppose. For example, patching OPP talkgroups on Fleetnet may lead a scanner listener to believe that Port Credit units are showing up on the Cambridge talkgroup...when all of us trunker-usin'-folk can easily see that it's a patch or a multiselect or what-have-you.