Date   

locked Re: Menu items are repositioned in latest versions of JTA

WB5JJJ - George
 

Thanks Mike. 

I had seen all the comments about the menu being missing for some users, but nowhere did I see that in the ALT layout it was moved below the title bar, or I just missed comments with that context.  So I was a bit thrown off when it happened to me.  In my haste to update, I guess I just clicked on the wrong place and downloaded the ALT layout and went blindly forward.  Downloaded the proper one and now all is good again. 

As with all software I have, I try to keep the latest versions installed.  However, occasionally an update breaks something I depend on so I have to roll back until a re-fix is rolled out.  That's what I did with JTA.  Just didn't pay attention to the AL in that download.  Speed bumps along the way.  Realign the front end and roll on.  Life goes on. 

Thanks again. 

--
73's
George - WB5JJJ


locked Re: Time setting 1 hour off

 

 

It should read 15:53 as the time is 10:54 here.

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Michael Black via Groups.Io
Sent: Wednesday, April 3, 2019 8:30 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Time setting 1 hour off

 

This question is more appropriate for the WSJT-X list.

 

I take it you mean this time

Inline image

Is one hour behind the decode times?

Inline image

Can you provide a screenshot?

 

If you're on WIndows 10 right-click the date/time -- select Adjust date/time -- And ensure the "Adjust for daylight saving time..." is turned on.

 

de Mike W9MDB

 

 

 

 

 

On Wednesday, April 3, 2019, 6:26:43 AM CDT, Dave Alexander <dave.alexander1947@...> wrote:

 

 

I just noticed that the WSJT-X time at the bottom of the screen is one hour behind the actual time. I am in the south west corner of PA. It is now 12:24 utc and the time aon the screen says 11:24.


locked Re: Menu items are repositioned in latest versions of JTA

Michael Black
 

That's the alternate layout with the menu items moved below the title bar.

You want the other one.

de Mike W9MDB




On Wednesday, April 3, 2019, 9:06:46 AM CDT, WB5JJJ - George <wb5jjj@...> wrote:


HamApps_JTAlert_AL_2.13.2_Setup is what I used.

--
73's
George - WB5JJJ


locked Re: Menu items are repositioned in latest versions of JTA

WB5JJJ - George
 
Edited

HamApps_JTAlert_AL_2.13.2_Setup is what I used.
Must have got on the wrong line.  The normal has always worked for me. 
--
73's
George - WB5JJJ


locked Re: Menu items are repositioned in latest versions of JTA

Michael Black
 

You apparently downloaded the alternate version of JTAlert.

Try downloading the non-alternate version.  The menu items had to be re-positioned for some people who's menu item doesn't work on their video card.


de Mike W9MDB


On Wednesday, April 3, 2019, 8:30:55 AM CDT, WB5JJJ - George <wb5jjj@...> wrote:


I've not been on FT8 regularly for the past few weeks as I and operating more on SSB phone.  I updated to JTA v2.13.2 and noticed that the menu line items are now under the title instead of beside of it in the open space.  This is a small change, but it does increase the JTA real estate that was being used by WSJTx to display just one more line of Band Activity.  Plus, in the new location, they don't stand out as easily as before.  Any chance of putting them back on the top line?  If not, then bold them like in WSJTx so they stand out better for those with less than perfect vision.  
--
73's
George - WB5JJJ


locked Menu items are repositioned in latest versions of JTA

WB5JJJ - George
 
Edited

I've not been on FT8 regularly for the past few weeks as I am operating more on SSB phone.  I updated to JTA v2.13.2 and noticed that the menu line items are now under the title instead of beside of it in the open space.  This is a small change, but it does increase the JTA real estate that was being used by WSJTx to display just one more line of Band Activity.  Plus, in the new location, they don't stand out as easily as before.  Any chance of putting them back on the top line?  If not, then bold them like in WSJTx so they stand out better for those with less than perfect vision.  

Attached are before and current screen shots.
--
73's
George - WB5JJJ


locked Re: Time setting 1 hour off

Michael Black
 

This question is more appropriate for the WSJT-X list.

I take it you mean this time
Inline image

Is one hour behind the decode times?
Inline image

Can you provide a screenshot?

If you're on WIndows 10 right-click the date/time -- select Adjust date/time -- And ensure the "Adjust for daylight saving time..." is turned on.

de Mike W9MDB





On Wednesday, April 3, 2019, 6:26:43 AM CDT, Dave Alexander <dave.alexander1947@...> wrote:


I just noticed that the WSJT-X time at the bottom of the screen is one hour behind the actual time. I am in the south west corner of PA. It is now 12:24 utc and the time aon the screen says 11:24.


locked Time setting 1 hour off

 

I just noticed that the WSJT-X time at the bottom of the screen is one hour behind the actual time. I am in the south west corner of PA. It is now 12:24 utc and the time aon the screen says 11:24.


