Date   

locked JTAlert to N3FJP VHF Contest Log v6.2

Mike Coogan
 



With June VHF Contest this weekend, doing a test of JTAlert logging WSJT-X Digi modes to N3FJP VHF Contest Log, v6.2. All appears to work except
receive the above alarm, that JTAlert did not log test Qso's. They are in fact logged as expected. Ignore the alarm??
Thanks Laurie for your great program.
Mike KB7ME



locked Re: Decodes window not always populating

John Holmes W9ILY
 

Laurie,
In have "Delete Old Records" checked and I do not use any filters.
Thanks.

John W9ILY


locked Re: Midway?

Carter
 

In 2002, I worked P5/4L4FN on 15 meter RTTY. The band was not overloaded with amps as you might expect. The only problem was that he was running at the "European" 66 words per minute instead of the more usual 60 wpm. Fortunately, after a couple of calls I realized that and changed the Kantronics KAM+ to 66 wpm and got him on the first call and his QSL.

On Thursday, June 11, 2020, 9:24:14 AM EDT, Jim N6VH <n6vh@...> wrote:



On 6/10/2020 2:36 PM, HamApps Support (VK3AMA) wrote:
On 11/06/2020 6:27 am, Jim N6VH wrote:

Yes, you are right. He is using the /4 to indicate the call area. However, that is interpreted by some logging programs as /AH4, which is Midway. Log4OM v2 (my main logging program) considers AH6P/4 as Midway. Log4Om v1 lists it as Hawaii. N1MM+ shows Midway. DXKeeper, as Laurie already mentioned, doesn't list a country, and asks for a country code to be entered. ACLog lists it as Hawaii.  Swisslog shows Midway. If I enter AH6P/W4, all logs correctly show United States. That would probably be the better call for him to use.

73,

Jim N6VH


Jim, good report, thanks for the tests.

It could be worse, the Station in question could be running portable in Zone 5 and signing "/P5".

de Laurie VK3AMA


locked Re: Sound Test works no audio alert for CQ

HamApps Support (VK3AMA)
 

On 11/06/2020 11:38 pm, Arni Hagen wrote:
Using Sounds 2.5.3, Call Signs 2020.06.08
Sound Test returns spoken "Test 1 2 3"
No audio alert for received my call or CQ
point me to the instructions. Thanks, W5SRO
Check that you have a sounds assigned for these Alerts.

de Laurie VK3AMA


locked Sound Test works no audio alert for CQ

Arni Hagen
 

Using Sounds 2.5.3, Call Signs 2020.06.08
Sound Test returns spoken "Test 1 2 3"
No audio alert for received my call or CQ
point me to the instructions. Thanks, W5SRO


locked Re: JTAlert stops reporting decodes and logging to HRD sporadically #HRD

Jim Denneny
 

Michael

Yesterday I had same issue with JTAlert.  Latest WSJT-X, JTAlert, Win10 v1909.  JTAlert would not capture WSJT-X signals.  Today, it works.  Go figure

73, Jim K7EG


locked Re: Midway?

Jim N6VH
 


On 6/10/2020 2:36 PM, HamApps Support (VK3AMA) wrote:
On 11/06/2020 6:27 am, Jim N6VH wrote:

Yes, you are right. He is using the /4 to indicate the call area. However, that is interpreted by some logging programs as /AH4, which is Midway. Log4OM v2 (my main logging program) considers AH6P/4 as Midway. Log4Om v1 lists it as Hawaii. N1MM+ shows Midway. DXKeeper, as Laurie already mentioned, doesn't list a country, and asks for a country code to be entered. ACLog lists it as Hawaii.  Swisslog shows Midway. If I enter AH6P/W4, all logs correctly show United States. That would probably be the better call for him to use.

73,

Jim N6VH


Jim, good report, thanks for the tests.

It could be worse, the Station in question could be running portable in Zone 5 and signing "/P5".

de Laurie VK3AMA

_._,_._,_


I can't even imagine what the band would sound like - especially when everybody turned on their amps.  :-)

73,

Jim N6VH



locked Re: Download ver 2.16.7 immediately getting removed by Norton

neil_zampella
 

