Date   

locked Re: Where is the location of the WSJT-X log? #FT8 #logging

Pietro Molina
 

Under "File" menu there is a line with "Open log directory" or similar (I
have another language set).

Pietro I2OIM

Il giorno mer 20 apr 2022 alle ore 08:44 Evan Smith via groups.io <FAZAMY=
aol.com@groups.io> ha scritto:

Where is the location of the qsos you made in WSJT-X?
After a lot of trial and error I made several qsos that I logged.
I want to export the list of qsos onto XMLog.

Evan
KB2AMY

Windows 11
TS-480
--
Forgive me if you responded to my question. I couldn't find my question
and therefore couldn't get an answer.

My question:

When I try to activate WSJT-x I get the following: "Invalid audio input
device." How can I fix this?
-- TS-480.
-- Windows 11
-- Latest version of WSJT-x
-- Drivers updated

The output is OK.

I have used WSJT-x for many years with Windows 7.






locked Re: Where is the location of the WSJT-X log? #FT8 #logging

William Smith
 

Open the log directory and look for an adi file.

73, Willie N1JBJ

On Apr 20, 2022, at 2:44 AM, Evan Smith via groups.io <FAZAMY@...> wrote:

Where is the location of the qsos you made in WSJT-X?
After a lot of trial and error I made several qsos that I logged.
I want to export the list of qsos onto XMLog.

Evan
KB2AMY

Windows 11
TS-480
--
Forgive me if you responded to my question. I couldn't find my question and therefore couldn't get an answer.

My question:

When I try to activate WSJT-x I get the following: "Invalid audio input device." How can I fix this?
-- TS-480.
-- Windows 11
-- Latest version of WSJT-x
-- Drivers updated

The output is OK.

I have used WSJT-x for many years with Windows 7.





locked Re: Totally Stumped..Carrier with No AFSK #transmit

Dave Garber
 

does the 1000mp have a menu with the option of input from microphone or
rear connector??


Dave Garber
VE3WEJ / VE3IE

On Wed, Apr 20, 2022 at 8:39 AM Jim K2QB <nfjimc@...> wrote:


Thanks Mike I'll give this a try.
--
Jim K2QB






locked Re: Totally Stumped..Carrier with No AFSK #transmit

Jim K2QB
 

Thanks Mike I'll give this a try.
--
Jim K2QB


locked Re: Totally Stumped..Carrier with No AFSK #transmit

Michael Black
 

#1 Unplug the Signalink#2 Uninstall the USB Audio CODEC#3 Shut down #4 Plug Signalink back in#5 Boot#6 Check audio settings in WSJT-X and sound card settings in sound card control panel for 0dB level (right-click level slider) and 48kHz rate.  Also in sound control panel ensure USB Audio CODEC is not the default device (no green check marks on USB Audio CODEC).
On Windows 10 the last USB device plugged in automagically becomes the default.  So be sure SignaLink is plugged in BEFORE you boot the computer. 
Mike W9MDB

On Wednesday, April 20, 2022, 07:04:54 AM CDT, Jim K2QB <nfjimc@...> wrote:

Trying to get a fellow ham on FT8 and for the life of me can't figure this one out. I have been running both WJST-X and JTDX for several years, so I am very aware of all the little nuances like USB port power settings. His set up is a Yaesu FT1000MP with a SignalLink interface. Running Windows 10. We have had everything up and running fine and suddenly the other day it stopped working. He attributes it to a possible Windows update but I'm not so sure. WJSTX and JTDX both act the exact same way. When we hit tune or transmit the rig will key, the power meter shows a carrier/power out but there appears to be no actual AFSK. I've listened to him, and my waterfall shows nothing on his xmt frequency. I swear we have tried every sound setting in Windows with no luck. We've rebooted the PC, changed USB ports, and all the usual stuff. I'm almost thinking the SignalLink is faulty but seems unlikely. Any help would really be appreciated.
Thanks!

--
Jim K2QB


locked Re: Totally Stumped..Carrier with No AFSK #transmit

William Smith
 

Sounds like he’s on the wrong frequency if he’s outputting power. Maybe he’s in Lower Side Band mode?

73, Willie N1JBJ

On Apr 20, 2022, at 8:04 AM, Jim K2QB <nfjimc@...> wrote:

power meter shows a carrier/power out but there appears to be no actual AFSK. I've listened to him, and my waterfall shows nothing on his xmt frequency


