| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
user to see, with brevity.
|
| |
|
|\ |
|
| |
| |
| |
| | |
Signed-off-by: Moritz Fischer <moritz.fischer@ettus.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Moritz Fischer <moritz.fischer@ettus.com>
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
- It's status is thrown away anyway
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
- Implemented IOCTL macro for linux and macosx
- Refactored v1 and v2 proxy code
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
- b200: compat 10
- e300: compat 10
- x300: compat 14
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Patch addresses issue:
#742 "tx_waveforms seems to produce unexpectedly large image"
Tx Quad Cal performance is temporally dependent with better results
when run after the AD9361 is configured for transmission than at
initialization. This gets is roughly 5-10 dB of additional quadrature
image suppression.
Even better performance can be reached when Tx Quad Cal is run
after streaming and the AD9361 is actively transmitting. Calibration
in this state, however, requires user intervention by retuning the
transmit chain by > 100 MHz. Total IQ suppression should be in the
range of 40-50+ dBFS dependent on operating frequency.
Signed-off-by: Tom Tsou <tom.tsou@ettus.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Patch addresses issue:
#872 "B200: Tx and Rx calibration share same frequency state"
ADI specifies recalibration for certain paths when the LO shifts by
more than 100 MHz. Tx and Rx maintain independent LO frequencies so
use separate values for determining whether to perform re-calibration
at tuning intervals.
Also, maintain last calibration frequencies from initialization and
clock rate changes. Doing so prevents a re-calibration if the first
requested Tx or Rx frequency is close to the default values of
850 and 800 MHz respectively.
Signed-off-by: Tom Tsou <tom.tsou@ettus.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Addressed and related issues:
#186 "B200: Catalina RX signal distortion"
#821 "Incorrect behavior with auto DC Offset correction turnned off"
#820 "Rx DC Offset Correction Convergence on B2xx Dependent on Master Clock Rate"
#755 "Demodulate IQ signal amplitude oscillation on B210 at 200 MHz carrier"
Due to recent change "ad9361: Invert phase on Rx LNA bypass path", we
now have uniform phase alignment across the entire gain range. This
drastically improves performance of RF DC tracking - not to be confused
with the - active and input dependent - baseband (BB) DC tracking loop.
RF DC tracking is not affected by input signals and updates during gain
changes. The updated configuration provides improved DC suppression for
operation whether BB tracking loop is enabled or disabled.
New behavior differs from the previous case where disabling BB tracking
would clear all - static and active - calibration tables. Now, static
correction tables are not wiped when BB tracking is turned off.
Signed-off-by: Tom Tsou <tom.tsou@ettus.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Patch provides an alternative resolution to issue #807
"B210: severe distortion on In-phase data for some gain settings"
Rx quadrature tracking, an active input-sensitive loop, causes problems
on a handful of receive signals. Problematic signals include pulsed GMSK
and near-DC tones among others.
As an alternative, improve operation when active tracking is disabled.
Run single shot quadrature calibration at the following events to provide
calibrated image suppression. The corrections without active tracking are
not input dependent.
Rx quadrature single shot calibration points:
1. AD9361 initialization
2. Clock rate change
3. Tuning differences greater then 100 MHz when tracking is disabled
Note that if tracking is enabled (default case), this patch has no effect
during streaming. Only the non-default (user set) case is affected.
Signed-off-by: Tom Tsou <tom.tsou@ettus.com>
|
| |
| |
| |
| |
| |
| | |
X300 stops sending packets when too many overruns occur. This presumably
happens due to a lock up in the source flow control. In this patch we
force a flow control update every time an overrun occurs.
|
| |
| |
| |
| |
| | |
- Included list header in soft_reg header
- Fixed typo in x300_impl
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
* Cleaned up usage of handles vs. handle pointers
* Store global string for last error thrown
* Removed uhd::device_addr_t handle, added std::vector<std::string> handle
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
exception handling which uses uhd::usb_error (not uhd::runtime_error).
|
| | |
| | |
| | |
| | |
| | |
| | | |
set LibUHD to required
* If required component's dependencies aren't met, CMake will throw an error unless user specifically disables it
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
- Added UHD_USRP_MULTI_USRP_REGISTER_API
- Added UHD_USRP_MULTI_USRP_FILTER_API
|
|\| | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Resolves issue #890
"E300: Does not transmit on master"
Fixes GPIO register mismatch introduced by c2827e9a0b.
"x300, e300: Moved common register names to radio namespace"
With register correction, transmit and LED behaviour performs as
expected.
Signed-off-by: Tom Tsou <tom.tsou@ettus.com>
|
| | | |
|
| | | |
|