Date   

locked Re: JTAlertX 2.13.7 throws an alert that QSO Not Logged on every entry

KT7AZ
 

Laurie,
I was close, I was choosing the regular ACLog and not the FieldDay log in LOG File path.  Works great now.

thank you very much.

de Gary KT7AZ


locked Re: Autolt Error

HamApps Support (VK3AMA)
 

On 17/06/2019 10:19 pm, RICHARD BRESSLER via Groups.Io wrote:
I am experiencing the same error when I use slicemaster to open jt alert.   

Rick
Rick,

If your only using SliceMaster while running JTAlert, than try having JTAlert auto-start SliceMaster. No guarantees, but may be worth a try.

de Laurie VK3AMA


locked Re: JTAlertX 2.13.7 throws an alert that QSO Not Logged on every entry

HamApps Support (VK3AMA)
 

On 19/06/2019 4:56 am, KT7AZ wrote:
I have the interface working with JTalert 2.13.7 to log into N3FJP's Field Day log.  the transfer goes through to N3FJP Field Day Log but I get a popup from JTAlert on every log entry saying QSO Not Logged.

I also must enter my exchange on every log entry, is there a place where that can be automatically populated?

thanks,

KT7AZ
OM,

If JTAlert is warning after every logged QSO that it was unable to Confirm the QSO than very likely JTAlert is examining the wrong N3FJP log file.
I expect you have not correctly setup JTAlert to work with the FD log and that JTAlert is examining your ACLog log file instead.
If your having to enter the exchange each time, suggests that you may not have WSJT-X in FD Contest mode. WSJT-X will automatically populate the Sent/Rcvd exchanges in its Log QSO window and they are received by JTAlert. Note, JTAlert automatically logs the exchanges for the N3FJP Contest Loggers only, not ACLog.

See the JTAlert Help File, "Tutorials -> N3FJP Contest Logs Logging? topic. It explains the correct setup (it is not difficult).

de Laurie VK3AMA


locked Re: Accurate call signs showing in JTA fields.

HamApps Support (VK3AMA)
 

On 19/06/2019 4:11 am, N7BTH@... wrote:
I am a new user of JTALERTX.  I have it working more or less as I want it to however as I watch the receive window in WSJT-X decode CQ messages I note that the JTALERTX window does not show all the same stations.  In other words some of the Green CQ messages in the WSJT-X window show up in the JTALERTX fields and some do not.  I am guessing I have some setting wrong but have been unsuccessful in finding out why this is happening.  
 
Any pointers?
OM (please sign your messages),

If JTAlert is showing less Callsigns per period that WSJT-X, than likely you have one or more Alert filters active.
Does you JTAlert titlebar indicate active Filtering (note the "F")?

   

de Laurie VK3AMA


locked Re: Wild cards for call alert

HamApps Support (VK3AMA)
 

On 19/06/2019 1:25 am, Tony Dixon G4CJC wrote:
I've looked but can't find any info in the help file on wild cards for call sign alerts. The help file has a lot under construction.
73 Tony G4CJC
Tony,

When was your last visit to the Optometrist? ;-)

The Wanted Callsign Alert in the Settings clearly says to visit the Help file for wildcard instructions.

   

And from the Help file...

   

de Laurie VK3AMA


locked JTAlertX 2.13.7 throws an alert that QSO Not Logged on every entry

KT7AZ
 

I have the interface working with JTalert 2.13.7 to log into N3FJP's Field Day log.  the transfer goes through to N3FJP Field Day Log but I get a popup from JTAlert on every log entry saying QSO Not Logged.

I also must enter my exchange on every log entry, is there a place where that can be automatically populated?

thanks,

KT7AZ


locked Accurate call signs showing in JTA fields.

WALTDEWS@...
 

I am a new user of JTALERTX.  I have it working more or less as I want it to however as I watch the receive window in WSJT-X decode CQ messages I note that the JTALERTX window does not show all the same stations.  In other words some of the Green CQ messages in the WSJT-X window show up in the JTALERTX fields and some do not.  I am guessing I have some setting wrong but have been unsuccessful in finding out why this is happening.  
 
