MD Emergency p96 file

[NINN27]

ok, its done... here are the banks...

0. MEMA/DNR/MSP/BGE trunk
1. BWI Airport and Fire Dispatch channels
2. Ft. Meade trunk
3. Anne Arundel County trunk
4. Baltimore City trunk
5. Baltimore County trunk/Roads & Traffic
6. Howard County trunk
7. Montgomery County trunk
8. D.C. Fire trunk
9. D.C. Police trunk/FMR/GMRS/US Capitol Police

 

[mlevin]

Well done, way to go!

 

[ka3jjz]

ok, its done... here are the banks...

0. MEMA/DNR/MSP/BGE trunk
1. BWI Airport and Fire Dispatch channels
2. Ft. Meade trunk
3. Anne Arundel County trunk
4. Baltimore City trunk
5. Baltimore County trunk/Roads & Traffic
6. Howard County trunk
7. Montgomery County trunk
8. D.C. Fire trunk
9. D.C. Police trunk/FMR/GMRS/US Capitol Police

Sounds like a winner. Now if I could get that file in csv format (if memory serves, Win96 has this capability), I'll start converting it for the Uniden scanners on Scan Control.
My thinking is that I'll split the file in 2 - the 'A' version (for analog only) will necessarily omit the Baltimore city, Howard, Montgomery, DC fire and DC police trunks as they are all digital. Since the 'A' version will be for the 895, 245, 780 and PRO2052, I'll probably back fill the unused banks with the rebroadcast and analog fire freqs for Baltimore city, Howard and Montgomery counties, DC Fire and MPD. Granted that it's not the best, but at least it'll be something. I'll likely include some ham repeaters, USPP and SHA 47 mhz as well. Since SC automatically upgrades, if a user wants to move this file up to the digital Unidens, that can be done fairly easily.
The 'D' (digital) version should handle just about everything here with minimal fuss. This file will be for the 785/796/250d/296.

My id is ka3jjz@erols.com

Thanx and nice job...Mike

 

[TinEar]

NINN27, I was going to ask if you could either post or email me a .txt version of your list to do much the same as Mike mentioned just above. You've already done a hell of a job and I hate to ask for more but just in case you get the opportunity....

 

[NINN27]

i would, but i dont know how to convert it to .txt

 

[TinEar]

And I'm too ignorant about computers to give you directions. I know I've sent emails of my ARC250 files and just attached the .mem file to the email and it arrives in a readable file and can be downloaded into another Uniden 250/785. In fact, I just tried sending one (unzipped) to myself to see if it worked that way and it actually did. The first few lines for the freqs look like this in the received email:
ARC250 MEM V1.00
1,"0459.6250","","1","0","2","0","0","0","0","0","3","3"," "
2,"0459.7500","","1","0","2","0","0","0","0","0","3","3"," "
3,"0459.8000","","1","0","2","0","0","0","0","0","3","3"," "
4,"0460.0250","","1","0","2","0","0","0","0","0","3","3"," "

And the talkgroup files look like this:
TD0 ,"016688","Command 1","0","0",""
TD1 ,"016400","District 1","0","0",""
TD2 ,"016432","District 2","0","0",""
TD3 ,"016464","District 3","0","0",""

And that's the best I can come up with. I have no idea if a memory file from the PRO-96 would look anything like that though.

 

[bear105]

Great Job!! Thanks!

 

[ka3jjz]

i would, but i dont know how to convert it to .txt

Not .txt, .csv format. that option is mentioned on the Win96 home page. Scan Control has the ability to import csv files - in fact it has a fairly slick utility for just this function.
I'll bet someone here knows how to do this...

73s Mike

 

[stlscanner]

I'll bet someone here knows how to do this...

Yep.

FREQUENCY columns are as follows:
Scanner Bank - Channel Number - Text Tag - Frequency - Mode - Tone

TALKGROUP columns are as follows:
Scanner Bank - Talkgroup Bank - Talkgroup Slot - Text Tag - Talkgroup Number


