Date   

locked Re: DX Marathon Wanted and B4

Jon KM8V
 

Well, strangely, without changing anything else - except posting this message! :) - the B4 station is now properly highlighted as Marathon Wanted, after being B4 highlighted for an hour.


locked Re: DX Marathon Wanted and B4

Jon KM8V
 

Worked B4 is not available in the alerts priority settings window.


locked Re: DX Marathon Wanted and B4

Jim Cooper
 

On 26 Dec 2020 at 6:15, Jon KM8V wrote:

> It looks like B4 highlighting is
> taking precedence over Marathon
> Wanted status - Marathon should
> alert even if it is worked B4, or
> there should be an option to ignore
> B4 for wanted Marathon stations, I
> would think?

In the alert priority list, do you have
"Worked B4" below the "Wanted CQ Marathon"?

graphic

Use F1 to get the above window.

w2jc

  


locked Duplicate Logging in HRD and more...

Craig
 

With HRD supporting Google Earth Pro, the logging record must have the blank fields populated, specifically LAT / LON.  Under HRD --> Tools --> Configure --> QSO forwarding, there are two UDP Receive check boxes that enable the lookup and filling of this data.  To work with the WSJT-X / JTAlert combo the checkbox for receiving QSO UDP notifications via WSJT-X needs to be checked.  This action, along with requiring JTAlert to have HRD logging enabled generates a duplicate HRD logging entry, one of which (from JTAlert) is not populated completely as needed, the other from WSJT-X which contains all of the populated fields required.

The dilemma is turning off the UDP receive from WSJT-X leaves the JTAlert logging record, which is missing the data required.  Turning off JTAlert HRD logging disables the important tracking functionality wanted in JTAlert. 

So the issue is not limited to getting rid of a duplicate log entry, but to ensuring that the record that is logged includes the populated field data.  Otherwise, the logging record has to be edited separately with the lookup / update options.

Has anyone been able to get this to work?  Appreciate any guidance on this.  73, Craig


locked DX Marathon Wanted and B4

Jon KM8V
 

It looks like B4 highlighting is taking precedence over Marathon Wanted status - Marathon should alert even if it is worked B4, or there should be an option to ignore B4 for wanted Marathon stations, I would think?

Thanks & 73 - Love JT-Alert!


locked Re: Feature Request: QSO Pop-up

John AA6ZT
 

Sure it pops up, but nothing helpful is showing. The sub-menu when right clicking on an alerting call sign displays many vital information choices. The "Show QSOs History Popup" is not reflected in the F3 choice.


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

Dick Bingham
 

Hello Laurie

I guess it is Merry Christmas time down there in VK-Land now. I hope it is a
merry one for you and your family.

Now regarding your ===>
While more memory is always good, CPU usage is the most critical. What is taskmanager telling you when WSJT-X is busy 
processing decodes at the end of a period? What CPU usage is it indicating? If your hitting 80% or greater than that is a problem,
it will cause WSJT-X (and everything else on your PC) to be slowed.

The Underline indicates that that Callsign has the Text Messages function of JTAlert enabled and is set to receive messages.

de Laurie VK3AMA 
 
 I observed my CPU usage for 5-minutes or so and observed a max-usage of the CPU to be close to
65-percent during decode processing. Most of the time CPU usage runs in the mid-40's.

Again, I'm seeing up to 65-seconds for the WSJT-X logging pop-up window to finish once I click
on the "OK" after my "73" transmission finishes. During the 65-second period the main WSJT-X
screen is frozen (according to the 'clock' feature on the main WSJT-X window) and then jumps
to the correct time once the logging window collapses.

I will shut-down the computer and restart everything and observe what happens during the logging
process.

OK on the under-lining - doubt I will use it.

73  Dick/w7wkr at CN97uj

BIG SNIP


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

HamApps Support (VK3AMA)
 

On 24/12/2020 10:52 am, Dick Bingham wrote:

I guess I did not make myself clear . I am decoding call signs OK but when the CQer is 
sending "CQ DX VK3AMA QF##" I do not see the "DX" part in the 'cell' with the callsign.
The State and VE parts display fine.

No change when I expand to 4 X 9 display presentation. Once I'm certain what needs to
be seen is there, the main window for WSJT-X can be collapsed and only use the JTAlert
display.

Great software ! How many development MAN-Years does JTTAlert represent ? 

73  Dick/w7wkr at CN97uj

RRR.

"DX" is never explicitly displayed like a State or Province. There is however a directed CQ indicator (see the Alerts -> CQ section of the Settings) that can be displayed, "#" versus the "*" for a non-directed CQ. There is also a colored border option  that will wrap the Callsign, you can set a different color for directed CQs.

The copyright notice for JTAlert indicates it was first produced in 2011, so 10 years.

de Laurie VK3AMA

de Laurie VK3AMA


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

HamApps Support (VK3AMA)
 

On 24/12/2020 11:16 am, Dick Bingham wrote:
Hello again

I highly suspect my DELL Laptop E6510 W7 with 4G of RAM is the problem.
when the following SW is running:

