Page 1 of 1

Implementing simple frequency hopping

Posted: Fri Jul 03, 2015 2:15 am
by itay
Hello guys,
I'm searching for any suggestion for implementing frequncy hopping between 4-5 totally diffrent frequencies via GNU radio?

Thanks,
Itay

Re: Implementing simple frequency hopping

Posted: Sat Jul 04, 2015 10:37 am
by itay
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

Re: Implementing simple frequency hopping

Posted: Wed Aug 15, 2018 8:30 am
by alexlitv
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

Re: Implementing simple frequency hopping

Posted: Wed Aug 22, 2018 11:32 am
by rtucker
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.:

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
Here's the options:
The general form of the device identifier string is;

Code: Select all

<backend>:[device=<bus>:<addr>] [instance=<n>] [serial=<serial>]
An empty ("") or NULL device identifier will result in the first encountered device being opened (using the first discovered backend)

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.
source: bladerf_open() documentation at https://www.nuand.com/bladeRF-doc/libbl ... a59cdb6a24