Mike --
Don't make the slider optional -- just remove it.
-- Joe
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Hi all,
Most of the necessary updates of the WSJT-X User Guide to cover features
in Version 1.8 are now in place. Use *Help -> Online User Guide* or
*F1* or click here:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.7.1-devel.html
Some screen shots still need to be
Enough, already, about the audio level slider!!
Those who read the manual knew what it was for.
It confused many others, and it was responsible for a large number of
emails to two reflectors and direct to me.
Its function was mildly useful, but redundant.
It will soon be history.
Hi Charlie,
On 6/29/2017 1:37 PM, G3WDG wrote:
Built and running - no on-air tests yet.
Noticed that the 15s period is insufficient to get the cw id in.
RR, we're aware of this. Will probably need to devote a full Tx period
to CW ID, for those who need it.
-- Joe, K1JT
Hi Wolfgang,
Was your QSO on 50.313? Will this be a good operating frequency for FT8
in IARU Region 1 ?
-- Joe, K1JT
On 6/29/2017 3:10 PM, Wolfgang wrote:
Hello all,
had my first QSO with CT1FBK a few minutes ago.
Thanks Miguel, CT1FBK, for the reply to my very first CQ
Next QSO
Hi Laurie,
On 6/29/2017 6:35 PM, Laurie, VK3AMA wrote:
The "~" mode character will be a problem. It is the character chosen by
JTDX for the T10 mode and would explain an earlier message that
indicated that a FT8 spot on HamSpots appeared as T10 (likely came from
JTAlert which spots "~"
t;s.j.fra...@icloud.com>
*To:* Black Michael <mdblac...@yahoo.com>; Joe Taylor
<wsjt-devel@lists.sourceforge.net>
*Sent:* Friday, June 30, 2017 8:28 AM
*Subject:* Re: [wsjt-devel] msk144sd.f90 problem?
Mike,
msk144sd is just a development routine - it is not used in WSJT-X.
Steve
> O
0638 | dtil...@captechconsulting.com
On Jun 30, 2017, at 10:45 AM, Joe Taylor <j...@princeton.edu> wrote:
Hi Steve,
Yes, 40 iterations for bp.
With norder=2 hardwired for everything I still get 574 good decodes. So
at least in jt9.exe, with no attempt to move nfqso around, using norder=3
prod
Hi George,
On 6/30/2017 12:38 PM, George J Molnar wrote:
The nut here seems to be with the use of the term “split.” It implies
two different frequencies are being used for the contact. This threw me,
and probably some others.
Yes, I understood what you took to be the meaning of "split".
The
Hi George,
Still feel like the way this is being implemented is counter-intuitive
for most operators. After your explanation, I get it. That said, I’ve
made 10,000 JT-mode QSOs and it never occurred to me when I saw this. I
think we might see a fair number of folks fall into the same
Hit F3 to see a list of keyboard shortcuts, and look at the entry for
CTRL+M.
On 6/30/2017 2:40 PM, Edfel Rivera wrote:
Hi:
I am not sure what I did but I am not able to access configuration.
Also, can not change band. I tried building new but no fix.
Previously used 1.7.1 with out any
ime, we're in something more like an "early testing" stage.
Yes, we can use some tests FROM PEOPLE WHO SEND US REPORTS. But we're
not yet ready to support and encourage widespread use. That will come,
soon enough!
-- Joe, K1JT
On 6/30/2017 4:29 PM, Dani EA4GPZ wrote:
El 30/06
We are well aware that displayed values of S/N are unreliable. This
will be fixed soon.
-- Joe, K1JT
On 6/30/2017 5:28 PM, Adrian Fabry wrote:
Hi all,
I saw also this problem.
For example, two signals, one very strong @ 806Hz -15 dB and one weak
@1254 Hz -17dB:
The wav file
Hi Edfel,
Thanks for your comments. We tend not to increment our version number
until we're ready (or nearly ready) to make an official release. This
will likely be very soon!
-- Joe, K1JT
On 6/30/2017 6:00 PM, Edfel Rivera wrote:
Hi:
Just an observation.
Hi all,
Far too many unwary users are being bitten by the "CTRL+M" bug. In
general, it seems like bad policy to hide screen controls and leave no
visible way to get them back.
In r7769 I added a checkbox labeled "Menus" on the main window, and one
labeled "Controls" on the Wide Graph.
Hi all,
Thanks for a busy ~20 hours of many people testing FT8. I now have
accumulated a directory with 527 *.wav files, each of which has at least
one visible FT8 signal. The files were recorded at K1JT at either
14.079 or 50.313 MHz.
Running the r7753 stand-alone slow-mode decoder
Hi Tamas,
Your files decode OK here in WSJT-X r7775 (running on Windows).
20m
130800 -7 0.6 1097 ~ EI4KF ES6DO KO27
20m
130815 -12 0.2 1098 ~ ES6DO EI4KF -13
20m
130830 -7 0.6
Hi Charlie,
What fraction of the transmission is needed for a successful decode
given ‘good’ S/N?
I’ve seen some “short” messages decode just now (using r7776).
The code rate is 1/2, so without AP decoding the bare minimum must be
about half a transmission. I've seen done good decodes
Hi Jay,
Thanks for sending the files. Alas, there's no way that second one is
going to decode -- its S/N is well below -20 dB.
-- Joe, K1JT
On 7/3/2017 10:33 AM, Jay Hainline wrote:
Worked EI3KD using the new mode FT8 on 6 meters this morning!
Attached are wav files from his last
Hi again Jay,
On 6/29/2017 4:02 PM, Jay Hainline wrote:
My message got bounced for being too large. So posting again with 2 wav
files instead of 3. Recorded from 50313. Please check the signal around
1050 hz. I was not able to decode.
The first of your two files, 170629_194730.wav, decodes
Hi Kari,
The 'worked before' feature is also not working with FT8.
I think this could be fixed by adding test for
FT8 on line 105 of "logbook/adif.cpp"
Thanks! I believe it's fixed in r.
-- Joe, K1JT
To: All WSJT-X users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT EXPERIMENTAL MODE FT8
Thanks to all alpha testers who have sent us helpful information on
their experiences with FT8. The mode is basically working well, but
we've determined that we can improve it
Hi all,
I'm compiling a list of important new features and other changes that
will be in WSJT-X v1.8.
1. New mode called FT8: QSOs 4 times faster than JT9, JT65
2. New mode for Frequency Calibration
3. Improved performance of decoders for JT65, QRA64, and MSK144
4. New utility programs:
Richard --
On 7/6/2017 3:48 PM, Richard Lamont wrote:
Is it a good idea to use AM broadcast transmitters as a frequency
standard when the regulatory tolerance (ITU and many countries) for such
transmitters is +/- 10 Hz? Is that good enough for the purpose?
73,
Richard G4DYA
As described here
Hi Al,
On 7/6/2017 3:59 PM, CX8AT VERA wrote:
Maybe I missed something when reading this group's mail, but something
that I don't like is to have 2 windows (main window and wide graph)
apart, is hard for me to keep both with the right size in a small wide
13" notebook, It is possible to
https://physics.princeton.edu/pulsar/k1jt/ft8_Protocol_Change.txt
On 7/6/2017 9:17 PM, David wrote:
Hi ...i have just used JTSDK to upgrade to r7800 compiled 100% but
when i started WSJT-X it came up with a message "FT8 tempory disabled"
went to the Mode tab and found FT8 greyed out used
Hi all,
If you knew you had to send an ID with a packet, could you not reduce the
amplitude of the whole data packet by a db or so and re-allocate that power to
the CW ID? It certainly doesn't have to be loud, much like repeaters do
id-under-voice. That way the FT8 signal taken by itself
Hi all,
I was interrupted late this afternoon just after committing r7654-76656,
and did not finish all the necessary additions. CMake of the full devel
branch will fail until tomorrow morning, when I will bring the
repository back into a self-consistent state.
For now, you can build from
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 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.
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
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
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
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
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
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 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
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
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 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
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
Hi Ed,
K0KC wrote:
> I was running WSJT-X 1.7.1 r7672 this afternoon and noticed that under
> the Rx Frequency heading the D before the T was missing and that the
> alignment was off. Obviously this is not a big deal, but I am sure that
> it could be easily fixed.
In what operating mode ???
I
Hi Igor,
Thanks for identifying and reporting this bug in gen9.f90.
-- 73, Joe, K1JT
On 5/19/2017 9:23 AM, Игорь Ч wrote:
> Hello Joe,
> .
> In gen9.f90 207th bit of the i1EncodedBits(207) / i1ScrambledBits(207)
> arrays is not initialized and may take any integer*1 non binary value
>
Hi Seb,
Thanks for sharing your ideas for a WSJT-X web site. Your draft
examples look very nice! I look forward to its further development.
In future, if you think there might be an advantage to closer
coordination with other parts of the WSJT-X development effort, let us know!
--
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
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 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
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 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
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
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
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 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,
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
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
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
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 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 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
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 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,
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
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
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/
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 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 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?
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
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
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 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
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
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
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
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
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
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
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
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
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 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
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
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
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
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
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
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
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 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:
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 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
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
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
701 - 800 of 1545 matches
Mail list logo
