Date   

locked Re: Automatic LotW logging #Alinco #adiFiles

Jim Cary
 

Phil,

No, that is not the case. My W2SM location action was the same as the ZF location until I had to reload from scratch all my software at W2 because of a lightening strike that took out the computer, as well as damaged my radios. And when I finished downloading and installing all the software, the "automatic LotW" logging started. So I have something different set between the two systems. I don't know if it is a WSJT-X or JTAlert setting or perhaps a DXKeeper setting.

It's not a critical issue at all, just something that bugs me!

73,

Jim


locked Re: Automatic LotW logging #adiFiles #Alinco #logging

Jim Cary
 

Laurie..... Thanks.

You are the man!!!

73,

Jim


locked Re: Older version 2.5.1 #general

 

Tnx Charles for the info.

73's Dave NU4N

On 3/9/2022 4:58 AM, Charles Suckling wrote:
https://sourceforge.net/projects/wsjt/files/

On Wed, 9 Mar 2022 at 11:51, Dave Tucker Nu4N <dwtucker19@...>
wrote:

Where can I get a older copy of WSJT-X version 2.5.1 ?
--
Thanks 73's de NU4N/Dave






--
Tnx 73's de NU4N Dave
--
Thanks 73's de NU4N/Dave


locked Re: FT857 Rig control problem #hamlib

d_ziolkowski
 

Karl- Thanks for the detailed explanation, it worked. attached is the log for Mike thanks DAN KC2STA On Wed, Mar 9, 2022 at 4:46 AM Karza wrote: > Don, > > When started with parameter "--rig-name=FT857" WSJT-X will store > coniguration into file named > 'WSJTX - FT857.ini'. This file is stored in directory '~/.config'. You > should place file 'wsjtx_log_config.ini' into '~/.config' too. > > The 'WSJT-X_RigControl.log' file will then be created in directory > '~/.local/share/WSJT-X - FT857'. > > HTH de Kari, oh2gqc > > > You should place the > On 9.3.2022 0.04, d_ziolkowski wrote: > > Mike -- > > > > Found wsjtx.ini in ~/.wsjtx. > > > > placed the log.ini in that folder. > > > > ran test as directed, no log generated. > > > > Perhaps you need to know that the ft857 runs wsjtx --rigname=FT857. > > > > ~/.wsjtx$ ls > > afmhot.dat in.dat save wsjtx.ini > > ALL.TXT jt9 shortcuts.txt > wsjtx_log_config.ini > > blue.dat jt9.txt timer.out wsjtx_status.txt > > CALL3.TXT kvasd.dat wsjtx > > decoded.txt mouse_commands.txt wsjtx_changelog.txt > > > > Thanks DAN kc2sta > > > > > > > > On Tue, Mar 8, 2022 at 3:24 PM Michael Black via groups.io > yahoo.com@groups.io> wrote: > > > >> The you didn't put the file in the right place. > >> Should be the same location as the WSJT-X.ini file wherever your system > >> put that. > >> > >> > >> > >> On Tuesday, March 8, 2022, 01:18:05 PM CST, d_ziolkowski < > >> dan.ziolkowski@...> wrote: > >> > >> Mike > >> > >> Error occurred again, did as email directed, but no rigcontol.log file > is > >> generated. > >> > >> Dan KC2STA > >> > >> On Mon, Mar 7, 2022 at 4:17 PM Michael Black via groups.io >> yahoo.com@groups.io> wrote: > >> > >>> Please place this file in > >>> ~/.local/share/WSJT-X > >>> https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0 > >>> Restart WSJT-X and duplicate the problem.Shut down WSJT-X > >>> Then send me the WSJT-X_RigControl.log file that will be in the same > >>> location. > >>> Mike W9MDB > >>> > >>> > >>> > >>> > >>> On Monday, March 7, 2022, 03:14:01 PM CST, d_ziolkowski < > >>> dan.ziolkowski@...> wrote: > >>> > >>> Running WSJTX-2.5.4 on Ubuntu 18.04. Rig FT-857. > >>> > >>> Upgraded to this version a couple weeks ago, and all was fine. PC runs > >>> 24/7. > >>> > >>> Today when I loaded wsjtx and transmitted, I received this Error: > >>> ======================================= > >>> Hamlib error: Command rejected by the rig > >>> 0000 f0 . > >>> ft817_read_ack: ack received (240) > >>> rig.c(1571):rig_set_freq return(-9) Command rejected by the rig > >>> 0000 f0 . > >>> ft817_read_ack: ack received (240) > >>> ft817_read_ack: ack received (240) while setting frequency > >>> > >>> Timestamp: 2022-03-07T18:40:57.283Z > >>> =================================== > >>> > >>> Seems odd that the error references an ft817, but rig is set to FT857. > I > >>> also set rig to NONE, then back to FT857, still problem. > >>> > >>> After the error, I then hit retry and back to normal, until next xmit, > >>> problem repaets. > >>> > >>> I reduced power to rig from 60 watts , to 5 watts, same problem. > >>> > >>> Connected dummy load , same problem at 5 watts > >>> > >>> Also problem occurs AFTER transmit ends. Not while transmitting. > >>> > >>> SO I re-installed wjtx, but same problem. > >>> > >>> PC reboot does not fix problem either. > >>> > >>> I tried FLrig, and no problems with control. > >>> > >>> Any help is appreciated, > >>> > >>> Thanks Dan KC2STA > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >> -- > >> Dan Ziolkowski KC2STA > >> SKCC #4290T > >> Ubuntu LINUX > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > > > > > > > -- Dan Ziolkowski KC2STA SKCC #4290T Ubuntu LINUX


