Date   

locked Re: Linux Serial Port Issues

jgrantham@...
 

If you have FLRig working, launch that and then set WSJT-x to use FLRig as the radio. Works great.


From: WSJTX@groups.io <WSJTX@groups.io> on behalf of Mark Erbaugh <mark.election@...>
Sent: Monday, May 11, 2020 7:41:33 AM
To: WSJTX@groups.io <WSJTX@groups.io>
Subject: [WSJTX] Linux Serial Port Issues
 

I am building a Raspberry Pi 4 to serve as a portable data terminal. For more information, see KM4ACK’s YouTube video and his pi-build script on GitHub (www.github.com/km4ack/pi-build).

 

The rig is an Elecraft KX3. The interface is a Timewave Navigator. The Navigator provides multiple FTDI USB/serial ports, one of which provides a CAT interface to the rig. Just to eliminate the Navigator as the problem, I also tried the standard Elecraft KXUSB interface cable, which also provides a FDTI USB serial port. (the Navigator and KXUSB were not connected at the same time).

 

With the interface cable plugged in to the RPi, I did dmesg and saw that the serial ports were correctly associated with the FTDI drivers.

 

I did the “usermod -a -G dialout pi” to add my local user (pi) to the dialout group for access to the serial ports.

 

FLRig is able to access the CAT interface and control the KX3.

 

I exit FLRig and launch WSJT-X. Under rig setup, I specify the correct serial port (/dev/ttyUSB0) and baud rate. I click the Test CAT button and it doesn’t change color – neither red nor green. Sometimes, this disables the Test PTT button, but when it doesn’t toggling the Test PTT button toggles Tx on the KX3.

 

Back on the WSJT-X  main screen, the frequency mirrors the KX3’s frequency, changes to frequency on the radio change in WSJT-X and vice versa, but the “fake it” split mode doesn’t work.

 

This is with WSJT-X 2.1.10 which was built from source code. The RPi 4 is running Raspian Buster which has been updated with the latest changes.

 

For comparison, I installed WSJT-X 2.1.12 from the .deb file on the website onto a desktop computer running Linux Mint 19. I saw the same problems. Again FLRig worked fine.

 

I did various things such as changing the owner of the serial ports to the local user and changing the group of the serial ports to the local user – no change.

 

I started WSJT-X using sudo and the Test CAT button worked and turned green, so I think there may still be a permission issue.

 

Thanks for any suggestions, 73,

Mark, N8ME

 

 

 

 


locked Re: JT Alert Question

John Morphet
 

This depends if JTAlert uses all.txt. I would ask the question on the JTalert forum. Secondly, If you really have to delete it, I would not. I would save it off somewhere else and start with a fresh file. What about the WSJTX_log.adi file? Are you really having a space problem? Most modern operating systems today can handle a very large file size. If you are running out of hard drive space. There are probably much larger candidates you could look at or get a larger hard drive.

 

John, WØZI

 

From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of Bill
Sent: Monday, May 11, 2020 9:26 AM
To: WSJTX@groups.io
Subject: [WSJTX] JT Alert Question

 

I know I'm on the wrong forum, but I don't see how to post on the JTAlert forum.

My question is simple and it has to do with the "All.txt" file.

It is getting very large and would like to know, what happens, if anything if I erase it ?

Bill
K2WH


locked Re: WSJT-X 2.2.0-rc1

J. JAVIER CAMARENA Q. <xe2cq@...>
 

GRACIAS Joe it's running now.
73 de Javier

CTA./PA. JOSE JAVIER CAMARENA QUIÑONES Jr.
TIJUANA/MMTJEmojiEmojiEmojiEmoji
MÉXICO

AMATEUR RADIO 
XE2CQ



On Monday, May 11, 2020, 07:53:29 AM PDT, Joe <joe@...> wrote:


WSJT-X 2.2.0 will be a significant program upgrade offering many new
features.

The first candidate release, WSJT-X 2.2.0-rc1, is now available for
download and use by beta testers.  This candidate release is your first
chance to test the new features and provide feedback to the WSJT
Development Group.

A list of program changes since WSJT-X 2.1.2 can be found in the
cumulative Release Notes
... and also in the updated WSJT-X 2.2.0 User Guide here:

Upgrading from earlier versions of WSJT-X should be seamless.  There is
no need to uninstall a previous version or move any files.  You might
want to install to a different directory from your WSJT-X 2.1.2
installation.

