Date   

locked Re: MESSAGE #FT8

David Brittenham
 

You would be surprised how many people don't even know the messaging feature is there.  You would probably be more surprised to know how may people don't use JTAlert.   And, you might be even more surprised to know how many of those have no idea the program even exists.  I don't know how anyone can work with WSJT-X without JTAlert.  

73
David
WA0RVK


locked Re: Alert Database

Dave Garber
 

My log is saved on google drive (web)  and jtalert finds it.    Does your cloud log include any kind of path to the file

sent via LG hand held device

On Wed., Dec. 1, 2021, 8:52 p.m. Ken Alexander, <ve3hls@...> wrote:
Thanks Larry,

My understanding of how things work is pretty much as you described.  However, I use a logger (Cloudlog) that is web based and stores my logs in "the cloud".  There's nothing on my computer to sync with JT Alert.  I can download an ADIF from my logger and I think JT Alert can read it but I'm not sure and am a little scared of making a mess of things.

I update my alert list manually every week or so; I don't work that much new stuff. I also keep countries and states on the alert list until they are QSLed.  I don't know if JT Alert lets me do that.

73 and thanks again,

Ken Alexander
VE3HLS

On Wed, Dec 1, 2021, 18:28 Dev Null <aptget@...> wrote:
Like you (I think) I get stuck in terminology. I am a very literal person. Laurie takes great care to be precise, but in this environment of three or more apps trying to work together, some terms get duplicated.

As I understand it, the "alert database" in this case is the database within JTAlert that keeps track of what you want to be alerted for.

When we "rebuild the alert database" (by the way, terminology for this action was recently changed to better describe it) we are scanning the database of the logging app, to see what we have confirmed or not "as of right now."

This should be done after any new contacts have been confirmed in the log, such as after updating the log from LOTW. Then for example, JTAlert will see that we no longer need a country or prefix or whatever you are looking for, and no longer bother you with alerts for stuff that you have confirmed.

Hope this helps.

Larry N8KU


locked Re: Alert Database

Ken Alexander <ve3hls@...>
 

Thanks Larry,

My understanding of how things work is pretty much as you described.  However, I use a logger (Cloudlog) that is web based and stores my logs in "the cloud".  There's nothing on my computer to sync with JT Alert.  I can download an ADIF from my logger and I think JT Alert can read it but I'm not sure and am a little scared of making a mess of things.

I update my alert list manually every week or so; I don't work that much new stuff. I also keep countries and states on the alert list until they are QSLed.  I don't know if JT Alert lets me do that.

73 and thanks again,

Ken Alexander
VE3HLS


On Wed, Dec 1, 2021, 18:28 Dev Null <aptget@...> wrote:
Like you (I think) I get stuck in terminology. I am a very literal person. Laurie takes great care to be precise, but in this environment of three or more apps trying to work together, some terms get duplicated.

As I understand it, the "alert database" in this case is the database within JTAlert that keeps track of what you want to be alerted for.

When we "rebuild the alert database" (by the way, terminology for this action was recently changed to better describe it) we are scanning the database of the logging app, to see what we have confirmed or not "as of right now."

This should be done after any new contacts have been confirmed in the log, such as after updating the log from LOTW. Then for example, JTAlert will see that we no longer need a country or prefix or whatever you are looking for, and no longer bother you with alerts for stuff that you have confirmed.

Hope this helps.

Larry N8KU


locked Re: Flashing Callsign

Ron W3RJW
 

Read the 2.50.8 release notes.

or

See the Help file "Tutorials -> ATNO Visual Alert" topic for
       setup and usage instructions.

--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, wsjtx-2.5.2-win64_improved_widescreen+MAP65-3.0.0.exe, JTAlert 2.50.9, HRD Deluxe v6.7.0.391
FTdx-3000, SignaLink USB


locked Re: Flashing Callsign

Inbody, Don
 

ATNO?


On Wed, Dec 1, 2021, 13:36 John Kludt K7SYS <johnnykludt@...> wrote:
I am sure it is in the documentation but I cannot find it.  In 2.50.9 what does it mean when a callsign flashes in the Callsigns area?

John K7SYS


--
73, Don AD0K
EM10bc
Buda, TX


locked Flashing Callsign

John Kludt K7SYS
 

I am sure it is in the documentation but I cannot find it.  In 2.50.9 what does it mean when a callsign flashes in the Callsigns area?

