Date   

locked #Install #BugReport #WSJTX_config WSJT-X not working after 2.3.0 install #install #IssueReport #WSJTX_config

Jim Pruitt
 

I was decoding using WSJT-X 2.2.2 (64 bit) and today I installed the newest 2.3.0 (64 bit)  When I did WSJTX stopped working.  The waterfall is totally blank (not a single signal showing up despite LOTS of activity on the frequency.  Looking at the configuration had the Audio Soundcard input first as Default device Not found and then it showed it as blank and now it is back to not found. The USB sound card dongle was working with 2.2.2 but is not even seen by 2.3.0 and the dongle is flashing with the audio input.  How do I get it working?  Or should I just re install 2.2.2?

Thank you.

Jim Pruitt
WA7DUY


locked Re: WSJTX Install Fail on Pi64bit #install #linux #IssueReport

Bill Somerville
 

On 03/02/2021 19:56, Ken Hendrickson wrote:
Fails to install on Raspberry Pi 4 with Ubuntu installed - 64 bit version downloaded from Ubuntu website.
See attached messages.

wsjtxerror.png

wsjtxinstallerror.png

Hi Ken,

the 64-bit ARM Debian package was built on the Raspberry Pi OS beta 64-bit operating system release, it certainly installs and runs on that. I'm not sure what it is trying to write to /usr/share/appdata. The unmet dependencies is just a case of needing to install the prerequisite package dependencies. As always, if the provided package does not install you can build WSJT-X from sources.

73
Bill
G4WJS.


locked Re: Multiple Instances of WSJTX .. #FT8 #WSJTX_config

Bill Somerville
 

On 03/02/2021 22:10, Dave H wrote:

Hello,

I want to run multiple Instances of WSJTX, I found that I need to create 2 shortcuts with the following added

wsjtx --rig-name=FT-991 

wsjtx --rig-name=FT-891 

What I'm not clear on.? Will I end up with "2" wsjt-x adi files or is there a single shared file.

Just trying to think ahead for getting wsjt-x to Log into Log4OM

Thanks...

Hi Dave,

two separate log files, although you can make them use a single file using a symlink (use a hard link on MS Windows), with some minor restrictions on highlighting of stations worked before.

73
Bill
G4WJS.


locked Multiple Instances of WSJTX .. #FT8 #WSJTX_config

Dave H
 

Hello,

I want to run multiple Instances of WSJTX, I found that I need to create 2 shortcuts with the following added

wsjtx --rig-name=FT-991 

wsjtx --rig-name=FT-891 

What I'm not clear on.? Will I end up with "2" wsjt-x adi files or is there a single shared file.

Just trying to think ahead for getting wsjt-x to Log into Log4OM

Thanks...


locked WSJTX Install Fail on Pi64bit #install #linux #IssueReport

Ken Hendrickson
 

Fails to install on Raspberry Pi 4 with Ubuntu installed - 64 bit version downloaded from Ubuntu website.
See attached messages.


locked Re: #logging #logging

 

Only if they’re a member of the ADIF group. If they’re not why not?

 

Phil GM3ZZA

 

Sent from Mail for Windows 10

 

From: David Ackrill
Sent: 03 February 2021 18:42
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] #logging

 

Thanks Neil,

Does that mean an update to ADIF will be available to logging programs as well?  If so, I'll email the guy who wrote the one I use and see if he has been able to get an update.

Cheers - Dave (G0DJA)

 


--
73 Phil GM3ZZA


locked Re: Automatic power up of rig #WSJTX_config

David Ross
 

Hi Bill I have been away just back
I have attached the wsjtx log file as requested 
My radio is the Yaesu FTDX101MP
David 


locked Re: #WSJTX_config #WSJTX_config

Monty Wilson, NR0A
 

Neil,

My message was a little long with lots of parts. But since the problem is now loss of then connection between WSJT-X and JTALERT I don’t see what the new database in HRD has to do with my issue. 