Links to installation packages for Windows, Linux, and Macintosh are
available here:
Scroll down to find "Candidate release:  WSJT-X 2.2.0-rc1".

You can also download the packages from our SourceForge site:
It may take a short time for the SourceForge site to be updated.

WSJT-X is licensed under the terms of Version 3 of the GNU General
Public License (GPL).  Development of this software is a cooperative
project to which many amateur radio operators have contributed.  If you
use our code, please have the courtesy to let us know about it.  If you
find bugs or make improvements to the code, please report them to us in
a timely fashion.

We hope you will enjoy using this beta release of WSJT-X 2.2.0.  Please
report bugs by following instructions found here in the User Guide:

      -- 73 from Joe, K1JT, Steve, K9AN, and Bill, G4WJS, for the
                        WSJT Development Group


locked Re: Curved Line in Waterfall

Dave_G0WBX
 

Re:-

Is there a PC program to measure drift using WWV as a calibrated source?

Though WSJTx has some functionality, I've not seen anything in it to
calibrate for any sound card sample rate discrepancy.  (Unless I've just
not found it yet.)

However.  Fldigi has a frequency measuring and recording function.   It
also does allow you to correct for the sound card's "Actual" sample rate
against any of the usual broadcast Standard Frequency and Time stations.

73.

Dave G0WBX.


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


locked Re: v2.2.0.rc1 fake it setting not working

Dave (NK7Z)
 

Yes, I am surprised at how fast the RC1 decodes! I am seeing decodes well before the transmit cycle begins... A very nice improvement in performance.

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

On 5/11/20 9:22 AM, Jim AF5FH wrote:
[Edited Message Follows]
After restarting all the ham software, I am no longer seeing this issue. Sorry, you can delete this topic!
And Dave NK7Z is correct, decodes are noticeably faster.
73,
Jim AF5FH


locked Re: Linux Serial Port Issues

Bill Somerville
 

Hi Mark,

so, to sure, the "Test CAT" button is not turning green, and yet the "Test PTT " button is becoming enabled. That should only happen if the "PTT Method" is not "CAT" or "VOX". What do you have "Settings->Radio->PTT Method" set to?

73
Bill
G4WJS.

On 11/05/2020 17:25, Mark Erbaugh wrote:
No error message. The only thing that happens is that the Test PTT button becomes active.


On May 11, 2020, at 11:23 AM, Bill Somerville <g4wjs@...> wrote:


On 11/05/2020 15:30, Mark Erbaugh wrote:

Kari,

 

Thanks for the reply. See below.

You issuded "sudo usermod ..", right?
After that, did you log off and on again?
Does command 'id' show 'dialout' as one of your groups now?
 

I’m not sure I had logged off and back on, but I did just now.

 

Id shows that pi is a member of the dialout group

 
What does command 'ls -ltr /dev/tty*' show when you have
the KUSB cable connected?
 

crw-rw---- 1 root dialout 188, 0 May 11 10:19 /dev/ttyUSB0

 

What exactly does not work? How did you test?

 

I retested, and it seems the only thing not working is the Test CAT button.

 

73,

Mark

Hi Mark,

if the "Test CAT " button is not working then you should be getting an error message window. What does that error message window say, including the text revealed by the "Show Details ..." button?

73
Bill
G4WJS.



locked Re: Linux Serial Port Issues

Mark Erbaugh <mark.election@...>
 

No error message. The only thing that happens is that the Test PTT button becomes active.


On May 11, 2020, at 11:23 AM, Bill Somerville <g4wjs@...> wrote:


On 11/05/2020 15:30, Mark Erbaugh wrote:

Kari,

 

Thanks for the reply. See below.

You issuded "sudo usermod ..", right?
After that, did you log off and on again?
Does command 'id' show 'dialout' as one of your groups now?
 

I’m not sure I had logged off and back on, but I did just now.

 

Id shows that pi is a member of the dialout group

 
What does command 'ls -ltr /dev/tty*' show when you have
the KUSB cable connected?
 

crw-rw---- 1 root dialout 188, 0 May 11 10:19 /dev/ttyUSB0

 

What exactly does not work? How did you test?

 

I retested, and it seems the only thing not working is the Test CAT button.

 

73,

Mark

Hi Mark,

if the "Test CAT " button is not working then you should be getting an error message window. What does that error message window say, including the text revealed by the "Show Details ..." button?

