Date   

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



locked Missing visual alerts on WSJT-X display #FT8

asobel@...
 
Edited

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


locked settings

tom harmon <goldiev316@...>
 

I want to work different countries only. In JTAlert under settings -alert- what do I choose? Thanks 


locked Maunally updat GRID squares #JTDX

Danny Van Tricht ON4VT <on4vt@...>
 

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


locked Re: JT Alert V 2.16.6 Program quits

Michael Black
 

That's a Window's sound and not configurable as far as I know.   Might be nice to be able to turn that off.

Mike W9MDB




On Saturday, June 6, 2020, 08:55:35 AM CDT, Bill Hicks <smoke744@...> wrote:


Another funny thing is the logged qso confirmation pop up still makes a noise with no issues.


 Bill

 


 


On Jun 6, 2020, at 6:21 AM, Bill Hicks <smoke744@...> wrote:

 Laurie,

I have turned off all alerts and it will run just fine.  I will keep trying various things and let you know if I am able to figure out any combination that works. 

Is there a error log on my computer for the protection software you mention that I could glean some insight from? 

I have two version installed in different folders but I have had that before with no issues. 

The program is absolutely great and makes the mode very enjoyable. Thank you for all your hard work on it. 


 Bill

 


 


On Jun 5, 2020, at 9:44 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 6/06/2020 8:25 am

I have a windows 10 enterprise 64 bit system running wsjtx 2.2.0 with jt alert 2.16.6.  Jt alert keeps cutting out every so often with the program just closing on its own.  Any thoughts?  It is cutting out when I get the calling you message meaning a station responds and it it immediately crashes. It’s not RF as I can call all I want.  


Sorry OM,

I have no idea what is happening your end. If there is a problem playing sound, the only process that should be affected is the JTALertV2.Manager.exe process, it is responsible for all audio output. If the Manager process crashes or is forced closed, JTAlert will detect that and automatically start a new process. With the main JTAlert executable closing without any prior error indication suggests to me that your PC protection software is likely interfering with it running and force closing JTAlert.

de Laurie VK3AMA



locked Re: JT Alert V 2.16.6 Program quits

Bill Hicks
 

Another funny thing is the logged qso confirmation pop up still makes a noise with no issues.


 Bill

 


 


On Jun 6, 2020, at 6:21 AM, Bill Hicks <smoke744@...> wrote:

Laurie,

I have turned off all alerts and it will run just fine.  I will keep trying various things and let you know if I am able to figure out any combination that works. 

Is there a error log on my computer for the protection software you mention that I could glean some insight from? 

I have two version installed in different folders but I have had that before with no issues. 

The program is absolutely great and makes the mode very enjoyable. Thank you for all your hard work on it. 


 Bill

 


 


On Jun 5, 2020, at 9:44 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 6/06/2020 8:25 am

I have a windows 10 enterprise 64 bit system running wsjtx 2.2.0 with jt alert 2.16.6.  Jt alert keeps cutting out every so often with the program just closing on its own.  Any thoughts?  It is cutting out when I get the calling you message meaning a station responds and it it immediately crashes. It’s not RF as I can call all I want.  


Sorry OM,

I have no idea what is happening your end. If there is a problem playing sound, the only process that should be affected is the JTALertV2.Manager.exe process, it is responsible for all audio output. If the Manager process crashes or is forced closed, JTAlert will detect that and automatically start a new process. With the main JTAlert executable closing without any prior error indication suggests to me that your PC protection software is likely interfering with it running and force closing JTAlert.

de Laurie VK3AMA



locked Re: JTAlert does strangle my computer again and again / Final / Not Final

asobel@...
 

Larry
The problem on which I did complain 2 month ago does still exist
Few times a day, one of my 4 JTAlert instances does crash and I have to restart it.
My win10, WSJT-X, JTAlert and HRD are up to date, y computer's memory was increased from 8GB to 24GB, Memory tests OK.
Please help

Amos 4X4MF


locked Re: wsjtx rig setting when using jtalert

neil_zampella
 

Norm,

If you used HRD to control the rig before, continue to do so.   Just turn OFF the ACLog settings that have it access CAT control.   GIving it access is usually fine when using other digital and non-digital modes, but you want WSJT-X to have CAT control so it can utilize the rig SPLIT settings, as well as set the band and frequency changes .