I do have a problem with logs getting to HRD from JTALERT. However until I can get data to JTALERT the HRD issue is immaterial. 



Monty Wilson

On Feb 3, 2021, at 1:29 AM, neil_zampella <neilz@...> wrote:



FWIW ... the answer can be found on the JT-Alert groups.io support group, not here as it really does not pertain to WSJT-X other than it originates the Log UDP message.

Apparently, the answer is to create a NEW database in HRD, and import your log from the old DB.   When you do that DO NOT create an access database, create one in Maria DB.   For two reasons, its a real SQL database, and it can handle many more records.

You can find out more about this on the hamapps.groups.io support list.

Neil, KN3ILZ

On 2/2/2021 10:13 PM, Monty Wilson wrote:

Yesterday, I downloaded and successfully loaded WSJT-X V 2.3.0.  On my first try I did not have a connection to JTALERT.  I was told about the new loopback option and once set, WSJT-X was communicating with JTALERT.  I was able to interact with calls on JTALERT and make contacts without any issues.  However, I found that JTALERT would not write logs to my local HRD log.

 

I spent this morning troubleshooting that issue without success and eventually shut everything down to take a lunch break.

 

I think started my HRD (version) 6.7.0.323, followed by WSJT-X (version 2.3.0) and then JTALERT (V 2.16.17).  For unknown reasons, I have now lost the link between WSJT-X and JTALERT. 

 

I have checked the settings in WSJT-X (I use multicast) and JTALERT.  All of the settings look correct.  The only error message I see is

 

Unable to communicate with the WSJT-X process.

  UDP Port : 2333

  IP Address : 239.255.0.0

  Values read from WSJT-X config file...

    C:\Users\jwils\AppData\Local\WSJT-X\WSJT-X.ini

 

WSJT-X Detected Instance...

  Process Window Title : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN

  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"

 

Decode alerts and logging will be unavailable until corrected.

 

JTALERT about shows:

 

JTAlert Instance      : #1

JTAlert Start Params  : /wsjtx

WSJT-X Window Title   : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN

WSJT-X Command Line   : "C:\WSJT\wsjtx\bin\wsjtx.exe"

WSJT-X   --rig-name   :

WSJT-X Config File    : C:\Users\jwils\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Version               :

WSJT-X Revision              :

WSJT-X Spec Op Mode          : None

WSJT-X UDP ID                :

WSJT-X UDP Port              : 2333

WSJT-X UDP Server            : 239.255.0.0

WSJT-X UDP MCast on Loopback : True

WSJT-X UDP Max Schema        :

 

==================================================

UDP Ports used

--------------------------------------------------

JTAlert.exe           : 54408 65471

JTAlertV2.Manager.exe : 62581 62582

JTAlertV2.Decodes.exe :

 

In background, I have been running 2.2.2 since it was released.  I was successful in connecting to JTALERT and JTALERT to HRD for logging.  For some reason, since I loaded 2.3.0 I have had problems with the connections.

 

I don’t know where to look to troubleshoot.  All of the configuration points (as far as I know) are set the same as 2.2.2 with the exception of the new Loopback field.  I am looking for ideas.

 

I may try to revert back to 2.2.2 to see if that will get me started again.

 

Thanks in advance

 

Monty, NR0A

jwilson16@...

 







locked Re: Version 2.3.0 64 bit will not install #install

neil_zampella <neilz@...>
 

What are you using for an antivirus?   Are you sure you're getting a good download? 

Neil, KN3ILZ

On 2/3/2021 12:14 PM, William Perry wrote:

I can’t install 2.3 either on Windows 10
N3VEZ 

On Wednesday, February 3, 2021, Gary Liebisch <glieb01@...> wrote:
I have instead found a copy of 2.2.1 and it installs fine. No uninstall. So I went from 2.1.2 to 2.2.1 without issue, then I tried 2.3.0 again with a fresh download and it still fails to do anything. So obviously there is something different about the 2.3.0 install.  I am going to sit this one out, satisfied for the time being with 2.2.1 and perhaps try again at later date. Perhaps someone else will find and contribute to a solution. Thanks.
--
Gary Liebisch
W8GEL
Powell, OH




