mirror of
				https://github.com/saitohirga/WSJT-X.git
				synced 2025-10-31 13:10:19 -04:00 
			
		
		
		
	Starting to update the WSJT-X User Guide for version 1.7. More to come!
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@7063 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
This commit is contained in:
		
							parent
							
								
									2d9b729c6c
								
							
						
					
					
						commit
						3dc2e696cd
					
				
										
											Binary file not shown.
										
									
								
							| Before Width: | Height: | Size: 34 KiB After Width: | Height: | Size: 69 KiB | 
										
											Binary file not shown.
										
									
								
							| Before Width: | Height: | Size: 6.6 KiB After Width: | Height: | Size: 4.6 KiB | 
										
											Binary file not shown.
										
									
								
							| Before Width: | Height: | Size: 3.3 KiB After Width: | Height: | Size: 3.5 KiB | 
| @ -6,25 +6,40 @@ the program name stand for "`Weak Signal communication by K1JT,`" while | |||||||
| the suffix "`-X`" indicates that _WSJT-X_ started as an extended (and | the suffix "`-X`" indicates that _WSJT-X_ started as an extended (and | ||||||
| experimental) branch of the program _WSJT_. | experimental) branch of the program _WSJT_. | ||||||
| 
 | 
 | ||||||
| _WSJT-X_ Version 1.6 offers five protocols or "`modes`": JT4, JT9, JT65 | _WSJT-X_ Version 1.7 offers eight protocols or "`modes`": *JT4*, | ||||||
| WSPR, and Echo.  The first three are designed for making reliable  | *JT9*, *JT65*, *QRA64*, *WSPR*, *Echo*, *ISCAT*, and *MSK144*.  The | ||||||
| QSOs under extreme weak-signal conditions. They use nearly identical | first four are designed for making reliable QSOs under extreme | ||||||
| message structure and source encoding.  JT65 was designed for EME | weak-signal conditions. They use nearly identical message structure | ||||||
| ("`moonbounce`") on the VHF/UHF bands and has also proven very effective | and source encoding.  JT65 and QRA64 were designed for EME | ||||||
| for worldwide QRP communication on the HF bands.  JT9 is optimized for | ("`moonbounce`") on the VHF/UHF bands and have also proven very | ||||||
| the LF, MF, and lower HF bands.  It is 2 dB more sensitive than | effective for worldwide QRP communication on the HF bands.  QRA64 has | ||||||
| JT65 while using less than 10% of the bandwidth.  JT4 offers a wide | a number of advantages over JT65, including better performance on the | ||||||
| variety of tone spacings and has proved very effective for EME on | very weakest signals.  We imagine that over time it will replace JT65 | ||||||
| microwave bands up to 24 GHz.  All three of these modes use one-minute | for EME use.  JT9 is optimized for the LF, MF, and lower HF bands.  It | ||||||
| timed sequences of alternating transmission and reception, so a | is 2 dB more sensitive than JT65 while using less than 10% of the | ||||||
| minimal QSO takes four to six minutes — two or three transmissions by | bandwidth.  JT4 offers a wide variety of tone spacings and has proved | ||||||
| each station, one sending in odd UTC minutes and the other even. On | very effective for EME on microwave bands up to 24 GHz.  All of these | ||||||
| the HF bands, world-wide QSOs are possible using power levels of a few | "`slow`" modes use one-minute timed sequences of alternating | ||||||
| watts and compromise antennas.  On VHF bands and higher, QSOs are | transmission and reception, so a minimal QSO takes four to six minutes | ||||||
| possible (by EME and other propagation types) at signal levels 10 to | — two or three transmissions by each station, one sending in odd UTC | ||||||
| 15 dB below those required for CW. | minutes and the other even. On the HF bands, world-wide QSOs are | ||||||
|  | possible using power levels of a few watts (or even milliwatts) and | ||||||
|  | compromise antennas.  On VHF bands and higher, QSOs are possible (by | ||||||
|  | EME and other propagation types) at signal levels 10 to 15 dB below | ||||||
|  | those required for CW. | ||||||
| 
 | 
 | ||||||
