Date   

locked Re: F9 DECODE WINDOW

HamApps Support (VK3AMA)
 

On 12/09/2020 8:46 pm, Scott L wrote:
Good morning, when I hit F9 my decode window opens up. I used to have data in there and everything ran just fine. For some reason, maybe since the update, its now blank. The decode check box is checked under settings, I have no filters on, and in the other decode smaller window, I do see calls in that. 

Any help would be appreciated

Thanks,
Scott
You need to delete the decodes database file.

Recent support group messages have the answer.
see. https://hamapps.groups.io/g/Support/message/31568

de Laurie VK3AMA


locked Re: JT Alert intermittent

HamApps Support (VK3AMA)
 

On 12/09/2020 10:35 am, James Bricker wrote:

JT Alert intermittently alerts me that my call sign is present.  Its clearly displayed on the WSJT-X screen but no alert.

Has anyone else reported this intermittent operation?

Any suggestions?

I'm running version 2.15.9 with Windows 7 (32 bit) on a Dell desktop (Intel E2160 CPU @ 1.8 Ghz with 2 Gig of memory.)

Thanks,
Jim Bricker
N3JHB

What does "Intermittent" mean in this context? Lack of Callsigns coloring and/or lack of audio announcement for the Own Callsign alert?

de Laurie VK3AMA


locked Re: F9 DECODE WINDOW

Jim Nuytens
 

Scott,

Close the Decode window.
Navigate to the Decode folder buried under the App Data folder (see attached example).
Delete the 6 files I've highlighted in red.
Re-open the Decode window, using the F9 key.
Everything should return to normal.

Jim

On 9/12/2020 10:46, Scott L wrote:
Good morning, when I hit F9 my decode window opens up. I used to have data in there and everything ran just fine. For some reason, maybe since the update, its now blank. The decode check box is checked under settings, I have no filters on, and in the other decode smaller window, I do see calls in that.

Any help would be appreciated

Thanks,
Scott


locked Timing Adjustment.

JoAnn Donaldson
 
Edited

Reading the JTAlert Docs, it mentions that you can adjust the how to adjust the Check QSO Log Record time in JTAlert' but I can not find it under Settings/Manage Settings/Misc. See the two attach files. One shows it. This is from the N3FJP Digital Hits Page and the other which does not show it is from Settings/Manage Settings/MISc. has this setting been removed? I am having problems with JTAlert not confirming contact with my ACLog.
 
JoAnn - AB8YZInline image


locked Re: JTAlerts - WSJT-X communications failure

g4wjs
 

On 12/09/2020 17:56, Michael wrote:
I get the following error message The JTAlerts help file and the "About" for 2.16.13 listing do  not match so I cannot see what is wrong. Windows ten updated last week to the listing below
Hi Michael,

either JTAlert is not listening for connections on your local subnet (192.168.0/8) or your firewall is blocking it. Since JTAlert requires that WSJT-X be run on the same host as itself you should use either 127.0.0.1 or better still a suitable multicast group IP address like 239.255.0.0. Set that in WSJT-X "Settings->Reporting->UDP Server".



--
73
Bill
G4WJS.


locked JTAlerts - WSJT-X communications failure

Michael
 

I get the following error message The JTAlerts help file and the "About"  for 2.16.13 listing do  not match so I cannot see what is wrong. Windows ten updated last week to the listing below






Mike W7OSG


locked Re: GB1COR

John Holmes W9ILY
 

It's at the very top of the Marathon list, Jim. Just another call to add to the database.
John W9ILY


locked Re: JT Alert intermittent

Jim N6VH
 


On 9/11/2020 5:35 PM, James Bricker wrote:
Hello:
I have read several positive reviews on JT Alert so I will start off by saying I believe my problem is in my system and not a bug in JT Alert.

Currently, the only feature of JT Alert that I'm using is the "Alert on My Call" while operating WSJT-X in FT-8 mode.

JT Alert intermittently alerts me that my call sign is present.  Its clearly displayed on the WSJT-X screen but no alert.

Has anyone else reported this intermittent operation?

Any suggestions?

I'm running version 2.15.9 with Windows 7 (32 bit) on a Dell desktop (Intel E2160 CPU @ 1.8 Ghz with 2 Gig of memory.)

