Date   

locked Re: FAILURE : QSO Not logged ...

GARY JOHNSON
 

I have had this issue for several months.   I has been ongoing before and after upgrading both WSJT-X  and JTALERT.  The failure to Log errors seem to happen after the programs are left running, but not in use, for a period of time.  JTALERT is logging to AC Log.  When i click Log QSO after restarting both programs,  I get another message that the QSO being logged does not match the current QSO Partner.  

Another problem that might be related is a delay of several seconds after  TX cycle starts before the rig, Yaesu FTdx-3000 is keyed.    

Kind of annoying,  but I have dealt with these issues for several months.  Any suggestions will be appreciated.   

Gary, wy0v




Sent from my Samsung Galaxy Tab®4


-------- Original message --------
From: Uwe <DG2YCB@...>
Date: 04/01/2020 6:33 AM (GMT-06:00)
To: Support@HamApps.groups.io
Subject: [HamApps] FAILURE : QSO Not logged ...

Hi Laurie,
From time to time (mostly after JTAlert has been updated) I am getting an error message "FAILURE : QSO Not logged ..." (see screenshot 1). Usually it is enough to re-start JTAlert and next time it works. However, I like to identify the reason for this unwanted behaviour.
Under "Logging" "Standard ADIF File" is selected, and the file exists and is a valid file (see screenshot 2). Note: Although my ADIF file has the same name as the one from wsjt-x it is another file. I've already tried another file name, but it has no effect on the mentioned error.
After JTAlert comes with such an error message, each time JTAlert's file B4logv2.mdb has an entry showing the correct band, but without a callsign, see the example as screenshot 3). When I manually add the missing data and save the B4logv2.mdb file station is correctly identified as worked B4.
What may cause this unwanted behaviour? Is there anything I can do to prevent this error?
73 de Uwe DG2YCB





locked FAILURE : QSO Not logged ...

Uwe, DG2YCB
 

Hi Laurie,
From time to time (mostly after JTAlert has been updated) I am getting an error message "FAILURE : QSO Not logged ..." (see screenshot 1). Usually it is enough to re-start JTAlert and next time it works. However, I like to identify the reason for this unwanted behaviour.
Under "Logging" "Standard ADIF File" is selected, and the file exists and is a valid file (see screenshot 2). Note: Although my ADIF file has the same name as the one from wsjt-x it is another file. I've already tried another file name, but it has no effect on the mentioned error.
After JTAlert comes with such an error message, each time JTAlert's file B4logv2.mdb has an entry showing the correct band, but without a callsign, see the example as screenshot 3). When I manually add the missing data and save the B4logv2.mdb file station is correctly identified as worked B4.
What may cause this unwanted behaviour? Is there anything I can do to prevent this error?
73 de Uwe DG2YCB





locked JTAlert 2.16.3 is available. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The latest JTAlert version 2.16.3 is now available @ https://hamapps.com/JTAlert/

Please review the Release notes at the end of this message.

de Laurie VK3AMA

Release Notes.

2.16.3 (30-MAR-2020)

  *** Includes Callsign database file version 2020-03-30 (2020-March-30)

  Changes:

    - US State Scan: A popup warning that a new scan is needed will be shown
       whenever the "Consider DC as MD" checkbox is changed. The new scan is
       needed to correctly update the wanted lists counts to reflect whether
       "DC" is considered a separate alert-able entity.

    - Non US Callsigns that are listed in the FCC database with a US based
       State will be alerted as the United States and not the Country normally
       identified by their Callsign prefix. (eg NH2 Guam, AH0 Mariana Is, etc)

  Fixes:

    - Logging: Some users experiencing non-logging of US State code.

    - Decodes Window: Show only Alerts filter incorrectly hiding callsigns that
       generated a VE Province Alert.

    - Decodes Window: Delays in decode population where the display would
       appear to pause with the display updates being one or more periods late.

    - Decodes Window: Rare "Threading" errors being thrown.

    - Decodes Window: US Callsigns loosing their State code after logging.

    - B4 Indicator: All decodes showing as B4 after several decode periods.
       This affected Log4OM MySQL log users. (2.16.0 defect)

    - DXCC Alert: "TNX73" alerting as "Republic of the Congo".

    - State Alert: Showing a total of "51 States" rather than "50 States"
       when the "Consider DC as MD" setting is enabled.

    - B4 Date: "NO Log" users getting "Unknown Date" in the Callsign tooltip
       for previously worked Callsigns showing the B4 indicator.

    - WAE Country Names: Incorrect name shown in Callsign tooltip. This was a
       cosmetic defect only. The correct dxcc code was still used for alerting.

    - Country Name Display: US based callsigns missing the State code after the
       Country name when the Callsign is a B4.


