Рубрика «Форумы»

5G support

5G support submitted by /u/promach
[link] [comments]

New monitor, unwanted side effect.


right in the centre of the marine band and business radio.

upgraded from an old dual dvi monitor to a gaming one (Asus MG278Q) on displayport.

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

Antennas • Re: Recommended outdoor antenna for SDR?

There are active antennas that provide the frequency range you want, e.g. like the R&S®HE700 with the Rod antenna but than the price is also quite high, since with the other antenna elements it works up to 18 GHz (thats 18 000 MHz).

Models Frequency range
R&S®HE700 10 kHz to 18 GHz
R&S®HE700 Rod antenna 10 kHz to 100 MHz
R&S®HE700 Dipole antenna 100 MHz to 1500 Hz
R&S®HE700 Spiral antennas 1.5 GHz to 18 GHz

You might try an active antenna the cheapest form is a short whip with an associated pre-amplifier. For starter from an old active car antenna could do, since it had to work for AM and FM (~600 kHz up to ~108 MHz).
If you search the internet you will find ideas how to DIY e.g. http://www.g8jnj.net/activeantennas.htm.
Comercial active antennas come in price ranges from a few hundred up to and exceeding 10 000 € (e.g. like the R&S antenna above), but then you get several GHz of Bandwidth and all the bells and whistles you could possibly wish for.

For SW and below just put 5 or more meter of wire horizontally up for FM and above simple groundplanes will do, since for receive you can get away with a lot and still receive signals. You can always improve with time

Statistics: Posted by snn47 — Sun Jan 20, 2019 6:48 am

GOES 16 woes continue…

GOES 16 woes continue...

Second attempt at receiving images from GOES 16 here, using raspberry pi running goestools. After my last attempt was foiled by an issue with the bias tee of my SDR that resulted in the LNA not being powered, I was hopeful that I would get an image this time. Firing up goestools, my viterbi error rate never went below 2000, indicating no signal. However when I connected the SDR to my laptop and ran CubicSDR, the waterfall showed a clear (perhaps weak) signal at the 1.68 GHz range when pointed at the satellite's approximate location:

Definetely something


Which dissapeared when not pointed at GOES, ruling out interference

Despite not changing antenna positioning at all between running goestools and the waterfall, the latter clearly (I believe) showed some reception from GOES. My question is how is it possible to then not be getting a single packet or drop in vit rate? I don't see where there could be a fault in the hardware (in case it was my Pi I tried running goestools on a linux machine, no luck), and I find it hard to believe it's the software. Or was the signal just too weak? Thanks in advance for any ideas/help, this project is fascinating and frustrating at the same time!

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

Troubleshooting Help • Is there any way to run audio through DAP BEFORE Aux VFO???

I'm trying to run a voice inverted signal through the DAP then out the AUX VFO to VB Cable then to a Zello application. I can get this to work if it is the selected frequency and running through the default audio device selected in Windows but when I route it out the Aux VFO it is still scrambled. Is there any way to make DAP process the audio BEFORE it is routed out the Aux VFO????

Statistics: Posted by Fireman3351 — Sun Jan 20, 2019 4:35 am

RTL-SDR Discussion • SW Definitions

Shortwave definitions vary slightly between ITU regions between 1.6 to 1.8 MHz up to 30 MHz see https://en.wikipedia.org/wiki/Shortwave_radio

While TV channel 1 existed in the beginning, most TV Turner in the past 50 years tuned only between channel 2 to 13, and did not provide means for tuning to channel 1. WIth CATV and use of analogue and digital TV norms (meaning e.g. D2MAC and not todays DVB-x modulation) thigs became more complicated.

Until the 6 m was opened HAM SW receiver covered at best 160 m to 10 m, but never above 30 MHz (e.g. Drake or Heathkit, Yeasu, Kennwood ...).

Statistics: Posted by snn47 — Sun Jan 20, 2019 4:24 am

Automating Goestools on Pi?

I've been trying all night to get goesrecv and goesproc to run on my pi via crontab so i dont need to login via ssh and start it every time.....

no success so far...

has anyone setup their Pi to run goestools without having to execute the commands via ssh?

