I posted this inquiry and didn't realize I had unsubscribed from the
list. I then re-subscribed and got the confirmation of doing so. I then
reposted the issue but got no response and in looking at the posts for
September, my subscription was renewed Sept. 2nd, I did not find my post.
My issue is that lately for some reason, WSJT-X is adding the prop_mode
ECH to my QSOs which I assume means the propagation mode was the Echo
mode. This is causing rejections from QSOs on eQSL as eQSL shows the
contacts as FT8 EchoLink. When I discovered the reason, I ended up
having to remove the "<prop_mode:3>ECH" from the QSOs before I upload
them to LoTW, eQSL, Club Log and QRZ.
I have never used the Echo mode with WSJT-X and would like to know why
this is happening and what can be done about it. I have double-checked
all my settings for WSJT-X to make sure the Echo mode has not been set
and found it is not set. Here is an example from my WSJT-X wsjtx_log.adi
file:
<call:6>JH7AUL <gridsquare:4>QM07 <mode:3>FT8 <rst_sent:3>+03
<rst_rcvd:3>+00 <qso_date:8>20240907 <time_on:6>015215
<qso_date_off:8>20240907 <time_off:6>015245 <band:3>12m
<freq:9>24.917666 <station_callsign:6>WB9VGJ <my_gridsquare:6>DM34TQ
<tx_pwr:2>90 <prop_mode:3>ECH <eor>
I hope you or someone can provide an answer to me on why this is
happening. It is happening with version v2.6.1 6b6d74 and also happened
with the new SuperHound candidate version 2.7.0.rc6. I first thought it
was the new version causing this, so I went back to v 2.6 and it still
is happening.
73,
John, WB9VGJ
--
John L. Broughton
wb9...@arrl.net
2silverhon...@gmail.com
www.wb9vgj.us
--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