| WSPR (pronounced "`whisper`") stands for Weak Signal Propagation | *ISCAT*, *MSK144*, and optionally *JT9E-H* are "`fast`" modes designed | ||||||
|  | to take advantage of brief signal enhancements from ionized meteor | ||||||
|  | trails and other types of scatter propagation. These modes use timed | ||||||
|  | sequences of 5, 10, 15, or 30 s duration.  User messages are | ||||||
|  | transmitted repeatedly at high rate (up to 250 characters per second, | ||||||
|  | for MSK144) to make good use of the shortest meteor "`pings`".  ISCAT | ||||||
|  | uses free-form messages up to 28 characters long, while MSK144 uses | ||||||
|  | the same structured messages as the slow modes together with an | ||||||
|  | abbreviated format with hashed callsigns for messages sent after | ||||||
|  | initial contact has been established. | ||||||
|  | 
 | ||||||
|  | *WSPR* (pronounced "`whisper`") stands for Weak Signal Propagation | ||||||
| Reporter.  The WSPR protocol was designed for probing potential | Reporter.  The WSPR protocol was designed for probing potential | ||||||
| propagation paths using low-power transmissions. WSPR messages | propagation paths using low-power transmissions. WSPR messages | ||||||
| normally carry the transmitting station’s callsign, grid locator, and | normally carry the transmitting station’s callsign, grid locator, and | ||||||
| @ -34,7 +49,7 @@ internet access can automatically upload their reception reports to a | |||||||
| central database called {wsprnet} that provides a mapping facility, | central database called {wsprnet} that provides a mapping facility, | ||||||
| archival storage, and many other features. | archival storage, and many other features. | ||||||
| 
 | 
 | ||||||
| Echo mode allows you to detect and measure your own lunar echoes, | *Echo* mode allows you to detect and measure your own lunar echoes, | ||||||
| even if they are far below the audible threshold. | even if they are far below the audible threshold. | ||||||
| 
 | 
 | ||||||
| _WSJT-X_ provides spectral displays for passbands up to 5 kHz, | _WSJT-X_ provides spectral displays for passbands up to 5 kHz, | ||||||
|  | |||||||
| @ -1,36 +1,25 @@ | |||||||
| === New in Version 1.6 | === New in Version 1.7 | ||||||
| 
 | 
 | ||||||
| For quick reference, here's a short list of features and capabilities | For quick reference, here's a short list of features and capabilities | ||||||
| added to _WSJT-X_ since Version 1.5.0: | added to _WSJT-X_ since Version 1.6.0: | ||||||
| 
 | 
 | ||||||
| - *WSPR* mode, including coordinated automatic band-hopping and a | - New modes: ISCAT, MSK144, QRA64. | ||||||
| new two-pass decoder that can decode overlapping signals. |  | ||||||
| 
 | 
 | ||||||
| - EME-motivated features including *JT4* (submodes *A-G*), *Echo* | - Newly implemented submodes of existing modes: JT65B-C, JT9B-H (wide | ||||||
| mode, and automatic *Doppler tracking*.  The JT4 decoder is more | and fast). | ||||||
| sensitive than that in the latest WSJT, and message averaging is fully |  | ||||||
| automated.  (Note that submodes *JT65B* and *JT65C* are also present |  | ||||||
| in Version 1.6, but the high-sensitivity decoder required for EME with |  | ||||||
| JT65 is not yet included.) |  | ||||||
| 
 | 
 | ||||||
| - Tools for accurate *frequency calibration* of your radio, so you can | - New Franke-Taylor decoder replaces the Koetter-Vardy decoder in | ||||||
| be always on-frequency to within about 1 Hz. | JT65.  KVASD is no longer used. | ||||||
| 
 | 
 | ||||||
| - Mode-specific standard working frequencies accessible from the | - Improvements to the JT4, JT9, and JT65 decoders. | ||||||
| drop-down band selector. | 
 | ||||||
|  | - Multi-pass decoding for JT65 and WSPR. | ||||||
|  | 
 | ||||||
|  | - Improved convenience features for EME Doppler tracking. | ||||||
|  | 
 | ||||||
|  | - Multiple program configurations can be saved and restored. | ||||||
|  | 
 | ||||||
|  | - A new sample-file download facility. | ||||||
| 
 | 
 | ||||||
| - A number of corrections to the Hamlib library, fixing balky | - A number of corrections to the Hamlib library, fixing balky | ||||||
| rig-control features.  A few unreliable features peculiar to | rig-control features.   | ||||||
| particular radios have been removed. |  | ||||||
| 
 |  | ||||||