locked Totally Stumped..Carrier with No AFSK #transmit

Jim K2QB
 

Trying to get a fellow ham on FT8 and for the life of me can't figure this one out. I have been running both WJST-X and JTDX for several years, so I am very aware of all the little nuances like USB port power settings. His set up is a Yaesu FT1000MP with a SignalLink interface. Running Windows 10. We have had everything up and running fine and suddenly the other day it stopped working. He attributes it to a possible Windows update but I'm not so sure. WJSTX and JTDX both act the exact same way. When we hit tune or transmit the rig will key, the power meter shows a carrier/power out but there appears to be no actual AFSK. I've listened to him, and my waterfall shows nothing on his xmt frequency. I swear we have tried every sound setting in Windows with no luck. We've rebooted the PC, changed USB ports, and all the usual stuff. I'm almost thinking the SignalLink is faulty but seems unlikely. Any help would really be appreciated.
Thanks!

--
Jim K2QB


locked Re: #linux #linux

Mike Sutherland
 

Problem solved
I got this message and followed the instructions
I suspect you are not selecting the correct serial port device for CAT in WSJT-X. Your screen capture shows "USB", that is definitely incorrect. I would guess that /dev/ttyUSB0 is the right one, that would be a USB to serial interface.

You also need to add your user to the 'dialout' group to be able to access serial devices:

sudo adduser $USER dialout

You must log out your desktop session and log back in for that to take effect, or simply reboot.

73
Bill
G4WJS.

--
73  VE3UET
FN03


locked #hamlib ERROR fix'r upper #hamlib

Mike Sutherland
 

I asked how to correct hamlib error on this group and on the WSJT-x facebook group and Brian Totten, shared this link with me

https://wsjtx.groups.io/g/main/topic/31843492?fbclid=IwAR00teZqrfhEbYxEWp6ubdratD4B6PRo8YIgSmUunWB8DGUUpShpHfYzvQ8

Ubuntu -- Hamlib error: IO error while opening connection to rig

I suspect you are not selecting the correct serial port device for CAT in WSJT-X. Your screen capture shows "USB", that is definitely incorrect. I would guess that /dev/ttyUSB0 is the right one, that would be a USB to serial interface.

You also need to add your user to the 'dialout' group to be able to access serial devices:

sudo adduser $USER dialout

You must log out your desktop session and log back in for that to take effect, or simply reboot.

73
Bill
G4WJS.

WoW!! I did that and now have my radio and computer talking like old buddies on 20 meters



--
73 Mike VE3UET
FN03


locked Where is the location of the WSJT-X log? #FT8 #logging

Evan Smith
 

Where is the location of the qsos you made in WSJT-X?
After a lot of trial and error I made several qsos that I logged.
I want to export the list of qsos onto XMLog.

Evan
KB2AMY

Windows 11
TS-480
--
Forgive me if you responded to my question.  I couldn't find my question and therefore couldn't get an answer.

My question:

When I try to activate WSJT-x I get the following:  "Invalid audio input device."  How can I fix this?
--  TS-480.
--  Windows 11
--  Latest version of WSJT-x
--  Drivers updated

The output is OK.

I have used WSJT-x for many years with Windows 7.


locked Re: Rig control issue with IC7800, WSJTx, & microham MKII #Cat_RigControl

Phil Cooper
 

Thanks Mike,

I will give it a try tomorrow. I have downloaded the file, which went just fine.

73 de Phil GU0SUP

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Michael Black via groups.io
Sent: 19 April 2022 14:33
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Rig control issue with IC7800, WSJTx, & microham MKII #Cat_RigControl

Try the latest hamlib...I made a change Nov 2021 where the rig's bandwidth is not supposed to change from what the user selects for Icom rigs.
New hamlib for Windows installation directions
#1 Shut down WSJTX/JTDX
#2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you multiple times.
If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there.
http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll
http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll
#3 If you don't save directly you need to open a file browser and move the file that way.
If you're not familiar with that here's a video on the file browser - https://www.youtube.com/watch?v=AyVqCJrs9dk
Mike W9MDB




On Tuesday, April 19, 2022, 08:20:09 AM CDT, Phil Cooper via groups.io <pcooper@...> wrote:

Hi all,

New to this group, and as you would expect, I have a weird issue which I need help with...
Let me see if I can explain it -