73
Bill
G4WJS.



locked Re: v2.2.0.rc1 fake it setting not working

Bill Somerville
 

On 11/05/2020 17:22, Jim AF5FH wrote:

[Edited Message Follows]

After restarting all the ham software, I am no longer seeing this issue. Sorry, you can delete this topic!

And Dave NK7Z is correct, decodes are noticeably faster.

73,
Jim AF5FH
Hi Jim,

thanks for the update. I will wait to see if other have similar strange behaviour before investigating further. Glad you are up and running now, thanks for the issue report.

73
Bill
G4WJS.


locked Re: v2.2.0.rc1 fake it setting not working

Jim AC9ZL
 
Edited

After restarting all the ham software, I am no longer seeing this issue. Sorry, you can delete this topic!

And Dave NK7Z is correct, decodes are noticeably faster.

73,
Jim AF5FH


locked Re: V2.2.0 rc1 error on start up (32 bit)

Bill Somerville
 

Hi Bob,

ah, so not a hardware restriction, just an excuse to splash out on a shiny new rig, hi hi.

73
Bill
G4WJS.

On 11/05/2020 17:07, Bob G8HGN wrote:

Hi Bill,

I'm using an FT-847 with a RigBlaster Pro on the 32 bit set up with a RS232 to USB converter. I use it for 144/432 only.

It'll will work with the new PC, but I was going for an IC-9700 as a rig upgrade before the lockdown and as of now haven't persued it as yet.

73

Bob G8HGN



On 11/05/2020 16:56, Bill Somerville wrote:
Hi Bob,

what stops you using your old rig with a newer PC, that seems a strange restriction?

73
Bill
G4WJS.

On 11/05/2020 16:55, Bob G8HGN wrote:

Hi Bill,

I did read that when the initial announcement was made, but forgot about it in the last few days to actual release, so aologies for the query. At least others will see it and not have to ask.

I understand the reasoning, I'll just have to use the old version until I get a new rig I can use with the newer PC.

Thanks for the quick reply, 73

Bob G8HGN

On 11/05/2020 16:48, Bill Somerville wrote:
On 11/05/2020 16:35, Bob G8HGN wrote:
Hi,

Have just downloaded the new rc1, and the 64 bit version is working on
my W10 64 bits PC, but the 32 bit version is not on my Vista 32 bit laptop.

I get an error message as in the attached screengrab.

Bob G8HGN
Hi Bob,

as stated on the WSJT-X web page https://physics.princeton.edu/pulsar/K1JT/wsjtx.html and on the SourceForge files area README information https://sourceforge.net/projects/wsjt/files/wsjtx-2.2.0-rc1/ , WSJT-X v2.2.0 is only supported on Windows 7 or later. We have been trailing removal of support for both Windows XP and Windows Vista for a number of releases, and as Windows 7 is now out of support and MS having three later releases of Windows in the field (8, 8.1 and 10); that time has come.

We have had to make this choice because supporting the latest versions of Windows, particularly the 64-bit version of WSJT-X, which has considerable performance advantages, makes support back to ancient and insecure operating system versions more trouble that it is worth. Specifically we do not wish to limit features and performance on newer operating systems just to support a few users of older systems.

73
Bill
G4WJS.


locked Re: V2.2.0 rc1 error on start up (32 bit)

Bob G8HGN
 

Hi Bill,

I'm using an FT-847 with a RigBlaster Pro on the 32 bit set up with a RS232 to USB converter. I use it for 144/432 only.

It'll will work with the new PC, but I was going for an IC-9700 as a rig upgrade before the lockdown and as of now haven't persued it as yet.

73

Bob G8HGN



On 11/05/2020 16:56, Bill Somerville wrote:
Hi Bob,

what stops you using your old rig with a newer PC, that seems a strange restriction?

73
Bill
G4WJS.

On 11/05/2020 16:55, Bob G8HGN wrote:

Hi Bill,

I did read that when the initial announcement was made, but forgot about it in the last few days to actual release, so aologies for the query. At least others will see it and not have to ask.

I understand the reasoning, I'll just have to use the old version until I get a new rig I can use with the newer PC.

Thanks for the quick reply, 73

Bob G8HGN

On 11/05/2020 16:48, Bill Somerville wrote:
On 11/05/2020 16:35, Bob G8HGN wrote:
Hi,

