Date   

locked Re: Default bug ?

Paul F6EXV
 

Hi Ron
It is still a bug, IMHO.
The JTAlert setting is about LoTW QSL sent, but it modifies the LoTW QSL received field in Log4OM.
It should not affect that.
73
Paul F6EXV

Le 26/05/2021 à 14:19, Ron W3RJW via groups.io a écrit :
Uncheck "Mark ... requested"
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.4.0, JTAlert 2.50.1 beta, HRD Deluxe v6.7.0.357
FTdx-3000, SignaLink USB


Garanti sans virus. www.avast.com


locked Re: Default bug ?

Ron W3RJW
 

Uncheck "Mark ... requested"
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.4.0, JTAlert 2.50.1 beta, HRD Deluxe v6.7.0.357
FTdx-3000, SignaLink USB


locked Re: Default bug ?

Paul F6EXV
 

Attachment here, sorry

Le 26/05/2021 à 04:46, Paul F6EXV a écrit :
Hello all
Using JTAlert v2.50.1 and Log4OM version 2.13.0.0
I have configured L4OM default LoTW snet to "requested", and LoTW received to "no".
I have configured JTAlert logging as shown on the attachment.
BUT when I log a QSO, the LoTW received in L4OM shows as requested, while it should show No... unless I missed something !

73
Paul F6EXV
--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


locked Default bug ?

Paul F6EXV
 

Hello all
Using JTAlert v2.50.1 and Log4OM version 2.13.0.0
I have configured L4OM default LoTW snet to "requested", and LoTW received to "no".
I have configured JTAlert logging as shown on the attachment.
BUT when I log a QSO, the LoTW received in L4OM shows as requested, while it should show No... unless I missed something !

73
Paul F6EXV

--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


locked V2.50.1 Logging Start time is the End time of last QSO

Ed Stallman
 

Doing a search for (logging start time End Time) I get 2014 2015 results . I'm using WSJT-X , Jtalerts V2.50.1 and AClog ... When I click on a call I'd like to work in JTalerts and after sending RR73 the logging window pops up but the start time is the End time of last QSO logged ! This can very from 1 minute to Hours . I've found what I have to do to set the Start time is double click the call in WSJT-X . I know I've missed a setting somewhere ?  The 2 J-pegs below, The left is clicking JTAlerts and right is clicking WSJT . Please not the Start time ..Thanks Ed N5DG
  


locked Re: ACL and JT alert

Dave Garber
 

make sure the api is on , in aclog


Dave Garber
VE3WEJ / VE3IE


On Tue, May 25, 2021 at 12:02 AM GMuller885 via groups.io <GMuller885=aol.com@groups.io> wrote:
I upgraded tp Armature Contact log 7.0 and JT alert 5.0 and now . Now ACL will not log the contacts to ACL from WSJT-X.  Please provide a step by step process to make this happen. I am not very computer literate. this used to work with the old version.
 


locked Re: Alerts window does'nt start.

HamApps Support (VK3AMA)
 

On 25/05/2021 10:59 am, jeff29754 M1BCM wrote:
Hi Laurie, what I call the "alerts window" is wthe window that shows all the calls which I can click on etc. I upgraded from 2.5.0. which was working fine up until the the.net and 2.5.1. installations.

Thanks for replying.

de Jeff M1BCM
Jeff,

There was no requirement for a .NET install with 2.50.1, the .NET install required for the 2.50.0 install is all that was needed. What prompted you to install a new NET 5 runtime?

Are you able to open the JTAlert Help->About window?

Are you able to open any of the new 2.50.x windows? See the "Yellow star" entries under the View menu of the main JTAlert window.
   

If none of these windows will open, that suggests a problem with the JTAlertV2.Manager process, likely it is not running or is continually stopping and starting. What does TaskManager show for this process?

The Manager process is dependent on the .NET 5 runtime. When you installed/upgraded the runtime for your 2.50.1 install did your install the correct architecture version matching that of JTAlert? The runtime needs to match JTAlert, either x86 or x64. If you're using Windows 64 bit, I suggests using the x64 version of the runtime and JTAlert. While the 32 bit (x86) runtime and JTAlert will work under 64bit Windows, IMO, it is best to keep it x64 across the board, Windows, NET runtime and JTAlert all being x64.

de Laurie VK3AMA




locked Re: Alerts window does'nt start.

jeff29754 M1BCM
 
Edited

Hi Laurie, what I call the "alerts window" is wthe window that shows all the calls which I can click on etc. I upgraded from 2.5.0. which was working fine up until the the.net and 2.5.1. installations.

Thanks for replying.

de Jeff M1BCM


locked Re: Alerts window does'nt start.

HamApps Support (VK3AMA)
 

On 25/05/2021 5:09 am, jeff29754 wrote:
Before installing the new JTAlert version, I first installed the new .net software. Both went with no problems but the Alerts window is a no-show and the QSO history window won't populate. I'm sure it's fixable in settings but I sure as hell can't find it hihi. Report sent.

Jeff M1BCM

There is no "Alerts" window in JTAlert 2.50.1