I have been using WSJTx & JTAlert for ages now, and when I changed to a new PC with Win10Pro 64bit, I had an issue with rig control, so I ended up using the DXLab Commander to control the rig, which works just fine.
However, over the Easter weekend, I decided to see if I could see what was going on with the native rig control.
It seems that I had the stop bit set wrong, and after correcting that, I managed to get rig control.

BUT.... with DXLab Commander, everything works as it should, and yet, when I use the native rig control, my radio goes to a narrow filter on TX, and then sets the RX filter to the same setting. If I change band, and set the wide filter, it will change to the narrow filter as soon as I transmit.

Going back to Commander, this behaviour is normal, and works without changing the filter.

I have looked everywhere to see what may be causing the narrow filter to be used, but I cannot see any setting for this in WSJTx. I have tried without JTAlert, and the same issue occurs, so I have to assume that it is something in WSJTx that is causing the narrow filter to be activated.

Has anyone got any thoughts please?

73 de Phil GU0SUP


locked Re: #raspberryPi #WSPR v2.3.0 - Band Hoping Schedule window is not displayed #raspberryPi #WSPR

gareth.pale <gareth.paley@...>
 

Success.

When I had version 2.5.4 installed although I couldn't get it to connect to
my rig I was able to get the schedule window up briefly and enter what I
wanted - 40m and 20m simultaneously on morning and evening greyline and 20m
day time and 40m night time.

After I removed version 2.5.4 I noticed that all the settings persisted
when I installed v 2.3.0 - a config file must have been left somewhere and
not removed under the automated de-install.

Now I'm running WSJT-X version 2.0.0 would you believe. It picked it up in
the add/remove applications when I searched for wsjtx. Rig control is fine
and I can tick band hoping but it doesn't bring up the schedule but the
schedule is there nonetheless.

I'm happy now. I can free up my PC for other things and just have the
raspberry running my WSPR beacon.

Thanks all
de M0WWS

On Tue, Apr 19, 2022 at 7:56 PM Brian Morrison <bdm@...> wrote:

On Tue, 19 Apr 2022 18:45:37 +0100
"gareth.pale" <gareth.paley@...> wrote:

I think I'm going to unistall and go back to 2.3.0 as I can live without
scheduled band hopping but it's useless without CAT control.
Which hamlib version are you using Gareth? The 4.5~git version has had
a lot of changes, so if you can try the current git version in place of
whatever the Pi currently uses it might behave better.

--

Brian G8SEZ






locked Re: Three character call sign in WSPR? #WSPR

Bruce KX4AZ
 

On Tue, Apr 19, 2022 at 04:15 PM, Ron wrote:
I guess I should have added - are you talking about special event 1x1
callsigns?
Yes, 1x1 call signs, such as the one I am currently working with, N1D. I have several queries about this posted on WSPR-related forums, and I surmise it may simply turn out to be a flaw in the current client decoder. It is interesting that a 1x1 call sign works fine for uploading spots and sending WSPR transmissions....but only certain (probably very old) clients will DECODE a 1x1 call sign, such as the one built into the KiwiSDR. The simplest workaround may be to use a compound call sign, such as N1D/KD4QHB.


locked Re: #FT4 #transmit #stopped_working #FT4 #transmit #stopped_working

Jeff Kaplan
 

The WSJT-X_RigControl.log file is an empty text file I created. I also
gave the wsjtx_log_config.ini file the chance to create the log file. I
tried both ways.

WSJT-X_RigControl.log that I manually created on the second attempt was
placed in C:/Users/<me>/AppData/Local/WSJT-X folder.

The file you placed in the drop box that writes to the log is named
wsjtx_log_config.ini. I placed this in both:

C:/Users/<me>/AppData/Local/WSJT-X
C:WSJT/wsjtx/bin/

The updated lib_hamlib4.dll was used.

The files were placed while WSJTX program was closed.

I then started the program and placed the split operation to Rig Control
and the mode to FT-4. I clicked the monitor button on to green. I hit
enable transmit.

The program tried to change frequencies several times without success. It
did succeed to transmit once but it struggled and failed many times.

I closed the program and found the log file was not created by the ini
file, and the log file which I manually created on a second attempt was
also empty.

Please do you know what I did wrong. I did database program in the 1990’s
using Windows NT, so I have a basic idea how this should work. Either I
named something wrong or put it in the wrong place, or maybe fid something
in the wrong order,

On Tue, Apr 19, 2022 at 4:07 PM Michael Black via groups.io <mdblack98=
yahoo.com@groups.io> wrote:

