Date   

locked Re: An question of "certainty"

JP Tucson, AZ
 

...part 2...

Have you not worked Field Day?

Lot of hams have auto keyers on cw, & all the digi modes have macros, even ssb radios have prerecorded audio macros - all are designed to assist in preventing repetitive motion injuries & loss of voice, etc.

As a humor, if you are still uncomfortable with all of the 'fancy' tech, perhaps smoke signals would be up your alley... haha...





73 - John - N7GHZ

On Fri, Sep 4, 2020, 9:49 AM K7GQ <K7GQ@...> wrote:
Developers

I have become more aware lately of certain stations that appear to operate without a letup.  This is admirable in a contesting environment but on the other hand, I have NO wish to work automatic stations.

Is there a single bit, say in TX1, available within the message stream to identify WSJT-X to other WSJT-X users?  Or is there a better way to select out automatic stations? 
--
Harry  K7GQ


locked Re: Installing V2.2.2 on Mint 18.2 from source #install

Bill Somerville
 

On 04/09/2020 18:27, Robin wrote:
As a long time user of WSJT software, I wish to install WSJTX V2.2.2 on my Linux Mint 18.2.
The available 18.04 Ubuntu package does not install.
So, following Bill Somerville's repeated advice here, I am attempting to use the source code wsjtx-2.2.2.tgz.

Respecting the instructions exactly, I have ensured that all required dependencies (Debian) are met.  
However, when the command cmake is invoked, the computer generates a lot of activity, but then prints:
CMake Error
  Could not find a package configuration file provided by "Qt5SerialPort" with any of the following names:
       Qt5SerialPortConfig.cmake
       qt5Serialport-config.cmake

and then finally
--Configuring incomplete, errors occurred!

Is there an oversight of mine somewhere, or does this recipe not work with Mint 18.2?

Robin, 9H1ZZ

Hi Robin,

there are a couple of missing dependencies in the INSTALL file instructions, sorry about that. Hopefully we have them right for mainstream Linux distributions for the next release.

For that issue you need to install the QtSerialPort development package:

sudo apt install libqt5serialport5-dev

Don;t hesitate to ask about any further unmet dependencies.

73
Bill
G4WJS.


locked Levels using a SCU-17 and Yaesu FTDX1200 #AudioIssues

Richard -- N7WFK
 
Edited

I am curious if anyone out there knows how to configure the Windows 10 to work well with the WSJT-X software. Maybe there are some general settings in Windows 10 that I am missing. I am making contacts but when overseas stations come up I am not connecting with them. I am wondering if my levels are wrong or what not. I tried turning up the dial on the SCU-17 TX levels a little bit from half way mark and still nothing. I am able to get the middle of the US towards Washington state but East coast is an issue as well. My antenna is a GAP Titan DX for a vertical and I also have a dipole for 80 and 40 but 80 doesn't seem to work too good because of SWR issues. My tuner keeps having to tune it on 80 meters. 

Anyway... if you hams out there can help I would be so appreciative because so far I am having a lot of fun with this.


locked Installing V2.2.2 on Mint 18.2 from source #install

Robin
 

As a long time user of WSJT software, I wish to install WSJTX V2.2.2 on my Linux Mint 18.2.
The available 18.04 Ubuntu package does not install.
So, following Bill Somerville's repeated advice here, I am attempting to use the source code wsjtx-2.2.2.tgz.

Respecting the instructions exactly, I have ensured that all required dependencies (Debian) are met.  
However, when the command cmake is invoked, the computer generates a lot of activity, but then prints:
CMake Error
  Could not find a package configuration file provided by "Qt5SerialPort" with any of the following names:
       Qt5SerialPortConfig.cmake
       qt5Serialport-config.cmake

and then finally
--Configuring incomplete, errors occurred!

Is there an oversight of mine somewhere, or does this recipe not work with Mint 18.2?

Robin, 9H1ZZ


locked Re: An question of "certainty"

JP Tucson, AZ
 

Harry, what makes you think they are automatic?

Have any proof? In fact, NO! There is no way to tell an automatic station, if such a thing even exists!

How do you know they aren't club stations with multiple operators? Or dxpedition station like the one in Mauratania that's been operating since at least the beginning of the year? (Also with mult operators & on several bands at once!) Or retired/disabled folks who have nothing else to do, especially with stay @ home, etc.  I have run over 30 hours before I gave up & finally fell asleep.

Here's the point... work 'em once & you're done with the station, then move on.



73 - John - N7GHZ





On Fri, Sep 4, 2020, 9:49 AM K7GQ <K7GQ@...> wrote:
Developers