John K7SYS


locked #Announcement #NewRelease : JTAlert 2.50.9 is available #Announcement #NewRelease

JTAlert Support (VK3AMA)
 

The latest JTAlert version 2.50.9 is now available at https://hamapps.com/JTAlert/

Note: The installer is now distributed as a single multi-architecture x64 & x86 (64bit & 32bit) executable file. After installation when JTAlert is run it will automatically use the correct 64bit or 32bit files required by your Windows OS installation. It is important that the correct NET 5 Desktop Runtime is installed, 64bit or 32bit, matching the architecture of your Windows OS. If you're running 64bit Windows you need the 64bit (x64) version of the NET 5 Desktop Runtime, NOT the 32bit version.

The new installer has been examined by Microsoft and flagged as Virus/Trojan free. The MS Defender definitions files have been updated to exclude JTAlert 2.50.8 as a possible threat.

Full release notes are available at the end of this message. I strongly encourage all users to read these before installing this new JTAlert release.

de Laurie VK3AMA

Release Notes:

2.50.9 (01-12-2021)

  *** Includes Callsign database file version 2021-12-01 (2021-Dec-01)

  Changes:

    - Ignored Callsigns: When disabled, all callsigns in the ignored list are now
       treated as non-ignored and can produce other alert types if triggered.
       Previously when disabled only the ignored coloring of the callsign was
       removed and the callsigns would not generate other alert types.

  Fixes:

    - VE Province Alert: LoTW confirmed provinces not found when running the
       "Rebuild Alert Database" operation against a DXLab DXKeeper log.

    - Blocked HamSpots Spotting: The help file topic for blocked spotting not being
       displayed when the warning popup window was acknowleged.

    - Fatal Error: Random line 38993 errors. (2.50.8 defect)




locked Re: Alert Database

Larry Banks
 

Hi Ken,

As  you add new DXCC confirmations, rebuilding your dB will automate this so that you don't need to do it manually.  It also does it for all the various awards, not just DXCC.

Larry / W1DYJ


On 12/1/2021 5:18, Ken Alexander wrote:
I'm baffled by the need to "rebuild" an alert database.  Shortly after installing JT Alert I went to the settings menu and created lists of Wanted DXCCs for each band.  Isn't that my Alert Database?  What does rebuilding the alert database do that I haven't done already?

73 and Many thanks,

Ken Alexander
VE3HLS



locked Re: Error Message

Dave Garber
 

set jtalert to aclog, port 1100
but you also need to have api turned on in aclog, and set to 1100 ( default)

also verify that the logfile you are using in aclog matches what jtalert is pointing to....     

is the log entry going in, and just the error, or is not logging..


Dave Garber
VE3WEJ / VE3IE


On Tue, Nov 30, 2021 at 11:01 AM Arthur Petteway <wb4mnk@...> wrote:
ERROR
ACLog : Unable To Confirm QSO Logged

Please direct me to the instructions on how to automatically load the ACLog file and TCP port into the JTAlert settings.

73,
Art WB4MNK


locked Re: Alert Database

Dev Null
 

Like you (I think) I get stuck in terminology. I am a very literal person. Laurie takes great care to be precise, but in this environment of three or more apps trying to work together, some terms get duplicated.

As I understand it, the "alert database" in this case is the database within JTAlert that keeps track of what you want to be alerted for.

When we "rebuild the alert database" (by the way, terminology for this action was recently changed to better describe it) we are scanning the database of the logging app, to see what we have confirmed or not "as of right now."

This should be done after any new contacts have been confirmed in the log, such as after updating the log from LOTW. Then for example, JTAlert will see that we no longer need a country or prefix or whatever you are looking for, and no longer bother you with alerts for stuff that you have confirmed.

Hope this helps.

Larry N8KU


locked Alert Database

Ken Alexander <ve3hls@...>
 

I'm baffled by the need to "rebuild" an alert database.  Shortly after installing JT Alert I went to the settings menu and created lists of Wanted DXCCs for each band.  Isn't that my Alert Database?  What does rebuilding the alert database do that I haven't done already?

73 and Many thanks,

Ken Alexander
VE3HLS


locked Re: Worked B4 stations not being highlighted on WSJTX.

Michael Black
 

FYI..we changed his multicast addr to 224.0.0.1 and turned on Multicast on Loopback in JTAlert.

Mike W9MDB




