I just assumed that the only intent of the function was to aid you in chasing a callsign for a new country, state, grid or other.  Rather, while I do use the "Wanted Callsign" for that purpose, I was also using it for seeing when buddies show up on the band, which was effective only until I worked them the first time.  However, your comment regarding the priority is illuminating and most helpful. 

Cheers
de Matt W5MT

Matt,

The Wanted Call alert, obeys the worked B4 checks (as do all the other Wanted alerts) and is not entirely suitable for a Wanted Friend (Buddy) style of alert.

The Wanted Call alert is for those chasing specific Callsigns that wish to work them on each band/mode regardless of whether those Callsigns will generate one of the other Alerts. Some use cases...

• Chasing a DXPedition to work on as many Bands/Modes as possible.
• Chasing a specific Callsign that is a known reliable QSL'er (eg. I use this for Callsigns that use LoTW and I  want to get the LoTW confirmations regardless of previous Card confirmations).

A Wanted Friend (Buddy) alert is on the todo list, but unlikely to be implemented until JTAlert V3.

de Laurie VK3AMA
   

Settings/Wanted Grids

Click on the Wanted Grids line to see the checkbox to enable it.

Ensure you have "By Individual Band" and "By Individual Mode: selected.

You just have to rescan your log at the beginning of the month to reset them.

de Mike W9MDB

Mike,

