f4exb
5ad63b7376
XTRX: refactored GPS lock test using workaround using change in 1PPS iterval clock counts. Fixes hanging for 1PPS signal
2019-01-20 00:52:57 +01:00
f4exb
989dbc28b6
REST API examples: added randomize_colors.py in the readme
2019-01-18 01:15:12 +01:00
f4exb
918e42e8c5
Updated XTRX documentation and Debian changelog
2019-01-18 00:45:19 +01:00
f4exb
89de799d52
Fixed compiler warning
2019-01-17 11:22:38 +01:00
f4exb
bfaaf2e1d3
Make the settings location appear in the log and in the about panel of the GUI also
2019-01-17 11:17:28 +01:00
f4exb
dbf5fb895e
Print the settings path at the beginning of the main window or main core constructor
2019-01-17 08:52:57 +01:00
f4exb
3826b1faeb
XTRX fixes (2)
2019-01-17 01:27:07 +01:00
f4exb
5109253d8b
SDRPlay: fixed REST API settings PUT and PATCH
2019-01-17 01:01:59 +01:00
f4exb
83883efcb5
Fixed missing display settings of transverted data where missing
2019-01-16 21:28:35 +01:00
f4exb
0ac871cb5c
Removed detailed compilation instructions in the main readme that are now in the Wiki
2019-01-16 02:38:42 +01:00
f4exb
8d4dc0c8ff
XTRX output: REST API fixes
2019-01-16 01:56:43 +01:00
f4exb
919c88b0ce
XTRX: REST API fixes
2019-01-16 00:37:27 +01:00
f4exb
7603848bbe
AirspyHF: updated documentation
2019-01-15 00:40:41 +01:00
f4exb
69b8aaa482
SerialDV: corrected cmake find module and improved main window error messages for SerialDV support
2019-01-14 23:41:24 +01:00
f4exb
cdfc72a859
REST API examples: Added a randomize channel colors utility as a way to answer to issue #275
2019-01-14 18:34:44 +01:00
f4exb
a0478d0f73
AirspyHF: implemented local DC and IQ imbalance corrections
2019-01-14 09:25:08 +01:00
f4exb
013e512948
AirspyHF: new settings
2019-01-14 02:36:33 +01:00
f4exb
932048dba0
SoapySDR: added try/catch blocks around calls to SoapySDR interface methods where missing
2019-01-13 23:33:31 +01:00
f4exb
00ca85c0bf
On preset load match on serial or driver id for SoapySDR devices
2019-01-13 22:09:45 +01:00
f4exb
46e92e41dc
REST API: fixed reverse API address setting
2019-01-13 11:35:31 +01:00
f4exb
b0a1f97fbc
FCD Pro+: fixed request mapper with correct hardware ID
2019-01-13 02:18:59 +01:00
f4exb
a9aac62617
FCD fixes for REST API
2019-01-12 23:34:11 +01:00
f4exb
0215839220
REST API: implement reverse API settings (3)
2019-01-11 14:45:00 +01:00
f4exb
3e096580b0
REST API: implement reverse API settings (2)
2019-01-11 08:50:47 +01:00
f4exb
6e0be2d122
REST API: implement reverse API settings (1). Bump version
2019-01-10 22:35:38 +01:00
f4exb
68e109193f
Test source: fixed reverse API address update from REST API
2019-01-10 15:45:03 +01:00
f4exb
0b93512771
BladeRF input: fixed GUI display device settings
2019-01-09 22:42:14 +01:00
f4exb
b148073db4
Windows MSVC build fixes
2019-01-07 17:51:18 +01:00
f4exb
4c1e2a26cc
Remove XTRX from Debian build
2019-01-05 17:51:52 +01:00
f4exb
26aab263e0
FCD: Decimation and Fc Pos REST API implementations
2019-01-05 10:07:25 +01:00
f4exb
b68eceb635
FCD: fixed documentation
2019-01-05 01:07:15 +01:00
f4exb
12484199b9
FCD: added documentation
2019-01-05 01:04:26 +01:00
f4exb
65e7519cd1
FCD: added decimation and center frequency shift
2019-01-05 00:31:16 +01:00
f4exb
050ae9d2e8
FCD: implemented decimation
2019-01-04 15:12:35 +01:00
f4exb
b5a7425f1e
PlutoSDR: some minor changes to pull request #269 (Get LO range from device) and get Tx LO range also from device
2019-01-04 11:23:54 +01:00
f4exb
01269ac07e
Merge pull request #269 from rgetz/pluto_get_LO_range
...
pluto: Get LO range from device
2019-01-04 10:51:22 +01:00
f4exb
680c584fe0
Device engines: unified some debug messages
2019-01-04 10:49:47 +01:00
f4exb
a5c2de87a8
XTRX: corrected debug message
2019-01-04 10:49:15 +01:00
f4exb
9beeb45a05
XTRX output: more restrictions documented
2019-01-04 10:48:33 +01:00
f4exb
b1d1d3c5e0
XTRX: fixed apply settigns loop in case NCO is used on both channels. Refactored debug messages
2019-01-04 10:47:34 +01:00
f4exb
7173032645
XTRX: updated documentation with real time scheduling tricks and other minor updates
2019-01-04 05:09:55 +01:00
f4exb
733f3d4ba4
XTRX: make clock gen setting consistent
2019-01-04 04:45:52 +01:00
Robin Getz
333273b3cb
pluto: Get LO range from device
...
When updating firmware, the devices which have AD9364s on them, get
reset to the default of a AD9363 (tuning range of 325 to 3800 MHz).
SDRAngel assumes a AD9364, and the GUI allows you to set LO settings
that the firmware doesn't support.
This ensures that does not happen, by going out to the hardware, and
querying the device to set the min/max limits on LO.
Signed-off-by: Robin Getz <robin.getz@analog.com>
2019-01-03 12:46:40 -05:00
f4exb
e3069d3a69
XTRX: updated documentation
2019-01-03 14:58:15 +01:00
f4exb
bbec66c662
XTRX: fixes for better stability
2019-01-03 13:08:11 +01:00
f4exb
3b648609db
XTRX: GUI cosmetic changes
2019-01-03 13:07:17 +01:00
f4exb
7a6ecc41bc
XTRX output: take better settings defaults
2019-01-03 13:06:06 +01:00
f4exb
56102acc96
XTRX: set block size back to 8k
2019-01-03 13:05:11 +01:00
f4exb
cf4b90f3ae
cmake files cleanup and build simplification
2019-01-02 21:33:45 +01:00
f4exb
70970d7b7a
XTRX input: added documentation and refactored cmake files for XTRX
2019-01-02 19:13:50 +01:00