As far as setting up ACLog with JT-Alert it is as simple as going into settings, under the LOGGING section, selecting the ACLog page, and turning on the "Enable ACLog Logging", make sure that the 'Local PC' radio button is checked, and then JT-Alert should be ready to go.   You may have to close and restart JT-Alert so it can read the ACLog configuration to pick up the location of your log files, but that's about it.

I don't use ACLog but based on other users who do, it is a snap to setup.

Neil, KN3ILZ


On Fri, Jun 5, 2020 at 10:24 PM, Norm wrote:

Icom7600. Win 10 64. Want to connect Wsjtx to ACL. I don’t know how to tell Jr alert to report to ACL.  And does ACL still control the rig?
I’m accustomed to using HRD with WSJT.  Where HRD is set as the rig. 
Thanks for any help. 
 
toggle quoted messageShow quoted text

 

On Fri, Jun 5, 2020 at 10:03 PM Dave Garber <ve3wej@...> wrote:
What rig do you have

sent by my LG phone

On Fri, Jun 5, 2020, 9:47 PM Norm, <norman@...> wrote:
aclog wsjtx using jtalert as interface
What rig do I select.  in wsjtx.

 

 

--
..Norm


locked Re: Callsign Display Decays

neil_zampella
 

Bob,

1.   you've just turned off the switch that lets sends informatoni to PSK Reporter to let other stations know you can hear them, and what signal report is calculated at your location.   This often helps other operators know how they're doing, and what the propagation is like.

2.   You don't have access to the FT4 mode, which is the faster contesting mode introduced in v2.1.x.   Also, the FT8 protocol was moved to GMSK modulation which is backwards compatible, but has improved the mode in many ways.

As Laurie says, you are showing issues that have been fixed in both WSJT-X and JT-Alert.    Finally, the new version of WSJT-X has come out that has a much improved FT8 decoder with a three pass system that has improved sensitivity tremendously.  Users are decoding signals now that were normally left under the noise floor.

I realize its up to you what you want to do, but you're shortchanging yourself on this, and we just wanted to point that out.

Neil, KN3ILZ


On Fri, Jun 5, 2020 at 07:14 PM, Bob Craig wrote:

Thank you all.

 

I found the PSKReporter switch and turned it off.

I also reverted to JTAlert 2.12.8 which is once again working just fine with the updated Callsign database which is all I really wanted to do in the first place.

 

Sorry for the trouble.


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

asobel@...
 

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.

Amos 4X4MF


locked Re: JT Alert V 2.16.6 Program quits

Bill Hicks
 

Laurie,

I have turned off all alerts and it will run just fine.  I will keep trying various things and let you know if I am able to figure out any combination that works. 

Is there a error log on my computer for the protection software you mention that I could glean some insight from? 

I have two version installed in different folders but I have had that before with no issues. 

The program is absolutely great and makes the mode very enjoyable. Thank you for all your hard work on it. 


 Bill

 


 


On Jun 5, 2020, at 9:44 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 6/06/2020 8:25 am

I have a windows 10 enterprise 64 bit system running wsjtx 2.2.0 with jt alert 2.16.6.  Jt alert keeps cutting out every so often with the program just closing on its own.  Any thoughts?  It is cutting out when I get the calling you message meaning a station responds and it it immediately crashes. It’s not RF as I can call all I want.  


Sorry OM,

I have no idea what is happening your end. If there is a problem playing sound, the only process that should be affected is the JTALertV2.Manager.exe process, it is responsible for all audio output. If the Manager process crashes or is forced closed, JTAlert will detect that and automatically start a new process. With the main JTAlert executable closing without any prior error indication suggests to me that your PC protection software is likely interfering with it running and force closing JTAlert.

de Laurie VK3AMA



locked Re: wsjtx rig setting when using jtalert

 

Icom7600. Win 10 64. Want to connect Wsjtx to ACL. I don’t know how to tell Jr alert to report to ACL.  And does ACL still control the rig?
I’m accustomed to using HRD with WSJT.  Where HRD is set as the rig. 
Thanks for any help. 

On Fri, Jun 5, 2020 at 10:03 PM Dave Garber <ve3wej@...> wrote:
What rig do you have

sent by my LG phone

