Date   

locked Re: Special callsigns

Jim Cooper
 

On 7 Jun 2020 at 18:04, Tom Melvin wrote:

Might be a PITA to program - you
mention 1 x 1 but if the Prefix is 2
characters e.g. GM then it fails -
so GM2T which is a special
event/contest callsign you would
want to apply the same. Are ALL 1 x 1
callsigns special events - would be
a problem if genuine call was treated
like that. You mention a pull-down
to set expiration - are people going
to use that on a per QSO basis or
were you thinking of having a global
setting for all 1x1, 2x1 etc.
tom ...

unlike most other countries these days,
it seems, the USA allows ONLY one kind
of 'special event' call sign ... a 1x1 such
as W2A .... NOBODY else gets a 1x1 call
sign for a regular license.

The point the poster is getting at is that
these 1x1 USA special event call signs are
ROTATED on a weekly, or at most a few
weeks, at a time and then issued for some
other special event. So you work W2E
this week, and next week it is for a totally
different special event -- that you probably
want to work again. (Causes a real PITA for
the QSL managers for the special events too,
as they are always getting cards for the wrong
event with the same call sign). Not the brightest
idea of our licensing commission ...

w2jc


locked Re: Special callsigns

Michael Black
 

There are 750 special event callsigns in U.S.  I haven't looked up foreign ones.

The point here to get JTAlert to recognize these as need-to-be-worked since they expire so quickly.

A regular expression detects them.

"[WKN][0-9][A-WYZ]"

And this to detect one with a suffix.
"[WKN][0-9][A-WYZ]/"

Mike W9MDB




On Sunday, June 7, 2020, 12:10:28 PM CDT, Tom Melvin <tom@...> wrote:


Hi

Might be a PITA to program - you mention 1 x 1 but if the Prefix is 2 characters e.g.  GM  then it fails - so GM2T which is a special event/contest callsign you would want to apply the same.  Are ALL 1 x 1 callsigns special events - would be a problem if genuine call was treated like that.  You mention a pull-down to set expiration - are people going to use that on a per QSO basis or were you thinking of having a global setting for all 1x1, 2x1 etc.

Tom

--
73

Tom
GM8MJV (IO85)





On 7 Jun 2020, at 16:20, Michael Black via groups.io <mdblack98@...> wrote:

Laurie -- I noticed that the special event 1x1 callsigns should be handled a bit differently.

Probably something like having an expiration time on B4 detection.  Since these things are only good for a short while and the events change constantly.
So having a pull down with maybe a 30-day default for B4 detection would work.

So those that want to work these don't ever get alerted a 2nd time for any specific call once you work any particular one.

Opinion?

Mike




locked Re: I need more callsign display real estate please

Jim N6VH
 


On 6/7/2020 9:04 AM, Guy G4DWV 4X1LT wrote:
Hi,

Is there any way I can display more callsigns? I have 4 rows and 9 per row and it seems that I am still missing a lot.
--
73 de Guy G4DWV 4X1LT
_._,_._,_


Guy,

This might work for you. If you haven't already done so, in Settings/Filters, check "Show CQ only Callsigns" and "Do not show Worked Before (B4) Callsigns".

73,

Jim N6VH


locked Re: Special callsigns

Tom Melvin
 

Hi

Might be a PITA to program - you mention 1 x 1 but if the Prefix is 2 characters e.g.  GM  then it fails - so GM2T which is a special event/contest callsign you would want to apply the same.  Are ALL 1 x 1 callsigns special events - would be a problem if genuine call was treated like that.  You mention a pull-down to set expiration - are people going to use that on a per QSO basis or were you thinking of having a global setting for all 1x1, 2x1 etc.

Tom

--
73

Tom
GM8MJV (IO85)





On 7 Jun 2020, at 16:20, Michael Black via groups.io <mdblack98@...> wrote:

Laurie -- I noticed that the special event 1x1 callsigns should be handled a bit differently.

Probably something like having an expiration time on B4 detection.  Since these things are only good for a short while and the events change constantly.
So having a pull down with maybe a 30-day default for B4 detection would work.

So those that want to work these don't ever get alerted a 2nd time for any specific call once you work any particular one.

Opinion?

Mike




locked Re: I need more callsign display real estate please

Jim Cooper
 

On 7 Jun 2020 at 9:04, Guy G4DWV 4X1LT wrote:

