Date   

locked How to merge Decode-History repeated CSV Exports?

KD7YZ Bob
 

I'm up to 59mb of decodes according to Decode-History.
I've started making an Open-Office xls type spreadsheet to put all these
sqlite's into one place.

From there I want to see some statistics.

When I look in the export folder I see numerous csv's .

How will I get the spreadsheet to gather all of them?

thanks


--
73,
Bob KD7YZ


locked Re: JTalert Not decodeing from WSJT-X

HamApps Support (VK3AMA)
 

On 11/12/2017 10:56 AM, ak9b@... wrote:
Unable to communicate wit WSJT-Xprocess
UDP Port : 2237
IP Address: 127.0.0.1
Values read from WSJT-X config File
C:\Users\Admin\AppData\Local\WSJT-X\WXJT-X.ini  I cant find the file so how do I fix it?

OM,

This message is shown if JTAlert doesn't receive a UDP packet from WSJT-X within the first minute after starting which indicates a communications failure.

The UDP Port and IP Address values read from your WSJT-X config as well as the config file location are shown for diagnostic purposes. Those values and file location look OK to me.

The problem is likely that the UDP comms is either being blocked (some overly aggressive Virus/Malware protection can cause this) or another program is running on your PC that has taken control of port 2237.

Have you made any recent changes to UDP settings in other programs (say a logger)? Some users see the word UDP and proceed to try and set all programs that utilise UDP to use the same port, which is wrong.

Have you ever had JTAlert working with WSJT-X?

What logger are you using with JTAlert?

de Laurie VK3AMA
   


locked Re: JTDX 18.1.0.31 and JTAlert 2.10.6 Double Click CQ Not Working - DEFECT in JTDX

HamApps Support (VK3AMA)
 

On 11/12/2017 3:58 AM, JohnB wrote:
JTDX v18.1.0.33 has solved this problem.  Tnx Laurie for tracking down the source of this bug.

Thanks John for letting us know.

My preference is not to debug the defects in other software, but the noise regarding this issue was overwhelming (the number of support requests was significant, exceeding the number of forum messages in the subject) that I had no choice but to track down the defect in JTDX as I was confident that JTAlert was not broken.

de Laurie VK3AMA
   


locked Re: JTAlertX 2.10.5 Not displaying all decoded calls

HamApps Support (VK3AMA)
 

On 11/12/2017 2:02 AM, n5js@... wrote:
Laurie, Thanks for your continued efforts developing and supporting a great app.  My understanding of the response to the original question in this thread is that the alert filters now apply to both audio alerts and the display of decoded callsigns where previously all decoded callsigns were displayed regardless of filter setting and the filters were only applied to the audio alerts.  I viewed this as a useful feature as it is nice to see if there is a desirable station to call that doesn't meet the filter criteria. Any chance "display all decodes - filter audio alerts only" could be added as an option?

Tnx & 73, Jim N5JS

Jim,

All Callsigns will be displayed regardless of the alerts activated by the Callsigns provided you don't have filters set to explicitly hide the Callsigns.

I typically run with many alert types disabled, with no alert filtering (except for ignored Callsigns) only having DXCC and my Own Call alerts enabled and the many other decoded Callsigns are displayed without any alert coloring (except if they generated a DXCC or Own Call alert).

Alert Filters have always hidden Callsigns if they didn't pass the filters. It is only recently that the Filters were extended to include the Ignore and B4 filtering that were previously set in different areas of JTAlert. There is the new "Show only Callsigns generating alerts" provided to help reduce the visual clutter on busy bands, but that filter is off by default. Fundamentally JTAlert is unchanged with what Callsigns are displayed except for this new filter.

What filters do you have set? What is not working as expected for you?

de Laurie VK3AMA
   


locked Re: Counties Not Logging

HamApps Support (VK3AMA)
 

On 11/12/2017 3:46 AM, W7JHR via Groups.Io wrote:

Just recently while using JTAlert, when I log my QSO’s to ACLogger, the counties aren’t showing up.  How might I fix this?

Thanks,

Jim W7JHR


Jim,

Counties are always logged to ACL if they are known. County data comes either from a previous ACL Log entry (if the County is set) or from an XML lookup. If Counties have stopped being logged the likely causeis that you have disabled XML lookups in JTAlert or your existing XML subscription has expired.

de Laurie VK3AMA
   


locked JTalert Not decodeing from WSJT-X

ak9b@...
 

Unable to communicate wit WSJT-Xprocess
UDP Port : 2237
IP Address: 127.0.0.1
Values read from WSJT-X config File
C:\Users\Admin\AppData\Local\WSJT-X\WXJT-X.ini  I cant find the file so how do I fix it?