Any pointers?


locked Wild cards for call alert

Tony Dixon G4CJC
 

I've looked but can't find any info in the help file on wild cards for call sign alerts. The help file has a lot under construction.
73 Tony G4CJC


locked Re: #HRD #HRD

chris g7ogx
 

Yes it is "🤔" but needs donations, as the site reminds you!


From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of Michel <micheluze@...>
Sent: Tuesday, June 18, 2019 10:02:02 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] #HRD
 
Hi all,

Stop paying for software that is more concerned with cash flow than updates for subscribers. 
There are free programs that do the same, if not better, for my part I use Log4OM which is no problem, there is everything yours does, the only difference is that it is free, updates are done when needed.

73 michel

De : Support@HamApps.groups.io <Support@HamApps.groups.io> de la part de HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
Envoyé : lundi 17 juin 2019 21:38
À : Support@HamApps.groups.io
Objet : Re: [HamApps] #HRD
 
On 18/06/2019 5:00 am, joaquin@... wrote:
Hello problem only with the FT4 mode in hdrlog, registration error, but if you register it as MFSK, emn previous version if you registered without error in FT4 What?
OM,

I can't fault FT4 uploads to HRDLog.net, they are working here.

From my tests, HRDLog does not accept the ADIF SUBMODE which needs to be set to "FT4" if you upload the QSO as MODE = "MFSK", HRDLog just ignores the SUBMODE.

How are you uploading to HRDLog.net, is it via JTAlert or are you uploading an ADIF file manually?
JTAlert only uploads to HRDLog.net as MODE=FT4

If you upload as MFSK, when you check the QSO on HRDLog you will note there is no field for SUBMODE only MODE. The MODE field is a dropdown with FT4 as one of the options.
   

   

From what I can see, HRDLog only accepts FT4 QSOs when logged with MODE = FT4.

de Laurie VK3AMA


locked Re: #HRD #HRD

Michel
 

Hi all,

Stop paying for software that is more concerned with cash flow than updates for subscribers. 
There are free programs that do the same, if not better, for my part I use Log4OM which is no problem, there is everything yours does, the only difference is that it is free, updates are done when needed.

73 michel

De : Support@HamApps.groups.io <Support@HamApps.groups.io> de la part de HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
Envoyé : lundi 17 juin 2019 21:38
À : Support@HamApps.groups.io
Objet : Re: [HamApps] #HRD
 
On 18/06/2019 5:00 am, joaquin@... wrote:
Hello problem only with the FT4 mode in hdrlog, registration error, but if you register it as MFSK, emn previous version if you registered without error in FT4 What?
OM,

I can't fault FT4 uploads to HRDLog.net, they are working here.

From my tests, HRDLog does not accept the ADIF SUBMODE which needs to be set to "FT4" if you upload the QSO as MODE = "MFSK", HRDLog just ignores the SUBMODE.

How are you uploading to HRDLog.net, is it via JTAlert or are you uploading an ADIF file manually?
JTAlert only uploads to HRDLog.net as MODE=FT4

If you upload as MFSK, when you check the QSO on HRDLog you will note there is no field for SUBMODE only MODE. The MODE field is a dropdown with FT4 as one of the options.
   

   

From what I can see, HRDLog only accepts FT4 QSOs when logged with MODE = FT4.

de Laurie VK3AMA


locked Windows 10 May 2019 Update - Confirmed broken JTAlert behaviour

HamApps Support (VK3AMA)
 

I can now confirm the broken JTAlert behaviour (minimize and close buttons disabled) under the 1903 update of Windows 10.

At this time, it is unknown if a fix will be possible. This update has broken something within the quite complex (and convoluted) code needed to display the menus and Band-Activity in the titlebar.