Is there any way I can display more
callsigns? I have 4 rows and 9 per row
and it seems that I am still missing
a lot. -- 73 de Guy G4DWV 4X1LT
use the Decodes History window ... it will
list everything vertically and you can click
in it to select a target call, etc. Plus it
shows you a bunch of info about the station.

Try it, you will like it !!

w2jc


locked I need more callsign display real estate please

Guy G4DWV 4X1LT
 

Hi,

Is there any way I can display more callsigns? I have 4 rows and 9 per row and it seems that I am still missing a lot.
--
73 de Guy G4DWV 4X1LT


locked Special callsigns

Michael Black
 

Laurie -- I noticed that the special event 1x1 callsigns should be handled a bit differently.

Probably something like having an expiration time on B4 detection.  Since these things are only good for a short while and the events change constantly.
So having a pull down with maybe a 30-day default for B4 detection would work.

So those that want to work these don't ever get alerted a 2nd time for any specific call once you work any particular one.

Opinion?

Mike



locked Re: JT Alert and N3fjp Field Day logging

Greg Yates
 

Steve,

 

Thank you very much.  That is exactly the information I was looking for.  I thought the info had to come from the other station.  I did what you said and it works perfectly.

 

It’s the little things and I am not a computer expert.

 

Thanks again,

 

Greg, WB2BIN

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of AI3KS
Sent: Sunday, June 7, 2020 7:54 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JT Alert and N3fjp Field Day logging

 

Greg,

Be sure that N3FJP FD Logger has the API enabled.
Configure both WSJT-X and JTAlert for Field Day.
In WSJT-X enter a call in the DX CAll window.
Click Log QSO
In the QSO entry window fill in both the exchanges (1E EPA) and click OK.
The QSO should log in N3FJP FD Logger.

Hope that helps.

Steve, AI3KS


locked Re: JT Alert and N3fjp Field Day logging

AI3KS
 

Greg,

Be sure that N3FJP FD Logger has the API enabled.
Configure both WSJT-X and JTAlert for Field Day.
In WSJT-X enter a call in the DX CAll window.
Click Log QSO
In the QSO entry window fill in both the exchanges (1E EPA) and click OK.
The QSO should log in N3FJP FD Logger.

Hope that helps.

Steve, AI3KS


locked Re: JTAlerts Error Message When Starting WSJT-X With Slicemaster

HamApps Support (VK3AMA)
 

On 7/06/2020 3:17 pm, pfullmer wrote:
     I'm running a Flex 6400 and use Slicemaster to start WSJT-X, CW Skimmer and to push spots to the radio.  When I start JTAlerts, its throwing an error message now that says "Line 7587 (File C:Program Files (x86)\HamApps\JTAlert\JTAlert_AL.exe"):   Error: Subscript used on non-accessible variable"

     I've searched the forums here and found a thread from about a year ago with similar issues from Flex and Slicemaster users,  https://hamapps.groups.io/g/Support/topic/31813423#24261  .  Was there ever a fix/diagnosis found for this issue.  Running the most current versions of WSJT-X, JTAlerts, Slicemaster and Flex SSDR.   Thanks for any help or suggestions.  I've sent an email to the Slicemaster author asking the question also.  Thanks in advance.

Pete KE7W

I am not very familiar with the Flex, what does slicemaster actually do, what is its purpose and how does JTAlert work with it?

You stated your running the most current version of JTAlert, that cannot be the case, the quoted executable name "JTAlert_AL.exe" does not exist in recent JTAlert releases, only "JTAlert.exe". Try updating your JTAlert version to the latest 2.16.6 and if that still does not work, please describe how your starting JTAlert and WSJT-X.

de Laurie VK3AMA


locked JTAlerts Error Message When Starting WSJT-X With Slicemaster

pfullmer
 

     I'm running a Flex 6400 and use Slicemaster to start WSJT-X, CW Skimmer and to push spots to the radio.  When I start JTAlerts, its throwing an error message now that says "Line 7587 (File C:Program Files (x86)\HamApps\JTAlert\JTAlert_AL.exe"):   Error: Subscript used on non-accessible variable"

     I've searched the forums here and found a thread from about a year ago with similar issues from Flex and Slicemaster users,  https://hamapps.groups.io/g/Support/topic/31813423#24261  .  Was there ever a fix/diagnosis found for this issue.  Running the most current versions of WSJT-X, JTAlerts, Slicemaster and Flex SSDR.   Thanks for any help or suggestions.  I've sent an email to the Slicemaster author asking the question also.  Thanks in advance.

Pete KE7W
 


locked Re: JT Alert and N3fjp Field Day logging