locked Re: JTAlert alt version disappears

Michael Coslo <mjcn3li@...>
 

On Mar 31, 2020, at 11:42 AM, g4wjs <bill.8@...> wrote:

Any AV product that quarantines your files without a means to restore them as if nothing had happened is not worth having.

I don’t disagree. My major issue is an AV that decides that innocent programs are a threat, then you pass them through, then asserting they are a threat again, then you get in Groundhog day mode of repeated quarantine and restore - and to me not much difference between restore and reinstall.

Anyhow, thanks for the help - it’s just Windows being Windows.

- 73 Mike N3LI -


locked Re: JTAlert alt version disappears

g4wjs
 

Mike,

you might not be able to see the quarantined objects in the Windows file system, but they are there in the quarantine store and can definitely be restored. I don't have any there but if there were I could seelct it and click teh "Restore" button:


Any AV product that quarantines your files without a means to restore them as if nothing had happened is not worth having.

73
Bill
G4WJS.

On 31/03/2020 16:37, Michael Coslo wrote:
Although in this case, there is now no program to take out of quarantine. So that won’t work. 

To me, the mystery is why it takes several  days until Defender kills the program.

I’ll do a deep scan to find any remains. Mostly out of curiosity though, because reinstalling is easier than restoring. A lot of things can break when doing that.

- 73 Mike N3LI - 

On Mar 31, 2020, at 9:38 AM, g4wjs <bill.8@...> wrote:

Hi Michael,

on the few occasions I've had Windows Defender quarantine an application it has been a simple matter of going to the quarantine list and restoring it, no fuss, no reinstall necessary.

73
Bill
G4WJS.

On 31/03/2020 13:49, Michael Coslo wrote:
Windows Defender is the culprit here.

Apparently the option is to reinstall the program. Looking at the Defender's history, you can see when and where it decided to kill JTJAlert. It looked like reinstalling was the best option.  Of course, I could shut Windows Defender off.  Naaah!

I reinstalled it with a two stage process that I happened upon. I reinstalled the first time, and Defender was really not happy at all.  I did set Defender to allow it to pass through, but the program was already gone. Very odd, that. So I tried reinstalling again, and it allowed it this time. So it’s working for the moment. I’ll just expect to reinstall it every so often as I fight with Windows and it’s stupid surprises.

It’s a pity that Windows is the defacto standard. Because it is the VHS tape format of operating systems. I do 99 percent of my work on my MacOS and Linux machines, and 99 percent of my troubleshooting on my Windows 10 machines. 

Granted, it’s not the worst W10 problem I’ve had. Updates were causing SSDR for Flex to rename all of the sound drivers  to one name, only suffix indexed by 1.  SSDR has a whole slew of audio drivers. So ya gotta do a whole slew of digging around and renaming back to what they originally were. 

- 73 - 
- Michael Coslo -
Frequency Coordinator, Beaver Stadium
814-404-3991

mjc5@...
mjcn3li@...



On Mar 30, 2020, at 7:57 PM, g4wjs <bill.8@...>
 wrote:

On 31/03/2020 00:55, Michael Coslo wrote:

Hi all,

About 5 minutes ago, I quit JTAlert alternate to do something else for a minute. I went to start it again and….it’s gone. As in the program is gone. JTAlert for JTDX is still there as is the standard JTAlert for WSJT-X. The alt version of JTAlert shortcuts are still there. While I can do some pretty dumb things at times, I did nothing but exit the program. Now once is one thing, but this is the second time it happened. Happened about a week and a half ago. Is this windows shenanigans? Is it by some chance related to Windows defender spanking me for allowing the program through when it tells me it is a trojan? Anyone else?