Have just downloaded the new rc1, and the 64 bit version is working on
my W10 64 bits PC, but the 32 bit version is not on my Vista 32 bit laptop.

I get an error message as in the attached screengrab.

Bob G8HGN

Hi Bob,

as stated on the WSJT-X web page https://physics.princeton.edu/pulsar/K1JT/wsjtx.html and on the SourceForge files area README information https://sourceforge.net/projects/wsjt/files/wsjtx-2.2.0-rc1/ , WSJT-X v2.2.0 is only supported on Windows 7 or later. We have been trailing removal of support for both Windows XP and Windows Vista for a number of releases, and as Windows 7 is now out of support and MS having three later releases of Windows in the field (8, 8.1 and 10); that time has come.

We have had to make this choice because supporting the latest versions of Windows, particularly the 64-bit version of WSJT-X, which has considerable performance advantages, makes support back to ancient and insecure operating system versions more trouble that it is worth. Specifically we do not wish to limit features and performance on newer operating systems just to support a few users of older systems.

73
Bill
G4WJS.




    


locked Re: v2.2.0.rc1 fake it setting not working

Bill Somerville
 

On 11/05/2020 16:53, Jim AF5FH wrote:
Downloaded v2.2.0.rc1, told MS Smart Screen that it was safe, installed on Windows 10 v1909 laptop. While making 3 contacts using FT8 on 30 meters, I see that the Settings, Radio, Split Operation, Fake It is set in software. However, there is approximately 2 second delay switching from receive to transmit, and Commander 14.5.8 is showing that WSJT-X is switching the VFO from A to B for transmit, and switching the VFO from B to A for receive. The front panel of the Icom 7200 is also displaying this.

Fake It setting is now working like Rig setting. This introduces a delay of about  2 seconds in switching from receive to transmit on Icom 7200. The previous released version of WSJT-X did not do this. I tried setting it to None, and then setting it back to Fake It, but the behavior did not change.

This new "feature" in the software did not prevent me from completing 3 contacts, and JTAlert 2.16.5 is working with v2.2.0.rc1 and DXLab Suite, uploading to eQSL and LoTW automatically after each contact, and one of my new contacts has already confirmed via eQSL and LoTW, so I am confident all this is working.

73,
Jim AF5FH
Hi Jim,

there have been no changes since WSJT-X v2.1.2 in that area so I suspect what you are seeing is the result of an issue with Hamlib. I need to get some information from you about what is going on, I will get back to you shortly about that.

73
Bill
G4WJS.


locked Re: v2.2.0.rc1 fake it setting not working

Dave (NK7Z)
 

Hi,

I have noticed decodes happening prior to the transmit window, (as a result of the faster decoding), could this be what you are seeing?

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

On 5/11/20 8:53 AM, Jim AF5FH wrote:
Downloaded v2.2.0.rc1, told MS Smart Screen that it was safe, installed on Windows 10 v1909 laptop. While making 3 contacts using FT8 on 30 meters, I see that the Settings, Radio, Split Operation, Fake It is set in software. However, there is approximately 2 second delay switching from receive to transmit, and Commander 14.5.8 is showing that WSJT-X is switching the VFO from A to B for transmit, and switching the VFO from B to A for receive. The front panel of the Icom 7200 is also displaying this.
Fake It setting is now working like Rig setting. This introduces a delay of about  2 seconds in switching from receive to transmit on Icom 7200. The previous released version of WSJT-X did not do this. I tried setting it to None, and then setting it back to Fake It, but the behavior did not change.
This new "feature" in the software did not prevent me from completing 3 contacts, and JTAlert 2.16.5 is working with v2.2.0.rc1 and DXLab Suite, uploading to eQSL and LoTW automatically after each contact, and one of my new contacts has already confirmed via eQSL and LoTW, so I am confident all this is working.
73,
Jim AF5FH


locked Re: V2.2.0 rc1 error on start up (32 bit)

Bill Somerville
 

Hi Bob,

what stops you using your old rig with a newer PC, that seems a strange restriction?

73
Bill
G4WJS.

On 11/05/2020 16:55, Bob G8HGN wrote:

Hi Bill,

I did read that when the initial announcement was made, but forgot about it in the last few days to actual release, so aologies for the query. At least others will see it and not have to ask.

I understand the reasoning, I'll just have to use the old version until I get a new rig I can use with the newer PC.

