diff --git a/doc/user_guide/en/astro_data.adoc b/doc/user_guide/en/astro_data.adoc index dcdc2800e..361ee9b00 100644 --- a/doc/user_guide/en/astro_data.adoc +++ b/doc/user_guide/en/astro_data.adoc @@ -1,46 +1,57 @@ -A text box entitled Astronomical Data provides information needed for -tracking the sun or moon, compensating for EME Doppler shift, and -estimating EME Doppler spread and path degradation. Toggle the -*Astronomical data* on the *View* menu to display or hide this window. - -image::AstroData_2.png[align="center",alt="Astronomical Data"] - -Available information includes the current UTC *Date* and time; *Az* -and *El*, azimuth and elevation of the moon at your own location, in -degrees; *SelfDop*, *Width*, and *Delay*, the Doppler shift, full -limb-to-limb Doppler spread in Hz, and delay of your own EME echoes in -seconds; and *DxAz* and *DxEl*, *DxDop*, and *DxWid*, corresponding -parameters for a station located at the *DX Grid* entered on the main -window. These numbers are followed by *Dec*, the declination of the -moon; *SunAz* and *SunEl*, the azimuth and elevation of the Sun; -*Freq*, your stated operating frequency in MHz; *Tsky*, the estimated -sky background temperature in the direction of the moon, scaled to the -operating frequency; *Dpol*, the spatial polarization offset in -degrees; *MNR*, the maximum non-reciprocity of the EME path in dB, -owing to a combination of Faraday rotation and spatial polarization; -and finally *Dgrd*, an estimate of the signal degradation in dB, -relative to the best possible time with the moon at perigee in a cold -part of the sky. - -The state of the art for establishing three-dimensional locations of -the sun, moon, and planets at a specified time is embodied in a -numerical model of the solar system maintained at the Jet Propulsion -Laboratory. The model has been numerically integrated to produce -tabular data that can be interpolated with very high accuracy. For -example, the celestial coordinates of the moon or a planet can be -determined at a specified time to within about 0.0000003 degrees. The -JPL ephemeris tables and interpolation routines have been incorporated -into _WSJT-X_. Further details on accuracy, especially concerning -calculated EME Doppler shifts, are described in {lunarEchoes} for -November-December, 2016. - -The sky background temperatures reported by _WSJT-X_ are derived from -the all-sky 408 MHz map of Haslam et al. (Astronomy and Astrophysics -Supplement Series, 47, 1, 1982), scaled by frequency to the -2.6 -power. This map has angular resolution of about 1 degree, and of -course most amateur EME antennas have much broader beamwidths than -this. Your antenna will therefore smooth out the hot spots -considerably, and the observed extremes of sky temperature will be -less. Unless you understand your sidelobes and ground reflections -extremely well, it is unlikely that more accurate sky temperatures -would be of much practical use. +A text box entitled Astronomical Data provides information needed for +tracking the sun or moon, compensating for EME Doppler shift, and +estimating EME Doppler spread and path degradation. Toggle the +*Astronomical data* on the *View* menu to display or hide this window. + +image::AstroData_2.png[align="center",alt="Astronomical Data"] + +Available information includes the current UTC *Date* and time; *Az* +and *El*, azimuth and elevation of the moon at your own location, in +degrees; *SelfDop*, *Width*, and *Delay*, the Doppler shift, full +limb-to-limb Doppler spread in Hz, and delay of your own EME echoes in +seconds; and *DxAz* and *DxEl*, *DxDop*, and *DxWid*, corresponding +parameters for a station located at the *DX Grid* entered on the main +window. These numbers are followed by *Dec*, the declination of the +moon; *SunAz* and *SunEl*, the azimuth and elevation of the Sun; +*Freq*, your stated operating frequency in MHz; *Tsky*, the estimated +sky background temperature in the direction of the moon, scaled to the +operating frequency; *Dpol*, the spatial polarization offset in +degrees; *MNR*, the maximum non-reciprocity of the EME path in dB, +owing to a combination of Faraday rotation and spatial polarization; +and finally *Dgrd*, an estimate of the signal degradation in dB, +relative to the best possible time with the moon at perigee in a cold +part of the sky. + +On the higher microwave bands, where Faraday rotation is minimal and +linear polarization is often used, spatial offset will reduce signal +levels. Some stations have implemented mechanical polarisation +adjustment to overcome this loss, and the amount of rotation needed is +predicted in real time by the value of *Dpol*. Positive Dpol means +that the antenna should be rotated in a clockwise direction looking +from behind the antenna towards the moon. For a dish antenna, the +feed should similarly be rotated clockwise looking into the mouth of +the feed. A negative value for Dpol means anticlockwise rotation. + + +The state of the art for establishing three-dimensional locations of +the sun, moon, and planets at a specified time is embodied in a +numerical model of the solar system maintained at the Jet Propulsion +Laboratory. The model has been numerically integrated to produce +tabular data that can be interpolated with very high accuracy. For +example, the celestial coordinates of the moon or a planet can be +determined at a specified time to within about 0.0000003 degrees. The +JPL ephemeris tables and interpolation routines have been incorporated +into _WSJT-X_. Further details on accuracy, especially concerning +calculated EME Doppler shifts, are described in {lunarEchoes} for +November-December, 2016. + +The sky background temperatures reported by _WSJT-X_ are derived from +the all-sky 408 MHz map of Haslam et al. (Astronomy and Astrophysics +Supplement Series, 47, 1, 1982), scaled by frequency to the -2.6 +power. This map has angular resolution of about 1 degree, and of +course most amateur EME antennas have much broader beamwidths than +this. Your antenna will therefore smooth out the hot spots +considerably, and the observed extremes of sky temperature will be +less. Unless you understand your sidelobes and ground reflections +extremely well, it is unlikely that more accurate sky temperatures +would be of much practical use. diff --git a/doc/user_guide/en/vhf-features.adoc b/doc/user_guide/en/vhf-features.adoc index 14c66221f..23e62fc1c 100644 --- a/doc/user_guide/en/vhf-features.adoc +++ b/doc/user_guide/en/vhf-features.adoc @@ -108,7 +108,11 @@ is generally used for EME on the 5.7 and 10 GHz bands. - For EME QSOs some operators use short-form JT4 messages consisting of a single tone. To activate automatic generation of these messages, -check the box labeled *Sh*. +check the box labeled *Sh*. This also enables the generation of a +single tone at 1000Hz by selecting Tx6, to assist in finding signals +initially. The box labeled *Tx6* toggles the Tx6 message from 1000Hz +to 1250Hz to indicate to the other station that you are ready to +receive messages. - Select *Deep* from the *Decode* menu. You may also choose to *Enable averaging* over successive transmissions and/or *Enable deep @@ -151,15 +155,15 @@ image::JT65B.png[align="center",alt="JT65B"] === QRA64 -QRA64 is an experimental mode in Version 1.7 of _WSJT-X_. The mode is +QRA64 is an experimental mode in Version 1.8 of _WSJT-X_. The mode is designed especially for EME on VHF and higher bands; its operation is -generally similar to JT65. The following screen shot shows an example -of a QRA64C transmission from DL7YC recorded at G3WDG over the EME -path at 24 GHz. Doppler spread on the path was 78 Hz, so although the -signal is reasonably strong its tones are broadened enough to make -them hard to see on the waterfall. The red curve shows that the -decoder has achieved synchronization with a signal at approximately -967 Hz. +generally similar to JT4 and JT65. The following screen shot shows an +example of a QRA64C transmission from DL7YC recorded at G3WDG over the +EME path at 24 GHz. Doppler spread on the path was 78 Hz, so although +the signal is reasonably strong its tones are broadened enough to make +them hard to see on the waterfall. The triangular red marker below +the frequency scale shows that the decoder has achieved +synchronization with a signal at approximately 967 Hz. image::QRA64.png[align="center",alt="QRA64"] @@ -177,12 +181,19 @@ most likely value for each of the message's 12 six-bit information symbols. A decode is declared only when the total probability for all 12 symbols has converged to an unambiguous value very close to 1. -TIP: In _WSJT-X_ Version 1.7 QRA64 is different from JT65 in that the -decoder attempts to find and decode only a single signal in the -receiver passband. If many signals are present you may be able to -decode them by double-clicking on the lowest tone of each one in the -waterfall. A multi-decoder like those for JT65 and JT9 has not -yet been written. +For EME QSOs some operators use short-form QRA64 messages consisting +of a single tone. To activate automatic generation of these messages, +check the box labeled *Sh*. This also enables the generation of a +single tone at 1000Hz by selecting Tx6, to assist in finding signals +initially, as the QRA64 tones are often not visible on the waterfall. +The box labeled *Tx6* switches the Tx6 message from 1000Hz to 1250Hz +to indicate to the other station that you are ready to receive messages. + + +TIP: QRA64 is different from JT65 in that the decoder attempts to find +and decode only a single signal in the receiver passband. If many +signals are present you may be able to decode them by double-clicking +on the lowest tone of each one in the waterfall. === ISCAT diff --git a/mainwindow.cpp b/mainwindow.cpp index a731d6e2d..17a6b2dd6 100644 --- a/mainwindow.cpp +++ b/mainwindow.cpp @@ -2765,8 +2765,8 @@ void MainWindow::readFromStdout() //readFromStdout } m_QSOText=decodedtext; } - if(m_mode=="FT8") auto_sequence (decodedtext.string(), 25, 50); - + if(m_mode=="FT8" or m_mode=="QRA64") auto_sequence (decodedtext.string(), 25, 50); + postDecode (true, decodedtext.string ()); // find and extract any report for myCall @@ -4814,7 +4814,7 @@ void MainWindow::on_actionQRA64_triggered() "Using old QRA64 sync pattern."); m_bQRAsyncWarned=true; } - displayWidgets(nWidgets("111110010010111110000000")); + displayWidgets(nWidgets("111110010110111110000000")); statusChanged(); }