Good luck!

Tony
more SCANNER stuff - http://myweb.accessus.net/~090/toc.html

--

 

[TinEar]

Tony, that's great...thank you. It unzipped and opened just fine in a similar format to what I posted above. I can now read it and adapt it for my uses. And thanks again NINN27 for the work you did to put the file together.

 

[NINN27]

no problem. i do have to send some credit to bear (for his DNR and BWI Airport frequencies). but non-the-less, i do hope everyone enjoys it. youre welcome everyone.

 

[ka3jjz]

no problem. i do have to send some credit to bear (for his DNR and BWI Airport frequencies). but non-the-less, i do hope everyone enjoys it. youre welcome everyone.

Firstly, let me congratulate NINN27 for the work in putting this together. There's a lot here, and I can see I'm going to have my hands full adapting all of this.
I have found many things that need some attention, though. I'm kinda a stickler for accuracy; particularly where emergencies are involved. This is NOT an attack of any kind - but these things do need a little attention;

1. The trunk system listed as 'BWI Airport' actually belongs to ARINC and is leased to USAir. The
Fleet IDs as given are incorrect; they've been remapped and are posted on the
RadioReference database. This system is slowly being phased out and is being
replaced by NexTel.
A much more useful system to scan - since it's largely unknown - is the United
400 Mhz system. The system stats are also posted on the RadioReference database.
Note that most of the system seems to use ICalls almost exclusively, except for
the 2 or 3 public talkgroups.

2. 125.3 hasn't been used in years and years; the correct frequency is 125.525

3. The milair listings are incorrect; you can find a much more complete - and correct-
listing here:

http://www.davidschoenberger.net/scanning/maryland/bwi.htm

4. The correct frequency for AirTran ops is 461.7125; the PL listed is correct. Be sure
to program this with the correct step size.

5. BWI Fire's frequency is correct, but the PL (123.0) is missing

6. If you're just concerned with the Metro area, you can eliminate Charles and Calvert, which
are both in Southern Md.

7. Anne Arundel county - the PL for 154.01 is 114.8. The BWI fire dispatch PL is 123.0 as was
mentioned earlier

8. Baltimore city freqs - The PLs for both 154.415 and 154.145 is 156.7. This applies to the
Balt city fire freq in the BWI list as well.

9. Montgomery county fire PL is, I'm pretty sure, still 156.7. Be sure to apply that to both the
fire freqs in the BWI section and in Montgomery county.

10. A rather old listing I have suggests that 154.385 Balt.city also uses 156.7 as a PL, even though
it's a fireground channel

11. The SHA listings look odd; was there a reallocation of regions and freqs? The RadioReference listing
is, I think, still correct.

12. Skywarn for Anne Arundel county is 147.105 PL 107.2. Make sure you use the correct step size

13. Metro traffic Baltimore is 450.4875, PL 141.3 This freq is also used for audio feeds.

73s and back to the listings...Mike

 

[TinEar]

I believe freq 126.75 is also left off the list for BWI. Three other freqs at the airport are 118.05 for Clearance Delivery, 120.20 for Ground Control as a backup freq which they seem to go to often because of noise on 121.9 and then there is 123.75 which is a backup tower freq which is also used but not as frequently as Ground Control backup. It wouldn't hurt to put the two Guard (Emergency) freqs in either - 121.5 and 243.0. These are of course up to each individual considering how exacting they want coverage to be of the airport.

Also, on AA County, talkgroups 13K, L, M are also in use but I can't pin down the users yet. I keep catching parts and pieces of conversations.

Still, this was a fantastic and beneficial piece of work by NINN27 to bring this all together. I'm sure everybody will have their favorites to add but this list covers the vast majority of things for an emergency listening resource.

 

[ka3jjz]

I believe freq 126.75 is also left off the list for BWI. Three other freqs at the airport are 118.05 for Clearance Delivery, 120.20 for Ground Control as a backup freq which they seem to go to often because of noise on 121.9 and then there is 123.75 which is a backup tower freq which is also used but not as frequently as Ground Control backup. It wouldn't hurt to put the two Guard (Emergency) freqs in either - 121.5 and 243.0. These are of course up to each individual considering how exacting they want coverage to be of the airport.

Also, on AA County, talkgroups 13K, L, M are also in use but I can't pin down the users yet. I keep catching parts and pieces of conversations.

Still, this was a fantastic and beneficial piece of work by NINN27 to bring this all together. I'm sure everybody will have their favorites to add but this list covers the vast majority of things for an emergency listening resource.

Yep, you're right on all counts. I'll put those additional BWI freqs in. It's a shame that the 245 doesn't cover milair, though

Here are just a few more items that need fixing;

a. MSP Barracks Q College Park is on 39.26, not .36 - they moved to avoid skip from the CHIPs

b. Dave Schoenberger's BWI page shows Southwest customer service on 461.575, not .600. Also check
Southwest maintenance on 461.275, not .300

c. 460.6 - Harford Fire uses PL 136.5
154.25 - Howard Fire uses PL 103.5
154.16 - Montgomery fire uses PL 156.7

I'm quickly finding out that 300 channels simply isn't enough (hi). I'll probably rebuild my files to concentrate on the DC-Baltimore metro area, and leave off the other areas. Those NIR frequencies may also have to go, too, darn it. I'll need the space for the COG/RINS and all the rebroadcast frequencies.
Still though, my files will be using NINN27's freqs for the most part.

73s Mike

 

[TinEar]

It would be a shame to not be able to listen to the 243.0 guard freq if you live closer to the DC area since it's often active and interesting. There seem to constantly be aircraft wandering into the prohibited area, followed by very stern warnings ("turn to 90 degrees and exit the area immediately"). The tone of voice leaves no doubt about the consequences of noncompliance.

The 118.05 Clearance Delivery freq I mentioned above for the airport is a drag to listen to most of the time (unless you follow the flight plan on an airway map and realize how cool the planning is). The upside is that during weather or emergency delays, that freq is where you'll learn what the airport radar is currently showing and when they expect the airport to reopen for flights - along with sometimes very detailed descriptions of weather related storms passing through the area. The captains are mollified by this info since they are sitting in their cabins just waiting and waiting and need to tell their passengers the reasons for delays. I love it since I'm so close to the airport that these reports pertain to me and the safety of my house. I guess we all have different reasons for liking certain freqs.

 

[ka3jjz]

It would be a shame to not be able to listen to the 243.0 guard freq if you live closer to the DC area since it's often active and interesting. There seem to constantly be aircraft wandering into the prohibited area, followed by very stern warnings ("turn to 90 degrees and exit the area immediately"). The tone of voice leaves no doubt about the consequences of noncompliance.

===========
Ah, but I've heard that once in a while on 121.5 as well, so you won't miss too awful much.

I've got a baseline freq file built, but I need to clean it up and test it before I can release it. I also need to see if I can build scan lists. Because the 895 and 245 are different, I'm going to have to build them differently; the 245 can do 400 mhz trunk and have conventional/trunk freqs in the same bank while the 895 cannot. No big deal there, and it might free up a little space. I don't have too many conventional slots free at the moment!

The layout I am using consists of:

1. MSP/SHA/DNR/MENA
2. BWI airport
3. fire rebroadcasts and DC (Capitol and USPP, along with the MPD rebroadcast).
4. FRS/GMRS
5. ITAC/COG/PMARS/Baltimore metro
6 Ft.Meade/Howard (conventional for the 895, trunked for the 245)
7 USAir/ARINC
8. BGE
9 Baltimore county
10 AA county

I'll probably move things around a little, but that's basically it. I might add the MTA bridges and tunnels freqs (and even there, there's going to be a little trick, since the 895 can do PL, the 245 can't) and one or two more things. But as you see, it's basically NINN27's file.
Oh yes, this file will be optimized for the DC metro area from Montgomery up to the state line. I just don't have the room for the southern and western stuff.
73s for now while I uncross my eyeballs....Mike

 