locked New JTAlert 2.10.7 Available - HB9HQX 5.2 support, JTDX FT8 Patch. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

New JTAlert 2.10.7 is available for download.

IMPORTANT: JTDX FT8 users need to be using at least JTDX version 18.1.0.33

*** Please review the Release Notes ***

Visit HamApps.com for the download link and upgrade instructions.

Release Notes for 2.10.7
  New Features:
    - Works with new 5.2 version of JT65-HF HB9HQX Edition.
       (Important Note: Only JT65-Log, the default, is supported)
  Fixes:
    - More changes to correct bad mode alerting/spotting of FT8 with JTDX 18.1.0


de Laurie VK3AMA


locked Re: JTDX 18.1.0.31 and JTAlert 2.10.6 Double Click CQ Not Working - DEFECT in JTDX

igwt1939 <igwt1939@...>
 

 

Downloaded both the newest versions of JTDX and JTAlert.

After figuring out how to get them to work together I really enjoy

Using them.

Was really surprised this morning when I opened eQSL’s this morning to find so many.

Will be looking for updates now.

KO4PU


locked Counties Not Logging

W7JHR@...
 

Just recently while using JTAlert, when I log my QSO’s to ACLogger, the counties aren’t showing up.  How might I fix this?

Thanks,

Jim W7JHR

 

Sent from Mail for Windows 10

 


locked Re: JTAlertX 2.10.5 Not displaying all decoded calls

n5js@...
 

Laurie, Thanks for your continued efforts developing and supporting a great app.  My understanding of the response to the original question in this thread is that the alert filters now apply to both audio alerts and the display of decoded callsigns where previously all decoded callsigns were displayed regardless of filter setting and the filters were only applied to the audio alerts.  I viewed this as a useful feature as it is nice to see if there is a desirable station to call that doesn't meet the filter criteria. Any chance "display all decodes - filter audio alerts only" could be added as an option?

Tnx & 73, Jim N5JS


locked Re: JTDX 18.1.0.31 and JTAlert 2.10.6 Double Click CQ Not Working - DEFECT in JTDX

JohnB
 

JTDX v18.1.0.33 has solved this problem.  Tnx Laurie for tracking down the source of this bug.


locked Re: Moving/merging logs from one PC to another - How to?

Marion D. Kitchens
 

Roger that.  I understand.
 
On Sun, 10 Dec 2017 15:21:29 +1100 "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...> writes:

On 10/12/2017 9:16 AM, k4gok@... wrote:
I understand that means there is no way to merge the log files.
 
