Rob,
There is no repo that you can just “drop and run” for WSJTX 2.2.2 – You really
need to compile your own
Go to the JTSDK @ GROUPS.IO site. I have a post there for dependencies etc.
needed to build your own WSJTX on Ubuntu 20.04.
i.e.
https://groups.io/g/JTSDK/topic/some_dependencies_
01:01, Stephen VK3SIR wrote:
Rob,
There is no repo that you can just “drop and run” for WSJTX 2.2.2 – You really
need to compile your own
Go to the JTSDK @ GROUPS.IO site. I have a post there for dependencies etc.
needed to build your own WSJTX on Ubuntu 20.04.
i.e.
https://groups.io/g/JTSDK/
that, but those instructions are not needed for users who simply want to build
the application to run. We provide a build script, and instructions to run it,
just for that sort of user.
73
Bill
G4WJS.
On 12/08/2020 01:21, Stephen VK3SIR wrote:
Bill,
KISS Principle in my answer to Rob’s post …. Y
overcoming their issues!
You can pee highest up the wall
Steve I
From: Bill Somerville
Sent: Wednesday, 12 August 2020 11:15 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Changes to the INSTALL file in the 2.2.2 tarball
On 12/08/2020 02:01, Stephen VK3SIR wrote:
Folks
Hi Folks,
I can recall in a post a couple of weeks (months???) back - that I cannot
locate - that some minor changes to WSJT-X source were required to make WSJT-X
2.2.x compile cleanly under the Qt 5.15.x Windows stream.
Before I start work on the promised updates to the Windows JTSDK 3.1 patch
ase don't over-complicate a
relatively simple recipe for building.
73
Bill
G4WJS.
On 12/08/2020 01:01, Stephen VK3SIR wrote:
Rob,
There is no repo that you can just “drop and run” for WSJTX 2.2.2 – You really
need to compile your own
Go to the JTSDK @ GROUPS.IO site. I have a post the
Ps: The fix is around 3/4 of the way to compiling your own anyway !
From: Stephen VK3SIR
Sent: Saturday, 15 August 2020 12:51 AM
To: WSJT software development
Subject: Re: [wsjt-devel] Changes to the INSTALL file in the 2.2.2 tarball
Bill,
I am off the sick list again…… Ok I am going to put
work !
On 14/08/2020 15:50, Stephen VK3SIR wrote:
Bill,
I am off the sick list again…… Ok I am going to put my “Newbie” hat on here (as
this is the type of help request that I get by PM).
* One deploys Ubuntu 20.04.1 using the software at
https://ubuntu.com/download/desktop
* You perform
Bill,
Please READ My emails …. On first reading it can appear that you have a deep
misunderstanding of Linux
* there are no issues when building from source on Ubuntu 20.04. users are
building on 20.04 and several other Linux distributions and versions with
issues.
There are no issues if y
Hi Folks,
I am unsure whether this has been reported:
30m:
055130 -11 0.2 1626 ~ CQ CO8LY FL20 Cuba
055130 -17 0.3 1342 ~ R3BV F1LYV RR73
055130 -19 0.3 618 ~ CQ DX 5CT JN0 Morocco <-- Will not allow this to
be picked this up
055200 -12 0.2 1627 ~ CQ CO8LY FL20 Cuba
No
ent: Tuesday, 18 August 2020 5:35 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX
Hi Steve
I don't think that 5CT is a valid callsign. A search on the Internet gave no
result.
73 de Michael 5p1kzx
Den 18-08-2020 k
/wsjtx-main-2.2.2.html#PROTOCOL_OVERVIEW
. Consequently, all my messages were sent as free text messages truncated at
13 characters, which is just right.
73 Frode LA6VQ
tir. 18. aug. 2020 kl. 08:11 skrev Stephen VK3SIR
mailto:vk3...@hotmail.com>>:
Hi Folks,
I am unsure whether this has been rep
development
Subject: Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX
Hi,
Nothing wrong with a call ;)
It is F5CT in JN08.
He probably messed up his setup in WSJT-X or any other similar problem.
Best regards and RR73 9A5CW
uto, 18. kol 2020. 10:05 Stephen VK3SIR
2020 at 2:41 PM +0200, "Stephen VK3SIR"
mailto:vk3...@hotmail.com>> wrote:
Patrick,
* It is F5CT in JN08.
Great detective work… and WSJT-X working as it should by blocking an invalid
from being responded to !
73
Steve I
VK3VM / VK3SIR
[ Ps: Sorry I almost missed t
decodes are not false, it is the operator fault who did make a mistake.
It does happens ;) (leadings space, non supported character, etc..)
There is no software on the market which is not Lidsproof ;) joke
Wish you all the best,
73 Patrik 9A5CW
uto, 18. kol 2020. 16:21 Stephen VK3
Frode and The Community-at-large,
Yes its invalid – the discussion has clearly identified that and I suspected
that at the first post. The community has done a great job in clarifying this
not only just for me but also lots of others.
No more discussion needed on that subject of the callsign va
Frode,
All is extremely good and productive; it has been an invigorating and
enlightening discussion. Most of the discussion has been within the Spirit of
HAM – Help All Mankind. ☺
All I have done is have a look at code … and taken a brief look “into the
crystal ball” knowing that “to every ac
Claude,
Excellent suggestion. Your method set here at the point of display is the most
efficient and generalist - but will prevent some non-standard but valid calls
getting through. That will help me with some other projects I am working on so
I cannot thank you enough ! For this project, memor
gt;>
Sent: 19 August 2020 20:36
To: WSJT software development
mailto:wsjt-devel@lists.sourceforge.net>>
Subject: Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX
I find the discussion interesting.
73, Carey,
Hi Folks,
As many are aware “patches” that make the Windows JTSDK 3.1 x64 operate
basically to the same processes and procedures that the well-established JTSDK
3.0 x86 operates to/under have been released to the JTSDK @ GROUPS.IO (i.e.
https://groups.io/g/JTSDK/topics ) JTSDK Tech Group.
I st
Hi Core Developer Team,
For some time now I have been seeking guidance with patches for the Windows
JTSDK 3.1 x64 with respect to upgrading Windows CMAKE to a more contemporary
version found on many Linux distros (i.e. v3.14.4 is delivered in Greg KI7MT’s
original files; v3.18.2 is the current
*** REPOST – WRONG HEADING ***
Hi Core Developer Team,
For some time now I have been seeking guidance with patches for the Windows
JTSDK 3.1 x64 with respect to upgrading Windows CMAKE to a more contemporary
version found on many Linux distros (i.e. v3.14.4 is delivered in Greg KI7MT’s
origina
).
While we can work around issues at our end this can create cross-platform
portability concerns and unnecessary complexity.
It may require push from “our mountain” to move “their mountain”… Only our Core
Development Team has the credibility to report matters – if they exist.
From: Stephen
ake script we use to cater for the rather outdated
file naming used by the FFTW3 packaging.
73
Bill
G4WJS.
On 22/08/2020 11:14, Stephen VK3SIR wrote:
Postscript:
The issue may not be anything to do with WSJT-X nor its Makefile construction …
but could possibly be an unnoticed “inconsistency” p
Bill,
The matters raised are FAR FROM TRIVIAL as the JTSDK’s must be tolerant and
resilient to library and Qt version upgrades. Guidance now exists in that
additional variables for special-purpose scripts (such as jtbuild) will now be
incorporated into to scripts to handle FFTW and CMAKE’s intr
Bill,
* Instead you choose to write long rants about the incompetence of the
WSJT-X development team..
Long “rants” … People also said that of Washington, Adams, Franklin and
Jefferson’s speeches and dispatches (and I am not in their league)….
I asked for assistance time and time again on
:35 PM, Stephen VK3SIR
mailto:vk3...@hotmail.com>> wrote:
Bill,
* Instead you choose to write long rants about the incompetence of the
WSJT-X development team..
Long “rants” … People also said that of Washington, Adams, Franklin and
Jefferson’s speeches and dispatches (and I am not
Neil is right,
Everyone please take the time to read this … and carefully … verbosity hones in
on precision… and its lack of reading that has cause this situation.
It is most definitely time to “give it a rest” as where things are headed has
now become abusive and divisive … But these final com
Gee: Grammar revisions warranted for clarity … Apology for the “further
correspondence” but its necessary on re-reading this for the 50th time !
..
Neil is right,
Everyone please take the time to read this … and carefully … verbosity hones in
on precision… and its lack of reading that
Hi Gents,
As a suggestion is it possible to direct the installer scripts on a Windows
build to auto-deploy the Appropriate Win32 or Win64 OpenSSL Lite package?
Should the SDK's and package requirements be looked at with regards to
providing access to these libraries available for the future?
I
Hi Folks,
Does the "Allow Tx Frequency Changes While Transmitting" (File/Settings/General
Tab) when not-checked function as intended?
My expectation would be that if disabled that any frequency changes observed in
the Tx spin-box widget on the Main Window should be delayed until the end of
the
Joe,
Thanks for the clarification. Also thanks for the notification for us all in
posts to others that rc2 is imminent.
Thanks also for the reminder to everyone participating that we should head to
the documentation before posting. I was aware of the documentation having been
there first befor
Joe and the Core Development Team,
Test environ: The Main FT-991 connected to a 80m Doublet (v2.2 rc1); Second
environ is a FT-897D with SCU-17 into a dummy load (v2.1.2). Test band is 20m.
I can confirm as that on FT8 transmissions that frequency changes on Tx are
blocked.
But...
Yet the T
Ps: The JPEG's supplied show changes in Tx frequency when the "Tx spinner-box"
widget has its "up" control selected while transmitting !
-Original Message-
From: Stephen VK3SIR
Sent: Thursday, 21 May 2020 7:24 AM
To: WSJT software development
Subject: R
Ed,
There is a strange anomaly that makes no sense yet many of us that (especially)
work weak DX observe frequently ... Sometimes when you end up in a R -XX/RR73
loop ("RR/73 loop" or "ACK dance" as you term it) with a station anecdotally
and observationally sometimes sending 73 sequences back
Hi Michelle,
By far the best way to avoid duplicates in logs is to not set
"Settings\Reporting\ Log automatically..." . If you come back with a RR73, auto
log, and then a station comes back with a R-XX (what I term a "RR/73 Loop")
then both communication and logging can lead to duplicates in lo
;s" function to "Export standard ADIF"
back to the "wsjtx_log.adi" file (found in the location accessible by
"File/Open Log Directory"). DXKeeper has great tools
for managing duplicates. When all duplicates are removed periodically write
them back to WSJT-X ove
Core Development Team,
Very well done. The wsjt-x source compiles beautifully with the JTSDK 3.1 x64
bit (with 0.35b patches applied to make it work).Some of our community have
noted issues getting access to the "jt...@groups.io" site so email me if you
need these.
Only one "warning" noted in
Folks,
Around 8 intermittent QSO's on 17m FT8 so far (with the odd set of QSO's that
follow on). No issues observed with Windows-10-built FT8 operation so far !
My operational environ is Windows 10 Pro Windows 1909 X64 (no virtualisation -
fully updated) on an early 2012 Mac Mini i5 running wi
Folks,
I just picked up a false decode that can be replicated when played back
through WSJT-X 2.2.0 rc2:
104945 -23 -0.5 1623 ~ VK3VM FH9ZZV/R ND49 ? a2
Research suggests this is not a genuine call and is definitely a false decode
(i.e. ND49 = middle of Southern Ocean). I hav
73
Steve I
VK3VM / VK3SIR
-Original Message-
From: Bill Somerville
Sent: Monday, 25 May 2020 9:43 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 2.2.0-rc2 False Decode
On 25/05/2020 12:04, Stephen VK3SIR wrote:
> Folks,
>
> I just picked up a fa
ry to reproduce them, are welcome but unless there is common cause that
can be detected by the application, like unrealistically low SNR values
combined with marginal sync detection and maximum FEC required, there's little
that can be done.
73
Bill
G4WJS.
On 25/05/2020 12:54, Stephen
Bill and Joe,
As a summary for readers I have identified that MANY false decodes being
observed were observed ESPECIALLY using the “flipping” of the bits that results
in a /R. Subsequently there has also been a bit of chatter re field days etc.
and the use of non-standard suffixes even in the f
HiFolks,
There seems to be some strong evidence mounting regarding non-standard suffix
usage – in particular /R …
Remember that we should be using Save/Save Decoded so that these can be emailed
on request to The Core Development Team when discovered !
73
Steve I
VK3VM/VK3SIR
From: Allan VK4
Joe,
Thanks for the clarification on the supply of "false decode" recordings. There
are multiple posts that many of us see and have requesting such files, so
further direction has been appreciated I am sure by us all.
Firstly, I assume that no mitigation strategies for false decodes are planned
Joe, Bill and Steve,
A great job with rc3 ! It compiles almost without message under the Windows 3.1
x64 JTSDK. I have yet to test it with the Ubuntu 20.04 LTE release yet.
Also I note the comments regarding releasing code under Qt 5.12.8 - required
due to Mac-deployment issues. Qt 5.12.8 is t
David,
It’s a good reminder for us all... New software versions (and especially
JT-software) should start with a fresh, clean wsjtx.ini file. Yes we get used
to our screen settings etc... but once the new "default" wsjtx.ini file is in
place we can cut and paste across identical settings as lon
Bill,
Thanks for the comments ... still working here on a Ubuntu 20.04 release
> Note that the LTS releases of Qt have little bearing on Qt open source users
> since for them support always ends at the date of the next release.
All Noted and :-)
BUT we are aware of some grief across toolk
Joe,
The advice that you have issued is against what any academic or trade educator
would EVER recommend as sound practise to our trainees / clients / researchers
etc.
One always starts with a clean slate and then introduces changes - especially
when testing and evaluating. That is "Scientifi
Hi Folks,
The FT-991 now works with WSJTX 2.2.0 with Mike and Nate's latest patches. I
have not fully tested split modes etc. yet though !
I have also a background report, based off my compile, that FT-891 now works.
Some will not directly post here.
Perhaps current packaged releases should be
Bill,
* please do not redistribute WSJT-X, that is in breach of our copyright.
Now where on Earth did you get that idea from and where has this come from
???
Can you please provide a link to code that I have distributed?
Here again is my post:
* Hi Folks,
* The
Bill,
> you stated the above, that is indirect evidence that you have distributed a
> binary version of WSJT-X.
Indirect evidence - h ... Assumptions. Reminds me of Fleishman, Pons and
their "Cold Fusion" ...
Fact: The reference to the 891 refers to equipment at an alternate site listed
Hi Folks,
Interesting discussion. Peter’s overview is 100% correct. Philip (PSKReporter’s
maintainer) states that his resource should only offer a “guide” and I must
also highlight that.
TCP should be perhaps only used in the exception and only if uploads to
PSKreporter are observed to not reg
Marco,
What OS, Version and Qt version are you using? Is your OS fully updated? Are
all required dependencies required to build WSJT-X as described in the WSJT-X
INSTALL and README files deployed? Are you following the instructions to
compile WSJT-X as described in the WSJT-X INSTALL file?
I r
Bill,
(From the next release forward) Is it possible to update the “makefile”
sections used to build a packaged Windows version to force an uninstall of any
previously installed WSJTX version before continuing the install?
As WSJTX installs into the same location with every packaged install use
Bill,
Ø we don't do that because users often want to install multiple versions,
particularly with RC releases where we recommend just that.
I will have to correct your “often” to “very occasionally”… although many like
me at the moment are using 2.2.1 and 2.2.2 in parallel !
Ø So it's a
Terry,
Matters around TCP spotting has been raised a number of times (and I note a
subsequent response from Robert AD6I).
Terry - as Bill raises - JTAlert is by FAR the most advanced tool that has the
"potential" ... yet at the moment lacks "capability".
[ Laurie VK3AMA also runs his own "sp
Dave,
Sorry I have to step in here.
> Seriously, I do think Ham Radio software does need to adopt some modern
> architecture principles.
ABSOLUTE GARBAGE in my opinion ... that attitude puts Amateur Radio and its
people back into the stone age
You move away from standards you get uncon
My sincerest apology Dave !
No it was not directed at you !
I failed at multitasking here !
-Original Message-
From: Dave AA6YQ
Sent: Tuesday, 30 June 2020 3:11 PM
To: 'WSJT software development'
Subject: Re: [wsjt-devel] Request for WSJT-X Feature
+ AA6YQ comments below
On the
T E S T of a new system
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Mike,
I tried pretty much all angles – including two reloads of the old iMac 5,1 with
Ubuntu 20.04 and the Full “apt” deployed Qt 5.12.8 toolchain ! …. It won’t
drive the FT-897D directly on that !
Yet all works PERFECTLY and as expected in a VMware Workstation 15.5.6 VM …
The anomaly is that
Testing systems yet again; upstream proxy and caching issues under diagnosis.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Claude,
There issues in some cases are wide and various but based primarily around some
"byte dropouts" and acknowledgement-of-commands.
As an example, an issue that is currently being investigated relates to
acknowledgement of commands (i.e. intermittently 3 bytes returned rather than
the ex
Ps:
> Also for the core developers: For the next source release, can the INSTALL
> files
> packaged at the top level of the tarball/within the "wsjtx.tar" tarball also
> be made
> consistent across the entire package i.e. update/incorporate the changes in
> the
> WSJT-X Linux build script sh
o: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] FW: CAT problems with FT817, FT857 and FT897
On 7/2/20 11:25 AM, Stephen VK3SIR wrote:
Many thanks, Stephen, for this very interesting information and for your tips.
> i.e. sudo usermod -a G adm,tty,disk,dialout,audio,video,plugdev
In my
ucp', just look at which group
devices are in to determine which group you need to be a member of.
73
Bill
G4WJS.
On 02/07/2020 11:17, Stephen VK3SIR wrote:
Clause,
A minor correction here: its -G
i.e. sudo usermod -a -G adm,tty,disk,dialout,audio,video,plugdev
There is a little "
Jim,
A very appropriate comment based on some email chats here going on in the
background. Background discussion that I have been having relates around the
"standards" discussion opened earlier in the week and the necessity in this
modern day and age for standards with so many new manufacturer
[ I'll resend this as its not flowed through (Which has resulted in some
testing of late) ]
Jim,
A very appropriate comment based on some email chats here going on in the
background. Background discussion that I have been having relates around the
"standards" discussion opened earlier in the
Hi Everyone,
Is anyone observing possible issues when the Linux xorgxrdp packages are
deployed?
[ Note here I am testing with FT-897D, SCU-17, Ubuntu 20.04 x64 on an old
32-bit EFI iMac With WSJTX 2.2.2 and “Master” repositorty Hamlib ]
Hardware and “basic OS incompatibilities” are eliminated
Bill,
A couple of weeks back you provided some guidance as to necessary changes to
the Makefiles needed to build WSJTX 2.2.1 (I think it was) under the Qt 5.15.x
stream.
Qt 5.15.1 is not far away.
Has WSJTX 2.2.2(+) source been made Qt 5.15.x friendly?
If not can you please re-post that
Hi Everyone,
I have noted that when you select a frequency to operate on that hardware is
not capable of then a Hamlib disconnect (i.e. The Settings/Radio configuration
widgets) is thrown without any console error messages being recorded.
i.e. I run a FT-897D and an old IC-725 here… With either
frequency ranges trying to be addressed and the handling of such anomalies #bug
On 13/07/2020 10:01, Stephen VK3SIR wrote:
Hi Everyone,
I have noted that when you select a frequency to operate on that hardware is
not capable of then a Hamlib disconnect (i.e. The Settings/Radio configuration
widgets) is
Group Moderators,
I did not receive this email; such information is rather critical for work that
I perform for the community on the JTSDK in the absence of the main convenors.
No the message is not in SPAM folders … This is a “Hotmail” account so there
are not issues there.
Can you please ens
Folks,
I am only responding here as I have had a few emails in the background ... and
I put this out there to guide learning for some... for many this will be old
hat news !
There has been a lot of work take place with Hamlib since R 2.2.2 was released.
WSJTX relies heavily on Hamlib.
The pac
JTSDK 3.1 x64 Patches: Preparation for
imminent release of Qt 5.15.1
Hi Steve,
I have not yet upgraded to 5.15. It is interesting.
I noticed that "setqtver.cmd" of 0.4a is something wrong and the content is for
"build-hamlib.sh".
73 Yukio
JG1APX
On Thu, 20 Aug 2020 01:28:34
75 matches
Mail list logo
