Hi Jerry,
On 12/19/2017 4:22 PM, Jerry S wrote:
Thanks Joe.
I get a build error when I try to compile.
Will debug as time permits.
The development branch is not usable on the air. You must use v1.8.0
and be patient waiting for a possible v1.8.1.
-- Joe, K1JT
Hi Dan,
On 12/19/2017 12:44 PM, Dan Malcolm K4SHQ wrote:
I have obviously missed something. I still have JTSDK and it still
builds v1.7.1 r. But that is not for prime time code. How to I set
things to build v1.8 devel releases?
As has been stated here several times before, the
Hi Jerry,
On 12/19/2017 11:03 AM, Jerry S wrote:
How does one get an updated version 1.8 with the patch installed?
It would prevent the momentary transmit when I use the double click.
Jerry
W8DLD
There is no released version of WSJT-X that has the patch you mention.
You'll need to wait for
Mike --
This is not a desirable change. Clicking on decoded text windows is
often used (especially on VHF bands) to highlight some selected text to
copy it to the clipboard, perhaps to post of Ping Jockey or whatever.
This is always expected as the behavior of such text windows. That's
You must do this yourself. Links at bottom of message.
On 12/18/2017 4:44 AM, donato maniello via wsjt-devel wrote:
Unsubsxribe me
--
Check out the vibrant tech community on one of the world's most
engaging tech
Hi Garry,
Thanks for directing attention to this program flaw. Can you reproduce
this problem by starting WSJT-X v1.8.0 in MSK144 mode and opening a
suitable *.wav file? If so, please send me the .wav file and the exact
series of steps that causes the popup message.
-- Joe, K1JT
I am happy to announce that German translations of the WSJT-X User Guide
(Version 1.8) and associated documents have been done by Enrico
Schürrer, OE1EQW. Links to them can be found on the WSJT web site here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
The individual documents are
Mike: Please do NOT encourage discussion of the Dxpedition stuff, just
yet. It's still premature for that step.
-- Joe
On 11/23/2017 8:57 AM, Black Michael via wsjt-devel wrote:
Seeing as how the DXpedition foxhunt is being actively developed right
now you probably want to comment on
Hi Brian,
Thanks for your input. By all means, send us a context diff with your
code for connection to N1MM Logger, including additions to the Reporting
tab. It will be much appreciated! You can send it directly to me,
along with your comments on the White Paper.
-- Joe, K1JT
On
On 11/16/2017 6:27 PM, Gilbert Baron wrote:
What is the best timing software for W10? I did not realize the need for
1 sec accuracy when I started thinking about these modes.
W0MN EN34rb 44.08226 N 92.51265 W
Why not consult the WSJT-X User Guide for relevant advice? It's hard to
miss,
Hi all,
I write to share the good news that the WSJT Development Group has been
awarded the Yasme Excellence Award for 2017. A few details can be found
here:
http://www.yasme.org/yasme-excellence-awards/
GM Enrico,
On 11/4/2017 12:47 PM, Enrico Schürrer wrote:
Dear colleagues,
at the moment I'm working on the translation of the WSJT-X User Guide
into German language.
Please let me know what I will have to do to give this document to the
public.
73's
Enrico
OE1EQW
No special permissions
Hi John,
AC0ZG wrote> 2) For the wsjtx developers: It's tough to release binary
packages that
cover the wide range of linux releases. But you can greatly increase
the chance of things working by linking statically against smaller
libraries like libreadline. Of course, you could link
Rich, Jay, and all,
The gist of my message was that nobody should be surprised by the
behavior of WSJT-X when presented with nonstandard callsigns like 3XY4D
(or, for that matter, OX90ABC and other "special event" calls).
No doubt you're correct that 3XY has been used for over 18 years. The
Hi all,
Until further notice, WSJT-X will contain some experimental, potentially
unstable code. DO NOT USE revisions later than 8193 on the air!
For on-the-air operation, please use WSJT-X v1.8.0.
-- 73, Joe, K1JT
Hi Rich,
On 10/29/2017 1:19 PM, Rich - K1HTV wrote:
A new FT8 DXCC country popped up today, 3XY4D. When I double clicked on his CQ call, it did not populate the message boxes.
...
The behavior you described is no surprise to anyone who has read the
definition of what's treated as a standard
The WSJT Development Group is pleased to announce the full General
Availability release of WSJT-X Version 1.8.0.
Changes since "Release Candidate 3" (wsjtx-1.8.0-rc3) are very minor;
they are described in the Release Notes posted here:
Hi Neal,
I am sorry that you find the WSJT-X User Guide vague and unclear.
There is no description as to how many local station editions are
sufficient, or if we should delete
ALL frequencies that are difficult to receive locally. How many WWV
and local broadcast stations
are enough?
One
Hi Unni,
The error messages you posted are from PSTRotator, not from WSJT-X.
Apparently you need to tell the PSTRotator program the location of file
wsjtx_status.txt. Normally in Windows this will be the directory
%LOCALAPPDATA%\Temp\WSJT-X.
-- 73, Joe, K1JT
On 10/23/2017 11:32 AM,
Hi Chris,
On 10/17/2017 3:19 PM, Chris Getman N3PLM wrote:
I just downloaded Version 1.8.0 RC3 and found it missing the Lock Rx-Tx
feature.
In using FT8 from the beginning, I have only twice found a station
wanting to work splits.
So I really miss this feature.
Any chance of putting it
Hi Dave,
On 10/16/2017 7:08 PM, David Fisher wrote:
I’m proof reading the 1.8 RC 3 document. Here’s something I’ve noticed
before that might be helpful.
As I understand it (and I’m probably wrong), the “Settings, General, My
Grid” field accepts 6 character grid information such as CM97bq
Hi all,
This is my last post here for today, and it has little to do with
WSJT-related software development. But its topic has occupied much of
my time for the past ten days -- and it has made me feel as excited as a
youngster with a new scientific toy! A few have asked offline if I
would
Hi Eric, Jay, and all,
On 10/16/2017 8:27 AM, Eric NO3M wrote:
630M opened up to some US Amateurs this past weekend. FT8 may have
killed JT65 / JT9 for the most part on HF, but down on 630 JT9 is still
king. We need to dig deep for weak (5W EIRP) signals amidst harsh
noise, etc. I'd like
Hi all,
Some interesting statistics on downloads of wsjtx-1.8.0-rc2, derived
from the SourceForge web page
https://sourceforge.net/projects/wsjt/files/wsjtx-1.8.0-rc2/
Platform Downloads Pct
-
Windows11,369 91.6
Linux 6965.6
Macintosh 3562.9
The WSJT Development Group is pleased to announce a third candidate
release of WSJT-X Version 1.8.0. We believe this is the all-but-final
beta release; we expect very soon -- perhaps next week -- to make
Version 1.8.0 the full general availability (GA) release of WSJT-X.
Changes since
Hi Dan,
I also have a question. The FMT analysis program initially had an error
and referred to bad data. The online manual does say to edit the
fmt.all file and remove bad data. I did that and the analysis ran
without error. I made a judgement call as to what constitutes “bad
data”, in
Steve --
In the screen shot you posted, the line of text produced by the decoding
procedure reads:
UTC dB DT Freq
---
2051 -30 8.3 1275
I am puzzled as to how this line was generated. DT=8.3 seconds???
Seems too big; I am surprised this can ever happen. Why is there
Steve --
Another question: when this odd switch of Tx mode occurs, does the
transmitted audio signal actually change to JT9 mode? Or is it only the
Tx bandwidth indicator on the waterfall, to which your screen shot draws
attention?
-- Joe, K1JT
On 10/5/2017 9:28 PM,
Hi Steve,
When this happens again, please send me the .wav file for the sequence
ending at t=52 -- that is, the Rx sequence that seemed to trigger the Tx
mode switch from JT65 to JT9.
-- Joe, K1JT
On 10/5/2017 9:28 PM, st...@k5dog.com wrote:
WSJT-X v1.8.0-rc2 r8069 on Windows 10 64
Hi David,
Logging your QSO and having Tx Enable turned off sets the
auto-sequencing logic to "not in QSO". So double-clicking on "NX6D
KD0ZZ RRR" is interpreted to mean that you want to start a new QSO.
-- 73, Joe, K1JT
On 10/5/2017 5:55 PM, David Fisher wrote:
This time, with the
Hi Erik,
On 10/2/2017 10:42 AM, Erik EI4KF - wrote:
Since you were kind enough to write to me directly regarding the issue below,
may I ask you about some other aspects of WSJTx? I have previously posted about
these in the Development List but without reply.
It's best always to pose
Hi David,
The real issue is the TX Enable. I’d like to avoid having it set on the
double click so I can pick the right time in the other QSO to send my
message, on a split frequency.
Why not simply uncheck the box "Double-click on call sets Tx Enable", on
the *Settings -> General* page?
or CTRL-click on the waterfall.
A SHIFT does nothing, moves neither Tx nor Rx
B CTRL moves only the Rx
C ALT moves the Rx
D only unchecking Hold Tx will allow Tx to move
Erik EI4KF.
-----Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: 30
Hi all,
On 9/30/2017 2:48 PM, James Shaver wrote:
Ok, I may have figured it out: it looks like when using JTAlert to
respond to CQ's, if the CQ is in "CQ " format, both the TX
and RX move unless the "Hold TX Freq" box is checked as you'd expect.
When the CQ is structured as "CQ " the RX
Hi all,
Changes in program behavior can be confusing, so I apologize for some
recent instability in GUI operational behavior. Code revision r8146 is
yet another attempt to get it right -- or as near "right" as possible --
while supporting both simplex and split-frequency default operating
Hi Tim,
... I see that it says not to use “this feature” on the air in the r8120 commit
comments, but does that mean we should not use any release r8120 or above on
the air? Or is it something that we have to specifically do to use “RR73 NOW”
and “NIL NOW”, like enter those into Tx 4
After further testing in the field, the experimental changes introduced
in r8125 and later will now become permanent.
In r8144 I have added an option to enforce simplex operation (thus
moving both Tx and Rx frequency) when you double-click a decoded text
line. This option allows simpler
Forwarded Message
Subject: [wsjtgroup] Double-click on decoded message
Date: Fri, 29 Sep 2017 13:06:11 -0400
From: Joe Taylor j...@princeton.edu [wsjtgroup]
<wsjtgroup-nore...@yahoogroups.com>
Reply-To: Joe Taylor <j...@princeton.edu>
To: Lance Collister, W7GJ
Hi Lance,
You must have wondered for a long time why for you, double-clicking on
some decoded JT65 messages does not copy the callsign to DX Call, the
locator to Dx Grid, and populate the Tx message boxes. Or maybe you
figured it out by now.
Anyway, I just happened upon the reason and
On 9/29/2017 10:39 AM, George J Molnar wrote:
One point about using control-clicks that hasn’t been raised, but might affect
usability is the growing number of tablet and other touch screens in use.
Double clicking for setting both RX/TX, unless TX Lock is on, is the simplest,
most natural
Hi all,
If you are building WSJT-X from code in the development branch and
experimenting with it on the air, please pay attention to the commit
message for r8125 and report your findings here.
For full and open disclosure I'll copy the commit message here:
Neil --
The trailing indicators "? a2" should always tell you to view the decode
with healthy skepticism.
Best to heed the commit message with r8120:
" First tests of "RR73 NOW ..." and "NIL NOW ..." (i3bit=1, 2) messages
in FT8. DO NOT USE THIS FEATURE ON THE AIR!"
Please send me your
Hi Ed, Charlie, Neil, and all,
On 9/25/2017 2:34 PM, Neil Zampella wrote:
I just build r8120 .. and that also occurs here.
The double click on a decode does NOT switch both the Tx & Rx
frequencies. There is nothing listed in the commit history that shows
this being changed, I was using
KA9CFD
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: September 22, 2017 17:50
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] NA VHF Contest Mode
Hi Jay, Larry, George, and all,
Revision r8105 is another a
Hi Jay, Larry, George, and all,
Revision r8105 is another attempt at eliminating all potential causes of
confusion when one party has checked NA VHF Contest Mode and the other
has not.
Please find someone else with whom you can test this feature and report
you results here -- if possible,
PS: The tests need to be made on a VHF band, 50+ MHz.
On 9/22/2017 1:49 PM, Joe Taylor wrote:
Hi Jay, Larry, George, and all,
Revision r8105 is another attempt at eliminating all potential causes of
confusion when one party has checked NA VHF Contest Mode and the other
has not.
Please find
Hi Steve,
On 9/22/2017 8:12 AM, Steven Franke wrote:
Hi Joe,
Recall that MSK144 is configured such that fix_contest_msg is *always* called,
independent of whether or not the contest box is checked. Won’t this prevent
the contest-mode prompt from being triggered in that mode?
Yes, it seems
prompt and the auto sequence did
not advance beyond sending TX1.
73 Jay KA9CFD
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: September 20, 2017 19:48
To: WSJT Software Development <wsjt-devel@lists.sourceforge.net>
Subject: [wsjt-devel] NA VHF Contest Mode
of
contest mode?
-- Joe
On Sep 21, 2017, at 12:42 PM, Joe Taylor <j...@princeton.edu> wrote:
Hi George,
On 9/21/2017 3:31 PM, George J Molnar wrote:
Quick feedback on the repositioned contest mode checkbox. Bravo! Good idea.
Before GA release, it might be helpful to clean up the
Hi George,
On 9/21/2017 3:31 PM, George J Molnar wrote:
Quick feedback on the repositioned contest mode checkbox. Bravo! Good idea.
Before GA release, it might be helpful to clean up the labels and alignment, so
everything flows smoothly. ”Sh” could be written out, and maybe NA VHF Contest
Hi Jay,
On 9/20/2017 5:08 PM, Jay Hainline wrote:
Joe and all. Curious because I am not a big contester. My understanding is the
reason for the extra coding is for producing the message sent for TX3 with both
calls plus R Grid. If it’s a problem with extra characters involved, why can't
you
Hi Dan,
On 9/21/2017 11:54 AM, Dan Malcolm wrote:
Joe, Michael,
I don't disagree. I do have a problem being the cognizant human being at
times, and yes it is my responsibility. I just didn't realize how things
worked until now. The online guide says nothing about this behavior however
(yes I
Dan --
On 9/21/2017 11:21 AM, Dan Malcolm wrote:
Yes I did log it twice because the first attempt failed. But since the QSO is
reflected in the log entry, the times should still be correct.
WSJT-X does not attempt to replace the cognizant human being using it.
All logging information is
Hi all,
As an experiment, code revision r8101 in the WSJT-X development branch
includes several changes to the way *NA VHF Contest Mode* is
implemented. The goal is to obviate any cause for confusion (e.g.,
implausible grid squares being diaplayed) when one station uses Contest
Mode and the
Hi Anders,
Yes, please!
However, very soon I must leave for the airport. I will be in the UK
until Sept 17. I will be very happy to post your Swedish translation on
the WSJT web site when I return home.
-- Joe, K1JT
On 9/2/2017 2:08 PM, Anders Rhodin wrote:
Hi everyone,
I have
Nor is it supposed to do so. As discussed here many times before, there
are too many variations in allocations, world-wide. You can set any
desired frequency, yourself.
On 9/2/2017 10:48 AM, Philip Finkle wrote:
Does not set up the 60M band FT8 and JT65 QRG of 5.357
Phil K6EID
On 9/2/2017 10:52 AM, Scott Bidstrup wrote:
I tried that, and only after several retries, including re-starting the
software twice, did that finally work - might still be a problem there
that will need looking into.
Or maybe you need to remember to click OK to dismiss the Settings page.
Please read the RC2 announcement again. Carefully.
On 9/2/2017 10:37 AM, Scott Bidstrup wrote:
Gentlemen,
I have downloaded and installed the RC2 release software, and am
delighted to report that, for the most part, it is working.
One problem I have noted, though, is that the drop-down
The WSJT Development Group is pleased to announce a second candidate
release of WSJT-X Version 1.8.0. Once again this is a beta release.
Most changes since the "RC1" release candidate are related to the FT8
mode, and most new features have already been tested in the field by
several hundred
RR, good idea! -- Joe, K1JT
On 8/31/2017 7:31 PM, Jaroslav Skarvada wrote:
Hi Joe,
thanks for info. I have WSJT-X packaging on my todo list, but I didn't know
that it completely superseded WSPR-X. But no problem, I will probaly close
the WSPR-X inclusion request and will open new one for
Hi Jaroslav,
Thanks for your email. I wish I could have saved you the effort already
put into this task, because I do not recommend packaging WSPR-X for any
platform or distribution. WSPR-X is obsolete, and no longer supported.
Its functions are limited, and anyway now much better served by
file it decoded but still could double click and insert
call.
I will be leaving home no radio for few days but should have email
access but not my radio computer or such.
Thanks Morris WA4MIT
On Wednesday, August 30, 2017, 7:23:28 PM CDT, Joe Taylor
<j...@princeton.edu> wrote:
On 8/30/
On 8/30/2017 6:14 PM, Morris Wideman via wsjt-devel wrote:
I was not able to make WSJT-X development release 8049 pick up this
callsign "K4XP" a legitimate US callsign and transfer it to DX Call by
double click. I was trying to pick up a new state for FT8 on 15M after
he had worked another
On 8/28/2017 7:53 PM, Rich - K1HTV wrote:
Using R8035, on FT8, with the "Show DXCC entity and worked before
status" box CHECKED, certain free form CQs messages result in the wrong
country name being displayed on the right side of the line in the "Band
Activity" column.
Examples:
CQ USA
On 8/28/2017 7:35 PM, Rich - K1HTV wrote:
Using R3035, in FT8, with the "Allow Tx frequency changes while transmitting"
box UNCHECKED, I am still able to change the TX frequency by Shift-clicking on a
different frequency on the waterfall.
Yes, you can move the Tx frequency marker on the
Thanks to all for your informative comments on frequencies and operating
procedures for FT8 under extreme pileup conditions.
We need more such input. Preferably some of it should come from
operators who actually plan to use FT8 in a major DXpedition. The most
useful input will surely come
PS - I'll have more to say about possible DXpedition operating
procedures, but probably not until tomorrow.
-- Joe, K1JT
--
Check out the vibrant tech community on one of the world's most
engaging tech sites,
Hi Rich, Ned, Alex, and all,
On 8/20/2017 2:15 PM, Alex, VE3NEA wrote:
Hi Ned,
Your picture of the future FT8 pileups of the top-ten DXpeditions is
very realistic but very scary. ...
... A 400 W linear amplifier will easily transmit 10 x 40W
signals if it is linear enough.
Surely this
Richard --
There is no 1.8.0-rc2 release yet, as you must know. Consequently there
is no WSJT-X User Guide with "1.8.0-rc2" in its file name.
If you are building for yourself and have not turned off the option that
builds docs, you should be creating the Local User Guide.
Anyway, the link
Hi Rich and all,
On 8/19/2017 2:15 PM, Rich - K1HTV wrote:
DXpeditions - FT8, Split or not to split
Thanks for sharing your ideas on this topic.
We (the WSJT developers, that is) will be happy to offer advice, when/if
asked. But I don't consider it our task to tell the DXpedition crew
Hi Alex, Iztok, and all,
Thanks for your comments and suggestions for optimizing FT8 QSO rates in
pileup conditions.
In my message posted yesterday I kept things simple and did not go into
any detail about what to do when things do not go exactly "by the book".
Of course you are right to
Hi John and all,
On 8/8/2017 12:19 PM, John Zantek KE7B wrote:
This past weekend, I attended the Pacific NW DX Convention, where the buzz
of JT/FT was tangible. ... The
biggest news for me was the talk about the upcoming DXpedition to Mellish
Reef (VK9MA) and the stated intention to try JT65
Hi Rich,
K1HTV wrote:
I believe that my suggestion of changing the present FT8 screen's "Tx
even/1st" description to "1st & 3rd 15 second sequence" or an
abbreviated version of "1st & 3rd 15 sec seq" will make the meaning of
the check box very clear as to eliminate the present ambiguity.
On 8/4/2017 2:46 PM, Bill Turner via wsjt-devel wrote:
Would it be useful to add the revision version to the top line on the
main screen? something like:
WSJT-X v1.7.1-devel-r7997 by K1JT
It's on the *Help -> About" screen (Ctrl+F1).
-- Joe, K1JT
Hi Alex,
On 8/4/2017 11:02 AM, Alexandre Moleiro via wsjt-devel wrote:
- Is the list of keyboard shortcuts on section 10.1.9 updated ?
As far as I am aware, yes. Did you find something missing or incorrect?
-- Joe, K1JT
Hi Jay,
Thanks for the feedback.
On 8/2/2017 5:01 PM, Jay Hainline KA9CFD wrote:
2 things I noticed about the User Guide.
1. In Section 16.2 Slow Modes, FT8 is listed. Should it be listed in the
Fast modes instead?
The X Fast modes in WSJT-X send their messages repeatedly in a single Tx
Hi all,
In preparation for a soon-to-come second candidate release of WSJT-X
Version 1.8, I committed a large number of updates to the WSJT-X User
Guide today.
The new user guide is posted here:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.7.1-devel.html
If you are
On 8/2/2017 10:58 AM, WB9BSD wrote:
Where can I go to learn more about this mode?
Is it very wide or what is the reason why it isn't useable below 50 Mhz?
Joe WB9SBD
1. Why not go to the WSJT-X User Guide? You might start at these two
places:
ave uncovered a bug, it's best to provide a
series of steps that will reproduce the bug.
-- 73, Joe, K1JT
On 7/28/2017 1:33 PM, Joe Taylor wrote:
Hi all Beta Testers,
In code revision r7969 the WSJT-X development branch supports "Contest
Mode" in FT8 as well as MSK144. This mod
elaborate on why you think it does not.
As always, if you think you have uncovered a bug, it's best to provide a
series of steps that will reproduce the bug.
-- 73, Joe, K1JT
On 7/28/2017 1:33 PM, Joe Taylor wrote:
Hi all Beta Testers,
In code revision r7969 the WSJT-X development
Thanks Bob! -- Joe, K1JT
On 7/31/2017 5:53 AM, Bob Thornton via wsjt-devel wrote:
Using 1.7.1-Devel r7970
Help/Keyboard Shortcuts. F4 says "Clear DX Call, DX Grid, TX messages 1-5"
In practice Tx 5 is not being cleared. I suspect there is good reason for that,
if so the help needs update.
Bill --
Thanks for catching and fixing my broken code with your commit r7971!
-- Joe
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
On 7/31/2017 9:12 AM, Black Michael via wsjt-devel wrote:
I think anytime users have questions about why WSJT-X doesn't do what it
says it's going to do that it's worthy of a comment and potentially a fix.
The whole point is that WSJT-X *does* do what it says it will do.
WSJT-X operates the
On 7/31/2017 12:28 AM, Black Michael via wsjt-devel wrote:
Couple of people on the HamApps mailing list mentioned their callsigns
don't workand I confirmed they are correct.
OT17L
VB7150
Why would you be surprised or consider this worthy of comment?
Anyone familiar with WSJT-X should
Hi Richard,
On 7/30/2017 7:07 AM, Richard Lamont wrote:
Looking at this a little further, in the 15 seconds before, on the same
Rx freq, AD5FW called CQ. So maybe the true message was "AD5FW VE3SMB
FN04" not "G4DYA VE3SMB FN04".
In the compressed 28-bit callsign field, how many bits are the
Hi Charlie,
Does Generate Std Msgs set up these messages or does it all happen when
someone calls you? Haven't used contest mode in MSK144 before.
To be honest, at the moment I don't remember for sure. I think so, for
MSK144. And I'm not sure that I have connected things so that it will
16:18:29 -0400
Joe Taylor <j...@princeton.edu> wrote:
On 7/28/2017 4:03 PM, Richard Bown wrote:
It could be a considerable amount Joe, Some countries in region 1 are small.
But what I wanted to know is what that amount actually is, in practice,
in a typical VHF+ Region 1 contest log cont
On 7/28/2017 4:36 PM, Richard Bown wrote:
you are missing an important point Joe
As FT8 is a quick exchange mode it will encourage more use, so
I assure you that no important point has been missed. I simply want to
have an initial reference point.
-- Joe, K1JT
On 7/28/2017 4:03 PM, Richard Bown wrote:
It could be a considerable amount Joe, Some countries in region 1 are small.
But what I wanted to know is what that amount actually is, in practice,
in a typical VHF+ Region 1 contest log containing some hundreds of QSOs.
-- Joe, K1JT
See
below.
-- Joe, K1JT
On 28 July 2017 at 20:17, Joe Taylor <j...@princeton.edu
<mailto:j...@princeton.edu>> wrote:
One additional question I should have asked.
If you think FT8 might get appreciable use in Region 1 VHF+
contests, would there be significant need
One additional question I should have asked.
If you think FT8 might get appreciable use in Region 1 VHF+ contests,
would there be significant need for handling compound callsigns such as
ZA/PA9XYZ, etc.?
-- Joe, K1JT
On 7/28/2017 2:49 PM, Joe Taylor wrote:
Hi Palle (and other VHF
Hi Palle (and other VHF+ contest enthusiasts in IARU Regioin 1),
Thanks for the suggestions you posted to wsjt-devel concerning VHF+
contest exchanges in EU.
I have been sketching out some possible enhanced 75-bit message
structures for FT8 mode aimed (among other things) at supporting your
Hi all Beta Testers,
In code revision r7969 the WSJT-X development branch supports "Contest
Mode" in FT8 as well as MSK144. This mode is designed for NA VHF+
contests in which the required exchange is a 4-character grid locator.
Contest Mode is enabled by checking the box labeled "FT8 and
Hi Alex,
We have already done most of what you suggest. Note, however, that
documenting the latest changes and additions in the WSJT-X User Guide is
still to be done.
-- Joe, K1JT
On 7/26/2017 12:54 PM, Alex, VE3NEA wrote:
The JT65 Communications Protocol document
On 7/26/2017 12:01 PM, W9MDB Black Michael via wsjt-devel wrote:
What is "AP" decoding?
Decoding a message with aid of "a priori" information gathered
cumulatively during the progress of a QSO. It has been in WSJT-X for
about a year, in mode QRA64. It's now available in FT8.
--
Hi Richard,
On 7/25/2017 4:58 PM, Richard Lamont G4DYA wrote:
On 25/07/17 00:17, Joe Taylor wrote:
Ubuntu MATE 16.04 amd64
1.7.1-devel r7939
Auto seq and call 1st enabled
Tried it and it looks as though FT8 now has a two-pass decoder, which is
nice.
Since you're providing feedback
software version for each one; it will have been a recent dev
build (I suspect v1.8.0-rc2 r7924), but it's somewhat irrelevant because
this particular problem has been quite persistent through versions.
Regards, Mark
On 24/07/2017 22:27, Joe Taylor wrote:
Hi Mark,
On 7/24/2017 5:12 PM, Mark Turner
Hi Richard,
Richard G4DYA wrote:
Ubuntu MATE 16.04 amd64
1.7.1-devel r7939
Auto seq and call 1st enabled
Tried it and it looks as though FT8 now has a two-pass decoder, which is
nice.
Since you're providing feedback on development code, you should not need
to guess or make inferences
Hi Mark,
On 7/24/2017 5:12 PM, Mark Turner EI3KD via wsjt-devel wrote:
I'm currently trying to capture some examples where the WSJT-X waterfall
appears to become corrupt with multiple images of signals, along with
multiple decodes - I see this fairly frequently when using FT8, and have
also
Hi Neil,
but doesn't that mean you have to redo the logic used by the double
click to change the current function from seeing RR73 as a grid, ...
The change in logic is minimal.
I'm also guessing that you would have to make this band specific so its
not used with MS/EME/etc modes which
701 - 800 of 1516 matches
Mail list logo
