Hi Andy, Mike, Russ, ...
Yes, double-clicking on the decoded message "<...> 9M2TO -18" does not
copy 9M2TO into the DX Call entry box. Yes, we should probably add this
capability some time.
Frustrating??? Really, I don't get it. How hard can it be to type
"9M2TO" into the DX Call box,
Hi all,
I'm only a semi-serious contester, but I had good fun over the weekend
in the first WW-Digi contest. With a barefoot IC-7300 and dipole
antennas I scored a little over 66 k in the SOLP class.
In an attempt to see what software improvements might be desirable for
contesting, I've
Hi Dave,
On 8/15/2019 3:06 PM, David Gilbert AB7E wrote:
Why is so much of the FT8/4 main screen space devoted to the lower half
of the window at the expense of the activity windows? The layout just
seems really inefficient.
...
It just seems weird to me that the more useful Band Activity
Hi Serge,
On 8/8/2019 17:31, Serge F6BHK wrote:
at the dawn of WSJT-X we had the choice to decode JT65+JT9 under the
same combo value. I remember I found it very useful. When I
double-clicked a JT65 signal then I was sending using JT65, same for JT9.
would'nt it be nice to have a FT8+FT4
Hi all,
On 7/31/2019 12:32, Serge Smirnoff R6YY via wsjt-devel wrote:
Six years ago there was neither FT8 nor FT4. And today - they are the
main types of communication.
Let's not get carried away with hyperbole.
FT8 and FT4 address only one type of Amateur Radio communication: the
minimal
Joe --
On 7/18/2019 9:10 AM, Joe WB9SBD wrote:
I will double check the colors, BUT
Thinking Why should those make any difference at all anyway?
It is not just listening to all who is CQing, and then grab who is the
strongest?
Why should any of those choices below make any
On 7/17/2019 12:55 AM, Jim Brown K9YC wrote:
It has come to my attention that the default FT4 frequency on 40M has
been set to 7047.5 As N5TM put it on Slack VHF-Chat, "this is going to
start an all out war on 40M." I couldn't agree more.
I'm very active on the HF bands, and there's a LOT of
I don't understand what's bugging you. You decoded K1RMN at UTC
15:03:15, 15:03:30, 15:03:45, and 15:04:00. Evidently he called you
four times and copied no response. What did you consider egregious?
-- Joe, K1JT
On 7/17/2019 11:08 AM, Dave Slotter, W3DJS wrote:
I'm
/2019 10:27 AM, Conrad PA5Y wrote:
Thanks both Bill and Joe, that is certainly a very worthwhile
improvement, thanks to the team for the effort! I will read everything
with interest.
Regards
Conrad PA5Y
*From:* Joe
Hi Conrad,
On 7/17/2019 4:09 AM, Conrad PA5Y wrote:
Hello Joe I am quite interested to learn more about the GMSK waveform
generation, where can I read more about it and the implementation in
WSJT-X and the advantages.
A good place to start would be our document describing FT4 during its
Hi George,
On 7/15/2019 18:02, WB5JJJ wrote:
I have mentioned this numerous times without resolution. Here is what
mine always looks like. It's just not dynamically adjusting the size
based on a larger font I need to be able to read the Band Activity and
Rx Frequency sections.
We have
File -> Settings -> Frequencies: right-click in the Working Frequencies
list and select "Reset".
On 7/15/2019 1:00 PM, Tim Goeppinger via wsjt-devel wrote:
I do not see the FT4 frequencies in the frequency list. I read the
user guide and did not see this addressed. Is this by design?
Tnx
The WSJT Development Group is pleased to announce the general
availability (GA) release of WSJT-X Version 2.1.0.
WSJT-X 2.1 is a major upgrade that introduces FT4, a new protocol for HF
contesting. Improvements have also been made in the following areas:
- FT8 waveform generation using
Hi Conrad,
On 7/8/2019 18:29, Conrad PA5Y wrote:
In fact Martin, sometimes they clearly AP reflections are but often they are
not. They have no discernible doppler slant at all and appear to be a fixed
offset and have me completely puzzled. I regularly see 2 or 3 'ghost' signals
between 6
Hi Vincent,
On 7/9/2019 3:30 AM, Vincent Molloy 3DA0VV wrote:
WSJTX v2 will not accept my 3DA0VV callsign?? The full licence for The
"Kindom of Eswatini" (The countries name has changed, make sure you get
the country name right) is 3DA0(Zero)## for unrestricted licence and
3DA1## for
On 6/15/2019 10:21, Jon Anhold KM8V wrote:
###
3. On the Settings | Colors tab, select ONLY the following: "My Call in
message", "New DXCC", "New Call on Band", "CQ in message" and
"Transmitted message"
Hi Jon and Uwe,
On 6/14/2019 16:10, KM8V wrote:
For what it's worth, my experience matches David's.
Multiple times I tried to "arm" Best S+P and it never called anyone, despite
eligible stations calling CQ being decoded.
On 6/14/2019 16:22, DG2YCB, Uwe wrote:
Same experience here. Best
On 6/12/2019 12:22 PM, WB5JJJ wrote:
Mine is the 32-bit. I tried the 64 bit but it always came up with no
window sizes remember and sometimes even come up on wrong screen/size or
even completely off the screen so I went back to 32b.
This is true ONLY if you switch back and forth between
On 6/8/2019 20:33, Jason Smith Q-Sky wrote:
have an issue when restarting the application. Loads on the screen
normally and you can see signals being received, however as soon as I
click on the ‘Pre-Install’ notice all windows close, no error message,
just all disappear.
We definitely
Did you read the startup message, before clicking OK on it ???
On 6/8/2019 17:05, Svend Aage Jessen wrote:
Something strange happend right now.
Started the lastest edition of wsjtx, but it just collapsed
when clicking ok-button at the startup.
Have used this edition and it was working just fine
Use WSJT-X 2.0.1, FT8, ARRL Field Day messages.
On 6/8/2019 10:49, Ryan Tourge wrote:
So with all the updating and stuff what is going to be the preferred
mode and method for field day?
Asking for a friend...
Ryan, N2YQT
___
wsjt-devel mailing
thanks Joe, I sent a copy to developer of VQLOG soft
73, Miguel
-Mensaje original-
De: Joe Taylor [mailto:j...@princeton.edu]
Enviado el: viernes, 07 de junio de 2019 16:34
Para: WSJT software development
Asunto: Re: [wsjt-devel] MFSK MODE
Hi Miguel
On 6/7/2019 10:26 AM, ea4bas wrote
David --
On 6/7/2019 10:46, David Kaplan WA1OUI wrote:> If there is no station
that will give me a new multiplier/call on band/etc, will it call
anyone, or just sit there (or call CQ) as I experienced?
I gave you the whole sequence of priorities.
If a new multipler has called CQ, it calls
Hi Miguel
On 6/7/2019 10:26 AM, ea4bas wrote:
In FT4 mode the WSJT-X program sends the message as FT4, but the mode
created in the * .adi file is different appears MSFK mode
For reasons best known to itself the ADIF Committee has defined FT8 as
an independent mode, but FT4 to be a Submode of
Hi David,
On 6/7/2019 7:36 AM, David Kaplan WA1OUI via wsjt-devel wrote:
Can anyone tell me how Best S+P is supposed to work, as opposed to how
it did work for me during the mock ru? Apparently I’m not alone in
having it work for me the way it did.
We may not have it coded exactly right,
Hi Palle,
Let me follow up more completely on suggestions you made in an earlier
email.
On 4/15/2019 6:13 PM, Palle Preben-Hansen, OZ1RH wrote:
Hi,
People are using EU VHF if they are in a contest requiring either a
serial number and/or the full 6-digit locator. This is required in the
Hi Palle,
On 6/6/2019 9:06 PM, Palle Preben-Hansen, OZ1RH wrote:
As reported b4 I experienced the error window "Invalid QSO Data Check
exchange sent and received" on nearly every of the 103 QSO's I did in
the mock contest. I have noticed two causes:
1. If my QSO was with a station not
Thanks to all who participated in yesterday's FT4 mock-contest practice
session -- and especially to those who provided useful feedback. It is
much appreciated!
Everyone likes the 7.5 s T/R sequences, which provide operators with
significantly more human-interaction time than in previous
Hi Jesus,
I cannot reproduce the problem you describe. Please give us a
step-by-step recipe, beginning with program startup (in XXX mode?) that
will show the incorrect sequence length for FT4.
-- 73, Joe, K1JT
On 6/5/2019 11:19 AM, Jesús Gutiérrez Rodríguez wrote:
Good afternoon, I
On 6/4/2019 15:59, Adriaan Koopman wrote:
Dear OM,
Audio goes by 64bits *Candidate Release/WSJT-X 2.1.0-rc7 /*/still to
100%./*/
/*
*/73, Adriaan PE2K/*
Read before download: Known Issues:
https://physics.princeton.edu/pulsar/k1jt/Known_issues.txt
DV2/W8NET in the Philippines
Licensed since 1974
On Jun 4, 2019, at 12:12 PM, Joe Taylor <mailto:j...@princeton.edu>> wrote:
Hi Gene,
I have seen nothing like the duplicate decodes you report. Please
send us the .wav file for one or two of your examples, and tell us
something about
Hi Gene,
I have seen nothing like the duplicate decodes you report. Please send
us the .wav file for one or two of your examples, and tell us something
about your computer setup.
-- 73, Joe, K1JT
On 6/4/2019 11:39, Gene Marsh via wsjt-devel wrote:
FT4: I have seen 7-8 times, double
Hi Alan,
On 6/4/2019 6:44 AM, Alan Hopper wrote:
on rc7 trying to use jt9.exe to decode a wav works on the 32bit version
but fails on the 64bit version. It throws
At line 58 of file C:\Users\bill\src\k1jt\wsjtx\lib\readwav.f90
Fortran runtime error: Inquire statement identifies an internal
To: Users of WSJT-X -- especially those interested in radio contesting
From: WSJT Development Group
We apologize for the confusion created by release yesterday of WSJT-X
2.1.0-rc6. That program version had a bug that prevented it from
running for some users. This bug has been fixed in
On 6/2/2019 9:07 AM, Black Michael W9MDB via wsjt-devel wrote:
Was looking at the nhash.c function and it's always masking the result
to 16 bits.
final(a,b,c);
c=(32767);
return c;
Don't we want 32 bits from nhash for FT8 so we can use 28 bits or such
for the message? Or at least
Hi Rich,
On 5/30/2019 19:49, Rich Zwirko - K1HTV wrote:
If stations with non-standard non-compound calls are presently
allowed to skip the TX1 message and start with TX2, will a future
release of WSJT-X inhibit users with such calls from doing the TX1 to
TX2 skip?
Perhaps. But think
On 5/30/2019 10:24 AM, Black Michael via wsjt-devel wrote:
Is there any reason TX2 can't default to be " ME -01" instead of
"THEM -01" ?
YES.
You're assuming ME is a nonstandard call, which needs 58 bits to be sent
in full. In your example the hashed call uses 12 bits. That
does not
Hi Ed,
No changes (yet) to the frequencies recommended for FT4.
-- Joe, K1JT
On 5/28/2019 12:08, e...@w0yk.com wrote:
Are the currently recommended FT4 frequencies still what are in 2.1.0 rc5?
I've found a few stations on 14.080 but haven't seen anyone on 7.047 yet and
wondered if I
Hi Pete,
On 5/17/2019 10:59 PM, Pete wrote:
I've been trying to get the ft4d program (2.1.0-rc5) to compile with
Cygwin64 on Windows 10 (just because) and ran across this oddity.
The ft4b subroutine in ft4b.f90 calls the getcandidates4 subroutine like
this:
call
On 5/15/2019 1:13 PM, donald rossman KC3SCZ wrote:
Joe Taylor how I can get ft4 I am looking forward to it I like it up in
Firefox only I see
Is ft8 I am trying found it only I see is wsjt one I see is ft8 not ft4
are you still working on ft4
Available downloads are always posted
Hi Mike,
I'm looking at some timing issues that are critical for FT4. You're
using a Flex (and I suppose, PowerSDR/Thetis), right? Could you please
send me an extract from your ALL.TXT file for the recent FT4 practice
session? That's May 8, - 0100 UTC (190509_00 through
For the record, in np particular order, here's a list of comments or
problems mentioned in reports from last night:
1 Timing is very tight: hard to raise someone on 1st call
2 Seemed to miss too many decodes
3 No auto-response when receiving R+exch after I sent RR73
4 Many repeated CQs
Thanks to everyone for feedback on FT4 over the past 10 days -- and
especially from yesterday's practice contest session! Your reports have
been very helpful. My own report is included below, but first let me
give an overall status report.
FT4 works well, but (as implemented WSJT-X
Reminder to all:
FT4 Practice Contest session this evening (NA time), May 9 to 0100
UTC.
Details and instructions can be found here:
http://physics.princeton.edu/pulsar/k1jt/FT4_Practice_Contest.txt
-- 73, Joe, K1JT (for the WSJT Development Group)
One-hour "practice contest" sessions will be held this week and next
week using the FT4 mode and the ARRL RTTY Roundup rules.
Thursday, May 9, -0100 UTC (Wednesday evening, May 8, NA time)
Tuesday, May 14 -0100 UTC (Monday evening, May 13, NA time)
Dial frequency 7.090 (and higher, in
On 5/3/2019 11:21 AM, DG2YCB, Uwe wrote:
Next curious observation: WSJT-X 64 bit and JTDX in parallel, listening
to 6m band, both connected to the same audio source, no QSO running,
only a few stations on band, with both programs saving all audio files
to my SSD. Results: From time to time
Jari --
Please click on "Read Before Download" here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
... which will take you here:
http://physics.princeton.edu/pulsar/k1jt/Reported_bugs.txt
There is no need to provide further feedback on any of the known issues
in WSJT-X 2.1.0-rc5 that
Hi Paul,
On 5/2/2019 8:43 PM, Paul Kube K6PO wrote:
The documentation
http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol.pdf says, re S+P:
"Here “best potential QSO partner” means “New Multiplier” (1st priority)
or “New Call on Band” (2nd priority)."
Now it seems to me that "New Call"
Hi Chris,
On 5/2/2019 12:52 PM, Topher Petty AI8W wrote:
... I don't believe it's available processor power, or RAM availability.
With only WSJT-X, TQSL, and Chrome (six tabs open) running, the T410 has
more than enough processor (24 threads) to handle these decodes, yet
they're not being
On 5/2/2019 10:07 AM, DG2YCB, Uwe wrote:
I’ve just made my first QSO with JTDX while running WSJT-X in parallel.
And believe me or not: It happened exactly that what I noted in my first
email. Look at the following screenshot: JTDX got the full QSO, but
WSJT-X missed F5NK’s “+05” reply. Means
To: Beta-Testers of WSJT-X 2.1.0-rc5
Thanks for your help in improving the quality of WSJT-X. Before sending
bug reports to this email reflector, please check the list of known bugs
posted here:
http://physics.princeton.edu/pulsar/k1jt/Reported_bugs.txt
-- 73, Joe, K1JT
Please read messages to the list before sending your own on the same topic!
Please read the announcement abou -rc5:
"Windows users will discover that WSJT-X v2.1.0 has been made available
as a 64-bit MS Windows build for 64-bit versions of Windows since Vista.
This version has one known
Paul --
Did you read the -rc5 announcement before downloading the new package ???
"Windows users will discover that WSJT-X v2.1.0 has been made available
as a 64-bit MS Windows build for 64-bit versions of Windows since Vista.
This version has one known defect. The audio input device level
Hi Ria,
Good to hear from you!
On 4/30/2019 14:10, rjai...@gmail.com wrote:
Hi Joe, Bill, Steve and team,
I'm getting feedback about the frequency choices for the initial FT4
rollout. There is conflict with users because it is so low down in the
band on 40 meters (7047). The QRP fox hunt (CW)
Gary --
Did you read the -rc5 announcement before downloading the new package ???
"Windows users will discover that WSJT-X v2.1.0 has been made available
as a 64-bit MS Windows build for 64-bit versions of Windows since Vista.
This version has one known defect. The audio input device level
On 4/29/2019 18:52, Edfel Rivera KP4AJ wrote:
Not sure if missing something from guide, Contest Log not showing new
QSO with FT4. RC5 Windows 10 64bit.
Contest logging takes place only when contest messages are used. Are
you in contest mode?
-- Joe, K1JT
Chris and all --
On 4/30/2019 13:05, Chris K2CR wrote:
Hi, all. I was also frustrated by the moving OK/Cancel buttons in the
logging dialog. I think this change was made without regard to those hams
which require accessibility assistance, and good UI practice.
We really do not need further
Hi Jari,
On 4/30/2019 9:02 AM, Jari A OH2FQV wrote:
I meant, when I open 2.0.1 version after using 2.1.0, - 201 main window
opens in center to my (win 7 pro 64bit) desktop and other windows are
minimized, including contest window.
I need to open them separately, reposition and resize them.
To: Users of WSJT-X -- especially those interested in radio contesting
From: WSJT Development Group
By now most of you know about the FT4 protocol under development for
eventual release in WSJT-X 2.1.0. The new mode is particularly
optimized for use in radio contesting.
FT4 is mostly like
Thanks to Michael Chen, BD5RV, for translating "The FT4 Protocol for
Digital Contesting" into Chinese. The English document and all
available translations are now will posted on the WSJT-X web page:
https://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Scroll down to near the bottom.
Thanks to Saku Nylund, OH1KH, for translating "The FT4 Protocol for
Digital Contesting" into Finnish.
I have posted the translation here:
http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol_fi.pdf
A link to this document in English and all available translations will
soon be posted on the
Thanks to Dany Bélanger, VE2EBK, for translating "The FT4 Protocol for
Digital Contesting" into French.
I have posted the translation here:
http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol_fr.pdf
-- 73, Joe, K1JT
___
wsjt-devel mailing
Thanks to Miguel Iborra, EA4BAS, for translating "The FT4 Protocol for
Digital Contesting" into Spanish.
I have posted the translation here:
http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol_es.pdf
-- 73, Joe, K1JT
___
wsjt-devel mailing
Hi Jordan,
On 4/22/2019 14:30, Jordan Sherer KN4CRD wrote:
Contesting on the WARC bands is discouraged. It seems reasonable to
think that including calling frequencies on 10/18/24 MHz should be
avoided for this mode since it is specifically designed for radio
contesting. Do you agree?
Of
Thanks to Enrico Schürrer, OE1EQW, for translating "The FT4 Protocol for
Digital Contesting" into German.
I have posted the translation here:
http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol_de.pdf
-- 73, Joe, K1JT
___
wsjt-devel
To: WSJT-X users interested in testing FT4
From: K1JT, K9AN, and G4WJS
Soon after the "FT8 Roundup" held on December 1-2, 2018, we started
serious work on a faster, more contest-friendly digital mode that can
compete with RTTY-contesting QSO rates while preserving many of the
benefits of
Hi all,
On 4/14/2019 7:56 AM, Tom Melvin GM8MJV wrote:
What I can’t workout is why people are using EU VHF in the 1st place.
On 4/15/2019 6:13 PM, Palle Preben-Hansen, OZ1RH wrote:
People are using EU VHF if they are in a contest requiring either a
serial number and/or the full 6-digit
Hi Fred,
FT8 generates a pure 8-tone FSK signal. There is no carrier, and no
amplitude modulation.
-- 73, Joe, K1JT
On 4/5/2019 12:58, Frederic Beaulieu wrote:
Hello,
I’m discussing with a friend about the FT8 maximum power allowed in
Canada (see below Industry Canada extract) .
On 3/19/2019 10:43 AM, Black Michael W9MDB via wsjt-devel wrote:
There's a possible bug in the Hound moving logic where TX3 gets shifted.
Shouldn't the m_nFoxFreq>600 be n_nFoxFreq>900??
if (m_nSentFoxRrpt==2 and m_ntx==3) {
// move off the original Fox frequency on
Not a good idea to install SimJT in directory
"C:\Program Files (X86)\WSJT".
Re-install in directory C:\WSJT, or perhaps
C:\SimJT.
On 3/10/2019 7:04 AM, Christian wrote:
Hi group,
When I try to execute the last version of SIMJT.exe on Win7-pro 64bit
updated, "Execution error 13:
so cannot monitor through
the nights reliably.
73,
Mike
K7MDL
-Original Message-----
From: Joe Taylor
Sent: Monday, March 4, 2019 15:00
To: WSJT software development
Subject: Re: [wsjt-devel] Busy CPU
Hi Al,
Decodes do not fail because of a slow or overburdened CPU. They simply ta
Hi Al,
Decodes do not fail because of a slow or overburdened CPU. They simply
take longer.
This is true for all modes supported in WSJT, MAP65, and WSJT-X.
-- 73, Joe, K1JT
On 3/4/2019 2:37 PM, Al K0VM wrote:
(WSJT-X 2.0.1)
I have noticed that at times while running FT8
Hi Attila,
How nice to head from you! Comments in-line below:
On 2/25/2019 4:09 PM, Attila de 4U1ITU wrote:
Dear WSJT-X developers,
I appreciate very much your development of FT8.
We at the 4U1ITU started to use the last version of FT8 (Version 2.0.1)
last week during the CPM-19, mostly in
Hi Frode,
The attached "diff" file might save you some work looking for changes to
the User Guide. The changes are generally small: some updated screen
shots, corrected or added text in a few places, etc.
-- 73, Joe, K1JT
diff --git a/doc/CMakeLists.txt b/doc/CMakeLists.txt
index
The WSJT Development Group is pleased to announce the general
availability (GA) release of WSJT-X Version 2.0.1, a bug-fix release.
It includes repairs of defects reported up to February 22, 2019.
For a list of corrected bugs see the Release Notes:
On 2/18/2019 17:53, N0UU wrote:
A long time looker at this subject: Why do we need to take the AF
signal and run it thru whatever steps to make an RF signal?
That just seems to require way too much processing. Can anyone explain
why the various signals can't be simply generated, especially
Hi Tom,
Pretty daft to kill processes that may be needed on an assumption.
It's not daft, at all. Probably 99% of WSJT-X users run only one
instance. In the rare but not unheard-of case where something caused a
program crash, jt9.exe may be left running. When WSJT-X is re-started,
that
Hi George, Hasan, and all,
On 1/21/2019 17:09, Hasan al-Basri wrote:
I agree, George, CM worked wonderfully. Processing my log for ARRL was a
complete pain. The cab file has full freq in it, and ARRL won't accept
it in the upload. So I had to edit the file. The file had full freq and
ARRL
On 1/21/2019 10:49 AM, DG2YCB, Uwe wrote:
Interesting is the following: Same station, same equipment, same
settings, same signal level, just a couple of minutes later. Maybe DD7…
has his antenna in a more direct direction?
The aircraft reflection that had caused the Doppler-shifted signal in
Hi Philip,
Our policy is to report all decodes that include a grid square, as we
receive them. Multiple decodes of the same transmission by the same
receiving station are most frequently caused by:
1. Low-level sidebands offset in frequency by multiples of the
power-line frequency.
NA VHF Contest messages are working perfectly here -- and for everyone I
am working. What do you consider "broken" ?
-- 73, Joe, K1JT
On 1/19/2019 20:56, Edfel Rivera wrote:
Hi:
Not sure it was stated, when settings NA VHF, functionality seems broken
compared with RU.
Hi Bill,
Thanks for sharing your draft: an interesting analysis of the changeover
to the "v2.0" message formats for FT8. Here are a few more comments, in
addition to the ones already posted here by Bill Somerville, G4WJS.
1. We published a schedule, three months in advance, specifying
It has nothing to do with "separate carrier". Rather, the messages are
being sent as free text and therefore are truncated when longer than 13
characters.
DXpeditions using compound callsigns like KH1/KH7Z are properly
supported in DXpedition mode. Those like 9LY1JM that use nonstandard
Yes
On 1/12/2019 11:42, nick wrote:
In wsjtx-2.0.0 the state of the CQ Only checkbox is not saved on exit.
There is no entry for it in WSJT-X.ini.
Is this by design?
73
Nick
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Thanks, Ashley! I guess that error has been in qra64.c for a long time,
without anyone noticing. ;-)
-- Joe, K1JT
On 1/8/2019 2:55 AM, Ashley Brighthope wrote:
Hi, i noticed during compiling the source of
784f75 master
Hi all,
I'm relaying the message copied below for Jeff, WK6I.
-- 73, Joe, K1JT
Please share this notice with your local groups, as appropriate.
Same time and same drill as in recent years. This coming Friday,
Hi Gaëtan,
On 12/28/2018 4:05 AM, ON4KHG wrote:
So, if I have well understood, as far as AP and Auto Seq are not concerned (and all other things being
equal), messages like "F6ABC ON4KHG 73" or "73 XYZ TU" (or even "ABCDEFGHIJK")
should equally well be decoded ?
HNY 2019.
Just a bit more
Hi Igor,
On 12/22/2018 05:10, Игорь Ч UA3DJY via wsjt-devel wrote:
Hello Joe,
.
There is a bug in packjt77 module observed when first character of the
base call is 'P' in the compound callsign.
It can be seen in ft8apset.f90 code, where message with user's callsign
DU6/VA3AAA is packed as
bogus
decodes (while averaging) show up, there is nothing at all shown in the
averaging window (F7).
Thanks for your help.
73, Russ K2TXB
-Original Message-----
From: Joe Taylor
Sent: Saturday, December 15, 2018 1:31 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Version 2.0 is
Hi Brian,
On 12/17/2018 7:28 PM, bagel W9BGL wrote:
Now that FT8 version 2 is released and the uptake on the new version is
very successful, I hope this is an appropriate time to ask questions of
the development team. I want to learn the details on the FT8 decoding
algorithms. I am reading
Hi Lance,
On 12/15/2018 15:18, L Barley wrote:
I'm using v2.0.0 on Windows 10 and the "worked before status" isn't
functioning. It looks like I have the appropriate boxes selected in the
settings area. I've been working on this for several days without any
improvements.
Does anyone
Russ --
You're calling some displays "bogus decodes", and evidently they are
bogus. But you appear to have all the knobs turned up to maximum
aggressiveness. Most if the displayed messages are flagged with "?",
which you may interpret as "caveat emptor", or some such.
Probably you saved
Ton --
On 12/15/2018 12:11, Ton PA0TBR wrote:
I am trying to work out why some callsigns are shown as <...> in WSJT-X
Sometimes <...> is reflected in JTAlert as ... other times it is not
shown in JTAlert.
Why not consult the User Guide? Why do you think we bother to write
one, which takes
Hi Charlie,
On 12/15/2018 12:38, G3WDG wrote:
If deep search is engaged, does it look through call3.txt randomly, or
start for example at the most recent entry?
Deep Search uses whatever is saved in CALL3.TXT. There's nothing
'random' about it, and order in the file does not matter. If you
Many thanks to all those who are helping to further the transition to
new protocols for FT8 and MSK144!
This morning I ran an instance of WSJT-X v1.9.1 in parallel with WSJT-X
2.0. An informal count of decodes in the old and new protocols shows
far more activity using the new 77-bit
On 12/13/2018 12:19 PM, Conrad PA5Y wrote:
Once upon a time it was recommended that FSK441 and JT65 should use a 44.1kHz sample rate and the newer modes such as MSK144 and FT8 should use 48kHz? What about JT6M?
WSJT-X *always* requests data sampled at 48 kHz. That's true for all
supported
Jim --
On 12/13/2018 10:44 AM, ai...@use.startmail.com wrote:
After finding the exe in the bin folder, I searched the online guide for
the term "aggregator" and came up empty. A search through the mailing
list turns up some hits, but the interface is utterly tedious
... Is that a complete air
Hi Edfel,
On 12/12/2018 4:30 PM, Edfel Rivera KP4AJ wrote:
My question is this, when I change mode to MSK144, freq defaults to
50.280 but when I check frequency used but stations doing contacts in
50m, freq is 50.560. Same goes to JT65 default freq is 50.310 but JT65
used to use 50.276.
Patrick --
On 12/12/2018 3:34 PM, Patrick 9A5CW wrote:
Hi Bill,
i suposed that only shud be in the <...> but i see when
i checked my all.txt
that normaly also the callers are marked the same... is that normal
behaviour?
Please read Section 7.5, "Compound Callsigns" in the WSJT-X 2.0 User
Hi Svend,
On 12/12/2018 7:31 AM, Svend Aage Jessen LA6YJA wrote:
The info / message box that opens at startup...
How to deactivate this one, or will it deactivate by itself
at the date set in this box?
I guess you would prefer not to see the startup message. Perhaps you
do not mind if we
301 - 400 of 1516 matches
Mail list logo
