#
bladerf
Here are 25 public repositories matching this topic...
Open
tests
cooperq
commented
Oct 15, 2020
We currently don't have any tests (other than the tests built in to srslte) we should write some tests for the python end of things and set up continuous integration. I don't have any opinions about what test suite we should use.
Bluetooth Low Energy (BLE) packet sniffer and transmitter for both standard and non standard (raw bit) based on Software Defined Radio (SDR).
security
dsp
sniffer
protocol-analyser
ble
bluetooth-low-energy
sdr
protocol-parser
hackrf
packet-sniffer
rf
indoor-positioning
software-defined-radio
wireless-sensor-networks
wireless-communication
baseband
bladerf
wireless-security
angle-of-arrival
-
Updated
Jul 16, 2021 - C
Readsb is a Mode-S/ADSB/TIS decoder for RTLSDR, BladeRF, Modes-Beast and GNS5894 devices. Future development version with protocol buffer storage.
typescript
leaflet
indexeddb
sdr
rtl-sdr
ads-b
adsb
protocol-buffer
rrd
dump1090
rtlsdr
mode-s
bladerf
adalm-pluto
protobuf-c
dump1090-fa
gns5894
ubladerf
readsb
libprotobuf-c
-
Updated
Aug 1, 2021 - C
A Ble Fingerprint Sniffer based on SDR.
-
Updated
May 13, 2020 - C++
GNU Radio block for bladeRF devices
-
Updated
Jun 17, 2021 - C++
Repository for the models and code used in "UE Tracking Beamforming using a MIMO Software-Defined Radio" MSc project.
-
Updated
Jul 11, 2021 - MATLAB
Software Defined Radio GPS Signal Simulator
-
Updated
Jan 15, 2021 - C
The goal of this app is to make it trivial to demodulate most basic RF transmission, and provide a digital worksheet for your reverse engineering efforts.
-
Updated
Mar 12, 2020 - Ruby
Tool to locate taxis who use ham radio for communication
-
Updated
Jun 8, 2020 - C++
Improve this page
Add a description, image, and links to the bladerf topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the bladerf 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