| 
									
										
										
										
											2015-05-27 23:50:08 +00:00
										 |  |  |  | // Status=review | 
					
						
							|  |  |  |  | 
 | 
					
						
							|  |  |  |  | _WSJT-X_ is a computer program designed to facilitate basic amateur | 
					
						
							|  |  |  |  | radio communication using very weak signals. The first four letters in | 
					
						
							| 
									
										
										
										
											2016-10-13 20:28:02 +00:00
										 |  |  |  | the program name stand for "`**W**eak **S**ignal communication by | 
					
						
							|  |  |  |  | K1**JT**,`" while the suffix "`-X`" indicates that _WSJT-X_ started as | 
					
						
							| 
									
										
										
										
											2020-05-08 10:02:05 -04:00
										 |  |  |  | an e**Xt**ended and e**X**perimental branch of the program _WSJT_, | 
					
						
							|  |  |  |  | first released in 2001.  Bill Somerville, G4WJS, and Steve Franke, | 
					
						
							| 
									
										
										
										
											2020-05-23 11:57:53 -04:00
										 |  |  |  | K9AN, have been major contributors to program development since 2013 | 
					
						
							| 
									
										
										
										
											2020-05-08 10:02:05 -04:00
										 |  |  |  | and 2015, respectively. | 
					
						
							| 
									
										
										
										
											2015-05-27 23:50:08 +00:00
										 |  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2019-06-06 13:44:32 -04:00
										 |  |  |  | _WSJT-X_ Version {VERSION_MAJOR}.{VERSION_MINOR} offers ten different | 
					
						
							|  |  |  |  | protocols or modes: *FT4*, *FT8*, *JT4*, *JT9*, *JT65*, *QRA64*, | 
					
						
							|  |  |  |  | *ISCAT*, *MSK144*, *WSPR*, and *Echo*.  The first six are designed for | 
					
						
							|  |  |  |  | making reliable QSOs under weak-signal conditions. They use nearly | 
					
						
							| 
									
										
										
										
											2018-12-07 01:44:19 +00:00
										 |  |  |  | identical message structure and source encoding.  JT65 and QRA64 were | 
					
						
							|  |  |  |  | designed for EME ("`moonbounce`") on the VHF/UHF bands and have also | 
					
						
							|  |  |  |  | proven very effective for worldwide QRP communication on the HF bands. | 
					
						
							| 
									
										
										
										
											2020-05-14 18:56:35 -04:00
										 |  |  |  | QRA64 has a some advantages over JT65, including better performance | 
					
						
							|  |  |  |  | for EME on the higher microwave bands.  JT9 was originally designed | 
					
						
							|  |  |  |  | for the LF, MF, and lower HF bands.  Its submode JT9A is 2 dB more | 
					
						
							|  |  |  |  | sensitive than JT65 while using less than 10% of the bandwidth.  JT4 | 
					
						
							|  |  |  |  | offers a wide variety of tone spacings and has proven highly effective | 
					
						
							|  |  |  |  | for EME on microwave bands up to 24 GHz.  These four "`slow`" modes | 
					
						
							|  |  |  |  | use one-minute timed sequences of alternating transmission and | 
					
						
							|  |  |  |  | reception, so a minimal QSO takes four to six minutes — two or three | 
					
						
							| 
									
										
										
										
											2018-12-07 01:44:19 +00:00
										 |  |  |  | transmissions by each station, one sending in odd UTC minutes and the | 
					
						
							|  |  |  |  | other even.  FT8 is operationally similar but four times faster | 
					
						
							| 
									
										
										
										
											2019-06-06 13:44:32 -04:00
										 |  |  |  | (15-second T/R sequences) and less sensitive by a few dB.  FT4 is | 
					
						
							|  |  |  |  | faster still (7.5 s T/R sequences) and especially well suited for | 
					
						
							|  |  |  |  | radio contesting.  On the HF bands, world-wide QSOs are possible with | 
					
						
							|  |  |  |  | any of these modes 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. | 
					
						
							|  |  |  |  | 
 | 
					
						
							|  |  |  |  | Note that even though their T/R sequences are short, FT4 and FT8 are | 
					
						
							| 
									
										
										
										
											2019-06-17 15:47:47 -04:00
										 |  |  |  | classified as slow modes because their message frames are sent only | 
					
						
							|  |  |  |  | once per transmission.  All fast modes in _WSJT-X_ send their message | 
					
						
							|  |  |  |  | frames repeatedly, as many times as will fit into the Tx sequence | 
					
						
							|  |  |  |  | length. | 
					
						
							| 
									
										
										
										
											2016-09-08 17:04:18 +00:00
										 |  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2016-10-17 20:51:16 +00:00
										 |  |  |  | *ISCAT*, *MSK144*, and optionally submodes *JT9E-H* are "`fast`" | 
					
						
							| 
									
										
										
										
											2016-09-08 20:30:12 +00:00
										 |  |  |  | protocols designed to take advantage of brief signal enhancements from | 
					
						
							| 
									
										
										
										
											2016-10-17 20:51:16 +00:00
										 |  |  |  | ionized meteor trails, aircraft scatter, 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-trail reflections or "`pings`".  ISCAT uses free-form | 
					
						
							|  |  |  |  | messages up to 28 characters long, while MSK144 uses the same | 
					
						
							| 
									
										
										
										
											2016-10-26 17:50:48 +00:00
										 |  |  |  | structured messages as the slow modes and optionally an abbreviated | 
					
						
							| 
									
										
										
										
											2016-10-17 20:51:16 +00:00
										 |  |  |  | format with hashed callsigns.   | 
					
						
							| 
									
										
										
										
											2016-09-08 17:04:18 +00:00
										 |  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2016-10-17 20:51:16 +00:00
										 |  |  |  | *WSPR* (pronounced "`whisper`") stands for **W**eak **S**ignal | 
					
						
							|  |  |  |  | **P**ropagation **R**eporter.  The WSPR protocol was designed for probing | 
					
						
							|  |  |  |  | potential propagation paths using low-power transmissions. WSPR | 
					
						
							|  |  |  |  | messages normally carry the transmitting station’s callsign, grid | 
					
						
							|  |  |  |  | locator, and transmitter power in dBm, and they can be decoded at | 
					
						
							| 
									
										
										
										
											2018-12-04 14:34:08 -05:00
										 |  |  |  | signal-to-noise ratios as low as -31 dB in a 2500 Hz bandwidth.  WSPR | 
					
						
							| 
									
										
										
										
											2016-10-26 17:50:48 +00:00
										 |  |  |  | users with internet access can automatically upload reception | 
					
						
							| 
									
										
										
										
											2016-10-17 20:51:16 +00:00
										 |  |  |  | reports to a central database called {wsprnet} that provides a mapping | 
					
						
							|  |  |  |  | facility, archival storage, and many other features. | 
					
						
							| 
									
										
										
										
											2015-05-27 23:50:08 +00:00
										 |  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2016-10-17 20:51:16 +00:00
										 |  |  |  | *Echo* mode allows you to detect and measure your own station's echoes | 
					
						
							|  |  |  |  | from the moon, even if they are far below the audible threshold. | 
					
						
							| 
									
										
										
										
											2015-11-15 15:01:57 +00:00
										 |  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2016-10-17 20:51:16 +00:00
										 |  |  |  | _WSJT-X_ provides spectral displays for receiver passbands as wide as | 
					
						
							|  |  |  |  | 5 kHz, flexible rig control for nearly all modern radios used by | 
					
						
							|  |  |  |  | amateurs, and a wide variety of special aids such as automatic Doppler | 
					
						
							|  |  |  |  | tracking for EME QSOs and Echo testing.  The program runs equally well | 
					
						
							|  |  |  |  | on Windows, Macintosh, and Linux systems, and installation packages | 
					
						
							|  |  |  |  | are available for all three platforms. | 
					
						
							| 
									
										
										
										
											2015-05-31 15:29:59 +00:00
										 |  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2018-02-02 19:31:54 +00:00
										 |  |  |  | *Version Numbers:* _WSJT-X_ release numbers have major, minor, and | 
					
						
							|  |  |  |  | patch numbers separated by periods: for example, _WSJT-X_ Version | 
					
						
							| 
									
										
										
										
											2019-06-06 13:44:32 -04:00
										 |  |  |  | 2.1.0.  Temporary _beta release_ candidates are sometimes made in | 
					
						
							| 
									
										
										
										
											2018-02-02 19:31:54 +00:00
										 |  |  |  | advance of a new general-availability release, in order to obtain user | 
					
						
							| 
									
										
										
										
											2019-06-06 13:44:32 -04:00
										 |  |  |  | feedback.  For example, version 2.1.0-rc1, 2.1.0-rc2, etc., would | 
					
						
							|  |  |  |  | be beta releases leading up to the final release of v2.1.0. | 
					
						
							| 
									
										
										
										
											2018-02-02 19:31:54 +00:00
										 |  |  |  | Release candidates should be used _only_ during a short testing | 
					
						
							| 
									
										
										
										
											2018-02-07 20:52:01 +00:00
										 |  |  |  | period. They carry an implied obligation to provide feedback to the | 
					
						
							| 
									
										
										
										
											2018-02-02 19:31:54 +00:00
										 |  |  |  | program development group.  Candidate releases should not be used on | 
					
						
							|  |  |  |  | the air after a full release with the same number has been made. |