locked Re: JTA Throws Error on Restart after Crashing

Laurie, VK3AMA
 


On 1/04/2019 9:33 pm, Hasan Schiers N0AN wrote:
I only had worked selected in the settings of JTA...and the original WSJTX-adi log would not work, it would read in, but it produced nothing. So, something is not right with the format of the wsjtx adi file in terms of being read by JTA

73, N0AN
Hasan

Hasan,

I received your wsjt-x adi log file.

The clue to why the JTAlert Scan & Rebuild "produced nothing" was in your email stating "but did not produce any values for States Worked...etc". As I previously indicated, the wsjt-x adi log file is very limited in the adif fields it supports. At the time, I was referring to QSL confirmation fields as I was thinking that was your issue. In addition to no QSL confirmation fields (which is expected), it also doesn't contain any State or DXCC fields. Your Scan & Rebuild subsequently didn't find any worked States or Countries as that data is not available in the wsjt-x adi log.

JTAlert does not attempt to determine the State, dxcc, etc, when the data is missing as that would add significantly to the processing time overhead of the adif import. The expectation is that the user-provided adif file contains the required fields needed for the users alerting needs. In most cases the user-provided adif file does contain the data when the adif is an export from the users Logger. ADIF logging is a way of getting QSOs into Loggers not supported by JTAlert.

The wsjt-x adi log file is suitable for basic Band/Mode worked B4 determination only.

My recommendation on using the wsjt-x adi log was a last ditched effort to recover some of your lost log.

de Laurie VK3AMA


locked Re: 2.13.2 Lost Menu Settings

K2EK Bill
 

"protected folder" gave me all sorts of grief with Trusted QSL until I figured out
what was up and turned it off.


-----Original Message-----
From: Bob WB2NVR <wb2nvr@...>
To: Support <Support@HamApps.groups.io>
Sent: Tue, Apr 2, 2019 9:56 am
Subject: Re: [HamApps] 2.13.2 Lost Menu Settings

Hi Laurie -

TNX for the quick response. Turning off the Protected folders cleared
the issue.

I still don't have the menu items with the "standard" version, but the
alternate version works FB.

TNX again!

73,

Bob WB2NVR

--
Bob Schaps  WB2NVR

914-347-7331  Office
914-262-3535  Cell
914-472-0690  Home





locked Re: 2.13.2 Lost Menu Settings

Bob WB2NVR
 

Hi Laurie -

TNX for the quick response. Turning off the Protected folders cleared the issue.

I still don't have the menu items with the "standard" version, but the alternate version works FB.

TNX again!

73,

Bob WB2NVR

--
Bob Schaps WB2NVR

914-347-7331 Office
914-262-3535 Cell
914-472-0690 Home


locked Re: JTA Throws Error on Restart after Crashing

Hasan Schiers N0AN
 

Tnx Laurie, will do, soonest
73, N0AN
Hasan


On Mon, Apr 1, 2019 at 6:25 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 1/04/2019 9:33 pm, Hasan Schiers N0AN wrote:
BTW, I was not checking for any confirmed. I only had worked selected in the settings of JTA...and the original WSJTX-adi log would not work, it would read in, but it produced nothing. So, something is not right with the format of the wsjtx adi file in terms of being read by JTA

73, N0AN
Hasan
Hasan,

Good to hear your back working.

I'll investigate why the wsjt-x adi log did not work, it is standard adif so there should have been no problem. Please send me direct (not via this group) the wsjt-x adi log file you used.

de Laurie VK3AMA


locked Re: JTAlert Library

HamApps Support (VK3AMA)
 

On 31/03/2019 4:05 am, Randall Sanborn wrote:
Does anyone know what library is being used to interface to WSJT-X? I want to play around with some things like a dead man's switch that disables "Enable Tx" if I don't click a button saying I'm still there, etc.

Regards,

Randall
JTAlert doesn't use a library (dll) for working with wsjt-x. The code is all individual methods coded by myself and are not in a suitable form for public publication.

de Laurie VK3AMA


locked Re: JTA Throws Error on Restart after Crashing

HamApps Support (VK3AMA)
 

On 1/04/2019 9:33 pm, Hasan Schiers N0AN wrote:
BTW, I was not checking for any confirmed. I only had worked selected in the settings of JTA...and the original WSJTX-adi log would not work, it would read in, but it produced nothing. So, something is not right with the format of the wsjtx adi file in terms of being read by JTA

73, N0AN
Hasan
Hasan,

Good to hear your back working.

I'll investigate why the wsjt-x adi log did not work, it is standard adif so there should have been no problem. Please send me direct (not via this group) the wsjt-x adi log file you used.

de Laurie VK3AMA


locked Re: 2.13.2 Lost Menu Settings