locked Re: #logging #logging

David Ackrill
 

Thanks Neil,

Does that mean an update to ADIF will be available to logging programs as well?  If so, I'll email the guy who wrote the one I use and see if he has been able to get an update.

Cheers - Dave (G0DJA)


locked Re: Version 2.3.0 64 bit will not install #install

Bob Lewis
 

My Norton antivirus blocked it as “too new” and a potential threat. I just selected “install anyway” and it installed and runs fine on Windows 10. This is pretty safe if you know that you have downloaded it directly from the WSJT web site.

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of William Perry
Sent: Wednesday, February 03, 2021 1:15 PM
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] Version 2.3.0 64 bit will not install #install

 

I can’t install 2.3 either on Windows 10

N3VEZ 

On Wednesday, February 3, 2021, Gary Liebisch <glieb01@...> wrote:

I have instead found a copy of 2.2.1 and it installs fine. No uninstall. So I went from 2.1.2 to 2.2.1 without issue, then I tried 2.3.0 again with a fresh download and it still fails to do anything. So obviously there is something different about the 2.3.0 install.  I am going to sit this one out, satisfied for the time being with 2.2.1 and perhaps try again at later date. Perhaps someone else will find and contribute to a solution. Thanks.
--
Gary Liebisch
W8GEL
Powell, OH


locked Re: Version 2.3.0 64 bit will not install #install

William Perry
 

I can’t install 2.3 either on Windows 10
N3VEZ 


On Wednesday, February 3, 2021, Gary Liebisch <glieb01@...> wrote:
I have instead found a copy of 2.2.1 and it installs fine. No uninstall. So I went from 2.1.2 to 2.2.1 without issue, then I tried 2.3.0 again with a fresh download and it still fails to do anything. So obviously there is something different about the 2.3.0 install.  I am going to sit this one out, satisfied for the time being with 2.2.1 and perhaps try again at later date. Perhaps someone else will find and contribute to a solution. Thanks.
--
Gary Liebisch
W8GEL
Powell, OH


locked Re: #logging #logging

neil_zampella <neilz@...>
 

The ADIF has already been updated for the latest modes in v2.3.0.

Neil, KN3ILZ

On 2/3/2021 9:17 AM, David Ackrill wrote:

Hi,

I was discussing, via email, problems with logging old modes with a logbook program author (It was JT8 that was the problem on an export from a previous logging program that I'd used in the past) and I mentioned that WSJT-X was getting new operating modes and how to set up to log them and export to other programs.

He said that the people who update the specification for the ADIF recorded modes need to be notified so they can add designators and then these will get sent to the various logbook authors to update their software.

Maybe it has already been done, but does anyone know how long it takes to get the ADIF update sorted?  I guess those who use eQSO and LoTW will run into problems if the new modes are not recognised when they upload their WSJT-X logs?

Dave (G0DJA)





locked Re: #install - WSJT-X 2.3.0 Annoyance #install

Bill Somerville
 

On 03/02/2021 15:47, Nathern Priddy via groups.io wrote:
I just downloaded and installed WSJT-X 2.3.0.  In this version, there is a little box on the waterfall that follows the cursor showing the frequency that the cursor is at.  I find this to be a distraction and an annoyance. 

I've searched for a way to turn the box off, but no success.  Is there a way to turn this box off?

Barry Priddy - K5VIP/KG4BP

Hi Barry,

sorry, there's not.

This is going to sound trite, but if you don't like it then don't move the mouse pointer around the Wide Graph plots.

73
Bill
G4WJS.


locked Re: #install - WSJT-X 2.3.0 Annoyance #install

Karza
 

Barry,

On 3.2.2021 17.47, Nathern Priddy via groups.io wrote:
I just downloaded and installed WSJT-X 2.3.0.  In this version, there is a little box on the waterfall that follows the cursor showing the frequency that the cursor is at.  I find this to be a distraction and an annoyance. 
I myself rather like this feature ;)

