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 nonstanda
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 0
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 show
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 installatio
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 ist
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 ar
From my post to this list several days ago (see item #3):
#
For the record, and to avoid the necessity for multiple posts on the
same issue, here is a list of currently known bugs:
1. If a message's first callsign contains
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
!!!
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 lette
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 -r
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
message. 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 ca
o now.
-- 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".
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 wsjtx-2.
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
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 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 g
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 in
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
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 menti
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 stat
Hi Mark,
Thanks for your reply. The "/R" usage is intended for NA VHF contest
messages only. You can't "mix and match" with the special message
formats. Thus, you can't use a "/R" callsign in (say) the special RTTY
Roundup message formats.
See the example QSOs in the "Quick-Start Guide to
Tnx Mike, it will be in -rc3.
-- Joe, K1JT
On 9/26/2018 2:22 PM, Black Michael via wsjt-devel wrote:
I submitted this before but since it's not in RC2 here it is again.
Need to turn off transmit before we reset power after Tune otherwise can
get a power spike at the end of Tune.
els
Tnx Alex, it will be fixed in -rc3.
-- 73, Joe, K1JT
On 9/26/2018 3:19 PM, Alex Voytko wrote:
Hi!
See in the attachment..
Best regards..
Alex UR5NMZ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge
Hi Uve,
I cannot reproduce the problem you describe.
See the attached screen shot. OE1KFV is in the log, at JN88. OE1KFV is
identified as a new call, which is correct.
I don't know what your yellow color means?
-- Joe, K1JT
On 9/26/2018 1:01 PM, DG2YCB, Uwe wrote:
- Fixed a b
not issued in Austria!
It's either OE9KFV or OE100KFV.
73, Frank
OE9KFV
OE100KFV
-Ursprüngliche Nachricht-
Von: Joe Taylor
Gesendet: Mittwoch, 26. September 2018 22:30
An: WSJT software development
Betreff: Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc2
Hi Uve,
I c
Thanks to all who reported on experiences during the FT8 mock contest
last evening. Reports are still coming in, but this seems like a good
time to summarize some basic conclusions.
Beta-testing of software is done to help identify problems including
programming errors, missing or broken feat
Hi Andy,
If you have read and understood the documentation distributed with
WSJT-X 2.0-rc1 and -rc2, you must understand that there is no room in a
77-bit message for two nonstandard calls and a signal report, even if
one of the nonstandard calls is encoded as a hash code.
-- Joe, K1
Dave --
Please use the original (or at least an informative) subject line rather
than allowing your email client to insert something like
"Re: [wsjt-devel] wsjt-devel Digest, Vol 55, Issue 106".
As best I can infer from information you've provided, you must not have
had a valid entry in the "
Keijo --
On 10/1/2018 9:30 AM, OG55W wrote:
- Program version WSJT-X v2.0.0-rc2 cc148d
- Windows 10, latest update yesterday
- I need to tell to other stations with free text that they can not get
the QSO with me with RC1. RC2 is working OK
- When I come back from free text to standard text ENA
Keijo,
On 10/1/2018 10:31 AM, OG55W wrote:
1. Start WSJT-X 2.0-rc2 with "MyCall" = OG55W
2. CQ OG55W in Tx6
3. Select a free text message in Tx6 "RC2 PSE"
4. After transmission finishes, select General message
5.QSY to label 1 Std Messages
6. Try to CQ again, but do not get Enable TX red.
7. Cl
s I do not understand any other way.
I start CQ with label 1 Tx6.
As the TX6 is not given the locator I go also to free text to give as
stations are asking it.
But I think that the problem was in Windpws update..
73 Keijo OG55W
-Alkuperäinen viesti----- From: Joe Taylor
Sent: Monday, Octob
John --
On 10/4/2018 5:23 PM, John Kludt K4SQC wrote:
In to and checked NA VHF Contest - on main page TX
2.0 NA VHF verbage appeared in Red Bar. Generated messages as
expected. TX1 grayed out. Went back to checked ARRL FD and
filled in exchange. Back on main page Red Bar TX 2.0 now read
On 10/8/2018 6:15 PM, Bill Pence KI4US wrote:
Ok. I tried some tests.
I do decode both 77 bit and old messages
I had a buddy send an old cq and 77 bit cq.
I decided both.
But I did not select the always generate 77 bit messages so I expected
to answer with the format I decoded. That was not t
A third candidate release ("RC3") of WSJT-X 2.0 is now available for
download and use by beta testers.
Changes in RC3 relative to RC2 include the following:
1 Improved SNR calculation for FT8
2 Test grid4 (not grid6) for matches in ADIF log
3 Auto-generate 77-bit messages for callsigns wi
A one-hour "practice contest" will be held next week using the FT8 mode
and the ARRL RTTY Roundup rules.
Thursday, 25 October 0200-0300 UTC (Wednesday evening, NA time)
Dial frequency 7.078 (and higher, in 2 kHz increments, if too much QRM).
Everyone works everyone.
To participate you must
Hi Glen,
On 10/17/2018 1:02 PM, Glen Brown wrote:
Joe and the Team,
It might be helpful if you clarify for everyone that the Ducie
expedition expects everyone to use 1.9.1. This is even more important
now that rc3 forces 77 bit encoding for Expedition mode.
73,
Glen W6GJB
From the "Quick-
Mike --
On 10/17/2018 5:22 PM, Black Michael via wsjt-devel wrote:
Was working a QSO...logged him during the 73 being sent from me.
He came back with another RRR and the autosequence then sent R+00
instead of 73. Had to turn off autoseq to finish the QSO.
This is another example of why we ne
Hi Attila,
A program bug causes your Tx1 message to be auto-generated incorrectly
when you double-click on a nonstandard callsign. As a temporary
work-around, when working a station such as CR140AA disable Tx1 by
double-clicking on the Tx1 button (or radio Button) first, so that you
will cal
Hi all,
According to PSK Reporter statistics, more than 650 users are busy
making QSOs with WSJT-C 2.0-RC3. This is good!
Nearly all of the early reports are related to one of two issues:
1. Some Windows users receive error messages related to downloading the
ARRL's LoTW status file. Messa
File all.txt in your log directory has a complete list of messages you
received and transmitted. If the behavior you describe is worthy of a
bug report, please document it by extracting a few lines from that file
and forwarding them to this list.
-- 73, Joe, K1JT
On 10/18/2018 4:06 P
On 10/18/2018 6:06 PM, Black Michael via wsjt-devel wrote:
Seems it's not possible to turn off 77-bit messages when Hound is selected?
As soon as I save it and come back in they're checked again.
From the Quick-Start Guide to WSJT-X 2.0:
"FT8 DXpedition Mode: Starting with release candidate RC
On 10/18/2018 6:36 PM, K5GZR - Rick wrote:
In FT8 mode, selection of any one of the ‘Special operating activity’
options causes a red background ‘flag’ to appear on the WSJT-X main
window just to the right of the large date and time box, indicating
which activity has been selected.
However,
Hi Frank,
On 10/19/2018 9:47 AM, Frank Kirschner KF6E wrote:
One thing I haven't seen discussed on this reflector is improving the
S/N by narrowing the receiver bandwidth. It is no surprise that
decreasing the bandwidth received increases the S/N, by 10 to 15 dB,
sometimes more. When I see a s
Hi Gorm,
On 10/20/2018 5:33 AM, Gorm Helt-Hansen OZ6GH wrote:
Fox - Hound mode. Qso with ZL7X.
I noticed WSJT-X had a delay when receiving answer from DX. I received a
multible callsign answer from DX. WSJT-X continued sending call. When
receiving a specific answer from DX, WSJT-X changed to
Hi Paul,
On 10/20/2018 11:04 AM, Paul Bramscher KD0KZE wrote:
Running WSJT-X 1.9.1 r8747 compiled on Debian (AMD64) Linux. A couple
days ago an operator on 20M FT8 was calling CQ 052 {his call | his
grid}. Out of curiosity I clicked his message in the band activity
pane. My radio then swit
Gorm --
On 10/21/2018 6:31 AM, Gorm Helt-Hansen OZ6GH wrote:
Hi.
WSJT-X 2.0.0.-rc3
Windows 10
When starting WSJT-X I receive the error msg:
'Error loading LotW Users Data.
Network Error - Too many redirects:
'https://lotw.arrl.org/lotw-user-activity.csv'
And no LotW colours in WSJT-X
Di
Gorm,
On 10/21/2018 1:34 PM, Gorm Helt-Hansen OZ6GH wrote:
In Fox-Hound mode I can not make 'RX all freq.' to work. Nothing is
decoded. I normal mode all seems to work.
Can you possibly imagine that we do not test any of these things ???
When you say "Nothing is decoded", I presume you mean
Hi Mark,
On 10/21/2018 2:07 PM, Mark Spencer VE7AFZ wrote:
Hi. Was running with another station on MSK144. I was in NA contest mode (but I
believe the other station wasn't as they were not calling me with my "/R" call.)
Things seemed to be working until another Station sent "TU JOHN 73" t
Tom --
Your problem has been described a number of times already on this email
list. The work-around solution is simple: run the program from a
command-prompt window.
-- 73, Joe, K1JT
On 10/22/2018 5:40 PM, Tom Harson wrote:
Hello
I am experiencing a program crash with RC3 (*This
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, 25 October 0200-0300 UTC
Dial frequency 7.078 (and higher, in 2 kHz increments, if too much QRM).
Everyone works everyone.
To partici
On 10/25/2018 8:32 AM, Joe WB9SBD wrote:
where does the exported cabrillo get saved?
Use the command "File -> Export Cabrillo log". You can save it wherever
you choose.
-- Joe, K1JT
___
wsjt-devel mailing list
wsjt-devel@lists.s
Everyone seems to have had fun exercising the RTTY RU features in
WSJT-X. I did, too, making 37 QSOs in a little over an hour using 100 W
and a dipole.
I found more things wrong than others have reported, so far. I will
document them carefully and report here more fully in a little over a
w
On 10/25/2018 9:27 AM, Joe WB8SBD wrote:
where does the exported cabrillo get saved?
Use the command "File -> Export Cabrillo log". You can save it wherever you
choose.
Thats what I thought would happen. But after the test last night I did
do that sequence, and the usual popup asking where
Hi Russ,
On 11/8/2018 7:59 PM, Russ wrote:
Hi All. Want to report some problems.Maybe they have been reported
before but it takes too long to go through all the messages on this forum.
I’m running RC3 on a windows 10 system.
1. I’m on MSK144 and have FTOL set to 200.I go to JT65 and set FTOL
Hi Dave,
On 11/9/2018 2:05 PM, David Gould wrote:
I see the following which has been has been present for some time, I
thought it might have changed in RC3 but it has not.
I am not sure it is a bug, but a design perhaps limitation.
I always have Hold TX freq checked.
When change to Hound mode
A fourth candidate release ("RC4") of WSJT-X 2.0 is now available for
download and use by beta testers.
Changes in RC4 relative to RC3 include the following:
- Fix the "cannot open file fort.81" bug
- Avoid too many redirect loops related to openSSL support
- Fix the auto-generated messag
On 11/13/2018 10:28 AM, Bob via wsjt-devel wrote:
Just downloaded the new Beta RC4 and no signals are showing decoded.
Answer?
Bob AA7CT
Please follow instructions and "Be sure to read this entire guide before
using RC4:
http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf "
Tnx Ed, that's very helpful. More will get the picture, soon.
-- 73, Joe, K1JT
On 11/13/2018 10:48 AM, Ed Wilson via wsjt-devel wrote:
Working great for me...made several contacts above 2000 Hz.
Ed, K0KC
___
wsjt-devel mailing list
wsjt-d
Thanks to all who have installed RC4, read the new Quick-Start Guide,
and proceeded to make QSOs using the new FT8 protocol.
Transition to the v2.0 protocol seems to be going smoothly. Most people
with RC4 are using the standard FT8 dial frequencies and remembering to
transmit above Tx Freq 2
Hi all,
Please read the posts by others and remember that a problem needs to be
reported only once.
You may rest assured that we already know that the state of the "Auto
Seq" box is not being remembered on program restart.
-- &3, Joe, K1JT
_
A one-hour "practice contest" will be held next week using the FT8 mode
and the ARRL RTTY Roundup rules.
Tuesday, November 20, 0200-0300 UTC (Monday evening, NA time)
Dial frequency 7.078 (and higher, in 2 kHz increments, if too much QRM).
Everyone works everyone.
To participate you must us
Hi Jim,
On 11/14/2018 12:54 AM, Jim Shorney NU0C wrote:
The only little nit I have os Operator call isn't sticky in the logging box.
Not that big a deal since I rarely do mutli-op, but I like to fill it in for
completeness if it is there and having to enter if for each QSO gets old. Am I
missin
Uwe --
On 11/14/2018 6:29 AM, DG2YCB, Uwe wrote:
*And PLEASE FIX ALL COLOR SCHEME BUGS BEFORE THE GA VERSION IS
ANNOUNCED!!! *I don’t want to be impolite, but we have been discussing
the color scheme issues at least for one and a half months now and rc4
is still full of bugs ...
There is no
Hi Svend,
On 11/14/2018 12:00 PM, Svend Aage Jessen LA6YJA wrote:
The option of LOTW is giving me an error.
I do not use LOTW. Is there an option of turning it off?
Please follow instructions in the "Quick-Start Guide to WSJT-X 2.0",
https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X
On 11/15/2018 9:17 AM, Black Michael via wsjt-devel wrote:
Was checking out the recent_calls hash and noticed this:
mskrtd.f90: recent_calls(i)(1:13)=' '
But recent_calls is char*12.
Not correct. See at top of packjt77.f90:
#
Hi Ed,
On 11/15/2018 12:48 AM, Ed Muns wrote:
Don AA5AU and I are pleased to announce the FT8 Roundup to be held on 1-2
December 2019. Rules, tutorials and other information can be found at:
https://www.rttycontesting.com/ft8-roundup/
...
One further suggestion, in addition to changing "Dec
Hi Paul,
Welcome to wsjt-devel, and thanks for the suggestion. It would not be
very difficult to implement something along these lines. We'll put it
on the ToDo list, for when time is available.
-- 73, Joe, K1JT
On 11/16/2018 7:01 AM, N1BUG wrote:
Hi,
This my first post here.
So
Hi Gary,
Thanks for the report from down under.
On 11/16/2018 3:18 AM, Gary Hinson wrote:
RC4 works down here on the Far Side, albeit upside-down.
There are not too many RC4 stations to work, yet, but enough to know it works.
I believe I've been called several times today by 75-bit users (oft
Hi Chris and all,
On 11/16/2018 10:43 AM, Chris Schulz wrote:
I just started using the RC4 this morning. I had a strong signal on the
waterfall trying to come back to me and never got a decode. So a local
ham and myself went to 10m to test this. He was running RC3 and I ran
RC4. He decoded my
Hi Paolo,
On 11/16/2018 12:16 PM, iw2etr Paolo Fiorelli IW2ETR wrote:
Hello everyone, can anyone understand why installing the rc4 I do not
receive the station? with 1.9.1 everything is ok.
We assume that people using our beta releases will read and understand
the Release Notes and Quick-Star
Hi Giuseppe
On 11/16/2018 12:38 PM, Giuseppe Molinaro KE8FT via wsjt-devel wrote:
I would like to bring to your attention that I had to reinstate version
RC3 because for some unknown reason the RX sensitivity is extremely low
when using RC4 (about 90% less station decoded as compared to version
Hi all,
Please! No need for any more comments about a 5 minute mouse-movement
timeout! This feature was never intended to be a permanent addition.
It had to do only with preventing trivial robotic use of WSJT-X during a
digi-mode contest.
Evidently it was a bad idea. Already, several days
A one-hour "practice contest" will be held tomorrow using the FT8 mode
and the ARRL RTTY Roundup rules.
Tuesday, November 20, 0200-0300 UTC (Monday evening, NA time)
Dial frequency 7.078 MHz (and higher, in 2 kHz increments, if too much
QRM). Secondary dial frequency, especially for those in
On 11/19/2018 7:16 PM, Mark Spencer VE7AFZ wrote:
I downloaded and installed a fresh copy of RC-4 onto a different computer (a
laptop running Windows 10 pro) a noticed the same behaviour.
While running FT8 if I select auto sequence and then re start the application
auto sequence is not enable
Hi Julian,
On 11/19/2018 9:46 PM, Julian VK4CMV wrote:
I've noticed that WSJT-X logging thinks it's on local time - see the
Contest Log - the QSOs do make it in Z time to my HRD log via JTAlert
though. (We are +10hrs on UTC)
There are some signals at 14.078 that I can't decode in RC4 or 1.9.1
Hi Dave and all,
On 11/20/2018 11:11 AM, David Kjellquist WB5NHL wrote:
Has anyone come up with ideas for avoiding dups when using FT8 in a
large contest? JTAlert checks B4 but its display matrix is limited and
not really designed for contest use. N1MM log integration works well but
I don't se
Hi Mike,
On 11/20/2018 11:51 AM, Black Michael via wsjt-devel wrote:
It was mentioned a while ago that changes would be made to the Fox mode
to avoid the power loss for multiple QSOs going on.
Has this been done? rc4 still points to the old DXpedition guide.
The only change made to FT8 DXpe
On 11/21/2018 12:08 AM, jarmo OH1MRR wrote:
Some months ago we said "The existing FT8 DXpedition mode will still
be supported, and a more powerful DXpedition mode may be offered as
well." We have not yet done serious work on the potentially "more
powerful mode". -- Joe, K1JT
As during VP6D, wa
Hi Gorm,
On 11/26/2018 2:10 PM, Gorm Helt-Hansen OZ6GH wrote:
Windows 10 64 bit - WSJT-X RC4.
When starting I get the error msg: Error Loading LotW Users Data Network
Error - SSL/TLS support not installed, cannot fetch:
"https://lotw.arrl.org/lotw-user-activity.csv";
This error msg came be
A fifth candidate release ("RC5") of WSJT-X 2.0 is now available for
download and use by beta testers. RC5 is stable, works well, and fixes
the known problems in RC4. It is likely that the General Availability
(GA) release of WSJT-X 2.0, scheduled for two weeks from today, will be
nearly iden
Hi all,
Another one-hour "practice contest" is scheduled for Saturday, December
1, 0200-0300 UTC (that's Friday evening, Nov 30, NA time). This session
will serve as a final tune-up opportunity for those planning to operate
in the "FT8 Roundup" on December 1-2 (more details below).
DIAL FRE
Please read the Release Notes. First item on the Help menu.
On 11/26/2018 10:13 PM, Unni Tharakkal wrote:
Hai
I tried the new RC.4 and. latest RC.5 upgrades. On both there is no RX
decode how to solve it
VU2TE
Unni
___
wsjt-devel mailing list
w
On 11/27/2018 9:54 AM, Rory Bowers wrote:
I installed rc5 this morning and ran ISCAT B on 6M. I got two calls
from my CQ. When I tried to double click on one of them the program
said "Double Click Not Available for ISCAT Mode". How do you answer a
call in ISCAT Mode??
Thanks,
Rory, K5CKS
On 11/27/2018 12:52 PM, Paul Kube K6PO wrote:
wsjt-x 2.0.0-rc5
Windows 10 Pro x64 Version10.0.17134 Build 17134
Position the mouse cursor in the waterfall window.
Right click.
A small dialog pops up announcing "Set Rx and Tx Offset".
The Rx and Tx offsets themselves are not affected.
However, t
Hi Charlie, Jari, and all,
Thanks for your reports -- they are much appreciated. I'm sure you
understand that our recent work has mostly been related to HF interests
-- in particular, the new 77-bit protocols for FT8 and MSK144, and new
special messages for contesting.
We are certainly not
On 11/27/2018 12:07 PM, Jari A wrote:
... I work several qsos with RC5 on FT8, then got silent with FT8, so I
change to JT65 as I saw traffic on it.
I also note, that after I change from JT65 to JT9, RC5 keeps tx on FT8,
even JT9 is indicated below date/ time window.
Aaah! Now I understand
Hi Steve,
Thanks for the report. You do know that ""W6XX W7WM RR73 TNX" is not a
legal FT8 message, right?
Nevertheless, the program should not crash when it's given a bad
message. This defect will be fixed in the 2.0 GA release.
-- Joe, K1JT
On 11/27/2018 2:19 PM, Steve Boone W7
Hi Eugene,
On 11/27/2018 2:26 PM, Eugene UA1NAN wrote:
Hi friends!
I can send a translation (not machine) into Russian of the article
"Quick-Start Guide to WSJT-X 2.0" from Joe Taylor, K1JT.
73, Eugene, UA1NAN.
Thanks for this offer! I will be happy to post your translation on
Hi Peter,
while reading the last batch of posts here, I noticed a reference by
another that their system appear to jump into JT9 in certain
circumstances so while pondering what is going on with my RC5 install, I
noticed the Red TX marker on the waterfall is the size I would expect
for JT9
Hi John,
Would it not be better if files were always numbered with 6 time digits insted
of a mix of 4 and 6 digits, then the list would be ordered in a squential
manner?
Possibly, but that's not the way we've done it. Labeling files with
4-digit times makes good sense for the modes with 60
Lee --
On 11/28/2018 10:27 AM, Lee. KX4TT via wsjt-devel wrote:
It also does not work well with the green highlighting for those who are
color-blind; People with either protanomaly or deuteranomaly may have
problems in this case. The result for red lettering on a green
background can be two i
ll
also
work, but rc5 is preferred since it has improvements and bug fixes beyond
rc4.)
73,
Ed W0YK
Don AA5AU
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: 26 November, 2018 13:55
To: WSJT software development
Subject: [wsjt-devel] "FT8 Roundup" mock
On 11/27/2018 10:20 AM, Rory Bowers K5CKS wrote:
Is there a chance you will change that to a double click Joe?
No. ISCAT uses free-form messages. It's totally unsuited to
double-clicking or Auto-Sequencing logic.
I think
ISCAT could be a LOT of fun. I was amazed at the sensitivity!!
I
Hi all,
I was on 40 meters for the FT8 Roundup practice session last evening (NA
time).
Operating time: 0200 to 0259 UTC
Program: WSJT-X 2.0 RC5
Dial frequency 7.080
Power: 100 Watts
Antenna: Dipole at 50 ft
I operated as a Run station, calling CQ at audio Tx frequency 1000 Hz.
There are 240
On 11/29/2018 11:03 AM, Stephen Ireland VK3VM/VK3SIR wrote:
Any chance of coordinating a better time/band for testing?
The times selected (0200 GMT) are the worst possible times for
long-haul, cross-equatorial propagation from your parts on 40m under
current solar conditions. 0500 on 20m may p
Hi Martin,
On 11/29/2018 3:44 PM, Martin Davies G0HDB wrote:
Using the 'Default' configuration in v2.0.0-rc5, I've just been invoking and
trying all the various
modes that I'm likely to use, and JT65 seems to have disappeared.
In the process of trying each mode in turn I've found that even
On 11/30/2018 10:49 AM, DAMIJAN ŠKVARČ S58G wrote:
Sorry, maybe I have overlooked in the rules: Which exact frequencies
will be used in 1-2 December Roundup?
J. Taylor wrote for mock test:
<<>>
But what about for 80, 15 and 10 M please?
Go here for FT8 Roundup Rules and related advice:
http
s little as
possible
Il 29/11/2018 22:36, Martin Davies G0HDB ha scritto:
On 29 Nov 2018 at 16:06, Joe Taylor wrote:
Hi Martin,
Thanks for your report. This bug was identified and fixed several days
ago. It will not be present in the GA release.
The workaround in the RC5 release is si
On 11/30/2018 5:06 PM, Jim Shorney NU0C wrote:
FWIW I have always used JT9+JT65 as opposed to plain JT65 mode.
So did I. Emphasis on past tense. It was convenient and did a lot to
encourage use of JT9 when it was a new mode.
Why would one not?
If one is involved in writing and maintaini
901 - 1000 of 1871 matches
Mail list logo
