Blitzortung.org Forum
SOLVED: Identifying interference with oscilloscopes and software-defined radio - Printable Version

+- Blitzortung.org Forum (https://forum.blitzortung.org/mybb)
+-- Forum: Public Forums (https://forum.blitzortung.org/mybb/forumdisplay.php?fid=29)
+--- Forum: Hardware, Software, Lightning Physics (https://forum.blitzortung.org/mybb/forumdisplay.php?fid=30)
+--- Thread: SOLVED: Identifying interference with oscilloscopes and software-defined radio (/showthread.php?tid=2260)

Pages: 1 2 3

SOLVED: Identifying interference with oscilloscopes and software-defined radio - djhuft - 2017-08-06

Hello,

I run station #1500 and am trying to reduce local RF interference so that my receiver performs better. My station statistics suggest that I am receiving lots of interference, so I have been trying to identify and hopefully eliminate some of them. I live in a row of apartment buildings, so I have many neighbors with lots of  electrical equipment. Finding and fixing everything will be nearly impossible.

There has been much written on interference, particularly this thread: http://www.wxforum.net/index.php?topic=20439.0.

I previously used my System Blue's web interface for trying to diagnose interference, it was poorly suited for the task. The time-domain signals that it displayed could not give me any frequency information, and also were not useful for tracking the interference over long time periods. Therefore, I am documenting two methods I found to be much more powerful and insightful.

Oscilloscope Method
Earlier in the summer, I was using an oscilloscope to examine the signals that my System Blue was receiving. I soldered the four optional SMA connectors to the PCB (1). These connectors provide access each of the four amplified antenna signals. I connected these signals to my oscilloscope (2) and used the scope's FFT mode to view their frequency spectrum. From this, I was able to identity several spurious frequencies.

After a lengthy process of elimination, I found that one very significant source of interference was the network switch that my receiver was connected to. It was a large 24 port TP-Link Gigabit Ethernet switch, and it was actually conducting the interference through the Ethernet cable into my receiver. I solved this problem by instead connecting my receiver to a port on one of my WiFi routers. Apparently, that router was less noisy than the network switch and did not tend to conduct noise through its Ethernet jacks.

After fixing this, I still had a few sources of interference. I still received a constant signal at 25 kHz and a flickering one at 60 kHz. I tried turning every piece of electrical equipment in my apartment off, but the interference was still there..


Software Defined Radio Method
After much experimentation, I stumbled upon an even better way to troubleshoot the interference. Basically, it involves connecting an inexpensive software-defined radio (SDR) dongle to my receiver, and viewing the received signals on a PC. Similar to the oscilloscope method above, you must install the optional SMA jacks on your System Blue board and connect the dongle to them (3).

I am using an R820T2 RTL-SDR dongle (approx $20). This particular model is capable of receiving between 24 – 1766 MHz, which is obviously not the correct frequency range.

To receive the low-frequency signals that I am interested in, I use the Ham It Up Upconverter. This is connected between the System Blue and the RTL-SDR dongle. It shifts its input signals up in frequency by 125 MHz, where they can then be received by the RTL-SDR dongle. (4)

The final thing required is software to view the signals. I am using GQRX (5). It has an instantaneous frequency display, similar to the FFT plot on my oscilloscope. More importantly, it has a nice waterfall display that allows me to view the received frequencies as they change over time. The time scale on the waterfall can be adjusted from a few seconds to many hours, which is extremely useful.

LED Lighting Causing Interference
Here is a short capture that I took while turning on and off a fixture with six LED light bulbs. The timescale of the waterfall is about 30 seconds. The area circled in red, just above 70 kHz, shows emissions that appeared each time I switched the bulbs on. Perhaps I should find different bulbs, or switch to incandescent.
[Image: HrWa0it.png]


Long Time Spans
Here is a very long capture that I made starting late at night. In this case, the time scale on the waterfall is 10 hours! Notice the increased emissions near the top of the waterfall. These appear at about 8:00 and 9:20 AM. One might suspect that they might be caused by my neighbors switching on electrical devices after getting up in the morning. I was still sleeping at the time, so I could not have caused them.
[Image: 9xCkKwH.png]
Also note that there are significant emissions at 25 kHz and 60 kHz. These are the signals that I originally identified using my oscilloscope! They seem to be present all the time.

Conclusion
I still have not found the source of my two main interfering signals, but in the process of searching for them I think I developed some useful and powerful methods for investigating interference. Hopefully others will find this information useful.

If anybody has questions or wants clarifications on anything I discussed, please ask. I'll try to post more screenshots if I find any other interesting interfering signals.

Footnotes:

(1): Mentioned in the "Digital filter option" section of the assembly instructions
(2): Be sure to switch your station to fixed gains, not "automatic mode" if you want to make measurements, otherwise you will see sudden changes in signal amplitude whenever the gain is automatically adjusted by the receiver's microcontroller.
(3): I drilled an extra hole into my receiver's case, then installed a small SMA cable from the connector on the PCB out to the outside of the case. This gives me a convenient connection for my experimentation without the need to open the case.
(4): Software-defined radio receivers have become extremely popular in the past several years, and many different models are available.  Other models should certainly be suitable, and some are able to receive signals below 1 MHz without the need for a separate up-converter.
(5): Similar programs exist for Windows, for example PothosSDR

RE: Identifying interference with oscilloscopes and software-defined radio - djhuft - 2017-08-06

Here is a photo of my test setup:
[Image: Yhe59au.jpg]

And here is a close-up of the connection that I added which connects to the internal amplifier:
[Image: CCIyL6p.jpg]

RE: Identifying interference with oscilloscopes and software-defined radio - djhuft - 2017-08-08

I recorded a bit more since last post. Keep in mind that you are seeing the spectrum between DC and 120 kHz.

10 hours of recording through the night:
[Image: WlwUPTI.png]

Another 10 hours from the daytime:
[Image: pNlYHpB.png]

There are lots of interesting signals here, in my opinion:
  • Both images: There is broadband interference across the spectrum periodically.
  • Both images: There is a signal that sometimes appears and drifts slowly from low 60 kHz range to steady-state above 70 kHz. Maybe this is some sort of thermal effect inside the interfering device?
  • Both images: The signals at 25 and 60 kHz are very strong and still present all the time.
  • Both images: There is a strong signal at 45 kHz that comes and goes.
  • Second image: There is a broadband interferer between 8 and 15 kHz that occasionally appears.

I'm not sure what to conclude...

The next time I am away from the apartment, I plan to shut off every circuit breaker, except for the one powering my laptop and Blitzortung receiver. Maybe some of these strange signals will disappear. If not, I probably need to look outside my apartment.

Also, maybe I should make a 5V battery backup for my Blitzortung receiver, then pray for a neighborhood-wide power outage.  Angel  I could get a lot of interesting data then!

RE: Identifying interference with oscilloscopes and software-defined radio - djhuft - 2017-08-08

One final experiment for the night...

I still have my software defined radio dongle connected to my Blitzortung receiver's amplifier output.
  1. I turned all the (LED) lights on in my apartment, and switched on as many gadgets and devices as possible (my PC, fans, radio).
  2. I powered my Blitzortung receiver from a USB battery pack.
  3. I disconnected my laptop charger (the laptop that I used to record this data)  from its outlet. The charger generates significant interference, which tends to confound my measurements.
  4. I set up my software-defined radio dongle and GQRX to record a waterfall plot that was five minutes long.

Then I started recording...

After a couple of minutes, I turned off all the circuit breakers in my house.
(Lower on the waterfall is earlier in time.)
[Image: F7YYhA7.png]
Lots of noise is eliminated, but not everything! Those pesky 25 kHz and 60 kHz signals are still there..

Next, I left everything off for a couple minutes, then I turned the breakers back on.
[Image: PdA3bmj.png]
You can see interesting emissions as my devices powered back up. I suspect that this coincided with routers booting up, etc.

RE: Identifying interference with oscilloscopes and software-defined radio - opadavis2 - 2017-08-08

Thank you for this information. I recently started up my Blue and am getting very poor signals on both E and H antennas. I already have 4 of 6 inch BNC to SMA cables coming in by mail and look forward to troubleshooting. I think I have room to mount all 4 BNC bulkhead connectors to the back panel. 
Peter

RE: Identifying interference with oscilloscopes and software-defined radio - pasense - 2017-08-08

You should consider to use the low pass filters. With them I could cut out the high frequency noise and could concentrate on hunting the noise sources around 10-30 kHz. Soldering the tiny filters in was far easier than I feared, but they are of course a bit expensive.

RE: Identifying interference with oscilloscopes and software-defined radio - Breitling - 2017-08-09

(2017-08-08, 19:58)pasense Wrote: You should consider to use the low pass filters. With them I could cut out the high frequency noise and could concentrate on hunting the noise sources around 10-30 kHz. Soldering the tiny filters in was far easier than I feared, but they are of course a bit expensive.

Hi pasense. I don't want to hijack this magnific thread, but I have doubts about soldering the low pass filters (I already have them). Any link or post where to see the PCB place and soldering tips?

Thanks !!

RE: Identifying interference with oscilloscopes and software-defined radio - pasense - 2017-08-09

Hi Breitling,
two answers: I took a quick lock at the signal from your station, and the major noise is at 15-16 kHz, so this cannot be removed by the filters. On the other hand, the smaller peak at 66 kHz can be suppressed. 
I used the following procedure to solder the filter ICs: First, I applied a bit of flux with a pen dispenser on the legs of the filters and on the pads on the board. The soldering iron had a flat tip of 4 mm width, like the tip of an old screwdriver. This tip then covers all 4 legs on one side of the package. The soldering iron was on a middle temperature, not on max and I wetted its tip only with a small amount of solder. Then I used a pincer to hold the filter at the two sides were there are no legs and placed them exactly on the pads on the board and pressed the legs on one side down with the flat tip of the soldering iron. The solder on the pads melted immediately and the legs moved down a bit. I then withdrew the soldering iron sideways, so there were to solder bridges between the legs and waited of few seconds until the solder had cooled down. Then I rotated the board and soldered the four legs on the other side. In this way I did'nt need a very fine tip, the broad one did even better, it allowed to solder all four legs in one go. The amount of solder which is already on the pads is sufficient to fix the filters and connect them. 
I should add that I am very short-sighted, so without my glasses I can see very good at short distances and I did'nt need a magnifying glass in order to control the whole operation. .

RE: Identifying interference with oscilloscopes and software-defined radio - djhuft - 2017-08-10

(2017-08-08, 19:58)pasense Wrote: You should consider to use the low pass filters. With them I could cut out the high frequency noise and could concentrate on hunting the noise sources around 10-30 kHz. Soldering the tiny filters in was far easier than I feared, but they are of course a bit expensive.

I am seriously considering buying those filters. I read in the instructions manual that they are enabled in software by soldering closed a jumper. I'm very curious what options appear in the web interface when you do this. Is it possible to adjust the frequency manually, and what are the limits??

Thanks!

RE: Identifying interference with oscilloscopes and software-defined radio - cutty - 2017-08-10

(2017-08-10, 00:21)djhuft Wrote:
(2017-08-08, 19:58)pasense Wrote: You should consider to use the low pass filters. With them I could cut out the high frequency noise and could concentrate on hunting the noise sources around 10-30 kHz. Soldering the tiny filters in was far easier than I feared, but they are of course a bit expensive.

I am seriously considering buying those filters. I read in the instructions manual that they are enabled in software by soldering closed a jumper. I'm very curious what options appear in the web interface when you do this. Is it possible to adjust the frequency manually, and what are the limits??

Thanks!
The filters are set for cutoff frequency in settings. these settings are NOT visible unless the devices are installed, you have the latest firmware, and the microprocessor is enabled with that jumper you mentioned. The 'idea' is to work between 3K-300KHz, but the actual high end is 328 in settings. On the "Low end", you can virtually turn a channel off... so say "0 to 328K" effective. 
There's no need for these filters if you don't have the higher frequency noise. And eliminating noise with them between 3K and 30K actually kills a lot of the sferic information we're looking for. And they do work...extremely well.  However, I run mine wide open...why not? Same as not having 'em in there... ... my noise is all in that 'critical area' 3-30kHz, unfortunately... and it's sporadic.