1
0
mirror of https://github.com/f4exb/sdrangel.git synced 2024-11-16 13:21:50 -05:00
Commit Graph

3210 Commits

Author SHA1 Message Date
f4exb
4fe16095d4 Rename SDRDaemonSource device plugin to RemoteInput (1) 2019-02-03 00:26:26 +01:00
f4exb
ffb766b42d Rename SDRDaemonSink device plugin to RemoteOutput (2): REST API 2019-02-02 23:27:34 +01:00
f4exb
ad66b4af49 Rename SDRDaemonSink device plugin to RemoteOutput (1) 2019-02-02 22:58:42 +01:00
Robin Getz
95edff4985 plutosdr: grab the RF bandwidth range from the device
This will use the RF bandwidth from the device, which is different
between AD9363 and AD9364.

Things are now managed like the device likes - analog low pass bandwidth
is RF (complex) bandwidth, not baseband single I or Q bandwidth.

Signed-off-by: Robin Getz <robin.getz@analog.com>
2019-02-01 16:42:08 -05:00
f4exb
4372938b15 Windows build: fixed SoapySDR build 2019-01-27 13:21:12 +01:00
f4exb
6fb6cc4dc4 Windows build: fixed rtlsdr build 2019-01-27 10:41:10 +01:00
f4exb
c294f0a017 Migration of DaemonSource channel to RemoteSource 2019-01-23 00:44:13 +01:00
f4exb
5b04cf4b5a Migration of DaemonSink channel to RemoteSink 2019-01-22 23:39:12 +01:00
f4exb
e5b23e9864 Voice type modulators: corrected documentation on sound file input format 2019-01-22 13:30:54 +01:00
f4exb
918e42e8c5 Updated XTRX documentation and Debian changelog 2019-01-18 00:45:19 +01:00
f4exb
3826b1faeb XTRX fixes (2) 2019-01-17 01:27:07 +01:00
f4exb
83883efcb5 Fixed missing display settings of transverted data where missing 2019-01-16 21:28:35 +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
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
46e92e41dc REST API: fixed reverse API address setting 2019-01-13 11:35:31 +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
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
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
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
f4exb
73a32a8cd7 XTRX output 2019-01-02 15:35:43 +01:00
f4exb
93f64eee70 Merge branch 'master' into dev 2019-01-01 19:00:07 +01:00
f4exb
3374892c61 XTRX input: implemented REST API interfaces 2019-01-01 18:28:53 +01:00
ZigaS
747c0c3cda Depyloyment scrip update, QT project updates for OSX environment 2019-01-01 15:30:20 +01:00
f4exb
61baf75471 XTRX input: MI to SI transition fixes 2019-01-01 10:55:20 +01:00
f4exb
a9211ac298 XTRX input: separate settings for channels A and B including NCO 2018-12-31 21:05:19 +01:00
f4exb
7c8a2120e6 XTRX input: basic MIMO working 2018-12-31 20:22:42 +01:00