Thanks for the quick reply, 73

Bob G8HGN

On 11/05/2020 16:48, Bill Somerville wrote:
On 11/05/2020 16:35, Bob G8HGN wrote:
Hi,

Have just downloaded the new rc1, and the 64 bit version is working on
my W10 64 bits PC, but the 32 bit version is not on my Vista 32 bit laptop.

I get an error message as in the attached screengrab.

Bob G8HGN
Hi Bob,

as stated on the WSJT-X web page https://physics.princeton.edu/pulsar/K1JT/wsjtx.html and on the SourceForge files area README information https://sourceforge.net/projects/wsjt/files/wsjtx-2.2.0-rc1/ , WSJT-X v2.2.0 is only supported on Windows 7 or later. We have been trailing removal of support for both Windows XP and Windows Vista for a number of releases, and as Windows 7 is now out of support and MS having three later releases of Windows in the field (8, 8.1 and 10); that time has come.

We have had to make this choice because supporting the latest versions of Windows, particularly the 64-bit version of WSJT-X, which has considerable performance advantages, makes support back to ancient and insecure operating system versions more trouble that it is worth. Specifically we do not wish to limit features and performance on newer operating systems just to support a few users of older systems.

73
Bill
G4WJS.


locked Re: V2.2.0 rc1 error on start up (32 bit)

Bob G8HGN
 

Hi Bill,

I did read that when the initial announcement was made, but forgot about it in the last few days to actual release, so aologies for the query. At least others will see it and not have to ask.

I understand the reasoning, I'll just have to use the old version until I get a new rig I can use with the newer PC.

Thanks for the quick reply, 73

Bob G8HGN

On 11/05/2020 16:48, Bill Somerville wrote:
On 11/05/2020 16:35, Bob G8HGN wrote:
Hi,

Have just downloaded the new rc1, and the 64 bit version is working on
my W10 64 bits PC, but the 32 bit version is not on my Vista 32 bit laptop.

I get an error message as in the attached screengrab.

Bob G8HGN

Hi Bob,

as stated on the WSJT-X web page https://physics.princeton.edu/pulsar/K1JT/wsjtx.html and on the SourceForge files area README information https://sourceforge.net/projects/wsjt/files/wsjtx-2.2.0-rc1/ , WSJT-X v2.2.0 is only supported on Windows 7 or later. We have been trailing removal of support for both Windows XP and Windows Vista for a number of releases, and as Windows 7 is now out of support and MS having three later releases of Windows in the field (8, 8.1 and 10); that time has come.

We have had to make this choice because supporting the latest versions of Windows, particularly the 64-bit version of WSJT-X, which has considerable performance advantages, makes support back to ancient and insecure operating system versions more trouble that it is worth. Specifically we do not wish to limit features and performance on newer operating systems just to support a few users of older systems.

73
Bill
G4WJS.



    


locked Re: Curved Line in Waterfall

Dave (NK7Z)
 

Pretty much, if all the traces are tilted in the same direction, it is probably your radio drifting. If you have a few straight traces, and a pile of tilted traces, the radio is probably not drifting, but still a bit suspect...

Just watch things for a bit, if in the whole you are seeing all traces tilt, the radio is drifting.

I was seeing that now and then, I changed to a TXCO, and have not seen it again.

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

On 5/11/20 8:27 AM, Gary - AG0N wrote:

On May 11, 2020, at 05:58, Samuel KJ4VPI <sernstfortin@...> wrote:

Has anyone else noticed some slight variation in received messages in WSJT-X well after warmup? I'm noting a little tilting, and I wonder if the radio is experiencing a little thermal drift. Is there a PC program to measure drift using WWV as a calibrated source?
There’ll be those who say to use the Freq Cal mode, but you don’t even need that if you’re just looking for large drift. Take the VFO and shove it to your nearest friendly neighborhood WWV/CHU frequency, tune off center by 1000 or 1500 (whatever you want), and just leave it. If the radio is drifting, you should be able to see it right away. If it is a long term deal, park it for an hour, or hours, and see what it does over time. If you use the Freq Cal mode, it will read out the tone frequency in decimals of cycles so you can see precisely what it is doing.
Gary - AG0N


locked v2.2.0.rc1 fake it setting not working

Jim AC9ZL
 

