kopia lustrzana https://github.com/f4exb/sdrangel
Fix spelling using ispell
Daniele Forsi
rodzic
1989b1ac17
commit
794be61957
|
|
@ -41,5 +41,5 @@ We are interested to find out how other people make use of this software.
|
|||
* Please list Center Frequency, bandwidth and any other applicable RF settings that are pertinent to the issue.
|
||||
|
||||
### Log Files
|
||||
* Please read any pertinant log files!
|
||||
* Please read any pertinent log files!
|
||||
* Attach any relevant information you find here.
|
||||
|
|
|
|||
|
|
@ -114,13 +114,13 @@ See the principle of operation section below for optimum scope settings.
|
|||
|
||||
<h4>C.1.1 Port side incoming wave</h4>
|
||||
|
||||
The red arrow shows the direction of the incoming wave assuming it is ccoming from the port side of the antenna system (antenna 1 to 2). The value in degrees is displayed in (C.2).
|
||||
The red arrow shows the direction of the incoming wave assuming it is coming from the port side of the antenna system (antenna 1 to 2). The value in degrees is displayed in (C.2).
|
||||
|
||||
This also corresponds to positive angles in the trigonometric sense with respect to the antenna baseline.
|
||||
|
||||
<h4>C.1.2 Starboard side incoming wave</h4>
|
||||
|
||||
The green arrow shows the direction of the incoming wave assuming it is ccoming from the starboard side of the antenna system (antenna 1 to 2). The value in degrees is displayed in (C.3).
|
||||
The green arrow shows the direction of the incoming wave assuming it is coming from the starboard side of the antenna system (antenna 1 to 2). The value in degrees is displayed in (C.3).
|
||||
|
||||
This also corresponds to negative angles in the trigonometric sense with respect to the antenna baseline.
|
||||
|
||||
|
|
@ -134,7 +134,7 @@ The darker area on the compass background shows the sector where no readings can
|
|||
|
||||
<h3>C.2 Positive DOA angle (Port side)</h3>
|
||||
|
||||
Displays the posiive azimuth in degrees with respect to antenna direction of the incoming wave. This corresponds to the port side with respect to the antenna system from antenna 1 to antenna 2. This direction is displayed with a red arrow on the compass (1).
|
||||
Displays the positive azimuth in degrees with respect to antenna direction of the incoming wave. This corresponds to the port side with respect to the antenna system from antenna 1 to antenna 2. This direction is displayed with a red arrow on the compass (1).
|
||||
|
||||
<h3>C.3 Negative DOA angle (Starboard side)</h3>
|
||||
|
||||
|
|
@ -168,13 +168,13 @@ This is the number of FFT series used for DOA calculation thus the weighting ave
|
|||
|
||||
<h2>Principle of operation</h2>
|
||||
|
||||
DOA estimation is based on the "FFT" correlation function and active only when selected with (A.2). FFT analysis helps in removing non essential contributions and is more efficient than simple product wutn conjugate (A.B*).
|
||||
DOA estimation is based on the "FFT" correlation function and active only when selected with (A.2). FFT analysis helps in removing non essential contributions and is more efficient than simple product with conjugate (A.B*).
|
||||
|
||||
It assumes that channel A is connected to antenna 1 or antenna of reference (device stream 0) and channel B is connected antenna 2 the second antenna (device stream 1) in the following configuration:
|
||||
|
||||
|
||||
|
||||
<h3>Configuring the scope dsisplay</h3>
|
||||
<h3>Configuring the scope display</h3>
|
||||
|
||||
The scope shall be configured to have X and Y displays with Y1 set to a magnitude display projection and X to a phase related projection. See scope controls in B section for setup. Here are the different possibilities:
|
||||
- **X**: Phi, DOAP, DOAN
|
||||
|
|
@ -204,7 +204,7 @@ In general the angle can be calculated from the baseline distance D (distance be
|
|||
φ = π D cos(θ) / (λ/2) ⇒
|
||||
cos(θ) = (φ / π) . ((λ/2) / D)
|
||||
|
||||
If D is larger than λ/2 the possible values of cos(θ) do not cover the whole [-1:1] interval and thus there is a blind sector at the front of antenna 2 and the back of antenna 1 which is shown on the compass as a darker area (C.1.4). However signals coming from this blind sector will fold into the valid sector. Putting antennas further apart than λ/2 can give more accurate measurements inside the valid sector at the condition you already validated the assunption that the incoming wave angle is inside the valid sector and that no significant signal from the blind sector can influence the masurement. One can imagine having a pair of directive antennas placed at a distance for which the valid sector matches the antenna system lobe for final accurate measurement.
|
||||
If D is larger than λ/2 the possible values of cos(θ) do not cover the whole [-1:1] interval and thus there is a blind sector at the front of antenna 2 and the back of antenna 1 which is shown on the compass as a darker area (C.1.4). However signals coming from this blind sector will fold into the valid sector. Putting antennas further apart than λ/2 can give more accurate measurements inside the valid sector at the condition you already validated the assumption that the incoming wave angle is inside the valid sector and that no significant signal from the blind sector can influence the measurement. One can imagine having a pair of directive antennas placed at a distance for which the valid sector matches the antenna system lobe for final accurate measurement.
|
||||
|
||||
If D is smaller than λ/2 extreme incoming angles (0 or π) yield smaller φ which will be compensated by the (λ/2) / D factor however with less accuracy.
|
||||
|
||||
|
|
@ -224,7 +224,7 @@ For best results the antenna system should be clear of possible reflectors inclu
|
|||
|
||||
<h3>Device settings</h3>
|
||||
|
||||
The actual connections to RF ports depends on each device to get the angles right. BladeRF and Pluto+ have constant corrections and do not require calibration for each new masurement. This is not the case of LimeSDR USB or XTRX however and it makes them not practical for this application.
|
||||
The actual connections to RF ports depends on each device to get the angles right. BladeRF and Pluto+ have constant corrections and do not require calibration for each new measurement. This is not the case of LimeSDR USB or XTRX however and it makes them not practical for this application.
|
||||
|
||||
Known corrections and connections for some devices:
|
||||
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ Use this combo to select which (complex) signal to use as the display source:
|
|||
|
||||
<h3>7: Locked loop</h3>
|
||||
|
||||
Locks a PLL or FLL on the signal and mixes its NCO with the input signal. This is mostly useful for carrier recovery on PSK modulations (PLL is used). This effectively de-rotates the signal and symbol points (constellation) can be seen in XY mode with real part as X and imagiary part as Y.
|
||||
Locks a PLL or FLL on the signal and mixes its NCO with the input signal. This is mostly useful for carrier recovery on PSK modulations (PLL is used). This effectively de-rotates the signal and symbol points (constellation) can be seen in XY mode with real part as X and imaginary part as Y.
|
||||
|
||||
When the PLL is locked the icon lights up in green. The frequency shift from carrier appears in the tooltip. Locking indicator is pretty sharp with about +/- 100 Hz range. The FLL has no indicator.
|
||||
|
||||
|
|
@ -122,7 +122,7 @@ Average total power in dB relative to a +/- 1.0 amplitude signal received in the
|
|||
|
||||
<h3>10. Toggle root raised cosine filter</h3>
|
||||
|
||||
Use this toggle button to activate or de-activate the root raised cosine (RRC) filter. When active the bnadpass boxcar filter is replaced by a RRC filter. This takes effect only in normal (DSB) mode (see control 14).
|
||||
Use this toggle button to activate or de-activate the root raised cosine (RRC) filter. When active the bandpass boxcar filter is replaced by a RRC filter. This takes effect only in normal (DSB) mode (see control 14).
|
||||
|
||||
<h3>11. Tune RRC filter rolloff factor</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -46,13 +46,13 @@ This specifies the channel sample rate the demodulator uses. Values of 2M-12MSa/
|
|||
|
||||
Checking the S button will enable demodulation of Mode-S ELS (Elementary Surveillance), EHS (Enhanced Surveillance) and MRAR (Meteorological Routine Air Report) frames.
|
||||
|
||||
<h3>7: FP - Correlate Against Full Preamable</h3>
|
||||
<h3>7: FP - Correlate Against Full Preamble</h3>
|
||||
|
||||
When the FP button is checked, the demodulator will correlated the received signal against all expected 8 bits of the ES1090 preamble. When unchecked, the correlation will only be against the first 6 bits. Only correlating the first 6 bits can reduce the processing requirements, but may result in more invalid frames.
|
||||
|
||||
<h3>8: Threshold</h3>
|
||||
|
||||
This sets the correlation threshold in dB between the received signal and expected 1090ES preamble, that is required to be exceeded before the demodulator will try to decode a frame. Lower values should decode more frames amd will require more processing power, but will more often decode invalid frames. You may also look at correlation values obtained with reliable signals in the "Correlation" column of the data table.
|
||||
This sets the correlation threshold in dB between the received signal and expected 1090ES preamble, that is required to be exceeded before the demodulator will try to decode a frame. Lower values should decode more frames and will require more processing power, but will more often decode invalid frames. You may also look at correlation values obtained with reliable signals in the "Correlation" column of the data table.
|
||||
|
||||
<h3>9: Download Opensky-Network Aircraft Database</h3>
|
||||
|
||||
|
|
@ -86,7 +86,7 @@ Clicking the Display Settings button will open the Display Settings dialog, whic
|
|||
* Whether demodulator statistics are displayed (primarily an option for developers).
|
||||
* Whether the columns in the table are automatically resized after an aircraft is added to it. If unchecked, columns can be resized manually and should be saved with presets.
|
||||
|
||||
You can also enter an [avaiationstack](https://aviationstack.com/product) API key, needed to download flight information (such as departure and arrival airports and times).
|
||||
You can also enter an [aviationstack](https://aviationstack.com/product) API key, needed to download flight information (such as departure and arrival airports and times).
|
||||
|
||||
A [CheckWX](https://www.checkwxapi.com/) API key can be entered in order to download airport weather (METARs) which can be displayed on the map.
|
||||
|
||||
|
|
@ -287,7 +287,7 @@ The table displays the decoded ADS-B and Mode-S data for each aircraft along sid
|
|||
* Updated - The local time at which the last message was received. (ADS-B / Mode-S)
|
||||
* RX Frames - A count of the number of frames received from this aircraft. (ADS-B / Mode-S)
|
||||
* TIS-B - A count of the number of TIS-B frames for this aircraft. (ADS-B)
|
||||
* Correlation - Displays the minimum, average and maximum of the preamable correlation in dB for each received frame. These values can be used to help select a threshold setting. This correlation value is the ratio between the presence and absence of the signal corresponding to the "ones" and the "zeros" of the sync word adjusted by the bits ratio. It can be interpreted as a SNR estimation.
|
||||
* Correlation - Displays the minimum, average and maximum of the preamble correlation in dB for each received frame. These values can be used to help select a threshold setting. This correlation value is the ratio between the presence and absence of the signal corresponding to the "ones" and the "zeros" of the sync word adjusted by the bits ratio. It can be interpreted as a SNR estimation.
|
||||
* RSSI - This Received Signal Strength Indicator is based on the signal power during correlation estimation. This is the power sum during the expected presence of the signal i.e. the "ones" of the sync word.
|
||||
* Flight status - scheduled, active, landed, cancelled, incident or diverted. (API)
|
||||
* Dep - Departure airport. (API)
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ This plugin can be used to demodulate AIS (Automatic Identification System) mess
|
|||
|
||||
AIS is broadcast globally on 25kHz channels at 161.975MHz and 162.025MHz, with other frequencies being used regionally or for special purposes. This demodulator is single channel, so if you wish to decode multiple channels simultaneously, you will need to add one AIS demodulator per frequency. As most AIS messages are on 161.975MHz and 162.025MHz, you can set the center frequency as 162MHz, with a sample rate of 100k+Sa/s, with one AIS demod with an input offset -25kHz and another at +25kHz.
|
||||
|
||||
The AIS demodulators can send received messages to the [AIS feature](../../feature/ais/readme.md), which displays a table combining the latest data for vessels amalgamated from multiple demodulators and sends their positiosn to the [Map Feature](../../feature/map/readme.ais) for display in 2D or 3D.
|
||||
The AIS demodulators can send received messages to the [AIS feature](../../feature/ais/readme.md), which displays a table combining the latest data for vessels amalgamated from multiple demodulators and sends their positions to the [Map Feature](../../feature/map/readme.ais) for display in 2D or 3D.
|
||||
|
||||
AIS uses GMSK/FM modulation at a baud rate of 9,600, with a modulation index of 0.5. The demodulator works at a sample rate of 57,600Sa/s.
|
||||
|
||||
|
|
@ -97,4 +97,4 @@ The received messages table displays information about each AIS message received
|
|||
* Hex - The message in hex format.
|
||||
* Slot - Time slot (0-2249). Due to SDR to SDRangel latency being unknown, this is likely to have some offset.
|
||||
|
||||
Right clicking on the table header allows you to select which columns to show. The columns can be reorderd by left clicking and dragging the column header. Right clicking on an item in the table allows you to copy the value to the clipboard.
|
||||
Right clicking on the table header allows you to select which columns to show. The columns can be reordered by left clicking and dragging the column header. Right clicking on an item in the table allows you to copy the value to the clipboard.
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ When the PLL is locked the icon lights up in green. The frequency shift from car
|
|||
|
||||
<h3>3: DSB/SSB selection</h2>
|
||||
|
||||
Use the left mouse button to toggle DSB/SSB operation. Soemtimes one of the two sidebands is affected by interference. Selecting SSB may help by using only the sideband without interference. Right click to open a dialog to select which sideband is used (LSB or USB).
|
||||
Use the left mouse button to toggle DSB/SSB operation. Sometimes one of the two sidebands is affected by interference. Selecting SSB may help by using only the sideband without interference. Right click to open a dialog to select which sideband is used (LSB or USB).
|
||||
|
||||
<h3>4: Channel power</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -71,7 +71,7 @@ This includes:
|
|||
- Whether to automatically save images on LOS.
|
||||
- Whether a combined image including telemetry should be saved.
|
||||
- Whether separate images of channel A and B, without telemetry, should be saved.
|
||||
- Whether equidistant cylindrical (plate carr<EFBFBD>e) project images used for the map, should be saved.
|
||||
- Whether equidistant cylindrical (plate carrée) project images used for the map, should be saved.
|
||||
- Path to save automatically saved images in.
|
||||
- The minimum number of scanlines required to be in an image, after noise cropping, for it to be automatically saved.
|
||||
- After how many scanlines image processing is applied and updates sent to the map. Lower values require more CPU power.
|
||||
|
|
|
|||
|
|
@ -92,7 +92,7 @@ For FM choose the algorithm that best suits your conditions.
|
|||
|
||||
☞ only FM3 is accurate with regard to FM deviation (see 10).
|
||||
|
||||
⚠ in AM modes (also USB and LSB) there is an automatic amplitude scaling so that the video signal fits in the 0.0 to 1.0 range. For synchronziation standards other than HSkip (see B.3) it may be difficult for the system to find the appropriate level when the standard changes or the signal power changes abruptly. In this case you have to select HSkip (B.3) until the video signal reaches the 0.0 to 1.0 range approximately (use scope tab see C) before returning to the desired standard.
|
||||
⚠ in AM modes (also USB and LSB) there is an automatic amplitude scaling so that the video signal fits in the 0.0 to 1.0 range. For synchronization standards other than HSkip (see B.3) it may be difficult for the system to find the appropriate level when the standard changes or the signal power changes abruptly. In this case you have to select HSkip (B.3) until the video signal reaches the 0.0 to 1.0 range approximately (use scope tab see C) before returning to the desired standard.
|
||||
|
||||
⚠ USB and LSB modes are experimental and do not show good results for sample rates greater than 1 MS/s. Adjusting the BFO can be picky and unstable.
|
||||
|
||||
|
|
|
|||
|
|
@ -46,7 +46,7 @@ This is the power of the reconstructed stereo pilot signal.
|
|||
|
||||
<h3>A.7: Toggle RDS decoding</h3>
|
||||
|
||||
USe this button to activate or de-activate RDS decoding
|
||||
Use this button to activate or de-activate RDS decoding
|
||||
|
||||
<h3>A.8: Level meter in dB</h3>
|
||||
|
||||
|
|
@ -120,7 +120,7 @@ Shows counters of received message by type.
|
|||
- **EWS**: Emergency Warning System (C.19)
|
||||
- **EON**: Enhanced Other Networks information (C.24, 25, 26, 27)
|
||||
|
||||
<h3>C.8: Proram Identification</h3>
|
||||
<h3>C.8: Program Identification</h3>
|
||||
|
||||
The ¨PI" label lights up if a PI message is received.
|
||||
|
||||
|
|
|
|||
|
|
@ -137,13 +137,13 @@ You can suspend and resume decoding activity using this button. This is useful i
|
|||
|
||||
This is used to determine the end of message automatically. It can be de-activated by turning the button completely to the right (as shown on the picture). In this case it relies on the message length set with (A.4).
|
||||
|
||||
During paylaod detection the maximum power value in the FFT (at argmax) P<sub>max</sub> is stored and compared to the current argmax power value P<sub>i</sub> if S<sub>EOM</sub> is this squelch value the end of message is detected if S<sub>EOM</sub> × S<sub>i</sub> < S<sub>max</sub>
|
||||
During payload detection the maximum power value in the FFT (at argmax) P<sub>max</sub> is stored and compared to the current argmax power value P<sub>i</sub> if S<sub>EOM</sub> is this squelch value the end of message is detected if S<sub>EOM</sub> × S<sub>i</sub> < S<sub>max</sub>
|
||||
|
||||
<h4>A.4: Expected message length in symbols</h4>
|
||||
|
||||
This is the expected number of symbols in a message. When a header is present in the payload it should match the size given in the header (A.11).
|
||||
|
||||
<h4>A.5: Auto mesasge length</h4>
|
||||
<h4>A.5: Auto message length</h4>
|
||||
|
||||
LoRa mode only. Set message length (A.4) equal to the number of symbols specified in the message just received. When messages are sent repeatedly this helps adjusting in possible message length changes automatically.
|
||||
|
||||
|
|
|
|||
|
|
@ -73,7 +73,7 @@ The current program area display information about the currently playing program
|
|||
|
||||
<h3>Statistics</h3>
|
||||
|
||||
The statistics areas displays statistics generated by the demodulator that may give an indiciation of the quality of the received signal.
|
||||
The statistics areas displays statistics generated by the demodulator that may give an indication of the quality of the received signal.
|
||||
|
||||
If you are hearing dropouts in audio, try adjusting your antenna in order to improve the reported SNR.
|
||||
|
||||
|
|
|
|||
|
|
@ -206,7 +206,7 @@ String is in the form: `02223297>G00000222`
|
|||
|
||||
|
||||
|
||||
<h5>A11.3.1: dPMR frame tyoe</h5>
|
||||
<h5>A11.3.1: dPMR frame type</h5>
|
||||
|
||||
- `--`: undetermined
|
||||
- `HD`: Header of FS1 type
|
||||
|
|
|
|||
|
|
@ -164,7 +164,7 @@ The file name is constructed as follows where date is the day date in YYYYMMDD f
|
|||
|
||||
<date>_d<device index>c<channel index>.txt
|
||||
|
||||
Files will be stored in the system application data location in the `ft8/logs` folder. The application dat location depends on the O/S:
|
||||
Files will be stored in the system application data location in the `ft8/logs` folder. The application data location depends on the O/S:
|
||||
|
||||
- Linux: ~/.local/share/f4exb/SDRangel
|
||||
- Windows: C:\Users\<your user>\AppData\Local\f4exb\SDRangel
|
||||
|
|
@ -272,7 +272,7 @@ This restores the default band preset values:
|
|||
- **17m**: 18100 kHz
|
||||
- **15m**: 21074 kHz
|
||||
- **12m**: 24915 kHz
|
||||
- **10m**: 28074 kHZ
|
||||
- **10m**: 28074 kHz
|
||||
- **6m**: 50313 kHz
|
||||
- **4m**: 70100 kHz
|
||||
- **2m**: 144120 kHz
|
||||
|
|
|
|||
|
|
@ -211,7 +211,7 @@ The airport ICAO (purple box) and runway (yellow box) can be entered in (11).
|
|||
|
||||
|
||||
Next, we need to enter the latitude (8), longitude (9) and elevation (10) of the runway threshold. This is available on some charts (orange box), but not usually accurately enough to line up perfectly on the 3D map.
|
||||
For this, it's best to use the 3D map, and git statu click while holding shift at the start of the threshold to set a marker, which will display the coordinates.
|
||||
For this, it's best to use the 3D map, and click while holding shift at the start of the threshold to set a marker, which will display the coordinates.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -197,7 +197,7 @@ Shows status information on the decoder:
|
|||
|
||||
<h4>C1.8.1: Transition constellation or symbol synchronization signal toggle</h4>
|
||||
|
||||
For now this is ineffective and only transition consellation is available.
|
||||
For now this is ineffective and only transition constellation is available.
|
||||
|
||||
<h4>C1.8.2: Trace length</h4>
|
||||
|
||||
|
|
@ -306,7 +306,7 @@ There are 4 combinations and therefore 4 possible diagrams:
|
|||
|
||||
|
||||
|
||||
As expected the values decay with time if no more errors are receeived. Note that in BER mode the vertical axis has a logarithmic scale which is more convenient for BER values. The minor ticks are set at tenths of the major ticks intervals
|
||||
As expected the values decay with time if no more errors are received. Note that in BER mode the vertical axis has a logarithmic scale which is more convenient for BER values. The minor ticks are set at tenths of the major ticks intervals
|
||||
|
||||
<h4>Current error counts display</h4>
|
||||
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ When checked, writes all received messages to a .csv file, specified by (14).
|
|||
|
||||
<h3>14: .csv Log Filename</h3>
|
||||
|
||||
Click to specify the name of the .csv file which received messasges are logged to.
|
||||
Click to specify the name of the .csv file which received messages are logged to.
|
||||
|
||||
<h3>15: Read Data from .csv File</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -187,7 +187,7 @@ Use the checkbox to toggle DCS activation. When activated it will look for a squ
|
|||
|
||||
<h3>C.5: DCS code</h3>
|
||||
|
||||
This is the DCS code to be selected among the normalized values. The value is in octal format suffixed by "P" for positive or normal codes and "N" for negative or inverted codes. The values are those listed [here](http://onfreq.com/syntorx/dcs.html). The special value `--` desactivates the squelch but the DCS code is still searched.
|
||||
This is the DCS code to be selected among the normalized values. The value is in octal format suffixed by "P" for positive or normal codes and "N" for negative or inverted codes. The values are those listed [here](http://onfreq.com/syntorx/dcs.html). The special value `--` deactivates the squelch but the DCS code is still searched.
|
||||
|
||||
<h3>C.6: Show positive or negative code</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ Click to open the character encoding dialog, which allows a mapping from the rec
|
|||
|
||||
|
||||
|
||||
Each row contains a mapping from a 7-bit value to a Unicode code point. Values should be entered in hexideicmal
|
||||
Each row contains a mapping from a 7-bit value to a Unicode code point. Values should be entered in hexadecimal
|
||||
|
||||
<h3>10: Find</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ This plugin can be used to demodulate RS41 radiosonde weather balloon signals. R
|
|||
|
||||
RS41 radiosondes transmit data frames every second, containing position, velocity and PTU (Pressure, Temperature and Humidity) readings. The radios use GFSK modulation, with <20>2.4kHz deviation at 4,800 baud. Reed Solomon encoding is used for ECC (Error Checking and Correction).
|
||||
|
||||
The Radiosonde demodulator can forward received data to the [Radiosone feature](../../feature/radiosonde/readme.md), which can plot charts showing how altitude and PTU vary over time, and also plot the position of the radiosonde on the 2D and 3D maps.
|
||||
The Radiosonde demodulator can forward received data to the [Radiosonde feature](../../feature/radiosonde/readme.md), which can plot charts showing how altitude and PTU vary over time, and also plot the position of the radiosonde on the 2D and 3D maps.
|
||||
|
||||
<h2>Interface</h2>
|
||||
|
||||
|
|
@ -80,7 +80,7 @@ The received frames table displays information about each radiosonde frame recei
|
|||
|
||||
* Date - The date the frame was received.
|
||||
* Time - The time the frame was received.
|
||||
* Serial - The serial number of the radiosonde. Double clicking on this column will search for the radiosone on https://sondehub.org/
|
||||
* Serial - The serial number of the radiosonde. Double clicking on this column will search for the radiosonde on https://sondehub.org/
|
||||
* Frame - Frame number
|
||||
* Phase - Flight phase: On ground, Ascent and Descent.
|
||||
* Lat (<28>) - Latitude in degrees, North positive. Double clicking on this column will search for the radiosonde on the Map.
|
||||
|
|
@ -103,6 +103,6 @@ The received frames table displays information about each radiosonde frame recei
|
|||
* GPS Time - GPS date and time on board radiosonde. GPS time is offset 18 seconds from UTC.
|
||||
* GPS Sats - Number of GPS satellites used in position estimate.
|
||||
* ECC - Number of symbol errors corrected by Reed Solomon ECC.
|
||||
* Corr - Premable correlation value calculated for the frame. This can be used to choose a value for TH (6).
|
||||
* Corr - Preamble correlation value calculated for the frame. This can be used to choose a value for TH (6).
|
||||
|
||||
Right clicking on the table header allows you to select which columns to show. The columns can be reorderd by left clicking and dragging the column header. Right clicking on an item in the table allows you to copy the value to the clipboard.
|
||||
Right clicking on the table header allows you to select which columns to show. The columns can be reordered by left clicking and dragging the column header. Right clicking on an item in the table allows you to copy the value to the clipboard.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
This plugin can be used to demodulate RTTY (Radioteletype) transmissions.
|
||||
RTTY uses BFSK (Binary Frequency Shift Keying), where transmission of data alternates between two frequencies,
|
||||
the mark frequency and the space frequency. The RTTY Demodulor should be centered in between these frequencies.
|
||||
the mark frequency and the space frequency. The RTTY Demodulator should be centered in between these frequencies.
|
||||
The baud rate, frequency shift (difference between mark and space frequencies), bandwidth and baudot character set are configurable.
|
||||
|
||||
<h2>Interface</h2>
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
<h2>Introduction</h2>
|
||||
|
||||
This plugin can be used to demodulate VOR (VHF omnidirectional range) navaids (navigation aids). VORs are radio naviation aids in the VHF 108 - 117.975MHz band commonly used for aircraft navigation.
|
||||
This plugin can be used to demodulate VOR (VHF omnidirectional range) navaids (navigation aids). VORs are radio navigation aids in the VHF 108 - 117.975MHz band commonly used for aircraft navigation.
|
||||
|
||||
VORs transmit two 30Hz signals, one AM at the VOR center frequency and one FM on a 9960Hz sub-carrier. The FM reference signal's phase is set so 0 degrees corresponds to magnetic north from the VOR (Some VORs at high latitudes use true North). The phase of the AM variable signal is such that the phase difference to the reference signal corresponds to the bearing from the VOR to the receiver. For example, if a receiver is North from the VOR, the AM and FM 30Hz signals will be received in phase. If a receiver is East from the VOR, the phase difference will be 90 degrees.
|
||||
|
||||
|
|
@ -68,7 +68,7 @@ Magnitude of the received 30Hz FM reference signal in dB.
|
|||
|
||||
<h3>10. Variable signal power in dB</h3>
|
||||
|
||||
Mangitude of the received 30Hz AM variable signal in dB.
|
||||
Magnitude of the received 30Hz AM variable signal in dB.
|
||||
|
||||
<h3>11. VOR identifier code (decoded)</h3>
|
||||
|
||||
|
|
@ -76,4 +76,4 @@ Demodulated identifier. If an identifier is received that is not 2 or 3 characte
|
|||
|
||||
<h3>12. VOR identifier code (Morse)</h3>
|
||||
|
||||
Demodulated Morse code identifier. Colour coding is the ame as for the decoded identifier.
|
||||
Demodulated Morse code identifier. Colour coding is the same as for the decoded identifier.
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
<h2>Introduction</h2>
|
||||
|
||||
This plugin can be used to demodulate VOR (VHF omnidirectional range) navaids (navigation aids). VORs are radio naviation aids in the VHF 108 - 117.975MHz band commonly used for aircraft navigation.
|
||||
This plugin can be used to demodulate VOR (VHF omnidirectional range) navaids (navigation aids). VORs are radio navigation aids in the VHF 108 - 117.975MHz band commonly used for aircraft navigation.
|
||||
|
||||
VORs transmit two 30Hz signals, one AM at the VOR center frequency and one FM on a 9960Hz sub-carrier. The FM reference signal's phase is set so 0 degrees corresponds to magnetic north from the VOR (Some VORs at high latitudes use true North). The phase of the AM variable signal is such that the phase difference to the reference signal corresponds to the bearing from the VOR to the receiver. For example, if a receiver is North from the VOR, the AM and FM 30Hz signals will be received in phase. If a receiver is East from the VOR, the phase difference will be 90 degrees.
|
||||
|
||||
|
|
@ -64,19 +64,19 @@ The VOR table displays information about selected VORs. To select or deselect a
|
|||
|
||||
* Name - The name of the VOR. For example: 'LONDON'.
|
||||
* Freq (MHz) - The center frequency the VOR transmits on in MHz.
|
||||
* Offset (kHz) - This is the current difference between the VOR's center frequency and SDRangle's device center frequency. If displayed in red, the VOR is out of range and it's signal will not be able to be received.
|
||||
* Offset (kHz) - This is the current difference between the VOR's center frequency and SDRangel's device center frequency. If displayed in red, the VOR is out of range and its signal will not be able to be received.
|
||||
* Ident - A 2 or 3 character identifier for the VOR. For example: 'LON'.
|
||||
* Morse - The Morse code identifier for the VOR. For example: '.-.. --- -.'
|
||||
* RX Ident - This contains the demodulated ident. If it matches the expected ident, it will be displayed in green, if not, it will be displayed in red. If an ident is received that is not 2 or 3 characters, it will not be displayed, but the last received ident will be displayed in yellow.
|
||||
* RX Morse - This contains the demodulated Morse code ident. Colour coding is as for RX Ident.
|
||||
* Radial - This contains the demodulated radial direction in degrees (unadjusted for magnetic declination). If there is a low confidence the value is correct (due to a weak signal), it will be displayed in red.
|
||||
* Ref (dB) - This displays the magnitude of the received 30Hz FM reference signal in dB.
|
||||
* Var (dB) - This displays the mangitude of the received 30Hz AM variable signal in dB.
|
||||
* Var (dB) - This displays the magnitude of the received 30Hz AM variable signal in dB.
|
||||
* Mute - This button allows you to mute or unmute the audio from the corresponding VOR.
|
||||
|
||||
<h3>Map</h3>
|
||||
|
||||
The map displays the locations of each VOR, with an information box containing the information about the VOR, such as it's name, frequency, ident (in text and Morse), range and magnetic declination.
|
||||
The map displays the locations of each VOR, with an information box containing the information about the VOR, such as its name, frequency, ident (in text and Morse), range and magnetic declination.
|
||||
|
||||
To initialise the VORs on the map, first set your position using the Preferences > My position menu, then open the VOR Demodulator channel (close and reopen it, if already open). Then press the Download VOR Database button (This only needs to be performed once). The map should then display VORs in your vicinity.
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ Each recording is written in a new file with the starting timestamp before the `
|
|||
- Given file name: `test.sdriq` then a recording file will be like: `test.2020-08-05T21_39_07_974.sdriq`
|
||||
- Given file name: `test.2020-08-05T20_36_15_974.sdriq` then a recording file will be like (with timestamp updated): `test.2020-08-05T21_41_21_173.sdriq`
|
||||
- Given file name: `test.first.sdriq` then a recording file will be like: `test.2020-08-05T22_00_07_974.sdriq`
|
||||
- Given file name: `record.test.first.sdriq` then a recording file will be like: `reocrd.test.2020-08-05T21_39_52_974.sdriq`
|
||||
- Given file name: `record.test.first.sdriq` then a recording file will be like: `record.test.2020-08-05T21_39_52_974.sdriq`
|
||||
|
||||
If a filename is given without `.sdriq` extension then the `.sdriq` extension is appended automatically before the above algorithm is applied.
|
||||
If a filename is given with an extension different of `.sdriq` or `.wav` then the extension is replaced by `.sdriq` automatically before the above algorithm is applied.
|
||||
|
|
@ -48,7 +48,7 @@ This is the total recording time for the session.
|
|||
|
||||
This is the total number of bytes recorded for the session.The number is possibly suffixed by a multiplier character:
|
||||
- **k**: _kilo_ for kilobytes
|
||||
- **M**: _mega_ for meabytes
|
||||
- **M**: _mega_ for megabytes
|
||||
- **G**: _giga_ for gigabytes
|
||||
|
||||
<h3>7: Fixed frequency shift positions</h3>
|
||||
|
|
@ -95,7 +95,7 @@ The button turns red if recording is active.
|
|||
|
||||
<h3>14: Select output file</h3>
|
||||
|
||||
Use this button to open a file dialog that lets you specify the location and name of the output files. Please refer to the indtroduction at the top of this page for details on how the recording file name is composed from the given file name.
|
||||
Use this button to open a file dialog that lets you specify the location and name of the output files. Please refer to the introduction at the top of this page for details on how the recording file name is composed from the given file name.
|
||||
|
||||
The file path currently being written (or last closed) appears at the right of the button.
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Both manual and automatic controls are active at the same time and the user can
|
|||
|
||||
To change the frequency manually use the wheels to adjust the frequency shift in Hz from the center frequency of reception. Left click on a digit sets the cursor position at this digit. Right click on a digit sets all digits on the right to zero. This effectively floors value at the digit position. Wheels are moved with the mousewheel while pointing at the wheel or by selecting the wheel with the left mouse click and using the keyboard arrows. Pressing shift simultaneously moves digit by 5 and pressing control moves it by 2.
|
||||
|
||||
<h3>2: Instantateous tracker error</h2>
|
||||
<h3>2: Instantaneous tracker error</h2>
|
||||
|
||||
This is the instantaneous frequency error in Hz. It is activated as soon as the FLL or PLL tracker is selected (7.3) regardless of the tracking activation (7.1)
|
||||
|
||||
|
|
@ -85,7 +85,7 @@ This is the order of m-ary PSK modulation for the PLL. It can be selected in pow
|
|||
|
||||
<h3>7.5 Toggle root raised cosine filter</h3>
|
||||
|
||||
Use this toggle button to activate or de-activate the root raised cosine (RRC) filter. When active the bnadpass boxcar filter is replaced by a RRC filter. This takes effect only in normal (DSB) mode (see control 14).
|
||||
Use this toggle button to activate or de-activate the root raised cosine (RRC) filter. When active the bandpass boxcar filter is replaced by a RRC filter. This takes effect only in normal (DSB) mode (see control 14).
|
||||
|
||||
<h3>7.6 Tune RRC filter rolloff factor</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
This plugin can be used to generate a heat map based on RF channel power. Channel power is measured as average power, maximum peak power, minimum peak power as well as pulse average power (i.e. average power above a threshold).
|
||||
|
||||
To view the Heat Map visually, the [Map Feature](../../feature/map/readme.md) should be opened. If using the 3D map, it is recommended to set the Terrain to Ellisoid (as the heat map is 2D).
|
||||
To view the Heat Map visually, the [Map Feature](../../feature/map/readme.md) should be opened. If using the 3D map, it is recommended to set the Terrain to Ellipsoid (as the heat map is 2D).
|
||||
|
||||
To record data for a heat map, a GPS is required, and Preferences > My Position should have "Auto-update from GPS" enabled.
|
||||
|
||||
|
|
@ -53,7 +53,7 @@ Sets the sample rate at which channel power is sampled and measured. Values rang
|
|||
|
||||
<h3>7: Tavg - Average Time</h3>
|
||||
|
||||
Time period overwhich the channel power is averaged. Values range from 10us to 10s in powers of 10. The available values depend upon the sample rate.
|
||||
Time period over which the channel power is averaged. Values range from 10us to 10s in powers of 10. The available values depend upon the sample rate.
|
||||
|
||||
<h3>8: THp - Pulse Threshold</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ Use this button to start or stop processing.
|
|||
|
||||
<h4>A.7.3: DSP functions</h4>
|
||||
|
||||
Togles DSP functions (gain and FFT filter)
|
||||
Toggles DSP functions (gain and FFT filter)
|
||||
|
||||
<h4>A.7.4: Gain</h4>
|
||||
|
||||
|
|
@ -113,9 +113,9 @@ Displays the index of the selected FFT band. Displays "0" if no FFT bands are av
|
|||
|
||||
This is the relative position to the center of the passband of the lower bound of the FFT band. The actual frequency shift from center is displayed on the right.
|
||||
|
||||
<h3>A.12: FFT band relative bandwidth or higher boumd</h3>
|
||||
<h3>A.12: FFT band relative bandwidth or higher bound</h3>
|
||||
|
||||
This is the relative badnwidth of the FFT band. The value displayed on the right is either the bandwidth or the higher frequency band depending on the (A.13) button setting.
|
||||
This is the relative bandwidth of the FFT band. The value displayed on the right is either the bandwidth or the higher frequency band depending on the (A.13) button setting.
|
||||
|
||||
<h3>A.13: Toggle bandwidth or higher frequency bound</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -251,7 +251,7 @@ Specifies the baseline used for calculating Tsource from Tsys. This can be:
|
|||
|
||||
<h3>1.25: delta G / G - Gain Variation</h3>
|
||||
|
||||
delta G / G specifies the gain variation of the LNA / receiver. Gain variation places a limit on the sensitvity improvement available by increased integration counts.
|
||||
delta G / G specifies the gain variation of the LNA / receiver. Gain variation places a limit on the sensitivity improvement available by increased integration counts.
|
||||
This value is only used for the estimation of sigma_Tsys0 and sigma_Ssys0, it does not affect any measurements.
|
||||
|
||||
<h3>1.26: HPBW / Omega A</h3>
|
||||
|
|
@ -507,7 +507,7 @@ Allows the user to scroll through and select the recorded spectra, showing the d
|
|||
Specifies the rest frequency of the reference spectral line:
|
||||
|
||||
- HI neutral hydrogen at 1420.405760MHz.
|
||||
- OH hydroxyl at 1612.231040Mhz.
|
||||
- OH hydroxyl at 1612.231040MHz.
|
||||
- DI neutral deuterium at 327.384MHz.
|
||||
- Custom allows a user-defined frequency in MHz to be entered.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Such files can be read in SDRangel using the [SigMF file input plugin](../../sam
|
|||
|
||||
As per SigMF specifications two files are created in fact.
|
||||
- One with `.sigmf-meta` extension contains meta data and details to find the different captures in the data file blob. It is written in JSON format and is human readable. You can refer to SigMF documentation in the link at top to read about the details.
|
||||
- Another with `.sigmf-data` contains the IQ data as a blob indexed by structures in the `.sigmf-meta` file. Thus to the SigMF file reader data appears as a sequence of captures having idependent start time and length, center frequency and with SDRangel specific extensions independent sample rates.
|
||||
- Another with `.sigmf-data` contains the IQ data as a blob indexed by structures in the `.sigmf-meta` file. Thus to the SigMF file reader data appears as a sequence of captures having independent start time and length, center frequency and with SDRangel specific extensions independent sample rates.
|
||||
|
||||
If a filename is given without `.sigmf-meta` extension then the `.sigmf-meta` extension is appended automatically.
|
||||
If a filename is given with an extension different of `.sigmf-meta` then the extension is replaced by `.sigmf-meta` automatically.
|
||||
|
|
@ -49,7 +49,7 @@ This is the current recording time of the whole file (all captures)
|
|||
|
||||
This is the total number of bytes including all captures. This corresponds to the size of the `.sigmf-data` file. The number is possibly suffixed by a multiplier character:
|
||||
- **k**: _kilo_ for kilobytes
|
||||
- **M**: _mega_ for meabytes
|
||||
- **M**: _mega_ for megabytes
|
||||
- **G**: _giga_ for gigabytes
|
||||
|
||||
<h3>7: Fixed frequency shift positions</h3>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
This plugin draws I/Q samples from a Local Output plugin device sink in another device set into the baseband. It is basically the same as the Remote Source channel plugin but pipes the samples internally instead of receiving them over the network.
|
||||
|
||||
It may be used when you want to use a particular sub area of the baseband for madulation.
|
||||
It may be used when you want to use a particular sub area of the baseband for modulation.
|
||||
|
||||
Note that because it uses only the channelizer half band filter chain to achieve interpolation and center frequency shift you have a limited choice on the center frequencies that may be used (similarly to the Remote Source). The available center frequencies depend on the baseband sample rate, the channel interpolation and the filter chain that is used so you have to play with these parameters to obtain a suitable center frequency and pass band.
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ Use this button to toggle mute for this channel.
|
|||
|
||||
<h3>4: PHY</h3>
|
||||
|
||||
This specifies the parameters of the PHY (physical layer), including the bit rate and modulation that is used for the frame transmission. Supported PHYs are 20kbps BPSK, 40kbps BPSK, 100kpbs <1GHZ O-QPSK, 250kpbs <1GHz O-QPSK and 250kbps 2.4GHz O-QPSK.
|
||||
This specifies the parameters of the PHY (physical layer), including the bit rate and modulation that is used for the frame transmission. Supported PHYs are 20kbps BPSK, 40kbps BPSK, 100kpbs <1GHz O-QPSK, 250kpbs <1GHz O-QPSK and 250kbps 2.4GHz O-QPSK.
|
||||
These 802.15.4 PHYs use DSSS (Direct sequence spread spectrum), whereby multiple chips are transmitted per symbol. This means that a high baseband sample rate and large RF bandwidth is required. The baseband sample rate should be set to an integer multiple of the chip rate (at least 4x).
|
||||
Each PHY is applicable only for specific frequency bands as detailed below:
|
||||
|
||||
|
|
|
|||
|
|
@ -111,7 +111,7 @@ Use this button to stop sending text. When resuming keying restarts at the start
|
|||
|
||||
12.7: Activate morse keys keyboard control
|
||||
|
||||
This disables text or continuous dots or dashes. Toggle input from keyboard. Occasionnaly the focus may get lost and you will have to deactivate and reactivate it to recover the key bindings.
|
||||
This disables text or continuous dots or dashes. Toggle input from keyboard. Occasionally the focus may get lost and you will have to deactivate and reactivate it to recover the key bindings.
|
||||
|
||||
12.8: Iambic or straight
|
||||
|
||||
|
|
|
|||
|
|
@ -127,25 +127,25 @@ This is a LoRa specific feature and is also known as explicit (with header) or i
|
|||
|
||||
<h4>10.5: My callsign (QSO mode)</h4>
|
||||
|
||||
Enter your callsign so it can populate message palceholders (See next)
|
||||
Enter your callsign so it can populate message placeholders (See next)
|
||||
|
||||
<h4>10.6: Your callsign (QSO mode)</h4>
|
||||
|
||||
Enter the other party callsign so it can populate message palceholders (See next)
|
||||
Enter the other party callsign so it can populate message placeholders (See next)
|
||||
|
||||
<h4>10.7: My locator (QSO mode)</h4>
|
||||
|
||||
Enter your Maidenhead QRA locator so it can populate message palceholders (See next)
|
||||
Enter your Maidenhead QRA locator so it can populate message placeholders (See next)
|
||||
|
||||
<h4>10.8: My report (QSO mode)</h4>
|
||||
|
||||
Enter the signal report you will send to the other party so it can populate message palceholders (See next)
|
||||
Enter the signal report you will send to the other party so it can populate message placeholders (See next)
|
||||
|
||||
<h4>10.9: Message selector</h4>
|
||||
|
||||
This lets you choose which pre-formatted message to send:
|
||||
|
||||
- **None**: empty message. In fact this is used to make a transition to trigger sending of the sa,e ,essage again. It is used internally by the "play" button (11) and can be used with the REST API.
|
||||
- **None**: empty message. In fact this is used to make a transition to trigger sending of the same message again. It is used internally by the "play" button (11) and can be used with the REST API.
|
||||
- **Beacon**: a beacon message
|
||||
- **CQ**: (QSO mode) CQ general call message
|
||||
- **Reply**: (QSO mode) reply to a CQ call
|
||||
|
|
|
|||
|
|
@ -120,7 +120,7 @@ Use this button to stop sending text. When resuming keying restarts at the start
|
|||
|
||||
10.7: Activate morse keys keyboard control
|
||||
|
||||
This disables text or continuous dots or dashes. Toggle input from keyboard. Occasionnaly the focus may get lost and you will have to deactivate and reactivate it to recover the key bindings.
|
||||
This disables text or continuous dots or dashes. Toggle input from keyboard. Occasionally the focus may get lost and you will have to deactivate and reactivate it to recover the key bindings.
|
||||
|
||||
10.8: Iambic or straight
|
||||
|
||||
|
|
|
|||
|
|
@ -141,7 +141,7 @@ This is a special mode for Bit Error Rate Testing. In this mode only a synchroni
|
|||
|
||||
Panels corresponding to each available packet type are arranged in a tabbed setup. Tabs can be selected with icons on the right. These are:
|
||||
|
||||
- **SMS**: SMS data with the chat icon. Selects SMS packet tyoe.
|
||||
- **SMS**: SMS data with the chat icon. Selects SMS packet type.
|
||||
- **APRS**: APRS data with the world icon. Selects APRS packet type.
|
||||
|
||||
<h3>C.6.1: SMS data</h3>
|
||||
|
|
@ -158,9 +158,9 @@ Selected with the tab with word icon (bottom most). Selecting this tab will set
|
|||
|
||||
|
||||
|
||||
<h4>C.6.2.1: From idnetifier</h4>
|
||||
<h4>C.6.2.1: From identifier</h4>
|
||||
|
||||
This is the "FROM" of APRS message and usuaiiy is the station callsign followed by a dash and a numeric suffix.
|
||||
This is the "FROM" of APRS message and usually is the station callsign followed by a dash and a numeric suffix.
|
||||
|
||||
<h4>C.6.2.2: Add location data</h4>
|
||||
|
||||
|
|
@ -184,7 +184,7 @@ Arbitrary data payload to be added to the APRS message. As per APRS standard it
|
|||
|
||||
<h3>D.1: Baud rate</h3>
|
||||
|
||||
Only the standard 4.8 kBaud rate is available. This is a provision for possible future experimnentations.
|
||||
Only the standard 4.8 kBaud rate is available. This is a provision for possible future experimentations.
|
||||
|
||||
<h3>D.2: Source call</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -96,7 +96,7 @@ When changing the RF bandwidth the channel spacing selection in the combo box is
|
|||
|
||||
<h3>5: Audio Filters</h3>
|
||||
|
||||
- The slider controls the bandwidth in khz of the modulating signal filtered before modulation.
|
||||
- The slider controls the bandwidth in kHz of the modulating signal filtered before modulation.
|
||||
- The "P" switch button next activates or de-activates pre-emphasis (fixed 120 μs)
|
||||
- The rightmost button next activates or de-activates 300 Hz highpass filter when no CTCSS nor DCS is active
|
||||
|
||||
|
|
@ -211,7 +211,7 @@ Use this button to stop sending text. When resuming keying restarts at the start
|
|||
|
||||
18.7: Activate morse keys keyboard control
|
||||
|
||||
This disables text or continuous dots or dashes. Toggle input from keyboard. Occasionnaly the focus may get lost and you will have to deactivate and reactivate it to recover the key bindings.
|
||||
This disables text or continuous dots or dashes. Toggle input from keyboard. Occasionally the focus may get lost and you will have to deactivate and reactivate it to recover the key bindings.
|
||||
|
||||
18.8: Iambic or straight
|
||||
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ Adjusts the gain in dB from -60 to 0dB. The gain should be set to ensure the lev
|
|||
|
||||
Enter your amateur radio callsign and optionally a sub-station ID (SSID). E.g. M7RCE or M7RCE-1
|
||||
|
||||
<h3>10: Preemphaisis Filter</h3>
|
||||
<h3>10: Preemphasis Filter</h3>
|
||||
|
||||
Check this button to enable a FM preemphasis filter, which amplifies higher frequencies. Right click to open the dialog to adjust settings for the filter.
|
||||
|
||||
|
|
|
|||
|
|
@ -200,7 +200,7 @@ Use this button to stop sending text. When resuming keying restarts at the start
|
|||
|
||||
16.7: Activate morse keys keyboard control
|
||||
|
||||
This disables text or continuous dots or dashes. Toggle input from keyboard. Occasionnaly the focus may get lost and you will have to deactivate and reactivate it to recover the key bindings.
|
||||
This disables text or continuous dots or dashes. Toggle input from keyboard. Occasionally the focus may get lost and you will have to deactivate and reactivate it to recover the key bindings.
|
||||
|
||||
16.8: Iambic or straight
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ This is the bandwidth in kHz of the channel signal filtered after modulation. It
|
|||
|
||||
<h3>6: Audio frequency bandwidth</h3>
|
||||
|
||||
This is the bandwidth in khz of the modulating signal filtered before modulation. It can be set in kHz steps from 1 to 20 kHz
|
||||
This is the bandwidth in kHz of the modulating signal filtered before modulation. It can be set in kHz steps from 1 to 20 kHz
|
||||
|
||||
<h3>7: Frequency deviation</h3>
|
||||
|
||||
|
|
@ -115,7 +115,7 @@ Use this button to stop sending text. When resuming keying restarts at the start
|
|||
|
||||
13.7: Activate morse keys keyboard control
|
||||
|
||||
This disables text or continuous dots or dashes. Toggle input from keyboard. Occasionnaly the focus may get lost and you will have to deactivate and reactivate it to recover the key bindings.
|
||||
This disables text or continuous dots or dashes. Toggle input from keyboard. Occasionally the focus may get lost and you will have to deactivate and reactivate it to recover the key bindings.
|
||||
|
||||
13.8: Iambic or straight
|
||||
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ The vessels table displays the current status for each vessel, base station or a
|
|||
* Updated - Gives the date and time the last message was received.
|
||||
* Messages - Displays the number of messages received.
|
||||
|
||||
Right clicking on the table header allows you to select which columns to show. The columns can be reorderd by left clicking and dragging the column header.
|
||||
Right clicking on the table header allows you to select which columns to show. The columns can be reordered by left clicking and dragging the column header.
|
||||
|
||||
Right clicking on a table cell allows you to copy the cell contents, view the vessel on a variety of websites or find the vessel on the map.
|
||||
|
||||
|
|
|
|||
|
|
@ -88,7 +88,7 @@ Each recording is written in a new file with the starting timestamp before the `
|
|||
- Given file name: `test.wav` then a recording file will be like: `test.2020-08-05T21_39_07_974.wav`
|
||||
- Given file name: `test.2020-08-05T20_36_15_974.wav` then a recording file will be like (with timestamp updated): `test.2020-08-05T21_41_21_173.wav`
|
||||
- Given file name: `test.first.wav` then a recording file will be like: `test.2020-08-05T22_00_07_974.wav`
|
||||
- Given file name: `record.test.first.eav` then a recording file will be like: `reocrd.test.2020-08-05T21_39_52_974.wav`
|
||||
- Given file name: `record.test.first.wav` then a recording file will be like: `record.test.2020-08-05T21_39_52_974.wav`
|
||||
|
||||
If a filename is given without `.wav` extension then the `.wav` extension is appended automatically before the above algorithm is applied. If a filename is given with an extension different of `.wav` then the extension is replaced by `.wav` automatically before the above algorithm is applied.
|
||||
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ For example, this allows an aircraft to be tracked, by setting the Source to the
|
|||
|
||||
<h3>5: Source</h3>
|
||||
|
||||
Specify the SDRangel Channel or Feature that that will control the target aziumth and elevation values, when Track (4) is checked.
|
||||
Specify the SDRangel Channel or Feature that that will control the target azimuth and elevation values, when Track (4) is checked.
|
||||
|
||||
<h3>6: Target</h3>
|
||||
|
||||
|
|
@ -76,12 +76,12 @@ The elevation offset specifies an angle in degrees that is added to the target e
|
|||
<h3>15 and 16: Azimuth Min and Max</h3>
|
||||
|
||||
The azimuth min and max values specify the minimum and maximum azimuth values (after offset has been applied), that will be sent to the rotator.
|
||||
These values can be used to prevent the rotator from rotating an antenna in to an obstable.
|
||||
These values can be used to prevent the rotator from rotating an antenna in to an obstacle.
|
||||
|
||||
<h3>17 and 18: Elevation Min and Max</h3>
|
||||
|
||||
The elevation min and max values specify the minimum and maximum elevation values (after offset has been applied), that will be sent to the rotator.
|
||||
These values can be used to prevent the rotator from rotating an antenna in to an obstable.
|
||||
These values can be used to prevent the rotator from rotating an antenna in to an obstacle.
|
||||
If the maximum elevation is set to 0, the controller will only use the M GS-232 command, rather than M and W.
|
||||
|
||||
<h3>19: Tolerance</h3>
|
||||
|
|
@ -103,7 +103,7 @@ Specifies the coordinate system used by the GUI for entry and display of the pos
|
|||
|
||||
* Az/El - For azimuth and elevation in degrees.
|
||||
* X/Y 85' - For X/Y coordinates in degrees. 0,0 is zenith. X is positive Southward. Y is positive Eastward.
|
||||
* X/Y 30' - For X/Y coordinates in degrees. 0,0 is zenith. X is positivie Eastward. Y is positive Northward.
|
||||
* X/Y 30' - For X/Y coordinates in degrees. 0,0 is zenith. X is positive Eastward. Y is positive Northward.
|
||||
|
||||
Equations for translating between these coordinate systems can be found [here](https://ntrs.nasa.gov/citations/19670030005).
|
||||
|
||||
|
|
|
|||
|
|
@ -52,7 +52,7 @@ It displays "D" when in device control or "C" when in channel control mode.
|
|||
|
||||
<h3>Contour devices</h3>
|
||||
|
||||
The Controur devices generally have a central "jog" wheel inside a spring loaded ring called the "shuttle" wheel plus a series of buttons.
|
||||
The Contour devices generally have a central "jog" wheel inside a spring loaded ring called the "shuttle" wheel plus a series of buttons.
|
||||
|
||||
<b>ShuttleXpress layout</b>
|
||||
|
||||
|
|
@ -95,7 +95,7 @@ The contour devices proceed by mapping their events to keyboard events and this
|
|||
|
||||
Contour provides software to perform the mapping on Windows. You just need to install the driver software downloaded from Contour web site, open the support program and then follow instructions. You will have to specify the target program when you create the profile for SDRangel. This is `sdrangel.exe` located in `C:\Program Files\SDRangel`. Note also that the buttons are named differently but the program shows their location on an interactive diagram so this should be no problem to identify them correctly.
|
||||
|
||||
When running on Linux ou may use [ShuttlePRO](https://github.com/nanosyzygy/ShuttlePRO) for keyboard mapping. It will work also for the ShuttleXpress with minor changes. You will have to identify the path of the Shuttle device and run the program with the device path as argument in a terminal. See the last section for details.
|
||||
When running on Linux you may use [ShuttlePRO](https://github.com/nanosyzygy/ShuttlePRO) for keyboard mapping. It will work also for the ShuttleXpress with minor changes. You will have to identify the path of the Shuttle device and run the program with the device path as argument in a terminal. See the last section for details.
|
||||
|
||||
<h4>Keyboard mapping</h4>
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
This plugin supports the [LimeRFE](https://github.com/myriadrf/LimeRFE) board. This board hosts a hardware power amplifier (PA) module with appropriate filtering and support circuitry to augment primarily but not only the LimeSDR, LimeSDR Mini, and LimeNET Micro platforms, providing a complete solution that addresses real life applications ranging from HAM radio to standards-compliant cellular network implementations.
|
||||
|
||||
As mentioned above it can be connected to a wide variety of SDR receivers and transmitters and this feature supports the synchronization with any receiver or trasmiiter device sets.
|
||||
As mentioned above it can be connected to a wide variety of SDR receivers and transmitters and this feature supports the synchronization with any receiver or transmitter device sets.
|
||||
|
||||
This plugin depends on [LimeSuite](https://github.com/myriadrf/LimeSuite) that should be available in your system in order to be compiled.
|
||||
|
||||
|
|
@ -12,7 +12,7 @@ This plugin depends on [LimeSuite](https://github.com/myriadrf/LimeSuite) that s
|
|||
|
||||
|
||||
|
||||
When starting you need first to open the LimeRFE device with button (2). You havr to select the appropriate serial device from (1). Note that all serial USB based devices are listed. You need to identify which one corresponds to the LimeRFE board you want to target.
|
||||
When starting you need first to open the LimeRFE device with button (2). You have to select the appropriate serial device from (1). Note that all serial USB based devices are listed. You need to identify which one corresponds to the LimeRFE board you want to target.
|
||||
|
||||
Once opened successfully (check status message in 6) you will apply the settings using the Apply button (5). Whenever the settings are changed this button lits in green showing that you may press it to update the board. Conversely the "to GUI" button (4) reads the settings from the board and updates the GUI.
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ On top of this, it can plot data from other plugins, such as:
|
|||
* Satellites from the Satellite Tracker,
|
||||
* Weather imagery from APT Demodulator,
|
||||
* The Sun, Moon and Stars from the Star Tracker,
|
||||
* Weather ballons from the RadioSonde feature,
|
||||
* Weather balloons from the RadioSonde feature,
|
||||
* RF Heat Maps from the Heap Map channel,
|
||||
* Radials and estimated position from the VOR localizer feature,
|
||||
* ILS course line and glide path from the ILS Demodulator.
|
||||
|
|
@ -206,7 +206,7 @@ Ionosonde data and MUF/coF2 contours from [KC2G](https://prop.kc2g.com/) with so
|
|||
Icons made by Google from Flaticon https://www.flaticon.com
|
||||
World icons created by turkkub from Flaticon https://www.flaticon.com
|
||||
|
||||
3D models are by various artists under a variety of liceneses. See: https://github.com/srcejon/sdrangel-3d-models
|
||||
3D models are by various artists under a variety of licenses. See: https://github.com/srcejon/sdrangel-3d-models
|
||||
|
||||
<h2>Creating 3D Models</h2>
|
||||
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ Specify the number of packets to transmit.
|
|||
Controls when the test is started, after the start button (1) is pressed. This can be either:
|
||||
|
||||
* Immediately
|
||||
* On satellite AOS (Acquistion of signal)
|
||||
* On satellite AOS (Acquisition of signal)
|
||||
* On satellite mid pass ((AOS-LOS)/2)
|
||||
|
||||
When either satellite option is selected, the Satellites field appears, allowing you to enter the names of satellites which should start the test.
|
||||
|
|
@ -42,7 +42,7 @@ Specify the interval in seconds between packet transmissions.
|
|||
|
||||
Specify the contents of the packet to transmit and expect to be received. Data should be entered in hexadecimal bytes (E.g: 00 11 22 33 44).
|
||||
|
||||
The exact format required will depend on the underlying protocol being used. For AX.25 using the Packet modulator, LoRo using the ChirpChat modulator, AIS and 802.15.4, it is not necessary to include the trailing CRC, as this is appended automatically by the SDRangel modulators.
|
||||
The exact format required will depend on the underlying protocol being used. For AX.25 using the Packet modulator, LoRa using the ChirpChat modulator, AIS and 802.15.4, it is not necessary to include the trailing CRC, as this is appended automatically by the SDRangel modulators.
|
||||
|
||||
Aside from hex values, a number of variables can be used:
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ based on data received via [Radiosonde Demodulators](../../channelrx/demodradios
|
|||
|
||||
The chart can plot two data series vs time for the radiosonde selected in the table.
|
||||
|
||||
The Radiosonde feature can draw ballons objects on the [Map](../../feature/map/readme.md) feature in 2D and 3D.
|
||||
The Radiosonde feature can draw balloons objects on the [Map](../../feature/map/readme.md) feature in 2D and 3D.
|
||||
|
||||
<h2>Interface</h2>
|
||||
|
||||
|
|
@ -36,13 +36,13 @@ The Radiosonde table displays the current status of each radiosonde, based on th
|
|||
* Updated - Gives the date and time the last message was received.
|
||||
* Messages - Displays the number of messages received.
|
||||
|
||||
Right clicking on the table header allows you to select which columns to show. The columns can be reorderd by left clicking and dragging the column header.
|
||||
Right clicking on the table header allows you to select which columns to show. The columns can be reordered by left clicking and dragging the column header.
|
||||
|
||||
Right clicking on a table cell allows you to copy the cell contents, or find the radiosonde on the map.
|
||||
|
||||
<h3>Map</h3>
|
||||
|
||||
The Radiosonde feature can plot ballons (during ascent) and parachutes (during descent) on the [Map](../../feature/map/readme.md).
|
||||
The Radiosonde feature can plot balloons (during ascent) and parachutes (during descent) on the [Map](../../feature/map/readme.md).
|
||||
To use, simply open a Map feature and the Radiosonde plugin will display objects based upon the data it receives from that point.
|
||||
Selecting a radiosonde item on the map will display a text bubble containing information from the above table.
|
||||
To centre the map on an item in the table, double click in the Lat or Lon columns.
|
||||
|
|
|
|||
|
|
@ -59,7 +59,7 @@ The Devices tab displays a list of devices that have been added to this Remote C
|
|||
* Press Remove to remove the selected device.
|
||||
* Press Edit... to edit settings for the selected device.
|
||||
* The up and down arrows move the selected device up or down in the list.
|
||||
The order of devices in the list determines the display order of the device's controls and senors in the Remote Control's GUI.
|
||||
The order of devices in the list determines the display order of the device's controls and sensors in the Remote Control's GUI.
|
||||
|
||||
<h3>Settings Tab</h3>
|
||||
|
||||
|
|
@ -80,7 +80,7 @@ The Home Assistant fields must be completed in order to discover devices connect
|
|||
|
||||
<h4>VISA Settings</h4>
|
||||
|
||||
* Resource filter - A regular expression of VISA resources not to attempt to open. This can be used to speed up VISA device discovery. As an example, devices using TCP and serial connections can be filted with: ^(TCPIP|ASRL). Leave the field empty to try to connect to all VISA devices.
|
||||
* Resource filter - A regular expression of VISA resources not to attempt to open. This can be used to speed up VISA device discovery. As an example, devices using TCP and serial connections can be filtered with: ^(TCPIP|ASRL). Leave the field empty to try to connect to all VISA devices.
|
||||
* Log I/O - Check to log VISA commands and responses to the SDRangel log file.
|
||||
|
||||
<h4>Devices Settings</h4>
|
||||
|
|
@ -94,7 +94,7 @@ The Home Assistant fields must be completed in order to discover devices connect
|
|||
|
||||
<h2>Device Dialog</h2>
|
||||
|
||||
The Device Dialog allows selecting devices to add to the Remote Control, as well as customing what controls and sensors are displayed for the device in the GUI.
|
||||
The Device Dialog allows selecting devices to add to the Remote Control, as well as customizing what controls and sensors are displayed for the device in the GUI.
|
||||
|
||||
|
||||
|
||||
|
|
@ -119,7 +119,7 @@ By default, real numbers are displayed to 1 decimal place. To increase this to 3
|
|||
|
||||
Checking the Plot column will result in a chart being drawn that plots sensor data versus time.
|
||||
All enabled sensors for a device will be plotted on the same chart.
|
||||
The Y Axis field below the table determines whether each series will have it's own Y axis (Per-sensor) or whether a single Y axis will be used for all series (Common).
|
||||
The Y Axis field below the table determines whether each series will have its own Y axis (Per-sensor) or whether a single Y axis will be used for all series (Common).
|
||||
|
||||
The Layout fields control how the Controls and Sensors will be laid-out in the GUI. This can be set to be either Horizontally or Vertically.
|
||||
|
||||
|
|
|
|||
|
|
@ -53,8 +53,8 @@ To perform an action on an SDRangel device set on AOS or LOS, press the "Add dev
|
|||
* Whether to stop acquisition on LOS.
|
||||
* Whether any file sinks in the preset should be started on AOS and stopped on LOS. This allows the baseband signal received from the satellite to be recorded to a file.
|
||||
* Whether to override the centre frequency in the preset. This allows a single preset to be used with multiple satellites.
|
||||
* A command or script to execute on AOS. See (8) for list of subsitituions.
|
||||
* A command or script to execute on LOS. See (8) for list of subsitituions.
|
||||
* A command or script to execute on AOS. See (8) for list of substitutions.
|
||||
* A command or script to execute on LOS. See (8) for list of substitutions.
|
||||
|
||||
Multiple tabs can be added, to allow independent control of multiple device sets. To remove a tab, click the cross next to the device set name in the tab list.
|
||||
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@ Pressing this button displays a settings dialog, that allows you to set:
|
|||
* Air pressure in millibars. This value can be automatically updated from OpenWeatherMap.
|
||||
* Air temperature in degrees Celsius. This value can be automatically updated from OpenWeatherMap.
|
||||
* Relative humidity in %. This value can be automatically updated from OpenWeatherMap.
|
||||
* Height above sea level in metres of the observation point (anntenna location).
|
||||
* Height above sea level in metres of the observation point (antenna location).
|
||||
* Temperature lapse rate in Kelvin per kilometre.
|
||||
* What data to display for the Solar flux measurement. Data can be selected from 2800 from DRAO or a number of different frequencies from Learmonth. Also, the Learmonth data can be linearly interpolated to the observation frequency set in the main window.
|
||||
* The units to display the solar flux in, either Solar Flux Units, Jansky or Wm^-2Hz-1. 1 sfu equals 10,000 Jansky or 10^-22 Wm^-2Hz-1.
|
||||
|
|
@ -151,7 +151,7 @@ An offset in degrees that is added to the computed target elevation.
|
|||
|
||||
When the target is set to Custom l/b, you specify the galactic longitude (angle in degrees, Eastward from the galactic centre) of the target object.
|
||||
|
||||
For all other target settings, this sisplays the calculated galactic longitude to the object.
|
||||
For all other target settings, this displays the calculated galactic longitude to the object.
|
||||
|
||||
<h3>21: b - Galactic Latitude</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -69,12 +69,12 @@ The VOR table displays information about selected VORs. To select or deselect a
|
|||
* RX Morse - This contains the demodulated Morse code ident. Colour coding is as for RX Ident.
|
||||
* Radial - This contains the demodulated radial direction in degrees (unadjusted for magnetic declination). If there is a low confidence the value is correct (due to a weak signal), it will be displayed in red.
|
||||
* Ref (dB) - This displays the magnitude of the received 30Hz FM reference signal in dB.
|
||||
* Var (dB) - This displays the mangitude of the received 30Hz AM variable signal in dB.
|
||||
* Var (dB) - This displays the magnitude of the received 30Hz AM variable signal in dB.
|
||||
* Mute - This button allows you to mute or unmute the audio from the corresponding VOR.
|
||||
|
||||
<h2>C: Map</h2>
|
||||
|
||||
The map displays the locations of each VOR, with an information box containing the information about the VOR, such as it's name, frequency, ident (in text and Morse), range and magnetic declination.
|
||||
The map displays the locations of each VOR, with an information box containing the information about the VOR, such as its name, frequency, ident (in text and Morse), range and magnetic declination.
|
||||
|
||||
To initialise the VORs on the map, first set your position using the Preferences > My position menu. Then press the Download VOR Database button (This only needs to be performed once). The map should then display VORs in your vicinity.
|
||||
|
||||
|
|
|
|||
|
|
@ -120,7 +120,7 @@ Use this toggle button to switch the sample rate input next (A.7) between device
|
|||
|
||||
This is the LMS7002M device to/from host stream sample rate or baseband sample rate in samples per second (S/s). The control (A.6) is used to switch between the two input modes. The device to/from host stream sample rate is the same for the Rx and Tx systems.
|
||||
|
||||
The limits are adjusted automatically. In baseband input mode the limits are driven by the decimation or intepolation factor (A.9). You may need to increase this factor to be able to reach lower values.
|
||||
The limits are adjusted automatically. In baseband input mode the limits are driven by the decimation or interpolation factor (A.9). You may need to increase this factor to be able to reach lower values.
|
||||
|
||||
Use the wheels to adjust the sample rate. Pressing shift simultaneously moves digit by 5 and pressing control moves it by 2. Left click on a digit sets the cursor position at this digit. Right click on a digit sets all digits on the right to zero. This effectively floors value at the digit position. Wheels are moved with the mousewheel while pointing at the wheel or by selecting the wheel with the left mouse click and using the keyboard arrows.
|
||||
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ This lets you compensate for the main oscillator frequency inaccuracy. Value is
|
|||
|
||||
<h4>8.1: Sample rate</h4>
|
||||
|
||||
This combo box lets you control the four pssible values for the device to host sample rate (Rx). Host to device (Tx) sample rate is fixed by design of the Metis interface at 48 kS/s:
|
||||
This combo box lets you control the four possible values for the device to host sample rate (Rx). Host to device (Tx) sample rate is fixed by design of the Metis interface at 48 kS/s:
|
||||
|
||||
- **48k**: 48000 samples per second
|
||||
- **96k**: 96000 samples per second
|
||||
|
|
|
|||
|
|
@ -150,7 +150,7 @@ Use this toggle button to switch the sample rate input next (A.7) between device
|
|||
|
||||
This is the LMS7002M device to/from host stream sample rate or baseband sample rate in samples per second (S/s). The control (A.6) is used to switch between the two input modes. The device to/from host stream sample rate is the same for the Rx and Tx systems.
|
||||
|
||||
The limits are adjusted automatically. In baseband input mode the limits are driven by the decimation or intepolation factor (A.9). You may need to increase this factor to be able to reach lower values.
|
||||
The limits are adjusted automatically. In baseband input mode the limits are driven by the decimation or interpolation factor (A.9). You may need to increase this factor to be able to reach lower values.
|
||||
|
||||
Use the wheels to adjust the sample rate. Pressing shift simultaneously moves digit by 5 and pressing control moves it by 2. Left click on a digit sets the cursor position at this digit. Right click on a digit sets all digits on the right to zero. This effectively floors value at the digit position. Wheels are moved with the mousewheel while pointing at the wheel or by selecting the wheel with the left mouse click and using the keyboard arrows.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
This output sample sink plugin sends its samples to a [LimeSDR device](https://myriadrf.org/projects/limesdr/).
|
||||
|
||||
<p>⚠ Version 18.04.1 of LimeSuite is used in the buildsand corresponding gateware loaded in the LimeSDR should be is used (2.16 for LimeSDR-USB and 1.24 for LimeSDR-Mini). If you compile from source version 18.04.1 of LimeSuite must be used.</p>
|
||||
<p>⚠ Version 18.04.1 of LimeSuite is used in the builds and corresponding gateware loaded in the LimeSDR should be is used (2.16 for LimeSDR-USB and 1.24 for LimeSDR-Mini). If you compile from source version 18.04.1 of LimeSuite must be used.</p>
|
||||
|
||||
<p>⚠ LimeSDR-Mini seems to have problems with Zadig driver therefore it is supported in Linux only.</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
<h2>Introduction</h2>
|
||||
|
||||
You can use this plugin to interface with a http server block in the Aaronia RTSA suite connected to a Spectran V6 device. It is assumed that you have prior knowledge of the Aaronia RTSA suite software and operation of the Spectran V6 RTSA (Real Time Spectrum Analyzer). However in this context there are some specificities i.e. it assumes that the "mission" (in RTSA suite terms) that is the equivalent of a "configuration" in SDRangel has a `HTTP Server` block preceded by a `IQ Demodulator` block (the equivalent of the "Frequency translating FIR filter" in GNU radio). The center frequency and span (equal to decimated sample rate) can be controlled from either RTSA sutie or SDRangel.
|
||||
You can use this plugin to interface with a http server block in the Aaronia RTSA suite connected to a Spectran V6 device. It is assumed that you have prior knowledge of the Aaronia RTSA suite software and operation of the Spectran V6 RTSA (Real Time Spectrum Analyzer). However in this context there are some specificities i.e. it assumes that the "mission" (in RTSA suite terms) that is the equivalent of a "configuration" in SDRangel has a `HTTP Server` block preceded by a `IQ Demodulator` block (the equivalent of the "Frequency translating FIR filter" in GNU radio). The center frequency and span (equal to decimated sample rate) can be controlled from either RTSA suite or SDRangel.
|
||||
|
||||
An example flow graph could be the following (with two http servers) hence two possible Aaronia receivers in SDRangel:
|
||||
|
||||
|
|
|
|||
|
|
@ -95,6 +95,6 @@ This appears to work only on HF band. Turns on or off the LNA (+6dB). Gain is co
|
|||
|
||||
This appears to work only on HF band and is active only if AGC is off (10). Attenuator value can be set from 0 to 48 dB in 6 dB steps.
|
||||
|
||||
<h3>13: LibaispyHF DSP</h3>
|
||||
<h3>13: LibairspyHF DSP</h3>
|
||||
|
||||
Turns on or off the libairspyhf DSP routines. When on the internal DC and IQ imbalance corrections (4) and (5) are useless and should be turned off.
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ This button opens a dialog to set the transverter mode frequency translation opt
|
|||
|
||||
<h3>7: Set default values</h3>
|
||||
|
||||
Use this oush button to force default reasonable values for all parameters below (8)
|
||||
Use this push button to force default reasonable values for all parameters below (8)
|
||||
|
||||
<h3>8: Parameters</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -88,7 +88,7 @@ The device stream from the HackRF is decimated to obtain the baseband stream. Po
|
|||
- **Inf**: the decimation operation takes place around Fs - Fc.
|
||||
- **Sup**: the decimation operation takes place around Fs + Fc.
|
||||
|
||||
With SR as the sample rate before decimation Fc is calculated depending on the decimaton factor:
|
||||
With SR as the sample rate before decimation Fc is calculated depending on the decimation factor:
|
||||
|
||||
- **2**: Fc = SR/4
|
||||
- **4**: Fc = 3*SR/8
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Stream I/Q sample rate in kS/s
|
|||
|
||||
<h3>5: Auto remove DC component</h3>
|
||||
|
||||
Filters out the possible DC component. You use this if yoy notice a spike in the center of the pass band.
|
||||
Filters out the possible DC component. You use this if you notice a spike in the center of the pass band.
|
||||
|
||||
<h3>6: Auto make I/Q balance</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ This string represents the sequence of half-band filters used in the decimation
|
|||
|
||||
<h3>7: Remote sink center frequency shift</h3>
|
||||
|
||||
This is the shift of the remote sink channel center frequency from the remte device center frequency. Its value is driven by the remote device sample rate, the decimation (5) and the filter chain sequence (8).
|
||||
This is the shift of the remote sink channel center frequency from the remote device center frequency. Its value is driven by the remote device sample rate, the decimation (5) and the filter chain sequence (8).
|
||||
|
||||
<h3>8: Remote sink half-band filter chain sequence</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -97,7 +97,7 @@ This selects the IF frequency between these values:
|
|||
|
||||
- **0 for zero IF**
|
||||
- 450 kHz.
|
||||
- Move center frequency by -450 kHZ (3).
|
||||
- Move center frequency by -450 kHz (3).
|
||||
- Direct frequency reading is -450 kHz off from real Rx frequency.
|
||||
- You may use the transverter mode (7) with a shift of +450 kHz to correct the frequency reading
|
||||
- If you already use the transverter mode for transverter work just add 450 kHz to the current shift
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ This is the center frequency of reception in Hz of the track (or capture) being
|
|||
|
||||
<h3>3: Track sample rate</h3>
|
||||
|
||||
This is the sample rate in S/s of the track being played currently. It is possibly suffixed by a thousands mutiplier ('k' for kHz, 'M' for MHz). Recording SigMF files in SDRangel offers the possibility to change sample rate within the same record creating a new track.
|
||||
This is the sample rate in S/s of the track being played currently. It is possibly suffixed by a thousands multiplier ('k' for kHz, 'M' for MHz). Recording SigMF files in SDRangel offers the possibility to change sample rate within the same record creating a new track.
|
||||
|
||||
<h3>4: Open file</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -136,7 +136,7 @@ This label turns green when data is being received from the device.
|
|||
|
||||
The stream warning indicators are reset when the acquisition is started.
|
||||
|
||||
<h2>Dependendices</h2>
|
||||
<h2>Dependencies</h2>
|
||||
|
||||
On Ubuntu 20, the libuhd-dev package should be installed. The FPGA images then need to be downloaded with:
|
||||
|
||||
|
|
|
|||
|
|
@ -229,12 +229,12 @@ The script runs in daemon mode and is stopped using `Ctl-C`.
|
|||
- `-j` or `--psd-in` JSON file containing PSD floor information previously saved with the `-J` option
|
||||
- `-J` or `--psd-out` Write PSD floor information to JSON file
|
||||
- `-n` or `--nb-passes` Number of passes for PSD floor estimation. Default: `10`
|
||||
- `-f` or `--psd-level` Use a fixed PSD floor value therefore do not perform PSD floor estimaton
|
||||
- `-f` or `--psd-level` Use a fixed PSD floor value therefore do not perform PSD floor estimation
|
||||
- `-X` or `--psd-exclude-higher` Level above which to exclude bin scan during PSD floor estimation
|
||||
- `-x` or `--psd-exclude-lower` Level below which to exclude bin scan during PSD floor estimation
|
||||
- `-G` or `--psd-graph` Show PSD floor graphs. Requires `matplotlib`
|
||||
- `-N` or `--hotspots-noise` Number of hotspots above which detection is considered as noise. Default `8`
|
||||
- `-m` or `--margin` Margin in dB above PSD floor to detect acivity. Default: `3`
|
||||
- `-m` or `--margin` Margin in dB above PSD floor to detect activity. Default: `3`
|
||||
- `-g` or `--group-tolerance` Radius (1D) tolerance in points (bins) for hotspot aggregation. Default `1`
|
||||
- `-r` or `--freq-round` Frequency rounding value in Hz. Default: `1` (no rounding)
|
||||
- `-o` or `--freq-offset` Frequency rounding offset in Hz. Default: `0` (no offset)
|
||||
|
|
@ -281,7 +281,7 @@ This file drives how channels in the connected SDRangel instance are managed.
|
|||
|
||||
Refer to supervisord documentation.
|
||||
|
||||
Esample of `superscanner.conf` file to put in your `/etc//etc/supervisor/conf.d/` folder (add it in the `[include]` section of `/etc/supervisor/supervisord.conf`). Environment variable `PYTHONUNBUFFERED=1` is important for the log tail to work correctly.
|
||||
Example of `superscanner.conf` file to put in your `/etc//etc/supervisor/conf.d/` folder (add it in the `[include]` section of `/etc/supervisor/supervisord.conf`). Environment variable `PYTHONUNBUFFERED=1` is important for the log tail to work correctly.
|
||||
|
||||
```
|
||||
[program:superscanner]
|
||||
|
|
|
|||
|
|
@ -73,7 +73,7 @@ This is the codec applied before sending the stream via UDP. The following are a
|
|||
|
||||
<h3>1.10 SDP string</h3>
|
||||
|
||||
This is the SDP string representatiopn of the stream sent via UDP (RTP). In SDP files it is used on the `a=rtpmap`line (See 1.14). It can be used to check the effect of settings 1.5, 1.8 and 1.9.
|
||||
This is the SDP string representation of the stream sent via UDP (RTP). In SDP files it is used on the `a=rtpmap`line (See 1.14). It can be used to check the effect of settings 1.5, 1.8 and 1.9.
|
||||
|
||||
<h3>1.11 UDP address</h3>
|
||||
|
||||
|
|
@ -159,7 +159,7 @@ Each recording is written in a new file with the starting timestamp before the `
|
|||
- Given file name: `test.wav` then a recording file will be like: `test.2020-08-05T21_39_07_974.wav`
|
||||
- Given file name: `test.2020-08-05T20_36_15_974.wav` then a recording file will be like (with timestamp updated): `test.2020-08-05T21_41_21_173.wav`
|
||||
- Given file name: `test.first.wav` then a recording file will be like: `test.2020-08-05T22_00_07_974.wav`
|
||||
- Given file name: `record.test.first.eav` then a recording file will be like: `reocrd.test.2020-08-05T21_39_52_974.wav`
|
||||
- Given file name: `record.test.first.wav` then a recording file will be like: `record.test.2020-08-05T21_39_52_974.wav`
|
||||
|
||||
If a filename is given without `.wav` extension then the `.wav` extension is appended automatically before the above algorithm is applied. If a filename is given with an extension different of `.wav` then the extension is replaced by `.wav` automatically before the above algorithm is applied.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,12 +1,12 @@
|
|||
<h1>Configurations dialog</h1>
|
||||
|
||||
Configuraitons stores the complete setup of a SDRangel instance:
|
||||
Configurations stores the complete setup of a SDRangel instance:
|
||||
|
||||
- Workspaces
|
||||
- Device sets
|
||||
- Features
|
||||
|
||||
It also stores the geometry of all windows and workspaces so that the entire aspect of a configuration of the instance can be saved and retrieved. A default configuration is saved at program exit and retrieved at the next prograp start. Use the `--scratch` command line option to skip the retrieval of the default configuration and start with an empty setup.
|
||||
It also stores the geometry of all windows and workspaces so that the entire aspect of a configuration of the instance can be saved and retrieved. A default configuration is saved at program exit and retrieved at the next program start. Use the `--scratch` command line option to skip the retrieval of the default configuration and start with an empty setup.
|
||||
|
||||
|
||||
|
||||
|
|
@ -27,7 +27,7 @@ Update the selected configuration with the current setup
|
|||
Change configuration name or the configuration group to which this configuration belongs. If selection is a group the group name can be changed.
|
||||
|
||||
<h3>5: Export configuration</h3>
|
||||
Export selected configraton in a file that can be imported on another machine possibly with a different O/S. The configuration binary data (BLOB) is saved in Base-64 format.
|
||||
Export selected configuration in a file that can be imported on another machine possibly with a different O/S. The configuration binary data (BLOB) is saved in Base-64 format.
|
||||
|
||||
<h3>6: Import preset</h3>
|
||||
This is the opposite of the previous operation. This will create a new configuration in the selected group or the same group as the configuration being selected.
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
The user can give arguments in the form of a string related to a specific device that appears in the list of enumerated device. At the moment these arguments are related to a specific hardware and its sequence in enumeration. For example `LimeSDR,0` for the first Lime SDR, `LimeSDR,1` for the second Lime SDR ...
|
||||
|
||||
THe corresponding plugin can make use of this user string in any way it finds useful. At present this is used only by the SoapySDR input/output plugins to override the `kwargs` (keyword arguments) at device open time (the `driver` argument is preserved as defined in the enumeration)
|
||||
The corresponding plugin can make use of this user string in any way it finds useful. At present this is used only by the SoapySDR input/output plugins to override the `kwargs` (keyword arguments) at device open time (the `driver` argument is preserved as defined in the enumeration)
|
||||
|
||||
The following dialog is used to specify these arguments:
|
||||
|
||||
|
|
|
|||
|
|
@ -193,7 +193,7 @@ Toggles the spectrum on bottom (off) or on top (on) versus waterfall/spectrogram
|
|||
|
||||
Toggles the waterfall display
|
||||
|
||||
<h4>B.3.3: 3D Spectrgram</h4>
|
||||
<h4>B.3.3: 3D Spectrogram</h4>
|
||||
|
||||
Toggles the 3D spectrogram display. Controls inside the spectrogram window are described at the bottom of this page
|
||||
|
||||
|
|
@ -203,11 +203,11 @@ This control is only visible when the 3D Spectrogram is being displayed.
|
|||
|
||||
This dropdown determines how the 3D Spectrogram data is rendered.
|
||||
|
||||
- **Points**: The data are rendeded as points.
|
||||
- **Points**: The data are rendered as points.
|
||||
- **Lines**: The data points are connected by lines.
|
||||
- **Solid**: The data are rendeded as a solid surface with constant illumination.
|
||||
- **Solid**: The data are rendered as a solid surface with constant illumination.
|
||||
- **Outline**: The data are rendered as a solid surface with outlines of the polygons highlighted.
|
||||
- **Shaded**: The data are rendeder as a solid surface with a combination of ambient and diffuse lighting. This requires OpenGL 3.3 or greater.
|
||||
- **Shaded**: The data are rendered as a solid surface with a combination of ambient and diffuse lighting. This requires OpenGL 3.3 or greater.
|
||||
|
||||
<h3>B.4: Spectrum FFT controls - block #4</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
<h1>Spectrum calibration management</h1>
|
||||
|
||||
The spectrum calibration is controlled by this dialog. It manages the list of calibration points (calibration chart), genaral options and the import/export from/to a .csv file.
|
||||
The spectrum calibration is controlled by this dialog. It manages the list of calibration points (calibration chart), general options and the import/export from/to a .csv file.
|
||||
|
||||
This calibration is an artifact of the spectrum display it does not make any change in the actual levels in the DSP processing. It assumes nothing about the receiving or transmitting chains it is up to the user to run the calibration procedure to make the face power levels match the desired levels. If anything is changed in the receiving or transmitting parameters then the calibration procedure may have to be re-run again. Also it assumes nothing about the units of the calibrated power. Normally one would like to make dBm (or mW) measurements but it is up to the user to assume the actual units. One may want to use dBW or any other custom units therefore the displayed calibrated values will remain unit-less (dB).
|
||||
|
||||
|
|
|
|||
|
|
@ -122,7 +122,7 @@ Arranges windows in the MDI area of the workspace as tiled windows.
|
|||
|
||||
<h3>1.9: Stack windows</h3>
|
||||
|
||||
Arranges windowsa in the MDO area of the workspace in a way similar to the arrangement in version 6:
|
||||
Arranges windows in the MDO area of the workspace in a way similar to the arrangement in version 6:
|
||||
|
||||
- Devices are stacked in numerical order top left.
|
||||
- Fixed height features are stacked in order underneath devices and resized to match width of devices
|
||||
|
|
@ -261,7 +261,7 @@ Short description of a command.
|
|||
|
||||
<h4>2.3.5: Key binding sequence</h4>
|
||||
|
||||
Thisis a descriptive text of the key sequence that is used for the key binding.
|
||||
This is a descriptive text of the key sequence that is used for the key binding.
|
||||
|
||||
<h4>2.3.6: Command control or actions</h4>
|
||||
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue