Hi,
On computers with windows-xp if you leave wsjt-x active for a long time at
some point the menu disappears.He always did it also with the old versions.
I think it's a memory problem, if I turn it OFF and ON again it's normal.
I have to try what happens on the computer with Windows 7 and on the l
Hello Serge
the same thing happened to me when I wanted to call someone using the
special prefix HB90.
It seemed that I was not able to call the desired station because in
transmission another call came out.
Then I gave up but if I remember correctly all the fields from TX1 to TX5
contained the cor
Hi Bill,
Thanks for the reply. A friend sent me a link to the USKA website where they
explained to remove the auto sequence.
The article was in German and fortunately Chroma suggested to translate the
page into Italian.
It seems that by removing auto sequence it is possible to make the qso
betwee
I'm CCing the wsjt developer list so people designing
improvements to wsjt are aware of some of the issues Mac users
face running multi-digital-mode contests.
On 1/3/19 at 7:16 PM, ae...@arrl.net (Bill AE6JV) wrote:
My plan is to run in RTTY with RUMlogNG, which uses CAT to send
and receive R
Hi,
My participation in the "2230-2300 UTC, Friday, 5 January - FT8 focus"
session went very very smoothly and I was able to complete 10 QSO in little
above 30 mins on 40 m.
Some observations (all positive) :
* received one popup dialog with an "Invalid Rcvd Exch" for a station
re
Hi there
Well, It might be of help: another hash mixup issue probably. No answer
needed.
Here is the QSO
225200 0 -1.3 2868 ~ CQ JT/PD0LK
225217 Tx 2868 ~ F6BHK
225245 Tx 2868 ~ F6BHK
225300 -3 -1.3 2868 ~ F6BHK -08
225315 Tx 2868 ~ F6BHK
225330 -8 -1.3 2868 ~
On 04/01/2019 19:57, Bill Somerville wrote:
it is technically possible for two non-standard callsign stations to
have QSO using FT8 in WSJT-X v2.0.0
Hi Luigi,
I should have qualified the statement above. My example is only possible
if one of the callsigns is a compound callsign since the sugg
On 04/01/2019 20:05, nick wrote:
The User Guide says "these are built to target one contemporary
version of a Linux distribution".
Is there a note anywhere saying which Qt version has been used to
build them so that users can check that the Qt version included in
their distribution as standar
On 04/01/2019 17:30, Bill Somerville wrote:
ok, I understand now. Yes should build WSJT-X using the headers and
libraries you intend to run with.
Thank you for the comprehensive reply Bill. I will rebuild with Qt5.9.7
tomorrow.
Referring to the .deb files here...
https://physics.princeton.
On 04/01/2019 19:22, Luigi Casari wrote:
Hello to all
I am Luigi HB9CXZ, this year for the ninetieth of USKA use HB90CXZ.
I use the latest version of WSJT-X 2.0 on a computer running Windows XP.
I can not make qso with portable stations, the reports are cut both in
transmission and in reception.
Hello to all
I am Luigi HB9CXZ, this year for the ninetieth of USKA use HB90CXZ.
I use the latest version of WSJT-X 2.0 on a computer running Windows XP.
I can not make qso with portable stations, the reports are cut both in
transmission and in reception.
For example I could not make a qso with EW
Hi Bill,
Since I've been SWL only so far on FT8, I hadn't bothered to enter my
callsign or grid locator into the "station details" entry window under
"settings". Perhaps it is a coincidence, but since entering my callsign
and grid locator, the subject problem has not recurred despite letting
Hi Bill,
many thanks for pointing out my mistaking that my Ubuntu has the right qt
version.
Looks like I'll need to upgrade my Ubuntu OS.
I'm usually hesitant in upgrading because it sometimes breaks some specially built
software that needs the older libs.
73,
Paul K6WIS
Pa
I write the QST results article for the RTTY Roundup.
The article is only as good as the input I receive from all of you, the
operators that participated.
I'll be asking for your thoughts on the contest when it is over. Stories of
your trials, tribulations, and your successes and milestones. Peop
On 04/01/2019 17:51, Paul Milligan wrote:
I have all the necessary prerequisite tools and libraries installed
on my Ubuntu 14.04LTS laptop,
Hi Paul,
that is not correct, you do not have all the necessary prerequisites.
Quoted from the WSJT-X source tarball INSTALL file:
Installation
==
Been there, done that. 14.04LTS is almost end-of-life and does not meet all the
dependencies. And it likely never will. Safest answer is upgrade to 18.04LTS.
73
-Jim
NU0C
On Fri, 4 Jan 2019 09:51:03 -0800
Paul Milligan wrote:
> I'm having a problem building the latest version wsjtx-2.0.0 f
I'm having a problem building the latest version wsjtx-2.0.0 from source tarball
I have all the necessary prerequisite tools and libraries installed on my Ubuntu
14.04LTS laptop,
and I previously built wsjtx-1.9.1 from the source tarball with no problems.
But for version 2.0.0:
No problem wit
1. For an experimental works, we have been evaluating FT8 with superb results.
2. However, we want to evaluate a FASTER mode.
3. Any recommendation? Is JT9E a good choice, at 5 seconds cycle time,
instead of 15 seconds FT8?
Does JT9E mode use the same 'advanced decode technologies' as FT8?
How
On 4 Jan 2019 at 10:58, Bill Somerville wrote:
> Hi Martin,
>
> the version I tested with was a pre-release version and we may have
> fixed up the print on the status bar. Either way the result is the same
> as the first part of the message is a hash code, because WSJT-X has
> concatenated you
On 04/01/2019 15:55, nick wrote:
I did not compile Qt. I used the .run file from here...
Could it be that builds are backwards compatible but not forward
compatible with respect to Qt versions? e.g. a build using 5.8.1 would
run on say 5.5, but not on 5.9.7?
Hi Nick,
ok, I understand now.
On 04/01/2019 15:29, Richard Shaw wrote:
On Fri, Jan 4, 2019 at 9:16 AM nick wrote:
Probably a silly question, but must I rebuild wsjtx-2.0.0 from scratch
with Qt 5.9.7 for it to run using Qt5.9.7?
Wish I could tell you what the problem is but I can tell you that I build
WSJT-X for Fedora a
Forwarded Message
Subject: Re: [wsjt-devel] Qt Version
Date: Fri, 4 Jan 2019 15:55:10 +
From: nick
To: wsjt-devel@lists.sourceforge.net
I used the .run file from here
http://download.qt.io/official_releases/qt/
___
wsjt-devel m
On 04/01/2019 15:31, Bill Somerville wrote:
There may be some issues with non-standard Qt configuration on Linux
systems. On other platforms we have to generate a qt.conf to tell WSJT-X
where to find things like Qt plugins. Have you done a 'make install' on
your Qt build?
Tried QT_PLUGIN_PAT
On 04/01/2019 15:11, nick wrote:
Probably a silly question, but must I rebuild wsjtx-2.0.0 from scratch
with Qt 5.9.7 for it to run using Qt5.9.7?
Hi Nick,
I nearly missed you post, please start a new topic rather that replying
to an unrelated message and changing the subject.
There may be
On Fri, Jan 4, 2019 at 9:16 AM nick wrote:
> Probably a silly question, but must I rebuild wsjtx-2.0.0 from scratch
> with Qt 5.9.7 for it to run using Qt5.9.7?
>
Wish I could tell you what the problem is but I can tell you that I build
WSJT-X for Fedora and it works fine with Qt 5.11.1.
Thanks
/nick/Qt5.9.7/5.9.7/gcc_64/lib
QMake version 3.1
Using Qt version 5.9.7 in /home/nick/Qt5.9.7/5.9.7/gcc_64/lib
**starting wsjtx...
[20190104 14:57:18.844 GMT F] This application failed to start because
it could not find or load the Qt platform plugin "xcb"
in "".
NOAA forecasters say there is a 65% chance of G1-classgeomagnetic storms on
Jan. 5th. That's when a stream of solar wind flowing from a large hole in the
sun's atmosphere is expected to hit Earth's magnetic field.
___
wsjt-devel mailing list
wsjt-deve
On 04/01/2019 10:36, Martin Davies G0HDB wrote:
On 3 Jan 2019 at 22:11, Bill Somerville wrote:
Hi Martin,
as always with WSJT-X messages the actual message sent appears with a
yellow background in the status bar while it is being transmitted. In
this case you will see:
<...> G0HDB IO81
which
On 3 Jan 2019 at 22:11, Bill Somerville wrote:
> Hi Martin,
>
> as always with WSJT-X messages the actual message sent appears with a
> yellow background in the status bar while it is being transmitted. In
> this case you will see:
>
> <...> G0HDB IO81
>
> which is exactly how it will be deco
29 matches
Mail list logo
