I would suspect as a program that has to be able to be cross-compiled across many OSs,  it would not necessarily have the 'hooks' for each OS to use to do this from the appropriate UI controls.

Neil, KN3ILZ

Thanks, but wondering why it has to be done this way and not automatic when selecting dark mode in the os?

I have the same problem. Went back to 2.1.0 and no trouble. I can not see the article cited previously.

73,
Ed KA9EES

Could you tell me how to do this on a Mac?  Thanks...Mike..kb3lan

Hi Mike,

it is essentially the same, but the command to launch an application bundle like WSJT-X from the command line is like this:

open /Applications/wsjtx.app --args -stylesheet :/qdarkstyle/style.qss

73
Bill
G4WJS.

I have used WSJTX, Win4Icom, and other logging software without issues , mostly using methods used in your number 1. However I never involved Omnirig.  I use DX Lab Suite and set WSJT-X to "DX LAB" as the radio. Are you dead set on N3FJP ?

Andy K3UK 

Hello all.

I am a new UK operator. I have been trying for the last few weeks to have N3FJP logger, Win4Icom Suite and WSJT-X work together happily. I am not fussed about having all active at the same time, I understand WSJT-X creates it's own logs that I have been able to import into N3FJP successfully.

My radio is an ICOM 9700 that is connected to my PC via USB (ICOM USB drivers installed). This has caused the creation of Com ports 3 & 4.

My issue is around com ports and the ability of either N3FJP or WSJT-X to directly address the radio for CAT control. I have tried two different approaches:

1. Using Win4Icom to take ownership of Com 3, then creating two pairs of virtual Com ports (using com0com), one port of each pair being assigned to Win4Icom and the other port of each pair being assigned to N3FJP & WSJT-X respectively. This approach also required the installation of OmniRig, which was a complete PITA trying to find a 9700.ini file. I was able to have everything running this way after a couple of weeks of cursing and some late nights, but I'm not entirely convinced WSJT-X was working properly.

2. Using N3FJP and WSJT-X on their own. I used WSJT-X first and it took Com 3 and it works without issue. When I then close WSJT-X and load N3FJP (also assigned Com 3), it can't access the 9700 and complains about an open port it can't close. I have tried rebooting between sessions of the apps as well and that doesn't work either - N3FJP seems to think WSJT-X has locked Com 3.

Can anyone suggest a way to deal with this? Ideally I'd like to be able to just use option 2 above, but have both apps work properly and address the 9700 properly when opened (not at the same time). Is there a way to force WSJT-X to release Com 3? I have tried setting the port in settings to something else, but that doesn't work either.

The only other thought I've had is to use a CI-V cable in addition to the USB cable to create two physical connections between radio and PC, in the hope that CAT control will be possible with either dependent upon which app is running. 

TIA for any advice.

So here is how I work around this..
I use Log4OM.  I export my Confirmed/Verified logs and copy/paste them into WSJT's log and overwrite what is there!
Making the colors actually useful.
It’s much more productive to just overwrite the log so you have the verified countries in there not just worked.. After all, worked doesn’t matter if I don’t have any credit for it.

In Log4OM, open QSL Management.

Along the bottom, click Search Parameters.

