https://nccgroup.github.io/RFTM/fsk_receiver.html
https://www.ripublication.com/ijeer17/ijeerv9n8_03.pdf
Trying to recreate an FSK receiver and transmitter over and HackRFOne SDR + antenna.
Dont seem to find a good or working alternative for Encoder/Decoder function on GNU radio(using version 3.10)
Related
I thought it would be fun to implement a rudimentary version of Octoprint that can receive a gcode file and initiate a print on my Prusa i3.
What are the requirements for initiating a print on a 3D printer via USB?
You can use the pySerial library in Python to send raw G-Code to the /dev/ttyWhereverYourPrinterIs serial device. Most printers specify their baud rate in their UI, or user's manual. My printer says its USB baud rate is 115200.
Quoting Gina Häußge:
If you are only targeting a very specific printer with a very specific firmware variant: serial connection and then read up on https://reprap.org/wiki/G-code. It becomes a horrible nightmare to implement and maintain though when you take the thousands of firmware variants out there into account, so beware.
I am new in beaglebone black. BBone Device is connected to the GSM Module on the USB port. I faced some issue like;
1 USB Port not initialize
2 Beaglebone abruptly Off
3 Beaglebone Restated
I have to find some patch for controlling bubble interrupt but I am not finding that patch path in the beaglebone device.
Pls see below patch link;
https://marc.info/?l=git-commits-head&m=144331613106445&w=2
Can Anybody faced similar type problem????
And finding a solution then reply me...
Do you supply the power from the jack? Not from the usb right?
Where the GSM module takes the power? Does it take from the Beaglebone USB_VBUS?
If the GSM module takes the power from the USB_VBUS of BeagleBone or any IO from the BeagleBone. It is possible to cut the connection and restart because, there is an over current protection on the hardware.
It is an important point that what are the power sources of Beaglebone and GSM module? Also, GSM modules maximum current increase the 2A.
I am trying to connect MQ5 sensor to a Telosb and read the values, and i am using contiki os.
My problem now is:
I know that i need an ADC driver in contiki os, but i do not know how to do it or from where to start ?
Can anyone guide me please?
The ADC driver for TelosB is already implemented in Contiki, you can find it in file sky-sensors.c and sky-sensors.h in contiki/platforms/sky.
See light-sensor.c and temperature-sensor.c for examples of sensor drivers that use this "sky_sensor" API. Basically you need to select which ADC input channel to use and what reference voltage to use, the rest is trivial: call sky_sensors_configure function and read from the right memory location mapped to an ADC input port. For example, by reading ADC12MEM4 you can access the ADC channel 4.
What would be the filter command in wireshark to find the specific MAC address of the beacon ?
So for the MAC address of F4:8B:F9:B0:61 how would I filter out this specific beacon in wireshark?
Error after following tutorial by davidyoung :
"Error in column 'payload protocol' dissector not found"
If you want to use Wireshark with Ubertooth, you must either build or buy the Ubertooth board: http://ubertooth.sourceforge.net/
I have not done this, so I can not speak to the exact steps or the relative merits of this approach. The approach I have taken to sniffing Bluetooth LE traffic is to buy a TI CC2540 USB dongle, which you can get with sniffing software for Windows: http://processors.wiki.ti.com/index.php/BLE_sniffer_guide
An alternative to the Ubertooth that #davidgyoung mentioned is the Adafruit Bluefruit LE Sniffer. At $30 it is significantly cheaper than the Ubertooth.
Assuming you already have a hcidump or know how to create one.
try following as filter:
frame[7:6] == F4:8B:F9:B0:61
In Version 1.10.6 it seems to give me only the packages from that specific beacon.
It's possible to even create a dissector for the advertising data, if you know how to decode it.
I’m doing a study project on wifi signal quality. What I want to do is use Raspberry Pi’s to monitor as many metrics as possible on packet level data. I want to do this by putting wifi adapters on monitor mode (using airmon-ng) and than capture the data about the packets using a wireless network protocol analyzer, like tshark.
What I understand from the wireless networks is that you mainly have three parts: a frame part that has the same information independent of what you’re capturing on, which contains things as frame number, frame length and arrival time. (Want to upload images but don't have 10 reputation yet...).
Then the IEEE 802.11 data which contains the necessary stuff for the network to work. When capturing on WLAN this contains the MAC addresses.
And than we have the radiotap header, which contains all kind of information (signal strength db and dbm, noise level, signal quality, TX value, and much more). This one is a bit different, since this information is actually filled or injected by the wifi adapter you use to capture the data with.
In the present flags you can find which values are actually being injected by the wifi adapter. Now my problem is that for my research I really need as much values as possible. I’ve been working for hours but I didn’t succeed in finding a way to capture with anything more than dmb signal strength (if even available). So this is what I tried so far:
The adapters I used so far are the Edimax EW7811UN, the AirPcap Classic, the AirPcap Tx and two similar alfa adapters with Atheros AR9271 chipset. The AR9271 adapters worked out of the box on raspbian (debian for raspberry pi) on the ath9k_htc driver. Putting them on monitor mode and capturing works fine, but only dbm singal strength is given (as in the screenshots above) in the capture. The Edimax was working out of the box on the 8192cu driver, however it clearly doesn’t support monitor mode. I could put it into monitor mode when booting it on the zd1211rw driver but that didn’t even give the dbm signal strength. Strange thing however, is that a friend tried the exact same Edimax adapter and he could capture, and the only difference we could find is that the lsmod says rtl8192cu and not 8192cu. Strangely, forums are saying that 8192cu is the newer version, however this friend had the newest arch linux kernel installed (newer than the raspbian). So I installed Arch Linux on the pi, but still wasn’t able to put the edimax on 8192cu driver in monitor mode. Then I found a package in the aur repos: dkms-8192cu which was supposed to have a patched version. However, after installing it still didn’t work. Also downloading the driver from the realtek website didn’t work. There is some stuff on patching on the aircrack-ng website, but it actually is mentioning injection of frames and doesn’t really look to be what I exactly need.
Than I bought the Airpcap Classic and the Airpcap Tx to see what they could do. First of all, they have zero linux support so that already is a big drawback since l need to use it from the Pi’s. However even in windows the airpcap’s only capture db and dbm noise and signal quality. It does receive some data at dbm noise level, but it’s worthless since it is always at -100 level. I can boot the Airpcap classic and tx have zd1211B chipset so I can boot them on zd1211rw driver but this also gives no dbm signal value or anything else.
So my question is, what exactly determines what’s in the radiotap header? I guess it would be all in the driver, but I need to be exactly sure before I write off every ath9_htc driver based adapter. I’m about to purchase another adapter which runs on carl9170 driver, however I can’t find no guarantee anywhere that it will give me those values. What I did find in the literature is that the madwifi driver gives (or was giving) noise levels, however it is acquired by Atheros so the project stopped and all websites are suggestion just to use ath9k or ath5k drivers. I tried to install it but I failed because it seems to be really outdate software since the project stopped.
It would be of really big help if someone can explain me what exactly determines what’s inside the radiotap headers, and also if someone could share any experience on when they did capture more than only dbm signal strength values from linux.