banging my head against a wall here ;)

i've tried this

@reboot /usr/bin/goesrecv -v -i 1 -c /home/pi/goesrecv.conf > /home/pi/goesrecvlog.txt

@reboot /usr/bin/goesproc -c ~/goesproc-goesr.conf -m packet --subscribe tcp:// > /home/pi/goesproclog.txt

and I can see goesproc in the running processes after rebooting, but goesrecv isnt there (a problem, obviously) and there's no output in either of the files.

can anyone point me in the right direction?

or does anyone automate goestools a different way?

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

troubleshooting goesrecv

hi, I built a setup according to this. After the first few seconds, my packet drops are consistently at 10-13. I've adjusted the antenna back and forth, up and down, and my vit doesn't get much better than what shows below. I've tweaked the gain and sample rate without any luck. Any advice? Thanks in advance!

Jan 19 23:52:18 raspberrypi goesrecv[1913]: Found Elonics E4000 tuner

Jan 19 23:52:19 raspberrypi goesrecv[1913]: Disabled direct sampling mode

Jan 19 23:52:19 raspberrypi goesrecv[1913]: [E4K] PLL not locked for 0 Hz!

Jan 19 23:52:19 raspberrypi goesrecv[1913]: Exact sample rate is: 2000000.052982 Hz

Jan 19 23:52:19 raspberrypi goesrecv[1913]: Allocating 15 zero-copy buffers

Jan 19 23:52:20 raspberrypi goesrecv[1913]: 2019-01-19T23:52:20Z [monitor] gain: 6.73, freq: -333.8, omega: 2.157, vit(avg): 944, rs(sum): 111, packets: 16, drops: 15

Jan 19 23:52:21 raspberrypi goesrecv[1913]: 2019-01-19T23:52:21Z [monitor] gain: 4.44, freq: -619.0, omega: 2.157, vit(avg): 868, rs(sum): 317, packets: 29, drops: 12

Jan 19 23:52:22 raspberrypi goesrecv[1913]: 2019-01-19T23:52:22Z [monitor] gain: 2.94, freq: -665.3, omega: 2.157, vit(avg): 237, rs(sum): 217, packets: 44, drops: 0

Jan 19 23:52:23 raspberrypi goesrecv[1913]: 2019-01-19T23:52:23Z [monitor] gain: 2.94, freq: -621.2, omega: 2.157, vit(avg): 241, rs(sum): 206, packets: 44, drops: 0

Jan 19 23:52:24 raspberrypi goesrecv[1913]: 2019-01-19T23:52:24Z [monitor] gain: 2.94, freq: -644.7, omega: 2.157, vit(avg): 239, rs(sum): 189, packets: 42, drops: 0

Jan 19 23:52:25 raspberrypi goesrecv[1913]: 2019-01-19T23:52:25Z [monitor] gain: 2.94, freq: -605.1, omega: 2.157, vit(avg): 236, rs(sum): 210, packets: 44, drops: 0

Jan 19 23:52:26 raspberrypi goesrecv[1913]: 2019-01-19T23:52:26Z [monitor] gain: 2.94, freq: -559.4, omega: 2.157, vit(avg): 328, rs(sum): 204, packets: 40, drops: 2

Jan 19 23:52:27 raspberrypi goesrecv[1913]: 2019-01-19T23:52:27Z [monitor] gain: 2.94, freq: -723.6, omega: 2.157, vit(avg): 347, rs(sum): 108, packets: 20, drops: 12

Jan 19 23:52:28 raspberrypi goesrecv[1913]: 2019-01-19T23:52:28Z [monitor] gain: 2.94, freq: -624.2, omega: 2.157, vit(avg): 497, rs(sum): 116, packets: 22, drops: 12

Jan 19 23:52:29 raspberrypi goesrecv[1913]: 2019-01-19T23:52:29Z [monitor] gain: 2.94, freq: -563.3, omega: 2.157, vit(avg): 402, rs(sum): 100, packets: 22, drops: 11

Jan 19 23:52:30 raspberrypi goesrecv[1913]: 2019-01-19T23:52:30Z [monitor] gain: 2.94, freq: -653.3, omega: 2.157, vit(avg): 430, rs(sum): 103, packets: 21, drops: 12