Greg Yates
 

I was using Field Day  Log and I think it is set up properly but HOW DO I TEST to make sure.  I have not found a way.  Please tell  me.

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Saturday, June 6, 2020 7:45 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JT Alert and N3fjp Field Day logging

 

On 7/06/2020 9:29 am, Greg Yates via groups.io wrote:

I am sure someone is going to use the above.  I have it installed I think.  I can’t think of a way to test if it logs to N3fjp.  I have tried to log a contact but says it is wrong exchange and it is but how do you test it before Field Day?

 

I asked this question on the N3fjp forum but did not get an answer and not really sure this is the forum but you never know until you ask.

 

Thanks for any help.

 

Greg

WB2BIN

When I test FD with ACLog I manually entered the correct exchanges in the WSJT-X Log QSO window. WSJT-X has to be running in ARRL FD mode and JTAlert has been setup correctly to work with the N3FJP FD Contest logger (you can't use ACLog).

Proper setup of JTAlert and N3FJP is in the JTAlert help file (with pictures), it is a simple operation.
See the "Tutorials -> N3FJP Contest Logs Logging" Help topic.

de Laurie VK3AMA


locked Re: Transferring to a New Computer

Dave Corio
 

Thanks, Laurie. I searched the forum but failed to check the help file. (Should have been the first place I looked!)_

73
Dave - K1DJE


On 6/6/2020 7:25 PM, HamApps Support (VK3AMA) wrote:
On 7/06/2020 9:07 am, Dave Corio via groups.io wrote:
I realize when I set up the new (to me) PC that I will need to install the JTAlert program, Call Sign Database, and Sounds files, but could I copy over the C:\Users\Doc\AppData\Local\HamApps directories an files? Would sure be a time saver, and I archive them daily.

I plan to install the latest release version until I know the system is stable before I try a new beta.

Tnx es 73
Dave - K1DJE
�
The Help file is your friend.
See the "Frequently Asked Questions -> Move JTAlert to a New PC" topic.

de Laurie VK3AMA



locked Re: JT Alert and N3fjp Field Day logging

HamApps Support (VK3AMA)
 

On 7/06/2020 9:45 am, HamApps Support (VK3AMA) via groups.io wrote:
When I test FD with ACLog

Sorry, that should read "When I test FD with N3FJP FD Contest Log".

de Laurie VK3AMA



 


locked Re: JT Alert and N3fjp Field Day logging

HamApps Support (VK3AMA)
 

On 7/06/2020 9:29 am, Greg Yates via groups.io wrote:

I am sure someone is going to use the above.  I have it installed I think.  I can’t think of a way to test if it logs to N3fjp.  I have tried to log a contact but says it is wrong exchange and it is but how do you test it before Field Day?

 

I asked this question on the N3fjp forum but did not get an answer and not really sure this is the forum but you never know until you ask.

 

Thanks for any help.

 

Greg

WB2BIN

When I test FD with ACLog I manually entered the correct exchanges in the WSJT-X Log QSO window. WSJT-X has to be running in ARRL FD mode and JTAlert has been setup correctly to work with the N3FJP FD Contest logger (you can't use ACLog).

Proper setup of JTAlert and N3FJP is in the JTAlert help file (with pictures), it is a simple operation.
See the "Tutorials -> N3FJP Contest Logs Logging" Help topic.

de Laurie VK3AMA


locked JT Alert and N3fjp Field Day logging

Greg Yates
 

I am sure someone is going to use the above.  I have it installed I think.  I can’t think of a way to test if it logs to N3fjp.  I have tried to log a contact but says it is wrong exchange and it is but how do you test it before Field Day?

 

I asked this question on the N3fjp forum but did not get an answer and not really sure this is the forum but you never know until you ask.

 

Thanks for any help.

 

Greg

WB2BIN


locked Re: Transferring to a New Computer

HamApps Support (VK3AMA)
 

On 7/06/2020 9:07 am, Dave Corio via groups.io wrote:
I realize when I set up the new (to me) PC that I will need to install the JTAlert program, Call Sign Database, and Sounds files, but could I copy over the C:\Users\Doc\AppData\Local\HamApps directories an files? Would sure be a time saver, and I archive them daily.

I plan to install the latest release version until I know the system is stable before I try a new beta.

Tnx es 73
Dave - K1DJE
 
The Help file is your friend.
See the "Frequently Asked Questions -> Move JTAlert to a New PC" topic.

de Laurie VK3AMA


locked Transferring to a New Computer

Dave Corio
 

I realize when I set up the new (to me) PC that I will need to install the JTAlert program, Call Sign Database, and Sounds files, but could I copy over the C:\Users\Doc\AppData\Local\HamApps directories an files? Would sure be a time saver, and I archive them daily.

I plan to install the latest release version until I know the system is stable before I try a new beta.

Tnx es 73
Dave - K1DJE


locked Re: African Italy, European Turkey and ITU Vienna. #FT8

Joe Subich, W4TV
 

I can make it easier for you. Please let me know which DXCC code is
used for each of the WAE entities as you see below:
ADIF "DXCC Codes" *DO NOT IDENTIFY WAE ENTITIES* They were never
intended to do so. Applications must identify WAE Entities by
CALLSIGN (e.g., IT9, 4U1VIC, etc.) or by an override in AD1C's
CTY files.

73,

... Joe, W4TV


On 2020-06-06 5:32 PM, asobel@... wrote:
Laurie
I can make it easier for you. Please let me know which DXCC code is used for
each of the WAE entities as you see below:
This list of separate countries (entities) for the CQ World Wide DX Contest
and the CQ DX Marathon is based on a combination of the ARRL DXCC list,
additional entities on the WAE (Worked All Europe) list and the Italian
islands
of Lampedusa (IG9) & Pantelleria (IH9), in CQ Zone 33 off the coast of North
Africa.
This provides a total of 346 entities, based on 340 DXCC entities, five
additional
WAE entities (GM/Shetland, IT/Sicily, TA1/European Turkey, 4U1VIC, JW/Bear
Is.)
plus African Italy.
Amos 4X4MF


locked Re: Question on audio alert options by band

Tom Melvin
 

Comments all fine Hasan

I do know there a quite a few Scottish stations (MMxyyyy) are very active on 6m Es - while we are slightly further north so I suspect when 6M opens to USA you will get the G’s to the south, that will be enough to trip your alert, by the time it reaches us you are well aware there is opening.   

So your G% will work well and for any others wanting to set something similar

Regards

Tom
GM8MJV

On 6 Jun 2020, at 23:04, Hasan Schiers N0AN <hbasri.schiers6@...> wrote:

Laurie and Tom:

Keep in mind that goal was 6 meter ALERT for DX outside USA/CANADA. 

The approach was based on Laurie's warning not to overload the Misc. Alert file. So my thinking was:

How often on 6m have I seen no G prefix, but have seen M prefix? For me, it's been nearly never. So G is used to take advantage of GM,GW, etc. So if 6m is open to EU, (UK), then I'm highly likely to see G.

If this approach is used all over the world, then selecting a few populated DX prefixes should catch many if not most band openings on 6m.

It was Laurie's warning that kept me from going too far and just get the biggest areas covered. I read that warning and took it to heart.

I have been watching the effects of the Misc Alert file I'm using and it has had virtually no impact on 6 meters, even during a pretty good opening, because the number of decodes per sequence is maybe 15 or 20 when things are just wild....but on 20 meters, it is easy to get > 30 decode per sequence and while this didn't cause any untoward symptoms, I could see a dramatic increase in CPU utilization at the end of the decode periods. I was seeing up to 75% CPU utilization on 20m, but no more than 15-25% on 6m when 6 was busy.

Of course, part of that load is from X itself!

Core I5, 3 GHz, 8 gB RAM, Win10Pro, Latest X 2.2.1, and a full DXLabSuite running along with 4 Browser tabs and a few other utilities.

Running latest Beta JTA atm.

I have gotten 3 new DXCC on 6 meters in the last 10 days and have been alerted to KL7HBK twice, but was not able to catch him in time, as it was a peek-a-boo opening that was one and done.

Misc Alerts are fantastic for 6 meters.

73, N0AN
Hasan


On Sat, Jun 6, 2020 at 4:26 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 7/06/2020 6:54 am, Tom Melvin wrote:
Remember to add M% for UK as well 

Just make sure you don't go crazy with the number of wildcards.
From the "Wanted Callsign" topic in the help file...
Important : Wildcard matching is an expensive task, processing wise, and can lead to delays in decode alerting if there are many wildcards defined, especially if there are many decodes to process on a busy band. It is recommended that the number of wildcard filters be kept to a minimum, preferably less than 20.

The above was written when the Bands were not so busy and the number of decodes per period produced by WSJT-X was less than the now normal. 20 may now be too high depending on the Bands used and the capability of the PC running a JTAlert.

de Laurie VK3AMA