- PowerSDR OpenHPSDR mRX PS v3.4.7
- Voicemeeter Banana
- WSJT-X v2.2.2
- DXKeeper 15.7.2
- JTAlert 2.16.17

The available free RAM drops below 350MB according to Win Task Manager.
I now only click "OK" in the pop-up logging window after my last transmission
has cleared. I have a reasonably fast internet connection and use a router to
connect with remote computers.

JTAlert DOES present a success or failure message after the logging has finished.
Same for the pop-up window associated with the WSJT-X logger. 

What is the significance of a call displayed as AA7Aw - AZ VS AA7AW - AZ
where one 'cell' is underlined and another is not underlined ?

73  Dick/w7wkr at CN97uj

While more memory is always good, CPU usage is the most critical. What is taskmanager telling you when WSJT-X is busy processing decodes at the end of a period? What CPU usage is it indicating? If your hitting 80% or greater than that is a problem, it will cause WSJT-X (and everything else on your PC) to be slowed.

The Underline indicates that that Callsign has the Text Messages function of JTAlert enabled and is set to receive messages.

de Laurie VK3AMA


locked Re: Feature Request: QSO Pop-up

HamApps Support (VK3AMA)
 

On 25/12/2020 6:58 am, John Maguire AA6ZT wrote:

The QSO Pop-up is a helpful tool.

However, it should include:

1. Timed appearance. 5 seconds is enough, or a user choice
2. Smaller. It could be smaller if there is no activity to report
3. Position. It should be movable to another place on the screen as the user chooses


73s, John AA6ZT


Use the F3 hotkey to bring up the "Callsign History Window" which is the same as the popup you refer to. It is a standalone window that can be positioned anywhere. It will auto-track the DXCall in WSJT-X. If you have the hotkeys turned off, the "View -> Callsign History Window" menu does the same.

de Laurie VK3AMA


locked Feature Request: QSO Pop-up

John AA6ZT
 

The QSO Pop-up is a helpful tool.

However, it should include:

1. Timed appearance. 5 seconds is enough, or a user choice
2. Smaller. It could be smaller if there is no activity to report
3. Position. It should be movable to another place on the screen as the user chooses


73s, John AA6ZT


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

neil_zampella
 

Um ... you'll never see the DX in the cell ... you need to set the 'Directed Call' color in the settings which will notify you of that request by a colored band around the cell.   I use a RED color to reflect a 'directed' call.

 

Neil, KN3ILZ


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

Robert Lorenzini
 

I can't respond to you're specific problems but you need to
upgrade to the latest (3.4.9) before posting a problem. There
have been fixes since 3.5.7. That may not fix your problem but
it puts us all on the same page.  Happy holidays to you and
the group.

Bob - wd6dod

On 12/23/2020 4:16 PM, Dick Bingham wrote:
Hello again

I highly suspect my DELL Laptop E6510 W7 with 4G of RAM is the problem.
when the following SW is running:

- PowerSDR OpenHPSDR mRX PS v3.4.7
- Voicemeeter Banana
- WSJT-X v2.2.2
- DXKeeper 15.7.2
- JTAlert 2.16.17

The available free RAM drops below 350MB according to Win Task Manager.
I now only click "OK" in the pop-up logging window after my last transmission
has cleared. I have a reasonably fast internet connection and use a router to
connect with remote computers.

JTAlert DOES present a success or failure message after the logging has finished.
Same for the pop-up window associated with the WSJT-X logger. 

What is the significance of a call displayed as AA7Aw - AZ VS AA7AW - AZ
where one 'cell' is underlined and another is not underlined ?

73  Dick/w7wkr at CN97uj

On Wed, Dec 23, 2020 at 2:15 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 24/12/2020 7:38 am, Dick Bingham wrote:
- IF I click "OK"in the "Confirm QSO Window" while my "73" is being transmitted, the entire system freezes for tens-of-seconds before recovering - being careful to click 
 "OK"  after the transmission is completed solves this problem


That indicates that JTAlert is stuck waiting to verify the QSO was actually written to the DXKeeper log. 10's of seconds is excessive, on a moderate PC I would expect that to be under 5 secs depending on what online activities DXKeeper is performing post logging. How reliable/fast is your internet connection? If you have DXKeeper auto-uploading to LoTW or eQSL and those services are down or slow, than delays in DXKeeper writing the QSO to the log file are normal and JTAlert will hang (as will DXKeeper) while it retries reading the log file to confirm the QSO was written.

Does JTAlert present you with a success or failure message after the logging?

de Laurie VK3AMA



locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

Dick Bingham
 

Hello again

I highly suspect my DELL Laptop E6510 W7 with 4G of RAM is the problem.
when the following SW is running:

- PowerSDR OpenHPSDR mRX PS v3.4.7
- Voicemeeter Banana
- WSJT-X v2.2.2
- DXKeeper 15.7.2
- JTAlert 2.16.17

The available free RAM drops below 350MB according to Win Task Manager.
I now only click "OK" in the pop-up logging window after my last transmission
has cleared. I have a reasonably fast internet connection and use a router to
connect with remote computers.

JTAlert DOES present a success or failure message after the logging has finished.
Same for the pop-up window associated with the WSJT-X logger. 