Downloaded v2.2.0.rc1, told MS Smart Screen that it was safe, installed on Windows 10 v1909 laptop. While making 3 contacts using FT8 on 30 meters, I see that the Settings, Radio, Split Operation, Fake It is set in software. However, there is approximately 2 second delay switching from receive to transmit, and Commander 14.5.8 is showing that WSJT-X is switching the VFO from A to B for transmit, and switching the VFO from B to A for receive. The front panel of the Icom 7200 is also displaying this. 

Fake It setting is now working like Rig setting. This introduces a delay of about  2 seconds in switching from receive to transmit on Icom 7200. The previous released version of WSJT-X did not do this. I tried setting it to None, and then setting it back to Fake It, but the behavior did not change.

This new "feature" in the software did not prevent me from completing 3 contacts, and JTAlert 2.16.5 is working with v2.2.0.rc1 and DXLab Suite, uploading to eQSL and LoTW automatically after each contact, and one of my new contacts has already confirmed via eQSL and LoTW, so I am confident all this is working.

73,
Jim AF5FH


locked Re: V2.2.0 rc1 error on start up (32 bit)

Bill Somerville
 

On 11/05/2020 16:35, Bob G8HGN wrote:
Hi,

Have just downloaded the new rc1, and the 64 bit version is working on
my W10 64 bits PC, but the 32 bit version is not on my Vista 32 bit laptop.

I get an error message as in the attached screengrab.

Bob G8HGN
Hi Bob,

as stated on the WSJT-X web page https://physics.princeton.edu/pulsar/K1JT/wsjtx.html and on the SourceForge files area README information https://sourceforge.net/projects/wsjt/files/wsjtx-2.2.0-rc1/ , WSJT-X v2.2.0 is only supported on Windows 7 or later. We have been trailing removal of support for both Windows XP and Windows Vista for a number of releases, and as Windows 7 is now out of support and MS having three later releases of Windows in the field (8, 8.1 and 10); that time has come.

We have had to make this choice because supporting the latest versions of Windows, particularly the 64-bit version of WSJT-X, which has considerable performance advantages, makes support back to ancient and insecure operating system versions more trouble that it is worth. Specifically we do not wish to limit features and performance on newer operating systems just to support a few users of older systems.

73
Bill
G4WJS.


locked Re: Curved Line in Waterfall

Gary - AG0N
 

On May 11, 2020, at 09:27, Gary - AG0N <mcduffie@...> wrote:



On May 11, 2020, at 05:58, Samuel KJ4VPI <sernstfortin@...> wrote:

Has anyone else noticed some slight variation in received messages in WSJT-X well after warmup? I'm noting a little tilting, and I wonder if the radio is experiencing a little thermal drift. Is there a PC program to measure drift using WWV as a calibrated source?
There’ll be those who say to use the Freq Cal mode, but you don’t even need that if you’re just looking for large drift. Take the VFO and shove it to your nearest friendly neighborhood WWV/CHU frequency, tune off center by 1000 or 1500 (whatever you want), and just leave it. If the radio is drifting, you should be able to see it right away. If it is a long term deal, park it for an hour, or hours, and see what it does over time. If you use the Freq Cal mode, it will read out the tone frequency in decimals of cycles so you can see precisely what it is doing.

By the way, drifting should not change anything WSJT-X presents to you in the form of a message. The only thing you should see WSJT-X do is show you a different DF each receive cycle for a given signal that is not really moving.

Gary


locked Re: JT Alert Question

Bill Somerville
 

On 11/05/2020 16:26, Bill wrote:

I know I'm on the wrong forum, but I don't see how to post on the JTAlert forum.

My question is simple and it has to do with the "All.txt" file.

It is getting very large and would like to know, what happens, if anything if I erase it ?

Bill
K2WH
Hi Bill,

I'm not sure why you think your query has anything to do with JTAlert, the ALL.TXT file in the WSJT-X log files directory is a WSJT-X file. WSJT-X writes all decoded messages along with transmitted messages to that file, it is a journal of your operation, as such I recommend that you keep the contents. There is no need to keep the contents all in the ALL.TXT file, for example you might choose to archive the file to an offline storage media once a year. I recommend keeping the contents of the ALL.TXT file indefinitely as it can be very useful for clarifying future queries about completed, or otherwise, QSOS. WSJT-X only writes to the ALL.TXT file, unlike the wsjtx_log.adi log file which is used to determine which stations and related entities you have worked before.

73
Bill
G4WJS.