Whenever any antivirus labels something as 'trojan.GEN.MBT' its basically saying, this looks like something, that may be something else, it may be safe but we're not sure, so we're going to give it a label, and quarantine.

GEN stands for 'generic' which means it could be anything.

Neil, KN3ILZ


On Wed, Jun 10, 2020 at 04:37 PM, Jim N6VH wrote:

Trojan.GEN.MBT


locked Re: Decodes window not always populating

WB8ASI Herb
 

You can toggle it off and on using F9.  I'm using Delete Old Files and filtering out Worked B4.  73 Herb WB8ASI


locked Re: download ver 2.16.6

Andrew; KF6LU
 

Thanks Mike; As usual you have been a great resource of help.  I'll be reviewing that Microsoft link and setting up defender for the future both for JTalert and Log4Om. You were the one who helped me initially install Log40m after getting my rig to run WSJTx and JTalert.
Interesting development; Couldn't get ver 2.16.7 to run. I assumed it was the antivirus.  Previously I have used MS Edge to download programs.  Today I used Firefox and the program installed smooth as a baby's bottom.  Made contacts and all running well.  Another learning experience;  not only is antivirus a problem but the darn browser can also be the cause.


locked Re: JTAlert stops reporting decodes and logging to HRD sporadically #HRD

roamer
 



Get Outlook for Android gggggbgggghhz,xsestt3zeeees


From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of Michael, DJ2VA via groups.io <dj2va@...>
Sent: Sunday, June 7, 2020 4:22:39 AM
To: Support@HamApps.groups.io <Support@HamApps.groups.io>
Subject: [HamApps] JTAlert stops reporting decodes and logging to HRD sporadically #HRD
 
I was using several previous versions of JTAlert, WSJT-X and Hamradio Deluxe. Reporting Alerts and logging to HRD 6.7.0.xxx worked fine until I upgraded to JTAlert 2.16.6 and WSJT-X 2.2.0 RC3.
Now happens again and again, that JTAlert stops reporting decodes after a random period of time (several minutes). At the same time QSOs are no longer logged to HRD. Leaving everything on its own it takes again several minutes and suddenyl reporting starts again, also logging to HRD works again.

I could also force JTAlert to start reporting / logging, by closing and restarting JTAlert.
Does anybody else recognize that? Any ideas how to solve that problem?

73,
Michael


locked Re: JTAlert 2.16.7 not logging Country field in HRD #HRD

HamApps Support (VK3AMA)
 

On 11/06/2020 1:57 am, David De Coons wrote:
Laurie, you can direct HRD related support issues from users to me if you like. I really appreciate your app and I want to contribute. 

73
Dave wo2x

Tnx Dave!

de Laurie VK3AMA


locked Re: JTAlert 2.16.7 not logging Country field in HRD #HRD

HamApps Support (VK3AMA)
 

On 11/06/2020 1:42 am, Roger M via groups.io wrote:
Regarding the issue of JTAlert not logging the country field to HRD:
After a system reboot, the problem has not occurred again.

Thanks for your help.

Roger
AC6BW

Thanks for the update Roger.

Since a PC restart corrected the problem, my guess is your running Windows 10, is that the case?
It has been my experience with Win10 that when unusual, unexpected or abnormal application behavior is experienced, often the fix is to perform a Windows restart, and this is not exclusive to JTAlert. I frequently see this on my development PC when using Visual Studio it starts to be erratic and an application restart doesn't correct the problems, but a PC restart does, and this is without any pending Windows updates.

de Laurie VK3AMA


locked Re: Decodes window not always populating

HamApps Support (VK3AMA)
 

On 11/06/2020 5:26 am, Joe Spear wrote:
I have the same problem with the window not populating on startup.  It was happening with 2.16.4 and is happening with 2.16.7.  Refresh doesn't help.  Need to close and re-open and then it populates, as John said.  It's as if the decodes file isn't being loaded before the window is shown.

Joe W4WT

Joe,

Referring to https://hamapps.groups.io/g/Support/message/30323 want are your answers to the two questions asked?

de Laurie VK3AMA


locked Re: Decodes window not always populating

HamApps Support (VK3AMA)
 

