ve2ebk
User
Platinum Boarder
| Posts: 732 |   |
Karma: 5
|
Re:FT8 to be Permitted in 2019 ARRL RTTY Roundup - 2018/10/25 09:12
J'ai fait quelques Q hier dans le RU test avec la version WSJT-X 2.0 #RC3.
Mes remarques sont:
1- N1MM+ ne log pas l'échange (State/Prov ou le serial pour les DX)
Explication de Rick N2AMG: Il faut choisir Digital au lieu de RTTY dans Mode du contest.
2- Call 1st ne fonctionne pas
3- Délais de 3-4 sec pour faire TX après avoir choisi un call
Tant qu'aux autres commentaires, on peur se fier à W0YK et AA5AU
P.S. Il reste du travail à faire d'ici janvier
---------------------------------
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
1. No way to tell which stations have already been worked and
logged (dupes). Suggest stations calling CQ which are already in
the log be highlighted in gray color.
2. If you close the program and restart it, the log window does
not retain logged QSO info. It's blank. Cabrillo log does still
show all contacts.
3. "Log Automatically" works only in contest mode. Is this by design?
4. VE1BZI and KC9IL both answer my CQ. Clicked on both (VE1BZI
first) to invoke "next". Could not complete with VE1BZI and when I
called KC9IL, he did not come back. Called CQ but "next" remained
active. KC9IL then called and we completed but when I finished,
"next" kicked in and sent him a report again. "Next" never cleared
and I was stuck and could not answer any other stations. Had to
restart the program. Need a way to clear "next" manually. I doubt
"next" is an effective tool for FT8 contesting. Most aren't going
to stick around to wait to see if you call them. I would probably
not use it in an FT8 contest. Instead, I would just opt to send
CQ. If the other station is still there, they will call again.
Unlike the previous test, this was the only time I got called by
more than one station so couldn't test "next" again.
5. On a couple of occasions when calling CQ and a station answered
with Tx2, the program sent Tx2 back to them when it should have
been Tx3. See example here:
6. Cabrillo file looks good. Just need a header now.
Don AA5AU
Post edited by: ve2ebk, at: 2018/10/29 10:34
|
Forum