| === Future releases |  | ||||||
| 
 |  | ||||||
| Much work has already been done on Version 1.7 of _WSJT-X_.  (Up to |  | ||||||
| now this branch has been called v1.6.1.)  More than 100 people have |  | ||||||
| been building this version for themselves as development progresses, |  | ||||||
| and reporting on their experiences.  The next release will offer |  | ||||||
| several "`fast modes`" intended for meteor and ionospheric scatter, |  | ||||||
| including a new FEC-enhanced mode called *JTMSK*.  It will also have a |  | ||||||
| significantly improved JT65 decoder, especially advantageous when used |  | ||||||
| in crowded HF bands.  Starting with Version 1.7, _WSJT-X_ will no |  | ||||||
| longer use the patented, closed-source Koetter-Vardy algorithm. |  | ||||||
|  | |||||||
| @ -1,16 +1,20 @@ | |||||||
| === VHF Setup | === VHF Setup | ||||||
| 
 | 
 | ||||||
| V1.6.0 is the first _WSJT-X_ version to include features specifically | _WSJT-X_ v1.7.0 builds on the features designed for use on VHF and | ||||||
| designed for use on VHF and higher bands.  These features include | higher bands first introduced in v1.6.  These features now include | ||||||
| *JT4*, a mode particularly useful for EME on the microwave bands; | *JT4*, a mode particularly useful for EME on the microwave bands; | ||||||
| *Echo* mode, for detecting and measuring your own lunar echoes; and | *QRA64*, a mode for EME using a "`Q-ary Repeat Accumulate`" code, a | ||||||
| automatic *Doppler tracking* for the EME path.  The accuracy of | low-density partity-check (LDPC) code using a 64-character symbol | ||||||
| Doppler calculations is better than 1 Hz at 10 GHz.  (Note that | alphabet; *MSK144*, a mode for meteor scatter using a binary LDPC code | ||||||
| sub-modes JT65B and JT65C are present in v1.6.0, but are not yet fully | and offset quadrature phase-shift keying (OQPSK), a waveform also | ||||||
| implemented for EME purposes.) | known as Minimum Shift Keying (MSK); and *ISCAT*, intended for other | ||||||
|  | types of scatter propagation.  Additional VHF-and-up features include | ||||||
|  | *Echo* mode, for detecting and measuring your own lunar echoes, and | ||||||
|  | automatic high-accuracy *Doppler tracking* for the EME path. | ||||||
| 
 | 
 | ||||||
| - To activate the VHF-and-up features check the box labeled _Enable | - To activate the VHF-and-up features check the box labeled _Enable | ||||||
|   VHF/UHF/Microwave features_ on the *Settings | General* tab. | VHF/UHF/Microwave features_ on the *Settings | General* tab.  In most | ||||||
|  | cases you will also want to check _Single decode_. | ||||||
| 
 | 
 | ||||||
| - If you will be doing EME, check the box _Decode at t = 52 s_ | - If you will be doing EME, check the box _Decode at t = 52 s_ | ||||||
| to allow for the EME path delay on received signals. | to allow for the EME path delay on received signals. | ||||||
| @ -38,28 +42,28 @@ to ensure that the right-hand portion of the window is visible. | |||||||
| 
 | 
 | ||||||
| image::Astronomical_data.png[align="center",alt="Astronomical data"] | image::Astronomical_data.png[align="center",alt="Astronomical data"] | ||||||
| 
 | 
 | ||||||
| IMPORTANT: Note that two different types of Doppler control are provided.   | IMPORTANT: Note that three different types of Doppler tracking are | ||||||
|  | provided. | ||||||
| 
 | 
 | ||||||
| - Select _Full Doppler to DX Grid_ if you know your QSO partner's locator | - Select _Full Doppler to DX Grid_ if you know your QSO partner's locator | ||||||
| and he/she will not be using any Doppler control. | and he/she will not be using any Doppler control. | ||||||
| 
 | 
 | ||||||
|  | - Select _Receive only_ to enable EME Doppler tracking of your receive | ||||||
|  | frequency to a specific locator; your Tx frequency will remain fixed. | ||||||
|  | 
 | ||||||
| - Select _Constant frequency on Moon_ to correct for your own (one-way) | - Select _Constant frequency on Moon_ to correct for your own (one-way) | ||||||
| Doppler shift to or from the Moon.  If your QSO partner does the same | Doppler shift to or from the Moon.  If your QSO partner does the same | ||||||
| thing, both stations will have the required Doppler compensation. | thing, both stations will have the required Doppler compensation. | ||||||
| Moreover, anyone else using this option will hear both of you | Moreover, anyone else using this option will hear both of you | ||||||
| without the need for manual frequency changes.  The hypothetical "`man | without the need for manual frequency changes.  The hypothetical "`man | ||||||
| in the moon`" will copy all of you on the selected nominal frequency. | in the moon`" would copy all of you on the selected nominal frequency. | ||||||
| 
 | 
 | ||||||
| - In the example depicted above, the moon-based nominal frequency is | - In the example depicted above, the moon-based nominal frequency is | ||||||
| 100 kHz above the stated band edge, or 10368.100 MHz for the 10 GHz | 100 kHz above the stated band edge, or 10368.100 MHz for the 10 GHz | ||||||
| band.  The home station two-way self Doppler shift is +6193 Hz, so the | band.  The home station two-way self Doppler shift is +24366 Hz, so the | ||||||
| one-way shift is +3096.5 Hz.  Therefore, the receive frequency is set | one-way shift is +12183 Hz.  Therefore, the receive frequency is set | ||||||
| to 10,360.103097 Hz.  When a transmission is started, the frequency | to 10,360.112183 Hz.  When a transmission is started, the frequency | ||||||
| is reset to 3096.5 Hz below the nominal frequency. | will be reset to 12183 Hz _below_ the nominal on-the-moon frequency. | ||||||
| 
 |  | ||||||
| - Spinner controls at top right of the *Astronomical Data* window let you |  | ||||||
| set a working frequency above the nominal band edge. The frequency above |  | ||||||
| band edge is the sum of the numbers in these two controls (kHz + Hz). |  | ||||||
| 
 | 
 | ||||||
| === EME with JT4 | === EME with JT4 | ||||||
| 
 | 
 | ||||||
| @ -82,11 +86,7 @@ image::Add_station_info.png[align="center",alt="Station information"] | |||||||
| 
 | 
 | ||||||
| - The JT4 decoder in _WSJT-X_ includes optional facilities for | - The JT4 decoder in _WSJT-X_ includes optional facilities for | ||||||
| averaging over successive transmissions and also correlation decoding, | averaging over successive transmissions and also correlation decoding, | ||||||
| sometimes known as "`Deep Search`".   | also known as "`Deep Search`".   | ||||||
| 
 |  | ||||||
| IMPORTANT: The *Decode* menu appears to provide options to set |  | ||||||
| different decoding behavior.  However, in JT4 mode _WSJT-X_ Version |  | ||||||
| 1.6 always behaves as if you have selected _Include correlation_. |  | ||||||
| 
 | 
 | ||||||
| image::decoding_depth.png[align="center",alt="Decoding Depth"] | image::decoding_depth.png[align="center",alt="Decoding Depth"] | ||||||
| 
 | 
 | ||||||
| @ -97,6 +97,22 @@ _Sh_ on the main window. | |||||||
| IMPORTANT: Thanks to G3WDG, many additional hints for using JT4 and | IMPORTANT: Thanks to G3WDG, many additional hints for using JT4 and | ||||||
| Echo mode on the EME path are available in {jt4eme}. | Echo mode on the EME path are available in {jt4eme}. | ||||||
| 
 | 
 | ||||||
|  | === EME with JT65 | ||||||
|  | 
 | ||||||
|  | TBD ... | ||||||
|  | 
 | ||||||
|  | === EME with QRA64 | ||||||
|  | 
 | ||||||
|  | TBD ... | ||||||
|  | 
 | ||||||
|  | === Meteor Scatter with MSK144 | ||||||
|  | 
 | ||||||
|  | TBD ... | ||||||
|  | 
 | ||||||
|  | === Scatter Propagation with ISCAT | ||||||
|  | 
 | ||||||
|  | TBD ... | ||||||
|  | 
 | ||||||
| === Echo Mode | === Echo Mode | ||||||
| 
 | 
 | ||||||
| *Echo* mode allows you to make sensitive measurements of your own | *Echo* mode allows you to make sensitive measurements of your own | ||||||
|  | |||||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user