Thanks Bill. Downloaded, installed, problem fixed.
73 – Ron – KE7RON
From: Bill Pence
Sent: Wednesday, October 17, 2018 7:52 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Error Loading LotW Users Data
I pulled this from a diff thread.
It's been discussed separately
T
> On Oct 15, 2018, at 15:57, Tom Melvin wrote:
>
> Would it not just be easier to Un-Tick the ‘Double Click on call sets TX
> Enable’ in Settings - you can click to your hearts content, do the DX
> lookup, play with QRZ etc.
And then it wouldn’t respond with double click when you want it t
Ted
The ~ is used to say what mode you are in ~=FT8, #=JT64 etc.
The list of options is covered in section 12.2 of the manual
Tom
GM8MJV
On 19 Oct 2018, at 01:25, Ted Gisske wrote:
> More importantly…Leave the colors to something that can be uniquely defined.
> LoTW yes/no is important in a
To summarize what you saw it appears V31MA was running in Fox mode but you
weren't in Hound mode.
So at 122930 he sent you RR73 and he was done with you and moved on.
Everything past that is him talking to somebody else as your call never shows
up again in his tranmissions.
de Mike W9MDB
122830
Sorry I'm late to the party on this one. Regarding item 1, I went back to
see where I had OpenSSL installed, and as Bill said previously in another
thread, I've got it all over the place:
C:\Users\david>where libeay32.dll
c:\Program Files (x86)\Intel\iCLS Client\libeay32.dll
c:\Program Files\Intel
I don't know if this is the right reflector for this question, but I need
some help getting WSJT-X v.1.9 transmitting again.
It was working fine this afternoon. When I returned to the rig after
dinner, WSJT-X would no longer transmit. It was receiving and decoding.
This has happened before, and cl
Just as a point of interest there is some VHF weak signal activity during field
day in the Pacific North West. While I have never tried to run meteor scatter
during field day it wouldn't surprise me if some one tried this at some point.
Also in Canada I can't see any legal reason why I cou
Joe,
Thanks for the quick response.
I did leave out one fact, which is: In MSK144 mode, selection of ARRL Field
Day or ARRL RTTY Roundup causes the message texts to change to the formats
appropriate to those contests.(But it does not show the red 'flag'
message.)
So my note was really to repor
More importantly…Leave the colors to something that can be uniquely defined.
LoTW yes/no is important in a number of other categories, so muddies the water
if it is just assigned to a color. Perhaps replacing the “~” in the decode with
a L would work. I cannot figure out what the tilde does othe
I agree, the colors are becoming so ubiquitous, that they end up diguising
as much as they highlight.
Some color is good, a lot of color can be overwhelming. I like a simple L
for LoTW user. Save the colors for things more dramatic that require
immediate notice like CQ, and My call
Hasan
On Th
The work-around functions correctly on my MacBook Pro. The JT-Bridge initiated
calls also began to function again.
Thanks and 73 John NU8M
> On Oct 17, 2018, at 15:15, Leo Bally wrote:
>
> Plan B should be now activated
> Several crashes are reported
> Fall back software must be activated now
I finally found it.
Strange ?
Running Windows 10 Pro latest version
I am not a computer geru so I don't know if it is my problem or a software
problem.
73 Maurice
PS I like the sensitivity of the decodes.
122830 -9 0.5 694 ~ CQ V31MA EK58
122830 -7 0.2 811 ~ DE KH6KG/W5 73
122830 -8
Is there a guide somewhere which outlines the proper process for building
the windows binary from source?
I downloaded the source, did a "cmake -S d:\mysoucedir -B d:\mybuilddir",
loaded the resulting "wsjtx-superbuild.sln" in VS 2017, performed a build,
and... no errors, but no binary either... S
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,
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,
In MSK144 mode, the red background 'flag' appear
Am I the only one that can not set the foreground color in anything
other LOTW?
I set the foreground color of "CQ in message" to blue:
View color highlighting scheme shows the blue text.
Text is still black in "Band Activity" panel.
RC3 - Ubuntu 18.04 AMD64
djb
Hi all,
Ubuntu 18.04 amd64 WSJTX V2.0.0-rc3 8a1244
Working Japan FT8 160m split 1840 kHz Tx / 1908 kHz Rx. (Split operation
set to 'none' in Settings/Radio for this configuration.)
While calling with a directional CQ (CQ JA G4DYA IO82) entered into the
Free msg box on Tab 2, Auto seq / Call 1st
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 Oct 18, 2018, at 5: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.
Mike,
You are correct. This is what was intended. Fox and Hound use only 77-bit
m
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.
de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listi
With the past few WSJT-X release candidates there have been a number of
concerns expressed about the use of colored letters over various colored
backgrounds to indicate decoded stations that use LOTW. In addition to the
visibility issues, the user now has to remember the meanings of the various
col
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
I had the same problem yesterday??
I didn't document it though as I thought it might have been my problem.
Running Windows 10 pro 1803
WA6PHR
-Original Message-
From: Dave J Barnes
Sent: Thursday, October 18, 2018 1:06 PM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] Weird
Many thanks, Joe! Installed SSL fix, then -RC3. Upload to LOTW was fine.
On another topic: Thanks for the change in frequency-swap arrows that came out
in -RC2. Much clearer now.
73,
Andrew Ellis NO6E
Sent from BlueMail
On Oct 18, 2018, 11:04, at 11:04, Joe Taylor wrote:
>Hi all,
>
>Accord
Station A called CQ
I answered Station A with my call and grid
Station A sends report
I send station A my R+ report
below messages decoded together at same time on same frequency
Apparently another station, B, was in contact with A previously -
Station B sends station A 73 message
St
On 18/10/2018 19:02, Joe Taylor wrote:
3. A few people have complained that color-highlighting does not work
as expected. Most of these can be traced back to not having used the
available configuration options.
Hi Joe,
there is a defect in the new DXCC highlighting that means they are not
m
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
Hi:
I have switched my home VHF station over to the latest RC version of WSJT-X. I
am hoping to be able to test the NA VHF contest and rover functionally over the
next few weeks.
I typically leave the station running and monitoring 144.174 using FT8 and
beaming towards the PNW from CN89 and fe
On 18/10/2018 16:04, Black Michael via wsjt-devel wrote:
Small omission in the RC3 online docs
|--config |
and
wsjtx --config FT8
wsjtx -c Echo
Should be
|--config=|
wsjtx --config=FT8
wsjtx -c Echo
de Mike W9MDB
Hi Mike,
that works ok for me, long option names can be separated from their
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
Small omission in the RC3 online docs
--config
and
wsjtx --config FT8
wsjtx -c Echo
Should be--config=
wsjtx --config=FT8
wsjtx -c Echo
de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listi
Special callsigns don't work in RC3known limitation.
de Mike W9MDB
On Thursday, October 18, 2018, 9:43:26 AM CDT, Attila Kocis
wrote:
Hi
Using RC3 on Win10 Pro x64 v1803
CR140AA calling CQ in 77 bit mode.
My Settings: 77bit tx and rx checked.
When I try to c
Hi
Using RC3 on Win10 Pro x64 v1803
CR140AA calling CQ in 77 bit mode.
My Settings: 77bit tx and rx checked.
When I try to call him, it cuts my callsign DL1NUX tu DL1NU
So I quit calling him, because „DL1NU“ also exists 😊
[cid:image001.png@01D46700.8EE043B0]
[cid:image002.png@01D4670
The sequence was a standard QSO.
When I sent the 73 I logged the QSO immediately.
He sent another RRR and the autosequence chose TX 3 to respond. I had not
moved to another QSO...was still on him.It appears to be caused by the reset of
m_QSOProgress here:
bool b=(m_mode=="FT8") and ui->cbAut
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
Option 4 fixed the problem. Thanks for the quick response.
73
Jim Parks NY0J
From: Black Michael via wsjt-devel
Sent: Thursday, October 18, 2018 6:54 AM
To: WSJT software development
Cc: Black Michael
Subject: Re: [wsjt-devel] WSJT-X 2.0.0-rc3 LOTW error
Already answered...solut
Already answered...solution here.
https://sourceforge.net/p/wsjt/mailman/message/36443778/
de Mike W9MDB
On Thursday, October 18, 2018, 1:29:04 AM CDT, David Kjellquist
wrote:
Loaded up rc3
I'm getting an error window on startup Error Loading LOTW user
data Too many red
Sorry there was a typo. I meant of course “Worked B4 instead of New Call?”
instead of Worked B4 instead of New Band?
As reported by several OMs New Call (and also New Call on Band) is not properly
working. Only a small portion of “New Calls” are colored as they should. In
addition to tha
As reported by several OMs New Call (and also New Call on Band) is not properly
working. Only a small portion of “New Calls” are colored as they should. In
addition to that, I see the general problem, that a “New Call” in many cases is
also a “New Grid” or even a “New DXCC”.
To overcome the
The same here at my PC (Windows 10, 64bit, all latest updates). New Calls are
only colored blue in roughly 10 % where it should be colored blue.
My proposal on that: Instead of “New Call” (or “New Call on Band”) call it
“Worked B4” (or “Worked B4 on Band”) and color it grey (as it is in JTAle
40 matches
Mail list logo
