Date   

locked Re: WSJT-X log Start & Stop times truncated to minute

Michael Black
 

If you want seconds you have to check it.

de Mike W9MDB




On Wednesday, April 29, 2020, 03:45:56 PM CDT, Richard McDonald via groups.io <ranchoham@...> wrote:


Hi Herb,

 

That option is not checked.

 

 

73,

Rich

WB0NRE

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of WB8ASI Herb
Sent: Wednesday, April 29, 2020 11:49 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] WSJT-X log Start & Stop times truncated to minute

 

On April 29, 2020 at 1:15 PM "Richard McDonald via groups.io" <ranchoham@...> wrote:

Software versions:
WSJT-X   v2.1.2
JTAlert for WSJT-X    2.16.4
HRD LOG    6.7.0.275

Since loading JTAlert, my logbook entries from WSJT-X have their start and stop time seconds entry truncated to zero.

Is JTAlert doing this?  Is there a way to stop it?

Rich
WB0NRE


 


locked Re: WSJT-X log Start & Stop times truncated to minute

g4wjs
 

On 29/04/2020 21:45, Richard McDonald via groups.io wrote:

Hi Herb,

 

That option is not checked.

Richard,

that is exactly why your QSO start and end times are being adjusted to whole minutes.


--
73
Bill
G4WJS.


locked Re: WSJT-X log Start & Stop times truncated to minute

Richard McDonald
 

Oops, ignore my last message; I read the option wrong.  I’ll set it and try again.

 

73,

Rich

WB0NRE

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of WB8ASI Herb
Sent: Wednesday, April 29, 2020 11:49 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] WSJT-X log Start & Stop times truncated to minute

 

On April 29, 2020 at 1:15 PM "Richard McDonald via groups.io" <ranchoham@...> wrote:

Software versions:
WSJT-X   v2.1.2
JTAlert for WSJT-X    2.16.4
HRD LOG    6.7.0.275

Since loading JTAlert, my logbook entries from WSJT-X have their start and stop time seconds entry truncated to zero.

Is JTAlert doing this?  Is there a way to stop it?

Rich
WB0NRE


 


locked Re: WSJT-X log Start & Stop times truncated to minute

Richard McDonald
 

Hi Herb,

 

That option is not checked.

 

 

73,

Rich

WB0NRE

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of WB8ASI Herb
Sent: Wednesday, April 29, 2020 11:49 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] WSJT-X log Start & Stop times truncated to minute

 

On April 29, 2020 at 1:15 PM "Richard McDonald via groups.io" <ranchoham@...> wrote:

Software versions:
WSJT-X   v2.1.2
JTAlert for WSJT-X    2.16.4
HRD LOG    6.7.0.275

Since loading JTAlert, my logbook entries from WSJT-X have their start and stop time seconds entry truncated to zero.

Is JTAlert doing this?  Is there a way to stop it?

Rich
WB0NRE


 


locked HamApps Callsign Database v2020.04.29

Jim AF5FH
 

I see that there is a new Callsign database update on HamApps.com today (4/29/2020). 

Just curious, since Laurie posted on 4/24/2020 that VK3AMA will be offline for 2 to 3 weeks, and during this time JTAlert and Callsign database updates will be suspended.

73,
Jim AF5FH


locked Re: WSJT-X log Start & Stop times truncated to minute

WB8ASI Herb
 


On April 29, 2020 at 1:15 PM "Richard McDonald via groups.io" <ranchoham@...> wrote:

Software versions:
WSJT-X   v2.1.2
JTAlert for WSJT-X    2.16.4
HRD LOG    6.7.0.275

Since loading JTAlert, my logbook entries from WSJT-X have their start and stop time seconds entry truncated to zero.

Is JTAlert doing this?  Is there a way to stop it?

Rich
WB0NRE

 


locked Re: V 2.16.4 not filling in NAME,QTH, or GRID info.

WB8ASI Herb
 

It's in you wifi connection properties.  Just found that mine has switched to Public also, but not having problems.  Put it back to Private anyways.  73 Herb WB8ASI

On April 29, 2020 at 2:30 PM "k6vib@q.com" <k6vib@q.com> wrote:

TNX John. Now where is that pub/priv found? I have seen it but not sure where. Bob K6viB

 


locked WSJT-X log Start & Stop times truncated to minute

Richard McDonald
 

Software versions:
WSJT-X   v2.1.2
JTAlert for WSJT-X    2.16.4
HRD LOG    6.7.0.275

Since loading JTAlert, my logbook entries from WSJT-X have their start and stop time seconds entry truncated to zero.

Is JTAlert doing this?  Is there a way to stop it?

Rich
WB0NRE


locked Re: V 2.16.4 not filling in NAME,QTH, or GRID info.

k6vib@q.com
 

TNX John. Now where is that pub/priv found? I have seen it but not sure where. Bob K6viB


locked Re: V 2.16.4 not filling in NAME,QTH, or GRID info.

John Kludt K7SYS
 

K6VIB,

I don't know how this works but I started having problems with number of apps after the last Win10 update.  It turned out that I am not sure how but the network had been flipped to "Public" from "Private."  When Is set things back to "Private" things started working again.

John

On Wed, Apr 29, 2020 at 2:07 PM k6vib@q.com <k6vib@q.com> wrote:
Using WSJT-X newest version. my JTAlert 2.16.4 is missing info even after uninstall/reinstall. See Subject line. Tried the ALT program and got the same thing. Any help? SENT 4-29-2020


locked Re: Decodes Window Will Not Open (Windows 10)

Marlo Montanaro - KA2IRQ
 

In both cases, I have found if the Decodes window is blank, opening the Statistics window (from the Decodes menu) will populate everything within a few seconds and processing will continue from that point.  You can then close the Statistics window.

Not sure why that is or if it is specific to my configuration, so, your mileage may vary.

 

73,

Marlo- KA2IRQ


locked Re: Decodes Window Will Not Open (Windows 10)

TomK
 
Edited

Thanks for update Tom.  I hope it's a good time off for him.
No rush for me. I'm all set for the moment.
TomK 73


locked Re: Decodes Window Will Not Open (Windows 10)

Tom Melvin
 

Laurie is ‘off the grid’ for a few weeks with no internet access.

I don’t believe there is anyone on this list that can answer those queries.

I’m sure he will reply when back so don’t be concerned with no response.

Tom

--
73’s

Tom
GM8MJV (IO85)

On 28 Apr 2020, at 23:01, TomK <QSO@KT1TK.com> wrote:

[Edited Message Follows]

I could have added a preamble that explained there were 2 Decodes display issues in this thread.
1. Decodes window initially opens w/o message traffic but starts after Decode window is close/reopened.
2. Decodes window opens but never displays traffic no matter how many Decode window or JT Alert restarts.

If yours is Case #1 then, I agree, it is a minor annoyance that may not be worth deleting/rebuilding your config.
My message was already as tedious as I was tired so I neglected to apply my usual 7th reread/edit :-)

I was commenting on Case #2 wherein the Decodes window never displays traffic regardless of actions.
As I hopefully explained, it seems related to the JT Alert & Decodes processes losing communication.
I surmised that deleting the config data might allow a re-install to re-sync JT main & decodes processes.
My pondering thus focused on how to completely uninstall JT Alert and all of its its configuration data.
Alas, that method also entails the loss of all previously customized user settings
There should be easier ways but I have not found/read the details of the lower level architecture.
I'll research that further - It's probably a simple thing that I have not yet come upon.

[Update]
I've since found a trick method to retain most (not all) user config data. What I did was to
copy back the SQLIte config DB file from a previous install to the current install's folder.
That resurrected most (not all) config settings while not undoing the re-synced communication.
Unfortunately, it did not resurrect my elaborate list of macros. They may be in another file.
Also think UDP port is in another file so it was not messed up by my SQLite DB restoration.

Laurie and Assoc:
Are there any accessible data on JT-Alert's disk and I/O architecture?
E.g., Outward I/O port operations + internal comms w/Decodes module.
Also descriptions of the purpose, format and location of all config data files.
It would greatly assist in debugging and fixing issues w//o taxing your time.
The initial goals being to figure out how to reset JT-Alert & JT-Decode comms
and to better archive and restore ancillary data like settings, Macros, etc.
There's just too much stuff in Local data folder to properly reverse engineer.
I could start a system utilities package listing basic lower level operations.

TomK 73


locked Re: Decodes Window Will Not Open (Windows 10)

TomK
 
Edited

I could have added a preamble that explained there were 2 Decodes display issues in this thread.
1. Decodes window initially opens w/o message traffic but starts after Decode window is close/reopened.
2. Decodes window opens but never displays traffic no matter how many Decode window or JT Alert restarts.

If yours is Case #1 then, I agree, it is a minor annoyance that may not be worth deleting/rebuilding your config.
My message was already as tedious as I was tired so I neglected to apply my usual 7th reread/edit :-)

