George --
On 9/26/2018 11:31 AM, WB5JJJ wrote:
I'm using RC1 again now, but this also happened when I was running RC2
since it was released.
Why -rc1 ??? The whole point of beta releases is to test and exercise
new code. Please use the latest release when helping us in this way.
Some
Ken --
On 9/26/2018 12:56 PM, Ken Miller wrote:
Using Win 10, 2.2.0-rc2 I5 quad core processor. It looks as EA1FA may be
having trouble decoding. The call is showing up with nothing but the
call sign in the decode window. I noticed this same thing yesterday on
rc-1 and thought it was the
Hi Mark,
Thanks for your interesting report on using FT8 at 222 MHz.
Also important: we're waiting to hear from you about the "/R" (rover)
capabilities in WSJT-X 2.0. This facility is there because you (and
others) asked for it. We would appreciate your feedback.
-- 73, Joe, K1JT
Thanks to everyone who commented on the color-highlighting of decoded
messages in WSJT-X 2.0-rc1 and -rc2. We appreciate hearing all the
sentiments expressed: they ranged from "keep it simple" and "better as
it was" to "more options are needed".
As most subscribers here know, in general we
Hi Uwe,
No need to send any further details -- we appreciate your bug report and
will fix the problem! This is why we do beta testing...
-- 73, Joe, K1JT
On 9/26/2018 9:19 AM, DG2YCB, Uwe wrote:
For confirmation: Just created an wsjt_log.adi file from my standard
logbook where all
s the file.
-- Joe, K1JT
On 9/26/2018 9:12 AM, jarmo wrote:
Wed, 26 Sep 2018 08:48:52 -0400
Joe Taylor kirjoitti:
Hi Jarmo,
Thanks for your report.
You had followed the instruction for beta testers and enabled "Save
all", right? Please send us the .wav file that was recorded just
Hi David,
Thanks for your early report on testing RTTY contest mode.
As you figured out, each of the issues you identified is a result of
invalid user input. We haven't yet included validation tests on some of
the new entry fields, but obviously these are needed. At present, it's
important
Hi Jarmo,
Thanks for your report.
You had followed the instruction for beta testers and enabled "Save
all", right? Please send us the .wav file that was recorded just before
you received this error message.
-- 73, Joe, K1JT
On 9/26/2018 5:57 AM, jarmo wrote:
Fedora 28 and
.
-- Joe, K1JT
On 9/25/2018 3:31 PM, Joe Taylor wrote:
Hi Jay,
Thanks -- that's definitely a program defect, and we'll fix it.
In the meantime, when using MSK144 you'll need to enter DX Call manually
and then type CTRL+L or click "Generate Std Msgs".
-- 73, Joe, K1J
Only seems to be TX1 in msk144 where double clicking does not work.
This is on Windows 10 64 bit.
73 Jay KA9CFD
-Original Message-----
From: Joe Taylor
Sent: September 25, 2018 16:22
To: WSJT software development
Subject: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc2
A second candidate release
Hi Don,
On 9/25/2018 10:03 AM, Don AA5AU wrote:
I have some questions in trying to set up for tomorrow night's FT8
Roundup test.
1. Will the QSO get logged automatically to the Cabrillo file or will I
have to manually log it? Typically is use JTAlert to log into DXKeeper
but I don't think I
A one-hour "practice contest" will be held tomorrow (Wednesday evening,
NA time) using the FT8 mode and the ARRL RTTY Roundup rules.
Date and time: Thursday, 27 September 0200-0259 UTC
Dial frequencies 7.078 and 14.078, everyone works everyone.
To participate you must use WSJT-X 2.0, either
A second candidate release of WSJT-X 2.0, is now available for download
and use by beta testers. Changes in WSJT-X 2.0.0-rc2 relative to -rc1
include the following:
- Corrected a flaw that encoded a message's first callsign as
hexadecimal telemetry data if the call consisted only of
Paul --
On 9/22/2018 3:32 PM, w3...@verizon.net wrote:
Just installed 2.0 RC1 yesterday, and so far so good with a couple of
exceptions,
I was under the impression that the false decodes would be
"significantly less than
previous versions", not the case here, if anything the rate is higher
Hi Jim,
On 9/22/2018 1:42 AM, DeYoung James N8OQ via wsjt-devel wrote:
1) The transmitter always goes off after a QSO. Under
"settings-general" the box is unchecked.
This behavior is by design, and has always been true for FT8. It is to
prevent WSJT-X from making robotic QSOs.
2) There
On 9/21/2018 2:46 PM, Attila Kocis wrote:
Hi,
this is DL1NUX OP Attila from Germany.
We have been QRV yesterday (sep. 20) with the special callsign DF1000ZEIL and made
several QSOs in 77bit mode. We discovered, that the wsjtx.adi logfile doesn't contain the
rst-sent information. This field
A one-hour "practice contest" will be held next week using the FT8 mode
and the ARRL RTTY Roundup rules.
Thursday, 27 September 0200-0259 UTC (Wednesday evening, NA time)
Dial frequencies 7.078 and 14.078, everyone works everyone.
To participate you must use WSJT-X 2.0. The Windows
On 9/21/2018 10:32 AM, oe9...@ft8.at wrote:
funny thing is, my own grid is saved in the adi-logfile in full 6 digits.
Nothing funny about that: the program simply saves whatever locator
information you entered on the Settings | General tab.
Stations showing up that I have already worked
Hi Jim,
Thanks for the report.
On 9/21/2018 9:38 AM, Jim Nuytens wrote:
My first attempt at a contact with a non-standard call resulted in the
program jumping back to Tx1, instead of Tx5. Below is the sequence:
132530 9 0.1 1343 ~ CQ OE100KFV
132545 Tx 1700 ~ KJ3N
132600 8
On 9/21/2018 10:16 AM, oe9...@ft8.at wrote:
Hello Joe,
" In general the gridsquare will not be saved in a QSO with a nonstandard
callsign, because grids are not exchanged in such QSOs."
Is that a hard restriction or could the gridsquare in a nonstandard callsign
be implemented?
The
On 9/21/2018 9:12 AM, oe9...@ft8.at wrote:
Seutup:
Software: v2.0.0-rc1 81d6f6
Own call = OE100KFV
77bit tx and rx enabled
Observations
Own grid is not shown in RX Frequency window during CQ-Call
Grid of other station not shown in QSO-entry mask
SV8QG FT8 +11
20180921 130215 20180921
On 9/21/2018 9:12 AM, "Jörg Hochheimer, DL6ZBN" wrote:
Hi all,
I was remotely operating the station PC and trying some QSOs on 14.078
with both 77 bit checkboxes checked. I successfully managed to finish
some QSOs until an EA station called me. There was visually nothing
unusual about it, but
uot; would clear it up for
people.
Mike
On Thursday, September 20, 2018, 4:10:27 PM CDT, Joe Taylor
wrote:
As stated in the code and in the "Quick-Start Guide to WSJT-X 2.0",
the logic currently highlights messages transmitted by stations that
have *NOT* uploaded a log to L
As stated in the code and in the "Quick-Start Guide to WSJT-X 2.0",
the logic currently highlights messages transmitted by stations that
have *NOT* uploaded a log to LoTW in the past year.
Of course, the test could be reversed. I did it this way because (in
the short test that I ran) it
Hi Don,
On 9/19/2018 4:03 PM, Don AA5AU wrote:
Ed, W0YK, and I are thinking of changing our Ten-Meter RTTY Contest,
which normally takes place the first weekend in December, to an all-band
FT8 contest.
If you think it might be done before then, we can certainly wait. Our
thinking is that
Hi Al,
See my message posted here yesterday:
###
1. If a message's first callsign contains only characters 0-9 and A-F it
will be interpreted as a hexadecimal number. The message will be
transmitted and decoded as if the
Hi Richard,
Thanks for your report. See my message posted here earlier today (at
11:37, according to my email client):
#
Many thanks to all the MSK144 gang who helped to identify a bug in
WSJT-X 2.0.
I believe the bug
RRL-VHF-JUN
CALLSIGN: K1JT
CATEGORY-ASSISTED: NON-ASSISTED
CATEGORY-MODE: MIXED
CATEGORY-OPERATOR: SINGLE-OP
CATEGORY-POWER: HIGH
CATEGORY-STATION: FIXED
CATEGORY-TRANSMITTER: ONE
CLAIMED-SCORE: 5640
OPERATORS: K1JT
CLUB: Mt Airy VHF Radio Club
NAME: Joe Taylor
EMAIL: k...@arrl.net
ADDRESS: Joe Taylo
Hi Dezider,
On 9/19/2018 3:03 PM, Dezider OM5NA wrote:
I had an opportunity to test the new -rc1 release of the WSJT-X v 2 with
a non-standard callsign OM100CSR.
Unfortunately I find out, that the SENT report and a gridsquare of the
counterpart station is not stored to the ADIF or WSJTX log
Hi Wolfgang,
On 9/19/2018 4:37 AM, Wolfgang wrote:
Tried to reply to a CQ of EI100MCV
In TX1 to TX3 his call sign was in brackets
but TX4 has: EI100MCV RR73
and TX5 is: EI100MCV 73
so, is my call sign sent in hash code at the end of a QSO?
73 de Wolfgang
OE1MWW
Yes, the behavior
Many thanks to all the MSK144 gang who helped to identify a bug in
WSJT-X 2.0.
I believe the bug is now fixed in our development code. We will post a
-rc2 candidate release very soon, probably next week. In the meantime,
it's best to use v1.9.1 for MSK144 QSOs.
BTW: this was a rather
Hi Steve,
This bug seems to have been caused by unitialized values of i3, n3
before calling pack77() in subroutine genmsk_128_90.
I believe the bug is fixed in commit 618fc05a.
-- Joe
___
wsjt-devel mailing list
Jari --
See my message posted here yesterday:
1. If a message's first callsign contains only characters 0-9 and A-F it will be interpreted as a hexadecimal number. The message will be transmitted and decoded as if the first callsign were telemetry data; the remaining parts are lost.
Hi all,
If your first language is Spanish or German, I want to call your
attention to translations of documentation for WSJT-X 2.0 prepared by
EA4BAS and and OE1EQW, now posted on the WSJT web site here:
https://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Thanks to Miguel and Enrico!
Hi Jim,
On 9/18/2018 2:59 PM, James Shaver wrote:
Talk about timing - I was just sending a note re: number one in your
note, Joe. I assume my attached screen shot is an example of this behavior?
Just want to make sure :)
You can be sure.
-- Joe, K1JT
Hi all,
Many of us have made many QSOs using the new 77-bit messages on 7.078
and 14.078 MHz. Overall the results have been good -- but not
surprisingly, bugs are being identified. Several are important enough
to warrant a second candidate release well before the originally
suggested
On 9/18/2018 2:02 AM, Claude Frantz wrote:
What is the right way to switch to 2.0-rc1 when using the source code
from the git repo ?
A source code tarball for WSJT-X 2.0-rc1 is posted on the WSJT web site:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
-- Joe, K1JT
Dan --
On 9/16/2018 7:21 PM, Dan P KW2T wrote:
Joe,
Thanks for getting back to me, and it's really cool what you did to ham
radio with this mode. Also, you and I have worked on 6M FT8, I'm up by
Boston in FN42.
I'm aware of your utility for doing encoding, but what I want is a full
WSJT-X 2.0 will be a major program release with many new features.
The first candidate release, WSJT-X 2.0-rc1, is now available for
download and use by beta testers. This candidate release is your first
chance to test the new features and provide feedback to the WSJT
Development Group.
Dan --
On 9/15/2018 9:49 PM, Dan P wrote:
Is there a way to get the tone data (1 of 8) out of the TX side of WSJT
FT8?
It's always best to consult the WSJT-X User Guide first. Section 19,
"Utility Programs", can be found here:
On 9/13/2018 9:12 AM, Rik Strobbe wrote:
With the right filename format it works like a charm.
Thank you Joe.
Just out of curiosity: what is the meaning of first value after
?
For some modes, and at some time in the past, the first number was the
number of signals for which a tentatively
On 9/12/2018 10:55 AM, Rik Strobbe wrote:
I already did, but I am not sure I understand the function of all arguments
correctly.
The program doesn't like the name you gave your file, "test.wav".
Rename it to something like a real WSPR .wav file, say 180912_0001.wav.
Here's example
Type "jt9 -h" (or simply "jt9" with no arguments) to display a help message.
On 9/12/2018 10:15 AM, Rik Strobbe wrote:
Dear all,
if I understand it correct JT9.EXE reads and decodes a WAV file.
As a first test I just tried (Windows 8 in DOS command mode): JT9 test.wav
But this returns an
Hi all,
No software in the WSJT family has ever depended on having an internet
"co-channel". No software in the WSJT family will ever do so.
I cannot imagine why anyone might have thought otherwise. I cannot
imagine why anyone might have thought the wsjt-devel email reflector
would be a
Hi Rik,
We are well aware that propagation-induced signal distortions at LF and
MF are very different (and generally much smaller) than at HF. The
extremely narrow bandwidths used by discontinued sub-modes JT9-2, JT9-5,
JT9-10, and JT9-30 took advantage of these differences and provided
Hi Jim --
On 9/1/2018 5:31 PM, Jim Brown wrote:
On 9/1/2018 11:26 AM, Joe Taylor wrote:
It's worth mentioning that for more than a decade MAP65, a sister
program of WSJT, WSPR, and WSJT-X, has provided a powerful and
uniquely effective form of diversity reception: polarization
diversity
Hi all,
On 9/1/2018 1:58 PM, Jim Brown wrote:
On 9/1/2018 3:14 AM, Iztok Saje wrote:
Instead of overcomplicating protocols, diversity reception shall be
considered.
Diversity reception has been around for nearly a century, and depends on
the very complex computing engine located between the
Hi Igor,
Earlier this month you made suggestions for a possible new protocol for
minimal weak-signal QSOs. I have been away on vacation since that time,
so have not had a chance to respond.
Of course there are many possible ways to make design trade-offs
involving message size, duration of
Hi Sandro,
On 8/24/2018 6:05 AM, Alessandro Gorobey IW3RAB via wsjt-devel wrote:
I noticed that in mainwindow.h (current git HEAD)
#include "commons.h"
is in line 26 and line 36.
There is specific reason or is a typo?
Thanks for catching this anomaly. The second #include is clearly
A number of people have asked for more details about capabilities
planned for WSJT-X Version 2.0. I have posted on the WSJT web site a
white paper that outlines the new features and a (necessarily tentative)
release schedule. Go here to read it:
Hi all,
On 7/24/2018 5:30 PM, Lance Collister, W7GJ wrote:> Thanks for sharing
this very exciting and welcome news!
I'm not sure why you sent this to a private collection of addressees,
rather than to a list where my original message was posted. I'll
respond here, on wsjt-devel, so that more
Hi Mike and all,
On 7/23/2018 7:37 PM, W0MU Mike Fatchett wrote:
First of all I want to thank everyone for this great advancement in the
hobby!
... (however, ...)
The CQ WW VHF was my first exposure to contest mode and it was a very
frustrating 27 hours.
Thanks for all the messages about
Your message arrived safely at wsjt-devel.
On 7/11/2018 5:15 PM, Frank Kirschner wrote:
How do I get support on WSJT-X? I joined the Yahoo group and the
SourceForge group, and got confirmation emails, but my posts all bounce.
What am I doing wrong?
On 7/11/2018 4:59 PM, Frank Kirschner wrote:
How do I get support on WSJT-X?
We do our best to provide good support. There are nearly 20,000 users
of WSJT-X, and only a few of us. So you need to do your part, too.
1. The first place to go for help is the WSJT-X User Guide:
One of the changes associated with moving source code for WSJT and
related programs from SVN to Git is a change in policy regarding
development code and the frequency of "commits" to the public repository.
Code development now takes place in limited-access git repositories.
New code is made
Mike and all,
On 7/10/2018 8:43 AM, Black Michael via wsjt-devel wrote:
One other idea that is more git-centric...how about we use date + 6
digit for the About revision? This would also help solve those who
think RCn is more current than the general release.
git log --date-format=:%Y%m%d
Hi all,
A French translation of the FT8 DXpedition Mode User Guide has been
added to the WSJT-X web page:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Many thanks to F8RZ!
A Spanish translation should be available soon, by EA4TV.
-- 73, Joe, K1JT
On 7/5/2018 8:59 AM, Joe
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
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
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
The FT8 DXpedition Mode User Guide is now available on the WSJT web site
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
in English, German, Polish, Norwegian, Finnish, Japanese, and Portuguese.
Many thanks to OE1EQW, SP9TTG, LA6VQ, OH1KH, JA7UDE, and CT1EKD for the
translations!
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
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
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
Hi David and all,
You should know that CW ID cannot be used with any FT8 transmission.
The blank interval (only ~2 seconds) at the end of an FT8 transmission
is much too short for a callsign at 25 WPM. Sending it at 60 WPM does
not seem very useful, either.
-- Joe, K1JT
On
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
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
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Tuesday, 3 July 2018 10:55 PM
To: WSJT software development
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
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 a good
job: he was using 2 slots, thereby keeping the queue moderately
On 7/2/2018 10:13 AM, Ed Stokes wrote:
running 1.9.1 on a Mac Mini
generally double clicking on DX station works as expected: call sign changes
and transmit is enabled.
sometimes, the software just keeps transmitting to the previous station.
It doesn’t matter if you turn off enable or halt
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
QSOs as SSB.
Openings between AJ10 and the US Northeast have been spotty and weak...
but I'm happy to have them in my log now on both 20 and 30m. :-)
-- 73, Joe, K1JT
On 6/30/2018 2:56 PM, Joe Taylor wrote:
On 6/30/2018 10:14 AM, Black Michael via wsjt-devel wrote:
... I noticed
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
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:
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)
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
On 6/29/2018 8:26 PM, David Fisher wrote:
I have the “ALL LOG” excerpt of this if you want to see it. You’ll have
to take my word on the rest.
The code version is 1.9.0-rc4 R8642. I built it from source a while back.
Version 1.9.0-rc4 was a program version made available for short-term
Hi Pat,
Please send us a screen shot showing the behavior you describe.
-- 73, Joe, K1JT
On 6/22/2018 4:16 PM, patrick hamel wrote:
Working HF with 1.9.1 - more than once I have called a station
unsuccessfully and then called another station later to have the red
line come up with
Hi Dani, Charlie, and all,
As you discovered, I never created a valid scheme for computing S/N in
JT4 (as implemented in WSJT-X). I did this today, and tested it with
various amounts of simulated Doppler spread. Corrected code will be
present in the next released version of WSJT-X.
You
Hi Gene,
On 6/14/2018 9:54 AM, Gene Marsh wrote:
Joe (and the group),
Jim Wilson, AC8NT, suggested a Field Day mod was bandied about several
months ago. Jim says he knows you and worked on some code for you. Jim
is the president of our local club (PCARS). Can you suggest an
Hi Ria,
Thanks for reporting on your experience using FT8 as a Rover during the
VHF QSO Party. We will be working on better solutions for the "/R" and
contest-mode issues.
-- 73, Joe, K1JT
On 6/13/2018 11:35 PM, rjai...@gmail.com wrote:
This weekend I was part of rover team K2EZ/R.
Enable VHF/UHF/Microwave features
Enable NA VHF Contest mode
On 6/9/2018 5:50 PM, John Pelham wrote:
I’m using v1.9.1. “A special NA VHF Contest mode can be activated for
FT8 and MSK144 modes by checking a box on the main window.”
I can’t find any such checkbox. I looked in File > Settings >
For what it's worth: on my linux box (Ubuntu 18.04 LTS) the button in
question is labeled "Close without saving". Steve's comments still apply.
Probably we should override the Qt-defined labels, to reduce confusion.
-- Joe, K1JT
On 6/8/2018 11:52 AM, Steven Franke wrote:
Hi Saku,
I
Hi all,
The WSJT-X web site now has translations of the FT8 DXpedition Mode User
Guide into German and Polish:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Thanks to Enrico Schürrer, OE1EQW, and Piotr Stuła, SP9TTG, for these
translations!
-- 73, Joe, K1JT
Pino --
On 6/1/2018 3:40 PM, Pino Zollo ZP4KFX wrote:
Hi everybody,
I am Pino, ZP4KFX.
I am not a DX expedition but it seems that I am the only ZP4 station
remained.
Years ago the where moretwo went SK... the others seem QRT.
If I appear on 20m or 17m a huge pile-up grows over me...and
Jim --
On 5/31/2018 4:47 PM, Jim Brown wrote:
On 5/31/2018 9:43 AM, Joe Taylor wrote:
Of course this could be done in FT8. But as I emphasized in a
previous email, we did not want to use a different solution for FT8
and MSK144.
As currently implemented, MSK144 has no spare bits.
Two
On 5/31/2018 1:16 PM, George Molnar wrote:
Would a unique CQ message for contest mode work, or is that asking for
confusion?
Normal mode: CQ KF2T FM18
Contest mode: CX KF2T FM18
The contest community is smaller than the general population, so it
might be an easier “sell."
*George J
On 5/31/2018 12:22 PM, Jay Hainline wrote:
Joe, is it possible to use one of the extra FT8 bits as a flag that you
are transmitting in contest mode or not? Would that be useful to keep
the program on the receiving end from being confused?
73 Jay KA9CFD
Of course this could be done in FT8.
Hi Jay, Ned, and all,
On 5/30/2018 8:57 PM, Jay Hainline KA9CFD wrote:
We had a big opening to JA today on 6m. Some of the contacts were over
10,000 km and I have heard some ops report their WSJT-X software would hang
up asking if they want to switch to contest mode. Apparently the program
sees
WSJT-X Version 1.9.1 is now available for download. This version
corrects a flaw in Version 1.9.0 that unintentionally restricted the
full use of FT8 DXpedition Mode by "Fox" stations.
New features and enhancements to WSJT-X since Version 1.8.0 are
summarized here:
Hi Neil, John, and all,
On 5/30/2018 10:39 AM, Neil Zampella KN3ILZ wrote:
Not really, the release version is 1.9.0 ... all the previous versions
were release candidates, nothing more.
Neil, KN3ILZ
On 5/30/2018 8:49 AM, John wrote:
Hi Bill,
The release note needs a minor fix:
The WSJT Development Group is pleased to announce WSJT-X Version 1.9.0.
If you have been using version 1.8.0, or a candidate release v1.9.0-rc#,
you should upgrade at this time.
New features and enhancements since Version 1.8.0 are summarized here:
Hi Al and all,
On 5/18/2018 11:21 AM, Al Pawlowski K6AVP wrote:
Why not make the FT/JT messages a bit longer to accommodate the compound calls?
If a longer tx/rx cycle time would be needed for FT8 - up to 30s would be fine
by me. It would be nice to have enough time to manually initiate a
Hi Saku,
I think we may call it a bug.
In r8665 I've made Ctrl+F11 and Ctrl+F12 change the Tx freq only when
equal to Rx Freq, and the list of Keyboard Shortcuts has been changed
accordingly. These keyboard commands override the setting of "Hold TX
freq", which seems OK to me.
Hi Steve,
I don't know what you mean by "WSJT-X jumped to Monitor #1".
If the Menu box is unchecked, the top-of window menus are not supposed
to be displayed. So what was unexpected ??
--Joe, K1JT
On 5/16/2018 1:45 PM, Steve Sacco NN4X wrote:
Generally, I run WSJT-X on my 2nd
Hi Grant,
Thanks for your message of May 11, sharing your thoughts after operating
as YJ0AG. It's good to hear that you achieved QSO rates as high as
50/hour using standard FT8 mode.
You and others will be happy to know that a General Availability (GA)
release of WSJT-X Version 1.9.0 is
Hi Dave,
On 5/14/2018 5:19 AM, David Birnbaum K2LYV wrote:
... IIRC with multiple
channels the amplitudes do not add directly but in quadrature since they
are not phase coherent. Others on this list are bettervequipped to answer.
No, that's not correct. As explained in the FT8 DXpedition
On 5/15/2018 3:45 PM, Steve Sacco NN4X wrote:
I guess the problem is pretty obvious - the forward slash after
"\WSJT-X" in the file name... :-)
"...ocal\Temp\WSJT-X/houndcallers.txt'?
No. Again: this bug was fixed several weeks ago, in r8646.
Steve --
You don't mention what code revision you are running. This bug was
(supposedly?) fixed in code revision r8646.
-- 73, Joe, K1JT
On 5/15/2018 3:30 PM, Steve Sacco NN4X wrote:
Greetings, all.
This fired again. Once again, I was away from the rig, and let WSJT-X
continue
<https://go.microsoft.com/fwlink/?LinkId=550986> for
Windows 10
*From: *Joe Taylor <mailto:j...@princeton.edu>
*Sent: *Tuesday, May 15, 2018 9:07 AM
*To: *WSJT software development <mailto:wsjt-devel@lists.sourceforge.net>
*Subject: *Re: [wsjt-devel] DxPediton Mode Development util
501 - 600 of 1516 matches
Mail list logo