On Tuesday, November 30, 2021, 06:15:41 PM CST, k5rcd <randyk5rcd@...> wrote:


Mike, W9MDB was gracious enough to help me get this all straightened out.
--
73,
RANDY
K5RCD
South Texas


locked Re: error message that randomly appears

John P
 
Edited

Laurie I posted the same problem in another thread this afternoon (Fatal error on WSJT false decode).

I can be a bit more specific about what happened I think. I was listening on 2 meter EME in JT65B mode. The instance of JTAlert was a 2nd instance; the 1st instance was monitoring another WSJT-X instance connected to my 6 meter radio.

When the error occurred, I also got a false decode on WSJT-X - "WA2FZW KK4MA ". I can't say which happened first, however. Did the false decode cause the JTAlert crash or did the crash cause the false decode? What I can say is that the "KK4MA" call sign was not in the call sign box on either WSJT-X or in the call sign area on the JTAlert window. Nor was the call "KK4MA" in any of the messages on WSJT-X.

The problem occurred twice over about a 5 minute period. Both times I got a false decode in WSJT-X (different call the first time it happened).

I'm running Windows-10 and the latest versions of both WSJT-X and JTAlert. I just installed JTAlert last night.

To answer your question in your earlier post, there was absolutely no detectable activity on 2 meter EME this afternoon when the problem occurred here.

EDIT: Ive never seen this in earlier versions of JTAlert.

--
John P.
WA2FZW


locked Re: error message that randomly appears

Steve Miller
 

Had a similar error tonight just after completing a ft8 40m f/h qso with sv2rsg/a in Mount Athos.
After acknowledging the error message JTA shut its self down. I'm using version 2.50.8 of JTA.

Steve, K8SJM


locked Re: Worked B4 stations not being highlighted on WSJTX.

k5rcd
 

Mike, W9MDB was gracious enough to help me get this all straightened out.
--
73,
RANDY
K5RCD
South Texas


locked Fatal error on WSJT False Decode

John P
 

I got the error shown in the attachment twice this afternoon while listening on 2 meter JT65B with WSJT-X. It coincided with a false decode "WA2FZW KK4MA <grid>"
--
John P.
WA2FZW


locked Error Message

Arthur Petteway
 

ERROR
ACLog : Unable To Confirm QSO Logged

Please direct me to the instructions on how to automatically load the ACLog file and TCP port into the JTAlert settings.

73,
Art WB4MNK


locked Re: WSJT-X & Win4ICOM #FT8

Jacques F1VEV
 

Hi Dave while no software guru, I run the same set up as you with  wsjtx is 2.5.2 and also JTAlert 2.50.8 I assume you check your OmniRig values are good in terms of com port as well as connected in Win4Icom settings /3rd party 
I do not load one software after the other, I let Win4Icom fire up wsjtx and JTAlert etc .  I start the Win4Icom suite and all other software opens up and decodes 
Cheers Jacques 
--
F1VEV


locked Re: Worked B4 stations not being highlighted on WSJTX.

k5rcd
 

Please ignore the screenshot about Amateur Contact Log, I don't know how that got in there.
--
73,
RANDY
K5RCD
South Texas


locked Worked B4 stations not being highlighted on WSJTX.

k5rcd
 

I had Worked B4 performing perfectly fine for a long time, but now for some reason, no matter what I try, it just won't highlight them. I've tried every setting I can think of, but no joy. My radios are both correctly configured, (Icom 756 PRO 3 and Icom 7300). I have tried setting up the HRD QSO Forwarding with UDP Send, and UDP Receive enabled, as both and each separately without success.

I am running the latest versions of JT Alert, Ham Radio Deluxe, and WSJTX.

I have contacted HRD support, but since this is third party software, they can't resolve the issue, although they have really tried to help.  I THINK it may be related to the "unknown band, unknown mode" message on the top of the JT Alert banner (see attached). I've attached screen shots of all the relevant info I can think of. If any other info is needed please let me know. 

I'm a 75 year old disabled Nam veteran, my brain is starting to get a bit fuzzy, and this issue has me completely frustrated. If anyone can help I will greatly appreciate it. It would be most helpful if maybe a screenshot or two illustrating the correct settings or changes necessary as I am not at all computer literate.

Please help if you can, If I don't get this fixed pretty soon, they will be coming to take me away!
--
73,
RANDY
K5RCD
South Texas

2141 - 2160 of 39839