Date   

locked Re: JTAlert not highlighting text in Band Activity window

Jim Cooper
 

On 14 Aug 2021 at 3:09, Steve Phillips - NS4P wrote:


I did change the fonts for WSJT-X.  I am using Arial Regular 10 as
the "Font" and Courier New Regular 10 as the "Decoded Text Font"
Have you tried CONSOLAS font ? it is nice and clean
and shows the Ø with the slant zero

w2jc


locked Information or Problem with messaging window

André C
 

Hello group,
                    If I open the messaging window, under the pull down menu of previously saved message, There is no previous messages saved.  I'm using version 2.50.4 with .net 5.0.9, but I remember that it was like this since some previous release.  Is there a missing log file somewhere ? or is this a normal behaviour ?

73 VE2WNF


locked Re: Worked B4

Don Melcher
 

You clearly don’t understand why I ask this.  I’m not sitting in front of a computer all day looking at call signs. I want a visual and audio alert and I thought that was the function. Since this was related I didn’t think it hurt to ask, but apparently you did. 
--
Don
W6CZ
DM07


locked Re: JTAlert not highlighting text in Band Activity window

Dave Garber
 

check your wsjt/jtdx settings and see if udp settings have a tick mark in the 3 boxes...

Dave Garber
VE3WEJ / VE3IE


On Sat, Aug 14, 2021 at 6:19 AM Steve Phillips - NS4P <sphillips3@...> wrote:
I built up a new PC and did a fresh install of WSJT-X and JTAlert.  I've got everything working except that JTAlert is not highlighting text (e.g. B4, New prefix) in the WSJT-X Band Activity window.  I am getting the alerts and colors in the Callsigns #1 window, but not in Band Activity.

I did change the fonts for WSJT-X.  I am using Arial Regular 10 as the "Font" and Courier New Regular 10 as the "Decoded Text Font"

Are there specific limitations on which fonts JTAlert will highlight, or have I missed another setting somewhere.

WSJT-X v2.4.0 and JTAlert 2.50.5

Thanks


locked JTAlert not highlighting text in Band Activity window

Steve Phillips - NS4P
 

I built up a new PC and did a fresh install of WSJT-X and JTAlert.  I've got everything working except that JTAlert is not highlighting text (e.g. B4, New prefix) in the WSJT-X Band Activity window.  I am getting the alerts and colors in the Callsigns #1 window, but not in Band Activity.

I did change the fonts for WSJT-X.  I am using Arial Regular 10 as the "Font" and Courier New Regular 10 as the "Decoded Text Font"

Are there specific limitations on which fonts JTAlert will highlight, or have I missed another setting somewhere.

WSJT-X v2.4.0 and JTAlert 2.50.5

Thanks


locked Re: Lost alert audio after updating to 2.50.5

Walt Flesher, W6SA
 

My sound card did not change.
The Sound - Test Sound Output menu did not work.
It is almost midnight here so I will reinstall tomorrow and see if there is any issue with the file you mentioned.
I am using McAfee Total Protection, supplied by my ISP which they update regularly.
I did not notice any alerts when I updated previously and will watch carefully when I update tomorrow.

Thanks

73 de Walt, W6SA


locked Re: Worked B4

Jim Cooper
 

I'm really not trying to be difficult, but just how
many POTA stations do you hear in a day?

Is it so many that you can't remember which ones
you just worked? or make a note on a small piece
of paper, "like we used to do in the old days"?

Laurie has done magic to add so many bells and
whistles to JTalert already, but some folks seem
to forget that EVERYTHING done by JTalert has
to be done in the last couple of SECONDS of each
FT8 cycle (even less with FT4). I think we should
all give a second and third thought to stuff we think
'would be nice to have' and consider if it is more
important that the REAL stuff that JTalert is good
at in the time it has to do the magic.

w2jc

On 13 Aug 2021 at 19:06, Don Melcher wrote:

Sorry to want to be so specific but...

