Willi,

I am unable to test Lo4OM v1, there is something wrong with my install. I did check Log4OM v2 and it correctly logged both the QSO_DATE and QSO_DATE_OFF.

What WSJT-X is logging.


What was logged by Log4OM v2.

Laurie,

here are screenshots of a log, from JTDX and Log4OM v1.41.0.0.
Note the missing check mark for QSO end date in Log4OM.

This is missing since an update some weeks ago, but I don't recall which one.

vy 73,
Willi, DJ6JZ

The Decodes window is present, but remains blank of data - it does not populate.  It did earlier today but not now. 

Icom 756 Pro2,  Windows 10,  8th Gen i7, HRD 6.7.0.357, WSJT-X v2.2.2

Looked at recent posts but could not find this problem.  Was at v 2.50.2 - upgraded to 2.50.4 today to see if that solved the problem.  No joy.
Have restarted program and restarted Windows, no joy.
I hope this is just an incorrect setting . . .

Thanks and 73  --  Don  K4GO

See this message https://hamapps.groups.io/g/Support/message/36296

de Laurie VK3AMA

Been using this wonderful program for quite a while now, and this is the first problem I've had to write about.  The Decodes window is present, but remains blank of data - it does not populate.  It did earlier today but not now. 

Icom 756 Pro2,  Windows 10,  8th Gen i7, HRD 6.7.0.357, WSJT-X v2.2.2

Looked at recent posts but could not find this problem.  Was at v 2.50.2 - upgraded to 2.50.4 today to see if that solved the problem.  No joy.
Have restarted program and restarted Windows, no joy.
I hope this is just an incorrect setting . . .

Thanks and 73  --  Don  K4GO

Laurie,

I am using Log4OM v1.41.0.0 and this version does not get QSO_DATE_OFF data.

I noticed that some weeks ago and since then I started to add this data manually.

vy 73,
Willi,DJ6JZ

Willi,

I am unable to test Lo4OM v1, there is something wrong with my install. I did check Log4OM v2 and it correctly logged both the QSO_DATE and QSO_DATE_OFF.

What WSJT-X is logging.


What was logged by Log4OM v2.


In JTAlert the logging code for Log4 v1 and v2 is identical (just a copy and paste), it is simply ADIF encoded text. JTAlert is sending both QSO_DATE fields for Log4 v1 and v2. It looks to me like the problem is with Log4 v1.

de Laurie VK3AMA

in previous versions, an audio alert was sounded to confirm a successful log entry to DX Keeper. With 2.50.4, this seems to have disappeared. The pop up boxes are as before and logging is correct but no alert audio is heard; other audio alerts are working as expected. I have looked multiple times at the various alert settings and also at the DXK Config setting and Help files but not seeing a way to enable/disable this alert. What am I missing?

Thanks,
Rick
K8EZB

Look under the "Alerts -> Miscellaneous Alerts -> Windows Notifications" section of the main JTAlert Settings window.

   

Make sure the "Enable" checkbox is ticked, top left corner of that Settings section.


de Laurie VK3AMA

Much was not working for me in 2.50.3, as many others have reported. Installing 2.50.4 corrected all issues I have tested so far except one: in previous versions, an audio alert was sounded to confirm a successful log entry to DX Keeper. With 2.50.4, this seems to have disappeared. The pop up boxes are as before and logging is correct but no alert audio is heard; other audio alerts are working as expected. I have looked multiple times at the various alert settings and also at the DXK Config setting and Help files but not seeing a way to enable/disable this alert. What am I missing?

Thanks,
Rick
K8EZB

On 7/16/2021 11:51 PM, Bob Frostholm wrote:

Hi Jim,

I upgraded WSJT-X and JTAlert  and all seems to work fine.

73

Bob

Ko6Lu

Bob,

Great! Glad it's working for you now.

73,

Jim N6VH

This is due to the logging code for the affected loggers being written back when WSJT-X did not record Date & Time off data. Log4OM was not affected as the JTAlert code for it was written when WSJT-X was  providing the Date & Time off data.

Laurie,

I am using Log4OM v1.41.0.0 and this version does not get QSO_DATE_OFF data.

I noticed that some weeks ago and since then I started to add this data manually.

vy 73,
Willi,DJ6JZ

Hi Jim,

I upgraded WSJT-X and JTAlert  and all seems to work fine.

73

Bob

Ko6Lu

--
Bob
KO6LU

On 17/07/2021 11:07 am, Patrick Hung wrote:

Where and how do I trigger that window? I can't find it.
--
73,

Patrick - W6AJR

Click the gear icon or press F2 when the window is active (has focus). This is not new, it has been that way since 2.50.0 for all the windows introduced with that version. Alternatively, activate the Callsigns window and press F1 then read the help file, "Standard Window Functionality" section.

de Laurie VK3AMA

Laurie Thank you for your quick response. Onaka JA4JOE

Where and how do I trigger that window? I can't find it.
--
73,

Patrick - W6AJR

On 17/07/2021 10:41 am, Bill Barber wrote:

He is trying to do the Settings to add his DXLabs logger and other configurations.  Any ideas why the Main window is blank? Other windows are normal,e.g. Callsigns and Decodes.

73,
Bill, NE1B

Bill,

Sorry, no idea. This is the first report I have seen of this type of behavior.

If your friend hasn't already done so, a Windows Restart wont hurt. I have lost count of the number of times that unexpected application behavior (not just JTAlert) was corrected by a simple Window Restart, especially with WIn10.

Without a physical menu to click, you could try using the F2 Hotkey after first making the window active. The F2 hotkey is  standard across all JTAlert windows for opening their associated Settings or Options.

de Laurie VK3AMA

I have been trying to find the settings to add logging.  On earlier versions, there was a Menu to select Settings>Manage Settings>Logging etc.

What am I missing?

73,

Bill, NE1B

Sounds like you trying to find the menu bar of the "Callsigns" window. There is none.
Look to the menu bar of the main JTAlert window. e.g.

   

de Laurie VK3AMA

This is a request for JTAlert's ADIF file.

JTAlert does not have <qso_date_off: 8> in the ADIF file.

WSJT-X and JTDX include <qso_date_off: 8>.

Log linkage software JT_Linker does not work well without <qso_date_off: 8>.

Could you please add <qso_date_off: 8> to ADIF file?

Sample data for JTAlrt and WSJT-X ADIF files.

[JTAlert]

<CALL: 6> UA0JBY <QSO_DATE: 8> 20210716 <TIME_ON: 6> 043200 <TIME_OFF: 6> 043300 <FREQ: 9> 21.076356 <FREQ_RX: 9> 21.076356 <BAND: 3> 15m <BAND_RX: 3> 15m <MODE : 3> FT8 <DXCC: 2> 15 <COUNTRY: 14> Asiatic Russia <CQZ: 2> 19 <ITUZ: 2> 33 <CONT: 2> AS <RST_SENT: 3> -10 <RST_RCVD: 3> -05 < LOTW_QSL_SENT: 1> R <LOTW_QSL_RCVD: 1> R <EQSL_QSL_SENT: 1> R <EQSL_QSL_RCVD: 1> R <QSLMSG: 11> TNX FB QSO! <K_INDEX: 1> 2 <SFI: 2> 74 <COMMENT: 25> FT8 Sent: -10 Rcvd: -05 <NAME: 12> herman Lebed <QTH: 14> Asiatic Russia <PFX: 3> UA0 <MY_GRID SQUARE: 8 > PM54SA82 <MY_CQ_ZONE: 1> 0 <MY_ITU_ZONE: 1> 0 <STATION_CALLSIGN: 6> JA4JOE <QSO_COMPLETE: 1> Y <EOR>

 

Hi OM,

I can confirm the missing QSO_DATE_OFF from the ADIF file (also DXKeeper, HRD5 and the lastqso.adi file).

This is due to the logging code for the affected loggers being written back when WSJT-X did not record Date & Time off data. Log4OM was not affected as the JTAlert code for it was written when WSJT-X was  providing the Date & Time off data. I neglected to update the DXKeeper, ADIF & HRD5 logging code when WSJT-X changed to include the extra information. Note there have been no changes to the ACLog code as it does not support the QSO_DATE_OFF data in its logging API.

Please check your email inbox, I have sent a new build of JTAlert for you to test.

de Laurie VK3AMA

On 7/15/2021 8:23 PM, Bob Frostholm wrote:

Based on what you said, I'm guessing that you have "Enable Standard ADIF File Logging" checked in JTAlert.

Yes

If so, that is the log that JTAlert will scan when you do a database rebuild. JTAlert doesn't scan the WSJT-X log when doing a rebuild. In that case, there won't be any QSL / LOTW confirmations listed in that file (or the WSJT-X file, for that matter). Since your database rebuild shows grid that aren't needed, I assume that you have "No QSL Confirmation (Any Worked Station)" checked in the Rebuild screen. Is that correct?

Yes

73

Bob

Ko6Lu

Bob,

Thanks for the info. Based on what you have said, the worked grids should show up immediately after doing a "Rebuild Alert Database" process. Since that isn't happening, something is wrong. Also, just closing and restarting JTAlert (and WSJT-X) shouldn't have any effect on the not-needed grids. That would only be done by the "Rebuild Alert Database" process.

Have you upgraded WSJT-X and JTAlert yet? If so, did that make a difference.

How long does the database rebuild process take? Since you have an SSD, it should be fairly quick. For example, I have over 60,00 QSO's in my Log4OM log, and it only takes a little over a minute to do the rebuild. I realize this is a very different database structure than the adif you use, but it should still be a fairly short amount of time.

Incidentally, if you don't care about whether or not the QSOs are confirmed, you can check the box in the Grid Alert screen that says "Auto clear triggered Alert entity after logging" (see attached picture). I use that for the Marathon alert, and it works fine. It would still be a good idea to get the rebuild process working, though, since you might decide later to have various confirmations (LOTW, etc) as criteria for scanning.

73,

Jim N6VH

That was exactly it Laurie.  Many thanks,

Trev EA5ISZ