Observation 12326506: WEIRD WATERFALL

Regarding Observation 12326506

During my tests yesterday, at some point I removed the 10 meters of TV cable I had between my LNA (powered via biasT), and my RTL SDR. The LNA was then directly conected to the RTL. I had some crazy waterfalls (see example observation) and thought I broke something.

I put the TV cable back and it came back normal.

Why is the waterfall so weird? Is putting the LNA directly on the RTL SDR is a bad practice?

I have seen this behavior before and found that the only solution is reconnecting the SDR (usb disconnect, usb reconnect)

It happens on both RTL SDR v3 as v4 and even after testing multiple drivers have found a solution.

Jan | PE0SAT

1 Like

Hello,

Thanks for the fast answer.

Does this issue appear randomly from time to time or is it just when you move stuff and change your setup like I did?

What I have found out, it seems an USB problem and can happen at random.
(Tried adding or removing USB devices to the system, unable to recreate the problem)

It is possible that multiple, days, weeks even months the problem will not happen and then maybe days after another.

Jan | PE0SAT

1 Like

Ok, thanks a lot.

1 Like

found similiar like this :

look like the owner of this station (SatNOGS Network - Observations) should replug the rtl-sdr usb..

1 Like

yeah, that is no signals at all, just crap data from the sdr, it will not matter if you have antenna connected or not when it is that state.
I’m not sure, but I think it is either temperature related or usb.
if it starts after touching or moving the sdr it might point to usb glitching out.
running it at lower sample rates reduces temperature. 1024e3 or 2048e3 being two very common rates, 2400e3 usually needs cooling.

Hello,

Sorry for the revive but I am on the same problem right now. My station worked fine for 1 month and half, but the USB connection glitched twice in a week (example: SatNOGS Network - Observation 12910047 )

  • Are you suggesting it’s the temperature that causes the issue?
  • Would putting 1024e6 (I think yoou meant e6 not e3?) solve the issue? Or just reduce the time it happens?
  • I saw we can programmatically reset the USB connection, do you think that works as well as unpluging, pluging again? (For context, I don’t live wher my station is, so if I can auto reset from time to time just doing this it would be nice.

Apart from lowering the sample rate to 1.024e6 I tried every option and always needed to remove and reconnect the RTL-SDR to get it back in a running state.

Only a power down of the RTL-SDR seems to fix this problem so maybe lowering the sample rate will stop the SDR from getting in this fault.

Jan | PE0SAT

1 Like

There’s no way to cut the power programatically?

Also what’s the downside of lowering the sample rate? Will it be harder to decode? Or is is still high enough anyway?

I haven’t found a way to power cycle the RTL-SDR remotely, you could try to find a remotely managed Pi power supply I know @ea5wa seems to have one.

Lowering the sample rate will reduce the decimation value and therefor lowers the reception quality.

At the end I replaced all my SDR devices with other models and haven’t experienced any problems after that.
Have a look at the meta data of all my stations to see what SDR is used.

Jan | PE0SAT

1 Like

Ok, thanks :+1:

1 Like

I normally switch off/on the power with a SONOFF device controlled with an Android app

1 Like

Can you share some details so others can also maybe make use of it.

Jan | PE0SAT

Its just a socket connected to WiFi. There are a lot of different models. Once is connected to your wifi, you can control it using the app (eWeeLink)

In my case, I use 4 relay devices (sonoff 4ch R3), to control 4 sockets.

I have 3 of them in my app

2 Likes