[NINN27]

just so everyone knows... i built this file WITHOUT my p96 (damn Ft. Worth service center), so i was waiting (thank you mike) for someone to find "mistakes". in any sense, i will leave the file as i originally posted on here, since (as mike had said earlier) people will add and/or delete what they want and dont want. thank you for the corrections mike.

 

[NINN27]

1. The trunk system listed as 'BWI Airport' actually belongs to ARINC and is leased to USAir. The
Fleet IDs as given are incorrect; they've been remapped and are posted on the
RadioReference database. This system is slowly being phased out and is being
replaced by NexTel.
A much more useful system to scan - since it's largely unknown - is the United
400 Mhz system. The system stats are also posted on the RadioReference database.
Note that most of the system seems to use ICalls almost exclusively, except for
the 2 or 3 public talkgroups.

2. 125.3 hasn't been used in years and years; the correct frequency is 125.525

3. The milair listings are incorrect; you can find a much more complete - and correct-
listing here:

http://www.davidschoenberger.net/scanning/maryland/bwi.htm

4. The correct frequency for AirTran ops is 461.7125; the PL listed is correct. Be sure
to program this with the correct step size.

5. BWI Fire's frequency is correct, but the PL (123.0) is missing

6. If you're just concerned with the Metro area, you can eliminate Charles and Calvert, which
are both in Southern Md.

7. Anne Arundel county - the PL for 154.01 is 114.8. The BWI fire dispatch PL is 123.0 as was
mentioned earlier

8. Baltimore city freqs - The PLs for both 154.415 and 154.145 is 156.7. This applies to the
Balt city fire freq in the BWI list as well.

9. Montgomery county fire PL is, I'm pretty sure, still 156.7. Be sure to apply that to both the
fire freqs in the BWI section and in Montgomery county.

10. A rather old listing I have suggests that 154.385 Balt.city also uses 156.7 as a PL, even though
it's a fireground channel

11. The SHA listings look odd; was there a reallocation of regions and freqs? The RadioReference listing
is, I think, still correct.

12. Skywarn for Anne Arundel county is 147.105 PL 107.2. Make sure you use the correct step size

13. Metro traffic Baltimore is 450.4875, PL 141.3 This freq is also used for audio feeds.

#1 - just labeled as BWI for my entertainment, ****s, and giggles (i knew it was ARINC, but thanks)

#2 - FIXED

#3 - FIXED

#4 - FIXED

#5, #7, #8, #9 - DIDNT KNOW ABOUT THESE, BUT AM LEAVING THE WAY IT IS (EASIER FOR ME, BUT YOU ARE FREE TO DO WHAT YOU WANT WITH THE FILE)

#6 - KEEPING FOR ****S AND GIGGLES

#10 - I ONLY PUT THE DISPATCH CHANNELS IN, BUT AGAIN, YOU ARE FREE TO DO WHAT YOU WANT WITH IT

#11 - FIXED

#12 - FIXED

 

[ka3jjz]

Ok I'm almost done assembling a version of NINN27's file for the 895 and 245 using Scan Control. I have frequencies and trunks set up, but the scanlists aren't working for some reason (they cause a communications crash when I try to upload them). I've written to Ken D. at Scan Control's tech support and he's looking into it.
Once that problem is fixed, we should be good to go. I plan to post these files in Scan Control's .dat format as well as csv (probably in a zip file) so most anyone can use them.

As soon as I have more info, I'll post it here.

73s for now...Mike

 

[TinEar]

a. MSP Barracks Q College Park is on 39.26, not .36 - they moved to avoid skip from the CHIPs

If so, they are back on 39.36 now - at least they are as of this evening and confirmed with callsign KSU469.

Mike, do you happen to know where the transmitter for DNR HQ/Tawes on 39.22 mHz is located? It's an extremely strong/loud signal.