Skip to main content

NOAA 19 Signal received using a RTL-SDR DVB-T usb receiver

A couple of years ago I tried to receive the NOAA 18 using a small in-door antenna and an RTL DVB-T USB receiver. The results were disappointing. However, I always had in the back of my mind that I will try again in the future with an external antenna. The era of cheap RTL-SDR hardware has come, so many people have started looking for receiving images from the weather satellites. Easy targets are the NOAA satellites that transmit weather images using Automatic Picture Transmission method (APT). These satellites provide images in different wavelengths of light.

So after following instructions from a site dedicated to the RTL-SDR receivers, I tried to receive some pictures using the simple TV antenna. However, this decision had many disadvantages, as the TV antennas are designed to receive signal on higher frequencies from NOAA satellites. Despite the poor reception and low cost (e.g.,. none, I had an old tv antenna installed, but not used) I was able to receive some pictures. I used the SDR# with the RTL-SDR plugin for receiving the signal (sound), orbitron for tracking the satellite, and WXtoImg for converting the images. Here is a screenshot of my setup:

Software setup for receiving NOAA 19. Left the SDR# tuned at 137.1 MHz using the RTL Dongle, right top the WXtoImg  to decode the image, and right bottom orbitron for tracking the satellite.
Software setup for receiving NOAA 19. Left the SDR# tuned at 137.1 MHz using the RTL Dongle, right top the WXtoImg
to decode the image and right bottom orbitron for tracking the satellite.

After the first reception, the WXtoImg converts the APT signal to images. Here are two examples of the pictures received:

Raw reception 26 of May 2015 of NOAA 19. Note the big cloud approaching from the left. On the right is the infrared version of the picture.
Raw reception 26 of May 2015 of NOAA 19. Note the big cloud approaching from the left. On the right is the infrared version of the picture.

APT weather image reception from NOAA 19.
Raw reception 24 (?) of May 2015 of NOAA 19.
After the first reception, WXtoImg makes some processing on the pictures to improve the contrast. Here is the output of raw images:

Improved contrast of NOAA 19 APT image. Received using RTL dongle, SDR# and WXtoImg.
Improved contrast of NOAA 19. Received using RTL dongle, SDR# and WXtoImg.

Improved contrast APT image received from NOAA 19 using the cheap solution for Software Defined Radio (SDR)
Improved contrast of NOAA 19.
After that, WXtoImg can also create a color version of the picture:

Color view of  the received APT image from the NOAA 19 using SDR# and WXtoImg.
Color view of the received image from the NOAA 19 using SDR# and WXtoImg.
Next target is to buy a proper antenna and a proper receiver, such as the  SDR play or the FUNcube Dongle plus.

Recent advancements in the RTL dongles packaging made affordable wide band receivers such as the  SDR Blog Receiver with Rtl2832u ADC Chip.

Popular posts from this blog

Processing Milky Way in RawTherapee

This text is an analysis of a video I did some months ago how to process photos of our Milky Way in RawTherapee. You can find the picture here . The photo was taken by wiegemalt. This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License. Editing: Step 1: Fixing lighting The first thing someone notices when opening the picture is the extreme noise due to high ISO used (1600 - check the picture on the right). The first thought is to de-noise the picture, however, if you do that you are going to loose the details of the night sky. The main reason for the high noise is the additional exposure Rawtherapee adds when the 'Auto' button is pressed. In particular, the RT adds +2.4 EV to equalize the picture. This is Wrong! What we want is to keep the noise down and at the same time bring the stars up. That's why we are going to play with the Tone Curve of the RT. To adjust the light properly we increase the cont

Static linking with gcc and g++

In this tutorial, we will explain what the static linking is, how this affect the size of final binary, and why statically linking with g++ sometimes is pain. By definition, a statically compiled binary is a group of programmer ‘s routines, external functions, and variables which are packed into the final binary executable. The compiler or the linker produces the final object and embeds all the functions and variables and the linking phase.  There are two reasons of using dynamic linking and shared libraries: 1) Avoid creating a huge binary, if all the programs use a standard set of libraries why not having the operating system providing to them 2) Compatibility on operating system and machine dependant characteristics: sometimes the libraries must be implemented based on the architecture or the operating system and using dynamic linking is an easy way to avoid this catch. On the other hand, static linking is the ideal way of distributing one software product, paying

Homemade NAS after two and half years

Few years ago, I created a NAS system using my old PC. The old pc is powerful enough to do the basic NAS operation except real time transcoding of 4K or more than one 1080 streams.  The setup was setup as follows: 1 SSD 128 GB for boot device 2x 4 TBs for the main storage configured as RAID 1 The hard disks were from different manufacturers (WD red plus and Segate) to avoid catastrophic situations: disks are part of a bad batch and you will have a second failed disk during the build of the RAID array. Here is a list of my mistakes: My first mistake was CentOS. I wanted a stable machine without surprises, unexpected behavior, as much less bugs affecting my setup. I had three free/open source options:  Open Media Vault: Debian based Linux with many configuration options. The main downside is that you don't have support for ZFS and you have to very often use the command line to fix things. Moreover, there are a plethora of open issues/bugs that can make your life harder than expected