Date   

locked Re: : Re: New alert?

Laurie, VK3AMA <groups08@...>
 

Tnx Bill

de Laurie VK3AMA
   


On 26/05/2016 10:26 AM, bill.8@... [HamApps] wrote:

Hi Laurie,

the latest revision of NetworkMessage.hpp is here:

WSJT / WSJT / [r6703] /branches/wsjtx/NetworkMessage.hpp

 

this is scheduled for the next release i.e. WSJT-X v1.7.0

73
Bill
G4WJS.


locked Re: : Re: New alert?

g4wjs
 

Hi Laurie,

the latest revision of NetworkMessage.hpp is here:

WSJT / WSJT / [r6703] /branches/wsjtx/NetworkMessage.hpp

 

this is scheduled for the next release i.e. WSJT-X v1.7.0

73
Bill
G4WJS.


locked Re: New poll for HamApps

bryan_m0oic
 

Hi Laurie,

I have added that I am using Windows 10. On my Dell laptop straight forward but on my iMac a bit different. My latest Mac is an iMac i5 5K with 16GB memory. 8GB is held for El Capitan when running Windows as Windows 10 Pro is virtualised via Parallels Desktop 11. Pleased to confirm that WSJT-X and JT-Alert/Macro never falter. Windows 10 is therefore running in 8GB with Parallels. Again, many thanks for what you do.

On 25 May 2016, at 23:31, HamApps@... wrote:


Enter your vote today! A new poll has been created for the HamApps group:
What is the Windows OS you use with JTAlert?
Created by: vkdxer
  1. Win10 upgrade pending
  2. Win10
  3. Win8
  4. Win7
  5. Vista
  6. XP


Thanks!




locked Re: : Scan and Update

groups08@...
 

OM (What is your Name?)

You said "I am using HRD and the log name matches where it is looking". Where are you setting the HRD Log name? JTAlert doesn't require the Log Name (file path), it uses the ODBC DSN of the log.

Please describe your operating environment. JTAlert version, HRD version & JT mode application. Do you have JTAlert logging to HRD enabled?

If the Scan Log is changing your manually set Wanted States suggests that you are likely specifying a QSL condition for the Scan that is not met by your HRD Log.

For example, if you have LoTW Confirmed as a requirement for a State to be no longer considered needed, but your HRD log has not been updated to reflect any new LoTW confirmations for that State, than the JTAlert "Scan Log" will not find any LoTW Confirmed (no longer needed) QSOs for that State and will mark the State as needed, regardless of any manual setting you made.

You should not be mixing manual setting of needed/unneeded States with a Scan Log. You should be using one or the other method. The Scan Log is the simplest and fastest, especially since your using one of the JTAlert supported Log types.

de Laurie VK3AMA


locked Re: Scan and Update

Laurie, VK3AMA <groups08@...>
 

OM (What is your Name?)

You said "I am using HRD and the log name matches where it is looking". Where are you setting the HRD Log name? JTAlert doesn't require the Log Name (file path), it uses the ODBC DSN of the log.

Please describe your operating environment. JTAlert version, HRD version & JT mode application. Do you have JTAlert logging to HRD enabled?

If the Scan Log is changing your manually set Wanted States suggests that you are likely specifying a QSL condition for the Scan that is not met by your HRD Log.

For example, if you have LoTW Confirmed as a requirement for a State to be no longer considered needed, but your HRD log has not been updated to reflect any new LoTW confirmations for that State, than the JTAlert "Scan Log" will not find any LoTW Confirmed (no longer needed) QSOs for that State and will mark the State as needed, regardless of any manual setting you made.

You should not be mixing manual setting of needed/unneeded States with a Scan Log. You should be using one or the other method. The Scan Log is the simplest and fastest, especially since your using one of the JTAlert supported Log types.

de Laurie VK3AMA
   

On 26/05/2016 1:22 AM, nt9e@... [HamApps] wrote:
I just unchecked all states for all bands and ran a (Wanted States) scan and update. I wend back to wanted states and every state was checked for every band, again!
I am using HRD and the log name matches where it is looking.


locked Re: New poll for HamApps

signalhz signalhz <signalhz@...>
 

2

N4ABN

Sent from my iPhone

On May 25, 2016, at 15:42, "HamApps@..." <HamApps@...> wrote:

 