I have become more aware lately of certain stations that appear to operate without a letup.  This is admirable in a contesting environment but on the other hand, I have NO wish to work automatic stations.

Is there a single bit, say in TX1, available within the message stream to identify WSJT-X to other WSJT-X users?  Or is there a better way to select out automatic stations? 
--
Harry  K7GQ


locked Re: An question of "certainty"

Karza <kari.sillanmaki@...>
 

Hi Harry,

On 4.9.2020 19.49, K7GQ wrote:

...Is there a single bit, say in TX1, available within the message stream to identify WSJT-X to other WSJT-X users?
...even if there were a bit availiable, that would not help. WSJT-X is an open source projetct and all the source code is freely available. So anyone (with enough programming skills) could program his auto-station-program to set that  bit.

Plus, I believe there are even programs out there that monitor what is going on on the computer screen and can press the right buttons in order to make automatic QSOs using 'off-the-shelf' WSJT-X program.

Or is there a better way to select out automatic stations?
I believe there is no practical way to detect auto stations. 2bad.

73's de Kari, oh2gqc


locked Re: An question of "certainty"

D. Scott MacKenzie
 

While not 20 hours – but I have seen an operator calling for 10.5 hours straight and only working 3 people from adjacent grids on 6M.

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of K7GQ
Sent: Friday, September 4, 2020 1:01 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] An question of "certainty"

 

No positive way but have a difficult time accepting that "x" station could be operating for ~ 20 hours without a break.
--
Harry  K7GQ


locked Re: An question of "certainty"

K7GQ
 

No positive way but have a difficult time accepting that "x" station could be operating for ~ 20 hours without a break.
--
Harry  K7GQ


locked Re: An question of "certainty"

Dave (NK7Z)
 

You took the words out of my mouth...

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources

On 9/4/20 9:52 AM, W1EL Eric wrote:
Hi Harry,
Please tell me how you are presently identifying automatic stations?
Best Regards, Eric W1EL
*From:* main@WSJTX.groups.io <main@WSJTX.groups.io> *On Behalf Of *K7GQ
*Sent:* Friday, September 04, 2020 12:50
*To:* main@WSJTX.groups.io
*Subject:* [WSJTX] An question of "certainty"
Developers
I have become more aware lately of certain stations that appear to operate without a letup.  This is admirable in a contesting environment but on the other hand, I have NO wish to work automatic stations.
Is there a single bit, say in TX1, available within the message stream to identify WSJT-X to other WSJT-X users?  Or is there a better way to select out automatic stations?
--
Harry  K7GQ


locked Re: An question of "certainty"

W1EL Eric
 

Hi Harry,

 

Please tell me how you are presently identifying automatic stations?

 

Best Regards, Eric W1EL

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of K7GQ
Sent: Friday, September 04, 2020 12:50
To: main@WSJTX.groups.io
Subject: [WSJTX] An question of "certainty"

 

Developers

I have become more aware lately of certain stations that appear to operate without a letup.  This is admirable in a contesting environment but on the other hand, I have NO wish to work automatic stations.

Is there a single bit, say in TX1, available within the message stream to identify WSJT-X to other WSJT-X users?  Or is there a better way to select out automatic stations? 
--
Harry  K7GQ


locked An question of "certainty"

K7GQ
 

Developers

I have become more aware lately of certain stations that appear to operate without a letup.  This is admirable in a contesting environment but on the other hand, I have NO wish to work automatic stations.

Is there a single bit, say in TX1, available within the message stream to identify WSJT-X to other WSJT-X users?  Or is there a better way to select out automatic stations? 
--
Harry  K7GQ


locked Re: LinHPSDR/WSJTX no network option for OpenHPSDR/PiHPSR

m_scot_alex
 

Sorry, was a little confused by the mention of OpenHPSDR - PiHSDR does indeed have a 'network' rig control ability, but PowerSDR-derivatives don't.

73,

Mike - N8MSA


locked Re: Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIF header"

Al Groff
 

Are you sure that after editing in the eoh, that the .adi file is actually saved with the edit ?
AL, K0VM

On 9/3/2020 8:39 PM, Bill Somerville wrote:

On 04/09/2020 02:29, John L. Broughton wrote:
On 9/3/2020 4:09 PM, Bob Lewis wrote:

It seems to me that if WSJT-x created a new log file with the ???eh??? problem, that log file would be empty or contain only the contacts you have logged since the original log file was deleted. It wouldn???t take an existing log file and just change the eoh to eh. When the new version of WSJT-x came out I simply installed it over the old version. It kept all of my settings and my log file. I never saw the ???eh??? problem because the new WSJT-x has never crated a new log file. I agree, something has to be deleting or renaming the WSJT-x log file, forcing it to create a new one.

??

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Martin G0HDB
Sent: Thursday, September 03, 2020 6:44 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIf header"

??

On Thu, Sep 3, 2020 at 07:49 PM, John L. Broughton wrote:

I have had it happen a few times. The last being last evening when I started the program. For some reason WSTJT-X removes the o in eoh at the end of the header, likely when the program shuts down or starts. Then I have to open the ADIF file and put the o back in.

??

There must be something else in your system that's either deleting or renaming the wsjtx_log.adi file, which results in WSJT-X having to create a new file with the defective header when you start the program.

You need to investigate what's causing your wsjtx_log.adi files to be deleted or renamed rather than 'blaming' the WSJT-X app for what you're experiencing.

--
Martin G0HDB


Well, I can't imagine any program that would be looking at a WSJT-X file in a WSJT-X directory and going in and removing one letter in the header. If that were the case, I'd expect to have seen it long before now. The few times it has happened has been with my current version, v 2.2.2, and the version before that. I've been using WSJT-X for several years and this is a recent development.

As I said, I had the problem most recently yesterday. I had made a few contacts the day before with no problem. When I opened WSJT-X yesterday, I got the error. Here are the contents of the entire file as it appeared when I opened WSJT-X before I edited it to put the o back in:

WSJT-X ADIF Export<eh>
<call:6>WB5CXJ <gridsquare:4>EM50 <mode:3>FT8 <rst_sent:3>-12 <rst_rcvd:3>+08 <qso_date:8>20200902 <time_on:6>014600 <qso_date_off:8>20200902 <time_off:6>014715 <band:3>20m <freq:9>14.075923 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:4>N5HC <gridsquare:0> <mode:3>FT8 <rst_sent:3>-06 <rst_rcvd:3>-09 <qso_date:8>20200902 <time_on:6>022215 <qso_date_off:8>20200902 <time_off:6>022515 <band:3>20m <freq:9>14.074414 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K2FTC <gridsquare:4>EM98 <mode:3>FT8 <rst_sent:3>-15 <rst_rcvd:3>-06 <qso_date:8>20200902 <time_on:6>022900 <qso_date_off:8>20200902 <time_off:6>022945 <band:3>20m <freq:9>14.076386 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>W4LES <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+16 <rst_rcvd:3>-23 <qso_date:8>20200902 <time_on:6>023115 <qso_date_off:8>20200902 <time_off:6>023345 <band:3>20m <freq:9>14.075990 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K1SUU <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+08 <rst_rcvd:3>+06 <qso_date:8>20200902 <time_on:6>024400 <qso_date_off:8>20200902 <time_off:6>024445 <band:3>20m <freq:9>14.074871 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>


73,

John, WB9VGJ

John,

clearly you have a new WSJT-X ADIF log file there. As with Ed, K6ELE, something has deleted or renamed your WSJT-X ADIF log file.

73
Bill
G4WJS.



    


locked Re: 40m activity has been mad the last few nights

David Simms, N4IW
 

You will be fine with 10 watts on FT8.  It’s all about propagation.  Best of luck on your test!  Study hard and you will do just fine.  Hope to work you on FT8 real soon!
--
Thanks,
David, N4IW


locked Re: Subprocess failed with exit code -524284580

Bill Somerville
 

On 03/09/2020 19:04, kgkuzmin@... wrote:
I wonder if anyone experienced the following.

WSJT-X starts, opens both windows, but shortly after fails with the following error:
Subprocess error
Subprocess failed with exit code -524284580

Software is installed on Windows 10 64-bit. Hardware: Dell Latitude 5400. Processor: Intel i7-8665U CPU @ 1.90GHz 2.11GHz
I have tried different versions of WSJT-X from 2.2.2 down to 1.9.1 and tried installation for both - 32 and 64-bit platforms. Same error.

Hi OM,

is that a WSJT-X error message box? If it is then please include the details.

73
Bill
G4WJS.


locked Subprocess failed with exit code -524284580

kgkuzmin@...
 

I wonder if anyone experienced the following.

WSJT-X starts, opens both windows, but shortly after fails with the following error:
Subprocess error
Subprocess failed with exit code -524284580

Software is installed on Windows 10 64-bit. Hardware: Dell Latitude 5400. Processor: Intel i7-8665U CPU @ 1.90GHz 2.11GHz
I have tried different versions of WSJT-X from 2.2.2 down to 1.9.1 and tried installation for both - 32 and 64-bit platforms. Same error.


