Date   

locked Re: Grid Chase - one more question

Michael Black
 

Yes...you get credit for each band/mode every month.

So 12 bands, 3 modes (Just looking at FT8, JT65, and JT9) , 12 months means up to 432 QSOs to the same call sign.  :-)

de Mike W9MDB



On Wednesday, January 10, 2018, 11:53:31 AM CST, Bernd - KB7AK <bernd1peters@...> wrote:


I think I found it, it seems that there is a distinction between FT8 and JT65 and JT9


locked Re: Grid Chase - one more question

Bernd - KB7AK
 

I think I found it, it seems that there is a distinction between FT8 and JT65 and JT9


locked Re: Grid Chase - one more question

Bernd - KB7AK
 

Hi Jim,

Yes, I did the scan, I scan several times a day, usually after I uploaded and synchronized with LoTW. 


locked Re: Feature Request - Filter out constrained CQ calls

Michael Black
 

You can turn on flags which indicate if a CQ is directional or not.
Alerts/CQ and QRZ has the two indicators "*" and "#" for non-directional an directional...so if you see "#" you should know to look first.

Not quite as sophisticated as to what you suggest...but "CQ DX" could include you too so not sure you'd want to filter those out.

de Mike W9MDB


On Wednesday, January 10, 2018, 10:46:38 AM CST, Bob Segrest <Bob.Segrest@...> wrote:


I really appreciate the fact that I can select an incoming CQ in the JTAlert application to trigger a response.  This helps a lot in FT8 when there is so much band activity that the you have to scroll back for it in WSJT-X.

The only down side I have seen with this is that some users are constraining their responses to a single state or DX only.  For example...

  • CQ AK ZS4JAN KG30
  • CQ DX W3BTX FN00
If you miss this, you tend to get a snarky response and it generally wastes time.

It would be nice to have a filter that would prevent these calls from triggering JTAlert alarms.  A simple ignore any CQ call with a "CQ XX " format would work.  Something a bit more sophisticated like "Ignore CQ XX unless XX = VA" would be better.

If there is already a way to do this, please let me know.

Bob
KO2F


locked Feature Request - Filter out constrained CQ calls

Bob Segrest
 

I really appreciate the fact that I can select an incoming CQ in the JTAlert application to trigger a response.  This helps a lot in FT8 when there is so much band activity that the you have to scroll back for it in WSJT-X.

The only down side I have seen with this is that some users are constraining their responses to a single state or DX only.  For example...

  • CQ AK ZS4JAN KG30
  • CQ DX W3BTX FN00
If you miss this, you tend to get a snarky response and it generally wastes time.

It would be nice to have a filter that would prevent these calls from triggering JTAlert alarms.  A simple ignore any CQ call with a "CQ XX " format would work.  Something a bit more sophisticated like "Ignore CQ XX unless XX = VA" would be better.

If there is already a way to do this, please let me know.

Bob
KO2F


locked Re: WSJT-X and FT-1000D

Michael Black
 

That really has nothing to with this email list.

Your problem is probably RF in the shack.

You'll probably find a certain power level on certain bands will interrupt the USB devices.

All sorts of solutions to be had -- USB cable with torroid (built-in or do-it-yourself), grounding things correctly, antenna loops to prevent RF on the shield.

de Mike W9MDB


On Wednesday, January 10, 2018, 5:50:51 AM CST, Jim Johnson <jim.kc4hw@...> wrote:


Using WSJT-X, v1.80 and FT-1000D for Digital Modes (especially FT-8).  The interface for
the CAT Control is from MFJ.

Unfortunately, the CAT Control with WSJT-X for the FT-1000D seems to be intermittent.  It
will just drop out and another dialog comes up that indicates that communication has failed
and to check SETTINGS.  Here are the setting for the FT-1000D in use:

CAT Contro
    Serial Port COM4
    Baud Rate: 4800
    Data Bits: 8
    Stop Bits: 2
    Handshake: None
    Force Control Lines:
    DTR:  No selection
    RTS:  RTS High
    PTT Method: VOX
    Transmit Audio Source:  Front/Mic
    Mode:  USB

