Date   

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
 

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




locked Re: Question on audio alert options by band

Paul AC9O
 

Thanks Laurie and Hasan for the ideas.

Some don't quite fit, but that's ok. The sound on/off is all or nothing. I still want the sound for DXCC and States on HF. I am only 7 away from 5BWAS and don't want to miss any.

I haven't tried multiple instances, will consider that. I only use one radio (IC-7300) that covers 6m which is where I am grid chasing the most.

Thanks again for the quick responses.

73
Paul, AC9O


locked wsjtx rig setting when using jtalert

 

aclog wsjtx using jtalert as interface
What rig do I select.  in wsjtx.


locked WSJTX, JTAlert, and DXKeeper Integration

JT Croteau
 

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


locked Re: JT Alert V 2.16.6 Program quits

HamApps Support (VK3AMA)
 

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 missing "bands" = 4m-band

HamApps Support (VK3AMA)
 

On 6/06/2020 7:33 am, Norbert Graf - DD3KF wrote:

I did a “Scan Log and Rebuild“ before testing.

 

Please see the screenshot for 4m.

 

The wrongly alerted WANTED GRID's JO21 and JO31 are included in this list.

 

In the afternoon there was another short opening on 4m. In this opening the described findings showed up again with stations from other verified GRID´s.

 

WANTED GRID Tracking on 6m and short wave working okay here.

 

73

 

______________

Norbert Graf


OK Norbet,

I'll look into it and run some tests. Honestly with the amount of code changes and copy/pasted code needed to add the new band, I'm surprised there have not been other defect reports.

de Laurie VK3AMA


locked Re: Callsign Display Decays

HamApps Support (VK3AMA)
 

On 6/06/2020 8:59 am, Bob Craig wrote:

 

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.

 


I can't see any reason why you would want to restrict your self by continuing to run WSJT-X 2.0.1 which has undergone significant performance improvements and fixes since that release.

JTAlert 2.12.8 is now 2.5 years old and long out-of-date. In the very near future the Callsign database will be getting an upgrade that will not be compatible with such an old JTAlert version. So unless you upgrade you will be left running old WSJT-X and JTAlert versions with a Callsign database that becomes more inaccurate with each passing week.

Your choice, good luck.

de Laurie VK3AMA


locked Re: Question on audio alert options by band

Hasan Schiers N0AN
 

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: Callsign Display Decays

Bob Craig, K8RC
 

 

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 JT Alert V 2.16.6 Program quits

Bill Hicks
 

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.  


TIA.

5481 - 5500 of 35446