Thanks,
Jim Bricker
N3JHB




Jim,

I don't know if this will solve your problem, but you might want to install the latest version of JTAlert - 2.16.13.

73,

Jim N6VH


locked F9 DECODE WINDOW

Scott L
 

Good morning, when I hit F9 my decode window opens up. I used to have data in there and everything ran just fine. For some reason, maybe since the update, its now blank. The decode check box is checked under settings, I have no filters on, and in the other decode smaller window, I do see calls in that. 

Any help would be appreciated

Thanks,
Scott


locked Re: Using JTALert and ACLog on different computers

TomK
 

Warning: You may know some or all of this but it may help others to repeat it every so often.

 

Re running across different computers:

Assuming workstations are on the same network with IP addresses in the same net, it “should” behave the same.

If on different “subnets”, it can be problematic but that is rarely needed in the same LAN under the same Ethernet/Wi-Fi router.

My home has 6 workstations, 16+ networked devices, and 2 AP/Routers all with no need for multiple subnets.

Ergo, the basic homogenous setup below should still hold water.

 

I have an almost identical DRW (Digital Radio Workflow) with most of same apps with direct UDP messaging and no forwards.
That is not to say I had not used forwarding. I did when the apps were still maturing.  

But thanks the efforts of some really great coders, that it is no longer needed or recommended.

 

The gist of my flow includes the interconnection of the following apps that required a relatively small effort:

 

WSJT  à   ( GridTracker + JTAlert )

 

   JTAlert  à   ( ACLog + QRZ + HRDLog + HamQTH + eQSL + ClugLog + DXLab + HRD + Log4OM )

 

   GridTracker à ( PSKRpt + QRZ + Clublog + HRDLog + Cloudlog + eQSL + LoTW + N1MM + Log4OM + N3FJPLogs + DXKeeper + HRD )

 

   There’s a few more apps/services I may have left out but the above covers 99% of them.

 

Basic UDP setup for the above DRW:

 

   WSJT  -->  JT-Alert via Multicast UDP messaging

       WSJT’s UDP address is set to a value in a range that implicitly enables Multicast which is 139.0.0.0 – 139.255.255.255. 
       … The actual UDP Port number can be left at the default of 2237 except in rare cases where that port may be in use.

       … I recommend avoiding 139.0.0.0 & 139.255.255.255 as these have special meanings in some network architectures.

       … I have been using 139.0.0.1 without any issues for a while now.

 

    JT-Alert’s Multicast UDP Port and Address is automatically set.

    … When JTA boots it searches for and uses the WSJT settings with no user intervention

 

   GridTracker’s Multicast UDP Port ad Address needs to be manually set to the same values as WSJT

   … However, one needs to click the “Multicast?” Radio Button in the settings dialog to explicitly enable Multicast.

 

   JTAlert à AC Log  - Another automatic setting.  Nothing to do.

 

   Other than entering your ID & Password for each log book and/or services you may be using, you are done!

 

All the above apps, database, and web services should then be talking to each other directly with no forwarding needed.

 

That total workflow has been working for me for 16hrs/day with only an occasional PC crash due to the sheer CPU/UDP load.

That’s because my system has about 20-30 apps and 100’s of services running concurrently with 16TB of storage on 10+ drives.

 

Hope that helps.  I’m working on printed and video tutorials for the above DRW that should be more visual and explanatory.

 

I don’t claim perfection in the above diatribe and welcome any probable corrections needed by those who that know better 😊

TomK 73

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Dave Garber
Sent: Friday, September 11, 2020 5:57 PM
To: Support@hamapps.groups.io
Subject: Re: [HamApps] Using JTALert and ACLog on different computers

 

I have jtalert sending to gridtracker ( on a different computer), then Gridtracker is sending to n3fjp, on another computer.   I was using this only as a backup to my main log.  but it worked, except the callsign did not get entered into the window.    but it did log, when I click on log it in wsjtx

 

Dave Garber

VE3WEJ / VE3IE

 

 

On Fri, Sep 11, 2020 at 3:08 PM JoAnn Donaldson via groups.io <joannplano2005=yahoo.com@groups.io> wrote:

Try #2.

 