I've searched for a way to turn the box off, but no success.  Is there a way to turn this box off?

Probably not, unless you modify the source code and recompile.

73's de Kari, oh2gqc


locked Re: Any Faster/Easier Way? #FT8

neil_zampella <neilz@...>
 

Ack ... that's going to be a hard one as, as you say, its maintained in the local instances' memory space.

Neil, KN3ILZ

On 2/3/2021 9:47 AM, Reino Talarmo wrote:

Neil,

His problem is not colors, but how to get adif information from instance A into instance B. There is a common adif file containing all information, but that is read into instance B runtime memory only at start-up or by manually re-scanning adif.

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of neil_zampella
Sent: 3. helmikuuta 2021 17:19
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Any Faster/Easier Way? #FT8

 

Each instance has its own settings (.ini) file, you just have to compare the color settings side by side to make sure they're the same.

Neil, KN3ILZ

On 2/3/2021 8:17 AM, Ken WB8UFC wrote:

Thank you for the responses.
But I think you all answered a question I didn't ask.
I already have a hard link for the log file and all of my instances share that one file.

I have a different issue.
Allow me to simplify and restate:
If I work 40M on Instance A and then switch to working 40M on instance B, the stations I worked on instance A are not colored as having been worked on instance B.

I currently address that problem by re-loading the log file on instance B - either by re-starting that instance or re-scanning the ADF log using the button provided.

I presume this results from a memory cache being used for some log-based functionality and the instances not sharing their cached information.

My question is... is there a faster or better workaround?

Thanks.

 
 
 




locked Re: #Logging #logging

David Ackrill
 

You can import the WSJT-X log file called "WSJT_log.adi" into Log4OM2 directly.

In Log4OM2 use "File>Import ADIF" then 'Load' and go to where the  WSJT_Log.adi file is located (In WSJT-X you can find where the ADI log file it it by clicking on "File>Open Log Directory".  It's under "AppData>Local>WSJT-X Logs" but you can open the ADI file from "File>Open Log Directory" and save a copy to somewhere easier to find if you want to).

Then, in Log4OM2, when you have 'loaded' the file, and before you click on 'Import' change the setting "Duplicates threshold" to something like 60 seconds (I did not do this the 1st time I imported a WSJT-X ADI file and I got a lot of duplicates because of the way WSJT-X saves contacts).  Then click Import.

It may take a while to import, especially on a big ADIF file, as Log4OM2 will carry out checks on the awards that each contact may qualify for.

Hope this helps - Dave (G0DJA)


locked Re: #Logging #logging

Herb Blue - WB8ASI
 

Ray,   I'm using Log4OMv2 with WSJT-X and JTAlert.  All works great.   I'd be glad to help.  Best place to look is in JTAlert Help > Open Help File > Settings > Logging > Log4OM v2.  Nice screen shots show the set up.   73, Herb WB8ASI


locked Re: 2.3.0 RC4 60m FT8 no longer working Yeasu #WSJTX_config #FT8

OZ4GD
 

My FTDX101D only works in VFO mode, else HAMLIB error (does not work in memory or MT mode.).

Version 2.3.0.   rig selected: FTDX101D.  cat + data/Pkt selected too.

OZ4GD


locked Re: Version 2.3.0 64 bit will not install #install

Gary Liebisch
 

I have instead found a copy of 2.2.1 and it installs fine. No uninstall. So I went from 2.1.2 to 2.2.1 without issue, then I tried 2.3.0 again with a fresh download and it still fails to do anything. So obviously there is something different about the 2.3.0 install.  I am going to sit this one out, satisfied for the time being with 2.2.1 and perhaps try again at later date. Perhaps someone else will find and contribute to a solution. Thanks.
--
Gary Liebisch
W8GEL
Powell, OH

18601 - 18620 of 40087