This setup seems to work with Logger 32, Writelog but is intermittent with WSJT-X.

Anyone using a FT-1000D have a solution to this intermittent CAT Control problem with
WSJT-X???

Jim/KC4HW

   




locked Daily Digest

Wes Elton
 

Hi,  Many thanks to those who responded. to my post re the above.

73,
Wes.
GW3RIH


locked Re: Grid Chase - one more question

Jim - N4ST
 

Bernd,

Your screenshots didn't come through, so I am shooting in the dark.
Did you do a logbook scan since you got the LoTW confirmation?
The JTAlert-X worked B4 status is only as good as the last logbook scan, assuming you are using a third-party logbook.
______________
73,
Jim - N4ST


From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Bernd - KB7AK
Sent: Wednesday, January 10, 2018 00:07
To: Support@HamApps.groups.io
Subject: [HamApps] Grid Chase - one more question

I am probably still misunderstanding something, but I was expecting that if I have worked a station on 40m before since the beginning of January, it wouldn't be marked as a needed grid (it was even the same mode. I have attached two screenshots, the first one shows WB6DJI calling CQ and it is highlighted in Purple, my color indicator for a needed grid. The CQ call is for DM03. The second screenshot shows that I worked a station from DM03 before, on this band, within this month, and that it was confirmed by LoTW.

What am I still not getting?
_._,_._,_
________________________________________


locked WSJT-X and FT-1000D

jim.kc4hw@...
 

Using WSJT-X, v1.80 and FT-1000D for Digital Modes (especially FT-8). The interface for
the CAT Control is from MFJ.

Unfortunately, the CAT Control with WSJT-X for the FT-1000D seems to be intermittent. It
will just drop out and another dialog comes up that indicates that communication has failed
and to check SETTINGS. Here are the setting for the FT-1000D in use:

CAT Contro
Serial Port COM4
Baud Rate: 4800
Data Bits: 8
Stop Bits: 2
Handshake: None
Force Control Lines:
DTR: No selection
RTS: RTS High
PTT Method: VOX
Transmit Audio Source: Front/Mic
Mode: USB

This setup seems to work with Logger 32, Writelog but is intermittent with WSJT-X.

Anyone using a FT-1000D have a solution to this intermittent CAT Control problem with
WSJT-X???

Jim/KC4HW


locked Grid Chase - one more question

Bernd - KB7AK
 

I am probably still misunderstanding something, but I was expecting that if I have worked a station on 40m before since the beginning of January, it wouldn't be marked as a needed grid (it was even the same mode. I have attached two screenshots, the first one shows WB6DJI calling CQ and it is highlighted in Purple, my color indicator for a needed grid. The CQ call is for DM03. The second screenshot shows that I worked a station from DM03 before, on this band, within this month, and that it was confirmed by LoTW.

What am I still not getting?


locked Re: JTAlert 2.10.8 I cannot get grid chase going.

HamApps Support (VK3AMA)
 

On 10/01/2018 12:04 PM, K6RC wrote:
It does not populate when I have grid only.   When I activate state or dxcc country it does populate.  I cannot get the grid chase feature to work.  I just uninstalled 2.10.8 and reinstalled it.  Same problem.  Since others seem to be able to use it I must have done something wrong.  I am using UDP  with ACLog to WSJT-x v1.8.0-rc2 and then jtalert 2.10.8
please help

73
Dave  K6RC

Dave,

Firstly, not related to the Grid alerts, your running an old pre-release beta of WSJT-X. You should be running the 1.8.0 general release. There were many changes/optimisations across the three release candidate before the final 1.8.0 release.

Regarding the Grid Chase, did you setup per the instructions in the help file, "Tutorials -> ARRL International Grid Chase 2018" topic?
Very important is the running of an initial Scan Log and then repeat at the start of each month (after first syncing ACLog with LoTW to get your LoTW confirmations into ACLog).