locked Re: I can't understand what is the mede #TechnicalHelpQuestion

Phil Davidson
 

Try https://www.sigidwiki.com/wiki/Signal_Identification_Guide
Regards - Phil

On Tue, 8 Mar 2022 at 15:49, Reino Talarmo <reino.talarmo@...>
wrote:

Hi Pietro and Mike,

It is too narrow about 1.5 kHz for WinDRM that is 2.2 to 2.4 kHz wide.

73, Reino OH3mA

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of
Michael Black via groups.io
Sent: 8. maaliskuutata 2022 16:53
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] I can't understand what is the mede
#TechnicalHelpQuestion

Could be WinDRM?https://www.sigidwiki.com/wiki/Category:HF

Mike W9MDB

On Tuesday, March 8, 2022, 08:29:51 AM CST, Pietro Molina <
pietro@...> wrote:

Despite the help, I cant find out the mode.

Here a new screenshot with frequency scale:
https://1drv.ms/u/s!AuQm2UBQE7eKpa82VrgAMXsNXjj1tw?e=FnV2Gg

I'd tried 8PSK but I cant solve. Which SW is to be used for 16PSK or 16QAM?

May be it is digital voice mode?

Pietro I2OIM


















locked Re: Older version 2.5.1 #general

Charles Suckling
 

https://sourceforge.net/projects/wsjt/files/

On Wed, 9 Mar 2022 at 11:51, Dave Tucker Nu4N <dwtucker19@...>
wrote:

Where can I get a older copy of WSJT-X version 2.5.1 ?
--
Thanks 73's de NU4N/Dave






locked Older version 2.5.1 #general

 

Where can I get a older copy of WSJT-X version 2.5.1 ?
--
Thanks 73's de NU4N/Dave


locked Re: FT857 Rig control problem #hamlib

Karza
 

Don,

When started with parameter "--rig-name=FT857"  WSJT-X will store coniguration into file named
'WSJTX - FT857.ini'. This file is stored in directory '~/.config'. You should place file 'wsjtx_log_config.ini' into  '~/.config' too.

The 'WSJT-X_RigControl.log' file will then be created in directory '~/.local/share/WSJT-X - FT857'.

HTH de Kari, oh2gqc


You should place the

On 9.3.2022 0.04, d_ziolkowski wrote:
Mike --

Found wsjtx.ini in ~/.wsjtx.

placed the log.ini in that folder.

ran test as directed, no log generated.

Perhaps you need to know that the ft857 runs wsjtx --rigname=FT857.