Enter your vote today! A new poll has been created for the HamApps group:
What is the Windows OS you use with JTAlert?
Created by: vkdxer
  1. Win10 upgrade pending
  2. Win10
  3. Win8
  4. Win7
  5. Vista
  6. XP


Thanks!


locked New poll for HamApps

HamApps@...
 

Enter your vote today! A new poll has been created for the HamApps group:
What is the Windows OS you use with JTAlert?
Created by: vkdxer
  1. Win10 upgrade pending
  2. Win10
  3. Win8
  4. Win7
  5. Vista
  6. XP


Thanks!


locked Re: : New alert?

g4wjs
 

On 25/05/2016 15:38, Black Michael mdblack98@... [HamApps] wrote:
WSJT-X 1.7 r6691 has a new UDP schema (version 3) that adds Rx DF, Tx DF, DE call, DE grid, DX grid

Hi Mike,


technically it is not a new schema. The existing schema allows new fields to be appended to existing messages so long as a sensible default is possible. It also allows new messages to be added. A schema number change is only required if the data field encoding is changed or if existing fields are removed or change data type. The current maximum schema number supported for WSJT-X v1.6.0 is 3 and these changes are still schema number 3.


73
Bill
G4WJS.


locked Re: New alert?

Laurie, VK3AMA <groups08@...>
 

Mike,

For want of a better title, an "RX Freq Alert". Generate an alert if a "free-form" decode is detected at your current RX DF +- a user defined
DeltaFrequency. Restricting to non-standard decodes should eliminate most of the the standard alert types (CQ, WAS, etc.) since they are irrelevant if your currently in QSO.
 

Does that sound like what your after?

de Laurie VK3AMA
   


On 26/05/2016 7:52 AM, Black Michael mdblack98@... [HamApps] wrote:
And this would also cover the case when QSO partners return a non-standard message that doesn't contain your callsign.   That happens quite frequently too and the alert serves to let you know.
So your description is correct with the addition of ignoring CQ's too.  So the next CQ that comes out after a QSO won't generate the alert.

Mike


locked Re: New alert?

Michael Black
 

And this would also cover the case when QSO partners return a non-standard message that doesn't contain your callsign.   That happens quite frequently too and the alert serves to let you know.
So your description is correct with the addition of ignoring CQ's too.  So the next CQ that comes out after a QSO won't generate the alert.

Mike


From: "'Laurie, VK3AMA' groups08@... [HamApps]"
To: HamApps@...
Sent: Wednesday, May 25, 2016 4:32 PM
Subject: Re: [HamApps] New alert?

 
Mike,

What are your trying to achieve?

Since the Rx DF will be at the frequency of your current QSO partner, I am assuming your wanting to monitor that frequency for non standard decodes, assuming that any decodes at that frequency are intended for you, so generating an "Own Call" style alert when the decode doesn't contain your Callsign. Is that the case?

de Laurie VK3AMA
   


On 26/05/2016 12:38 AM, Black Michael mdblack98@... [HamApps] wrote:
Could we get a new alert for Rx DF==DeltaFrequency that triggers when no other alert triggers, not a CQ, and doesn't contain DE call?
The idea being that a message that appears in the Rx Frequency window of WSJT-X may be of interest if you're monitoring that offset.  Any other alert would take precedence.  
WSJT-X uses +/- 10Hz for the Rx Window but having that adjustable in JTAlert would be nice too.  Maybe make "Ignore own call" and "Ignore CQ" checkable?
 
RRR
Mike W9MDB




locked Re: New alert?

Michael Black
 

I have my own patch in WSJT-X for this right now.

The idea is when you are monitoring another QSO session and hoping to break in.  So any message that shows up there is of interest.  And, in all cases that I can think of eliminating messages with your own call or CQ allows JTAlert to generate the appropriate alert with the patch I'm running.  With the multiple decodes now possible with WSJT-X 1.7 I've had a QSO partner respond after they are done directly so the CQ and own call alerts are generated correctly (no need for the new alert in this type of case).