locked Re: Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIF header"

Bill Somerville
 

On 04/09/2020 02:29, John L. Broughton wrote:
On 9/3/2020 4:09 PM, Bob Lewis wrote:

It seems to me that if WSJT-x created a new log file with the “eh” problem, that log file would be empty or contain only the contacts you have logged since the original log file was deleted. It wouldn’t take an existing log file and just change the eoh to eh. When the new version of WSJT-x came out I simply installed it over the old version. It kept all of my settings and my log file. I never saw the “eh” problem because the new WSJT-x has never crated a new log file. I agree, something has to be deleting or renaming the WSJT-x log file, forcing it to create a new one.

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Martin G0HDB
Sent: Thursday, September 03, 2020 6:44 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIf header"

 

On Thu, Sep 3, 2020 at 07:49 PM, John L. Broughton wrote:

I have had it happen a few times. The last being last evening when I started the program. For some reason WSTJT-X removes the o in eoh at the end of the header, likely when the program shuts down or starts. Then I have to open the ADIF file and put the o back in.

 

There must be something else in your system that's either deleting or renaming the wsjtx_log.adi file, which results in WSJT-X having to create a new file with the defective header when you start the program.

You need to investigate what's causing your wsjtx_log.adi files to be deleted or renamed rather than 'blaming' the WSJT-X app for what you're experiencing.

--
Martin G0HDB


Well, I can't imagine any program that would be looking at a WSJT-X file in a WSJT-X directory and going in and removing one letter in the header. If that were the case, I'd expect to have seen it long before now. The few times it has happened has been with my current version, v 2.2.2, and the version before that. I've been using WSJT-X for several years and this is a recent development.

As I said, I had the problem most recently yesterday. I had made a few contacts the day before with no problem. When I opened WSJT-X yesterday, I got the error. Here are the contents of the entire file as it appeared when I opened WSJT-X before I edited it to put the o back in:

WSJT-X ADIF Export<eh>
<call:6>WB5CXJ <gridsquare:4>EM50 <mode:3>FT8 <rst_sent:3>-12 <rst_rcvd:3>+08 <qso_date:8>20200902 <time_on:6>014600 <qso_date_off:8>20200902 <time_off:6>014715 <band:3>20m <freq:9>14.075923 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:4>N5HC <gridsquare:0> <mode:3>FT8 <rst_sent:3>-06 <rst_rcvd:3>-09 <qso_date:8>20200902 <time_on:6>022215 <qso_date_off:8>20200902 <time_off:6>022515 <band:3>20m <freq:9>14.074414 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K2FTC <gridsquare:4>EM98 <mode:3>FT8 <rst_sent:3>-15 <rst_rcvd:3>-06 <qso_date:8>20200902 <time_on:6>022900 <qso_date_off:8>20200902 <time_off:6>022945 <band:3>20m <freq:9>14.076386 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>W4LES <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+16 <rst_rcvd:3>-23 <qso_date:8>20200902 <time_on:6>023115 <qso_date_off:8>20200902 <time_off:6>023345 <band:3>20m <freq:9>14.075990 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K1SUU <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+08 <rst_rcvd:3>+06 <qso_date:8>20200902 <time_on:6>024400 <qso_date_off:8>20200902 <time_off:6>024445 <band:3>20m <freq:9>14.074871 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>


73,

John, WB9VGJ

John,

clearly you have a new WSJT-X ADIF log file there. As with Ed, K6ELE, something has deleted or renamed your WSJT-X ADIF log file.

73
Bill
G4WJS.


locked Re: [V 2.2.2] Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIf header"

John L. Broughton
 

In my case, it does that with an existing ADIF file that it was writing to in the prior WSJT-X session. It is not creating a new file. It is not difficult to edit the file to at the o to the eh to make it eoh again, but one has to ask why it is happening.

And yes, it is the correct directory with all the other WSJT-X files, ALL.TXT, wsjtx.log, etc.

73,

John, WB9VGJ
On 9/2/2020 8:47 PM, Tyler Parsons wrote:

Are you saying that you have an intact wsjtx_log.adi file in the proper location, same as the CALL.TXT, wsjtx.log file and the ALL.TXT FILE?? If you start up and the program creates a new adi file with the <eh> header, how do you still have a previous wsjtx_log.adi file to add the new information to because the name should be the same and either append or overwrite?  My system just appends to the adj file, no new file unless I erase it.

