 |
| Val. Com. Frequency Lists |
| King County Simulcast, Federal Way Site: From Left to Right 868.4250 (Control Channel) 851.0125 851.1625 851.3625 851.8125 851.9625 852.1125 852.6125 852.8625 853.3125 853.4875 853.6125 854.0875 854.2875 866.3625 866.3875 866.9375 866.9625 867.3375 867.4375 867.8375 867.8625 868.4500 |
| King County: McDonald Point Site: From Left to Right 860.7125 (Control Channel) 854.8125 855.3125 855.5625 855.8125 856.4375 856.7125 856.9375 857.2625 857.7125 858.2625 858.7125 858.9375 860.2625 |
| King County, Dodge Ridge Site: From Left to Right 855.2375 856.4625 856.9625 857.4625 858.4625 859.7625 |
| King County, Grass Mtn. Site: From left to right 858.4875 (Control Channel?) 855.7125 856.2375 856.4875 856.9875 857.2375 857.4875 857.9625 858.2375 |
| King County, Sobieski Site: From left to right 860.9625 (Control Channel?) 855.9875 858.9625 859.4625 859.9625 860.4625 |
| These are the exact frequencies that I have programed into my BC245XLT and Pro-2066 to monitor the South King County area of the Val. Com. system. If you plan on monitoring the South King County area I advise that you set up 2 trunking banks one for Fed. Way and one for McDonald Point. There are times when Units in this area go into range of Mcdonald Point, so you may be able to hear them on that system instead of Simulcast Federal Way. I know in different locations the Mcdonald Point site comes in much better than Federal Way. I only have the Fed. Way site and the McDonald Point site programed into my BC245XLT and Pro-2066. Because the other sites are to far away to monitor. So I'm unsure of the Control Channels on the last three sites. If you know them please let me know. Have Fun!!! |
|
|
|
|
|
|
| Updated 3/2001 |
| Note: With older Trunktracker Scanners you may want to enter the frequencies as a type one system with all the size groups set to one.. You can use type 2 if you like, but the type 2 ID#s wont come up as the right number If the system patches 2 ID#s together. Then what ever is the patched ID# being used is will be X amount of numbers higher than normal. This happens because the system changes the status bits on the ID# to create an ID# for the patch. (Example: 36944 with 36848 patched in would then be 36977) Newer scanners can ignore the status bits so the ID#s will come up as the normal ID#s on the type 2 system. When you set the scanner up in type 1 mode you need to use the type 1 ID#s, but they will appear correctly when patched. A very well deserved Thank you to Vince of Federal Way for helping me understand how this system works. |