So like right now I'm watching this...
CQ WA5IMF EM31
WA5MIF W9MDB EM49 (I replied)
KB9IFH WA5IMG +09 (somebody beat me but would still like an alert)
(can't see the other side but it would generate an alert too)
KB9IFH WA5IMG 73 (would like alert)

So...monitor the Rx +/1- 10Hz and tell me when there's a message in there but don't add to the noise by eliminating CQ and own call (their own alerts are already covered).  


Mike



From: "'Laurie, VK3AMA' groups08@... [HamApps]"
To: HamApps@...
Sent: Wednesday, May 25, 2016 4:32 PM
Subject: Re: [HamApps] New alert?

 
Mike,

What are your trying to achieve?

Since the Rx DF will be at the frequency of your current QSO partner, I am assuming your wanting to monitor that frequency for non standard decodes, assuming that any decodes at that frequency are intended for you, so generating an "Own Call" style alert when the decode doesn't contain your Callsign. Is that the case?

de Laurie VK3AMA
   


On 26/05/2016 12:38 AM, Black Michael mdblack98@... [HamApps] wrote:
Could we get a new alert for Rx DF==DeltaFrequency that triggers when no other alert triggers, not a CQ, and doesn't contain DE call?
The idea being that a message that appears in the Rx Frequency window of WSJT-X may be of interest if you're monitoring that offset.  Any other alert would take precedence.  
WSJT-X uses +/- 10Hz for the Rx Window but having that adjustable in JTAlert would be nice too.  Maybe make "Ignore own call" and "Ignore CQ" checkable?
 
RRR
Mike W9MDB




locked Re: New alert?

Laurie, VK3AMA <groups08@...>
 

Mike,

What are your trying to achieve?

Since the Rx DF will be at the frequency of your current QSO partner, I am assuming your wanting to monitor that frequency for non standard decodes, assuming that any decodes at that frequency are intended for you, so generating an "Own Call" style alert when the decode doesn't contain your Callsign. Is that the case?

de Laurie VK3AMA
   


On 26/05/2016 12:38 AM, Black Michael mdblack98@... [HamApps] wrote:
Could we get a new alert for Rx DF==DeltaFrequency that triggers when no other alert triggers, not a CQ, and doesn't contain DE call?
The idea being that a message that appears in the Rx Frequency window of WSJT-X may be of interest if you're monitoring that offset.  Any other alert would take precedence.  
WSJT-X uses +/- 10Hz for the Rx Window but having that adjustable in JTAlert would be nice too.  Maybe make "Ignore own call" and "Ignore CQ" checkable?
 
RRR
Mike W9MDB


locked Re: Scan and update?

Laurie, VK3AMA <groups08@...>
 

OM,

Why are you doing reinstalls of JTAlert? Not that it should matter, as your JTAlert configuration, which contains your Wanted Lists is retained across JTAlert reinstalls and upgrades. I am curious why you feel the need to do reinstalls.

What Log are you using with JTAlert, if any?

If your manually scanning a HRD log to update your Wanted Lists suggests that you don't have JTAlert set to log to your HRD log, then JTAlert will not use that HRD log for its automated "Scan Log" function and will overwrite any manual settings you made.

The JTAlert "Scan Log" is done against whatever log type you have JTAlert set to log to. This simplifies the updating of the Wanted Lists avoiding the manual updating you are performing.

It is not really clear from your description how you have your JTAlert/HB9HQX/HRD environment setup. Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration file for analysis.   

de Laurie VK3AMA
   


On 26/05/2016 12:57 AM, nt9e@... [HamApps] wrote:

When ever I have to re-install JTAlert(HB9) I do a scan and update. When I go back to check the states, every state on every band still has an X. I then have to do my own scanning via HRD and then check only the entities which are un confirmed. This also happens on DXCC entities, WPX, and WAZ. Am I doing something wrong?




locked Re: New alert?

Laurie, VK3AMA <groups08@...>
 

Mike,

Sorry, too early in the morning here (still on the first cup of coffee).

I was confusing the Grid passed in the Decode packet with the "DX Grid" of your current QSO partner. I would image it is passed in the Status packet of the extended schema.

de Laurie VK3AMA
   



On 26/05/2016 6:25 AM, 'Laurie, VK3AMA' groups08@... [HamApps] wrote:
 

Mike,

Which UDP packet is carrying this additional data. DX Grid would suggest the decode packet, while the other data suggests the Status packet. Do you have an updated "NetworkMessage.hpp" file reflecting the schema change?

Any changes to JTAlert embracing this new UDP schema won't make the next JTAlert release (2.7.3) as it is with the Beta testers and will likely to be made public later today.

de Laurie VK3AMA
   


On 26/05/2016 12:38 AM, Black Michael mdblack98@... [HamApps] wrote:
WSJT-X 1.7 r6691 has a new UDP schema (version 3) that adds Rx DF, Tx DF, DE call, DE grid, DX grid

Could we get a new alert for Rx DF==DeltaFrequency that triggers when no other alert triggers, not a CQ, and doesn't contain DE call?
The idea being that a message that appears in the Rx Frequency window of WSJT-X may be of interest if you're monitoring that offset.  Any other alert would take precedence.  
WSJT-X uses +/- 10Hz for the Rx Window but having that adjustable in JTAlert would be nice too.  Maybe make "Ignore own call" and "Ignore CQ" checkable?
 
RRR
Mike W9MDB



locked Re: New alert?

Michael Black
 

I can send you an install package too if you'd like.

Mike



From: "'Laurie, VK3AMA' groups08@... [HamApps]"
To: HamApps@...
Sent: Wednesday, May 25, 2016 3:25 PM
Subject: Re: [HamApps] New alert?

 
Mike,

Which UDP packet is carrying this additional data. DX Grid would suggest the decode packet, while the other data suggests the Status packet. Do you have an updated "NetworkMessage.hpp" file reflecting the schema change?

Any changes to JTAlert embracing this new UDP schema won't make the next JTAlert release (2.7.3) as it is with the Beta testers and will likely to be made public later today.

de Laurie VK3AMA
   


On 26/05/2016 12:38 AM, Black Michael mdblack98@... [HamApps] wrote:
WSJT-X 1.7 r6691 has a new UDP schema (version 3) that adds Rx DF, Tx DF, DE call, DE grid, DX grid

Could we get a new alert for Rx DF==DeltaFrequency that triggers when no other alert triggers, not a CQ, and doesn't contain DE call?
The idea being that a message that appears in the Rx Frequency window of WSJT-X may be of interest if you're monitoring that offset.  Any other alert would take precedence.  
WSJT-X uses +/- 10Hz for the Rx Window but having that adjustable in JTAlert would be nice too.  Maybe make "Ignore own call" and "Ignore CQ" checkable?
 
RRR
Mike W9MDB




locked Re: Facebook

Laurie, VK3AMA <groups08@...>
 

No,

There is not a Facebook page for JTAlert. There are no plans to add Facebook as an additional support forum.
 
This Yahoo group is the primary forum for JTAlert support.

de Laurie VK3AMA
   


On 26/05/2016 1:23 AM, nt9e@... [HamApps] wrote:

Is there a JTAlert Facebook page?




locked Re: New alert?

Laurie, VK3AMA <groups08@...>
 

Mike,

Which UDP packet is carrying this additional data. DX Grid would suggest the decode packet, while the other data suggests the Status packet. Do you have an updated "NetworkMessage.hpp" file reflecting the schema change?

Any changes to JTAlert embracing this new UDP schema won't make the next JTAlert release (2.7.3) as it is with the Beta testers and will likely to be made public later today.

de Laurie VK3AMA
   


On 26/05/2016 12:38 AM, Black Michael mdblack98@... [HamApps] wrote:
WSJT-X 1.7 r6691 has a new UDP schema (version 3) that adds Rx DF, Tx DF, DE call, DE grid, DX grid

Could we get a new alert for Rx DF==DeltaFrequency that triggers when no other alert triggers, not a CQ, and doesn't contain DE call?
The idea being that a message that appears in the Rx Frequency window of WSJT-X may be of interest if you're monitoring that offset.  Any other alert would take precedence.  
WSJT-X uses +/- 10Hz for the Rx Window but having that adjustable in JTAlert would be nice too.  Maybe make "Ignore own call" and "Ignore CQ" checkable?
 
RRR
Mike W9MDB


locked Facebook

Dave NT9E
 

Is there a JTAlert Facebook page?



locked Scan and Update

Dave NT9E
 

I just unchecked all states for all bands and ran a (Wanted States) scan and update. I wend back to wanted states and every state was checked for every band, again!
I am using HRD and the log name matches where it is looking.



locked Scan and update?

Dave NT9E
 

When ever I have to re-install JTAlert(HB9) I do a scan and update. When I go back to check the states, every state on every band still has an X. I then have to do my own scanning via HRD and then check only the entities which are un confirmed. This also happens on DXCC entities, WPX, and WAZ. Am I doing something wrong?