de Laurie VK3AMA
   


locked JTAlert 2.10.8 I cannot get grid chase going.

K6RC
 

It does not populate when I have grid only.   When I activate state or dxcc country it does populate.  I cannot get the grid chase feature to work.  I just uninstalled 2.10.8 and reinstalled it.  Same problem.  Since others seem to be able to use it I must have done something wrong.  I am using UDP  with ACLog to WSJT-x v1.8.0-rc2 and then jtalert 2.10.8
please help

73
Dave  K6RC


locked Re: Dupe grid alerts

Rich - K1HTV
 

Laurie,

  Thanks, now I understand. I do LOTW sync daily or more often and now have done JTAlert scan log and will do so more often. Having lots of fun chasing grids in the ARRL International Grid Chase. Now that I'm using JTAlert I'm better able to focus on working new grids rather than all stations seen. I see that at last look I was in 6th place of 11,000+ stations.


73,

Rich - K1HTV


= = =

On January 9, 2018 at 3:07 PM "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...> wrote:


On 10/01/2018 1:48 AM, Rich - K1HTV wrote:
Hi Laurie,
As many thousands are now doing, I'm participating in the ARRL
International Grid Chase. I just started using the JTAlert grid alert
feature, where CQing stations in a grid not yet worked on the band I'm
on, are flagged with an asterisk and the colors that I've chosen for
that type of alert.

It's been working fine but I noticed that stations in grids worked
this year, even on this date, continue to show up as not yet being
worked. I'm using DXkeeper for logging, but assume that the JTAlert
database of QSOs is being used to determine if the QSO is a dupe.
Shouldn't these stations NOT appear flagged as being needed grids?

Am I missing a setup requirement to shut off these duplicate grids?

Thanks for all of your efforts to develop and maintain this great JT8
tool.

73,
Rich - K1HTV

Rich,

A grid will continue to be alerted until it is marked as no longer
needed, that is it has been LoTW confirmed.
You need to periodically sync DXKeeper with LoTW to get the
confirmations into the log. Once DXKeeper has been updated, run a
JTAlert Scan Log to get those new confirmed grids marked as no longer
needed.

Remember the Grid Chase resets you grid totals every month, so you need
to run a JTAlert Scan Log at the start of each month. Grids confirmed in
the previous month will again be marked as needed and generate alerts.
frequent mid-moth scans are also recommended.

JTAlert doesn't automatically remove a grid from the wanted list after
working a Station, as there is no guarantee that Station will confirm
the Grid with a LoTW upload. The grid will continue to be alerted until
confirmed.

Many operators are performing the LoTW upload, Logger sync with LoTW and
JTAlert Scan Log sequence on a daily basis, some more frequently.

This is no different from the traditional alerting in JTAlert where, say
a dxcc or state, will continue to be alerted until it is marked as no
longer need in JTAlert.

de Laurie VK3AMA


locked Re: version update JTalert

K8TS
 

Thank You


locked Re: Alerting on a station calling CQ and a wanted grid.

Laurie, VK3AMA
 


On 10/01/2018 3:31 AM, K5TCJ wrote:
I’m alerting on stations calling CQ and stations in wanted grids.   
Is there a way to combine alerts, to alert on only those stations that meet more than one criteria? 
As in this case to only alert on stations calling CQ AND who are in a wanted grid?
Thanks and 73,
Tim K5TCJ
Tim,

Simple. Turn off all alert types (including CQ) except for the alerts your interested in. Then set the "Generate alerts for CQ only Callsigns" alert filter. JTAlert will then only alert (color and audio) on CQing Stations that also produce one or more of your enabled Wanted Alerts.

A quick way to turn off many alerts is to bring up the Alert Types window (F1 hotkey) and uncheck the unwanted alerts.

de Laurie VK3AMA
   


locked Re: Dupe grid alerts

HamApps Support (VK3AMA)
 