~/.wsjtx$ ls
afmhot.dat in.dat save wsjtx.ini
ALL.TXT jt9 shortcuts.txt wsjtx_log_config.ini
blue.dat jt9.txt timer.out wsjtx_status.txt
CALL3.TXT kvasd.dat wsjtx
decoded.txt mouse_commands.txt wsjtx_changelog.txt

Thanks DAN kc2sta



On Tue, Mar 8, 2022 at 3:24 PM Michael Black via groups.io <mdblack98=
yahoo.com@groups.io> wrote:

The you didn't put the file in the right place.
Should be the same location as the WSJT-X.ini file wherever your system
put that.



On Tuesday, March 8, 2022, 01:18:05 PM CST, d_ziolkowski <
dan.ziolkowski@...> wrote:

Mike

Error occurred again, did as email directed, but no rigcontol.log file is
generated.

Dan KC2STA

On Mon, Mar 7, 2022 at 4:17 PM Michael Black via groups.io <mdblack98=
yahoo.com@groups.io> wrote:

Please place this file in
~/.local/share/WSJT-X
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
Restart WSJT-X and duplicate the problem.Shut down WSJT-X
Then send me the WSJT-X_RigControl.log file that will be in the same
location.
Mike W9MDB




On Monday, March 7, 2022, 03:14:01 PM CST, d_ziolkowski <
dan.ziolkowski@...> wrote:

Running WSJTX-2.5.4 on Ubuntu 18.04. Rig FT-857.

Upgraded to this version a couple weeks ago, and all was fine. PC runs
24/7.

Today when I loaded wsjtx and transmitted, I received this Error:
=======================================
Hamlib error: Command rejected by the rig
0000 f0 .
ft817_read_ack: ack received (240)
rig.c(1571):rig_set_freq return(-9) Command rejected by the rig
0000 f0 .
ft817_read_ack: ack received (240)
ft817_read_ack: ack received (240) while setting frequency

Timestamp: 2022-03-07T18:40:57.283Z
===================================

Seems odd that the error references an ft817, but rig is set to FT857. I
also set rig to NONE, then back to FT857, still problem.

After the error, I then hit retry and back to normal, until next xmit,
problem repaets.

I reduced power to rig from 60 watts , to 5 watts, same problem.

Connected dummy load , same problem at 5 watts

Also problem occurs AFTER transmit ends. Not while transmitting.

SO I re-installed wjtx, but same problem.

PC reboot does not fix problem either.

I tried FLrig, and no problems with control.

Any help is appreciated,

Thanks Dan KC2STA











--
Dan Ziolkowski KC2STA
SKCC #4290T
Ubuntu LINUX












locked Re: Automatic LotW logging #adiFiles #Alinco #logging

 

Hi Jim,

The difference I see is that for one you are in W2 the other bin ZF2. Maybe it’s your communications ability at each location.

Phil GM3ZZA

Sent from Mail for Windows

From: Jim Cary
Sent: 08 March 2022 20:13
To: main@WSJTX.groups.io
Subject: [WSJTX] Automatic LotW logging #adiFiles #Alinco #logging

I have to stations with identical setups --- K3, WSJT-X, JTAlert, and DXKeeper.

On one station, W2SM, the contacts automatically upload to LoTW once I hit the "log: button.

On the other, ZF2LC, they only upload when I go to DXKeeper and tell it to upload to LoTW.

For the life of me, I cannot find the setting that controls this. Where is i?!!!

Jim
W2SM
ZF2LC


locked Re: Automatic LotW logging #adiFiles #Alinco #logging

JTAlert Support (VK3AMA)
 

On 9/03/2022 6:32 am, Jim Cary wrote:
I have to stations with identical setups --- K3, WSJT-X, JTAlert, and DXKeeper.

On one station, W2SM, the contacts automatically upload to LoTW once I hit the "log: button.

On the other, ZF2LC, they only upload when I go to DXKeeper and tell it to upload to LoTW.

For the life of me, I cannot find the setting that controls this. Where is i?!!!

