Great, thank you!
Gilbert On Jul 19, 2023, at 11:11 AM, Stonie Cooper <address@hidden> wrote:
Steve has an inside contact with the uplink contractor, he or one of us will reach out and see.
Stonie Steve, I totally agree. Stonie: is there anyway you can find out if somebody fired up the promised broadcast signal on the horizontal polarization of this satellite (Galaxy 31) and frequency?
They are on ANCF, btw.
Gilbert
Although stable, as everyone else expressed, lower.
If I were a betting person, and I'm not, my bet is this is an artifact of the uplink.... does anyone know if the SBN is on ANCF or BNCF, and which transmit vehicle?
Stonie Hi Jim, et. al,
On 7/19/23 07:54, Weber, Jim wrote:
> So it looks like on that graph that Stonie sent out it never really
> recovered completely. I see my signal is down roughly 2.5-3dB compared
> to the “normal” average I get. Are others seeing the same?
Our NOAAPort dish here in Boulder has seen the same thing as Stonie's
dish in Nebraska. On July 18 at 14:39 we experienced a 2 dB drop in
C/N, and it has not returned to previous levels, just like others.
Hopefully, the ticket that Gilbert opened will result in some positive
action 🤞
Cheers,
Tom
> *From:*Gilbert Sebenste <address@hidden>
> *Sent:* Tuesday, July 18, 2023 11:31 PM
> *To:* Mike Zuranski <address@hidden>
> *Cc:* address@hidden; address@hidden; address@hidden;
> address@hidden; address@hidden;
> address@hidden; address@hidden;
> address@hidden; address@hidden; Weber, Jim
> <address@hidden>; address@hidden; address@hidden; address@hidden;
> address@hidden
> *Subject:* Re: 20230718: latest 7 day summary NOAAPort Gap stats
>
> I just called the NWS Network Control of Operations (NCO).
>
> They were absolutely shocked when I showed them what happened today and
> what's happening right now. They said nobody called in about it and
> nobody at the NCF or the NCO noticed this. I'm literally the first
> person who saw it this afternoon. And I figured that something this bad
> would be noticed immediately. And the guy at NCO said "yes, I thought we
> would've noticed that too!".
>
> I can't tell you how frustrated I am right now...
>
> Gilbert
>
>
>
> On Jul 18, 2023, at 9:17 PM, Mike Zuranski <address@hidden
> <mailto:address@hidden>> wrote:
>
>
>
> Evening Gilbert,
>
> On Tue, Jul 18, 2023 at 8:38 PM Tom Yoksas <address@hidden
> <mailto:address@hidden>> wrote:
>
> Hi Gilbert,
>
> On 7/18/23 18:41, Gilbert Sebenste wrote:
> > Today, it's College Of DuPage, a cellular provider turned on
> > 5G at the tower 500' feet from us and wrecked our once beautiful
> > signal.
>
> Ugh!
>
> Michael Scott: NOoooooooo!!
>
> By the way, it looks like all of the sites reporting summary Gap
> stats had high numbers of Gap messages today:
>
> Oh my!
>
> The fact that everyone had high numbers means we can not
> conclusively say you actually need that filter, there is clearly
> something else going on at a larger scale. While the timing of that
> 5G tower going live is _super_ coincidental with your issues,
> today's numbers for everyone is even **more** coincidental IMO.
>
> I'm not arguing against getting a better filter if you need to, if
> it improves your signal it could be worth it. But I am VERY
> interested to see tomorrow's numbers... It's not solar
> interference season, (ponders) what could have caused this??
>
> re:
> > I have begun the process of getting a much better 5G filter, and
> > getting it installed.
>
> Please share with everyone CCed specifics of the 5G filter you
> go with including manufacturer, cost, relevant specs, and ordering
> lead time.
>
> Seconded, please and thank you!
>
> Best,
>
> -Mike
>
> *Mike Zuranski*
>
> Data Engineer II
>
> Unidata Program Center
>
> University Corporation for Atmospheric Research
>
>
>
> This message and its attachments may contain legally privileged or
> confidential information. It is intended solely for the named
> addressee(s). If you are not an addressee indicated in this message (or
> responsible for delivery of the message to an addressee), you may not
> copy or deliver this message or its attachments to anyone. Rather, you
> should permanently delete this message and its attachments and kindly
> notify the sender by reply e-mail. Any content of this message and its
> attachments that does not relate to the official business of Fox
> Corporation, or its subsidiaries must be taken not to have been sent or
> endorsed by any of them. No representation is made that this email or
> its attachments are without defect.
--
+----------------------------------------------------------------------+
* Tom Yoksas UCAR Unidata Program *
* (303) 497-8642 (last resort) P.O. Box 3000 *
* address@hidden Boulder, CO 80307 *
* Unidata WWW Service http://www.unidata.ucar.edu/ *
+----------------------------------------------------------------------+
|
