Joe and all Dx Pedition Mode developers,
I am with Joe about the share of modes which he raised in the statistics.
Congratulations and I hope FT8 will soon beat the rest of the modes. FT8 gives
me a new joy about Dx pedition hunting while listening my favorite music and
writing e-mails to
A friend of mine from my amateur radio club, Yavapai Amateur Radio Club,
Prescott, AZ, is one of the ops on the Baker Island DXpedition. He has
lots of experience working the CQ World Wide CW Contest with the Voodoo
Contest Group in African and Middle Eastern countries. I'm really
looking
I’ve literally only heard them with FT8 (still haven’t gotten them in the log
because I could only hear them for about an hour on 20 and an hour on 30 at -20
and below) – I’ve heard the pileup for CW and SSB but can’t hear Baker at all.
If that trend continues, my ONLY chance of getting them
In my opinion FT8 has been working great in its first outing. And it's
proven robust enough to keep working when some operators are not set up
correctly. Just RTFM and you'll do well.
And don't be threatened by a new way of operating. As Joe points out, work
them CW and SSB when you can, FT8
I also agree with Mike. Blind calling should be prevented somehow by software.
People do not read manuals, unfortunately.
JT and FT modes have clearly shown "diode" conditions of bands. Blind
transmitter does not receive Dx, but Dx may copy him well and waste his time
trying to make qso.
Of
I would like to approach this idea with some set of principles that everybody
can agree on...so here goes...
#1 Maximize QSO rate#2 Minimize blind callers
Just those two principles are enough to say we should do whatever we can to
reduce blind callers which will also help to maximize QSO rate as
By the way... is the English guide in another format so I can edit and
reuse at least the images?
Thanks
El sáb., 30 jun. 2018 21:16, Jaime Robles escribió:
> Hello all,
>
> I can take the Spanish guide. :-)
>
> Jaime, EA4TV
>
>
> El sáb., 30 jun. 2018 19:47, Joe Taylor escribió:
>
>> Hi Jarmo
Hello all,
I can take the Spanish guide. :-)
Jaime, EA4TV
El sáb., 30 jun. 2018 19:47, Joe Taylor escribió:
> Hi Jarmo and all,
>
> On 6/30/2018 10:54 AM, jarmo wrote:
>
> >> Translations of the FT8 DXpedition Mode User Guide into German,
> >> Polish, and Norwegian are available on the
Hi Mike
I think this is worth considering.
Or maybe a warning message like 'Do you *really* want to call when you have
not yet decoded the fox?'
Charlie
_
From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: 30 June 2018 20:21
To:
I'll modify the idea to recognize ANY call from the DXpedition (i.e. the call
in the DX Call box).Surely you'd have to agree that you should see them once
before calling...either CQ or answering somebody else. And the software should
enforce it.
de Mike W9MDB
On Saturday, June 30,
There are several people who have outright said they refuse to use 1.9.1 (or
WSJTX in general) and/or that they refuse to use DXPedition Mode because they
“don’t agree with being forced to use it.” I’m willing to bet some of the
people causing QRM fall into that category, as well, for some odd
Wholly concur with #2, but not necessarily #1, Mike. Yes, lots of folks are
calling in the blind. That’s not limited to FT8, guys.
But…
Depending on who’s running the digital tent (Don/Ned/?), rates of CQ vary from
every 10 minutes to generate some traffic down to NONE, because there
On 6/30/2018 10:14 AM, Black Michael via wsjt-devel wrote:
... I noticed the the Baker team gave a lukewarm endorsement
of FT8 on their news update ...
I do not consider their endorsement of FT8 to be lukewarm, at all.
Currently they have uploaded 12,319 QSOs to ClubLog:
CQ 4,735
SSB
As noticed in my previous post, my experience was the fox was not
calling CQ every five minutes, but simply working station after station.
Seeing as how I could copy all his transmissions, I called him, and got
the QSO. I don't feel guilty about how I worked him. I figure as long as
I can copy
The Baker Island DXpedition has brought out the very worst: Stations calling
blind for hours when KH7Z is not even on FT8, incessant calling below 1000 hz,
calling the wrong call sign (KH7V), calling in the wrong time slot, etc. One
would think that it would be reasonable to at least skim the
I can't say I agree with Mike that one should have to answer a CQ to
work the DXpedition station.
I worked KH7Z on 17M this past Thursday. However, in the time I was on
the frequency, I did not decode any CQ. KH7Z was working stations the
entire time I was on frequency. I simply kept an eye
Hi Jarmo and all,
On 6/30/2018 10:54 AM, jarmo wrote:
Translations of the FT8 DXpedition Mode User Guide into German,
Polish, and Norwegian are available on the WSJT-X web page
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
And into Fin, Saku OH1KH done and can be seen at:
On 6/30/2018 9:16 AM, Black Michael via wsjt-devel wrote:
I just tested this and Fox tried 3 times to respond to a blind call.
Define a "blind call." I would define it as calling someone you can't
copy.
As others have observed, an expedition op with a screenful of callers is
unlikely to
On 6/30/2018 7:14 AM, Black Michael via wsjt-devel wrote:
Tons of ops calling KH7Z when they can't see them. I assume this only
causes problems as it's quite possible KH7Z with their honker antennas
and can see them but not the other way round.
It's not "big honker antennas" -- the
Neil
Thanks - that's very helpful.
I didn't waste much time calling!
The other clue was that it was at a time when the propagation predictions
were blank.
Charlie
_
From: Neil Zampella [mailto:ne...@techie.com]
Sent: 30 June 2018 17:21
To:
For the record, here's the "Most important advice for Hounds" that I
posted to wsjtgroup yesterday:
1. Read the FT8 DXpedition Mode User Guide. Read it all!
http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf
2. You must select Hound mode.
3. The *Tx even/1st* box (grayed out)
I thought the goal of DXpedition mode was to optimize the QSO rate.The
DXPedition has no idea if the station calling can actually hear them so why
should WSJT-X allow it?
Allowing such blind calls is the antithesis to optimizing rates.
They haven't tried it because everybody is calling them
Charlie,
the consensus of many on the FB pages is that this station was a pirate.
Neil, KN3ILZ
On 6/30/2018 11:09 AM, Charles Suckling wrote:
Hi Mike
The problem with needing to see a CQ is that the dxpedition may rarely
transmit a CQ (some folks were reporting this yesterday). Then,
I just tested this and Fox tried 3 times to respond to a blind call.
I can guarantee that the majority of calls were blind and thus causing all
sorts of time wasting at the DXPedition.
We really need to block blind calling so enforce the CQ-every-5 and prevent
transmitting until you see CQ from
Hi Mike,
we are not hear to determine how operators at a DXpedition site choose
to operate, we are not aware of conditions on the ground. If they feel
that they are getting optimum rates without calling CQ then that is
their choice. Remember that calling CQ from a rare entity can result in
a
But what about them receiving all these calls in the blind? Isn't that going
to interfere when they try to respond to people who can't hear them?
Mike
On Saturday, June 30, 2018, 11:04:11 AM CDT, Bill Somerville
wrote:
On 30/06/2018 16:57, Black Michael via wsjt-devel wrote:
On 30/06/2018 16:57, Black Michael via wsjt-devel wrote:
OK...so it appears the CQ every 5 trasnmissions is NOT enforced unless
Fox clicks the "More CQs" box.
We'd be a lot better off if this was always forced and Hounds were
restricted to only answer CQ's.
This explains why we don't see the
OK...so it appears the CQ every 5 trasnmissions is NOT enforced unless Fox
clicks the "More CQs" box.We'd be a lot better off if this was always forced
and Hounds were restricted to only answer CQ's.This explains why we don't see
the CQ's and calling blind is normally necessary (as long as you
Please give a logical explanation why you think transmitting in the blind is
OK?DXpeditions generally run very good antennas on beaches in quiet places and
can receive pretty well.
The is absolutely NO reason to call them until you hear CQ as long as WSJT-X
forces a CQ every 5 transmissions.
If
WSJT-X has already been changed where Fox transmits CQ every 5 transmissions
now.If you don't see it then you shouldn't be calling.
>From the git log:
In DXpedition mode, enforce a Fox CQ at least every 5 transmissions.
On Saturday, June 30, 2018, 10:10:09 AM CDT, Charles Suckling
Sat, 30 Jun 2018 09:27:03 -0400
Joe Taylor kirjoitti:
> Hi all,
>
> In case you were not aware, and one of them would be helpful to you
> or someone you know:
>
> Translations of the FT8 DXpedition Mode User Guide into German,
> Polish, and Norwegian are available on the WSJT-X web page
>
Hi Mike
The problem with needing to see a CQ is that the dxpedition may rarely
transmit a CQ (some folks were reporting this yesterday). Then, stations
were working them by just calling. Majority were on the correct period,
most were above 1000Hz. From what I could see here about 90% of
I have some observations too.
#1 Tons of ops calling KH7Z when they can't see them. I assume this only
causes problems as it's quite possible KH7Z with their honker antennas and can
see them but not the other way round. So KH7Z will put them in the queue and
try to process them taking up the
Here's a patch for the txfirst problem. Explicitly use Hound/Fox mode to set
the checkbox before using the message time.
https://www.dropbox.com/s/3isqkm0hgpevmfd/txfirst.patch?dl=1
de Mike W9MDB
On Saturday, June 30, 2018, 3:33:38 AM CDT, Neil Zampella
wrote:
I realize I didn't
Hi all,
In case you were not aware, and one of them would be helpful to you or
someone you know:
Translations of the FT8 DXpedition Mode User Guide into German, Polish,
and Norwegian are available on the WSJT-X web page
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Many thanks to
Joe,
An observation if I may about expedition mode. I see with KH1/KH7Z that the
number of Fox TX channels varies - I presume as they place more stations in
the queue. As expected, the power per channel drops the more channels
running so that the amplifiers can keep up. However, this has an
I realize I didn't give the release number: 45427a (all that is shown
there).
Neil
On 6/30/2018 4:19 AM, Neil Zampella wrote:
Joe,
I was able to duplicate this this morning.
Action:
WSJT-X in Hound mode on 20m, I was trying to adjust my bandwidth
properly to make sure I can see the FOX
Joe,
I was able to duplicate this this morning.
Action:
WSJT-X in Hound mode on 20m, I was trying to adjust my bandwidth
properly to make sure I can see the FOX at around 200 + Hz. Not
seeing a thing there, but then saw one station that was replying at
305, and thought at least they see
Hi, this is a thought working with KH1/KH7Z to avoid continuous TX3 repeats
when their sig is so weak such as -20. It was actually happed for my 15m
unsuccessful QSO.
In the below table, my proposal is to increase the power of sequence 7 for
example 6 dB, to make sure W9XYZ receives RR73
Hi Mike
Yes, clicking a Hound message caused the greyed out box to get checked, and
it then tried to call the other Hound:
I saw one or two examples of Hounds calling other Hounds yesterday - this
perhaps explains how it happens.
Charlie
_
From: Black
40 matches
Mail list logo