Jim
W2SM
ZF2LC
If you are using JTAlert to log QSOs to DXKeeper than visit the JTAlert Settings window, "Logging -> DXLab DXKeeper" section and enable the "Instruct DXKeeper to upload each new QSO to LoTW" checkbox.

de Laurie VK3AMA


locked Re: FT857 Rig control problem #hamlib

d_ziolkowski
 

Mike --

Found wsjtx.ini in ~/.wsjtx.

placed the log.ini in that folder.

ran test as directed, no log generated.

Perhaps you need to know that the ft857 runs wsjtx --rigname=FT857.

~/.wsjtx$ ls
afmhot.dat in.dat save wsjtx.ini
ALL.TXT jt9 shortcuts.txt wsjtx_log_config.ini
blue.dat jt9.txt timer.out wsjtx_status.txt
CALL3.TXT kvasd.dat wsjtx
decoded.txt mouse_commands.txt wsjtx_changelog.txt

Thanks DAN kc2sta



On Tue, Mar 8, 2022 at 3:24 PM Michael Black via groups.io <mdblack98=
yahoo.com@groups.io> wrote:

The you didn't put the file in the right place.
Should be the same location as the WSJT-X.ini file wherever your system
put that.



On Tuesday, March 8, 2022, 01:18:05 PM CST, d_ziolkowski <
dan.ziolkowski@...> wrote:

Mike

Error occurred again, did as email directed, but no rigcontol.log file is
generated.

Dan KC2STA

On Mon, Mar 7, 2022 at 4:17 PM Michael Black via groups.io <mdblack98=
yahoo.com@groups.io> wrote:

Please place this file in
~/.local/share/WSJT-X
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
Restart WSJT-X and duplicate the problem.Shut down WSJT-X
Then send me the WSJT-X_RigControl.log file that will be in the same
location.
Mike W9MDB




On Monday, March 7, 2022, 03:14:01 PM CST, d_ziolkowski <
dan.ziolkowski@...> wrote:

Running WSJTX-2.5.4 on Ubuntu 18.04. Rig FT-857.

Upgraded to this version a couple weeks ago, and all was fine. PC runs
24/7.

Today when I loaded wsjtx and transmitted, I received this Error:
=======================================
Hamlib error: Command rejected by the rig
0000 f0 .
ft817_read_ack: ack received (240)
rig.c(1571):rig_set_freq return(-9) Command rejected by the rig
0000 f0 .
ft817_read_ack: ack received (240)
ft817_read_ack: ack received (240) while setting frequency

Timestamp: 2022-03-07T18:40:57.283Z
===================================

Seems odd that the error references an ft817, but rig is set to FT857. I
also set rig to NONE, then back to FT857, still problem.

After the error, I then hit retry and back to normal, until next xmit,
problem repaets.

I reduced power to rig from 60 watts , to 5 watts, same problem.

Connected dummy load , same problem at 5 watts

Also problem occurs AFTER transmit ends. Not while transmitting.

SO I re-installed wjtx, but same problem.

PC reboot does not fix problem either.

I tried FLrig, and no problems with control.

Any help is appreciated,

Thanks Dan KC2STA











--
Dan Ziolkowski KC2STA
SKCC #4290T
Ubuntu LINUX











--
Dan Ziolkowski KC2STA
SKCC #4290T
Ubuntu LINUX


locked Re: FT857 Rig control problem #hamlib

Michael Black
 

The you didn't put the file in the right place.
Should be the same location as the WSJT-X.ini file wherever your system put that.

On Tuesday, March 8, 2022, 01:18:05 PM CST, d_ziolkowski <dan.ziolkowski@...> wrote:

Mike

Error occurred again, did as email directed, but no rigcontol.log file is
generated.

Dan KC2STA

On Mon, Mar 7, 2022 at 4:17 PM Michael Black via groups.io <mdblack98=
yahoo.com@groups.io> wrote:

Please place this file in
  ~/.local/share/WSJT-X
  https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
Restart WSJT-X and duplicate the problem.Shut down WSJT-X
Then send me the WSJT-X_RigControl.log file that will be in the same
location.
Mike W9MDB




    On Monday, March 7, 2022, 03:14:01 PM CST, d_ziolkowski <