On Fri, Jun 5, 2020, 9:47 PM Norm, <norman@...> wrote:
aclog wsjtx using jtalert as interface
What rig do I select.  in wsjtx.

--
..Norm


locked Re: JT Alert V 2.16.6 Program quits

John L. Broughton
 



On 6/5/2020 6:44 PM, HamApps Support (VK3AMA) wrote:
On 6/06/2020 8:25 am

I have a windows 10 enterprise 64 bit system running wsjtx 2.2.0 with jt alert 2.16.6.  Jt alert keeps cutting out every so often with the program just closing on its own.  Any thoughts?  It is cutting out when I get the calling you message meaning a station responds and it it immediately crashes. It’s not RF as I can call all I want.  


Sorry OM,

I have no idea what is happening your end. If there is a problem playing sound, the only process that should be affected is the JTALertV2.Manager.exe process, it is responsible for all audio output. If the Manager process crashes or is forced closed, JTAlert will detect that and automatically start a new process. With the main JTAlert executable closing without any prior error indication suggests to me that your PC protection software is likely interfering with it running and force closing JTAlert.

de Laurie VK3AMA

I'm running JTAlert 2.16.6 and just upgraded WSJT-X to 2.2.0 today and am running Windows 10.

I have seen JTAlert close all by itself a very few times. I just restart it and all is well. I also have had the sound quit even though it is turned on. That happens rather infrequently. Closing and reopening the program solves that problem.

I just chalk these thing up to software glitches. They don't occur often enough to be a real problem for me.

73,

John, WB9VGJ


locked Re: wsjtx rig setting when using jtalert

Dave Garber
 

What rig do you have

sent by my LG phone

On Fri, Jun 5, 2020, 9:47 PM Norm, <norman@...> wrote:
aclog wsjtx using jtalert as interface
What rig do I select.  in wsjtx.


locked Re: WSJTX, JTAlert, and DXKeeper Integration

JT Croteau <jt.tobit@...>
 

Sorry to waste your time Laurie, I'm a loser.

On Fri, Jun 5, 2020 at 8:51 PM HamApps Support (VK3AMA)
<vk3ama.ham.apps@gmail.com> wrote:

On 6/06/2020 8:15 am, JT Croteau wrote:

Not sure where the issue is with this.

WSJTX 2.2.0, JTAlert 2.16.6, all DXLab apps at current versions. This
also occurred with prior releases. As I am making more and more QSOs
per day, it is becoming quite annoying.

7 times out of 10, all QSOs are reported and logged fine.

However, sometimes, I get a JTAlert pop up, after clicking ok on
WSJT's log window, saying DXKeeper cannot confirm the QSO and it
wasn't logged. However, DXKeeper still logs it fine.

It all seems to work fine but it's a mere annoyance by having me
clicking on another box when this happens.

Thoughts?

Thanks
N1ESE


Common problem that has become more frequent as Loggers start performing multiple online-tasks (upload to online logs, xml lookups, etc) when logging a QSO.

There is a dedicated section in the Help File "Frequently Asked Questions - Warning about QSO not logged when it is logged" topic that tells you what setting in JTAlert to adjust.

de Laurie VK3AMA




locked Re: WSJTX, JTAlert, and DXKeeper Integration

HamApps Support (VK3AMA)
 

On 6/06/2020 8:15 am, JT Croteau wrote:
Not sure where the issue is with this.

WSJTX 2.2.0, JTAlert 2.16.6, all DXLab apps at current versions.  This
also occurred with prior releases.  As I am making more and more QSOs
per day, it is becoming quite annoying.

7 times out of 10, all QSOs are reported and logged fine.

However, sometimes, I get a JTAlert pop up, after clicking ok on
WSJT's log window, saying DXKeeper cannot confirm the QSO and it
wasn't logged.  However, DXKeeper still logs it fine.

It all seems to work fine but it's a mere annoyance by having me
clicking on another box when this happens.

Thoughts?

Thanks
N1ESE

Common problem that has become more frequent as Loggers start performing multiple online-tasks (upload to online logs, xml lookups, etc) when logging a QSO.

There is a dedicated section in the Help File "Frequently Asked Questions - Warning about QSO not logged when it is logged" topic  that tells you what setting in JTAlert to adjust.

de Laurie VK3AMA



7841 - 7860 of 37815