HamApps Support (VK3AMA)
 

On 2/04/2019 12:38 am, Bob WB2NVR wrote:
TNX again for the great JT-Alert program. It really makes FT8 fun!

After the latest Windows 10 update, I noticed that i lost the menu items on JTAlert 2.13.2.  Prior to the update, I didn't have that problem.  I installed the AL version, and the menu items are back, and the program seems to be operating FB.

I did have two problems though.  During installation, I had a IPersistFile::Save failed error, and during a QSO, an Autolt Error.

The drive where JTAlert is installed is D, and there is 595 GB free;  C has 361 GB free.

I'll send my session files just in case you can find something interesting.

TNX ES 73,

Bob WB2NVR
Bob,

The error code reported by the setup is the code presented to it by the Operating System (Windows) when it prevented setup from creating the desktop shortcut. While the error code is normally used for disk space errors, the true error is that Windows actively prevented the creation of the shortcut, but setup doesn't know that and dutifully reports the error as given by Windows.

This is not a JTAlert specific issue. Googling indicates it occurs for many unrelated applications, the cause is the "Controlled Folder Access" setting within Windows Security (Defender). You should have see at the time a notice from Windows in the notification area.

Turning off that setting will allow the setup to work as normal. If your uncomfortable with temporarily turning off that setting, try rerunning the setup without selecting any desktop shortcuts to be created.

   

de Laurie VK3AMA


locked 2.13.2 Lost Menu Settings

Bob WB2NVR
 

Hi Laurie - 

TNX again for the great JT-Alert program. It really makes FT8 fun!

After the latest Windows 10 update, I noticed that i lost the menu items on JTAlert 2.13.2.  Prior to the update, I didn't have that problem.  I installed the AL version, and the menu items are back, and the program seems to be operating FB.

I did have two problems though.  During installation, I had a IPersistFile::Save failed error, and during a QSO, an Autolt Error.

The drive where JTAlert is installed is D, and there is 595 GB free;  C has 361 GB free.

I'll send my session files just in case you can find something interesting.

TNX ES 73,

Bob WB2NVR



locked Re: JTA Throws Error on Restart after Crashing

Hasan Schiers N0AN
 

Success! I used a search tool in Total Commander. It took  a long time but it found log.adi in the Recycle Bin. I copied it to the location I had specified in JTAlert and restarted the program, Everything came up fine.

I would have found it yesterday, but apparently I had not let the search of the Recycle Bin run long enough (its own search). When I went back to Total Commander this morning, it found log.adi in the Recycle Bin in less than 4 min. All I needed to do was click on it and copy it to the desired location.

You can be sure I will keep a backup of the log file from now on! (without using my full computer backup).

Thanks so much, Laurie. BTW, I was not checking for any confirmed. I only had worked selected in the settings of JTA...and the original WSJTX-adi log would not work, it would read in, but it produced nothing. So, something is not right with the format of the wsjtx adi file in terms of being read by JTA

73, N0AN
Hasan


On Sun, Mar 31, 2019 at 7:09 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 1/04/2019 8:08 am, Hasan Schiers N0AN wrote:

OK, I searched for log.adi...it is not on the drive. 
I shut down JTA
I copied the wsjtx *.adi log to the directory that Enable Logging was pointing to.
I rename the wsjtx.adi log to log.adi
I started X and it showed it was reading in 9500 some record (roughly)
I then went to Scan and Rebuild....told it do to all, (as I usually do)
It ran, but produced on worked stations. 

So, while it seems to read the wsjtx*.adi log renamed, for some reason the data 
while being read in, isn't being "used" by the program.

Any other ideas? I even tried Create new, chose wsjtx.adi, let it it overwrite it,
exited program. Deleted the newly created wsjtx.adi, recopied wsjtx.adi from 
wsjtx and then started JTA. It acted the same way, the 9500 some records appear
to read in, but when I do Scan and Rebuild, nothing shows up in either state or dx count.

Ideas? Again, thanks for your patience.
Hasan

Your original adif log file may not have been named log.adi, it could be anything, JTAlert doesn't care. log.adi is the default name JTAlert uses if you get JTAlert to create a new empty adif log file, which is what you have done.

Using a copy of the WSJT-X adi log file is acceptable within reason. It is a very limited file in terms of the adif fields it supports. Your Scan and Rebuild didn't find any Stations to take off your State and DXCC wanted lists because you very likely have QSL confirmation types set (eg Card or LoTW or eQSL) for the scans and the WSJT-X adi log file doesn't contain any of these QSL fields. In this situation, the WSJT-X adi log file is only useful for worked stations as there are no QSOs in the log marked as QSL confirmed. You will not be able to update the different wanted lists based on any QSL confirmation type, worked only.

