Date   

locked Re: lost my WSJTX logbook #logging

Williams, G (af8c) <af8c@...>
 

A bit of bad news is that a file that is lost may not be able to be recovered.  Making backups has to be done before a calamity.

I don't know everything about file recovery, but I believe that if you are using a spinning magnetic disk hard drive and not an SSD, it might be possible to recover some of your log because on magnetic disks files are erased by marking only the directory links as empty rather than writing blank data into the formerly used disk sectors where the data was.  So there at least used to be software that could scan a hard drive and reassemble and reconnect the directory links to unmark the data sectors as no longer empty.  It's also a way to recover data off a hard drive for forensic reasons. The other bad news is that the longer you wait it is more likely for disk sectors that held your log data may  be overwritten when new files are stored to disk.

A big  background benefit of using LOTW is you will effectively have a backup there, so that you can download your entire log from LOTW.  Anyone can tell us if I am wrong about that.

I have left in previous weeks a note on this reflector on how you can use a DOS COMMAND PROMPT script to make a date and time stamped copy of your WSJT-X log files. But no matter how you do it, backup files with modified file names will prevent WSJT-X from overwriting your log file.  When it's too late, it may be too late.  Any backup copies of files can be protected as READ ONLY with the file PROPERTIES menu selection.  READ ONLY files will not be overwritten nor erased in ordinary use.

--73, Glenn, AF8C

On 3/25/2022 12:59 PM, w5pwh via groups.io wrote:
Good morning all!
I accidentally erased my logbook on WSJTX
now when i am on ft8 it is look starting over
Please tell me there is a way to get my past logbook back
Dan
W5PWH



--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


locked calling myself in RX Frequency window #IssueReport

Williams, G (af8c) <af8c@...>
 

This has happened only twice with V2.5.4.  No other times with prior releases.

I was using WIndows 10 USB to Kenwood TS590SG with FT8.   Enable TX was green and I was transmitting  After several unsuccessful transmissions I decided I wanted to stop transmitting.  I clicked Halt TX before the transmission period finished. Then I did some other operation which I don't remember but all of sudden I got the red bar in the Rx Frequency window and the Band Activity window. However, it was a red bar with my call sign on the right.  The first time it happened it appears that I was calling my own call sign, twice  The other time it happened was in the last 24 hours or so.  The text was fine, but the bar was red, not yellow. Those are the only times during thousands of transmissions and those two events were months apart. Sorry I should have done a screen copy but I didn't think of it.

Rather than expose other call signs here to the world, I can send a transcript from ALL.TXT for the first one to any of the developer group in a private email.

The second example will not be able to be found because ALL.TXT does not show color.

--73, Glenn, AF8C


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


locked Re: lost my WSJTX logbook #logging

Michael Black
 

The  LOTW file does not contain time.

Mike W9MDB

On Friday, March 25, 2022, 05:36:01 PM CDT, Eugene Morgan <ee_morgan@...> wrote:





I was able to rebuild my WSJT-X log by using my QRZ log book.  I exported my log book and pull out all of my digital QSO's along with only the fields that WSJT-X uses.  Of course I did this using some simple code that I wrote but I think it would also be possible using Excel.

I also don't see any reason you couldn't use and export from LOTW but I have to admit I've not do it using an LoTW ADI file.

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of w5pwh via groups.io
Sent: Friday, March 25, 2022 11:00 AM
To: main@WSJTX.groups.io
Subject: [WSJTX] lost my WSJTX logbook #logging

Good morning all!
I accidentally erased my logbook on WSJTX now when i am on ft8 it is look starting over Please tell me there is a way to get my past logbook back Dan W5PWH


locked WSJTX terminates on UBUNTU 20.04 #wsjt-x-crashing #linux

Ron McMurdy
 

Updated to latest version and after approx 30 minutes of use terminates program with following message:

5qld@w5qld-MacBookPro:~$ wsjtx
terminate called after throwing an instance of 'boost::wrapexcept<boost::log::v2_mt_posix::conversion_error>'
what(): Could not convert character encoding
Aborted (core dumped)

System is: Linux w5qld-MacBookPro 5.4.0-104-generic #118-Ubuntu SMP Wed Mar 2 19:02:41 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Running Ubuntu on old MacBook Pro.
Thanks


locked Re: lost my WSJTX logbook #logging

Eugene Morgan
 

I was able to rebuild my WSJT-X log by using my QRZ log book. I exported my log book and pull out all of my digital QSO's along with only the fields that WSJT-X uses. Of course I did this using some simple code that I wrote but I think it would also be possible using Excel.

I also don't see any reason you couldn't use and export from LOTW but I have to admit I've not do it using an LoTW ADI file.

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of w5pwh via groups.io
Sent: Friday, March 25, 2022 11:00 AM
To: main@WSJTX.groups.io
Subject: [WSJTX] lost my WSJTX logbook #logging