- 73 N3LI -
- Michael Coslo -

Hi Michael,

I suspect your anti-virus software has quarantined it. There should be an option to restore it.

73
Bill
G4WJS.



-- 
73
Bill
G4WJS.



-- 
73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Re: JTAlert alt version disappears

Michael Coslo <mjcn3li@...>
 

Although in this case, there is now no program to take out of quarantine. So that won’t work.

To me, the mystery is why it takes several days until Defender kills the program.

I’ll do a deep scan to find any remains. Mostly out of curiosity though, because reinstalling is easier than restoring. A lot of things can break when doing that.

- 73 Mike N3LI -

On Mar 31, 2020, at 9:38 AM, g4wjs <bill.8@...> wrote:

Hi Michael,

on the few occasions I've had Windows Defender quarantine an application it has been a simple matter of going to the quarantine list and restoring it, no fuss, no reinstall necessary.

73
Bill
G4WJS.

On 31/03/2020 13:49, Michael Coslo wrote:
Windows Defender is the culprit here.

Apparently the option is to reinstall the program. Looking at the Defender's history, you can see when and where it decided to kill JTJAlert. It looked like reinstalling was the best option. Of course, I could shut Windows Defender off. Naaah!

I reinstalled it with a two stage process that I happened upon. I reinstalled the first time, and Defender was really not happy at all. I did set Defender to allow it to pass through, but the program was already gone. Very odd, that. So I tried reinstalling again, and it allowed it this time. So it’s working for the moment. I’ll just expect to reinstall it every so often as I fight with Windows and it’s stupid surprises.

It’s a pity that Windows is the defacto standard. Because it is the VHS tape format of operating systems. I do 99 percent of my work on my MacOS and Linux machines, and 99 percent of my troubleshooting on my Windows 10 machines.

Granted, it’s not the worst W10 problem I’ve had. Updates were causing SSDR for Flex to rename all of the sound drivers to one name, only suffix indexed by 1. SSDR has a whole slew of audio drivers. So ya gotta do a whole slew of digging around and renaming back to what they originally were.

- 73 -
- Michael Coslo -
Frequency Coordinator, Beaver Stadium
814-404-3991

mjc5@...
mjcn3li@...



On Mar 30, 2020, at 7:57 PM, g4wjs <bill.8@...>
wrote:

On 31/03/2020 00:55, Michael Coslo wrote:

Hi all,

About 5 minutes ago, I quit JTAlert alternate to do something else for a minute. I went to start it again and….it’s gone. As in the program is gone. JTAlert for JTDX is still there as is the standard JTAlert for WSJT-X. The alt version of JTAlert shortcuts are still there. While I can do some pretty dumb things at times, I did nothing but exit the program. Now once is one thing, but this is the second time it happened. Happened about a week and a half ago. Is this windows shenanigans? Is it by some chance related to Windows defender spanking me for allowing the program through when it tells me it is a trojan? Anyone else?

- 73 N3LI -
- Michael Coslo -
Hi Michael,

I suspect your anti-virus software has quarantined it. There should be an option to restore it.

73
Bill
G4WJS.



--
73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Re: JTAlert alt version disappears

g4wjs
 

Hi Michael,

on the few occasions I've had Windows Defender quarantine an application it has been a simple matter of going to the quarantine list and restoring it, no fuss, no reinstall necessary.

73
Bill
G4WJS.

On 31/03/2020 13:49, Michael Coslo wrote:
Windows Defender is the culprit here.

Apparently the option is to reinstall the program. Looking at the Defender's history, you can see when and where it decided to kill JTJAlert. It looked like reinstalling was the best option.  Of course, I could shut Windows Defender off.  Naaah!

I reinstalled it with a two stage process that I happened upon. I reinstalled the first time, and Defender was really not happy at all.  I did set Defender to allow it to pass through, but the program was already gone. Very odd, that. So I tried reinstalling again, and it allowed it this time. So it’s working for the moment. I’ll just expect to reinstall it every so often as I fight with Windows and it’s stupid surprises.