You really need to find your old log file. JTAlert would not have deleted it. Don't you have backups? Have you checked your Recycle Bin? Unless you can recover your old log file or create a new one from either your logger export (if you use one) or from a LoTW or eQSL download your will have to live with using the WSJT-X data.

de Laurie VK3AMA


locked Re: JTA Throws Error on Restart after Crashing

HamApps Support (VK3AMA)
 

On 1/04/2019 8:08 am, Hasan Schiers N0AN wrote:

OK, I searched for log.adi...it is not on the drive. 
I shut down JTA
I copied the wsjtx *.adi log to the directory that Enable Logging was pointing to.
I rename the wsjtx.adi log to log.adi
I started X and it showed it was reading in 9500 some record (roughly)
I then went to Scan and Rebuild....told it do to all, (as I usually do)
It ran, but produced on worked stations. 

So, while it seems to read the wsjtx*.adi log renamed, for some reason the data 
while being read in, isn't being "used" by the program.

Any other ideas? I even tried Create new, chose wsjtx.adi, let it it overwrite it,
exited program. Deleted the newly created wsjtx.adi, recopied wsjtx.adi from 
wsjtx and then started JTA. It acted the same way, the 9500 some records appear
to read in, but when I do Scan and Rebuild, nothing shows up in either state or dx count.

Ideas? Again, thanks for your patience.
Hasan

Your original adif log file may not have been named log.adi, it could be anything, JTAlert doesn't care. log.adi is the default name JTAlert uses if you get JTAlert to create a new empty adif log file, which is what you have done.

Using a copy of the WSJT-X adi log file is acceptable within reason. It is a very limited file in terms of the adif fields it supports. Your Scan and Rebuild didn't find any Stations to take off your State and DXCC wanted lists because you very likely have QSL confirmation types set (eg Card or LoTW or eQSL) for the scans and the WSJT-X adi log file doesn't contain any of these QSL fields. In this situation, the WSJT-X adi log file is only useful for worked stations as there are no QSOs in the log marked as QSL confirmed. You will not be able to update the different wanted lists based on any QSL confirmation type, worked only.

You really need to find your old log file. JTAlert would not have deleted it. Don't you have backups? Have you checked your Recycle Bin? Unless you can recover your old log file or create a new one from either your logger export (if you use one) or from a LoTW or eQSL download your will have to live with using the WSJT-X data.

de Laurie VK3AMA


locked Re: JTA Throws Error on Restart after Crashing

Hasan Schiers N0AN
 

Laurie, sorry to put you through this...

OK, I searched for log.adi...it is not on the drive. 
I shut down JTA
I copied the wsjtx *.adi log to the directory that Enable Logging was pointing to.
I rename the wsjtx.adi log to log.adi
I started X and it showed it was reading in 9500 some record (roughly)
I then went to Scan and Rebuild....told it do to all, (as I usually do)
It ran, but produced on worked stations. 

So, while it seems to read the wsjtx*.adi log renamed, for some reason the data 
while being read in, isn't being "used" by the program.

Any other ideas? I even tried Create new, chose wsjtx.adi, let it it overwrite it,
exited program. Deleted the newly created wsjtx.adi, recopied wsjtx.adi from 
wsjtx and then started JTA. It acted the same way, the 9500 some records appear
to read in, but when I do Scan and Rebuild, nothing shows up in either state or dx count.

Ideas? Again, thanks for your patience.
Hasan


On Sun, Mar 31, 2019 at 3:33 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 1/04/2019 7:18 am, Hasan Schiers N0AN wrote:
Laurie,
When I look at alerts by band as far as what is wanted, it is all "wanted" I no longer see any states worked or dxcc worked...and I had many, so I assume I have to do something to get all the old data read into JTAlert?
TIA
Hasan
See my most recent message.

Your getting all calls alerted as needed because your now using an empty ADIF file. This is because you created a new file rather than selecting your existing ADIF file. Only you know where your original ADIF file is located, it is unlikely to be in the default location shown in my last posted image.

de Laurie VK3AMA


locked Re: Auto Log to HRD Logbook #HRD #TIP

Michael Black
 

You can have WSJT-X log directly to HRD

Explanation in this link:

And there's an add-on for DXKeeper to publish to QRZ and HRDLog.net -- doesn't appear in can upload to either by itself.

de Mike W9MDB

On Sunday, March 31, 2019, 1:58:48 PM CDT, John Scheuer <johnuscheuer@...> wrote:


I use JTAlert all the time with WSJTx and it auto logs to DXKeeper. I would also like to use HRD logbook. My question is can I also auto-log to HRD logbook and DXKeeper at the same time?  I have HRD logbook on my QRZ.com page and I would like it to automatically update at the end of a contact. The alternative is being able to put my DXKeeper log on my QRZ.com page, is that a possibility. If so, how?
John  NA6Y

13241 - 13260 of 36994