[wsjt-devel] Mock FT8 Roundup Observations

2018-10-25 Thread Joe Taylor
Everyone seems to have had fun exercising the RTTY RU features in 
WSJT-X.  I did, too, making 37 QSOs in a little over an hour using 100 W 
and a dipole.


I found more things wrong than others have reported, so far.  I will 
document them carefully and report here more fully in a little over a 
week.  (I will be busy with other commitments from Oct 26 through Nov 1.)


Bottom line, as I see it today:

It's clear that the new FT8 message formats can work well for RTTY 
contesting.  We still have work to do on improving the contest-oriented 
user convenience features.


-- 73, Joe, K1JT


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Mock FT8 Roundup Observations

2018-10-25 Thread mail
I also played the entire hour, only worked 7 stations. My recieved signal reports were mostly 539, 549 so maybe I could have bumped up the power to be heard better. I spent most of the hour calling CQ with 5 responses although plenty of stations decoding/scrolling in the band activity window. No multiple calls to try out the "TU". I managed S on 2 stations that the color coding showed were needed grids.May have been my low power, twice a station that had answered my CQ did not respond with RR73 (or mine did not decode it) my side stayed in report sending mode waiting for the RR73 while they had moved off to another qso and did not respond to my reports until several minutes later, by then I had stopped the TX and cleared the qso to try to start calling CQ again, the resulting "2nd attempt" qso going to my log showing their call instead of rst & state in the rcvd field. Therefore I spent some time getting my log reports straightened out before getting back to TX CQ. That would be frustrating in a contest. Probably not the software's problem, just how it sometimes goes in a contest.I unchecked the RTTY box right after the mock contest to try out the 77 bit, but remaining stations were still in RU sending, so I only managed to have 1 "post contest" qso in 77 bit which resulted in me sending a -10 report and the other station sending 549 FL. Activity heard died off pretty quickly, and I got no response to further CQs in 77 bit.73Doug KV4ZY


 Original Message --------
Subject: [wsjt-devel] Mock FT8 Roundup Observations
From: "Ed Muns" <e...@w0yk.com>
Date: Wed, October 24, 2018 11:46 pm
To: "'WSJT software development'" <wsjt-devel@lists.sourceforge.net>

 I played the entire hour but only worked 7 stations.  There seemed to be a lot of participants, which is great, but I was not able to work very many of them.  I’m not sure if (1) my signal strength was too low, or (2) if my signal quality was poor, or (3) if I was running WSJT-X RC3 incorrectly.  Regardless, I felt I could enjoy HF FT8 contesting with WSJT-X at some point in the future.   My notes:   1.  Some people called me on my Tx frequency.  In general, I think it is better if people call on a different (clear) frequency.  I would add this to the “tips”, that is, encourage folks to check ‘Hold Tx’.   2.  I could never figure out how to call a CQer on the cycle following their CQ.  My Tx cycle had already started by the time I could click on their call from their CQ in the prior cycle.  Is there a technique I’m missing or is this an inherent issue (delay of 30 seconds)?   3.  I really missed the ability to call multiple stations.  Yes, I know it is not part of current contest rules, but I think it should be in the case of FT8.  This is a chicken vs. egg problem.  What changes first: the rules or WSJT-X?  Knowing that it is possible to easily have multiple parallel QSOs but being artificially restricted, is frustrating for an HF contester.  I advocate FT8 contests allow multiple parallel QSOs with the same audio passband.   4.  When my Tx frequency was less than 1000 Hz, WSJT-X dropped my Tx carrier frequency from 7.078 to 7.077.  I assume WSJT-X then added 1000 Hz to my Tx audio frequency but I couldn’t be sure.  This is probably explained in the documentation but I haven’t found it.   5.  I was hoping to try the ‘TU;’ sequencing but never got called by more than one station at a time.  The only stations I saw doing this were VP8LP and K1JT.   6.  The vast majority of stations were between 1000-2000 Hz on the 7.078 carrier frequency.  Is this coincidence or a function of something I don’t yet understand?  Why aren’t they lower and higher?   7.  When I’m CQing and getting no response, what happens if I click on another CQer in my Rx cycle?  I tried this a couple times and couldn’t be sure what I was transmitting in the next cycle: another CQ or my exchange to the other CQer?   73, Ed W0YK___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Mock FT8 Roundup Observations

2018-10-25 Thread Jim Brown

On 10/24/2018 8:46 PM, Ed Muns wrote:
*/My Tx cycle had already started by the time I could click on their 
call from their CQ in the prior cycle.  Is there a technique I’m missing 
or is this an inherent issue (delay of 30 seconds)?/*


Experience has been that if you have a good signal at the other end, a 
TX that begins in the first 2-5 seconds is often decoded.


73, Jim K9YC


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Mock FT8 Roundup Observations

2018-10-24 Thread Ed Muns
I played the entire hour but only worked 7 stations.  There seemed to be a
lot of participants, which is great, but I was not able to work very many of
them.  I'm not sure if (1) my signal strength was too low, or (2) if my
signal quality was poor, or (3) if I was running WSJT-X RC3 incorrectly.
Regardless, I felt I could enjoy HF FT8 contesting with WSJT-X at some point
in the future.

 

My notes:

 

1.  Some people called me on my Tx frequency.  In general, I think it is
better if people call on a different (clear) frequency.  I would add this to
the "tips", that is, encourage folks to check 'Hold Tx'.

 

2.  I could never figure out how to call a CQer on the cycle following their
CQ.  My Tx cycle had already started by the time I could click on their call
from their CQ in the prior cycle.  Is there a technique I'm missing or is
this an inherent issue (delay of 30 seconds)?

 

3.  I really missed the ability to call multiple stations.  Yes, I know it
is not part of current contest rules, but I think it should be in the case
of FT8.  This is a chicken vs. egg problem.  What changes first: the rules
or WSJT-X?  Knowing that it is possible to easily have multiple parallel
QSOs but being artificially restricted, is frustrating for an HF contester.
I advocate FT8 contests allow multiple parallel QSOs with the same audio
passband.

 

4.  When my Tx frequency was less than 1000 Hz, WSJT-X dropped my Tx carrier
frequency from 7.078 to 7.077.  I assume WSJT-X then added 1000 Hz to my Tx
audio frequency but I couldn't be sure.  This is probably explained in the
documentation but I haven't found it.

 

5.  I was hoping to try the 'TU;' sequencing but never got called by more
than one station at a time.  The only stations I saw doing this were VP8LP
and K1JT.

 

6.  The vast majority of stations were between 1000-2000 Hz on the 7.078
carrier frequency.  Is this coincidence or a function of something I don't
yet understand?  Why aren't they lower and higher?

 

7.  When I'm CQing and getting no response, what happens if I click on
another CQer in my Rx cycle?  I tried this a couple times and couldn't be
sure what I was transmitting in the next cycle: another CQ or my exchange to
the other CQer?

 

73,

Ed W0YK

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel