LiveATC Discussion Forums
Air Traffic Monitoring => Listener Forum => Topic started by: datainmotion on June 05, 2012, 03:03:57 PM
-
Over the last couple of weeks, I have had my Uniden 785 (not currently feeding audio) scanning just the High and Ultra-High channels used on the ZDV feed. It makes transmissions a bit easier to follow than the curent feed, which is crowded to say the least.
My thought is to keep Low channels on the existing feed and use the 785 to send audio from High/U-High channels to a new feed.
Love to hear everyone's thoughts on this...
-
My vote would be to split it. As at is now its so overloaded with frequencies its very difficult to listen to.
-
159 looks and only 2 votes? :-o
Everyone is welcome to vote in this poll as well as share their opinion, so please do.
Thanks.
-
Two weeks and all the votes are for a split ZDV feed. I'll get it ready...
-
Just a helpfull hint about the feeds. I have been listening this morning and it sounds good. the Low feeds frequency 133.95 if possible can be handled on both feeds since this frequency is a High Frequency as well a Low frequency. Also I dont know if you can check to see if 118.475 is on the low feed ?
Thanks
Mike in Boynton Beach FL
-
Hi Mike,
133.95 is Thurman (Low) and because of that, I am hesitant to add it to the High feed (it's very busy with traffic arriving/departing via the East). Which High sector is 133.95?
118.975 (S15-L) is being scanned on the Low feed. I may have given Dave an incorrect frequency on that one when the ZDV feed started and it was just never corrected on the posted list.
Mike
-
133.95 sometimes operate the high that 126.875 covers I would say a good 70 % of THE time. The low I meant was 118.475 not 118.975. Anyway feed found good
-
Yep - my bad. 118.475 Sydney/Brush is being scanned.
-
Hey,
I have a copy of the frequency and sector splits from the center itself. Would you like me to send it?
-
Im down with that. Please.
-
I 'm always open to freq info...
-
Wilco.
On the 785, its set per channel so give me a couple minutes and I'll have them all off delay.
*Done*
-
Its a standard scanner. Delay is on or off. All channels have been programmed to off. I can tell the difference...
-
In the audio, I mean, now that the delay is off. Sure you're not hearing looped audio from your player?
-
Okay - my apologies. Programming via ARC250 and the delay selection is not a drop down, so each selection must be clicked through. I selected a blank the first time around and apparently needed to click 3 more times for "none". :oops:
Needless to say, now there really is no delay, but whew, its tough to keep up with listening now... :|
-
The thing is with the delay off you are hearing a lot more transmissions, probably around 35-40% more. In my opinion this is much better than having a 2 second delay after every transmission that was resulting in almost 20 to 25 seconds a minute that the scanner was stopped (dead air).
I appreciate the input. While I have always been an avid fan of monitoring in general, my habits from land mobile scanning (i.e. - using the delay to hear a response) have carried over into my feeds. It's apparent that the same effect may not be desired as much in aero monitoring (at least high altitude Center channels). Duly noted.
It's hard to follow because you are scanning way to many busy frequencies which could be improved by not scanning as many.
I think you guys know by now that I am always open to suggestion and most of the time will defer to loyal listeners requests. I can certainly pare down the channels. With that said, my first thought is to do it geographically, starting with the most distant RCAG sites first (ZAB 71 and 72 come to mind). However, I also know someone with more experience in listening may suggest that I consider what airlanes are the busiest first, rather than just RCAG distance from my receiver. That's where I'd need some advice.
I also notice you have the flightwatch frequency on the high feed, you have it listed on the low feed, moving it over there would help.
Gone from high and back to low. I also have retained Guard on Hi as we do get traffic on it from time to time (usually one flight calling another to inform them Center is trying to contact them).
While on that topic, I do have a couple other freqs on the high feed that I haven't listed as of yet - they are the TSU (Tactical Special Use) channel for ZDV and also the UHF freqs for the U-Hi Sectors of 18,30,38,65,67.
As always, I appreciate everyone's input to make any of my five feeds here more enjoyable! :-D
-
data, if you need help adding more channels, or shuffling stuff around, we should talk... I'm near I-25 and Arapahoe and have been thinking about adding stuff, but duplicating your work wouldn't be smart...
(I do the KAPA TWR feed right now, and it really does need a rebuild since that scanner has a slight hum and the PC is ancient. Perhaps it's time to start work on some new gear in a rack and build it all "right"... Maybe split some stuff Left/Right, etc... The whole thing is just kludged together right now but has been running a long time that way with no significant problems other than Comcast outages.)
-
denverpilot - sent you a PM.
-
Hey,
I have a copy of the frequency and sector splits from the center itself. Would you like me to send it?
What - just tossed that teaser out there and then split? :lol:
I think a number of us may want to see what info you have...
-
Reviving dead thread...
We've been chatting. And I've been gathering gear...
BC780XLT, BC350A, power supply, antenna, connectors, coax, and assorted junk are already in "the project pile".
Waiting on some news about a very expensive automotive repair (wife's car's transmission) before committing to the multi port sound card and PC stuff.
-
Swapped the BC780XLT onto the KAPA TWR feed this afternoon. Also added two frequencies. (Sent to Dave for DB update.)
Audio quality and receiver sensitivity smoke the old scanner. Slight power supply him which will go away after I get the rack built with the DC supply in it.
-
Sounds excellent!
-
Sound card still hasn't arrived, just for a tickler update. :-(
It's coming via slow free shipping, so maybe another week.
-
Well - I've trimmed ZDV-Hi back to 18 freqs now (was 25) and ZDV-Lo is up one to 13. 8-)
-
If I may ask which frequencies did you lop off the high feed. been tryingt o figure out which ones while looking at my flight tracker but your delay is off so its quite difficult trying to figure it out .
-
Still no sound card. Grrr.
-
If I may ask which frequencies did you lop off the high feed.
Dave will be changing the published list on the feed later, but here's whats currently being monitored:
ZDV High (deleted any sectors not in CO)
ZDV03 126.725
ZDV04 135.125
ZDV05 132.850
ZDV14 128.325
ZDV16 120.575
ZDV17 127.650
ZDV25 133.525
ZDV28 134.125
ZDV29 132.225
ZDV30 135.400
ZDV33 127.950
ZDV34 133.175
ZDV37 125.675
ZDV39 127.525
ZDV46 124.775
ZDV61 126.875
ZDV65 127.075
ZDV67 124.225
-
Suggestion
you are missing 2 very close sectors that involve DEN A/D in not keeping 132.175 and 127.025 on the highh feed and 125.675 is a sector that is quite out of range(barely hear loud traffic on that one and 127.95 if i am not mistaken is a non working frequency.
can you please add 132.175 and 127.025 while deleting 125.675 and 127.95
also thinks that alb center 133.05 and kc 133.45 should be trimmed off
-
If you think about it it would leave the feed with 2 less frequencies
-
Sound card is backordered with no date for shipping. Company asked this morning if I would like to cancel the order. Bummer.
(Dave, your favorite Linux sound card appears to be discontinued.)
-
As a reference for this ZDV High Altitude feed I put together a chart (pdf attached below) that shows the applicable sectors and frequencies in range of Denver. The redish circle at 200 miles represents the approximate reception range. Frequencies have been confirmed from monitoring. Any updates or corrections always appreciated.
-
Suggestion
you are missing 2 very close sectors that involve DEN A/D in not keeping 132.175 and 127.025 on the highh feed and 125.675 is a sector that is quite out of range(barely hear loud traffic on that one and 127.95 if i am not mistaken is a non working frequency.
can you please add 132.175 and 127.025 while deleting 125.675 and 127.95
also thinks that alb center 133.05 and kc 133.45 should be trimmed off
I keep forgetting you post/PM your messages. I responded via PM. Let me look over the .pdf JetScan just posted and I'll get back to you...
-
As a reference for this ZDV High Altitude feed I put together a chart (pdf attached below) that shows the applicable sectors and frequencies in range of Denver. The redish circle at 200 miles represents the approximate reception range. Frequencies have been confirmed from monitoring. Any updates or corrections always appreciated.
You are a beautiful human being - this is exactly what I needed! 8-)
-
this is exactly what I needed!
Thanks for providing the radio ! This is what I used to confirm the frequencies.
-
Here is the re-revised ZDV High. Thanks guys!
ZDV03 126.725 Meeker
ZDV04 135.125 Grand Mesa
ZDV05 132.850 Kremmling / Aspen
ZDV07 133.950 Brush A (Low/High)
ZDV08 127.025 Hayes Center, NE
ZDV09 126.325 Ogallala, NE
ZDV14 128.325 Hayden
ZDV16 120.575 Sterling
ZDV17 127.650 Colby, KS
ZDV18 132.175 Colby, KS (UH)
ZDV25 133.525 Gunnison
ZDV28 134.125 La Junta
ZDV29 132.225 Eastonville / LaJunta
ZDV30 135.400 Pueblo
ZDV33 134.575 Cheyenne, WY
ZDV34 133.175 Medicine Bow / Cheyenne, WY
ZDV38 133.425 Farmington, NM (UH)
ZDV39 127.525 Lamar
ZDV46 124.775 Pueblo
ZDV61 126.875 Denver
ZDV65 127.075 Blue Mesa (UH)
ZDV67 124.225 North Platte, NE (UH)
I'll have it scanning this list momentarily...
-
thank you for the zdv feeds. is it possible to list zdv low freq like you did in reply 34? thank you.
-
You're welcome for the feeds - thanks for listening!
ZDV Low:
ZDV06 128.650 Denver A / Kremmling
ZDV07 133.950 Brush A
ZDV11-S 134.500 Grand Mesa B
ZDV11-N 120.475 Hayden
ZDV12 125.350 Gunnison / Montrose / Grand Mesa A
ZDV13 126.500 Denver A / Walton Peak
ZDV15 118.475 Brush B / Sterling
ZDV21 125.900 Cheyenne / Laramie
ZDV26 119.850 Denver B
ZDV27 133.400 La Junta
ZDV36 118.575 Cortez / Durango
ZDV41 128.375 Pueblo / Eastonville / Alamosa
ZDV42 134.975 Eastonville (discreet)
-
Turned on 10dB of attenuation for ZDV low just now - a bit to much amplification for it to handle w/o it.
-
Side update, house was hit by lightning last week, still dealing with various problems. It's back burnered almost everything "hobby" related.
I think [insert Deity here] is trying to tell me something. Hahaha. Wow. What a week.
The LiveATC gear survived the strike, and with some up and down for killing the power to the whole house for inspections and repairs, KAPA TWR is still generally plugging away.
-
Saw some of your tweets and pix - ugly :-o
Just keep that great APA feed running brother!
I picked up a mint Pro-2006 to split ZDV High into North and South (11 freqs each); should be online within the next week or so...
-
Sorry my promised "assistance" has turned into a total fizzle, man.
Tonight I had a first... Troubleshooting the malfunctioning continuously keyed IRLP setup, I ultimately found the GE CTCSS receive decode board blown in the MASTR II. Even more interesting, it blew in such a way to continuously key the transmitter?
I didn't bother figuring out why, since everything of interest in a GE CTCSS decode board is inside their proprietary two ICs standing above the board. I just swapped it for a spare one out of another receiver.
Here I thought it would be the IRLP board itself. Heh. Next I thought it might be the keying circuit on the 10V regulator card. Nope. Last thing I tried was pulling the decode board.
Lightning does whatever it wants to do, as always.
Yay for swappable radio components. No single board radio, the MASTR II. Stuff can actually be worked on. Yippee.
And now the coax is making crispy crunchy noises on receive if its wiggled, too. Going to have to order up some new LMR-400. I have a suspicion the link yagi was hit or partially hit during the storm. One of the branch circuits that had a blown ground was the one feeding the MASTR II. I think the UPS saved the PC and somehow it managed to survive also.