I saved one and just re-use it (defined as WSJT with LoTW Verified (click it in “Saved search” then click the disk with blue up-arrow.  Then click green checkmark to make it active.)

Note: I changed QSL status to (LotwQslRcvd = 'V' OR QslRcvd = 'V' OR QslRcvd = 'Y')

Then at the top, click Search.

Then click “Select All” at the bottom again then click “To ADIF” at the top.

Set “Simplified ADIF” and the path then export.

 

You now have an ADIF that can be used!  Open it in Notepad and copy the log rows without the header.

I then replaced the log rows in the WSJT-X Profiles (actually I replaced them in one then replaced copy/paste the file into the other two profiles.)

C:\Users\77ind\AppData\Local\WSJT-X

C:\Users\77ind\AppData\Local\WSJT-X - IC7610

C:\Users\77ind\AppData\Local\WSJT-X - IC9100

Then in WSJT-X, simply Rescan ADIF Log →

Could you tell me how to do this on a Mac?  Thanks...Mike..kb3lan

Hi Ted,

I own 3 Elecraft radios, also a PX3, and a KXPA100. I have copies of each factory configuration file backed up in multiple places. You reminded me that I still need to reach out to Elecraft support for the factory settings on this K3s. This may be why I did not bother to do a full reset.

A good reminder to others that may not know this about Elecraft gear.

73

K5RHD

/randy

FWIW... I would uninstall, you won't lose any of your settings or logs as they're kept in a separate directory, then install the 64 bit version.   There is a small issue with audio settings that Bill has posted about previously, I'm fairly sure you can do a search to find that post.

The reason I suggest an uninstall is to make sure that any 32 bit DLLs and the like are removed.

Neil, KN3ILZ

On 12/01/2020 07:44, spabish@... wrote:

Running the 32 bit version of WSJT-X on a Windows 10 computer.
Should I uninstall WSJT-X if I want to upgrade/install the 64 bit version?
Or should I just install the 64 bit version of WSJT-X on top of the current install?

Thanks
N2GNT

Hi OM,

you can do either. What is important is that the way Tx audio is handled in the 64-bit version is slightly different and you will have to do some initial setup. See this post for details:

https://groups.io/g/WSJTX/message/5077

73
Bill
G4WJS.

Running the 32 bit version of WSJT-X on a Windows 10 computer.
Should I uninstall WSJT-X if I want to upgrade/install the 64 bit version?
Or should I just install the 64 bit version of WSJT-X on top of the current install?

Thanks
N2GNT

Dave, Thanks for your comments.
With the FT-736, my initial concern is to use the Echo mode for testing the EME system. I expect that the oscillator drift will not be critical for the echoes. But I will look at either modifying or replacing the FT-736R if I want to do EME data modes later.

Regarding the DATA IO cables, I was advised just a couple of days ago that the Data-IN/OUT socket on the rear panel of the FT-736R is for FM modes only and that you can't use that socket in the SSB mode. I am not sure if that is correct. Certainly the FT-736R manual says the data socket connects your computer directly to the FM discriminator, but I find it hard to believe that Yaesu would have connected that socket up in such a way that no audio goes in or comes out in SSB mode. I am thinking of setting up a FT-736R on the bench and testing this, but I would be interested in your thoughts on that advice.
Cheers
George
vk3eip

I suggest you don’t ever do a full reset on a K3 without having a copy of the (hopefully vanilla) settings file. There are many things that are set up at the Elecraft factory to configure the radio. If you reset all to defaults, you lose the factory calibration, and have a whole lot of calibration to do with equipment and procedures you may not have.
--
VE3TRQ  Ted

Thanks for posting this info, Bill! MUCH easier on my eyes.

73 de Gary - W9BS

I also have a FT736r.

Nice radio, even now, but...

You will need to do something to prevent the 20.48MHz reference
oscillator drifting with temperature (even the TCXO drifts!)  It's
"OK"(ish) for voice modes, but is just not good enough for many digital
modes on 23cms.

Note too, that the "DATA" I/O cable, has a tendency to couple RF into
the radio in a bad way (a classic "Pin 1" problem) causing "wide"
signals and overall splatter.  Difficult to tell, as these rig's don't
have a TX monitor facility as standard, unless you use another RX to
monitor your TX signal with mk1 ear'ole.

Re the PTT.  Hamlib (V3.3 onwards) correctly controls the FT736r for
PTT, mode & frequency etc from WSJTx  (Thanks to Bill G4WJS) so go for
CAT control.  It works.  (And it correctly releases the radio when you
exit WSJTx.)

73.

Dave G0WBX.

--
Created on and sent from a Unix like PC running and using free and open source software: