#
airspy
Here are 34 public repositories matching this topic...
Spectrum analyzer for multiple SDR platforms (PyQtGraph based GUI for soapy_power, hackrf_sweep, rtl_power, rx_power and other backends)
visualization
python
radio
qt
spectrum-analyzer
sdr
rtl-sdr
fft
hackrf
software-defined-radio
airspy
limesdr
-
Updated
May 30, 2018 - Python
This project is about creation of affordable and easy-to-manufacture prototypes of PCBs which are used to expand the capabilities of existing low-cost SDR receivers based on RTL2832U chip.
radio
pcb
sdr
rtl-sdr
hackrf
smd
airspy
sdrplay
attenuator
rtl2832
sdr-receiver
antenna-mini-whip
hf-upconverter
lna
easyeda
bias-tee
sdr-receivers
antenna-switch
-
Updated
Jul 20, 2021
danieladams456
commented
Jan 13, 2021
It looks like on Raspberry pi, libssl-dev files get put in a different location than cqrlog is expecting. https://www.cqrlog.com/comment/7703#comment-7703
The reason for this is because on Rapsbian Buster libssl and libcrypto are at a different location than on other Linux releases. ( /usr/lib/arm-linux-gnueabihf )
Just copy from /usr/lib/arm-linux-gnueabihf to /usr/lib following files:
li
Obtain power spectrum from SoapySDR devices (RTL-SDR, Airspy, SDRplay, HackRF, bladeRF, USRP, LimeSDR, etc.)
-
Updated
Jan 24, 2020 - Python
python
weather
satellite
python3
satellite-imagery
lrit
hrit
airspy
rtlsdr
coms-1
weather-satellite
gk-2a
geo-kompsat-2a
xrit-rx
-
Updated
Aug 2, 2021 - Python
Various projects on the IKEA Sparsnäs/Sparsnas energy monitor
assembler
spi
msp430
sdr
rtl-sdr
lpc
ikea
hackrf
cc1101
wemos-d1-mini
signal-analysis
xor
rfcat
texas-instruments
frequency-analysis
nxp
openocd
airspy
jtag
lpc17xx
-
Updated
Apr 20, 2018 - Python
-
Updated
Jul 30, 2021 - Python
Plugin for SDR# (SDRSharp) adding Discord Rich Presence (RPC)
plugin
frequency
visual-studio
video
csharp
discord
rpc
rtl-sdr
rds
airspy
sdrsharp
sdr-sharp
rich-presence
discord-rpc
discord-rich-presence
discord-status
spyserver
sdr-rpc
-
Updated
Jul 6, 2021 - C#
Improve this page
Add a description, image, and links to the airspy topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the airspy topic, visit your repo's landing page and select "manage topics."
A common protocol structure is to have a header containing a
lengthfield, followed by data oflengthbytes, followed by additional protocol fields such as a CRC. If the length field is variable, the position of subsequent URH-specified protocol fields defined by fixed position will not be in the correct location.I do not know the best way to address this, but quick and easy way to support