10:55:59 AM
To: WSJT software development
Subject: RE: [wsjt-devel] Observation on Expedition Mode
Joe,
I am waiting your response to my previous message to recalculate additional
gain for myself.
To make sure my intention, I described the inquiry as follow.
One FT8 frame has 7x7x3 =147 bits
: WSJT software development
Cc: Steven Franke
Subject: Re: [wsjt-devel] Observation on Expedition Mode
Hi Take,
Your textbook figure shows the difference in Eb/N0 required to achieve 10^-4
BER on the AWGN channel, using single-symbol non-coherent detection.
Please consider the fact that if the SNR is
inkId=550986> for Windows 10
>
> From: Tsutsumi Takehiko mailto:ja5...@outlook.com>>
> Sent: Wednesday, July 4, 2018 10:20:16 PM
> To: WSJT software development
> Cc: Steven Franke
> Subject: RE: [wsjt-devel] Observation on Expedition Mode
>
> Steve,
>
> Thank yo
Hi Take,
On 7/5/2018 9:55 PM, Tsutsumi Takehiko JA5AEA wrote:
I am waiting your response to my previous message to recalculate
additional gain for myself.
To make sure my intention, I described the inquiry as follow.
One FT8 frame has 7x7x3 =147 bits synch words and I understand current
DX
is trying to help you avoid making a mistake.
Dave / NX6D
From: Joe Taylor
Sent: Thursday, July 5, 2018 5:26:35 AM
To: k...@arrl.net; WSJT software development; Jim Brown
Subject: Re: [wsjt-devel] Observation on Expedition Mode
Hi Dave, Jim, and all,
On 7/4
ows 10
From: Tsutsumi Takehiko
Sent: Thursday, July 5, 2018 1:09:38 PM
To: WSJT software development
Subject: RE: [wsjt-devel] Observation on Expedition Mode
Joe,
It is good to hear from you to increase your calculation about my additional
gain proposal from +(1~8) dB to +(1.5
Simple patch to solve this problem...
@@ -4031,6 +4031,10 @@ void
MainWindow::doubleClickOnCall2(Qt::KeyboardModifiers modifiers)
void MainWindow::doubleClickOnCall(Qt::KeyboardModifiers modifiers)
{
+ if (m_config.bHound()) {
+ MessageBox::information_message(this,"You must enter the
Hi Charlie and all,
On 7/5/2018 1:51 PM, char...@sucklingfamily.free-online.co.uk wrote:
Joe
I think there has been confusion in the ranks from two different
instructions to hounds.
Baker's website says to click a decode, and your instructions clearly
state to put the full expedition call
Joe
I think there has been confusion in the ranks from two different
instructions to hounds.
Baker's website says to click a decode, and your instructions clearly
state to put the full expedition call into the DX box.
I followed your instructions.
Charlie
That approach seemed to work for me.
73
Mark Spencer
VE7AFZ
netsyn...@gmail.com
> On Jul 5, 2018, at 9:59 AM, Black Michael via wsjt-devel
> wrote:
>
> So let's change the double-click on the Band Activity and tell them that
> rather than processing it.
> "You must enter the DXpedition
So let's change the double-click on the Band Activity and tell them that rather
than processing it."You must enter the DXpedition call yourself in the DX Call
box".
de Mike W9MDB
On Thursday, July 5, 2018, 11:56:20 AM CDT, Joe Taylor
wrote:
Jim --
On 7/5/2018 12:49 PM, Jim
Jim --
On 7/5/2018 12:49 PM, Jim Brown wrote:
On 7/5/2018 5:26 AM, Joe Taylor wrote:
There should be no need to edit the prefix in DXKeeper. When
attempting to work a DXpedition you know their callsign perfectly
well, in advance.
Yes, but -- when you click on their call when they have
On 7/5/2018 5:26 AM, Joe Taylor wrote:
There should be no need to edit the prefix in DXKeeper. When attempting
to work a DXpedition you know their callsign perfectly well, in advance.
Yes, but -- when you click on their call when they have called someone
else, you get KH7W, not KH1/KH7W,
Hi Dave, Jim, and all,
On 7/4/2018 8:56 PM, Jim Brown wrote:
On 7/4/2018 4:40 PM, David Fisher wrote:
Later when I uploaded to ClugLog, I was reminded that I logged the
wrong callsign. Easily fixed in ClubLog, but for LOTW, all I could do
was log the contacts again as KH1/KH7X.
I also
ink/?LinkId=550986> for Windows 10
From: Joe Taylor
Sent: Wednesday, July 4, 2018 11:27:08 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Observation on Expedition Mode
Hi Take,
On 7/4/2018 9:20 AM, Tsutsumi Takehiko JA5AEA wrote:
> C
On 7/4/2018 6:53 PM, Bill Barrett wrote:
Hello Jim-
I worked them several times and uploaded the contacts Club Log and LOTW but.
On Club Log I see "W" not green "C". No QSL in LOTW.
Just getting started with C.L. am I doing something wrong?
Go to ClubLog, but before you even sign in, click on
Hello Jim-
I worked them several times and uploaded the contacts Club Log and LOTW but.
On Club Log I see "W" not green "C". No QSL in LOTW.
Just getting started with C.L. am I doing something wrong?
Thanks;
73;
Bill W2PKY
On Wed, Jul 4, 2018 at 8:56 PM Jim Brown wrote:
> On 7/4/2018 4:40
On 7/4/2018 4:40 PM, David Fisher wrote:
Later when I uploaded to ClugLog, I was reminded that I logged the wrong
callsign. Easily fixed in ClubLog, but for LOTW, all I could do was log
the contacts again as KH1/KH7X.
I also simply click on their call when they're sending to someone else.
-devel
Sent: Monday, July 2, 2018 10:44:52 AM
To: 'WSJT software development'
Cc: Black Michael
Subject: Re: [wsjt-devel] Observation on Expedition Mode
In the case you give as long as you have the prior decode of them you would
just double-click it and that solves the problem as you have actually
Hi Take,
On 7/4/2018 9:20 AM, Tsutsumi Takehiko JA5AEA wrote:
Concerning the “second +4dB term”, I remember Bill’s suggestion included
hashing of callsign (I used the number of (28-15) x 5 = 65 bit
reduction). I also reduced five 7x7 synch to one 7x7 synch, which I am
not sure whether Bill
nesday, July 4, 2018 6:32:00 PM
To: WSJT software development
Cc: Steven Franke
Subject: Re: [wsjt-devel] Observation on Expedition Mode
Hi Take-san,
I meant QRAXX as “Q-ary Repeat-Accumulate Codes for Weak Signal Communications”
in Nico’s literature but I do not have any intent to modify wsjt-X
Hi Take-san,
> I meant QRAXX as “Q-ary Repeat-Accumulate Codes for Weak Signal
> Communications” in Nico’s literature but I do not have any intent to modify
> wsjt-X “QRA64” mode to this discussion.
Understood. But why not scale the well-known results from Nico’s excellent
QRA64 mode to see
ftware development
Cc: Steven Franke
Subject: Re: [wsjt-devel] Observation on Expedition Mode
Hi Take-san,
Additional gain comes from:
1. Adopt QRA64 or QRA128 utilizing 3kHz wide fox TX bandwidth : +4dB gain
I don’t think that there is 4 dB to gain here.
Nico showed that the 50% decoding thr
Hi Take,
On 7/3/2018 8:03 PM, Tsutsumi Takehiko JA5AEA wrote:
Joe, Just “listened and watched the show“???
I saw a critical message last night on a Japanese SNS that KH1/KH7Z FT8
OP should pay their respect to K1JT repeated calls and must promptly
return RR73.
Never fear, I have worked
from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
From: Joe Taylor
Sent: Tuesday, July 3, 2018 10:24:56 PM
To: WSJT software development; Tsutsumi Takehiko
Subject: Re: [wsjt-devel] Observation on Expedition Mode
Hi Grant, Take, and a
On 7/3/2018 6:24 AM, Joe Taylor wrote:
I think the Fox operators are learning to manage their pileups
reasonably well. I listened and watched the show on 40m this morning
for ~2.5 hours, with good signals from Fox. The Op was doing a good
job: he was using 2 slots, thereby keeping the queue
k they did on a couple of occasions)
> > I lost them and could never complete the QSO. It was from that perspective
> > that I made my observations.
> >
> > FWIW and further comment?
> >
> > Regards,
> > Grant VK5GR
> >
> >
> > -Origi
Mike --
On 7/3/2018 10:43 AM, Black Michael via wsjt-devel wrote:
Surely you jest...nobody reading directionslarge % calling in the
blindand they are going to learn how to control themselves based on
sig reports and slots? Not only do the majority not understand how
slots affects
rspective
> that I made my observations.
>
> FWIW and further comment?
>
> Regards,
> Grant VK5GR
>
>
> -Original Message-
> From: Joe Taylor [mailto:j...@princeton.edu]
> Sent: Tuesday, 3 July 2018 10:55 PM
> To: WSJT software development; Tsutsumi Takehiko
> Su
; Tsutsumi Takehiko
Subject: Re: [wsjt-devel] Observation on Expedition Mode
Hi Grant, Take, and all,
I think the Fox operators are learning to manage their pileups
reasonably well. I listened and watched the show on 40m this morning
for ~2.5 hours, with good signals from Fox. The Op was doing
ast day operation. I am expecting they
>> will expand their service at high and low bands.
>>
>> Regards,
>>
>> take
>>
>> de JA5AEA
>>
>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
>> Windows 10
>>
>> ---
On 7/3/2018 9:47 AM, Black Michael via wsjt-devel wrote:
That sounds like a jolly good ideabut why only 7dB improvement?
Wouldn't you recover all the loss from 5 slots=-14dB?
No.
With one signal handling 5 QSOs the information payload must be
increased from 72 to nearly 360 bits. The
Taylor [mailto:j...@princeton.edu]
Sent: Tuesday, 3 July 2018 10:55 PM
To: WSJT software development; Tsutsumi Takehiko
Subject: Re: [wsjt-devel] Observation on Expedition Mode
Hi Grant, Take, and all,
I think the Fox operators are learning to manage their pileups
reasonably well. I listened
gt;
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>
> *From:* Grant Willis
> *Sent:* Tuesday, July 3, 2018 7:05:09 AM
> *To:* 'WSJT software development'
> *Subject:* Re: [wsjt-devel] Observation on Expedition Mo
wlink/?LinkId=550986> for
Windows 10
*From:* Grant Willis
*Sent:* Tuesday, July 3, 2018 7:05:09 AM
*To:* 'WSJT software development'
*Subject:* Re: [wsjt-devel] Observation on Expedition Mode
Everyone,
The thread hi-
, 2018 7:05:09 AM
To: 'WSJT software development'
Subject: Re: [wsjt-devel] Observation on Expedition Mode
Everyone,
The thread hi-jacking has been interesting but time to bring it back to my
original question perhaps please?
Take,
Yes – the problem with varying power is I might hear him CQ w
here until certain preconditions are met - based on my
observations of the traffic patterns I don't see it helping the situation at
all.
From: Tsutsumi Takehiko [mailto:ja5...@outlook.com]
Sent: Monday, 2 July 2018 3:09 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Observation
In hound mode, would it be a good idea to use another watchdog timer to
trigger on received messages from the DX call, perhaps started with a 5 min
period (after first call) and reset to a longer timeout (15min?) on decoded
messages from the DX ? Additional reset by a longer idle period (say
I've been watching them (KH1/KH7Z) work various stations on 14 Mhz for the
last 30 Minutes or so. I have yet to see a single CQ from them.
73
Mark S
VE7AFZ
On Mon, Jul 2, 2018 at 7:38 AM, Bill Turner via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> I have seen kh7z answering
@lists.sourceforge.net]
Sent: Sunday, July 01, 2018 11:39 PM
To: WSJT software development
Cc: Black Michael
Subject: Re: [wsjt-devel] Observation on Expedition Mode
I foolishly thought that the commit message meant what it said. It should have
added "when the "More CQs box is checked".
I have seen kh7z answering stations on 20m last night at -7 to -20 strength.
Only saw one CQ at 11pm local in NC.
Sent from Yahoo Mail on Android
On Mon, Jul 2, 2018 at 9:24 AM, Russ wrote:
--
Check out the
11:39 PM
To: WSJT software development
Cc: Black Michael
Subject: Re: [wsjt-devel] Observation on Expedition Mode
I foolishly thought that the commit message meant what it said. It should have
added "when the "More CQs box is checked".
So the only way to solve all the lid
One question maybe some could answer is if they saw a Fox CQ and the Hound
responses but never saw the Fox secondary messages. You'd likely see several
repeats from the hounds that don't see the reduced power signal.
de Mike W9MDB
On Monday, July 2, 2018, 12:43:01 AM CDT, Tsutsumi
Grant,
Allow me to write my comment on your topic as I have same topic interest
writing “FOX adaptive power control” in this thread.
Concerning your proposal, i.e.“to have the setting of number of channels vs the
number of active channels maintain a constant PER CHANNEL TX power”
My comment
05 AM
To: 'WSJT software development'
Cc: Black Michael
Subject: Re: [wsjt-devel] Observation on Expedition Mode
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
Subject: Re: [wsjt-devel] Observation on Expedition Mode
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
That ain’t happening at KH1/KH7X. Not on 20M anyway.
Dave / NX6D
From: Black Michael via wsjt-devel
Sent: Saturday, June 30, 2018 8:39:05 AM
To: 'WSJT software development'
Cc: Black Michael
Subject: Re: [wsjt-devel] Observation on Expedition Mode
WSJT-X has
-devel
Sent: Saturday, June 30, 2018 7:14:54 AM
To: 'WSJT software development'
Cc: Black Michael
Subject: Re: [wsjt-devel] Observation on Expedition Mode
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
What branch has this been checked into?
The master branch doesn't appear to have any such change.
de Mike W9MDB
On Sunday, July 1, 2018, 9:37:53 AM CDT, Joe Taylor
wrote:
Hi Jarmo,
On 7/1/2018 10:14 AM, jarmo wrote:
> My observations, what more guys making contacts, that smoother
Hi Jarmo,
On 7/1/2018 10:14 AM, jarmo wrote:
My observations, what more guys making contacts, that smoother
it goes. And also "hounds" are learning. We have to remember, that
this is really first dxpeditio with FT8.
But, suggest that next versions, no change to click other than
DX.
This
My observations, what more guys making contacts, that smoother
it goes. And also "hounds" are learning. We have to remember, that
this is really first dxpeditio with FT8.
But, suggest that next versions, no change to click other than
DX.
Secondly, disable DX-mode using in regular ft8 freqs.
Hi all,
Some here may not already know that not all the early FT8 QSOs made it
into the first upload from KH1/KH7Z to ClubLog. They have now caught up
a bit further.
Some statistics of currently uploaded QSOs:
ModeQSOs DXCCs
CQ 13,571 105
SSB 8,986 102
> take
>
>
>
> de JA5AEA
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>
> ------
> *From:* Joe Taylor
> *Sent:* Sunday, July 1, 2018 3:56:39 AM
> *To:* WSJT software development
> *Subject:* Re: [wsjt-devel]
ows 10
From: Joe Taylor
Sent: Sunday, July 1, 2018 3:56:39 AM
To: WSJT software development
Subject: Re: [wsjt-devel] Observation on Expedition Mode
On 6/30/2018 10:14 AM, Black Michael via wsjt-devel wrote:
> ... I noticed the the Baker team gave a lukewarm endorsement
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
in the log will be FT8.
To me, that’s pretty darn cool as I otherwise would not have a shot.
Jim S.
N2ADV
From: Glen Brown [mailto:210g...@gmail.com]
Sent: Saturday, June 30, 2018 6:49 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Observation on Expedition Mode
In my
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
-devel@lists.sourceforge.net
Cc: Black Michael
Subject: Re: [wsjt-devel] Observation on Expedition Mode
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
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,
reason.
Jim S.
N2ADV
From: Gary Kohtala - K7EK via wsjt-devel
[mailto:wsjt-devel@lists.sourceforge.net]
Sent: Saturday, June 30, 2018 2:26 PM
To: 'WSJT software development'; John Zantek; Black Michael
Cc: Gary Kohtala - K7EK
Subject: Re: [wsjt-devel] Observation on Expedition Mode
Msgs to work
them successfully.
From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Saturday, June 30, 2018 7:15 AM
To: 'WSJT software development'
Cc: Black Michael
Subject: Re: [wsjt-devel] Observation on Expedition Mode
I have some observations too
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
oftware development'
*Cc:* Black Michael
*Subject:* Re: [wsjt-devel] Observation on Expedition Mode
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 bu
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
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
@lists.sourceforge.net
Subject: Re: [wsjt-devel] Observation on Expedition Mode
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
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
@lists.sourceforge.net]
*Sent:* 30 June 2018 15:15
*To:* 'WSJT software development'
*Cc:* Black Michael
*Subject:* Re: [wsjt-devel] Observation on Expedition Mode
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
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
[mailto:wsjt-devel@lists.sourceforge.net]
Sent: Saturday, June 30, 2018 7:15 AM
To: 'WSJT software development'
Cc: Black Michael
Subject: Re: [wsjt-devel] Observation on Expedition Mode
I have some observations too.
#1 Tons of ops calling KH7Z when they can't see them. I assume this only
caus
d see a CQ, so I entered it manually and generated the Std Msgs to work
them successfully.
From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Saturday, June 30, 2018 7:15 AM
To: 'WSJT software development'
Cc: Black Michael
Subject: Re: [wsjt-devel] O
med tobe no QSOs.
Charlie
From: Black Michael via wsjt-devel[mailto:wsjt-devel@lists.sourceforge.net]
Sent: 30 June 2018 15:15
To: ' WSJT software development '
Cc: Black Michael
Subject: Re: [wsjt-devel]Observation on Expedition Mode
I have some observations too.
#1 Tons of
.
Charlie
_
From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: 30 June 2018 15:15
To: 'WSJT software development'
Cc: Black Michael
Subject: Re: [wsjt-devel] Observation on Expedition Mode
I have some observations too.
#1 Tons of ops calling KH7Z
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
82 matches
Mail list logo
