Архив за 12.05.2019

KerberosSDR • Re: Power connection question

If it's not a PD supply it should work fine with the KSDR. The KSDR only really needs 2A, but if you're using single board computer like a Pi3 or Tinkerboard with it, then the singleboard computer absolutely must be powered with a 3A+ supply.

Statistics: Posted by rtlsdrblog — Sun May 12, 2019 11:38 pm

NOAA 15 — very low elevation pass (16°) — First successful capture with new LNA

NOAA 15 - very low elevation pass (16°) - First successful capture with new LNA submitted by /u/unknownantipatriot
[link] [comments]

RTL-SDR Discussion • LNA power supply?

I'm using a LNA with a 9v and was thinking about using something like a 12v 1a phone charger to power the LNA. Was wondering if that would create any noise though. Anybody tried this?

Statistics: Posted by Kev7274 — Sun May 12, 2019 11:22 pm

KerberosSDR • Re: Setting the KerberosSDR EEPROM

Found the culprit! I can't believe it, a brand new USB3.1 USB-C cable, probably less than ten times plugged in and out, straight from the box and *sha-zang*! The USB-C connector end came off when I unplugged it from the KSDR. :lol: :x :oops:

Luckily I was so hindsighted with the common non-existent quality control of today's world that I had bought two cables. So, all's well for now what comes to the KSDR EEPROM flashing. Did it on the Raspi3B+ box and gave 0 phuq'ues about the warnings, everything went as smooth as F.

Used the instructions as advised by rtl-sdr's initial post + the additions noted by user kb3cs.

1. Enabled all the DIP switches by switching all four to ON position.
2. Ran rtl_eeprom from the KSDR Raspbian pre-built image for Raspberry Pi Model 3B+

First batch of code:


rtl_eeprom -d 0 -g realtek_oemrtl_eeprom -d 1 -g realtek_oemrtl_eeprom -d 2 -g realtek_oemrtl_eeprom -d 3 -g realtek_oem
^ Power cycle (as suggested by rtl_eeprom after each flash) between each step in the above, just to be safe.

Second batch of code, ran them just one by one and then power cycled the device, worked just fine:


rtl_eeprom -d 0 -s "001" -m RTL-SDR -p KerberosSDRrtl_eeprom -d 1 -s "002" -m RTL-SDR -p KerberosSDRrtl_eeprom -d 2 -s "003" -m RTL-SDR -p KerberosSDRrtl_eeprom -d 3 -s "004" -m RTL-SDR -p KerberosSDR
Huge thanks to the forum mods & devs for listening me whine and username kb3cs for the additional heads up on adding the identification signature into KerberosSDR. You might want to change the official instructions on the initial post onto this thread to match that one.

Why? Well, upon my initial configuration, I noticed that actually having a RTL-SDR dongle running alongside with just one KerberosSDR's receiver unit at the same time will cause SDR software confusion. That's a real good catch on how to avoid any issues.

Also, my idea on this subject matter would be to perhaps have a simple script added to the official KSDR build so that you could quickly flash the unit to the recommended/desired EEPROM settings.


Statistics: Posted by StandingWave — Sun May 12, 2019 10:13 pm

My Trip to Arecibo Observatory — A VR virtual tour


When i went i took my 360 camera and took a fair amount of pictures. here is a virtual tour of the facility i threw together this morning specifically for /r/RTLSDR. enjoy. (no virtual reality headset required)

Camera is a gopro fusion i bought a few days before so i haven't quite mastered the techniques for taking high quality photos with it yet. thanks for understanding.

submitted by /u/mosler
[link] [comments]

Comment on Using a Beam Deflection Tube as a Mixer for an RTL-SDR Upconverter by Pawelr98

Recently I built a somewhat similar upconverter using ech81 heptode-triode. Triode works as Meissner (aka Armstrong for US people) oscillator (LO) while heptode works as mixer and RF amp. G3 tied to Triode grid, G1 is RF input. Vacuum tube upconverters have massive signal levels so they cannot really be plugged in directly. It peaks my RTL-SDR input even when beeing couple meters apart(small antenna provided with generic RTL-SDR). Around 200V anode, G2+G4 at around 85V. Triode anode at around 60V. Cathode at ground level. LO at around 11MHz, bringing some HF signals into RTL-SDR low-end usable range.

Beginner trying to detect signal on 868 MHZ

Hi, I have a central remote controlled heating from Honeywell (HC60NG) which is controlled via a CM67NG. I would like to reverse the communication protocol. According to the manual the two units communicate on 868.0 to 868.6 MHZ.

I tuned my SDR onto 868.3 MHZ using Gqrx and tried to find any signal. Unfortunately I can not see anything that looks like the signal from the panel.