Jan 19 23:52:31 raspberrypi goesrecv[1913]: 2019-01-19T23:52:31Z [monitor] gain: 2.94, freq: -635.4, omega: 2.157, vit(avg): 406, rs(sum): 129, packets: 22, drops: 11

Jan 19 23:52:32 raspberrypi goesrecv[1913]: 2019-01-19T23:52:32Z [monitor] gain: 2.94, freq: -594.9, omega: 2.157, vit(avg): 387, rs(sum): 108, packets: 21, drops: 13

Jan 19 23:52:33 raspberrypi goesrecv[1913]: 2019-01-19T23:52:33Z [monitor] gain: 2.94, freq: -593.5, omega: 2.157, vit(avg): 366, rs(sum): 97, packets: 20, drops: 12

Jan 19 23:52:34 raspberrypi goesrecv[1913]: 2019-01-19T23:52:34Z [monitor] gain: 2.94, freq: -614.0, omega: 2.157, vit(avg): 427, rs(sum): 107, packets: 23, drops: 11

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

Powering Devices with Bias Tee power

Hi! Using a bias tee as a power injector seems straight forward. However, I can't seem to find an answer as to how to remove the injected power to operate a device.

For example: I am injecting power into a cable using a bias tee which feeds into this LNA. There are three ports on the LNA: RF in, RF out, and DC in. How do I get the injected power to the DC in port of the LNA?

Does it require using another bias tee connected in reverse??? Thank you!

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

Question about GOES CIRA Geocolor…. Am I ever going to get realtime nighttime city lights?

So, I recently got my GOES 16 rig working.

Most of my inspiration came from THIS post from a few months ago, which showed a composite made from day/night shots that included city lights... I thought the night time city lights were awesome (twice as much viewing -- you can see interesting stuff at night, besides the IR channels).

I was disappointed when I didn't find that imagery among the captured channels.

I went back to the post, and read in the comments that he used CIRA geocolor to generate the images.

I found THIS page describing it...

here's a quote from the site:

The main caveat users must always be aware of when using this product is that the backgrounds (ie, the Blue Marble and NGDC nighttime city lights) in the current GeoColor product are static. As such, almost all dynamics pertaining to the background will not be captured in this product. Unless some aspect of the change is captured in the real-time GOES visible/infrared observations, it will not be represented. For example, seasonal changes in vegetation, power outages, river plumes, variation of nighttime land brightness with lunar phase, etc, or impacts from a natural disaster, may not be represented in real-time imagery produced from this method. Examples of backgrounds that will be detected are snow cover and sea ice during the daytime, which will manifest as bright targets in the current GOES imagery. Although technically part of the 'background' since they are not atmospheric features, they will be revealed in the GeoColor imagery due to their high reflectance in the GOES daytime visible channel imagery. For an example of poor performance due to static backgrounds, the city lights of New Orleans appeared to shine brightly the night after Hurricane Katrina’s passage over the city.

When this product is available in the actual GOES-R era, the backgrounds will be available more often because of the instruments on the NPOESS satellites. Specifically, the backgrounds will be produced more often and at higher fidelity by the Visible/Infrared Imager/Radiometer Suite (VIIRS) sensors (which include the Day/Night Band for nighttime lights). More frequent updates will enable the capture of some of the dynamic background components that were mentioned previously—improving its representation of all components of the scene. As for the nighttime side of GeoColor, the GOES-R ABI provides 'low light' sensitivity, but the light levels in this case refer to twilight conditions as opposed to natural/artificial terrestrial light emissions and lunar reflection light levels several orders of magnitude fainter.

so.... unfortunately there is no nighttime citylights right now... or ever, coming from GOES.... and those images are coming from NPOESS satellites and the image is overlaid.... and static.

So.... I'll never get (near) real-time nighttime lights?

:( disappointing... THIS beautiful image posted a few months ago is inspiring, but somewhat misleading. (not that OP hid anything)

submitted by /u/quartapound
[link] [comments]
Январь 2019
Пн Вт Ср Чт Пт Сб Вс
« Дек