It’s a pity that Windows is the defacto standard. Because it is the VHS tape format of operating systems. I do 99 percent of my work on my MacOS and Linux machines, and 99 percent of my troubleshooting on my Windows 10 machines. 

Granted, it’s not the worst W10 problem I’ve had. Updates were causing SSDR for Flex to rename all of the sound drivers  to one name, only suffix indexed by 1.  SSDR has a whole slew of audio drivers. So ya gotta do a whole slew of digging around and renaming back to what they originally were. 

- 73 - 
- Michael Coslo -
Frequency Coordinator, Beaver Stadium
814-404-3991
mjc5@...
mjcn3li@...

On Mar 30, 2020, at 7:57 PM, g4wjs <bill.8@...> wrote:

On 31/03/2020 00:55, Michael Coslo wrote:
Hi all,

About 5 minutes ago, I quit JTAlert alternate to do something else for a minute. I went to start it again and….it’s gone. As in the program is gone. JTAlert for JTDX is still there as is the standard JTAlert for WSJT-X. The alt version of JTAlert shortcuts are still there. While I can do some pretty dumb things at times, I did nothing but exit the program. Now once is one thing, but this is the second time it happened. Happened about a week and a half ago. Is this windows shenanigans? Is it by some chance related to Windows defender spanking me for allowing the program through when it tells me it is a trojan? Anyone else?

- 73 N3LI -
- Michael Coslo -
Hi Michael,

I suspect your anti-virus software has quarantined it. There should be an option to restore it.

73
Bill
G4WJS.



-- 
73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Re: JTAlert alt version disappears

Michael Coslo <mjcn3li@...>
 

Windows Defender is the culprit here.

Apparently the option is to reinstall the program. Looking at the Defender's history, you can see when and where it decided to kill JTJAlert. It looked like reinstalling was the best option. Of course, I could shut Windows Defender off. Naaah!

I reinstalled it with a two stage process that I happened upon. I reinstalled the first time, and Defender was really not happy at all. I did set Defender to allow it to pass through, but the program was already gone. Very odd, that. So I tried reinstalling again, and it allowed it this time. So it’s working for the moment. I’ll just expect to reinstall it every so often as I fight with Windows and it’s stupid surprises.

It’s a pity that Windows is the defacto standard. Because it is the VHS tape format of operating systems. I do 99 percent of my work on my MacOS and Linux machines, and 99 percent of my troubleshooting on my Windows 10 machines.

Granted, it’s not the worst W10 problem I’ve had. Updates were causing SSDR for Flex to rename all of the sound drivers to one name, only suffix indexed by 1. SSDR has a whole slew of audio drivers. So ya gotta do a whole slew of digging around and renaming back to what they originally were.

- 73 -
- Michael Coslo -
Frequency Coordinator, Beaver Stadium
814-404-3991
mjc5@...
mjcn3li@...

On Mar 30, 2020, at 7:57 PM, g4wjs <bill.8@...> wrote:

On 31/03/2020 00:55, Michael Coslo wrote:
Hi all,

About 5 minutes ago, I quit JTAlert alternate to do something else for a minute. I went to start it again and….it’s gone. As in the program is gone. JTAlert for JTDX is still there as is the standard JTAlert for WSJT-X. The alt version of JTAlert shortcuts are still there. While I can do some pretty dumb things at times, I did nothing but exit the program. Now once is one thing, but this is the second time it happened. Happened about a week and a half ago. Is this windows shenanigans? Is it by some chance related to Windows defender spanking me for allowing the program through when it tells me it is a trojan? Anyone else?

- 73 N3LI -
- Michael Coslo -
Hi Michael,

I suspect your anti-virus software has quarantined it. There should be an option to restore it.

73
Bill
G4WJS.



--
73
Bill
G4WJS.



locked Re: JTAlert alt version disappears

g4wjs
 

On 31/03/2020 00:55, Michael Coslo wrote:
Hi all,

About 5 minutes ago, I quit JTAlert alternate to do something else for a minute. I went to start it again and….it’s gone. As in the program is gone. JTAlert for JTDX is still there as is the standard JTAlert for WSJT-X. The alt version of JTAlert shortcuts are still there. While I can do some pretty dumb things at times, I did nothing but exit the program. Now once is one thing, but this is the second time it happened. Happened about a week and a half ago. Is this windows shenanigans? Is it by some chance related to Windows defender spanking me for allowing the program through when it tells me it is a trojan? Anyone else?

- 73 N3LI -
- Michael Coslo -
Hi Michael,

I suspect your anti-virus software has quarantined it. There should be an option to restore it.

73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked JTAlert alt version disappears

Michael Coslo <mjcn3li@...>
 

Hi all,

About 5 minutes ago, I quit JTAlert alternate to do something else for a minute. I went to start it again and….it’s gone. As in the program is gone. JTAlert for JTDX is still there as is the standard JTAlert for WSJT-X. The alt version of JTAlert shortcuts are still there. While I can do some pretty dumb things at times, I did nothing but exit the program. Now once is one thing, but this is the second time it happened. Happened about a week and a half ago. Is this windows shenanigans? Is it by some chance related to Windows defender spanking me for allowing the program through when it tells me it is a trojan? Anyone else?

- 73 N3LI -
- Michael Coslo -
Frequency Coordinator, Beaver Stadium
814-404-3991
mjc5@...
mjcn3li@...


locked Re: Log4om v2

Lawrence Godek
 

Dave,
I don't see it either but several folks have said that they use it with V2 also, so i don't
know why i can't get it to work.  I used it with V1 and it performed just fine.  I even use
VE7CC cluster as a stand alone program occasionally, just don't see any way to get it to
run in V2.  When you look at the V2 helpfiles for setting up the cluster, it shows you
should be able to download a whole bunch of clusters and then you pick out the one
you want to use as well as a backup.  I can't make my V2 do that so it only shows QRZ.COM
like you said.  Gotta call Mike, W9MBD and talk to him as he's pretty much an expert on
this stuff where as i'm just an old geezer trying to remember how to type!

Larry W0OGH


On 3/30/2020 2:58 PM, Dave Garber wrote:
Lawrence, almost missed you question, looks like it was in the middle of a new conversation..  I dont remember ever seeing cluster in jtalert, only qrz lookup 'q' at the end of the log line.  perhaps it was within your log of choice??


Dave Garber
VE3WEJ / VE3IE


On Mon, Mar 30, 2020 at 10:49 AM Lawrence Godek <LawrenceG94@...> wrote:
Hi herb and thanks for the offer to help.  I have the new version of JTAlert (2.16.0)  working ok, i think.
The think that is bothering me most now is that i can't get the cluster function to do anything.
It doesn't do anything like it shows in the V2 help file.  Got some idea on this?
I normally use the VE7CC cluster but i don't see a way to implement it.
Another mystry.  I worked on this almost all day yesterday, finally giving up around 6 pm
as i wasn't thinking straight anymore. HI!
Larry W0OGH


On 3/29/2020 5:42 PM, WB8ASI Herb wrote:
Open the JTAlert Help tab.   Click on Log4OM under the logging item.  Send me a note if you need help.  I've got JTA and Log4OMv2 working smoothly. 73, Herb WB8ASI
On March 29, 2020 at 8:24 PM Lawrence Godek <LawrenceG94@...> wrote:

I jumped on the Log4om v2 bandwagon today to se what the differences are.  Quite a lot, looks like a total overhaul.  Fist I'm  having a heck of a time getting a cluster working. Secondly, I know it's been mentioned on here some references to making it work with JTAlert .  As usual I have no idea where to look.  All the places I could think of turned up nothing.  How about a refresher please.
Tks Larry/w0ogh 

 



locked Re: Log4om v2

Dave Garber
 

Lawrence, almost missed you question, looks like it was in the middle of a new conversation..  I dont remember ever seeing cluster in jtalert, only qrz lookup 'q' at the end of the log line.  perhaps it was within your log of choice??


Dave Garber
VE3WEJ / VE3IE