Good morning all!
I accidentally erased my logbook on WSJTX now when i am on ft8 it is look starting over Please tell me there is a way to get my past logbook back Dan W5PWH


locked Re: lost my WSJTX logbook #logging

Michael Black
 

Not much.  Parsing is pretty fast.

Mike W9MDB

On Friday, March 25, 2022, 03:24:45 PM CDT, Dennis Wage <dwage@...> wrote:





As a follow up to this question. How much faster would a large WSJT-X adi
file be if you removed all the unnecessary fields? Is it worth it to remove
all but the 3 or 4 needed?

The *WSJT-X* ADIF file records must contain the "CALL" field. The "BAND",
and "MODE", and "GRIDSQUARE" fields are optional depending on your DXing
objectives. DXCC entity, continent, CQ, and ITU Zone data for call prefixes
and certain well known overrides are derived from the cty.dat database
which is bundled with *WSJT-X* (See Logging
<https://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.4.0-rc4.html#LOGGING>
for
details).

On Fri, Mar 25, 2022 at 12:51 PM Michael Black via groups.io <mdblack98=
yahoo.com@groups.io> wrote:

If you don't have a backup (which you should try to do in the future)
looks like your QRZ logbook would get you close at least.

You've got 1934 QSOs on there.
Go to your logbook and click Settings -- you'll then see an ADIF
Import/Export section where you can export your logbook.

I think you may have to change the header though for WSJT-X.

Mike








On Friday, March 25, 2022, 12:20:31 PM CDT, w5pwh via groups.io <w5pwh=
yahoo.com@groups.io> wrote:





Good morning all!
I accidentally erased my logbook on WSJTX
now when i am on ft8 it is look starting over
Please tell me there is a way to get my past logbook back
Dan
W5PWH











locked Re: RPI Bullseye, Compile 2.5.4 ok, TX audio none. #AudioIssues #linux

Cliff <ae5zaham@...>
 

Here are some screenshots to show what I'm seeing on the 64bit PiOS Bullseye with Wsjtx 2.5.4 built from source.









Note: No Audio Codec output device shown in the Playback screen, but one is shown in the Recording screen. Why??????? How to fix?????

73,
Cliff, AE5ZA

On Mar 25, 2022, at 11:02, Cliff <ae5zaham@...> wrote:

He Carl,

Thanks for the suggestion, but it's already installed. For what it's worth I'm connecting to a 7300.

The issue is that the output audio device is not seen by Wsjtx on my 64bit Pi OS Bullseye. I don't know what the process is, but when the software opens it should recognize the audio in and out devices and when that happens they appear in pavucontrol. This is exactly what happens when running fldigi. Before starting any software Pavucontrol does now show either of the audio channels from the radio. As fldigi starts up both the input and output channels of the radio's audio appear in Pavucontrol and all is well. With Wsjtx 64 bit the input channel appears normally, but not the output channel.

64bit Wsjtx Audio config sees both the input and output channels, the output does not get connected on startup.

32bit Wsjtx config does not see any audio devices at all in the Audio setup for Wsjtx.

It's bizarre and I'm lost as what to try next.

73,
Cliff, AE5ZA

On Mar 25, 2022, at 10:18, Carl - WC4H via groups.io <wc4h.dx@...> wrote:

Hi Cliff.

Try installing (if not yet instaled) pavucontrol.
Then use it to check the volume of output devices. Make sure that the radio's output device is at 100. This has happened to me when I do a fresh install on the Raspberry Pi 4B. It does note seem to default to 100%.

73.
Carl - WC4H





locked Re: Odd Fake-it behaviour with FTDX10 #Cat_RigControl

Michael Black
 

Fake It or Rig Split has two purposes.

#1 Keeps your audio in the 1500-2000Hz range above the suppressed carrier which means any 3rd order or higher harmonics will be 4500Hz or higher outside your bandpass.
#2 Allows you to transmit at any offset -- even outside your transmit bandpass.

Mike W9MDB

On Friday, March 25, 2022, 05:22:05 PM CDT, bruiser419 via groups.io <bruiser419@...> wrote:





@Steve I guess I misunderstood. 

But not sure why you would use fake it at all then, you don't want the frequency to change to when you're transmitting.  But then again, maybe I'm missing something else.


locked Re: Odd Fake-it behaviour with FTDX10 #Cat_RigControl

Bruce G
 

@Steve I guess I misunderstood.

But not sure why you would use fake it at all then, you don't want the frequency to change to when you're transmitting. But then again, maybe I'm missing something else.


locked Re: Odd Fake-it behaviour with FTDX10 #Cat_RigControl

Steve Kavanagh
 