What is the significance of a call displayed as AA7Aw - AZ VS AA7AW - AZ
where one 'cell' is underlined and another is not underlined ?

73  Dick/w7wkr at CN97uj

On Wed, Dec 23, 2020 at 2:15 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 24/12/2020 7:38 am, Dick Bingham wrote:
- IF I click "OK"in the "Confirm QSO Window" while my "73" is being transmitted, the entire system freezes for tens-of-seconds before recovering - being careful to click 
 "OK"  after the transmission is completed solves this problem


That indicates that JTAlert is stuck waiting to verify the QSO was actually written to the DXKeeper log. 10's of seconds is excessive, on a moderate PC I would expect that to be under 5 secs depending on what online activities DXKeeper is performing post logging. How reliable/fast is your internet connection? If you have DXKeeper auto-uploading to LoTW or eQSL and those services are down or slow, than delays in DXKeeper writing the QSO to the log file are normal and JTAlert will hang (as will DXKeeper) while it retries reading the log file to confirm the QSO was written.

Does JTAlert present you with a success or failure message after the logging?

de Laurie VK3AMA


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

Dick Bingham
 

Hello Laurie

I guess I did not make myself clear . I am decoding call signs OK but when the CQer is 
sending "CQ DX VK3AMA QF##" I do not see the "DX" part in the 'cell' with the callsign.
The State and VE parts display fine.

No change when I expand to 4 X 9 display presentation. Once I'm certain what needs to
be seen is there, the main window for WSJT-X can be collapsed and only use the JTAlert
display.

Great software ! How many development MAN-Years does JTTAlert represent ? 

73  Dick/w7wkr at CN97uj

On Wed, Dec 23, 2020 at 2:10 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 24/12/2020 7:38 am, Dick Bingham wrote:
- A decoded directed CQ (like "CQ DX W1AW FN##") is not indicated in a 2X8 JTAlert display Cell forcing me to still examine the WSJT-X screen to minimize interfering 
  with the CQer's real interest

You're missing decoded callsigns because your limiting the JTAlert display. The display can go to 4 lines x 9 callsigns. See the View menu.

If 36 callsign slots is not enough, you can try restricting the number displayed by using one or more Alert filters. Alternatively, use the Decodes window which will display all the callsigns in a period.

de Laurie VK3AMA


locked Re: JTAlert works fine but no colored calls in WSJT

N2TK, Tony
 

Thanks Laurie for the info.

Merry Christmas

N2TK, Tony

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Wednesday, December 23, 2020 6:30 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert works fine but no colored calls in WSJT

 

On 24/12/2020 10:15 am, N2TK, Tony via groups.io wrote:

Never mind. I have to use the red musical note shortcut to see the colored callouts in WSJT. Not sure what the colors mean but it is working fine.

N2TK, Tony

  Red icon  -> JTAlert for WSJT-X
  Blue icon -> JTAlert for JTDX

Don't bother trying to get the JTDX decodes colored by JTAlert, it is not supported. The relevant code in the original WSJT-X source was stripped by the JTDX people for some reason.

de Laurie VK3AMA


locked Re: JTAlert works fine but no colored calls in WSJT

HamApps Support (VK3AMA)
 

On 24/12/2020 10:15 am, N2TK, Tony via groups.io wrote:

Never mind. I have to use the red musical note shortcut to see the colored callouts in WSJT. Not sure what the colors mean but it is working fine.

N2TK, Tony

  Red icon  -> JTAlert for WSJT-X
  Blue icon -> JTAlert for JTDX

Don't bother trying to get the JTDX decodes colored by JTAlert, it is not supported. The relevant code in the original WSJT-X source was stripped by the JTDX people for some reason.

de Laurie VK3AMA


locked Re: JTAlert works fine but no colored calls in WSJT

N2TK, Tony
 

Never mind. I have to use the red musical note shortcut to see the colored callouts in WSJT. Not sure what the colors mean but it is working fine.

N2TK, Tony

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of N2TK, Tony via groups.io
Sent: Wednesday, December 23, 2020 5:52 PM
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlert works fine but no colored calls in WSJT

 

Updated JTAlert. Seems to be working fine. But none of the highlighted calls appear highlighted in WSJT. What did I forget to change?
I used the blue musical note shortcut. Do I need to use a different color and/or the "X" instead of the musical symbol?
Tnx
N2TK, Tony


locked JTAlert works fine but no colored calls in WSJT

N2TK, Tony
 

Updated JTAlert. Seems to be working fine. But none of the highlighted calls appear highlighted in WSJT. What did I forget to change?
I used the blue musical note shortcut. Do I need to use a different color and/or the "X" instead of the musical symbol?
Tnx
N2TK, Tony


locked Re: JT Alert & WSJT-X interactions

HamApps Support (VK3AMA)
 

On 22/12/2020 4:56 am, Mike Turner wrote:
I was trying to discover why I no longer get the "worked before" alert on JTAlert.

If you're not getting B4's than likely the log your using with JTAlert has changed or no longer contains your previous QSOs.

What log type are you using, does it still contain all your past QSOs?

de Laurie VK3AMA

4281 - 4300 of 36897