George, WB5JJJ, wrote: This applies to not only WSJTx, but JTAlert (if you use it). Older versions of JTA will not function under the new decoding process of WSJTx. Currently WSJTx is v2.2.2 with

Bill, Thank you for your suggestion. I think increasing the TX percentage will work quite well for my situation. At the present time, I only have resonant antennas for three of the bands I have

Tony, you should always keep your software up to date for a myriad of reasons. Just because none of the items "fixed" apply to your operational installation does not mean there are no "under the

I am not blaming either software. I am also not ruling out hardware, or some other piece of software causing the issue, I am just looking for help in finding the issue. I come here to get assistance

Yes I agree, didn't I say I cleaned it all out and used the tar?? I only joined the group in the last few days as until now have been able to sort it all out. Mike VK8MA

Mike, the Linux package files we provide are targeting specific Linux distribution versions, if you are not running those versions you should not be trying to adjust other

On 13/07/2020 07:21, oz4gd@... wrote: Per, this issue has been raised many times here on this list, each time with the same solution being offered. 73 Bill

Here similar problems. Was running fine, tried to upgrade to the new .deb version (2.2.2) on XUbuntu 20.04 and heaps of errors. Cleared it all out using purge to start afresh and try the tar

Hi Ted, you are correct. It should be obvious that all the slots for the band hopping schedule are full so no changes are possible. If you want to add other bands then you must disable some of the

You wrote: please use the FT-857 model until the next release when the issues is resolved. That's what I am doing. I have not heard from other hams about this problem. Seems I am no alone having this

I get that WSPR is mostly popular on HF frequencies, however, myself and some others in my immediate area are using WSPR to track and try to predict openings on 6m/2m/70cm around the SE US. I was

Don't be throwing crayons. Don W4DNR

So, Loren are you blaming the WSJT software or the HRD software? It seems plausible that YOU have some hardware issue, NOT a software issue, no? 73, Ted K7TRK

On 12/07/2020 22:37, oz4gd@... wrote: Hi Per, there is a known issue with the FT-817, FT-818, and FT-897 rig models with direct CAT control in WSJT-X v2.2.2, please use the

Hamlib connection error (?): · Program version WSJT-X 2.2.2 64bit· · Operating system Windows 10 / version ”2004”· · Concise

Read fixes for upgrade. If nothing impacts your setup, then don’t install the upgrade.

Oops, sorry, forgot to change the to address...

Hi Loren, I have been using JTAlert to connect WSJTX to ACLog. What I like about it is when I click on a call in WSJTX the fields in ACLog populate and I can see if there is anything I need

Ok, you guys are missing the point here. I already said I have been doing this for years with JT65 and FT8. Just to be safe, I looked at the video and RTFM and verified what I already knew I had

I "bumped into" that video awhile back and followed the steps that Mike outlines in the video. There has been to problem here. Al - W9KXI HRD 6 Windows 7 32 bit WSJT-X 2.2.2