Hello Scott..
Excuse me, must say, you was true.. I haven't tried it yesterday, because PC
was off that time and I didn't want disturb family..
Now heard you and called you on 20m and if set to DX Call - TI3/W7RI and
generate standard messages, it generates W7RI OK2ZO JN89.
If manualy set TI3/W7RI OK2ZO - it transmits only TI3/W7RI OK2Z
That's the issue.. The only full call is shown in TX5 - TI3/W7RI 73
If you had just TI/W7RI, it would be like I have written lower..
Therefore it realy can have an effect, you have mentioned..
Tried profile from your side, setting type 2 call in TX1 or TX3 is not good to
the pile, so only TX5 is usable.
Tx6 as of standard CQ TI3/W7RI EJ79.
So, the only solution is use more often Tx6 and Tx5..
73 Libor
P.S. Heard you only very short time, then the band started closing.. right as
written lower..
On Monday, December 4, 2017, 5:36:00 PM CST, Libor Holous OK2ZO
<ok...@email.cz> wrote:
Dear Scott..
Look.. As I said, experienced smart operator will get the call correctly..
The others can repair it in their logs anytime later. It's not your problem.
The system is setup this way, so if you can't get standard call, you must use
compound and count with it.
Lets see the example, not only for you or Gary...
On your side, I'd not use automatic reply 1st. Sit to some QRG, best lower
one 300-500Hz, switch fixed QRG on.
Tx6 CQ UP TI5/W7RI
Tx5 DE TI7/W7RI EJ79 - to include square for square hunters.
Tx4 switch to RR73
In Settings - set Doubleclick enable TX.. Open logging dialog automaticaly.
And lets go for QSO as automat works..
CQ UP...
Who replies with Tx1:
TI7/W7RI OK2ZO
OK2ZO W7RI -01
W7RI OK2ZO R-02
OK2ZO W7RI RR73 ... opens logging dialog - logging QSO
W7RI OK2ZO 73 ... during receiving this, double clicking to another station
of your choice, or you can let continue the automat with DE TI5/W7RI EJ79
One minute or 1.5 minute on ideal state..
Who replies with Tx2:
W7RI OK2ZO -10
OK2ZO W7RI R-03
W7RI OK2ZO RR73
DE TI5/W7RI EJ79 ... logging dialog, clicking save, quickly double clicking
next in list or wait until Tx5 is complete and waiting for new callers.
45s or 1.25 min for QSO.
You miss Grid here, but if it's not important for you? (BTW, you get it from
LotW when confirmed).
If sb. calls you with Tx1 like:
W7RI OK2ZO JN89
you can bet, he's got wrong call. Then you can click on Tx5 or Tx6 or just
reply to another caller and let Tx5 go during that period. If is not an idiot?
- return to first paragraph of this mail..
----------------------
According my previous "question", my experience with lots of stations from
NA/SA is bad. They prefer US wide open window against Central EU, especialy on
upper bands. If they work EU, than here is band closed already and they work
West EU or BigGuns only. And it's not only on FT8 of course.. In US? - EU is
not interesting - rather ragchewing within US, right when opening to us..
Thats from my experience... I can't have some beams and towers in the town.
Vertical on the roof is a miracle for me and luxury, the others can't have.
I'm not a big gun, but also with just a little bullet you can hit, if you
know howto...
I thank so much to all authors of such wonderful mode, which helps me aiming
much better..
73s.
Libor
PS.. I do apologise for probable errors in my English..
Odesláno ze zařízení Samsung
-------- Původní zpráva --------
Od: Scott Bidstrup <sc...@bidstrup.com>
Datum: 04.12.17 21:52 (GMT+01:00)
Komu: wsjt-devel@lists.sourceforge.net
Předmět: Re: [wsjt-devel] Another Compound Callsign Problem
On 04/12/2017 12:57 p.m., Libor Holous OK2ZO wrote:
> Experienced users will quickly know, you are from Costa Rica.. Just send
> time to time CQ and standard 73 message with full call..
Libor, I understand what you are saying, but the reality is that a lot
of fellows in the States, when they sit down for a session, will simply
glance at the band activity window and not connect up my abbreviated
call and my full callsign, because it may not appear on their list of
decodes. If my full callsign, from a CQ or 73 message doesn't appear in
the band activity window, they will not appreciate that I am a DX station.
I do, in fact, call CQ frequently - mostly so my full callsign gets out
there, and also because it makes starting an autosequence more sure.
But when I'm working a pileup, as I am most of the time, I can go for
quite a few QSOs - ten or fifteen minutes - with the software never
sending a CQ, but simply replying to the first decode that pops up after
my last 73 message, and Call 1st then sends to the standard messages.
When that happens, I do not send a complete callsign at all until the
next 73 message, (and technically, that's not legal under the rules here
- we are supposed to transmit the full, unabbreviated call signs of ours
and the other station's call, during the first and last transmissions in
a QSO and "frequently" in between). And it also means my full callsign
is transmitted far less frequently, as it appears only in the 73
messages I send. If the other station who might be considering calling
me has a lot of band activity that is generating a ton of decodes, he
may not ever notice that my full call is a DX callsign. And very few,
if any, ever will ever figure it out from my grid square alone.
> Anybody will always put you to the cluster, so you won't have to be
> worry, you not have a pileup..
That is not always true when I am working a lot of Stateside stations,
many of which probably never realize, till my 73 message, that they've
even worked a DX station. Many, if not most stations in the States will
never spot me to the cluster (because, even though I'm DX, I'm in a
commonly worked country), and, because of my proximity to the States,
they represent the bulk of stations I work.
I can always tell when I've been spotted to the cluster because the
pileup instantly gets much bigger. And that happens only infrequently
when most of the stations I am working are Stateside. When I am working
a lot of Europeans, yes, at least a third of the stations I work there
will spot me. But that is a much less common practice in the States.
> Question is, if EU is more DX than US for you? For lot of stations from
> Caribean it's opposite..
For purposes of awards, they're all the same - anything outside of Costa
Rica is DX to me - including 200km up the road in Nicaragua or 150 km
down the road in Panamá. If your question is whether I am more desirous
of working E.U. than U.S., no, it doesn't matter to me as I'm not really
much of a DX chaser, unless it's a country I haven't worked, and then I
want it - no matter where it is. And in E.U. all I am lacking are
Andorra and Lichtenstein, but still lack several in Latin America,
mostly in the Caribbean.
73,
Scott Bidstrup
TI3/W7RI
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
http://sdm.link/slashdot_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