I have ACLog on a different computer than the computer that JTAlert is on. The computer that JTALert is on has an Network Drive to the ACLog Computer. I amusing the Manual mode to connect with ACLog. I can not get the Auto Mode to work. When I click on a station, JTAlert sends the Pre-Load. The preload works OK. When I have a confirmed contact and tell WSIT-X to Log the contact. JTAlert sends the Log entry but most times I get an Database Error in ACLog. I suppect it happens when JTALert tries to confirm that the contact was logged. When the Pre-Load info is sent, it fills out the boxes on ACLog. When I click the Log button in WSiT-X, at first ACLog logs the contact, then the Database error occurs and the logged entry is then wiped. Why do you require a physical path to the ACLog Database. I suspect that using the Network Drive path is causing the problem. Other programs like N7YQ's PSK and RTTY programs ONLY require the IP Address and Port Number of ACLog or one of the Contest Loggers. They DO NOT require a physical path to the ACLog Database.

 

On Friday, September 11, 2020, 2:07:08 PM CDT, JoAnn Donaldson <joannplano2005@...> wrote:

 

 

Did not see this popup on my screen, so re-sending it.

 

JoAnn Donaldson - AB8YZ

 

On Thursday, September 10, 2020, 6:41:44 PM CDT, JoAnn Donaldson <joannplano2005@...> wrote:

 

 

 

I have ACLog on a different computer than the computer that JTAlert is on. The computer that JTALert is on has an Network Drive to the ACLog Computer. I amusing the Manual mode to connect with ACLog. I can not get the Auto Mode to work. When I click on a station, JTAlert sends the Pre-Load. The preload works OK. When I have a confirmed contact and tell WSIT-X to Log the contact. JTAlert sends the Log entry but most times I get an Database Error in ACLog. I suppect it happens when JTALert tries to confirm that the contact was logged. When the Pre-Load info is sent, it fills out the boxes on ACLog. When I click the Log button in WSiT-X, at first ACLog logs the contact, then the Database error occurs and the logged entry is then wiped. Why do you require a physical path to the ACLog Database. I suspect that using the Network Drive path is causing the problem. Other programs like N7YQ's PSK and RTTY programs ONLY require the IP Address and Port Number of ACLog or one of the Contest Loggers. They DO NOT require a physical path to the ACLog Database.

 

 

JoAnn Donaldson - AB8YZ

 


locked JT Alert intermittent

jhbricker@...
 

Hello:
I have read several positive reviews on JT Alert so I will start off by saying I believe my problem is in my system and not a bug in JT Alert.

Currently, the only feature of JT Alert that I'm using is the "Alert on My Call" while operating WSJT-X in FT-8 mode.

JT Alert intermittently alerts me that my call sign is present.  Its clearly displayed on the WSJT-X screen but no alert.

Has anyone else reported this intermittent operation?

Any suggestions?

I'm running version 2.15.9 with Windows 7 (32 bit) on a Dell desktop (Intel E2160 CPU @ 1.8 Ghz with 2 Gig of memory.)

Thanks,
Jim Bricker
N3JHB

Virus-free. www.avast.com


locked Re: Using JTALert and ACLog on different computers

Dave Garber
 

I have jtalert sending to gridtracker ( on a different computer), then Gridtracker is sending to n3fjp, on another computer.   I was using this only as a backup to my main log.  but it worked, except the callsign did not get entered into the window.    but it did log, when I click on log it in wsjtx

Dave Garber
VE3WEJ / VE3IE


On Fri, Sep 11, 2020 at 3:08 PM JoAnn Donaldson via groups.io <joannplano2005=yahoo.com@groups.io> wrote:
Try #2.

I have ACLog on a different computer than the computer that JTAlert is on. The computer that JTALert is on has an Network Drive to the ACLog Computer. I amusing the Manual mode to connect with ACLog. I can not get the Auto Mode to work. When I click on a station, JTAlert sends the Pre-Load. The preload works OK. When I have a confirmed contact and tell WSIT-X to Log the contact. JTAlert sends the Log entry but most times I get an Database Error in ACLog. I suppect it happens when JTALert tries to confirm that the contact was logged. When the Pre-Load info is sent, it fills out the boxes on ACLog. When I click the Log button in WSiT-X, at first ACLog logs the contact, then the Database error occurs and the logged entry is then wiped. Why do you require a physical path to the ACLog Database. I suspect that using the Network Drive path is causing the problem. Other programs like N7YQ's PSK and RTTY programs ONLY require the IP Address and Port Number of ACLog or one of the Contest Loggers. They DO NOT require a physical path to the ACLog Database.

