Date   

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

K1DJE - 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

K1DJE - 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@netvision.net.il 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






locked Re: Question on audio alert options by band

Hasan Schiers N0AN
 

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



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

asobel@...
 

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

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Saturday, June 6, 2020 11:22 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] African Italy, European Turkey and ITU Vienna. #FT8

 

On 6/06/2020 9:18 pm, asobel@... wrote:

My JTAlert 2.16.6 Wanted CQ Marathon is showing I did work WAE African Italy, WAE European Turkey and ITU Vienna. I could not identify any QSO with African Italy, Lampedusa, Pantelleria and ITU Vienna (4U1VIC). I did identifiy 2 QSOs with European Turkey (TC1) but those did belong to "Turkey".
Were are the missing QSOs hidden? I an using WSJT-X and HRD.


I have no way of knowing what Callsigns in your log JTAlert flagged as WAE. They may be callsigns with an WAE override in the cty.dat file JTAlert that are not normally WAE due to their callsign structure.

The only way I could identify the Callsigns would be if I had access to your HRD log file. Since I don't have access to a working copy of HRD I would need to use an ADIF export from your log. Please send an ADIF export file (zipped up) to me directly, NOT via this group.

de Laurie VK3AMA


locked Re: Question on audio alert options by band

HamApps Support (VK3AMA)
 

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



locked Re: Question on audio alert options by band

Tom Melvin
 

Hassan

Remember to add M% for UK as well 

Tom

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

I do exactly that for 6 meters vs. HF. I have a Miscellaneous Alerts file using the wildcard matching symbol "%"  

Since I want to know if 6m is open for virtually any DX, I use a lot of single letter matching, for example:

8% Barbados and Maldive Islands etc.
9%  covers 9A and  9N as well as others like 9Y and 9Z
J% covers Japan and J68
C% covers Cuba, Chile , Bahamas. Etc.
D% covers Germany and Cape Verde and Philipines etc
G% covers UK etc
P% covers Brazil, Brazil, Netherlands
S% covers Croatia, Sweden, Poland, Western Sahara
KH% for Hawaii and Pacific
KL% for Alaska (still needed on 6m)
VK%
Z% Albania,   New Zealand, Gibraltar,  etc


These can be placed in a text file, single line separated by commas and imported with one button press:

C%,D%,G%  and so on

The goal was to be alerted by every area except USA and Canada if heard on 6 meters.

Use on HF to test your filter entries, then keep off (uncheck enable in miscellaneous filters). When you want 6m alerts for any DX,  just check the enable box.

73, N0AN 

Hasan

On Fri, Jun 5, 2020, 3:14 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 6/06/2020 4:07 am, Paul AC9O wrote:
I think I know the answer, but will ask anyway.

Is there any way to select audio alerts by band?

I have audio alerts for DXCC, Zone, Continent, etc on all bands. Also have alerts turned on for Prefix, Grid on all bands.

Audio grid alerts on HF bands would be fairly constant and annoying. I prefer just to see the alert color.

However, on VHF, I would like to hear alerts, especially if I am away from the desk. But I can't find any settings by band for audio.

Not a big deal, but can always hope!

Thanks for all the great work! 

73
Paul, AC9O

Simplest solution is to click the "Sound" menu to "Sound OFF" to mute the sounds when on HF and turn them back on when on VHF.

If your running multiple JTAlert instances, say one on HF and one on VHF, then turn the Sounds off (via the main window menu) on the HF instance and leave the Sounds on for the VHF instance.

There is also the opinion to restrict Alert sounds to specific UTC hours.

de Laurie VK3AMA





locked Re: Maunally updat GRID squares #JTDX

HamApps Support (VK3AMA)
 

On 7/06/2020 6:33 am, HamApps Support (VK3AMA) via groups.io wrote:
will need to get a copy of your Log (send a zipped copy to me direct) and a note of some of the Grids that are not being detected by the JTAlert scan.

Don't send your actual log file, just a zipped ADIF export along with a note of a couple of Grids that are not being picked up during the Scan.

de Laurie VK3AMA


locked Re: Maunally updat GRID squares #JTDX

HamApps Support (VK3AMA)
 

On 7/06/2020 1:17 am, Danny Van Tricht ON4VT wrote:
Is it possible to manually edit the list of work grids ?  So far I cannot change it (I did a Log scan but not ALL worked grids are in my alert list!)

73 Danny ON4VT

It is not possible to manually add Grids to the "Not Needed Lists" a Scan Log is the only way.

If you have Grids in your log that JTAlert appears not to be picking up on the Scan, the cause will be that the Band/Mode/QSLConfirmation status of those missing Grids are not matching what you have set for the Alert Band/Mode tracking and/or the QSL confirmation for the Scan.

I suggest you take a closer look at the Log entry of one of those missing Grids and double-check that it is for the correct Band & Mode and if you have QSL confirmations set for the Scan that the entry has the required QSL flags.

If you can't identify wrong Log entries I will need to get a copy of your Log (send a zipped copy to me direct) and a note of some of the Grids that are not being detected by the JTAlert scan.

de Laurie VK3AMA


locked Re: settings

HamApps Support (VK3AMA)
 

On 7/06/2020 4:18 am, tom harmon wrote:
I want to work different countries only. In JTAlert under settings -alert- what do I choose? Thanks 

"Wanted DXCC" is for Country alerts.

de Laurie VK3AMA


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

HamApps Support (VK3AMA)
 

On 6/06/2020 9:18 pm, asobel@... wrote:
My JTAlert 2.16.6 Wanted CQ Marathon is showing I did work WAE African Italy, WAE European Turkey and ITU Vienna. I could not identify any QSO with African Italy, Lampedusa, Pantelleria and ITU Vienna (4U1VIC). I did identifiy 2 QSOs with European Turkey (TC1) but those did belong to "Turkey".
Were are the missing QSOs hidden? I an using WSJT-X and HRD.

I have no way of knowing what Callsigns in your log JTAlert flagged as WAE. They may be callsigns with an WAE override in the cty.dat file JTAlert that are not normally WAE due to their callsign structure.

The only way I could identify the Callsigns would be if I had access to your HRD log file. Since I don't have access to a working copy of HRD I would need to use an ADIF export from your log. Please send an ADIF export file (zipped up) to me directly, NOT via this group.

de Laurie VK3AMA


locked Re: Missing visual alerts on WSJT-X display #FT8

HamApps Support (VK3AMA)
 

On 7/06/2020 6:03 am, asobel@... wrote:
As you can see on the attached picture, GJ0KYZ is sometime in violet and sometime white. It happens quite often: voice alert comes without the visual alert.
Please take care of this problem.

Amos 4X4MF

The missing decode coloring is due to a defect in WSJT-X 2.2.0, it is triggered by a "+" symbol in the decode message.
This was reported 5 days ago to this group in this message https://hamapps.groups.io/g/Support/message/30069

WSJT-X 2.2.1 has just been release and its release notes indicate that this defect is fixed. I suggest you try that version.

de Laurie VK3AMA


6921 - 6940 of 36910