Hello Uwe,
I downloaded your most recent version - TNX! Last week during the big aurora, I
noticed that Q65-30C mode fails to advance the selected messages under certain
circumstances. I don't know but I think this might be a behavior in all the Q65
modes. It does not seem to be a problem with FT8, which operates very smoothly ;-)
Specifically, it seems that the messages to be sent do auto advance and the Logging
Screen pops up as expected if the station you are working replies to your TX3 message
with a RRR. The Logging Screen then pops up as you send 73, and the next message
advances to CQ (TX6) so you are ready to Enable TX again and work the next station.
HOWEVER, if the station I am working replies to me with TX3, the program advances for
me to transmit RRR (TX4) and then it just stalls (no advancing to the next message,
and ENABLE TX is disabled) and no logging window pops up. The other station logs the
contact but you just stop operation without logging.
I seem to recall that this behavior also was experienced with Q65-60A, and perhaps
even with Q65 PILEUP. However, I was only able to double check the Q65-30C mode today
on the air with a local station. It sure would be great if the program would work
more reliably in the Q65 mode.
MNI TNX and VY 73, Lance
On 5/10/2024 05:38:24, Uwe, DG2YCB via groups.io wrote:
Dear WSJT-X_IMPROVED Users,
I am glad to announce that a new "240510" release of wsjt-x_improved 2.7.1-devel is
available for download. The code "240510" brings a number of important fixes and
detail improvements, so I recommend everyone to update to this version.
Furthermore, it introduces a new feature: for the first time, it is now possible to
trigger the ATU tuning function on your transceiver directly from the program. This
video provides further information <https://www.youtube.com/watch?v=wyp1P2tvI7k>.
Here is the changelog:
* The Settings dialog now only resets the frequency to band/mode default if
it is
really necessary (rig failure, "oob", etc.). This means that you can now
quickly switch something on or off in the Settings (e.g. filters, alerts or
similar) without leaving DXpedition QRGs or the like. Very useful also for
EME
operation! A click on the mode button brings you back to your preferred
band/mode default frequency. If, in very rare cases, inconsistencies occur,
restart the program, try to reproduce the unwanted effect and give me a
report
of what exactly is wrong.
* Some improvements to the Wait & Call feature: The Wait & Call timeout is now
prevented when the station you have in your DX Call box sends you a message.
Then, the DX Call button turns yellow again but "Enable Tx" keeps red,
meaning
that your QSO with this station can no longer be interrupted by the W&C
timeout.
* Right-click functions are now less error-prone. This code improvement is
effective for all operating systems.
* Double-clicking on a "73" message to you from a station whose callsign is
still
in the DX Call box no longer triggers calling CQ. This prevents
unintentional
transmissions in certain QSO situations.
* New feature: Right-click on the Tune button initiates the ATU tuning
function
on your transceiver. Note: This feature is currently only supported with
some
rig models (e.g. IC-7300 or FT-991), and when the rig is connected via
hamlib.
* The Tune watchdog is now adjustable. Default is 60 seconds. You can set any
value between 0 and 300 seconds, and you can deactivate the Tune watchdog
completely. Note that the logic of the "Tune watchdog" checkbox is now
inverted: If the checkbox is set, the watchdog is switched on.
* Right-clicking the band buttons bring you now also to the DXpedition
frequencies when in FT4 mode. This is useful as we had recently some
"DXpeditions" using MSHV FT4 multi-streaming on the DXp QRGs.
* Improved readability of all labels and buttons with a red background. For
these, the text color (= foreground color) has now been set to white
instead of
black. This is relevant for the following buttons: Tune, Enable Tx, DX Call,
and "H".
* Fixed a bug with CQ: XYZ that AB1CD or B1CDE could falsely trigger a reply
for
B1CD.
* Fixed various minor inconsistencies related to some internal timers and a
few
rare issues.
* Added a new Help menu item "Recommended audio settings". Further
information on
this topic can now also be found on the project homepage
<https://wsjt-x-improved.sourceforge.io/>.
* Update to hamlib 4.6_2024-05-03_SHA=424a34.
As always, you can download the new version from my SourceForge page:
*https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.7.1/*
*Note:* If the Hamlib update does not work properly for your rig, simply click on
the "Revert Update" button on the Radio tab of the Settings dialogue, and you will
be back to the previously used version. Don't forget to also inform Mike W9MDB
about your problems in such a case.
*Special version
"wsjtx-2.7.1-devel-win64_improved_PLUS_240510-001_blocks_UDP_after_band_changed.exe
<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.7.1/wsjtx-2.7.1-devel-win64_improved_PLUS_240510-001_blocks_UDP_after_band_changed.exe>":*
Following our recent discussion on erroneous spots (particularly to RBN), I have
also created a special version "240510-001". It has one more experimental commit:
Sending out the decoded messages via UDP is blocked after a band change for
int(600.0*m_TRperiod), meaning that you must have received at least 60% of a
TRperiod in the new band before decoded messages are sent out again via UDP. This
is the value that we also use internally in the program to assign the decodes when
switching the band at any time so that it is consistent now. Please note that this
additional commit only means a change for external programs that are connected via
UDP.
It can help to prevent incorrect band assignments under certain conditions.
Honestly, given the fact that services like RBN get their data primarily from
skimmers, I don't expect it to have much effect. But certain users really wanted
such a change. Now it needs to be tested carefully and systematically. You should
also test whether there are any side effects with any third-party program.
If this commit proves successful, I will of course be happy to include it
permanently in wsjt-x_improved and WSJT-X.
73 de Uwe, DG2YCB
_._,_._,_
-------------------------------------------------------------------------------------
Groups.io Links:
You receive all messages sent to this group.
View/Reply Online (#2528) <https://groups.io/g/wsjtgroup/message/2528> | Reply To
Group
<mailto:wsjtgr...@groups.io?subject=Re:%20%5Bwsjtgroup%5D%20%22240510%22%20release%20of%20wsjt-x_improved%202.7.1-devel%20available%20%23WSJT-X%20%23improved>
| Reply To Sender
<mailto:dg2...@gmx.de?subject=Private:%20Re:%20%5Bwsjtgroup%5D%20%22240510%22%20release%20of%20wsjt-x_improved%202.7.1-devel%20available%20%23WSJT-X%20%23improved>
| Mute This Topic <https://groups.io/mt/106016114/432738> | New Topic
<https://groups.io/g/wsjtgroup/post>
Mute #improved <https://groups.io/g/wsjtgroup/mutehashtag/improved> | Mute #wsjt-x
<https://groups.io/g/wsjtgroup/mutehashtag/wsjt-x>
Your Subscription <https://groups.io/g/wsjtgroup/editsub/432738> | Contact Group
Owner <mailto:wsjtgroup+ow...@groups.io> | Unsubscribe
<https://groups.io/g/wsjtgroup/leave/12252350/432738/30209472/xyzzy> [w...@hotmail.com]
_._,_._,_
--
Lance Collister, W7GJ(ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR,
5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, S79GJ,
FO/W7GJ, TX7MB, TO7GJ, 3B9GJ)
P.O. Box 73
Frenchtown, MT 59834-0073
USA
TEL: (406) 626-5728
QTH: DN27ub
URL:http://www.bigskyspaces.com/w7gj
Skype: lanceW7GJ
2m DXCC #11 - 6m DXCC #815 - FFMA #7
Interested in 6m EME? Ask me about subscribing to the Magic Band EME
email group, or just fill in the request box at the bottom of my web
page (above)!
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
