Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RFI\]\s+80\s+meters\s+RFI\s+at\s+N9CJT\s+tracked\s+down\s+to\s+an\s+AT\&T\s+line\s+\(probably\s+VDSL\)\s*$/: 14 ]

Total 14 documents matching your query.

1. [RFI] 80 meters RFI at N9CJT tracked down to an AT&T line (probably VDSL) (score: 1)
Author: Don Kirk <wd8dsb@gmail.com>
Date: Sun, 10 Sep 2023 09:03:31 -0400
I was asked to help locate the source of RFI at N9CJT and yesterday we tracked down/identified the source to be from an AT&T (formerly Ameritech) system and all indications are that the system is VDS
/archives//html/RFI/2023-09/msg00015.html (7,950 bytes)

2. Re: [RFI] 80 meters RFI at N9CJT tracked down to an AT&T line (probably VDSL) (score: 1)
Author: AA5CT via RFI <rfi@contesting.com>
Date: Sun, 10 Sep 2023 13:34:00 +0000 (UTC)
ATT "U-Verse" service perhaps? I had straight ATT DSL, the original 3 MBit offering years back starting about 2010, and all energy was below 160 meters even (I work 160 from this small lot and the te
/archives//html/RFI/2023-09/msg00016.html (9,111 bytes)

3. Re: [RFI] 80 meters RFI at N9CJT tracked down to an AT&T line (probably VDSL) (score: 1)
Author: Alan Higbie <alan.higbie@gmail.com>
Date: Sun, 10 Sep 2023 10:09:24 -0600
Dons approach in this case is a good example of first focusing on WHERE IT IS. Imagine how much time they saved by simply locating and sniffing out the source. Trying to determine WHAT IT WAS by look
/archives//html/RFI/2023-09/msg00017.html (9,479 bytes)

4. Re: [RFI] 80 meters RFI at N9CJT tracked down to an AT&T line (probably VDSL) (score: 1)
Author: "Dave (NK7Z)" <dave@nk7z.net>
Date: Sun, 10 Sep 2023 09:19:32 -0700
Hi, I must agree with Alan here... One of the first steps, ahead of WHAT, should be WHERE... This was a great example of RFI sleuthing! Well done! 73, and thanks, Dave (NK7Z) https://www.nk7z.net ARR
/archives//html/RFI/2023-09/msg00018.html (9,652 bytes)

5. Re: [RFI] 80 meters RFI at N9CJT tracked down to an AT&T line (probably VDSL) (score: 1)
Author: Jim Brown <jim@audiosystemsgroup.com>
Date: Sun, 10 Sep 2023 12:05:23 -0700
I strongly disagree. The FIRST thing we should do in chasing noise is to determine whether it is impulse noise (mostly power line) or electronic noise, of which this is an example. Once that is deter
/archives//html/RFI/2023-09/msg00019.html (8,815 bytes)

6. Re: [RFI] 80 meters RFI at N9CJT tracked down to an AT&T line (probably VDSL) (score: 1)
Author: "Dave (NK7Z)" <dave@nk7z.net>
Date: Sun, 10 Sep 2023 12:58:30 -0700
Hi, Link to 24 hour recording methods... https://www.nk7z.net/sdr-rfi-survey-p1/ 73, and thanks, Dave (NK7Z) https://www.nk7z.net ARRL Volunteer Examiner ARRL Technical Specialist, RFI ARRL Asst. Dir
/archives//html/RFI/2023-09/msg00020.html (9,667 bytes)

7. Re: [RFI] 80 meters RFI at N9CJT tracked down to an AT&T line (probably VDSL) (score: 1)
Author: Don Kirk <wd8dsb@gmail.com>
Date: Sun, 10 Sep 2023 17:32:47 -0400
Hi Jim and gang. I think everyone here is right. The point being that it really is most important to track down what property the RFI is originating from and then you can figure out exactly what devi
/archives//html/RFI/2023-09/msg00021.html (11,415 bytes)

8. Re: [RFI] 80 meters RFI at N9CJT tracked down to an AT&T line (probably VDSL) (score: 1)
Author: Jim Brown <jim@audiosystemsgroup.com>
Date: Sun, 10 Sep 2023 15:13:41 -0700
Don, I absolutely agree that your tools and methods for tracking are spot on. Those who take the time to study NK7Z's webpage will learn that "that kind of technology" is nothing more than a basic SD
/archives//html/RFI/2023-09/msg00022.html (9,326 bytes)

9. Re: [RFI] 80 meters RFI at N9CJT tracked down to an AT&T line (probably VDSL) (score: 1)
Author: "Jeff \(W4DD\)" <w4dd09@gmail.com>
Date: Mon, 11 Sep 2023 09:53:45 -0400
FYI, Tracked a VDSL problem a year or two ago which seemed confusing at the time (was actually 2 DSL sources). Figured it was DSL as it had a strong increase in strength at 3.750MHz (this is where th
/archives//html/RFI/2023-09/msg00023.html (10,057 bytes)

10. Re: [RFI] 80 meters RFI at N9CJT tracked down to an AT&T line (probably VDSL) (score: 1)
Author: Don Kirk <wd8dsb@gmail.com>
Date: Thu, 5 Oct 2023 09:26:57 -0400
Here is followup & resolution regarding the RFI we tracked down about 3.5 weeks ago at the QTH of N9CJT that we suspected was DSL/VDSL as we had identified the RFI was coming from a box and associate
/archives//html/RFI/2023-10/msg00000.html (12,863 bytes)

11. Re: [RFI] 80 meters RFI at N9CJT tracked down to an AT&T line (probably VDSL) (score: 1)
Author: Michael Carter <Mike.Carter@unh.edu>
Date: Thu, 5 Oct 2023 13:32:13 +0000
Thanks for the detailed update, Don. It is a bit intimidating to think that resolution of similar RFI issues might require high-level intervention at the level of a major corporation's president's of
/archives//html/RFI/2023-10/msg00001.html (16,710 bytes)

12. Re: [RFI] 80 meters RFI at N9CJT tracked down to an AT&T line (probably VDSL) (score: 1)
Author: Pete Smith N4ZR <pete.n4zr@gmail.com>
Date: Thu, 5 Oct 2023 10:13:09 -0400
Sounds like AT&T knows it has a problem with responsiveness, to have set up such an intervention mechanism.  Good to see. 73, Pete N4ZR It is a bit intimidating to think that resolution of similar RF
/archives//html/RFI/2023-10/msg00002.html (17,003 bytes)

13. Re: [RFI] 80 meters RFI at N9CJT tracked down to an AT&T line (probably VDSL) (score: 1)
Author: Jim Brown <jim@audiosystemsgroup.com>
Date: Thu, 5 Oct 2023 09:41:38 -0700
"Criminal" is the right word. This is a violation of Federal Law. 73, Jim K9YC _______________________________________________ RFI mailing list RFI@contesting.com http://lists.contesting.com/mailman/
/archives//html/RFI/2023-10/msg00003.html (8,003 bytes)

14. Re: [RFI] 80 meters RFI at N9CJT tracked down to an AT&T line (probably VDSL) (score: 1)
Author: Steve London <n2icarrl@gmail.com>
Date: Thu, 5 Oct 2023 11:24:29 -0600
Apparently, a customer didn't know that he had no internet service, since his router couldn't sync up ? I wonder how much AT&T was charging for that ? 73, Steve, N2IC ________________________________
/archives//html/RFI/2023-10/msg00004.html (14,978 bytes)


This search system is powered by Namazu