That would work if I was to enter call signs.

I have an alert for decoding the word POTA. I can be working around
the shop with the system on a band waiting for a POTA Alert. When
it´s a new UTC day it counts as a new contact. So if I work a
station at 23:30, it is "eligible" to work again at 00:00 and
it´s likely propagation will still be good. So I´m looking to
clear the B4 for ANY station calling CQ POTA at 00:00 UTC every day.

On Aug 13, 2021, at 6:03 PM, Jim Cooper <jim.w2jc@gmail.com>
wrote:

On 13 Aug 2021 at 15:51, Don Melcher wrote:

I just want it to reset at 00 UTC.
ITMm looking for any POTA stations and
want to work them again if the
activation spans more then one day.
very simple ... with the callsign in the callsign
window at left side of the main JTalert window,
RIGHT click on it to get the menu,
then select "Add to Temporary Ignored Callsign List"

it will be ignored until you start up JTalert next time.

w2jc



locked Re: A curiosity at least

JTAlert Support (VK3AMA)
 

On 14/08/2021 11:25 am, heath calhoun - kb5vai wrote:
yea and screw u



This account has now been permanently banned. This message thread has also been locked to avoid others feeding this troll.

Ladies & Gentlemen, this is how you get added to my personal JTAlert Ignored List. Welcome to the club KB5VAI.

de Laurie VK3AMA


locked Re: A curiosity at least

heath calhoun - kb5vai <hcalhoun@...>
 

yea and screw u





-------- Original message --------
From: "Laurie, VK3AMA" <hamapps.support@...>
Date: 8/13/21 16:40 (GMT-06:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] A curiosity at least



On 14/08/2021 6:31 am, Jim Cooper wrote:
> Also noted that you have not mentioned any
> particular bug, or "one bug after another" ...
> are you just trolling ?

Trolling is my guess.
Poster is infamous for his recent two word "Up Yours" post on the WSJTX
group that got him banned. https://wsjtx.groups.io/g/main/message/27844
<https://wsjtx.groups.io/g/main/message/27844>

de Laurie VK3AMA







locked Re: Multiple instance of JTALERT #FT8

JTAlert Support (VK3AMA)
 

On 14/08/2021 11:16 am, Frank wrote:
Hopefully someone can assist me with this issue. I have one computer with myself and my XYL operating WSTJX. We have separate programs set up for WSJTX which creates an ADI file for each of us. This all seems to work fine. The problem is I am unable to set JTALERT up to function separately on each of our sessions. I reviewed a post back on 04/11/2017 and followed the directions, I believe accurately.  The JTALERT works fine on my account, as it always has, but when my XYL runs it in her WSJTX session it appears to bring up my log and if she makes a contact it gets added to my B4 lists.  I did set up a separate short cut for JTALERT as instructed in the 04/11/2017 post.  I just can't get my XTL's JTALERT to bring up her own clean log.
We are running windows 10, WSJTx ver 2.4.0 and JTALERT ver 2.50.4  I would certainly appreciate any guidance that could be provided on this issue.

Sorry, without a link to the post in question it is not practical to try and determine to what message you were referring, especially a message that is getting close to 4 years old.

Regardless, setting up JTAlert for multiple Station Callsigns is easy. You need to set the /callsign=XYL_CALL command-line parameter in the shortcut used to start your XYL JTAlert instance. The easiest way is to let JTAlert do that for you. Open the Settings window and navigate to the "Station Callsign" section (towards the bottom) and create your XYL shortcut from there.

Starting JTAlert with your new XYL shortcut will automatically create a new default JTAlert config that will need to have its settings adjusted, log type, wanted ALert setup, sounds, etc.

de Laurie VK3AMA


locked Re: JTAlert 2.50.0 Not Working

Joe Subich, W4TV
 

Have you installed the *CORRECT VERSION* of NET 5.0.8?

You must install the *DESKTOP* version and match 64 or 32 bit
to the version of JTAlert you have installed.

