Hello guys,
I'm searching for any suggestion for implementing frequncy hopping between 4-5 totally diffrent frequencies via GNU radio?
Thanks,
Itay
Implementing simple frequency hopping
-
itay
- Posts: 2
- Joined: Tue Dec 30, 2014 12:42 pm
Re: Implementing simple frequency hopping
Thanks Jon,
This is realy helpful info.
Any useful information about dynamicly change of varible value while running? Can it be implemnted via the standanrt GNU radio blocks?
Thanks,
Itay
This is realy helpful info.
Any useful information about dynamicly change of varible value while running? Can it be implemnted via the standanrt GNU radio blocks?
Thanks,
Itay
-
alexlitv
- Posts: 1
- Joined: Thu Aug 04, 2016 5:52 am
Re: Implementing simple frequency hopping
Hi !
I want to try libbladeRF_test_scheduled_retune.exe .
What meaning [device str] in command line?
device serial?
libusb instance ?
Thanks in advance
Alexander
I want to try libbladeRF_test_scheduled_retune.exe .
What meaning [device str] in command line?
device serial?
libusb instance ?
Thanks in advance
Alexander
- rtucker
- Posts: 77
- Joined: Sun Jan 25, 2015 10:38 am
Re: Implementing simple frequency hopping
It's looking for a device string. If you only have one device, it may be omitted. If you have more than one connected, you may select between them using the -d parameter, e.g.:
Here's the options:
Code: Select all
rtucker@rho:~$ bladeRF-cli -d *:instance=0 -e info
Board: bladerf1
Serial #: [redacted]
VCTCXO DAC calibration: 0x9004
FPGA size: 115 KLE
FPGA loaded: yes
USB bus: 4
USB address: 17
USB speed: SuperSpeed
Backend: libusb
Instance: 0
rtucker@rho:~$ bladeRF-cli -d *:instance=1 -e info
Board: bladerf2
Serial #: [redacted]
VCTCXO DAC calibration: 0x1ffc
FPGA size: Unknown
FPGA loaded: no
USB bus: 4
USB address: 16
USB speed: SuperSpeed
Backend: libusb
Instance: 1
source: bladerf_open() documentation at https://www.nuand.com/bladeRF-doc/libbl ... a59cdb6a24The general form of the device identifier string is;
An empty ("") or NULL device identifier will result in the first encountered device being opened (using the first discovered backend)Code: Select all
<backend>:[device=<bus>:<addr>] [instance=<n>] [serial=<serial>]
The 'backend' describes the mechanism used to communicate with the device, and may be one of the following:
*: Any available backend
libusb: libusb (See libusb changelog notes for required version, given your OS and controller)
cypress: Cypress CyUSB/CyAPI backend (Windows only)
If no arguments are provided after the backend, the first encountered device on the specified backend will be opened. Note that a backend is required, if any arguments are to be provided.
Next, any provided arguments are provide as used to find the desired device. Be sure not to over constrain the search. Generally, only one of the above is required – providing all of these may over constrain the search for the desired device (e.g., if a serial number matches, but not on the specified bus and address.)
device=<bus>:<addr>: Specifies USB bus and address. Decimal or hex prefixed by '0x' is permitted.
instance=<n>: Nth instance encountered, 0-indexed
serial=<serial>: Device's serial number.
Rey Tucker (she/her)
Systems Engineer, Nuand LLC
Rochester, NY, USA
#WontBeErased
Systems Engineer, Nuand LLC
Rochester, NY, USA
#WontBeErased