Copy Transcript
Copied
WEBVTT 00:00:12.240 --> 00:00:18.460 Supra 89 .7. This is a particular station that 00:00:18.460 --> 00:00:22.179 if you've been on Facebook and any of the Facebook 00:00:22.179 --> 00:00:26.339 radio engineering groups, you know very well 00:00:26.339 --> 00:00:32.649 who Supra 89 .7 is and WFAG LP out of Georgia. 00:00:33.149 --> 00:00:35.549 You know what station I'm talking about. But 00:00:35.549 --> 00:00:38.229 for the rest of you who may not be into the radio 00:00:38.229 --> 00:00:42.789 nerd cult that is radio engineering, Super 89 00:00:42.789 --> 00:00:48.229 .7 has a real interference problem. That's exactly 00:00:48.229 --> 00:00:51.990 why watching this station dismiss engineers accusing 00:00:51.990 --> 00:00:56.229 people of intentionally jamming their LPFM station 00:00:56.229 --> 00:01:00.000 and spamming the same argument across various 00:01:00.000 --> 00:01:04.959 radio Facebook groups is beyond frustrating at 00:01:04.959 --> 00:01:08.420 this point. Now, I'm going to start off by saying 00:01:08.420 --> 00:01:12.189 the physics isn't The the part that's unclear 00:01:12.189 --> 00:01:15.930 here. This has gone way beyond explaining how 00:01:15.930 --> 00:01:18.430 radio propagation works But we're gonna try to 00:01:18.430 --> 00:01:23.409 do that in a little bit. I have a bad habit of 00:01:23.409 --> 00:01:27.439 opening Facebook radio groups when I already 00:01:27.439 --> 00:01:32.370 know better Sometimes you learn something Sometimes 00:01:32.370 --> 00:01:34.750 somebody posts the picture of a transmitter that 00:01:34.750 --> 00:01:37.109 looks like it survived the small electrical fire 00:01:37.109 --> 00:01:40.069 and ask You know if the burn marks are normal 00:01:40.939 --> 00:01:45.629 And sometimes you get the same argument posted 00:01:45.629 --> 00:01:53.739 over and over and over and over again after multiple, 00:01:54.939 --> 00:02:00.099 multiple broadcast engineers have already explained 00:02:00.099 --> 00:02:05.239 what is happening. Fair warning, I'm a little 00:02:05.239 --> 00:02:09.389 over this one. We're talking about again, Super 00:02:09.389 --> 00:02:15.930 89 .7 WFAG LP out of Valdosta, Georgia. And usual 00:02:15.930 --> 00:02:18.009 disclaimer before I get any further. These are 00:02:18.009 --> 00:02:20.750 going to be my opinions. I'm as always speaking 00:02:20.750 --> 00:02:22.789 for myself. Everything here is from my point 00:02:22.789 --> 00:02:26.129 of view. This is the Tyler Woodward project. 00:02:26.530 --> 00:02:28.849 I'm Tyler. I'm a broadcast engineer in the upper 00:02:28.849 --> 00:02:34.250 Midwest. Hey, how you doing? And today we're 00:02:34.250 --> 00:02:38.909 going to explain that atmospheric propagation 00:02:38.909 --> 00:02:42.129 is not some conspiracy against your radio station. 00:02:43.860 --> 00:02:45.680 I never thought I would have to explain that, 00:02:45.680 --> 00:02:51.469 but here we are. Supra 89 .7 has an actual real 00:02:51.469 --> 00:02:56.610 problem. Nobody's disagreeing with that. I want 00:02:56.610 --> 00:03:01.009 to establish that first, that they do in fact 00:03:01.009 --> 00:03:03.490 have a real problem because I don't want this 00:03:03.490 --> 00:03:09.629 turned into, oh, you just hate LPFMs. No, actually, 00:03:09.689 --> 00:03:12.789 I like LPFMs. LPFMs have a place on the dial. 00:03:13.289 --> 00:03:17.469 I'm not arguing that point. WFAG LP is running 00:03:17.469 --> 00:03:24.550 100 watts on 89 .7 in Valdosta, Georgia. Radio 00:03:24.550 --> 00:03:28.009 World reported earlier this year that the station 00:03:28.009 --> 00:03:30.669 has been dealing with interference from WUSF 00:03:30.669 --> 00:03:34.639 in Tampa. And during sporadic e -skips, you know, 00:03:34.719 --> 00:03:37.400 little openings, WGBH in Boston comes through. 00:03:38.770 --> 00:03:42.509 That's frustrating. You know, I get it. If I'm 00:03:42.509 --> 00:03:46.439 trying to run a little community radio station 00:03:46.439 --> 00:03:49.520 and suddenly another station over 200 miles away, 00:03:49.900 --> 00:03:52.969 is eating into my signal, yeah, I'm gonna be 00:03:52.969 --> 00:03:58.030 a little pissed off too. Now, Supra 89 .7, they've 00:03:58.030 --> 00:04:03.770 already moved from 103 .7 to 89 .7 after interference 00:04:03.770 --> 00:04:08.770 problems on the previous frequency. So this isn't 00:04:08.770 --> 00:04:11.819 a new thing for them. And yes, the problem is 00:04:11.819 --> 00:04:17.610 real. The BS starts with what they've decided 00:04:17.610 --> 00:04:24.310 the explanation must be. The station has repeatedly 00:04:24.470 --> 00:04:29.230 questioned whether this is actually tropoducting 00:04:29.230 --> 00:04:33.730 or sporadic e -skip. Radio World quoted their 00:04:33.730 --> 00:04:37.389 general manager describing a quote, serious, 00:04:37.470 --> 00:04:41.029 suspicious phenomenon apparently ducting and 00:04:41.029 --> 00:04:44.750 raising the possibility of illegal broadcasting 00:04:44.750 --> 00:04:50.720 or some kind of human manipulation. Now, as you 00:04:50.720 --> 00:04:54.920 can imagine, Broadcast engineers responded. Michelle 00:04:54.920 --> 00:04:58.759 Bradley from REC networks told them what was 00:04:58.759 --> 00:05:04.300 happening. It's propagation. It's nature. 100 00:05:04.300 --> 00:05:08.319 watt LPFM. You know, it doesn't have a magical 00:05:08.319 --> 00:05:12.079 force field around its coverage area. And apparently, 00:05:13.329 --> 00:05:15.949 as you can expect, where I'm going with this, 00:05:16.860 --> 00:05:20.759 well, that answer wasn't good enough. Because 00:05:20.759 --> 00:05:25.389 now... We have an October 5th article from the 00:05:25.389 --> 00:05:31.879 radio station on their website that somehow Manages 00:05:31.879 --> 00:05:38.129 to go considerably further the article suggests 00:05:38.129 --> 00:05:42.110 that engineers at large companies I'm assuming 00:05:42.110 --> 00:05:46.670 large radio conglomerates is what they're referring 00:05:46.670 --> 00:05:49.470 to here, but you know engineers at large companies 00:05:49.470 --> 00:05:54.470 may be quote hacking ham radio equipment unquote 00:05:54.920 --> 00:06:05.779 to jam LPFM frequencies. It says ducting can't 00:06:05.779 --> 00:06:12.509 technically be proven. It calls scientific explanations 00:06:12.509 --> 00:06:18.509 fabricated theories. It says troppo forecast 00:06:18.509 --> 00:06:22.230 exists to deceive the radio broadcast community 00:06:22.290 --> 00:06:28.709 in the FCC. It suggests The interference could 00:06:28.709 --> 00:06:33.029 be some kind of relay intentionally designed 00:06:33.029 --> 00:06:40.569 to cause harm. It claims 99 % of LPFMs are intentionally 00:06:40.569 --> 00:06:44.209 being interfered with. Then it starts talking 00:06:44.209 --> 00:06:48.490 about federal crimes. What evidence is presented 00:06:48.490 --> 00:06:52.699 for any of that? Well, none that I can find. 00:06:53.959 --> 00:06:58.879 And that's a problem. Because once you start 00:06:59.540 --> 00:07:04.040 publicly accusing people of intentionally interfering 00:07:04.040 --> 00:07:09.449 with a licensed broadcast radio station and hacking 00:07:09.449 --> 00:07:12.269 equipment and deceiving the FCC and committing 00:07:12.660 --> 00:07:19.160 whatever federal crimes were not having an engineering 00:07:19.160 --> 00:07:23.480 disagreement anymore. Those are very serious 00:07:23.480 --> 00:07:30.579 accusations. You need evidence. I don't believe 00:07:30.579 --> 00:07:35.970 the engineers. That's not evidence. And this 00:07:35.970 --> 00:07:40.970 is the part that has been driving me up the freaking 00:07:40.970 --> 00:07:43.829 wall. Watching this spill over into the various 00:07:43.829 --> 00:07:48.649 radio Facebook groups. You post the problem. 00:07:49.490 --> 00:07:53.009 Broadcast engineers explain what is happening. 00:07:53.310 --> 00:07:56.949 They break the problem down for you. You don't 00:07:56.949 --> 00:08:00.360 like the explanation. So you post it somewhere 00:08:00.360 --> 00:08:05.720 else and again Broadcast engineers take the time 00:08:05.720 --> 00:08:09.519 to explain the same thing outside of their normal 00:08:09.519 --> 00:08:12.680 work hours Just trying to help out another radio 00:08:12.680 --> 00:08:15.860 station because believe it or not The broadcast 00:08:15.860 --> 00:08:18.620 engineering community were not the biggest group 00:08:18.620 --> 00:08:20.939 anymore. There's not a whole lot of us left out 00:08:20.939 --> 00:08:25.319 there We do in fact like helping other radio 00:08:25.319 --> 00:08:32.960 stations out. I mean They're gone. They tried 00:08:32.960 --> 00:08:40.889 So, you know again more engineers explain what 00:08:40.889 --> 00:08:44.629 is happening and they don't like that explanation 00:08:44.629 --> 00:08:49.299 either now eventually the engineers explaining 00:08:49.299 --> 00:08:53.919 basic RF propagation somehow Have become part 00:08:53.919 --> 00:08:58.570 of the story at some point You aren't asking 00:08:58.570 --> 00:09:02.120 for technical help anymore You're looking for 00:09:02.120 --> 00:09:06.730 somebody out there to validate the conclusion 00:09:06.730 --> 00:09:10.779 you've already reached in your head. And that 00:09:10.779 --> 00:09:20.440 is not engineering anymore. Now here's the especially 00:09:20.440 --> 00:09:25.049 bizarre part. Tropoducting isn't some obscure 00:09:25.049 --> 00:09:28.409 theory a couple of radio nerds invented because 00:09:28.409 --> 00:09:31.029 they wanted to pick on an LPFM station down in 00:09:31.029 --> 00:09:36.389 Georgia. The International Telecommunication 00:09:36.389 --> 00:09:40.570 Union has an entire recommendation dealing with 00:09:40.570 --> 00:09:45.169 the effects of, you know, tropoducting and radio 00:09:45.169 --> 00:09:48.549 propagation problems. It defines the conditions 00:09:48.549 --> 00:09:54.149 under which these ducting events form. It's a 00:09:54.149 --> 00:09:57.990 meteorological weather event. It happens. But, 00:09:58.029 --> 00:10:02.120 you know, it also explains how radio signals 00:10:02.120 --> 00:10:06.559 can travel far beyond the normal line of sight. 00:10:07.639 --> 00:10:11.549 It specifically discusses the interference those 00:10:11.549 --> 00:10:16.519 signals can create. The FCC even builds this 00:10:16.519 --> 00:10:25.399 into how it predicts interference. It knows radio 00:10:25.399 --> 00:10:30.899 signals don't behave exactly the same every hour 00:10:30.899 --> 00:10:36.070 of every day throughout the year. Sometimes a 00:10:36.070 --> 00:10:39.049 distant station gets stronger and reaches much 00:10:39.049 --> 00:10:44.379 farther than usual. That's normal enough that 00:10:44.379 --> 00:10:49.700 the FCC accounts for it in its engineering. The 00:10:49.700 --> 00:10:54.779 atmosphere changes. Signals can change with it. 00:10:55.340 --> 00:11:00.450 This isn't new. Any engineer who has worked around 00:11:00.450 --> 00:11:03.889 VHF for long enough has watched this happen. 00:11:04.730 --> 00:11:08.509 Hell, anybody who has done FMDXing has watched 00:11:08.509 --> 00:11:16.169 this happen. And WGBH showing up from Boston 00:11:16.169 --> 00:11:20.250 isn't even the same propagation mode as WUSF 00:11:20.250 --> 00:11:27.299 coming up from Tampa. A roughly thousand mile 00:11:27.299 --> 00:11:32.080 opening on the lower end of the FM band is completely 00:11:32.080 --> 00:11:36.769 consistent with sporadic -y different mechanism. 00:11:37.190 --> 00:11:42.559 Still not somebody hiding in a van with a hacked 00:11:42.559 --> 00:11:48.299 ham radio setup. There is Also, an actual federal 00:11:48.299 --> 00:11:52.960 law against willful or malicious interference. 00:11:53.769 --> 00:12:01.919 47, USC, section 333. The important words are 00:12:02.149 --> 00:12:09.440 willfully or maliciously. A licensed radio station 00:12:09.440 --> 00:12:11.860 operating normally does not commit a federal 00:12:11.860 --> 00:12:14.440 crime because atmospheric conditions carry its 00:12:14.440 --> 00:12:20.309 signal a little further that day. WUSF isn't 00:12:20.309 --> 00:12:22.950 sitting in Tampa turning the atmosphere knob 00:12:22.950 --> 00:12:30.840 toward Valdosta, and LPFM has another uncomfortable 00:12:30.840 --> 00:12:36.919 reality built into its service. LPFM is a secondary 00:12:36.919 --> 00:12:41.980 service. The local community radio act explicitly 00:12:41.980 --> 00:12:48.370 says LPFM stations, translators, and boosters 00:12:48.370 --> 00:12:54.279 remain secondary to existing and modified full 00:12:54.279 --> 00:13:00.059 service FM stations. That doesn't mean LPFM is 00:13:00.059 --> 00:13:05.419 worthless. It doesn't mean an LPFM operator should 00:13:05.419 --> 00:13:08.620 just accept every interference problem without 00:13:08.620 --> 00:13:13.299 investigating it. It means the regulatory structure 00:13:13.299 --> 00:13:16.440 does not guarantee that your little 100 watt 00:13:16.519 --> 00:13:21.259 signal gets to win every fight with a full -blown, 00:13:21.259 --> 00:13:27.779 full -power station. Those are very different 00:13:27.779 --> 00:13:32.639 things. And if the interference isn't propagation, 00:13:32.759 --> 00:13:36.860 great. Prove it. Put a receiver on the frequency. 00:13:37.480 --> 00:13:41.600 Log signal levels. Record the RDS pi codes. Put 00:13:41.600 --> 00:13:47.799 a directional antenna on it. Take bearings. Coerulate. 00:13:49.000 --> 00:13:53.759 the interference with weather conditions. Compare 00:13:53.759 --> 00:13:57.620 what happens during predicted tropo openings. 00:13:59.309 --> 00:14:04.029 I mean, if you think somebody has built an illegal 00:14:04.029 --> 00:14:09.159 transmitter nearby specifically to relay WUSF 00:14:09.159 --> 00:14:12.730 Tampa over your signal, that should be measurable. 00:14:13.590 --> 00:14:17.960 Find it. Document it. Give the FCC something 00:14:17.960 --> 00:14:21.529 they can actually investigate. I would take that 00:14:21.529 --> 00:14:26.070 seriously if you had the documentation, the data 00:14:26.070 --> 00:14:30.980 to back it up. What I won't take seriously is 00:14:30.980 --> 00:14:34.460 accusing broadcast radio engineers of participating 00:14:34.460 --> 00:14:37.139 in some deliberate campaign because they gave 00:14:37.139 --> 00:14:41.480 you an answer you didn't like or didn't want 00:14:43.269 --> 00:14:45.970 or didn't go with whatever you made up in your 00:14:45.970 --> 00:14:50.399 head. Their October article even singles out 00:14:50.370 --> 00:14:53.710 broadcast engineer Paul Walker Jr. calling him 00:14:53.710 --> 00:14:58.620 the bully man of LPFM radio and describing a 00:14:58.620 --> 00:15:02.519 comment about the station being blasted out as 00:15:02.519 --> 00:15:08.210 part of a smear campaign. Now, obviously I couldn't 00:15:08.210 --> 00:15:11.929 verify any smear campaign. What I can verify 00:15:11.929 --> 00:15:15.070 is that the station published the acquisition. 00:15:16.779 --> 00:15:19.740 And that's where this goes from irritating to 00:15:19.740 --> 00:15:25.070 irresponsible. You don't get to ask engineers 00:15:25.070 --> 00:15:29.090 what's happening, reject the engineering, accuse 00:15:29.090 --> 00:15:32.210 people of intentionally attacking you, and then 00:15:32.210 --> 00:15:35.970 complain that the engineering, the radio engineering 00:15:35.970 --> 00:15:41.279 community isn't taking you seriously. How exactly 00:15:41.279 --> 00:15:45.730 is that supposed to work? Now the stupid thing 00:15:45.730 --> 00:15:51.250 is, Supra 89 .7 could be having a much more useful 00:15:51.250 --> 00:15:56.070 conversation. Is 100 watts enough for some LPFM 00:15:56.070 --> 00:16:00.370 facilities and areas prone to enhanced propagation? 00:16:02.129 --> 00:16:06.730 Should the FCC revisit LPFM power levels? Would 00:16:06.730 --> 00:16:12.629 SOMEBODY or would SOMETHING like the proposed 00:16:12.629 --> 00:16:18.100 LP250 class help? Could the station improve antenna 00:16:18.100 --> 00:16:22.990 height or its antenna system? Are there receiver 00:16:22.990 --> 00:16:27.289 issues involving HD capture that deserves investigation? 00:16:29.019 --> 00:16:34.620 Those are real questions. Those are engineering 00:16:34.620 --> 00:16:39.460 questions. Those are policy questions. Those 00:16:39.460 --> 00:16:46.720 are common sense questions. There are engineers 00:16:46.720 --> 00:16:50.039 who would probably be happy to help answer. All 00:16:50.039 --> 00:16:54.679 of this for them. But you have to actually listen 00:16:54.679 --> 00:17:02.159 when they answer. You don't get to replace propagation 00:17:02.159 --> 00:17:05.079 with conspiracy theories because propagation 00:17:05.079 --> 00:17:09.279 is inconvenient for the argument. And you definitely 00:17:09.279 --> 00:17:12.480 shouldn't accuse people of federal crimes because 00:17:12.480 --> 00:17:16.259 Mother Nature has better coverage than you do. 00:17:18.359 --> 00:17:22.869 Again, the interference is real. The frustration 00:17:22.869 --> 00:17:27.160 is real. The conspiracy theory isn't supported 00:17:27.160 --> 00:17:33.390 by any measurable Evidence. Stop spamming Facebook 00:17:33.390 --> 00:17:36.359 groups looking for a different answer. Start 00:17:36.359 --> 00:17:41.940 documenting the signal. That's the show. If you 00:17:41.940 --> 00:17:43.940 want to keep up with it, subscribe wherever you're 00:17:43.940 --> 00:17:46.380 listening, Apple Podcasts, Spotify, iHeart, TuneIn, 00:17:46.380 --> 00:17:48.720 all of the various ones, and you can find everything 00:17:48.720 --> 00:17:52.160 else, the socials, everything, little tools at 00:17:52.160 --> 00:17:55.150 tylerwoodward .me. If you want to buy me a cup 00:17:55.150 --> 00:17:57.750 of coffee just to say thanks for what I do here 00:17:57.750 --> 00:17:59.849 for whatever reason, you can do that at tylerwoodward 00:17:59.849 --> 00:18:06.150 .me as well. And if you got thoughts 608 -668 00:18:06.150 --> 00:18:09.210 -4702 you can leave a voicemail or email Tyler 00:18:09.210 --> 00:18:13.410 at tylerwoodward .me I'll catch you next time