On Friday, September 11, 2020, 2:07:08 PM CDT, JoAnn Donaldson <joannplano2005@...> wrote:


Did not see this popup on my screen, so re-sending it.

JoAnn Donaldson - AB8YZ

On Thursday, September 10, 2020, 6:41:44 PM CDT, JoAnn Donaldson <joannplano2005@...> wrote:



I have ACLog on a different computer than the computer that JTAlert is on. The computer that JTALert is on has an Network Drive to the ACLog Computer. I amusing the Manual mode to connect with ACLog. I can not get the Auto Mode to work. When I click on a station, JTAlert sends the Pre-Load. The preload works OK. When I have a confirmed contact and tell WSIT-X to Log the contact. JTAlert sends the Log entry but most times I get an Database Error in ACLog. I suppect it happens when JTALert tries to confirm that the contact was logged. When the Pre-Load info is sent, it fills out the boxes on ACLog. When I click the Log button in WSiT-X, at first ACLog logs the contact, then the Database error occurs and the logged entry is then wiped. Why do you require a physical path to the ACLog Database. I suspect that using the Network Drive path is causing the problem. Other programs like N7YQ's PSK and RTTY programs ONLY require the IP Address and Port Number of ACLog or one of the Contest Loggers. They DO NOT require a physical path to the ACLog Database.


JoAnn Donaldson - AB8YZ


locked Re: GB1COR

Jim N6VH
 

On 9/11/2020 12:37 PM, John Holmes W9ILY wrote:
I believe the callsign database may have overlooked GB1COR as being in the Shetland Islands for DX Marathon credit.
73,
John  W9ILY
John,

I just looked, and I don't see Shetland Islands in the Marathon list in JTAlert. Laurie might want to fix that.

73,

Jim N6VH


locked GB1COR

John Holmes W9ILY
 

I believe the callsign database may have overlooked GB1COR as being in the Shetland Islands for DX Marathon credit.
73,
John  W9ILY


locked Re: Using JTALert and ACLog on different computers

JoAnn Donaldson
 

Try #2.

I have ACLog on a different computer than the computer that JTAlert is on. The computer that JTALert is on has an Network Drive to the ACLog Computer. I amusing the Manual mode to connect with ACLog. I can not get the Auto Mode to work. When I click on a station, JTAlert sends the Pre-Load. The preload works OK. When I have a confirmed contact and tell WSIT-X to Log the contact. JTAlert sends the Log entry but most times I get an Database Error in ACLog. I suppect it happens when JTALert tries to confirm that the contact was logged. When the Pre-Load info is sent, it fills out the boxes on ACLog. When I click the Log button in WSiT-X, at first ACLog logs the contact, then the Database error occurs and the logged entry is then wiped. Why do you require a physical path to the ACLog Database. I suspect that using the Network Drive path is causing the problem. Other programs like N7YQ's PSK and RTTY programs ONLY require the IP Address and Port Number of ACLog or one of the Contest Loggers. They DO NOT require a physical path to the ACLog Database.

On Friday, September 11, 2020, 2:07:08 PM CDT, JoAnn Donaldson <joannplano2005@...> wrote:


Did not see this popup on my screen, so re-sending it.

JoAnn Donaldson - AB8YZ

On Thursday, September 10, 2020, 6:41:44 PM CDT, JoAnn Donaldson <joannplano2005@...> wrote:



I have ACLog on a different computer than the computer that JTAlert is on. The computer that JTALert is on has an Network Drive to the ACLog Computer. I amusing the Manual mode to connect with ACLog. I can not get the Auto Mode to work. When I click on a station, JTAlert sends the Pre-Load. The preload works OK. When I have a confirmed contact and tell WSIT-X to Log the contact. JTAlert sends the Log entry but most times I get an Database Error in ACLog. I suppect it happens when JTALert tries to confirm that the contact was logged. When the Pre-Load info is sent, it fills out the boxes on ACLog. When I click the Log button in WSiT-X, at first ACLog logs the contact, then the Database error occurs and the logged entry is then wiped. Why do you require a physical path to the ACLog Database. I suspect that using the Network Drive path is causing the problem. Other programs like N7YQ's PSK and RTTY programs ONLY require the IP Address and Port Number of ACLog or one of the Contest Loggers. They DO NOT require a physical path to the ACLog Database.


JoAnn Donaldson - AB8YZ


locked Re: Using JTALert and ACLog on different computers

JoAnn Donaldson
 

Did not see this popup on my screen, so re-sending it.

JoAnn Donaldson - AB8YZ

On Thursday, September 10, 2020, 6:41:44 PM CDT, JoAnn Donaldson <joannplano2005@...> wrote:



I have ACLog on a different computer than the computer that JTAlert is on. The computer that JTALert is on has an Network Drive to the ACLog Computer. I amusing the Manual mode to connect with ACLog. I can not get the Auto Mode to work. When I click on a station, JTAlert sends the Pre-Load. The preload works OK. When I have a confirmed contact and tell WSIT-X to Log the contact. JTAlert sends the Log entry but most times I get an Database Error in ACLog. I suppect it happens when JTALert tries to confirm that the contact was logged. When the Pre-Load info is sent, it fills out the boxes on ACLog. When I click the Log button in WSiT-X, at first ACLog logs the contact, then the Database error occurs and the logged entry is then wiped. Why do you require a physical path to the ACLog Database. I suspect that using the Network Drive path is causing the problem. Other programs like N7YQ's PSK and RTTY programs ONLY require the IP Address and Port Number of ACLog or one of the Contest Loggers. They DO NOT require a physical path to the ACLog Database.


JoAnn Donaldson - AB8YZ


locked Re: after latest patch for win 10, fails to start

chas cartmel
 

Just installed the update so tested JTAlert x etc.
All working here as normal.


73 Charlie

G4EST

www.g4est.me.uk

Stay safe out there

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Román Toledo via groups.io
Sent: 10 September 2020 19:38
To: Support@HamApps.groups.io
Subject: Re: [HamApps] after latest patch for win 10, fails to start

 

[Edited Message Follows]

you might have to re install jtalert as it's working here ok with latest JT  and windows preview build 20206.rs_prerelease.200828-1431 , which is newer than ANY  regular updates most people get


locked Using JTALert and ACLog on different computers

JoAnn Donaldson
 


I have ACLog on a different computer than the computer that JTAlert is on. The computer that JTALert is on has an Network Drive to the ACLog Computer. I amusing the Manual mode to connect with ACLog. I can not get the Auto Mode to work. When I click on a station, JTAlert sends the Pre-Load. The preload works OK. When I have a confirmed contact and tell WSIT-X to Log the contact. JTAlert sends the Log entry but most times I get an Database Error in ACLog. I suppect it happens when JTALert tries to confirm that the contact was logged. When the Pre-Load info is sent, it fills out the boxes on ACLog. When I click the Log button in WSiT-X, at first ACLog logs the contact, then the Database error occurs and the logged entry is then wiped. Why do you require a physical path to the ACLog Database. I suspect that using the Network Drive path is causing the problem. Other programs like N7YQ's PSK and RTTY programs ONLY require the IP Address and Port Number of ACLog or one of the Contest Loggers. They DO NOT require a physical path to the ACLog Database.


JoAnn Donaldson - AB8YZ


locked Re: after latest patch for win 10, fails to start

Román Toledo
 
Edited

you might have to re install jtalert as it's working here ok with latest JT  and windows preview build 20206.rs_prerelease.200828-1431 , which is newer than ANY  regular updates most people get


locked Re: JtAlert call sign colors

HamApps Support (VK3AMA)
 

On 10/09/2020 6:07 am, Gerald Klotz wrote:
It’s has been longer than that. I have been reading and trying to figure it out without changing more things. I finally decided to swallow some pride and ask.

Gerry Klotz

You only option is to start JTAlert without a config file which will cause all existing settings to be lost and to be reset to their defaults.

de Laurie VK3AMA