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 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
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 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
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
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,
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 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/
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
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:
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 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
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 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
Hi Peter,
Unfortunately, take-up and use of WSJT-X by VK and ZL VHF operators --
at least by those who report back to us -- was rather slow during the
"candidate release" periods of v1.8.0-rc1 and -rc2. We can't fix what
we don't know is broken.
The first we heard of this problem was 10
what's already there.
-- 73, Joe, K1JT
On 5/8/2018 10:37 AM, Joe Taylor wrote:
In Fox mode WSJT-X maintains several queues.
A specified Hound callsign stays in Fox's "available to be selected"
list for up to 2.5 minutes after the most recent decode of that Hound.
Wh
Hello Take,
On 5/14/2018 7:14 PM, Tsutsumi Takehiko wrote:
Hi David,
Thank you for disclosing and sharing the motivation of the current FDM
frame architecture of Dxpedition mode.
I believe you are responding to comments made by Bill (G4WJS), not by
David (K2LYV). Bill's comments were made
Hi all,
Hearty thanks to everyone who participated in the Third Public Test of
FT8 DXpedition Mode!
A number participants and would-be participants reported that
propagation was spotty, at best. Nevertheless, at AA7A, G4WJS, K1JT,
and K9AN we copied 405 unique callsigns of stations acting
Hi Hasan,
I have some questions about the May 5 test run that you may be able to
help with. I am copying this message to the wsjt-devel list in the hope
that others with useful information might comment, as well.
You are one of six stations that appear in the log of W7/KH7Z three
times.
Hi all,
If your callsign is in the following list, could you please reply
off-list to let me know what program version you were using during the
May 5 Fox-and-Hounds test run, and whether you were operating in Hound
mode all the time? We are trying to understand why some "R+rpt" (Tx3)
FYI to folks on this list
Forwarded Message
Subject: Re: [wsjtgroup] DX Mode Test Bug Report
Date: Tue, 8 May 2018 10:51:05 -0400
From: Joe Taylor j...@princeton.edu [wsjtgroup]
<wsjtgroup-nore...@yahoogroups.com>
Reply-To: Joe Taylor <j...@princeton.edu>
Hi Gene,
On 5/8/2018 1:01 PM, Gene Marsh W8NET wrote:> What it the time for
“staying in the queue?> I took a “bio break”, and missed the
first try (first pic). The > lag was 4:15. Second pic is my
successful QSO:
From the *FT8 DXpedition Mode User Guide*, item #19 on p8:
Gene --
On 5/8/2018 1:25 PM, Gene Marsh W8NET wrote:
I understand. But, look closely at this pic. The last time I called
the Fox was at 153115. The Fox responded at 153530. The Fox had my
call in queue for 4:15?
In Fox mode WSJT-X maintains several queues.
A specified Hound callsign
Hi Ned,
Good job operating as W7/KH7Z! I haven't checked your dupes, yet, but I
copied you logging 318 QSOs in 94 minutes.
I also noticed most the items mentioned in your email. I confirm that
sort-by-grid fails (and program crashes) if there's a grid that displays
as "" in the list.
<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
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 Dick and all,
On 5/12/2018 12:51 PM, Dick Hale W7PP wrote:
The test went fine here but. I connected with the fox
sending a -17 signal report without problem. The fox set me the RR73 and
the program logged the contact... Then, and I don't know why, the
program sent another -17
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
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.
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
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 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 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
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
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 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.
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 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:
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.
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
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 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
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/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
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 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:
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/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,
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
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
Tnx George -- This bug (visible only in MacOS, I believe) has been fixed
in code revision r8646.
-- Joe, K1JT
On 5/1/2018 11:57 AM, George Molnar wrote:
I’ve had this reproducible error occur a few times now. 1.90rc4 (8642)
downloaded from the WSJT-X homepage crashes when
Hi Hideo-san,
On 4/27/2018 2:37 AM, JH3XCU wrote:
WSJT-X v1.9.0-rc4, mode change problem:
It will not be displayed correctly when WSPR - JT9etc mode changed.
Please see attached e-file
73, Hideo - JH3XCU
1. Use the mouse to grasp the right edge of the text window. You can
set its width
Hi Peter,
For completeness, this message is an addendum to the one sent a few
minutes ago.
You asked whether the variance in measured frequency offsets might be
too high. As you point out, it goes from -126 to -131 Hz across the 30
second period.
In your file fmt.all the variation
Hi Ray,
Probably you should not have selected "Settings -> Enable
VHF/UHF/Microwave features", since you are operating on an HF band.
You should not select "NA VHF Contest", since you are not operating in a
North American VHF contest.
-- 73, Joe, K1JT
On 5/2/2018 1:38 PM, Reinhard
Hi Peter,
The semi-automated calibration procedure assumes that you will use
calibration signals on at least two different frequencies.
You have used just one, at 144.450 MHz. Nevertheless, I think you can
do a good job of calibration with your existing data, using "by hand"
the individual
Hi Saku,
Thanks for your translation to Finnish of the FT8 DXpedition Mode User
Guide!
-- 73, Joe, K1JT
On 4/29/2018 2:55 PM, Saku wrote:
Hi !
I have translated ( Google did, and I fixed it to understandable Finnish
form ;) ) latest DXPedition mode manual's part for hounds
Hi Roger,
On 4/27/2018 11:52 PM, Roger Rehr W3SZ wrote:
Here I find the following:
When jt49sim is commanded to produce a jt4 wave file it produces a jt9
wave file, e.g. the command:
jt49sim "K1ABC W9XYZ EN37" 4C 1 0.0 0.0 1 -15
produces a JT9C wave file instead of the expected JT4C
Hi Hideo-san,
On 4/27/2018 2:37 AM, JH3XCU wrote:
WSJT-X v1.9.0-rc4, mode change problem:
It will not be displayed correctly when WSPR - JT9etc mode changed.
Please see attached e-file
73, Hideo - JH3XCU
1. Use the mouse to grasp the right edge of the text window. You can
set its width
Hi Peter,
On 4/26/2018 7:56 PM, Peter Sumner VK5PJ wrote:
as WSPR has been around for a long time now its value is well known
on HF and 50 MHz but as frequency increases the ability to find rigs
with the needed frequency stability and accuracy is not always easy.
There is a diverse group
Hi all,
I write to remind you of the third public test of *FT8 DXpedition Mode*
scheduled for Saturday, May 5, 1400-1700 UTC. You are cordially invited
to participate -- the more participants, the better!
Our main goal is to simulate pileups in which many "Hounds" call and
attempt to work
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 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
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
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
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
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
Click on the link at the bottom of all these messages, including yours:
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
... and scroll down, look for "Unsubscribe", etc...
On 1/17/2018 11:00 AM, James Barron wrote:
Someone please tell me how to get off this list?
Thank you very much
Hi Philip,
WSJT-X knows nothing about GPUs and makes no use of one. I run
PSKreporter alongside WSJT-X all the time, with no noticeable effect on
decoding performance.
-- Joe, K1JT
On 1/16/2018 10:51 AM, Philip Gladstone wrote:
One of the pskreporter users reported that when he
Hi Don,
Thanks for your message and your interest in FT8, etc.
We're well aware of the tables of "good CRC polynomials" published by
Koopman, though admittedly we have not always used them to best advantage.
Steve Franke, K9AN, did an extensive series of tests with different CRC
generators
Don --
One other matter...
Is there a more detailed description of the various modes available to
members of this list? I am a new ham, but did waveform design and
optimal detection for many years until I retired last May. I may be
able to help in some manner.
For detailed descriptions
Hi Mike,
As has been described here on a number of occasions before, all incoming
audio is saved to a *.wavfile. If you have *Save | None* checked, these
files will be deleted about 3/4 of the way through the next T/R
sequence. Thus, these files should not be accumulating unless you
If you receive this email, the list believes you are a member. You must
remove yourself: click on the link at the bottom every message from this
reflector.
On 1/25/2018 5:33 PM, iz6gvc--- via wsjt-devel wrote:
Please, remove this email from your mailing list, I'm not member.
Thanks and 73s
On 1/25/2018 8:45 AM, Black Michael via wsjt-devel wrote:
Yes they do. But the main problem for this is all the different
antennas one may have make it a band-specific value in a lot of cases.
Not so useful in that case.
This is not correct. WSJT-X reports Antenna Description information
Mike --
It's harmless -- and it's useful. You may comment it out if you choose.
-- Joe, K1JT
On 1/30/2018 11:10 AM, Black Michael via wsjt-devel wrote:
Is this code still needed? Or is "testing" done now? Was checking some
events and noticed this file check firing constantly.
Hi all,
You have probably heard something about recent efforts to develop a
special "FT8 DXpedition Mode" in WSJT-X. This message aims to bring you
up-to-date on our progress, and generally to make our plans more widely
known.
The basic goal of *FT8 DXpedition Mode* is to enable
Hi all,
In preparation for an upcoming release candidate of WSJT-X v1.9.0, I am
updating the WSJT-X User Guide. If you are aware of anything that needs
work in the User Guide, please post a message here or otherwise let me know.
Here's a specific question for Mac users. In Section 3.3 we
Hi Erik,
On 2/9/2018 8:43 AM, Erik Icket wrote:
Would it make sense to implement a feature so that CQ messages do not
start transmitting in the middle of an interval ?
Today, if one wants to launch a CQ message at the next interval, one has
to (1) observe the time, (2) select the appropriate
Hi Neil,
Many thanks for catching these omissions in the v1.9.0 User Guide. Much
appreciated! Even when we "know" about the need for such updates, at
some level, we don't always remember. It's good to be reminded.
-- 73, Joe, K1JT
On 2/11/2018 8:32 AM, Neil Zampella wrote:
Hi
Hi Jordan,
My guess is that (at least at present) the interest here is minimal.
Your idea for exchanging much longer messages is pretty far from the
core goals of the modes supported in WSJT-X.
Please don't let my comment discourage you from proceeding as you wish,
toward something new.
Hi Ivan,
On 2/8/2018 10:12 PM, I Yanasak AI0IA wrote:
With the latest GA version of WSJT-X (1.8.0), running Windows 10, I am running
into the problem where the auto-logging and CW ID features are highly
unreliable, at least using standard messages.
As far as I can tell, the only time that
Hi Per-Tore,
On 2/9/2018 5:24 PM, PTAa LA7NO wrote:
I wonder what the rationale behind this is:
"Hounds acknowledge having been called and send their “R+rpt” message at
a randomly selected frequency between 300 and 900 Hz."
If I was heard by the Fox on a certain freq., would it not be best
Hi Richard,
Thanks for your comments and suggestions.
On 2/9/2018 5:10 AM, Richard Lamont G4DYA wrote:
So there's no need for the Fox to transmit FT8S-type signals using
multiple tones. It would be possible to use a new modulation scheme, for
the Fox only, which uses the whole of the SSB
Itzok --
On 2/19/2018 11:56 PM, Iztok Saje S52D wrote:
Z6 is not (yet) on the list of 330 valid prefixes (prefixes.txt), as it
is rather new.
Your comment seems to indicate a serious misunderstanding about the way
standard callsigns and compound callsigns are handled in the structured
On 2/20/2018 4:23 PM, g...@isect.com ZL2IFB wrote:
I noticed that /M and /MM are missing from the "Short-list of Add-on
Suffixes" under the Help menu: is that just a little error on the help text
or a genuine (if surprising) omission from the list?
I'm puzzled because I worked a /MM station
Hi Per-Tore,
On 2/20/2018 3:24 AM, PTAa LA7NO wrote:
I wonder what the rationale behind this is:
"Hounds acknowledge having been called and send their “R+rpt” message at
a randomly selected frequency between 300 and 900 Hz."
If I was heard by the Fox on a certain freq., would it not be best
Doug --
Since wsjt-x 1.9.0-rc1 is not a public release, did you build it
yourself? Using what SVN code revision?
I see no evidence of a memory leak in Windows. Likewise for a short
test running under Ubuntu 14.04.5 LTS.
-- Joe, K1JT
On 2/21/2018 2:43 PM, Doug Collinge wrote:
Mike --
You're barking up the wrong tree. There's no reason that Fortran open()
and cloce() statements must be balanced. Many of the files remain in
use as long as jt9 is running; on termination all files are closed be
default.
-- Joe
On 2/21/2018 2:55 PM, Black Michael via
Steve --
On 2/21/2018 3:41 PM, Stephen Hicks, N5AC wrote:
If I understand correctly, the process will be for the fox to transmit
multiple carriers in the 300-900Hz range. If this is the case, have
there been any experiments run that verify that typical PA linearity
will be acceptable? If
Ricky,
Please be aware that the code development branch, which has revision
numbers later than r8193, is presently NOT for use on the air.
For normal operation you should be using the released program version,
v1.8.0.
-- 73, Joe, K1JT
On 12/21/2017 12:52 PM, Ricky Scott W7PSK
Jim --
On 12/20/2017 11:19 PM, Jim Record wrote:
Has it been considered to replace the use of shell.f90 (a shellsort)
that fully sorts before finding the kth element? The quickselect
algorithm is much faster as it does only a partial partitioning of the
data to find the kth element.
Jim
The WSJT Development Group is pleased to announce a Release Candidate of
WSJT-X Version 1.9.0. This is a second beta release, so it's called
v1.9.0-rc2. A first candidate release, v1.9.0-rc1, has already been
tested in the field by a small test group. A General Availability (GA)
release of
On 2/26/2018 3:20 PM, George J Molnar wrote:
Any chance for 6-place grid squares at VHF & higher?
Of course you can send a 6-character locator as part of a free text
message.
But as a JT-style structured message??
Think about it this way: A 4-character Maidenhead locator fits in a
15-bit
801 - 900 of 1545 matches
Mail list logo
