Actions

Difference between revisions of "Baltimore City"

From The RadioReference Wiki

(Added RIDs)
 
(19 intermediate revisions by 4 users not shown)
Line 1: Line 1:
'''FIRST, please read the [[Simulcast digital distortion]] article to understand what is going on and why you may be having trouble receiving the system.
+
{{Infobox_TRS_P25_US_Pub
'''
+
|Owner    = Baltimore City
 +
|City      = [[Baltimore City (MD)|Baltimore]]
 +
|County    = [[Baltimore  County (MD)|Baltimore]]
 +
|State    = [[Maryland (US)|Maryland]]
 +
|Band      = 800 [[MHz]]
 +
| <!-- using parameter "SysType"'s default value -->
 +
|SysID    = 39F
 +
|WACN      = BEE00
 +
|NAC      = 390
 +
|Callsigns = {{Callsign|WPYR413}}
 +
|sid      = 6906
 +
|state    = Maryland
 +
}}
  
This topic is being discussed [http://forums.radioreference.com/maryland-radio-discussion-forum/194926-baltimore-city-change-dec-1-a.html here]. The database entry for the new system can be viewed [http://www.radioreference.com/apps/db/?sid=6906 here]
+
==Related Wiki Pages==
 +
* [[Programming the Baltimore City System]]
 +
* [[Baltimore City Radio IDs]]
 +
* [[Baltimore City (MD) Police]]
 +
* [[Star-Spangled Spectacular]]
  
Please use this article to document tricks, settings, and anything else that can be used to program the current crop of [[:Category:Digital Scanners|digital trunktrackers]] to correctly track the new Baltimore City P25 system. 
 
  
== Programming System Frequencies ==
 
Using the Pro96 CC Dump monitoring utility, it appears that there is a constant data stream (not the control channel) that hops between system voice frequencies. It may be the fire station signalling data, which constantly interrogates the fire station signalling units to verify connectivity. This stream hops between system frequencies, but never uses any of the four eligible control channel frequencies. Your scanner may momentarily confuse this data signal as the control channel, which could delay your scanner while it searches for and acquires the control channel. For this reason, it is recommended that you only program the four control channel eligible system frequencies into your scanner.
 
  
==Pro-96/Pro-2096==
 
; Win96
 
[[Image:Balt City P25 Win96.jpg]]
 
<small> Thanks fmon</small>
 
  
==PSR-800/Pro-18==
 
  
Programming of the Baltimore City system on the PSR-800 requires simply that you obtain the most up-to-date library download via the EZ Scan software that came with the radio. Using that software, allow the library to be updated on the PSR-800. After that update is complete, you can simply import the system from the library using either the software or directly from within the PSR-800 Browse Library function.
 
  
 +
Return to Wiki page: [[Trunked Radio Systems (MD)]]<br/>
  
Note: In order the find new talkgroups not submitted/published the Radio Reference, you must use the EZ Scan software to create a "Wildcard" object. Once this step is completed, you then must copy the system to the scanner.
+
[[Category:Maryland Trunked Radio Systems]]
 
 
 
 
Within the city limits, the radio and this "default" programming appears to do fairly well. However, reports are still coming in on issues with reception.
 
 
 
 
 
One tweak that helps (but has side-effects that you must consider*) is to only program in the single active control channel frequency to avoid having the radio drift and try to search other frequencies. This can only be done using the EZ Scan software. Of course the side-effect* is that if the control channel frequency changes, you'll hear nothing until you (a) notice this has occurred and (b) reprogram the radio with the new control channel frequency.
 
 
 
 
 
Also see the [[GRE/RS_PC_Object_Oriented_FAQ]] for additional settings in the error correction and noise threshold areas that might help, as this is a LSM system
 
 
 
==Uniden DMA Scanners==
 
<gallery>
 
Image:FS Balt City non-XT system.JPG|1.Non-XT System screen
 
Image:FS Balt City non-XT site.JPG|2.Non-XT Site screen
 
Image:FS Balt City XT system.JPG|3.XT System screen
 
Image:FS Balt City XT site.JPG|4.XT Site screen
 
</gallery>
 
 
 
* Note that the way the pre-XT scanners and XT scanners define P25 systems is '''different'''
 
** For the 396T and 996T be sure to set your system type to ''Mot Type II / P25'' and site type (applicable to the 996T) to ''Mot P25/P25 Standard''
 
** Also see the [[P25 audio decode level adjustment]] article, as well as the the following sections in the Easier to Read manuals;
 
*** [http://marksscanners.com/396/396.shtml#optomizing Optimizing P25 Performance - Easier to Read 396T Manual]
 
*** [http://marksscanners.com/996/996.shtml#optomizing Optimizing P25 Performance - Easier to Read 996T Manual]
 
* For the 396XT and 996XT both the system and site types should be ''P25 Standard''.
 
** See these sections in the Easier to Read manual for Optimizing P25 decoding
 
*** [http://marksscanners.com/396XT/396xt.shtml#optomizing Optimizing P25 Performance - Easier to Read 396XT Manual]
 
*** [http://marksscanners.com/996xt/996xt.shtml#optomizing Optimizing P25 Performance - Easier to Read 996XT Manual]
 
* Examples using FreeScan are shown above (Images 1-4). Additional examples are solicited.
 
 
 
==Other Digital Trunktrackers==
 
* It's been noted in the above thread that the current list of Uniden and GRE/RS digital trunktrackers (with the exception of the PSR-800) do a very poor job of decoding this system. It's likely this has to do with both the multipath issues and the LSM modulation, which evidently the current firmware cannot handle well. The information in the Uniden section should be used as an ''experiment'' and probably won't work well in most situations for this system.
 
 
 
==Baltimore City System Radio IDs==
 
RIDs identified using PSR-800 in Fall-Winter 2011. Duplicates marked with (D). I realize police units identify with different letters based on shift and radios may cross over, but these are listed as-heard to avoid future-reference confusion.
 
 
 
*2260175 M12
 
2260221 E14
 
2260750 TRK 16
 
2260877 E2
 
2260910 E57 PTBL
 
2260994 M14
 
2263611 8C35
 
2263722 8A11 (D)
 
2263801 4C36
 
2263887 8A10
 
2263888 8A21
 
2264142 8A22
 
2264145 8A32
 
2264223 8A34
 
2264227 8A35
 
2264361 KGA SW DISP
 
2265446 SW 4
 
2265508 8A09
 
2265858 8A14
 
2265928 8A11 (D)
 
2265931 8C26
 
2265976 8A12
 
2266010 8A36
 
2266013 8801
 
2266039 8A39
 
2266042 8A33
 
2266408 8A15
 
2266543 8850
 
2266544 8C11
 
2267313 7803 K9
 
2267352 8A26
 
2267755 8C14
 
2268036 FOXTROT UNK
 
2270179 A3 EMS1 OPER
 
2275353 KGA SW DISP
 
2276536 KGA CW OPER
 
2279399 EMS OPER
 
2279543 A3 EMS1 OPER
 
2279979 A2 MAIN DISP
 
 
 
[[Category:Mid Atlantic Region]]
 
[[Category:Regional Programming]]
 

Latest revision as of 22:31, 2 June 2020

Public Trunked Radio System

NameBaltimore City
OwnerBaltimore City
Owner TypePublic
CityBaltimore
CountyBaltimore
StateMaryland
CountryUnited States

System Details
Band800 MHz
TypeProject 25 Phase I
ID39F
WACNBEE00
NAC390

FCC Callsign(s)
WPYR413

System-specific links
DatabaseFCC Site Map
ForumRR Site Map

Other Resources
Trunktracking
FAQ
Trunktracking
Glossary

Wiki FAQMediaWiki
QuickRefPDF Card

Wiki HomeCollaboration Gateway → United States → MarylandBaltimore County → Baltimore City TRS

Welcome to the Baltimore City collaboration article, a Public Trunked Radio System located in Baltimore County, Maryland, United States.
This is where you, the user, may index any articles you develop for scanning related topics for this Trunked Radio System.



Related Wiki Pages




Return to Wiki page: Trunked Radio Systems (MD)