On 10/01/2018 1:48 AM, Rich - K1HTV wrote:
Hi Laurie,
  As many thousands are now doing, I'm participating in the ARRL International Grid Chase.  I just started using the JTAlert grid alert feature, where CQing stations in a grid not yet worked on the band I'm on, are flagged with an asterisk and the colors that I've chosen for that type of alert.

It's been working fine but I noticed that stations in grids worked this year, even on this date, continue to show up as not yet being worked. I'm using DXkeeper for logging, but assume that the JTAlert database of QSOs is being used to determine if the QSO is a dupe. Shouldn't these stations NOT appear flagged as being needed grids?

Am I missing a setup requirement to shut off these duplicate grids?

Thanks for all of your efforts to develop and maintain this great JT8 tool.

73,
Rich - K1HTV

Rich,

A grid will continue to be alerted until it is marked as no longer needed, that is it has been LoTW confirmed.
You need to periodically sync DXKeeper with LoTW to get the confirmations into the log. Once DXKeeper has been updated, run a JTAlert Scan Log to get those new confirmed grids marked as no longer needed.

Remember the Grid Chase resets you grid totals every month, so you need to run a JTAlert Scan Log at the start of each month. Grids confirmed in the previous month will again be marked as needed and generate alerts. frequent mid-moth scans are also recommended.

JTAlert doesn't automatically remove a grid from the wanted list after working a Station, as there is no guarantee that Station will confirm the Grid with a LoTW upload. The grid will continue to be alerted until confirmed.

Many operators are performing the LoTW upload, Logger sync with LoTW and JTAlert Scan Log sequence on a daily basis, some more frequently.

This is no different from the traditional alerting in JTAlert where, say a dxcc or state, will continue to be alerted until it is marked as no longer need in JTAlert.

de Laurie VK3AMA
   


locked Re: Hamspots is back

HamApps Support (VK3AMA)
 

On 9/01/2018 6:48 PM, on5po wrote:
Hello Laurie,
My problem is that twice the three bands FT8, are empty, impossible to have the spots, the next day it works.
I'm well connected, I do not understand why, that's why, I'm pointing it out
it is possible that it comes from my instalation, but why?

73 de on5po, Janny
Janny,

The Band spots were temporarily disabled while an excessive load event was occurring on the Server, which has now been resolved. The Band spots displays have been working for a couple of days now.

de Laurie VK3AMA
   


locked Re: 9 JTDX decodes and JTAlert shows only 5

HamApps Support (VK3AMA)
 

On 10/01/2018 6:39 AM, kk5aa_fred via Groups.Io wrote:
Already sent you my files (contact support). This is happening to both JTDX and to WSJT-X. 

Fred - KK5AA
Fred,

Turn off your JTAlert Alert filters (note the "F" in the titlebar). You have the eQSL filter set so only Callsigns that are known eQSL(AG) members will have their callsigns shown in JTAlert.

de Laurie VK3AMA
   


locked 9 JTDX decodes and JTAlert shows only 5

kk5aa_fred
 

Already sent you my files (contact support). This is happening to both JTDX and to WSJT-X. 

Fred - KK5AA


locked Re: Alerting on a station calling CQ and a wanted grid.

JohnB
 

I alert on three criteria: 1) CQ, 2) LoTW Member, 3) Wanted Grid.

I see if all three criteria are met at the same time by setting up JTAlert as follows:

1. For CQ, I turn off "Enable CQ and QRZ Alert", and turn on "Show border around Callsign - Show All CQs". I also turn on "Show Directional CQs".  

2. For LoTW, I turn on "Enable LoTW Strip/Flag.

3. For Wanted Grid, I turn on "Enable ARRL 2018 Grid Chase" (salmon color). I also change the Alert Priority so that Wanted Grid is at the top.

Now when a station calls CQ, and is a LoTW member, and is in a wanted grid, I see a Salmon filled box, with a green border, and a LoTW Strip/Flag.

. . . John (WA3CAS)

19421 - 19440 of 37715