I was commenting on Case #2 wherein the Decodes window never displays traffic regardless of actions.
As I hopefully explained, it seems related to the JT Alert & Decodes processes losing communication.
I surmised that deleting the config data might allow a re-install to re-sync JT main & decodes processes.
My pondering thus focused on how to completely uninstall JT Alert and all of its its configuration data.
Alas, that method also entails the loss of all previously customized user settings
There should be easier ways but I have not found/read the details of the lower level architecture.
I'll research that further - It's probably a simple thing that I have not yet come upon.

[Update]
I've since found a trick method to retain most (not all) user config data. What I did was to
copy back the SQLIte config DB file from a previous install to the current install's folder.
That resurrected most (not all) config settings while not undoing the re-synced communication.
Unfortunately, it did not resurrect my elaborate list of macros. They may be in another file.
Also think UDP port is in another file so it was not messed up by my SQLite DB restoration.

Laurie and Assoc:
Are there any accessible data on JT-Alert's disk and I/O architecture?
E.g., Outward I/O port operations + internal comms w/Decodes module.
Also descriptions of the purpose, format and location of all config data files.
It would greatly assist in debugging and fixing issues w//o taxing your time.
The initial goals being to figure out how to reset JT-Alert & JT-Decode comms
and to better archive and restore ancillary data like settings, Macros, etc.
There's just too much stuff in Local data folder to properly reverse engineer.
I could start a system utilities package listing basic lower level operations.

TomK 73


locked Re: call change

Michael Black
 

If you're on Windows 10 go to your search bar and type "Change station".

JTAlert must not be running when you do it.

Otherwise it's in the HamApps program menu.

de Mike W9MDB




On Tuesday, April 28, 2020, 05:50:57 AM CDT, robert spit <pd0pvl@...> wrote:


hi,

 

I changes my call today from pd0pvl to PD2V.

 

Can you support this change?

 

Thanks

 

Robert

 

PD2V

 

 

Verzonden vanuit Mail voor Windows 10

 


Virusvrij. www.avg.com


locked Re: Decodes Window Will Not Open (Windows 10)

Dev Null
 

Why would I want to spend hours doing an uninstall/reinstall/reconfigure, when all I need to do (for now) is hit "x" to close the decode window, hit "view" on the main window, and select "decodes window" again? That is what I have been doing for weeks, and I can live with that until the next release.


locked call change

robert spit <pd0pvl@...>
 

hi,

 

I changes my call today from pd0pvl to PD2V.

 

Can you support this change?

 

Thanks

 

Robert

 

PD2V

 

 

Verzonden vanuit Mail voor Windows 10

 


Virusvrij. www.avg.com


locked Re: Decodes Window Will Not Open (Windows 10)

TomK
 

Hi All. I'm back!
This is a reply to everyone on this topic.
Found and Fixed the Problem

After 72 hours of little sleep, shooting repeatedly in the dark, methodically trying all permutations of my aforementioned actions, utilizing numerous old-hacker tricks, tracing UDP traffic with WireShark, and adding additional steps of uninstalling all apps used in my article "Digital Zen" (WSJT, JTAlert, ACLog, GridTracker), I've eventually arrived at my Eureka moment.

Final Journey:
After repeated failures of all combinations and sequencing of the above machinations, I followed a path subtly suggested by Laurie's query to another's report, "What UDP port does the help show".  I decoded that to mean JT Alert and JT Decodes might cavort via UDP.  I don't know for sure but found evidence of a changed port in my last bad session vs archived notes of an earlier successful config. However, having burnt through 3 days of reconnoitering I reached the point of no return. Losing the config to gain the DECODES was better than having no DECODES.

So, that brought me back, full circle, to my 1st idea of a deep uninstall of JT with deep erasure of its app data areas
 
- as Michael Black also made note of here. 

Analysis and Steps Taken (with some translation for those smart enough to avoid deep tech)

1. Scenario: Heavily loaded workstation quickly reveals slightest app issues
  • I run a typical mid-level but highly loaded workstation with following specs:
  • Intel Core i7 930 @ 3GHz (4 Cores, 8 threads, running at 3GHz);
  • 32GB of RAM; 12 TB DASD (internal and external SATA, USB2, USB3 drives)
  • mid-level NVIDIA GeForce GTX1050Ti graphics card pushing 2 mid-quality 24" monitors;
  • Running JT (16-24)/7/365 with 10-20 other foreground tasks and 50-100 background processes