I can turn the control panel into a test mode where it will send a signal every 5 seconds, if the main control receives this signal it will tun a led on. I enabled this mode and observed the LED flash but again I could not find anything that looks like the signal.

Could the manual be wrong about the used frequency? If so, what are other common frequencies besides 433 MHZ and what would be the easiest way to scan for an unknown but periodic signal?

Regarding my SDR, I could not really verify how well it is working, I can tune it to FM radio (tried around 103MHZ) and listen to radio stations using Gqrx. But I'm not sure if that's good enough to detect signals on 868MHZ.

submitted by /u/unkieee
[link] [comments]

KerberosSDR • Re: Setting the KerberosSDR EEPROM

OK, so after running KSDR on the Raspberry Pi 3B+ pre-built image from RTL-SDR, the status window in the KerberosSDR util seems to show a green light for the power status in the program window as I try running the simple routines on it.

With rtl_eeprom, I get the "same-kindish" warning as on the Win7/64bit PC:


pi@raspberrypi:~ $ rtl_eepromFound 4 device(s):  0:  Generic RTL2832U  1:  Generic RTL2832U  2:  Generic RTL2832U  3:  Generic RTL2832U Using device 0: Generic RTL2832Urtlsdr_write_reg failed with -9rtlsdr_demod_read_reg failed with -7rtlsdr_demod_write_reg failed with -9rtlsdr_demod_write_reg failed with -1rtlsdr_demod_read_reg failed with -1r82xx_write: i2c wr failed=-1 reg=1a len=1r82xx_init: failed=-1rtlsdr_demod_write_reg failed with -1rtlsdr_demod_read_reg failed with -1 No EEPROM has been found.
I'm not sure what the other error messages are, but the GitHub "safety catch" issue at https://github.com/rtlsdrblog/rtl-sdr-kerberos/issues/2 seems to suggest that by default, the rtl_eeprom util should show an error message for the EEPROM, since there is none on the board when it's shipped out. Am I on the right track or have I completely lost my mind already?

I'd assume it'd be the safest bet to run the rtl_eeprom flash procedure on a a RPI3B+ rather than in Win7/64bit admin prompt, as it's the latest version of the KSDR's pre-built Raspbian image and all, but ...

Statistics: Posted by StandingWave — Sun May 12, 2019 9:08 pm

Could SDR be Illegal? [Podcast]

submitted by /u/Corrosive_One
[link] [comments]

KerberosSDR • Re: Setting the KerberosSDR EEPROM

OK, so the previous power source I used was a Belkin's AC power distributor with USB ports in it, it was rated at 5V / 2.4 A max output power, no dice. I tried another PSU just now that's rated @5V that had a lower amp rating and that did not change the outcome with rtl_eeprom.exe.

Again, out of the available documentation (which is the product page for KSDR and some of the blog & forum posts here at rtl-sdr.com), is it nowhere properly and clearly stated what kind of PSU apart from the 5V voltage you should be using to power up the KSDR through the USB-C port. It says "that can handle up to 3A"; but on one of the threads over here somebody said that if you're running the KSDR on 5V instead of 4.5V, the amp requirements should be lower ... Sheesh!

The blue LED inside the KSDR (which is not properly explained either) does light up when I connect the USB-C cable in addition to the MicroUSB data transfer cable, that should be an indicator that at least it's getting powered, right?


...\rtl-sdr-release\x64>rtl_eeprom.exeFound 4 device(s):  0:  Generic RTL2832U  1:  Generic RTL2832U  2:  Generic RTL2832U  3:  Generic RTL2832UUsing device 0: Generic RTL2832UFound Rafael Micro R820T tunerCurrent configuration:Error: invalid RTL2832 EEPROM header!Error: invalid string descriptor!Error: invalid string descriptor!Error: invalid string descriptor!__________________________________________Vendor ID:              0xffffProduct ID:             0xffffManufacturer:                                                                                                                                     t☼Product:Serial number:Serial number enabled:  noIR endpoint enabled:    yesRemote wakeup enabled:  yes__________________________________________
What I DID find upon searching that particular error message though, was i.e. the rtlsdrblog GitHub issue that's been open since April 3., apparently it's quite easy to brick your KSDR. See the issue titled "safety catch" for rtl_eeprom #2: https://github.com/rtlsdrblog/rtl-sdr-kerberos/issues/2

Seriously, guys. What gives? I'm not the first nor the only one voicing my opinion on the fact that there needs to be a bit better documentation for the board. And that's with all due respect. You're doing an awesome job and I've been your long-time supporter, but seriously. Can we get this wagon rolling on, please?

[EDIT: I will try to run the rtl_eeprom on my Raspberry Pi 3B+ and see what it says then. Will post the results.]

Statistics: Posted by StandingWave — Sun May 12, 2019 8:27 pm

Май 2019
Пн Вт Ср Чт Пт Сб Вс
« Апр   Июн »