Mark Could it be some joe off the streets installed equipment and didn't know the settings like somebody took and used ubiquiti stuff and loaded openwrt or something? Do they know if its an wisp or not?
Tim On 2020-08-19 19:45, Mark Radabaugh wrote: > There have been several incidents including one to the south that they > were able to locate (not a WISP fortunately). The FCC has not found > the one to the NW yet. > > Mark > >> On Aug 19, 2020, at 3:19 PM, spierce <[email protected]> wrote: >> >> I was told the interference was SE of the radar site. >> >> -------- Original message -------- >> From: Mark Radabaugh <[email protected]> >> Date: 8/19/20 2:51 PM (GMT-05:00) >> To: [email protected] >> Subject: Re: [Ohio] TDWR Interference Investigation >> >> Hopefully this is clearer: >> >> On Aug 19, 2020, at 2:41 PM, spierce <[email protected]> wrote: >> North of what? >> >> -------- Original message -------- >> From: Mark Radabaugh <[email protected]> >> Date: 8/19/20 2:33 PM (GMT-05:00) >> To: [email protected] >> Subject: [Ohio] Fwd: TDWR Interference Investigation >> >> This is a better example of the noise that the radar at Columbus is >> seeing. It’s actually a bit farther north than was previously >> described: >> >> Mark >> >> Begin forwarded message: >> From: Albert Furlow <[email protected]> >> >> Subject: RE: [Ohio] TDWR Interference Investigation >> >> Date: August 19, 2020 at 2:24:08 PM EDT >> >> To: Mark Radabaugh <[email protected]> >> >> Regards, >> Albert Furlow >> Electronics Engineer >> Columbia Field Office >> FCC Enforcement Bureau >> [email protected] >> 301-725-0122 Office >> 202-391-1847 Cell >> >> From: Mark Radabaugh <[email protected]> >> Sent: Wednesday, August 19, 2020 2:21 PM >> To: Albert Furlow <[email protected]> >> Subject: Fwd: [Ohio] TDWR Interference Investigation >> >> Begin forwarded message: >> >> From: Mark Radabaugh <[email protected]> >> >> Subject: Re: [Ohio] TDWR Interference Investigation >> >> Date: August 19, 2020 at 2:18:46 PM EDT >> >> To: [email protected] >> >> Cc: [email protected] >> >> Reply-To: [email protected] >> >> As head of the policy committee I would like to emphasize how >> serious this matter is. THIS IS VERY IMPORTANT that this >> interference be found and stopped! >> >> About 4 years ago WISP’s came VERY close to losing high power >> operation in the entire lower half of the UNI-III band when the FAA >> went to the NTIA who went to the FCC to deal with interference to >> the terminal dopler weather radar system. This system is used to >> warn aircraft of wind shear during takeoff and landing. The >> proposed rules greatly tightened the out of band limits at the edge >> of the UNI-III 5720Mhz-5850Mhz to the point that very few >> manufacturers would be able to build a radio at a reasonable cost to >> operate outdoors. >> >> WISP’s came very close to losing one of our best tools due to this >> issue. We narrowly avoided it with considerable effort from WISPA, >> many manufacturers, and many WISP’s. Credit is also due to >> Ubiquiti for the compromise proposal that the FCC ultimately >> accepted. >> >> None of us can afford further black eyes over interference with >> TDWR. If you are operating between 5600 and 5650Mhz please make >> sure you are following the rules on operation in the DFS space, are >> operating at appropriate power levels, and are not aiming at TDWR >> sites. >> >> This appears to be more than 60 miles out. This is the best map of >> the interference that I have been able to find to date. I added >> the red line showing the interference direction: >> >> Please check your systems to make sure they are not the source of >> this interference! >> >> As an added incentive - if and when the FCC tracks the interference >> down the minimum fine starts at $20,000 and goes up. And as an >> added bonus you are presumed guilty and have to spend a bunch of >> money on lawyers to defend yourself. You also end up with a >> ‘compliance plan’ that involves a whole lot of reporting and >> other fun for years to come. >> >> Mark Radabaugh >> >> WISPA >> >> On Aug 19, 2020, at 11:48 AM, Todd Harpest <[email protected]> >> wrote: >> >> Ohio WISPs: >> >> We received an email from the Ohio contact regarding a TDWR >> interference investigation which they are looking into. While we >> checked our equipment and everything looks good, I thought it in the >> best interest of WISPs to forward his contact information should you >> need it as well as to be aware of our responsibilities to DFS in the >> 5 GHz frequencies. >> >> Here are his details of the issue at hand: >> >> I am investigating a strobe that is affecting the Glen John airport >> and I am requesting your assistants on this matter. This signal is >> emitting in the 5600 to 5650 MHz TDWR operation band. Being this is >> an out each attempt to try and resolve this matter remotely, I am >> asking for your team to review your DFS setting on your system. The >> strobe starts near the John Glen airport, Columbus and tracks >> to/near West unity, Oh., Frontier, Mi., direction. >> >> I used the National Broadband Map to locate the WISP operators near >> these areas and I am aware that there are more operators in the area >> that are not listed. >> >> The FCC tiger teams has tracked WISP signals beyond 60 miles that >> have affected TDWR systems. >> >> I would also am providing my contact information for any questions >> you might have and to have someone from your team contact me . >> >> Regards, >> >> Albert Furlow >> >> Electronics Engineer >> >> Columbia Field Office >> >> FCC Enforcement Bureau >> >> [email protected] >> >> 301-725-0122 Office >> >> 202-391-1847 Cell >> >> Thanks, >> >> Todd Harpest, _External Affairs & Regulatory Director_ >> >> Technologies, Inc. >> >> 419.990.0310 | 888.999.8002 x2310 >> >> [email protected] | www.metalink.net [1] >> >> <image001.png> >> >> _______________________________________________ >> Ohio mailing list >> [email protected] >> http://lists.wispa.org/mailman/listinfo/ohio [2] >> >> _______________________________________________ >> Ohio mailing list >> [email protected] >> http://lists.wispa.org/mailman/listinfo/ohio > > _______________________________________________ > Ohio mailing list > [email protected] > http://lists.wispa.org/mailman/listinfo/ohio > _______________________________________________ > Ohio mailing list > [email protected] > http://lists.wispa.org/mailman/listinfo/ohio > > > > Links: > ------ > [1] > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.metalink.net_&d=DwMFaQ&c=y0h0omCe0jAUGr4gAQ02Fw&r=L1637o2LkCzm7ne_WR06lL3_glyl6U7SSs5-WwlPQ7U&m=YAMf2yNxLZQYrkqorIn4vKd7XC_F0R7Q6LnZfq4Lbd0&s=YVKXUDSpsaFPek1_yNkvZAvs1Aj-TCN4acdYk62cbe8&e= > [2] > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.wispa.org_mailman_listinfo_ohio&d=DwMFaQ&c=y0h0omCe0jAUGr4gAQ02Fw&r=L1637o2LkCzm7ne_WR06lL3_glyl6U7SSs5-WwlPQ7U&m=YAMf2yNxLZQYrkqorIn4vKd7XC_F0R7Q6LnZfq4Lbd0&s=-uiD9-CLYDrvKILpiyKZiFfRgq7lGlH6Gx1y6Q0DjO8&e= > _______________________________________________ > Ohio mailing list > [email protected] > http://lists.wispa.org/mailman/listinfo/ohio _______________________________________________ Ohio mailing list [email protected] http://lists.wispa.org/mailman/listinfo/ohio