A correction, Set Mode Tracking to Any Digital Mode (The Grid Chase doesn't consider individual Digital modes).

de Laurie VK3AMA
   

Just wonder if I will be able to look for grids needed with JTAertX ???

OM,

Yes, JTAlert supports the Chase provided it is setup correctly.
See the JTAlert Help file, "Tutorials -> ARRL International Grid Chase 2018" topic.

de Laurie VK3AMA
   

Just wonder if I will be able to look for grids needed with JTAertX ???

Once you have worked a station B4 ,,, It can't be wanted anymore, for anything, can it ??
--
73
Ron, W3RJW

On 2/23/2018 07:40, g4wjs wrote:

you are running unreleased development WSJT-X code, why do you expect it
to work?

well.gee. because for a few years, I have been running such, and I only
have gotten the nag when I had erased the settings for the UDP stuff
inside wsjtx.

Try starting WSJT-X and accepting the warning notice about unreleased or
beta code before starting JTAlert.

Yup. I start WSJTx manually.
After a bit I remember, or I look up, and then start JTAlert.

the second time today, this afternoon, I started wsjtx then started
jtalert and it took two restarts with appropriate delays between
starting wsjtx, before I stopped seeing the UDP warning.

So, this was odd. So, I wrote.



--
73,
Bob KD7YZ

Thanks, Laurie, the explanation makes sense in how the whole alert process works.  I do enjoy the utilitarian aspects of JTAlert.  It is a fantastic addition to WSJT and the N3FJP logging software.

Keep up the great work.

73,
Stan

Spoke too soon.  Looks like "B4" has ultimate priority over all, unless you turn it off completely by band, mode or by date.  So, once a "Wanted Callsign" is worked, the callsign cannot be set to show "wanted" status again without turning off B4 for all stations (by the parameters above); is that correct?

Laurie,

Thanks for your comment.  I was going to comment that the "Wanted Callsign" only showed up in its default or user set color until you worked the callsign; after that, it shows up as B4.  I just assumed that the only intent of the function was to aid you in chasing a callsign for a new country, state, grid or other.  Rather, while I do use the "Wanted Callsign" for that purpose, I was also using it for seeing when buddies show up on the band, which was effective only until I worked them the first time.  However, your comment regarding the priority is illuminating and most helpful. 

Cheers
de Matt W5MT

On 23/02/2018 12:20, KD7YZ Bob wrote:

I get this nag rather frequently however there is no pattern.

The screenshot shows the nag and the other one shows the correct
settings in WSJTx itself.


-- 73, Bob KD7YZ

Hi Bob,

you are running unreleased development WSJT-X code, why do you expect it to work?

Try starting WSJT-X and accepting the warning notice about unreleased or beta code before starting JTAlert.

73
Bill
G4WJS.



--
73
Bill
G4WJS.

I get this nag rather frequently however there is no pattern.

The screenshot shows the nag and the other one shows the correct
settings in WSJTx itself.


--
73,
Bob KD7YZ

If JTAlert is spotting with an incorrect frequency, then WSJT-X must be reporting the wrong frequency.

Is the WSJT-X QRG changing when you enable dual watch?

de Laurie VK3AMA

In addition to the above, I can monitor another frequency using dualwatch on my 7800 without affecting WSJT-X/JTAlert, BUT if I make the subVFO active, WSJT-X changes frequency to that of the subVFO and subsequently, JTAlert is reporting the wrong frequency.

This is not a JTAlert defect, but expected behaviour if the active VFO is changed. IMHO.

de Laurie VK3AMA
   

On 23/02/2018 5:12 PM, Björn Ekelund wrote:

I don't know if this is a DXLab Commander or JTAlert issue but I start here.

I use DXLab Commander for WSJT-X rig control with my IC-7610.
I use JTAlert to log in DXKeeper and also create local spots in Spotcollector.
(The latter is a particularly great feature which allows you to briefly step a way from the radio without missing interesting stations.)
In WSJT-X I use "Fake it" for split operation which, technically, frees up the sub receiver for other use during WSJT operation.

If I, say, monitor FT8 on one band with WSJT-X/JTalert, enable dual watch and look for CW DX on another band with the sub-receiver,
JTAlert will use the selected (sub) VFO as the base frequency for local spots rather than the main VFO which is the one actually receiving FT8.
This means the local spots created by JTAlert end up "all over the place".

I realize this is likely "by design" so my question is rather if there is a way around it?

I agree this may be a somewhat odd use case, but for radios with dual receivers it is really great to have the ability to
check other frequencies for interesting DX while monitoring FT8.

Thanks & 73,

Björn SM7IUN

Björn.

JTAlert has no concept of frequency/CAT control, dual receivers or active VFO.

JTAlert determines your operating frequency via the frequency reported by WSJT-X (in its UDP Status packets).

If JTAlert is spotting with an incorrect frequency, then WSJT-X must be reporting the wrong frequency.

Is the WSJT-X QRG changing when you enable dual watch?

de Laurie VK3AMA

I set the wanted call alert for both audible and visual alerts.  I hear “wanted call” audible alert but no distinct display of the colors I set for the visual indication of the call.  As a result I’m missing something because I have a number of wanted calls and can’t decipher the call list quickly enough to verify which station it is.

Are the two alerts mutually exclusive or is there something I’m missing or an issue with this function?

Thanks for any assistance.

73,

Stan, WA4DYD

Stan,

The only time you wont see Wanted Callsign Alert coloring is if that Callsign (decode) generated one of the other alert types and that alert has a higher priority than the Wanted Callsign alert. By default, all of the other Wanted alerts have a higher priority than the Wanted Callsign alert.

If you need Wanted Callsign alerts to color the Callsign regardless of the other alerts generated, you need to adjust the Alert Priorities, see the Settings, Alerts -> Alert Priority section.

de Laurie VK3AMA
   

This post is about the CQ USA-CA, the famous american counties award and JT-Alert. I know tan in version 3 will include a tracker for counties, but I’ve been told that there is a way of tracking them with the actual versión if you are an XML user. I am, I activated the XML lookup, but I can’t find the way to make JT alert warn me abt my “no worked counties”. Is there any tutorial or anyone can give me a hand, please?

 

Carlos, EA1DWI

Carlos,

The only support for US Counties in JTAlert V2 is the logging of the County returned from an XML lookup (if the xml data contains a county entry).

There is no support for alerting of any sort for Counties.

de Laurie VK3AMA