Mike

I am not sure if I understood your request exactly, but I did some tests regarding whether the FTDX10 can change frequency while transmitting under WSJT-X control.

(1) Turning the tuning knob on the FTDX10 while transmitting using WSJT-X in TUNE (on DATA-U mode and with Fake It on) does change the transmitted frequency (could hear it move on another receiver).
(2) Changing the TX offset frequency by using the up/down arrows does change the transmitted frequency (could hear it move on another receiver).
(3) Changing the TX offset frequency by editing in the frequency box does change the transmitted frequency (could hear it move on another receiver).
(4) Changing the TX offset frequency between Fake It segments using the up/down arrows (for example from 2505 Hz to 2495 Hz or vice versa) does not change the FTDX10 frequency readout.
(5) Changing the TX offset frequency between Fake It segments by editing the frequency box (for example from 2495 Hz to 249 Hz, by pressing backspace key once) moves the cursor in the Wide graph, changes the frequency as heard on another receiver, but does not change the FTDX10 frequency display.

All the above tests were using TUNE. Behaviour is somewhat different when changing things while calling CQ (TX6), as documented in points 7- 11 below. All these tests pertain to what happens within a single 15 second transmission.

(7) Turning the tuning knob on the FTDX10 while transmitting using WSJT-X to call CQ (on DATA-U mode with Fake It on) does change the transmitted frequency (could hear it move on another receiver).
(8) Changing the TX offset frequency by using the up/down arrows does NOT change the transmitted frequency (could not hear it move on another receiver).
(9) Changing the TX offset frequency by editing in the frequency box does NOT change the transmitted frequency (could not hear it move on another receiver, even though the Wide Graph cursor moved).
(10) Changing the TX offset frequency between Fake It segments using the up/down arrows (for example from 2505 Hz to 2495 Hz or vice versa) does not change the FTDX10 frequency readout.
(11) Changing the TX offset frequency between Fake It segments by editing the frequency box (for example from 2495 Hz to 249 Hz, by pressing backspace key once) moves the cursor in the Wide graph, does NOT change the frequency as heard on another receiver, and does NOT change the FTDX10 frequency display.

I hope that is clear and covers what you were wondering about.

73,
Steve VE3SMA


locked Re: lost my WSJTX logbook #logging

Dennis Wage <dwage@...>
 

As a follow up to this question. How much faster would a large WSJT-X adi
file be if you removed all the unnecessary fields? Is it worth it to remove
all but the 3 or 4 needed?

The *WSJT-X* ADIF file records must contain the "CALL" field. The "BAND",
and "MODE", and "GRIDSQUARE" fields are optional depending on your DXing
objectives. DXCC entity, continent, CQ, and ITU Zone data for call prefixes
and certain well known overrides are derived from the cty.dat database
which is bundled with *WSJT-X* (See Logging
<https://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.4.0-rc4.html#LOGGING>
for
details).

On Fri, Mar 25, 2022 at 12:51 PM Michael Black via groups.io <mdblack98=
yahoo.com@groups.io> wrote:

If you don't have a backup (which you should try to do in the future)
looks like your QRZ logbook would get you close at least.

You've got 1934 QSOs on there.
Go to your logbook and click Settings -- you'll then see an ADIF
Import/Export section where you can export your logbook.

I think you may have to change the header though for WSJT-X.

Mike








On Friday, March 25, 2022, 12:20:31 PM CDT, w5pwh via groups.io <w5pwh=
yahoo.com@groups.io> wrote:





Good morning all!
I accidentally erased my logbook on WSJTX
now when i am on ft8 it is look starting over
Please tell me there is a way to get my past logbook back
Dan
W5PWH











locked Re: lost my WSJTX logbook #logging

Michael Black
 

If you don't have a backup (which you should try to do in the future) looks like your QRZ logbook would get you close at least.

You've got 1934 QSOs on there.
Go to your logbook and click Settings -- you'll then see an ADIF Import/Export section where you can export your logbook.

I think you may have to change the header though for WSJT-X.

Mike

On Friday, March 25, 2022, 12:20:31 PM CDT, w5pwh via groups.io <w5pwh@...> wrote:





Good morning all!
I accidentally erased my logbook on WSJTX
now when i am on ft8 it is look starting over
Please tell me there is a way to get my past logbook back
Dan
W5PWH


locked Re: lost my WSJTX logbook #logging

neil_zampella <neilz@...>
 

If you have access to another log (local program like DXKeeper, ACLog,
etc), or you upload to QRZ or the like, you can export an ADIF file and
rename it to the wsjtx_log.adi filename.

However, did you check the 'trash can' in Windows.    If you used the
Windows file dialog to delete the file, it will probably still be in the
trash.

Neil, KN3ILZ