On Mon, Mar 30, 2020 at 10:49 AM Lawrence Godek <LawrenceG94@...> wrote:
Hi herb and thanks for the offer to help.  I have the new version of JTAlert (2.16.0)  working ok, i think.
The think that is bothering me most now is that i can't get the cluster function to do anything.
It doesn't do anything like it shows in the V2 help file.  Got some idea on this?
I normally use the VE7CC cluster but i don't see a way to implement it.
Another mystry.  I worked on this almost all day yesterday, finally giving up around 6 pm
as i wasn't thinking straight anymore. HI!
Larry W0OGH


On 3/29/2020 5:42 PM, WB8ASI Herb wrote:
Open the JTAlert Help tab.   Click on Log4OM under the logging item.  Send me a note if you need help.  I've got JTA and Log4OMv2 working smoothly. 73, Herb WB8ASI
On March 29, 2020 at 8:24 PM Lawrence Godek <LawrenceG94@...> wrote:

I jumped on the Log4om v2 bandwagon today to se what the differences are.  Quite a lot, looks like a total overhaul.  Fist I'm  having a heck of a time getting a cluster working. Secondly, I know it's been mentioned on here some references to making it work with JTAlert .  As usual I have no idea where to look.  All the places I could think of turned up nothing.  How about a refresher please.
Tks Larry/w0ogh 

 


locked Re: DXKeeper FT4 Option

Dave AA6YQ
 

+ AA6YQ comments below

Dave, It appears that the problem is solved. I had an old revision, updated it, and there is was. Wanted to thank you and all the folks that responded to my posting, really appreciate it.

+ I'm glad you got it sorted, John!

73,

Dave, AA6YQ


locked Re: DXKeeper FT4 Option

 

Dave, It appears that the problem is solved. I had an old revision,  updated it, and there is was. Wanted to thank you and all the folks that responded to my posting, really appreciate it. I often wonder how I could have been so smart at 18 and now that I'm 79 how I got so stupid. HI.
Thanks again and 73's,
John    NA6Y


locked Re: Sort Order

Jim Cooper
 

On 29 Mar 2020 at 18:27, Marlo Montanaro - KA2IRQ wrote:

> I'm just not seeing that Jim... what Decodes window?  In JTAlert
> Settings? Not finding it.

You can open the Decodes window in several ways ...

Simplest is in JTalert, click  View / Decodes window;
or just click F9

In Settings / Manage Settings / Window / Decodes
you can permanently enable it by checking the [ ] at top.

graphic

  


locked Re: Log4om v2

WB8ASI Herb
 

Hi Larry,   I'm using JTA 2.16.1 and Log4OMv2 2.4.0.0.   I use cluster VE7CC-1 as primary and AE5E for backup.   Make sure you force an update to your V2 Help File.  Below is a pic of my Cluster management screen.   You can find it via V2 menu Connect>Telenet cluster>Connection tab.  You need to Disconnect while editing.  Pick the cluster(s) you want and add using the +.  You can edit, check port, add SSID, and remember to save.  Highlight the one you want as primary and click the crown.  Then remember to Connect.  You should see it working on the Management tab.  Also the Cluster tab will show you what V2 is tracking with the filters you have chosen.  The cluster also shows on the Main V2 screen on the Cluster (F8) tab and via the globe icon upper right.  Each location can have different filters and different layouts.  Not sure where you are getting hung up, but hope this helps you find your way.  73, Herb WB8ASI

On March 30, 2020 at 10:49 AM Lawrence Godek <LawrenceG94@...> wrote:

Hi herb and thanks for the offer to help.  I have the new version of JTAlert (2.16.0)  working ok, i think.
The think that is bothering me most now is that i can't get the cluster function to do anything.
It doesn't do anything like it shows in the V2 help file.  Got some idea on this?
I normally use the VE7CC cluster but i don't see a way to implement it.
Another mystry.  I worked on this almost all day yesterday, finally giving up around 6 pm
as i wasn't thinking straight anymore. HI!
Larry W0OGH


On 3/29/2020 5:42 PM, WB8ASI Herb wrote:
Open the JTAlert Help tab.   Click on Log4OM under the logging item.  Send me a note if you need help.  I've got JTA and Log4OMv2 working smoothly. 73, Herb WB8ASI
On March 29, 2020 at 8:24 PM Lawrence Godek <LawrenceG94@...> wrote:

I jumped on the Log4om v2 bandwagon today to se what the differences are.  Quite a lot, looks like a total overhaul.  Fist I'm  having a heck of a time getting a cluster working. Secondly, I know it's been mentioned on here some references to making it work with JTAlert .  As usual I have no idea where to look.  All the places I could think of turned up nothing.  How about a refresher please.
Tks Larry/w0ogh 

 


 


locked Re: Log4om v2

Lawrence Godek
 

Hi herb and thanks for the offer to help.  I have the new version of JTAlert (2.16.0)  working ok, i think.
The think that is bothering me most now is that i can't get the cluster function to do anything.
It doesn't do anything like it shows in the V2 help file.  Got some idea on this?
I normally use the VE7CC cluster but i don't see a way to implement it.
Another mystry.  I worked on this almost all day yesterday, finally giving up around 6 pm
as i wasn't thinking straight anymore. HI!
Larry W0OGH


On 3/29/2020 5:42 PM, WB8ASI Herb wrote:
Open the JTAlert Help tab.   Click on Log4OM under the logging item.  Send me a note if you need help.  I've got JTA and Log4OMv2 working smoothly. 73, Herb WB8ASI
On March 29, 2020 at 8:24 PM Lawrence Godek <LawrenceG94@...> wrote:

I jumped on the Log4om v2 bandwagon today to se what the differences are.  Quite a lot, looks like a total overhaul.  Fist I'm  having a heck of a time getting a cluster working. Secondly, I know it's been mentioned on here some references to making it work with JTAlert .  As usual I have no idea where to look.  All the places I could think of turned up nothing.  How about a refresher please.
Tks Larry/w0ogh 

 


locked Re: Auto start JTAlert with Win4Icom

Jacques Corbu
 
Edited

Hello
I use win4icom and auto start JTAlert from the software via a batch file and it works  details on the win4icom forum
Thanks

sample 

cmd /c start ""  "C:\Program Files (x86)\HamApps\JTAlert" /wsjtx

save the batch file on computer and point Win4icom to it 


locked Re: ACLog shows only (incorrect) 6m freq before logging

HamApps Support (VK3AMA)
 

On 30/03/2020 8:40 am, Dev Null wrote:
The only thing I disliked about this arrangement was that since I was relying on ACLog for B4 status, previous QSO's etc. - that was broken.

Simple workaround, two-mouse clicks when you change a Band.

With WSJT-X controlling your radio and Cat control disabled in ACLog, ACLog is not following any Band Changes which is to be expected. When a Callsign is sent to ACLog by JTAlert ACLog does its lookups based on the Band set in ACLog which may not be the operating Band. All you need to do is change the Band in ACLog, a single click on the Band combo box. The actual frequency is not important, only the Band for the ACLog lookup purposes. You just need to get in the habit of changing the Band in ACLog whenever you change the WSJT-X Band. If you forget, no harm as the correct Band/Frequency is always logged as that comes from WSJT-X which is communicating with your rig.

   
Alternatively, you can type the Band number into that field.

de Laurie VK3AMA


locked Re: Auto start JTAlert with Win4Icom

HamApps Support (VK3AMA)
 

On 30/03/2020 8:44 am, gary.sewell@... wrote:
I tried to create a shortcut with the /wsjtx on the end, but when I tell Win4icom the location of the shortcut, it expands the link to the actual exe file and does not execute the /wsjtx portion. It would work if we had an option in JTAlert to start either WSJT-X or JTDX only.
Or if Win4icom allowed for command-line parameters. I see this as more of a Win4icom issue than a JTAlert issue.

An alternate approach would be to have JTAlert auto-start all your programs including Win4icom. It supports executables requiring command-line parameters (eg WSJT-X with a --rig-name param) and will shutdown the applications when JTAlert is closed if required. Delays can be set to ensure applications startup correctly and in the required order.

See the Settings Windows, "Applications -> Auto-Start" section.

de Laurie VK3AMA