THIS IS ALL IN THE DOCUMENTATION.

73,

... Joe, W4TV

On 2021-08-13 9:32 PM, Harry Hall via groups.io wrote:
Outstanding done logging back on track.  A friend ham down the road has an old win7 computer of mine he says he uploaded to 2.50.0 with no problems I am going to hold off trying it again because nothing works on jtalert after install, no sound, no logging, no way to open any of the windows to show the call signs decoding.  You just get one box full of ????? near the top on 2.50.0.
Hers what we are using JTAlert 2.16.17 K5HLH {17M, ft8,hrd6+,Filter, #1} (Updates)
WSJT-X v2.40 by K1JT, G4WJS, K9AN, and IV3NWV
Device name      HarryHall-PC
Processor            AMD Phenom(tm) II X4 945 Processor   3.00 GHz
Installed RAM    8.00 GB
Device ID             C2DB017D-2A54-403B-B1A4-84D693AD8A5B
Product ID          00330-50000-00000-AAOEM
System type        64-bit operating system, x64-based processor
Pen and touch   No pen or touch input is available for this display
Edition  Windows 10 Pro
Version 20H2
Installed on        ‎6/‎19/‎2020
OS build               19042.1165
Experience          Windows Feature Experience Pack 120.2212.3530.0
Thanks for your time I am good on QRZ K5HLH 73’s
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
*From: *HamApps Support (VK3AMA) <mailto:vk3ama.ham.apps@gmail.com>
*Sent: *Friday, August 13, 2021 4:20 PM
*To: *Support@HamApps.groups.io <mailto:Support@HamApps.groups.io>
*Subject: *Re: [HamApps] JTAlert 2.50.0 Not Working
On 14/08/2021 8:08 am wrote:
Up graded from 2.16.17 to 2.50.0 nothing worked.  Reloaded back down
to 2.16.17 took several days to start working again now it doubles
the log entry back to HRD.
Device name HarryHall-PC
Processor AMD Phenom(tm) II X4 945 Processor   3.00 GHz
Installed RAM 8.00 GB
Device ID C2DB017D-2A54-403B-B1A4-84D693AD8A5B
Product ID 00330-50000-00000-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Edition Windows 10 Pro
Version 20H2
Installed on ‎6/‎19/‎2020
OS build 19042.1165
Experience Windows Feature Experience Pack 120.2212.3530.0
OM,
"Nothing Works" is a very broad statement. You will need to be more specific about what is not working.
As for Double-logging in HRD, that will be due to HRD listening for logging events from WSJT-X and also the logging instruction sent by JTAlert. You will need to turn off the "Enable logged contact ADIF broadcast" setting in WSJTX, under the "Secondary UDP Server (depreciated)" area of Reporting Tab of its Settings.
If that was not enabled, the extra logging will be coming via the JTAlert "UDP Resend" option being enabled, you need to turn that off under the "Applications -> WSJT-X/JTDX" section of the JTAlert Settings window.
de Laurie VK3AMA


locked Multiple instance of JTALERT #FT8

Frank
 

Hopefully someone can assist me with this issue. I have one computer with myself and my XYL operating WSTJX. We have separate programs set up for WSJTX which creates an ADI file for each of us. This all seems to work fine. The problem is I am unable to set JTALERT up to function separately on each of our sessions. I reviewed a post back on 04/11/2017 and followed the directions, I believe accurately.  The JTALERT works fine on my account, as it always has, but when my XYL runs it in her WSJTX session it appears to bring up my log and if she makes a contact it gets added to my B4 lists.  I did set up a separate short cut for JTALERT as instructed in the 04/11/2017 post.  I just can't get my XTL's JTALERT to bring up her own clean log.
We are running windows 10, WSJTx ver 2.4.0 and JTALERT ver 2.50.4  I would certainly appreciate any guidance that could be provided on this issue.  


locked Re: JTAlert 2.50.0 Not Working

Harry Hall
 

Outstanding done logging back on track.  A friend ham down the road has an old win7 computer of mine he says he uploaded to 2.50.0 with no problems I am going to hold off trying it again because nothing works on jtalert after install, no sound, no logging, no way to open any of the windows to show the call signs decoding.  You just get one box full of ????? near the top on 2.50.0.

 

Hers what we are using JTAlert 2.16.17 K5HLH {17M, ft8,hrd6+,Filter, #1} (Updates)

WSJT-X v2.40 by K1JT, G4WJS, K9AN, and IV3NWV

 

Device name      HarryHall-PC

Processor            AMD Phenom(tm) II X4 945 Processor   3.00 GHz

Installed RAM    8.00 GB

Device ID             C2DB017D-2A54-403B-B1A4-84D693AD8A5B

Product ID          00330-50000-00000-AAOEM

System type        64-bit operating system, x64-based processor

Pen and touch   No pen or touch input is available for this display

 

Edition  Windows 10 Pro

Version 20H2

Installed on        ‎6/‎19/‎2020

OS build               19042.1165

Experience          Windows Feature Experience Pack 120.2212.3530.0

 

Thanks for your time I am good on QRZ K5HLH 73’s

 

Sent from Mail for Windows

 

From: HamApps Support (VK3AMA)
Sent: Friday, August 13, 2021 4:20 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.50.0 Not Working

 

On 14/08/2021 8:08 am wrote:

Up graded from 2.16.17 to 2.50.0 nothing worked.  Reloaded back down to 2.16.17 took several days to start working again now it doubles the log entry back to HRD.

Device name HarryHall-PC

Processor AMD Phenom(tm) II X4 945 Processor   3.00 GHz

Installed RAM 8.00 GB

Device ID C2DB017D-2A54-403B-B1A4-84D693AD8A5B

Product ID 00330-50000-00000-AAOEM

System type 64-bit operating system, x64-based processor

Pen and touch No pen or touch input is available for this display

Edition Windows 10 Pro

Version 20H2

Installed on ‎6/‎19/‎2020

OS build 19042.1165

Experience Windows Feature Experience Pack 120.2212.3530.0


OM,

"Nothing Works" is a very broad statement. You will need to be more specific about what is not working.

As for Double-logging in HRD, that will be due to HRD listening for logging events from WSJT-X and also the logging instruction sent by JTAlert. You will need to turn off the "Enable logged contact ADIF broadcast" setting in WSJTX, under the "Secondary UDP Server (depreciated)" area of Reporting Tab of its Settings.
   
If that was not enabled, the extra logging will be coming via the JTAlert "UDP Resend" option being enabled, you need to turn that off under the "Applications -> WSJT-X/JTDX" section of the JTAlert Settings window.

de Laurie VK3AMA

 


locked Re: Worked B4

Jim Cooper
 

On 13 Aug 2021 at 15:51, Don Melcher wrote:

I just want it to reset at 00 UTC.
ITMm looking for any POTA stations and
want to work them again if the
activation spans more then one day.
very simple ... with the callsign in the callsign
window at left side of the main JTalert window,
RIGHT click on it to get the menu,
then select "Add to Temporary Ignored Callsign List"

it will be ignored until you start up JTalert next time.

w2jc


locked Re: Worked B4

Don Melcher
 

I just want it to reset at 00 UTC. I’m looking for any POTA stations and want to work them again if the activation spans more then one day. 
--
Don
W6CZ
DM07


locked Re: JTAlert 2.50.0 Not Working

JTAlert Support (VK3AMA)
 

On 14/08/2021 8:08 am wrote:
Up graded from 2.16.17 to 2.50.0 nothing worked.  Reloaded back down to 2.16.17 took several days to start working again now it doubles the log entry back to HRD.

Device name HarryHall-PC
Processor AMD Phenom(tm) II X4 945 Processor   3.00 GHz
Installed RAM 8.00 GB
Device ID C2DB017D-2A54-403B-B1A4-84D693AD8A5B
Product ID 00330-50000-00000-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Edition Windows 10 Pro
Version 20H2
Installed on ‎6/‎19/‎2020
OS build 19042.1165
Experience Windows Feature Experience Pack 120.2212.3530.0

OM,

"Nothing Works" is a very broad statement. You will need to be more specific about what is not working.

As for Double-logging in HRD, that will be due to HRD listening for logging events from WSJT-X and also the logging instruction sent by JTAlert. You will need to turn off the "Enable logged contact ADIF broadcast" setting in WSJTX, under the "Secondary UDP Server (depreciated)" area of Reporting Tab of its Settings.
   
If that was not enabled, the extra logging will be coming via the JTAlert "UDP Resend" option being enabled, you need to turn that off under the "Applications -> WSJT-X/JTDX" section of the JTAlert Settings window.

de Laurie VK3AMA



locked JTAlert 2.50.0 Not Working

Harry Hall
 

Up graded from 2.16.17 to 2.50.0 nothing worked.  Reloaded back down to 2.16.17 took several days to start working again now it doubles the log entry back to HRD.

Device name HarryHall-PC
Processor AMD Phenom(tm) II X4 945 Processor   3.00 GHz
Installed RAM 8.00 GB
Device ID C2DB017D-2A54-403B-B1A4-84D693AD8A5B
Product ID 00330-50000-00000-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Edition Windows 10 Pro
Version 20H2
Installed on ‎6/‎19/‎2020
OS build 19042.1165
Experience Windows Feature Experience Pack 120.2212.3530.0
 
 


locked Re: Lost alert audio after updating to 2.50.5

JTAlert Support (VK3AMA)
 

On 13/08/2021 4:27 pm, Walt Flesher, W6SA wrote:

I reinstalled 2.50.4 and audio returned.

Did I overlook something?

--
73 de W6SA

No, nothing to overlook because nothing has changed with respect to audio in this new release.

Does the "Sound -> Test Sound Output" menu work?

The audio management didn't change with 2.50.5, it is identical to 2.50.4. What has changed is that the Manager executable that handles all audio was updated. My guess is that your PC Protection software is interfering with this new build of JTAlertV2.Manager.exe


de Laurie VK3AMA


locked Re: A curiosity at least

Laurie, VK3AMA
 

On 14/08/2021 6:31 am, Jim Cooper wrote:
Also noted that you have not mentioned any
particular bug, or "one bug after another" ...
are you just trolling ?
Trolling is my guess.
Poster is infamous for his recent two word "Up Yours" post on the WSJTX group that got him banned. https://wsjtx.groups.io/g/main/message/27844 <https://wsjtx.groups.io/g/main/message/27844>

de Laurie VK3AMA


locked Re: A curiosity at least

JTAlert Support (VK3AMA)
 

On 14/08/2021 5:50 am, Dana Smith wrote:
So, I am running WSJTX 2.3.1, JT Alert 2.16.17 and Log4OM V2 2.16.0 and using Omnirig with an IC7410 on a Windows 10 computer. When I push Log QSO in WSJTX it used to automatically log into Log4OM Version 1. Now it won’t log into
Log4OM Version 2. (which sees the rig just fine so it recognizes the CAT op) That logging database is in the cloud as the manual suggests and all programs are seeing it and saying pass/pass when the connection is checked.

I have been through the manuals and install procedures for everything and have yet to divine why the new Log4OM isn’t automatically logged by JT Alert as things used to be.

Is there a master magician on line today who might have a clue about what the #%&&$# is going on?

Any help appreciated.
Dana   K7QH

The JTAlert help file contains instructions (with pictures) on how to correctly setup JTAlert & Log4OMV2.

A tip on logging. If you don't click the "OK" button on the WSJT-X "Log QSO" window, JTAlert will never see the logging event and will not log to LOg4OM or any of the supported loggers.

de Laurie VK3AMA

3261 - 3280 of 39821