It is still possible to close JTAlert, there are several methods available...
  •     Use either the Alerts or Settings title-bar menus, the bottom most menu item "Exit JTAlert"
  •     Right click the Windows taskbar entry for JTAlert and click the "Close Window" menu item.
  •     Left click the JTAlert icon in the titlebar (on the far left) and click the "Close" menu entry.
  •     Make JTAlert the active window and issue the standard Windows hotkey for closing window, Alt+F4

If you don't want to use one of these alternatives, the only solution is to install the "Alternate Layout" version  of JTAlert.

I have confirmed the "Alternate Layout" build is working with Win10 1903.

de Laurie VK3AMA


locked Re: #HRD #HRD

HamApps Support (VK3AMA)
 

On 18/06/2019 5:00 am, joaquin@... wrote:
Hello problem only with the FT4 mode in hdrlog, registration error, but if you register it as MFSK, emn previous version if you registered without error in FT4 What?
OM,

I can't fault FT4 uploads to HRDLog.net, they are working here.

From my tests, HRDLog does not accept the ADIF SUBMODE which needs to be set to "FT4" if you upload the QSO as MODE = "MFSK", HRDLog just ignores the SUBMODE.

How are you uploading to HRDLog.net, is it via JTAlert or are you uploading an ADIF file manually?
JTAlert only uploads to HRDLog.net as MODE=FT4

If you upload as MFSK, when you check the QSO on HRDLog you will note there is no field for SUBMODE only MODE. The MODE field is a dropdown with FT4 as one of the options.
   

   

From what I can see, HRDLog only accepts FT4 QSOs when logged with MODE = FT4.

de Laurie VK3AMA


locked #HRD #HRD

joaquin@...
 

Hello problem only with the FT4 mode in hdrlog, registration error, but if you register it as MFSK, emn previous version if you registered without error in FT4 What?


locked Re: Autolt Error

RICHARD BRESSLER
 

I am experiencing the same error when I use slicemaster to open jt alert.   

Rick


locked Re: Windows 10 May 2019 Update

Franco
 

Idem,
update at WIN10pro 64bit 1903 last week and jtALERT 2.13.7 here the righthand window cross is also not working.....I can close via taskbar 

Only after update at WIN10pro 64bit 1903

I always use "over 30Mhz" the MHSV with the MultiAnswer which is very useful for ES, Unfortunately it doesn't work with JTalertx, nevertheless I leave WSJTx open together ... ;-)


ps: Would it still be possible a "stby" option in JTalert to be opened even without WSJTx, so as to be able to use the interesting User Chat?If it starts first, it doesn't open if I open it together, but if I leave WSJTx, I don't know if JTalert also stop also the chat...

73's HB9oab


locked Re: Autolt Error

Rich McCabe
 

Oddly enough I think slicemaster was causing some issue. This is the bridge for Flex.  I deleted the slicemaster user directory and it took right off.

Rich


locked Re: Autolt Error

Rich McCabe
 

I have same issue all of a sudden. Have recent windows update but was working after that.

Tried renaming the ham apps directory under users. No help there.

Any other ideas?

Rich


locked Re: Windows 10 May 2019 Update

HamApps Support (VK3AMA)
 

On 17/06/2019 6:57 am, David wrote:
This was the standard layout.

I installed the alternate layout.  The minimize and close icons work fine.

David, AK2L
Tnx for reporting back David.

This is the result I expected.

There have been a couple of unverified reports that the "Alternate Layout" build was also malfunctioning after a recent Win10 update, but until I get confirmation from those users I am inclined to think they are mistaken as to the JTAlert build they are using. You confirmation adds further weight to idea.

de Laurie VK3AMA


locked Re: Windows 10 May 2019 Update

David - AK2L
 

Laurie,

This was the standard layout.

I installed the alternate layout.  The minimize and close icons work fine.

David, AK2L


locked Re: Seeing Only top of JTAlert Window

w2eck
 

Laurie - thanks so much for your timely help. Sorry must have missed the discussion on alternate layout, but that did the trick for me. Thank you for a great program and all the time you put in helping folks utilize it.
73 Paul
w2eck

11781 - 11800 of 36179