On 3/25/2022 11:59 AM, w5pwh via groups.io wrote:
Good morning all!
I accidentally erased my logbook on WSJTX
now when i am on ft8 it is look starting over
Please tell me there is a way to get my past logbook back
Dan
W5PWH




locked lost my WSJTX logbook #logging

w5pwh@...
 

Good morning all!
I accidentally erased my logbook on WSJTX
now when i am on ft8 it is look starting over
Please tell me there is a way to get my past logbook back
Dan
W5PWH


locked Re: RPI Bullseye, Compile 2.5.4 ok, TX audio none. #AudioIssues #linux

Cliff <ae5zaham@...>
 

He Carl,

Thanks for the suggestion, but it's already installed. For what it's worth I'm connecting to a 7300.

The issue is that the output audio device is not seen by Wsjtx on my 64bit Pi OS Bullseye. I don't know what the process is, but when the software opens it should recognize the audio in and out devices and when that happens they appear in pavucontrol. This is exactly what happens when running fldigi. Before starting any software Pavucontrol does now show either of the audio channels from the radio. As fldigi starts up both the input and output channels of the radio's audio appear in Pavucontrol and all is well. With Wsjtx 64 bit the input channel appears normally, but not the output channel.

64bit Wsjtx Audio config sees both the input and output channels, the output does not get connected on startup.

32bit Wsjtx config does not see any audio devices at all in the Audio setup for Wsjtx.

It's bizarre and I'm lost as what to try next.

73,
Cliff, AE5ZA

On Mar 25, 2022, at 10:18, Carl - WC4H via groups.io <wc4h.dx@...> wrote:

Hi Cliff.

Try installing (if not yet instaled) pavucontrol.
Then use it to check the volume of output devices. Make sure that the radio's output device is at 100. This has happened to me when I do a fresh install on the Raspberry Pi 4B. It does note seem to default to 100%.

73.
Carl - WC4H





locked Re: Odd Fake-it behaviour with FTDX10 #Cat_RigControl

Michael Black
 

One test you could that would help -- need to find out if the FTDX10 can change frequency while transmitting.

So if you change offset by more than 500Hz while transmitting does the rig change frequency in Fake It?

Mike W9MDB

On Friday, March 25, 2022, 10:31:37 AM CDT, Steve Kavanagh via groups.io <sjkavanagh1@...> wrote:





Thanks, Mike.  So far it has happened only once.  I think, in the interest of not breaking something by mistake, I'd better wait to see if it happens again, and if so then try the hamlib update. I've been using 2.5.4 for a while now and I have been quite active, so it still might have been a one-off thing due to RF or cosmic rays or whatever.

bruiser419@...  I am not sure if you understand that the dial reading on transmit is supposed to be different from receive when using Fake It, if your transmit audio frequency is outside the 1500-2000 Hz range.  My problem was that the rig got stuck on the transmit frequency.

73,
Steve VE3SMA


locked Re: Odd Fake-it behaviour with FTDX10 #Cat_RigControl

Steve Kavanagh
 

Thanks, Mike. So far it has happened only once. I think, in the interest of not breaking something by mistake, I'd better wait to see if it happens again, and if so then try the hamlib update. I've been using 2.5.4 for a while now and I have been quite active, so it still might have been a one-off thing due to RF or cosmic rays or whatever.

bruiser419@... I am not sure if you understand that the dial reading on transmit is supposed to be different from receive when using Fake It, if your transmit audio frequency is outside the 1500-2000 Hz range. My problem was that the rig got stuck on the transmit frequency.

73,
Steve VE3SMA


locked Re: RPI Bullseye, Compile 2.5.4 ok, TX audio none. #AudioIssues #linux

Carl - WC4H
 

Hi Cliff.

Try installing (if not yet instaled) pavucontrol.
Then use it to check the volume of output devices. Make sure that the radio's output device is at 100. This has happened to me when I do a fresh install on the Raspberry Pi 4B. It does note seem to default to 100%.

73.
Carl - WC4H


locked Re: Odd Fake-it behaviour with FTDX10 #Cat_RigControl

Michael Black
 

If you could install the latest hamlib as explained earlier in this thread and send me the debug file too it would be appreciated.

Mike W9MDB

On Friday, March 25, 2022, 10:04:04 AM CDT, bruiser419 via groups.io <bruiser419@...> wrote:





I saw this same issue with me.  I would receive on 7.074 but transmit at 7.0745. 

I simply changed the option from "Fake It" to "Off" and it fixed the problem.


locked Re: Odd Fake-it behaviour with FTDX10 #Cat_RigControl

Bruce G
 

I saw this same issue with me. I would receive on 7.074 but transmit at 7.0745.

I simply changed the option from "Fake It" to "Off" and it fixed the problem.

8661 - 8680 of 41499