Welcome, Guest. Please login or register.
Did you miss your activation email?
May 25, 2015, 11:40:03 AM
Home Help Login Register      
News: NEW Follow LiveATC updates on Twitter and Facebook

+  LiveATC Discussion Forums
|-+  Recent Posts
Pages: 1 2 3 [4] 5 6 ... 10

 31 
 on: May 18, 2015, 09:05:30 PM 
Started by Mr Dispatcher - Last post by dave
It may be weeks before it is back.  The person hosting the feed is in extended travel.

 32 
 on: May 18, 2015, 08:30:09 PM 
Started by K5PAT - Last post by K5PAT
KMSY is still down waiting for a new internet connection. The new tenant is changing ISP's
and he is working out of town and is having trouble connecting with AT&T.
It will be back soon....hopefully.


 33 
 on: May 18, 2015, 05:15:50 PM 
Started by Mr Dispatcher - Last post by Brad G.
KLAS feeds down due to network outage

 34 
 on: May 18, 2015, 05:09:26 PM 
Started by Mr Dispatcher - Last post by Mr Dispatcher
Been down a few days now, just wondering what the sites issue is and when we can expect it back up? Thanks

 35 
 on: May 18, 2015, 01:19:41 PM 
Started by stuartjnewman - Last post by dave
This is LiveATC equipment.  The network we're on there is having serious packet loss issues, which basically cripples streaming.

We are working with the host to try and resolve it but it is a slow process.

 36 
 on: May 18, 2015, 08:49:59 AM 
Started by dave - Last post by dave
Not sure when we will have them back...this is in a remote site and not easy to access all the time.  Might need a modem reset.

 37 
 on: May 17, 2015, 10:48:51 PM 
Started by MIAMIATC - Last post by dave
The new feed is a work in progress.  The frequencies are based on what ground side transmitters can be heard, and it isn't totally clear yet what will work from the new location.  So let's not engineer any changes based on this new site yet.


 38 
 on: May 17, 2015, 10:01:39 PM 
Started by MIAMIATC - Last post by JetScan1
Quote
I provide the zlc_slc #1 feed. I wasn't aware that we have another zlc feeder until I saw this thread.

Thanks for the reply, I was thinking it was the same person running both. Then wondering why they were essentially scanning the same thing. Two different feeds, that kinda complicates things trying to coordinate them.

Quote
There are two that aren't very effective - 125.57 and 121.15 - because they are so far away, and I have terrain issues in reception. Those two should probably be removed from the scanner and frequency list.

I agree, scanning distant sectors on the fringe of reception ends up with a lot of weak and hard to read signals blocking stronger clearer ones on other frequencies.

Quote
If Dave's ok with it, then I can change zlc #1 to feed just 133.9, 128.55, and 127.82. Let me know how that sounds.

That setup isn't really ideal because it would put both controllers on one radio and the traffic volume would not be equal and mix up geographic areas.

Just to confirm the frequencies you can you hear the controllers on ? Sounds like 127.700 and either or both on 119.950 and 135.775 ? Is that correct ?

If it can be coordinated I think my suggestion would be the most optimum with ..

Radio #1

127.700
133.800
128.550
125.925
124.350

Radio #2

119.950
135.775
133.900
127.825

This would split the feeds geographically, by traffic volume,  typical sector configuration, and by controller reception.

- 133.800 is used as required and otherwise is merged into 127.700, so both should be on the same radio
- 127.825 is used as required and otherwise is merged into 133.900, so both should be on the same radio.
- 127.700 merges with 125.925, so both should be on the same radio.
- 127.700 and 133.900 are both busy sectors and should be on separate radios.
- 119.950 merges with 135.775, so both should be on the same radio.
- 135.775 is also a very busy sector at times, so no other further away frequencies should be added.
- controller reception on 127.700 would be split from controller reception on 135.775/119.950 (and their merged sectors).

The above was based on personal monitoring from a few years ago, but from what I can tell from recent listening of the current feeds this hasn't changed much. Corrections or updates always appreciated.


 39 
 on: May 17, 2015, 06:29:58 PM 
Started by MIAMIATC - Last post by bbrasmussen
I provide the zlc_slc #1 feed. I wasn't aware that we have another zlc feeder until I saw this thread. It's great to have another feeder!

Originally the zlc feed was split in two. I combined all the frequencies and dropped to just one zlc feed in order to provide all of the other KSLC airport feeds.

There are quite a few issues with monitoring in this area. The ZLC is the largest center in the country geographically. Not only is area size a factor, but terrain is also a huge issue (lots of mountains). Reception of both ground traffic (RCAGs) and airborne traffic is limited by high terrain. So monitorable frequencies can be limited based on location.

The frequencies on my feed are basically the ones that can be heard from my location. I have had issues with birdies showing up due to local RFI so at times I've had to lock a couple out. There are two that aren't very effective - 125.57 and 121.15 - because they are so far away, and I have terrain issues in reception. Those two should probably be removed from the scanner and frequency list.

That leaves six that I can reasonably receive from my location. Three of those six are on the new zlc #2 feed - 127.7, 135.77, and 119.95. That leaves three more that are not duplicate - 133.90, 128.55, 127.82.

If it's more beneficial, I can feed those three only and lock out the frequencies that are duplicated by the other feed. Geographically and traffic-wise this would probably be the best scenario. I would have the south and west on zlc #1, and zlc #2 would cover north and east.

As far as traffic goes, the two busiest - the ones feeding in and out of KSLC - are 133.9 and 127.7. In any scenario, as long as these busiest sectors are not on the same feed we get "the best bang for the buck."

If Dave's ok with it, then I can change zlc #1 to feed just 133.9, 128.55, and 127.82. Let me know how that sounds.

 40 
 on: May 17, 2015, 04:45:41 PM 
Started by echostar - Last post by echostar
What day are we talking about? Friday?
it was a Friday departure Saturday arrival. 5/15 -> 5/16

Pages: 1 2 3 [4] 5 6 ... 10


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!