dan.ziolkowski@...> wrote:

  Running WSJTX-2.5.4 on Ubuntu 18.04. Rig FT-857.

Upgraded to this version a couple weeks ago, and all was fine. PC runs
24/7.

Today when I loaded wsjtx and transmitted, I received this Error:
=======================================
Hamlib error: Command rejected by the rig
0000    f0                                                  .
ft817_read_ack: ack received (240)
rig.c(1571):rig_set_freq return(-9) Command rejected by the rig
0000    f0                                                  .
ft817_read_ack: ack received (240)
ft817_read_ack: ack received (240) while setting frequency

Timestamp: 2022-03-07T18:40:57.283Z
===================================

Seems odd that the error references an ft817, but rig is set to FT857. I
also set rig to NONE, then back to FT857, still problem.

After the error, I then hit retry and back to normal, until next xmit,
problem repaets.

I reduced power to rig from 60 watts , to 5 watts, same problem.

Connected dummy load , same problem at 5 watts

Also problem occurs AFTER transmit ends. Not while transmitting.

SO I re-installed wjtx, but same problem.

PC reboot does not fix problem either.

I tried FLrig, and no problems with control.

Any help is appreciated,

Thanks Dan KC2STA











--
Dan Ziolkowski KC2STA
SKCC #4290T
Ubuntu LINUX


locked Automatic LotW logging #adiFiles #Alinco #logging

Jim Cary
 

I have to stations with identical setups --- K3, WSJT-X, JTAlert, and DXKeeper.

On one station, W2SM, the contacts automatically upload to LoTW once I hit the "log: button.

On the other, ZF2LC, they only upload when I go to DXKeeper and tell it to upload to LoTW.

For the life of me, I cannot find the setting that controls this. Where is i?!!!

Jim
W2SM
ZF2LC


locked Re: Logging based on prompt does not mean that the other station has logged the contact #logging

dl8le
 

Thanks a lot to all which responded to my question, starting from the suggestions to double check the all.txt file, to look for missing locators, the Two General's Wikipedia reference up to the publication about FT4_FT8_Contesting.

Conclusion for the next RSGB contest on March 28 will be that besides of looking very carefully at the messages after logging a call on prompt I will also take the time and look into the all.txt file much more deeper than I did already. This is not a big issue as the time of 1.5 hours is limiting the number of logged contacts to a two digit figure only most probably. And - as there is no solution for the Two General's problem - I will live with the remaining uncertainties.

Thanks again

73

Juergen, DL8LE


locked Re: FT857 Rig control problem #hamlib

d_ziolkowski
 

Mike

Error occurred again, did as email directed, but no rigcontol.log file is
generated.

Dan KC2STA

On Mon, Mar 7, 2022 at 4:17 PM Michael Black via groups.io <mdblack98=
yahoo.com@groups.io> wrote:

Please place this file in
~/.local/share/WSJT-X
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
Restart WSJT-X and duplicate the problem.Shut down WSJT-X
Then send me the WSJT-X_RigControl.log file that will be in the same
location.
Mike W9MDB




On Monday, March 7, 2022, 03:14:01 PM CST, d_ziolkowski <
dan.ziolkowski@...> wrote:

Running WSJTX-2.5.4 on Ubuntu 18.04. Rig FT-857.

Upgraded to this version a couple weeks ago, and all was fine. PC runs
24/7.

Today when I loaded wsjtx and transmitted, I received this Error:
=======================================
Hamlib error: Command rejected by the rig
0000 f0 .
ft817_read_ack: ack received (240)
rig.c(1571):rig_set_freq return(-9) Command rejected by the rig
0000 f0 .
ft817_read_ack: ack received (240)
ft817_read_ack: ack received (240) while setting frequency

Timestamp: 2022-03-07T18:40:57.283Z
===================================

Seems odd that the error references an ft817, but rig is set to FT857. I
also set rig to NONE, then back to FT857, still problem.

After the error, I then hit retry and back to normal, until next xmit,
problem repaets.

I reduced power to rig from 60 watts , to 5 watts, same problem.

