mirror of
https://github.com/f4exb/sdrangel.git
synced 2024-11-21 15:51:47 -05:00
Fix spellling errors found with aspell
This commit is contained in:
Daniele Forsi
parent
5e321e3ead
commit
d135dd9028
@ -10,4 +10,4 @@ Files copied over from the original 'doc' folder:
|
||||
|
||||
- copyright.txt
|
||||
- lgpl-3.0.txt
|
||||
- releasenotes.txts
|
||||
- releasenotes.txt
|
||||
|
||||
@ -30,7 +30,7 @@ Bandwidth in Hz of the channel for which power is to be measured.
|
||||
|
||||
<h3>4: 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>5: THp - Pulse Threshold</h3>
|
||||
|
||||
|
||||
@ -112,7 +112,7 @@ The LoRa standard specifies 0 (no DE) or 2 (DE active). The ChirpChat DE range i
|
||||
|
||||
The LoRa standard also specifies that the LowDataRateOptimizatio flag (thus DE=2 vs DE=0 here) should be set when the symbol time defined as BW / 2^SF exceeds 16 ms (See section 4.1.1.6 of the SX127x datasheet). In practice this happens for SF=11 and SF=12 and large enough bandwidths (you can do the maths).
|
||||
|
||||
Here this value is the log2 of the number of FFT bins used for one symbol. Extending the number of FFT bins per symbol decreases the probability to detect the wrong symbol as an adjacent bin. It can also overcome frequency or samlping time drift on long messages particularly for small bandwidths.
|
||||
Here this value is the log2 of the number of FFT bins used for one symbol. Extending the number of FFT bins per symbol decreases the probability to detect the wrong symbol as an adjacent bin. It can also overcome frequency or sampling time drift on long messages particularly for small bandwidths.
|
||||
|
||||
In practice it is difficult to make correct decodes if only one FFT bin is used to code one symbol (DE=0) therefore it is recommended to use a DE factor of 2 or more. With medium SNR DE=1 can still achieve good results.
|
||||
|
||||
|
||||
@ -71,7 +71,7 @@ When checked, writes all received messages to a .csv file, specified by (13).
|
||||
|
||||
<h3>13: .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>14: Read Data from .csv File</h3>
|
||||
|
||||
|
||||
@ -550,11 +550,11 @@ This button tunes the length of the trace displayed on B.1. Units are millisecon
|
||||
|
||||
<h4>B.15: Trace stroke</h4>
|
||||
|
||||
This button tunes the stroke of the points displayer on B.1. The trace has limited persistence based on alpha blending. This is the 8 bit unsigned integer value of the trace alpha blending. Default value is 100.
|
||||
This button tunes the stroke of the points displayed on B.1. The trace has limited persistence based on alpha blending. This is the 8 bit unsigned integer value of the trace alpha blending. Default value is 100.
|
||||
|
||||
<h4>B.16: Trace decay</h4>
|
||||
|
||||
This button tunes the persistence decay of the points displayer on B.1. The trace has limited persistence based on alpha blending. This controls the alpha value of the black screen printed at the end of each trace and thus the trace points decay time. The value is 255 minus he displayed value using 8 bit unsigned integers.
|
||||
This button tunes the persistence decay of the points displayed on B.1. The trace has limited persistence based on alpha blending. This controls the alpha value of the black screen printed at the end of each trace and thus the trace points decay time. The value is 255 minus he displayed value using 8 bit unsigned integers.
|
||||
|
||||
- A value of 0 yields no persistence
|
||||
- A value of 255 yields infinite persistence
|
||||
|
||||
@ -19,7 +19,7 @@ Modulation characteristics from LoRa have been augmented with more bandwidths an
|
||||
|
||||
The top and bottom bars of the channel window are described [here](../../../sdrgui/channel/readme.md)
|
||||
|
||||
|
||||
|
||||
|
||||
<h3>1: Frequency shift from center frequency of reception</h3>
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
<h2>Introduction</h2>
|
||||
|
||||
The Packet Error Rate (PER) Tester feature can be used to measure the packet error rate over digital, packet based protocols such as AX.25 (Packet mod/demod), LoRa (ChipChat mod/demod), AIS and 802.15.4.
|
||||
The Packet Error Rate (PER) Tester feature can be used to measure the packet error rate over digital, packet based protocols such as AX.25 (Packet mod/demod), LoRa (ChirpChat mod/demod), AIS and 802.15.4.
|
||||
|
||||
The PER Tester feature allows you to define the contents of the packets to transmit, which can include a per-packet 32-bit identifier, as well as a user-defined or random payload, how many packets are sent and the interval between them.
|
||||
|
||||
|
||||
@ -146,7 +146,7 @@ Click to open the Settings Dialog. The settings dialog allows a user to:
|
||||
|
||||
<h3>18: Display SDO/SOHO Imagery</h3>
|
||||
|
||||
When checked, displays imagary from NASA's SDO (Solar Dynamic Observatory) and ESA/NASA's SOHO (Solar and Heliospheric Observatory) satellites.
|
||||
When checked, displays imagery from NASA's SDO (Solar Dynamic Observatory) and ESA/NASA's SOHO (Solar and Heliospheric Observatory) satellites.
|
||||
|
||||
SDOs images the Sun in a variety of UV and EUV wavelengths. SOHO shows images of the solar corona. The images are near real-time, updated every 15 minutes.
|
||||
|
||||
@ -171,7 +171,7 @@ Selects which image / wavelength to view.
|
||||
| 211 Å | Active corona |
|
||||
| 304 Å | Chromosphere, transition region |
|
||||
| 335 Å | Active corona |
|
||||
| 1600 Å | Transition region, upper photoshere |
|
||||
| 1600 Å | Transition region, upper photosphere |
|
||||
| 1700 Å | Temperature minimum, photosphere |
|
||||
|
||||
[Ref](https://sdo.gsfc.nasa.gov/data/channels.php)
|
||||
|
||||
@ -106,7 +106,7 @@ When checked, the centre of view will track the coordinates received from the se
|
||||
|
||||
Select a Star Tracker, Rotator Controller, Satellite Tracker or Map plugin to read viewing coordinates from.
|
||||
|
||||
* When a Star Tracker is selected, target RA/Dec, observation position, antenna beamwith and date/time will be read from the selected plugin.
|
||||
* When a Star Tracker is selected, target RA/Dec, observation position, antenna beamwidth and date/time will be read from the selected plugin.
|
||||
* For other plugin types, Alt/El will be read and other parameters are taken from the the Display Settings dialog (12).
|
||||
|
||||
<h3>12: Display settings</h3>
|
||||
@ -129,7 +129,7 @@ The popup window can be moved by left clicking and dragging it.
|
||||
ESASky and Aladin are able to overlay catalog data:
|
||||
|
||||
* In ESASky, zoom in to the area of interest, then press the "Explore catalog data for this region" button. A window will appear showing available catalogs. Left click and boxes will be overlaid on the map for each catalog entry. The data is also displayed in tabular form. You can left click on a box to view its data in the table.
|
||||
* In Aladin, zoom in to the areae of interest, then press the "Manage layers" button. In the popup window, select one or more of the available catalogs, or press Add catalogue to add a new one. Boxes will be overlaid on the map for each catalog entry. Left click on a box to display the data for it in tabular form.
|
||||
* In Aladin, zoom in to the area of interest, then press the "Manage layers" button. In the popup window, select one or more of the available catalogs, or press Add catalogue to add a new one. Boxes will be overlaid on the map for each catalog entry. Left click on a box to display the data for it in tabular form.
|
||||
|
||||
<h2>Attribution</h2>
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@ All device types have common settings. Clicking on the button opens a dialog to
|
||||
|
||||
<h4>A.2.1: Toggle reverse API feature</h4>
|
||||
|
||||
Use this checkbox to toggle on/off the reverse API feature. With reverse API engaged the changes in the device settings are forwarded to an API endpoint given by address (A.2.2), port (A.2.3) and device index A.2.4) in the same format as the SDRangel REST API device settings endpoint. With the values of the screenshot the API URL is: `http://127.0.0.1:8888/sdrangel/deviceset/0/device/settings` The JSON payload follows the same format as the SDRangel REST API device settings. For example with HachRF Rx this would be something like:
|
||||
Use this checkbox to toggle on/off the reverse API feature. With reverse API engaged the changes in the device settings are forwarded to an API endpoint given by address (A.2.2), port (A.2.3) and device index A.2.4) in the same format as the SDRangel REST API device settings endpoint. With the values of the screenshot the API URL is: `http://127.0.0.1:8888/sdrangel/deviceset/0/device/settings` The JSON payload follows the same format as the SDRangel REST API device settings. For example with HackRF Rx this would be something like:
|
||||
|
||||
```
|
||||
{
|
||||
|
||||
@ -40,7 +40,7 @@ Spectrum display with the highlight artifact on:
|
||||
|
||||
The adjacent channel power measurement measures the power in a channel of user-defined bandwidth and compares it to the power in the left and right adjacent channels. Channel shift and adjacent channels width and separation are also adjustable with the dialog.
|
||||
|
||||
|
||||
|
||||
|
||||
- **Center frequency offset**: channels offset from the center in Hz
|
||||
- **Channel bandwidth**: bandwidth of the center channel in Hz
|
||||
|
||||
Loading…
Reference in New Issue
Block a user