On 11/06/2020 2:50 am, John Holmes W9ILY wrote:
When I launch the decodes window, it does not always populate with incoming calls. I have to close it and reopen several times and then all is OK. On a similar item, in the decodes window, the Canadian provinces that were not confirmed are shown as blue, even though I have not checked the Canadian Provinces option. To stop the blue coloring I needed to choose any mode, any band, uncheck all and save. That removed the erroneous blue coloring.
John W9ILY

John,

A couple of questions..

  • What startup options do you have for the Decodes display?
       

  • Are you in the habit of applying a filter to the Decodes display?
de Laurie VK3AMA


locked Re: Midway?

HamApps Support (VK3AMA)
 

On 11/06/2020 6:27 am, Jim N6VH wrote:

Yes, you are right. He is using the /4 to indicate the call area. However, that is interpreted by some logging programs as /AH4, which is Midway. Log4OM v2 (my main logging program) considers AH6P/4 as Midway. Log4Om v1 lists it as Hawaii. N1MM+ shows Midway. DXKeeper, as Laurie already mentioned, doesn't list a country, and asks for a country code to be entered. ACLog lists it as Hawaii.  Swisslog shows Midway. If I enter AH6P/W4, all logs correctly show United States. That would probably be the better call for him to use.

73,

Jim N6VH


Jim, good report, thanks for the tests.

It could be worse, the Station in question could be running portable in Zone 5 and signing "/P5".

de Laurie VK3AMA


locked Re: JT Alert Crashing when alert sound played

HamApps Support (VK3AMA)
 

On 11/06/2020 1:17 am, Bill Hicks wrote:
does this make any sense to anyone regarding JT Alert crashing when playing any audio alert?

Faulting application name: JTAlert.exe, version: 2.16.7.0, time stamp: 0x5edebe03

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x054783e8

Faulting process id: 0x4bd0

Faulting application start time: 0x01d63f38dd3521dc

Faulting application path: C:\Program Files (x86)\HamApps\JTAlert 2\JTAlert2\JTAlert.exe

Faulting module path: unknown

Report Id: ecfb0e91-5428-475d-8ae5-0ebdfce12d70

Faulting package full name:

Faulting package-relative application ID:


No it doesn't make any sense.

The JTAlert.exe executable itself does not play any audio, instead it offloads that task to a background process, the JTAlertV2.Manager.exe. That operation involves sending a UDP message to the Manager. My guess is that your PC protection software is directly interfering with JTAlert.exe as soon as it issues this UDP instruction.

de Laurie VK3AMA


locked Re: JT Alert new install

wazzan1@...
 

Thanks Neil and John that was the problem. I have been installing a heap of programs in my new shack computer and I must admit its a bit overwhelming (computer challenged). Its great to have so many helpful people in these groups
thanks again Wayne VK4WTN


locked Re: Lost AUDIO CODEXS

HamApps Support (VK3AMA)
 

On 10/06/2020 11:40 pm, John Scheuer wrote:
FYI. My problem was solved by re-downloading the Virtual Comport Driver from Silicone Labs, cp210x_Universal Windows Driver. I read that another had had this problem after MS did an update. I have had a number of things go south on me after an MS update so I it's not hard to believe.

John  NA6Y

Tnx for the update John, good to hear. It is always encouraging to get feedback that a bad user experience was not caused by JTAlert ;-).

de Laurie VK3AMA


locked Re: JT Alert Crashing when alert sound played

HamApps Support (VK3AMA)
 

On 11/06/2020 6:49 am, wsrmd@... wrote:
No the only bug I have is occasionally the first and maybe the second decodes in WSJT doe not populate in the JTAlert window, and then on the next round it might work well.  Sporadic

Bill  WA4WR

Update your JTAlert version.
Your HamSpots spot feed shows your spotting WSJT-X 2.2.1 decodes via JTAlert 2.16.6.
JTAlert 2.16.7 had a WSJT-X 2.2.x specific fix for lost decodes. From the release notes...
  Fixes:

    - WSJT-X 2.2.x FT8: Random loss of some early first-pass FT8 decodes received
       at the 11 second point of the Rx period.

de Laurie VK3AMA

6761 - 6780 of 36903