If your referring to the WSJT .adi log file, they can easily be merged using a text editor like notepad. They are plain text files, append the QSO records from one file to the end of the other file to create a combined adif file (don't copy the header record across). Simple, but will quickly become a chore if you try and keep the .adi files from two PCs in sync.

Just remember
JTAlert ignores this file.

de Laurie VK3AMA
   
 


locked Re: Opening/closing window wipes decodes

Michael Black
 

I tested this on Windows 10 and don't see this behavior at all.

Have you run a latency checker on your system?  Maybe poor latency could be involved?

You could send in a ?/Contact Support when this happens and include the time it occurs.  Laurie can probably tell you what happened.  And if you can grab the WSJT-X ALL.TXT section that didn't show up that would help even more.

de Mike W9MDB



On Friday, December 8, 2017, 11:05:39 AM CST, Tim Rife <lists_01@...> wrote:


Possibly off topic as I think this is a Windows thing.  But, I notice when I am listening to FT8 decodes that when I either minimize or maximize another window during the 15 second RX period, JTAlert will not display any call signs during that period.  For example, if I am looking at QRZ on my browser and minimize that window during the 15 second cycle, there will be no decodes show up in JTAlert.  Same thing if I maximize the browser window during that time period.  Anyone know why that happens?  Is there a windows setting I need to set differently?  Windows 7 64bit professional here using WSJT-X 1.8.

Thanks,

Tim
KK9T


locked Re: Problem starting JTalert

Michael Black
 

What exactly do you mean "cannot download" ??  Do you mean "cannot install"?


What error message are you seeing?

Windows 10 will warn you that it doesn't recognize the program and you have to click the "More Info" on that screen to install it anyways.
Is this what you're seeing?
Inline image


de Mike W9MDB

On Sunday, December 10, 2017, 6:02:44 AM CST, Masana Seki <seki@...> wrote:


Hi

While I was downloading JTAlert, my Windows Defender detect virus and
I cannot download.
I was trying to several times but I could not resolve this issue.
Please give me your advice.

Regards,
Masana/JA1LDG
---------------------------
Masana Seki <seki@...>
+81 90 3205 2434





locked Re: Problem starting JTalert

Masana Seki <seki@...>
 

Hi

While I was downloading JTAlert, my Windows Defender detect virus and
I cannot download.
I was trying to several times but I could not resolve this issue.
Please give me your advice.

Regards,
Masana/JA1LDG
---------------------------
Masana Seki <seki@masana.net>
+81 90 3205 2434


locked Re: Decoded callsigns missing with JTDX

Garry Herden
 

Hi Laurie,

Thanks for the prompt reply. I did have the latest JTalert but not the .32 release of JTDX.

I eventually found it and after install all is well and callsign boxes are being filled.

Thanks for the quick fix.

Cheers,

de Garry VK5ZK.

On 10/12/2017 08:24, HamApps Support (VK3AMA) wrote:
On 10/12/2017 6:38 PM, Garry Herden wrote:
I have just installed JTDX v18.1.0.30 which supports FT8 and have the JTDX shortcut for JTalert 2.10.6.

All is working except that no decoded callsigns appear in the JTalert boxes.  I have 4X9 matrix set in JTalert.
Band activity works and If I contact a station the details appear in the area directly below the callsign boxes
I also have WSJT-x 1.8.0 and JTalert and they work as expected  Decoded callsigns appear in the boxes.

I have compared the settings in WSJT-X and JTDX as best I can and nothing different stands out.

Any suggestions please.

Garry VK5ZK
Garry,

You need the latest JTDX which is 18.1.0.32 and the latest JTAlert 2.10.6 build 0001

Check the JTAlert build number via the ? -> About menu. If it is not build 0001, download 2.6.0 from HamApps.com again and rerun the setup.

de Laurie VK3AMA
   


locked Re: Decoded callsigns missing with JTDX

HamApps Support (VK3AMA)
 

On 10/12/2017 6:38 PM, Garry Herden wrote:
I have just installed JTDX v18.1.0.30 which supports FT8 and have the JTDX shortcut for JTalert 2.10.6.

All is working except that no decoded callsigns appear in the JTalert boxes.  I have 4X9 matrix set in JTalert.
Band activity works and If I contact a station the details appear in the area directly below the callsign boxes
I also have WSJT-x 1.8.0 and JTalert and they work as expected  Decoded callsigns appear in the boxes.

I have compared the settings in WSJT-X and JTDX as best I can and nothing different stands out.

Any suggestions please.

Garry VK5ZK
Garry,

You need the latest JTDX which is 18.1.0.32 and the latest JTAlert 2.10.6 build 0001

Check the JTAlert build number via the ? -> About menu. If it is not build 0001, download 2.6.0 from HamApps.com again and rerun the setup.

de Laurie VK3AMA
   


locked Decoded callsigns missing with JTDX

Garry Herden
 

I have just installed JTDX v18.1.0.30 which supports FT8 and have the JTDX shortcut for JTalert 2.10.6.

All is working except that no decoded callsigns appear in the JTalert boxes.  I have 4X9 matrix set in JTalert.
Band activity works and If I contact a station the details appear in the area directly below the callsign boxes
I also have WSJT-x 1.8.0 and JTalert and they work as expected  Decoded callsigns appear in the boxes.

I have compared the settings in WSJT-X and JTDX as best I can and nothing different stands out.

Any suggestions please.

Garry VK5ZK


locked Re: JTAlertX 2.10.5 Not displaying all decoded calls

HamApps Support (VK3AMA)
 

On 10/12/2017 3:51 PM, Michael Black via Groups.Io wrote:
Sometimes you can -- but you need to install the sqlite3 command line utility.



de Mike W9MDB
Mike,

I have been down that path without success. I have stopped trying to repair broken config.sqlite files for users and now just provide instructions on restoring a backup.

de Laurie VK3AMA
   


locked Re: JTAlertX 2.10.5 Not displaying all decoded calls

HamApps Support (VK3AMA)
 

On 8/12/2017 12:02 AM, KD7YZ Bob wrote:
so that brings up the question .. how to tell what the date of capture
was?? Only column is TIME
The Decodes History display was not designed for historical analysis of decodes, its primary function is to display the decodes for the current operating session, thus only the "TIME" display and to provide an equivalent to the decodes history csv file of JT65-HF (I don't recall what the file was called exactly)

If your viewing the decodes.sqlite file directly, you will observe both Date and Time data is recorded.

The exported daily csv files contain the Date and Time of each decode.

Note: All Date and Time data are in UTC.

de Laurie VK3AMA
   

19501 - 19520 of 37225