What version did you upgrade from, was it a pre 2.50.x version? If so, is it the missing Callsign display grid of the main JTAlert window that is your problem? If yes, see the 2.50.0 release notes.

de Laurie VK3AMA


locked Re: JTAlert freezes during start

HamApps Support (VK3AMA)
 

On 25/05/2021 12:03 am, Jim Denneny wrote:
Notice from NET here this AM that NET 5.0 has problem.  Recommends upgrade to 5.0.6.  That seems to be my fix

Do you have a link to the source of this .NET problem?

de Laurie VK3AMA



locked Alerts window does'nt start.

jeff29754 M1BCM
 

Hi guys, could'nt find a fix for this ...
Before installing the new JTAlert version, I first installed the new .net software. Both went with no problems but the Alerts window is a no-show and the QSO history window won't populate. I'm sure it's fixable in settings but I sure as hell can't find it hihi. Report sent.

Jeff M1BCM


locked Re: JTAlert 2.50.1 does not receive from WSJT-X - Callsigns, Activity and Band heat windows don't open

Jim Denneny
 

Known issue. I updated NET to later version.  It works

Jim K7EG


locked Re: JTAlert freezes during start

Jim Denneny
 

Laurie: Definitely not protection software.  Notice from NET here this AM that NET 5.0 has problem.  Recommends upgrade to 5.0.6.  That seems to be my fix..  It has been two days now.

73, Jim K7EG


locked Re: Always on top

Paul F6EXV
 

That was it, Michael, thanks !
73
Paul

Le 24/05/2021 à 11:48, Michael a écrit :

Hi Paul

You'll find it as shown on the picture.

73 de Michael 5p1kzx


JTA on Top
Den 24-05-2021 kl. 10:55 skrev Paul F6EXV:
Hi all
The answer is probably obvious, but I just could not find it...
The JTAlert windows is hidden when I bring another screen on top of it.
But the callsign windows is always on top. Can I change this ? Where please ?
73
Paul F6EXV



Garanti sans virus. www.avast.com


locked Re: Always on top

Michael
 

Hi Paul

You'll find it as shown on the picture.

73 de Michael 5p1kzx


JTA on Top
Den 24-05-2021 kl. 10:55 skrev Paul F6EXV:

Hi all
The answer is probably obvious, but I just could not find it...
The JTAlert windows is hidden when I bring another screen on top of it.
But the callsign windows is always on top. Can I change this ? Where please ?
73
Paul F6EXV


locked Always on top

Paul F6EXV
 

Hi all
The answer is probably obvious, but I just could not find it...
The JTAlert windows is hidden when I bring another screen on top of it.
But the callsign windows is always on top. Can I change this ? Where please ?
73
Paul F6EXV

--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


locked Re: JTAlert 2.50.1 does not receive from WSJT-X - Callsigns, Activity and Band heat windows don't open

Frode Igland
 

My apologies for a late reply and thanks for pointing me to the incorrect UDP setting. I have no recollection of checking it, nor changing the port number, but obviously I must have done so. The good thing is that it works just fine now. Thanks again.

73, Frode LA6VQ 


locked Re: UDP Error

KE7AZ
 

I only have two applications using the UDP port - WSJT-X and JTAlert.  I also tried the multicast set up and it didn't work. 

So I went back to find previous versions to see if I could get something to work.  Here is what I found...
WSJT-X Version     JTAlert version    Result
2.1.2                            2.12.9               OK
2.3.1                            2.15.0               OK
2.3.1                            2.16.17            UDP Error
2.3.1                            2.16.1              AutoIT Crash
2.3.1                            2.16.3              OK
2.3.1                            2.16.6              OK but crashes after settings change
2.3.1                            2.16.11             UDP Error

There was a Windows 10 update just before this appeared.  I tried backing out the update out but one of the updates did not give me the option to undo it.  I did not have a system restore that I could use because of subsequent Windows 10  updates.I suspect that this problem is an unintended consequence of a Windows 10 update.  Entropy is winning!

73
Logan


locked Re: help window problem

Javi LU5FF
 

Laurie thank you very much
that was my problem
everything is ok
73s

Javi - LU5FF
-----------------------

El domingo, 23 de mayo de 2021 17:14:17 ART, Laurie, VK3AMA <hamapps.support@vkdxer.com> escribió:








On 23/05/2021 11:18 pm, Javi LU5FF via groups.io wrote:


  
  
  
HI all...

how to make my window look maximized?

view photo

tnx 

 

Javi - LU5FF


If you can't drag the edges of the Callsigns window to increase its size, make the window active, then press the F2 key which will open the Options, then untick the "Size locked" checkbox which will allow you to resize the window.

   

de Laurie VK3AMA


locked Re: help window problem

Laurie, VK3AMA
 



On 23/05/2021 11:18 pm, Javi LU5FF via groups.io wrote:
HI all...
how to make my window look maximized?
view photo
tnx 
 
Javi - LU5FF

If you can't drag the edges of the Callsigns window to increase its size, make the window active, then press the F2 key which will open the Options, then untick the "Size locked" checkbox which will allow you to resize the window.

   

de Laurie VK3AMA

2361 - 2380 of 37312