Connected dummy load , same problem at 5 watts

Also problem occurs AFTER transmit ends. Not while transmitting.

SO I re-installed wjtx, but same problem.

PC reboot does not fix problem either.

I tried FLrig, and no problems with control.

Any help is appreciated,

Thanks Dan KC2STA











--
Dan Ziolkowski KC2STA
SKCC #4290T
Ubuntu LINUX


locked Re: I can't understand what is the mede #TechnicalHelpQuestion

Reino Talarmo
 

Hi Pietro and Mike,

It is too narrow about 1.5 kHz for WinDRM that is 2.2 to 2.4 kHz wide.

73, Reino OH3mA

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Michael Black via groups.io
Sent: 8. maaliskuutata 2022 16:53
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] I can't understand what is the mede #TechnicalHelpQuestion

Could be WinDRM?https://www.sigidwiki.com/wiki/Category:HF

Mike W9MDB

On Tuesday, March 8, 2022, 08:29:51 AM CST, Pietro Molina <pietro@...> wrote:

Despite the help, I cant find out the mode.

Here a new screenshot with frequency scale: https://1drv.ms/u/s!AuQm2UBQE7eKpa82VrgAMXsNXjj1tw?e=FnV2Gg

I'd tried 8PSK but I cant solve. Which SW is to be used for 16PSK or 16QAM?

May be it is digital voice mode?

Pietro I2OIM


locked Re: Call 1st - filtering #FT8

Reino Talarmo
 

Hi,

Not within WSJT-X.

73, Reino OH3mA

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Ellis Birt (G7SAI) via groups.io
Sent: 8. maaliskuutata 2022 12:59
To: main@WSJTX.groups.io
Subject: [WSJTX] Call 1st - filtering #FT8

Hi,

Is there any way to filter the callsigns or DXCC that WSJTX will respond to if you have Call 1st checked.

In these times of conflict some people do not want to QSO with operators in Russia or Belarus (The RSGB recommend against it).

Thanks & 73

Ellis G7SAI


locked Re: Call 1st - filtering #FT8

Karza
 

Hi Ellis,


Hi,

Is there any way to filter the callsigns or DXCC that WSJTX will respond to if
you have Call 1st checked.
No, there is no such option in WSJT-X. Just disable Call 1st and select
your QSO partners manually.

In these times of conflict some people do not want to QSO with operators in
Russia or Belarus (The RSGB recommend against it).

Thanks & 73

Ellis G7SAI
73's de Kari, oh2gqc


locked Re: I can't understand what is the mede #TechnicalHelpQuestion

Michael Black
 

On Tuesday, March 8, 2022, 08:29:51 AM CST, Pietro Molina <pietro@...> wrote:

Despite the help, I cant find out the mode.

Here a new screenshot with frequency scale: https://1drv.ms/u/s!AuQm2UBQE7eKpa82VrgAMXsNXjj1tw?e=FnV2Gg

I'd tried 8PSK but I cant solve. Which SW is to be used for 16PSK or 16QAM?

May be it is digital voice mode?

Pietro I2OIM


locked Re: Logging based on prompt does not mean that the other station has logged the contact #logging

Joe
 

On Mon, Mar 7, 2022 at 11:57 AM, dl8le wrote:


Hello,

I have participated in the RSGB FT4 contest and found the UBN-file stating
"missing qso in log" for 6 out of 64 contacts. I always click on ok, when the
prompt asks me to do the logging. I wonder how this can happen or what I can
do to avoid this problem showing up. As this happend before on another FT4
contest (similar percentage) it looks as I have a real problem to rely on this
prompt. Therefore it would be nice to have a solution. OS is Windows 11, I am
using version 2.4 of WSJT-X (latest version downloaded from the website).

73

Juergen, DL8LE
Hi Juergen,

The question of when to log an FT4/FT8 contest QSO was addressed at some length in an article in the ARRL's National Contest Journal. A copy of the article is posted here:
https://physics.princeton.edu//pulsar/k1jt/NCJ_FT4_FT8_Contesting.pdf

-- 73, Joe, K1JT

5621 - 5640 of 37978