2. CPU heavily taxed by digital workflow - maxing out with any media apps running
As such, Windows CPU threads and committed memory rapidly max out .
The slightest memory leaks or reduced garbage cleaning by apps can crash/freeze them out.
This happens routinely with WSJT+JTAlert running/decoding (16-24)/7/365.
Typically about 1/ week of continuous running JT crashed/freezes, requiring a hard process kill.

3. Item #2 above was scenario in place the day I lost DECODES 

JT crashed and I had to hard kill it. More specifically, JT Decodes process froze and would not exit.
Another symptom was (for several previous days) Window frame "X" command didn't exit JT.
Only Close Window command on JT's taskbar entry would close all JT Windows (most of the time).
On the day of the DECODES window loss, all the above occurred and ....
the DECODES sub-process kept running requiring a hard kill using the techie util ProcessExplorer.

4. Then my deepest hair pulling and visits here
Most important light bulb was that the config got corrupted, such as a UDP port change?
That may have occurred when orphaned DECODES sub-process hung around and dupe 2nd one started.
So on next run, a new UDP port may have been assigned - breaking the DECODE linkage.
Totally guessing here based only on techie gut and monitoring of the processes.
That "may" have broken JT communication with DECODES and the rest is history.
Whether or not there actually was a UDP port problem, the steps here did fix it.

5. Deep Cleaning
The goal here was to uninstall BOTH the JT Alert app as well as its system data folder.
WARNING: This loses ALL your JT your configuration settings - allowing for a virgin install.
This includes things like JT Macros, Call settings, etc --- everything!
A. Uninstall JT Alert program
  • Run Windows Programs & Features applet (via Windows > Settings Menu > Programs & Features)
  • Then locate JT Alert, double-click, then OK to Uninstall.
B. Renamed "HamApps" local program data folder (deletes w/o data loss by changing it to another name)
Your Windows account needs to be Administrator to access and rename this folder. (Usual case but not always).
  • Locate HamApps's AppData folder in File Explorer by entering path as "%LocalAppData%" (without quotes)
    That's a macro that expands to the path of your AppData\Local folder containing HamApps program data.
  • Locate HamApps folder and rename it to something else like HamApps [old]  (says yes if asked for permission)
At this point, you have removed the JT app as well as all of its configuration data.

C. For Good Measure .. I then ...
Closed all apps, backup programs, and anything else running!
Did a complete POWER DOWN to clear BIOS, USB pilot light, and all disk caches.
Waited a few minutes till all PC lights and fans were dead.

D.  Reboot, Install, Pray
I then reboot, hoping disk woke up again (never count on it, ha)
Reinstalled JT Alert
Ran wSJT & JT
Voila - It worked. Decodes windows back to normal.
The BAD. All custom setting gone. Took an hour to review and reset the all.
Advice: Perform a lot of screen captures of the JT setting screens for easy reference.

Nb. Trick that worked for me:  Don't advise it for non-techies.
I found the SQLite settings database in the old HamApps [old] JT-AlertX app data folder.
I copied it to the same place in the new HamApps folder.
That seemed to have restore all my settings EXCEPT Macros and the bad port assignment.
The former was bad but the latter good!

Laurie, if by chance, my thought on UDP port un-syncing makes any sense, is there a way to reset it?
Like telling us the location and allowing it to be cleared, force a search/reset on next run?
Just some random thoughts.
TomK 73


locked Re: Modes

Michael Black
 

Well you're on the wrong list for WSJT-X problems.

You will have to describe the problem a lot better than "can't change".

What are you expecting to see and what are you actually seeing that makes you think it's not changing anything?

de Mike W9MDB




On Monday, April 27, 2020, 01:14:30 PM CDT, Greg Yates via groups.io <gyates@...> wrote:


I am running WSJTX latest version and it seems to work fine in FT8 but I can’t change to any other mode.  Has anyone else experienced this problems.  WSJTX is working with an IC7610.  I have the software installed on a laptop and it works but on this desktop I can not get it to change modes.

 

Thanks,

 

Greg

WB2BIN


locked Modes

Greg Yates <gyates@...>
 

I am running WSJTX latest version and it seems to work fine in FT8 but I can’t change to any other mode.  Has anyone else experienced this problems.  WSJTX is working with an IC7610.  I have the software installed on a laptop and it works but on this desktop I can not get it to change modes.

 

Thanks,

 

Greg

WB2BIN

8041 - 8060 of 37288