That file would go in AppData/Local/WSJT-X
Mike W9MDB



On Tuesday, April 19, 2022, 03:03:09 PM CDT, Jeff Kaplan <
jkaplan1320@...> wrote:

Placed the wsjx_log_config.ini file from downloaded from drop box into
both folders. It did not generate the log file or fill the log file I then
created myself and placed in the ~<me>/appdat/local file you described.
Perhaps I misunderstood what you wanted?












locked Re: Three character call sign in WSPR? #WSPR

Ron
 

I guess I should have added - are you talking about special event 1x1
callsigns?

Ron - KJ5XX

On Tue, Apr 19, 2022, 1:55 PM Bruce KX4AZ <bruce@...> wrote:

I'm trying to operate a WSPR beacon for a special event station (N1D). It
appears that the decoder in WSJT-x does not accept the use of a three
letter call sign. The only spots I am getting are from (older?) decoders
such as what is built into a KiwiSDR receiver. Wonder if this limitation
is documented anywhere? Of course, the workaround would be to append a
special suffix to the call sign.






locked Re: #FT4 #transmit #stopped_working #FT4 #transmit #stopped_working

Michael Black
 

That file would go in AppData/Local/WSJT-X
Mike W9MDB

On Tuesday, April 19, 2022, 03:03:09 PM CDT, Jeff Kaplan <jkaplan1320@...> wrote:

Placed the wsjx_log_config.ini file from downloaded from drop box into both folders.  It did not generate the log file or fill the log file I then created myself and placed in the ~<me>/appdat/local file you described.  Perhaps I misunderstood what you wanted?


locked Re: #FT4 #transmit #stopped_working #FT4 #transmit #stopped_working

Jeff Kaplan
 

Placed the wsjx_log_config.ini file from downloaded from drop box into both folders. It did not generate the log file or fill the log file I then created myself and placed in the ~<me>/appdat/local file you described. Perhaps I misunderstood what you wanted?


locked Re: Three character call sign in WSPR? #WSPR

William Smith
 

I kinda thought he was talking about N1D, as per the first line of his original missive...

73, Willie N1JBJ

On Apr 19, 2022, at 3:53 PM, Ron <ron@...> wrote:

What do you mean by a "three letter callsign".

Are you talking about a 1 by three or a two by three such as:

K5OXM
or
KL7ETX?

An example would be helpful.

Ron - KJ5XX


On Tue, Apr 19, 2022, 1:55 PM Bruce KX4AZ <bruce@...> wrote:

I'm trying to operate a WSPR beacon for a special event station (N1D). It
appears that the decoder in WSJT-x does not accept the use of a three
letter call sign. The only spots I am getting are from (older?) decoders
such as what is built into a KiwiSDR receiver. Wonder if this limitation
is documented anywhere? Of course, the workaround would be to append a
special suffix to the call sign.

Ron - KJ5XX


locked Re: Three character call sign in WSPR? #WSPR

Ron
 

What do you mean by a "three letter callsign".

Are you talking about a 1 by three or a two by three such as:

K5OXM
or
KL7ETX?

An example would be helpful.

Ron - KJ5XX

On Tue, Apr 19, 2022, 1:55 PM Bruce KX4AZ <bruce@...> wrote:

I'm trying to operate a WSPR beacon for a special event station (N1D). It
appears that the decoder in WSJT-x does not accept the use of a three
letter call sign. The only spots I am getting are from (older?) decoders
such as what is built into a KiwiSDR receiver. Wonder if this limitation
is documented anywhere? Of course, the workaround would be to append a
special suffix to the call sign.





Ron - KJ5XX


locked Re: Three character call sign in WSPR? #WSPR

William Smith
 

Actually, according to https://www.codeproject.com/Articles/1200310/Creating-WSPR-Message-in-Cplusplus you can prepend a space, noting that the third character must be numeric. I hope that's not just for this particular code, but give it a try...

73, Willie N1JBJ

On Apr 19, 2022, at 2:55 PM, Bruce KX4AZ <bruce@...> wrote:

I'm trying to operate a WSPR beacon for a special event station (N1D). It appears that the decoder in WSJT-x does not accept the use of a three letter call sign. The only spots I am getting are from (older?) decoders such as what is built into a KiwiSDR receiver. Wonder if this limitation is documented anywhere? Of course, the workaround would be to append a special suffix to the call sign.

4641 - 4660 of 38068