I'm surprised that there is a provision in the FILE section to erase the wsjtx_log.adi file. That's where the program gets the information for the different colors. I haven't looked at it for a while but I remember the wsjtx.log file being the one able to be erased, maybe in a previous version, maybe not.
--
Tyler WB7DD

Virus-free. www.avg.com


    


locked Re: Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIF header"

John L. Broughton
 



On 9/3/2020 4:09 PM, Bob Lewis wrote:

It seems to me that if WSJT-x created a new log file with the “eh” problem, that log file would be empty or contain only the contacts you have logged since the original log file was deleted. It wouldn’t take an existing log file and just change the eoh to eh. When the new version of WSJT-x came out I simply installed it over the old version. It kept all of my settings and my log file. I never saw the “eh” problem because the new WSJT-x has never crated a new log file. I agree, something has to be deleting or renaming the WSJT-x log file, forcing it to create a new one.

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Martin G0HDB
Sent: Thursday, September 03, 2020 6:44 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIf header"

 

On Thu, Sep 3, 2020 at 07:49 PM, John L. Broughton wrote:

I have had it happen a few times. The last being last evening when I started the program. For some reason WSTJT-X removes the o in eoh at the end of the header, likely when the program shuts down or starts. Then I have to open the ADIF file and put the o back in.

 

There must be something else in your system that's either deleting or renaming the wsjtx_log.adi file, which results in WSJT-X having to create a new file with the defective header when you start the program.

You need to investigate what's causing your wsjtx_log.adi files to be deleted or renamed rather than 'blaming' the WSJT-X app for what you're experiencing.

--
Martin G0HDB


Well, I can't imagine any program that would be looking at a WSJT-X file in a WSJT-X directory and going in and removing one letter in the header. If that were the case, I'd expect to have seen it long before now. The few times it has happened has been with my current version, v 2.2.2, and the version before that. I've been using WSJT-X for several years and this is a recent development.

As I said, I had the problem most recently yesterday. I had made a few contacts the day before with no problem. When I opened WSJT-X yesterday, I got the error. Here are the contents of the entire file as it appeared when I opened WSJT-X before I edited it to put the o back in:

WSJT-X ADIF Export<eh>
<call:6>WB5CXJ <gridsquare:4>EM50 <mode:3>FT8 <rst_sent:3>-12 <rst_rcvd:3>+08 <qso_date:8>20200902 <time_on:6>014600 <qso_date_off:8>20200902 <time_off:6>014715 <band:3>20m <freq:9>14.075923 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:4>N5HC <gridsquare:0> <mode:3>FT8 <rst_sent:3>-06 <rst_rcvd:3>-09 <qso_date:8>20200902 <time_on:6>022215 <qso_date_off:8>20200902 <time_off:6>022515 <band:3>20m <freq:9>14.074414 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K2FTC <gridsquare:4>EM98 <mode:3>FT8 <rst_sent:3>-15 <rst_rcvd:3>-06 <qso_date:8>20200902 <time_on:6>022900 <qso_date_off:8>20200902 <time_off:6>022945 <band:3>20m <freq:9>14.076386 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>W4LES <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+16 <rst_rcvd:3>-23 <qso_date:8>20200902 <time_on:6>023115 <qso_date_off:8>20200902 <time_off:6>023345 <band:3>20m <freq:9>14.075990 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K1SUU <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+08 <rst_rcvd:3>+06 <qso_date:8>20200902 <time_on:6>024400 <qso_date_off:8>20200902 <time_off:6>024445 <band:3>20m <freq:9>14.074871 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>


73,

John, WB9VGJ


locked Re: World-wide Digi DX Contest Problem

Bill N4iQ
 

No - Roger I checked this.  The radio itself is not in split operation when In WSJTX Fake It.    The 590S and 590SG has some differences in the CAT commands and perhaps this is a reason the SG radio operates in Fake it and the 590S does not. Or the problem could be the way OMNIRIG is handling the Fake It from WSJT-X with the 590S.   I am not using OMNIRig with the 590SG.  There are other possibilities but not worth my time trying to figure it out.  Setting up WSJT-X  in Split Mode works for both radios so that is what I am using.   As I said previously "SPLIT works fine now.   During the contest turmoil perhaps I did not have the 590S in split for the WSJT-X split mode?  Totally possible.  Who knows."  I was trying a lot of things to find why Fake It was not working with the S radio and perhaps the 590 radio split was not turned back on for WSJT-X split. 

Think we can move on now.   I truly appreciate everyone's replies and help.  Happy WSJT-X contesting!!!!!

Thanks all - Bill N4iQ