Date   

locked Re: Transverter support #FT8

Jim @ K5ND
 

It's working correctly here. I select the 222 MHz band on WSJT-X. This sets my rig to 28 MHz. JTAlert shows 1.25 m band. And when I log the QSO, it shows up in AClog as 1.25 m.

As Bill says, select the correct band on WSJT-X that has previously been set up for the correct offset and you should be good.

73, Jim, K5ND


locked Re: JT Alert Not Triggering TX

W7JHR@...
 

Hi Jim,
I just uninstalled and re-installed WSJT-x 2.3. and I don’t see the other two windows .

Jim W7JHR 

 


locked Re: V2.16.17 crashes after logging in HRD 6.7.0.323

Ron W3RJW
 

Torsten,

Also look at the path to HRD AppData, Roaming, HRDLLC ....   and the path to the HRD log.
--
73
Ron, W3RJW


locked Re: More CQ Marathon info

Jim N6VH
 


On 2/5/2021 2:07 PM, Phil Cooper via groups.io wrote:

Hi Jim,

 

Just out of curiosity, I did check, and Albania is NOT in the wanted list

 

Still puzzled, but I will figure it out!

Currently, the only option after working a new Marathon entity (CQ Zone or DXCC) is to do a rebuild, which is not a major issue, but with over 100k QSO’s, it can take a few minutes.

 

73 de Phil GU0SUP


Phil,

If Albania is not in the Marathon Wanted list, then you should not be getting a Marathon alert for it. Incidentally, did you also check the Not Wanted list? It should be there if it isn't in the Wanted list. That might seem like an odd question, but I find it is a good idea not to assume anything in cases like this.

Also, did you recheck that all the settings are what they should be. It never hurts to check. If the country is in the Not Wanted list, and not in the Wanted list, and all the settings are checked correctly, then you should not get the alert.

73,

Jim N6VH


locked Re: JT Alert Not Triggering TX

Jim N6VH
 

On 2/6/2021 8:43 AM, W7JHR via groups.io wrote:
JTAlert worked perfectly in the past.  I upgraded to WSJT-X 2.3 two days ago and that's when I started to see the problem. Attached are two screen shots. One, the UDP set up in WSJT-x which has been the same since the mode was invented.  Also, I noticed on the screenshot of your UDP that you have two windows that I don't.  Outgoing Interfaces and Multicast TTL.  The second screenshot is of the UDP setup in the JTAlert program.  I have uninstalled and reinstalled both programs with no joy.  Thanks for your help.

Jim W7JHR
Jim,

Are you certain that you are actually running WSJT-X 2.3? That WSJT-X settings screen doesn't look like the one in 2.3. It should look like the one in the screen shot that Laurie sent.  Those two extra windows should be there.

73,

Jim N6VH


locked Re: JT Alert Not Triggering TX

W7JHR@...
 

JTAlert worked perfectly in the past.  I upgraded to WSJT-X 2.3 two days ago and that's when I started to see the problem.  Attached are two screen shots. One, the UDP set up in WSJT-x which has been the same since the mode was invented.  Also, I noticed on the screenshot of your UDP that you have two windows that I don't.  Outgoing Interfaces and Multicast TTL.  The second screenshot is of the UDP setup in the JTAlert program.  I have uninstalled and reinstalled both programs with no joy.  Thanks for your help.

Jim W7JHR


locked Re: JTAlert Crash After Viewing Or Changing Settings

David - AK2L
 

No error window; JTAlert silently disappears the same way it would if I had clicked the close [x] box.

This computer is using Windows Defender.  It always complains when I download or install an update to JTAlert, but I just override the warning and tell the computer to install anyway.  Windows Defender has done this since I first started using JTAlert and I have never had a problem before now.

OK on the re-install.  I will let you know the outcome.

AK2L


locked Re: V2.16.17 crashes after logging in HRD 6.7.0.323

DM1TS Torsten
 

Hi Laurie,
an additionell information: at the new PC I use a other Username like on the old system. I found an issue in WSJT-X with the path to the %appdata% directory. From the backup it was the wrong username but now I correct this to the new user in the "audio tab" of WSJTX (Save Directory).

But there is no impact of the issue but I feel that the new username could be the cause. But I check the settings serveral times and can't find other wrong parameter in the paths :-(

73 de Torsten
DM1TS, JO61OB

Am 05.02.2021 um 22:11 schrieb Laurie, VK3AMA:

On 6/02/2021 5:20 am, DM1TS Torsten wrote:
Hi,
I had to do a complete change of my HAM software to a new PC. This worked well thanks to the backup options. Here runs now WSJT-X in V2.3.0, in addition JTALERT in V2.16.17 and HRD in V6.7.0.323.
As soon as I have made a QSO in WSJT-X the log window pops up and I confirm the log entry. HRD reports immediately afterwards that the QSO is also there in the log, I see the entry also immediately. At this moment JTALERT terminates without warning or indication of an error. This happens after every QSO. In the event log of Windows I find the following information:

-- snip --

Is there any idea for this, unfortunately I can't work anymore.

73 de Torsten
DM1TS, JO61OB
It is unlikely to be JTAlert 2.16.17, which is quite stable, released late last year with no similar reports. JTAlert will typically show an error window when there is a critical failure. Since it is quietly closing, I am suspicious that your PC protection software may be interfering, what do you use?
Try downgrading JTAlert to an earlier version, try 2.16.16 or 2.16.15. Both are available on the JTAlert download page @ https://hamapps.com/JTAlert/
Just run the setup, no need to uninstall first. Your configuration is safe and will not be altered or deleted.
de Laurie VK3AMA


locked Re: V2.16.17 crashes after logging in HRD 6.7.0.323

DM1TS Torsten
 

Hi Laurie,
I have now downgraded to two versions back, disabled the virus scanner and also started JTAlert as administrator for testing. The behavior remains the same, it crashes abruptly and without a message after the entry of the QSO in the HRD logbook.

I am absolutely at a loss, it worked great with the old PC.

73 de Torsten
DM1TS, JO61OB

Am 05.02.2021 um 22:11 schrieb Laurie, VK3AMA:

On 6/02/2021 5:20 am, DM1TS Torsten wrote:
Hi,
I had to do a complete change of my HAM software to a new PC. This worked well thanks to the backup options. Here runs now WSJT-X in V2.3.0, in addition JTALERT in V2.16.17 and HRD in V6.7.0.323.
As soon as I have made a QSO in WSJT-X the log window pops up and I confirm the log entry. HRD reports immediately afterwards that the QSO is also there in the log, I see the entry also immediately. At this moment JTALERT terminates without warning or indication of an error. This happens after every QSO. In the event log of Windows I find the following information:

-- snip --

Is there any idea for this, unfortunately I can't work anymore.

73 de Torsten
DM1TS, JO61OB
It is unlikely to be JTAlert 2.16.17, which is quite stable, released late last year with no similar reports. JTAlert will typically show an error window when there is a critical failure. Since it is quietly closing, I am suspicious that your PC protection software may be interfering, what do you use?
Try downgrading JTAlert to an earlier version, try 2.16.16 or 2.16.15. Both are available on the JTAlert download page @ https://hamapps.com/JTAlert/
Just run the setup, no need to uninstall first. Your configuration is safe and will not be altered or deleted.
de Laurie VK3AMA


locked Re: JTAlert #JTDX

John Profita
 

Thank you Laurie, I wondered if I should have sent the short video. My apologies for doing so. I am in the process of a new install of JTDX and JTAlert. I will let you know how I make out.

Tnx, John
ND1X


locked Re: JT Alert Not Triggering TX

Laurie, VK3AMA
 

On 6/02/2021 11:46 am, W7JHR via groups.io wrote:
The call sign shows up in JTAlert, but does not transfer to the RX Frequency window in WSJT-X when clicked.  I went back in and looked at the UDP settings and they were all checked. I even changed the UDP Server address to yours, but that didn't work, so I put my former address back.

Thanks,
Jim W7JHR
If the Callsign is not being transferred to the DXCall field of WSJT-X that indicates one or two possibilities, either the "Accept UDP requests" is not enabled or that the decode that corresponds to the Callsign no longer exists within the WSJT-X list of decodes. If the decodes have been cleared in WSJT-X than it will not respond to Callsign click events from JTAlert, that is how WSJT-X is coded (as part of its anti-robot framework) and not something JTAlert can control (and not that I would want it to, the automated robot stations that now pollute the bands are a scurge on the hobby IMHO).

If this worked in the past, when did it stop working and what changed at that time, was it a JTAlert or WSJT-X upgrade?

If all else fails try a Windows restart, it can't hurt.

de Laurie VK3AMA


locked Re: JT Alert Not Triggering TX

W7JHR@...
 

The call sign shows up in JTAlert, but does not transfer to the RX Frequency window in WSJT-X when clicked.  I went back in and looked at the UDP settings and they were all checked. I even changed the UDP Server address to yours, but that didn't work, so I put my former address back.

Thanks,
Jim W7JHR


locked Re: Transverter support #FT8

g4wjs
 

Hi Mike, Tom, and Laurie,

yes, which is exactly what it does.

Tom, have you selected the right band in WSJT-X? The band you set the IF offset for is the one you select. For example you might have -116 MHz as the offset for the 2m band in "Settings->Frequencies->Station Information". Then simply select a 2m frequency in WSJT-X and your 10m IF rig will be controlled as expected.

73
Bill
G4WJS.

On 05/02/2021 15:02, Michael Black via groups.io wrote:
Seems to me WSJT-X should be reporting the correct frequency since it knows what's going on.

Mike W9MDB




On Friday, February 5, 2021, 08:58:20 AM CST, Tom Melvin <tom@...> wrote:


All

Not sure if this can be fixed/worked around - will depend I suspect on UDP message content

Testing a 13cm (2320) system - wsjt-x allows me to enter transverter offset so it knows what to set the rig to.

JTAlert reports the freq the rig is set to - is there a way to get JTAlert to report rig + offset?

2320 - offset (of  -2174) gives IF of 146 - JTAlert report 2m - which is correct for the rig but not to operating freq

Tom
GM8MJV



--
73
Bill
G4WJS.


locked Re: JTAlert Crash After Viewing Or Changing Settings

HamApps Support (VK3AMA)
 

On 6/02/2021 10:26 am, David wrote:
If I view settings, without changing any, JTAlert crashes as soon as I close the settings dialog.  After re-launching everything runs fine.
If I change a setting, JTAlert crashes as soon as I close the settings dialog.  After relaunching, everything runs fine and I observe that the setting change was successful.

Before I go to the trouble of re-installing JTAlert, is there any information that I can gather that would be useful to you?

As for re-installing, is there a way to export my settings or preserve them before I uninstall JTAlert?

Where does JTAlert store settings?  After un-installing, I want to ensure that I have removed all the old data.

David, AK2L

Does the crash produce an error window, if so what does it say or post an image?

The Settings are managed by an executable file, independent of the running JTAlert.exe, so closing it should not have any direct effect. PC protection software interference maybe?

All your settings are safe across an uninstall/install operation unless you use one of those cleaner apps that try to remove every last trace of an install by deleting folders in your $localappdata% directory tree and removing registry entries. If you use one of these programs and loose everything there is nothing I can do. My advice is avoid those cleaner type apps, they often create problems when none existed previously, in my experience.

In the Help file there is a topic on moving your JTAlert install to a new PC, that will give you the location of your JTAlert Configuration and supporting files. See the "Frequently Asked Questions -> Move JTAlert to a New PC" topic.

de Laurie VK3AMA


locked JTAlert Crash After Viewing Or Changing Settings

David - AK2L
 

Re: JTAlert 2.16.17 (and 2.16.16) / Windows 10 Pro with latest updates

Laurie,

If I view settings, without changing any, JTAlert crashes as soon as I close the settings dialog.  After re-launching everything runs fine.
If I change a setting, JTAlert crashes as soon as I close the settings dialog.  After relaunching, everything runs fine and I observe that the setting change was successful.

Before I go to the trouble of re-installing JTAlert, is there any information that I can gather that would be useful to you?

As for re-installing, is there a way to export my settings or preserve them before I uninstall JTAlert?

Where does JTAlert store settings?  After un-installing, I want to ensure that I have removed all the old data.

David, AK2L


locked Re: More CQ Marathon info

Steve, N3SL
 

Phil,
If you know you've only worked a new Marathon, scroll to the Marathon box in the "rebuild" window and simply rebuild that - only.  I have 30k Qs, and it takes 8 seconds.

On Fri, Feb 5, 2021 at 4:08 PM Phil Cooper via groups.io <pcooper=suremail.gg@groups.io> wrote:

Hi Jim,

 

Just out of curiosity, I did check, and Albania is NOT in the wanted list

 

Still puzzled, but I will figure it out!

Currently, the only option after working a new Marathon entity (CQ Zone or DXCC) is to do a rebuild, which is not a major issue, but with over 100k QSO’s, it can take a few minutes.

 

73 de Phil GU0SUP

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Jim N6VH
Sent: 05 February 2021 15:56
To: Support@HamApps.groups.io
Subject: Re: [HamApps] More CQ Marathon info

 

 

On 2/5/2021 6:16 AM, Phil Cooper via groups.io wrote:

Hi Steve,

 

For that call, it was a Marathon alert first and foremost.I have new Marathon entities set to a specific colour, and that is what it showed, and said.

 

Given that this call was previously worked on another band, it should not have given me a new Marathon alert.

 

I already have ZA worked, confirmed and verified on 30m, it should not have alerted me for a Wanted Prefix or DXCC, and that was not the alert type. I don't have grids set as an alert, so it won't have been that.

 

73 de Phil GU0SUP

 

Phil,

The Auto Clear is permanent.

You might have already done this, but you might want to make certain that none of the relevant settings have changed. IOW, Auto Clear is still checked, no QSL for Marathon, Any Band, Any Mode. They shouldn't have changed, but it might be worth a check.

Also, go to Settings - CQ Marathon, and see if Albania is listed in the "Not Wanted" or "Wanted" listing.

Even if you have already done thes, it is sometimes a good idea to a double, or even triple check.

73,

Jim N6VH

 


locked Re: More CQ Marathon info

Phil Cooper
 

Hi Jim,

 

Just out of curiosity, I did check, and Albania is NOT in the wanted list

 

Still puzzled, but I will figure it out!

Currently, the only option after working a new Marathon entity (CQ Zone or DXCC) is to do a rebuild, which is not a major issue, but with over 100k QSO’s, it can take a few minutes.

 

73 de Phil GU0SUP

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Jim N6VH
Sent: 05 February 2021 15:56
To: Support@HamApps.groups.io
Subject: Re: [HamApps] More CQ Marathon info

 

 

On 2/5/2021 6:16 AM, Phil Cooper via groups.io wrote:

Hi Steve,

 

For that call, it was a Marathon alert first and foremost.I have new Marathon entities set to a specific colour, and that is what it showed, and said.

 

Given that this call was previously worked on another band, it should not have given me a new Marathon alert.

 

I already have ZA worked, confirmed and verified on 30m, it should not have alerted me for a Wanted Prefix or DXCC, and that was not the alert type. I don't have grids set as an alert, so it won't have been that.

 

73 de Phil GU0SUP

 

Phil,

The Auto Clear is permanent.

You might have already done this, but you might want to make certain that none of the relevant settings have changed. IOW, Auto Clear is still checked, no QSL for Marathon, Any Band, Any Mode. They shouldn't have changed, but it might be worth a check.

Also, go to Settings - CQ Marathon, and see if Albania is listed in the "Not Wanted" or "Wanted" listing.

Even if you have already done thes, it is sometimes a good idea to a double, or even triple check.

73,

Jim N6VH

 


locked Re: Transverter support #FT8

Tom Melvin
 

Thanks Laurie & Mike

Will post over on wsjtx

Tom
GM8MJV

On 5 Feb 2021, at 21:05, Laurie, VK3AMA <hamapps.support@vkdxer.com> wrote:



On 6/02/2021 1:58 am, Tom Melvin wrote:
Not sure if this can be fixed/worked around - will depend I suspect on UDP message content

Testing a 13cm (2320) system - wsjt-x allows me to enter transverter offset so it knows what to set the rig to.

JTAlert reports the freq the rig is set to - is there a way to get JTAlert to report rig + offset?

2320 - offset (of -2174) gives IF of 146 - JTAlert report 2m - which is correct for the rig but not to operating freq

Tom
GM8MJV
This is a WSJT-X issue. JTAlert reports only the frequency reported by WSJT-X in its UDP Status messages. If the Status frequency is wrong, then JTAlert will be wrong. JTAlert has no concept of Transverter use, CAT or Rig control.

A common software development phrase applicable to this situation, GIGO, "Garbage In, Garbage Out". Sorry, I can't help, try posting on the WSJT-X group.

de Laurie VK3AMA







locked Re: V2.16.17 crashes after logging in HRD 6.7.0.323

Laurie, VK3AMA
 

On 6/02/2021 5:20 am, DM1TS Torsten wrote:
Hi,
I had to do a complete change of my HAM software to a new PC. This worked well thanks to the backup options. Here runs now WSJT-X in V2.3.0, in addition JTALERT in V2.16.17 and HRD in V6.7.0.323.
As soon as I have made a QSO in WSJT-X the log window pops up and I confirm the log entry. HRD reports immediately afterwards that the QSO is also there in the log, I see the entry also immediately. At this moment JTALERT terminates without warning or indication of an error. This happens after every QSO. In the event log of Windows I find the following information:

-- snip --

Is there any idea for this, unfortunately I can't work anymore.

73 de Torsten
DM1TS, JO61OB
It is unlikely to be JTAlert 2.16.17, which is quite stable, released late last year with no similar reports. JTAlert will typically show an error window when there is a critical failure. Since it is quietly closing, I am suspicious that your PC protection software may be interfering, what do you use?

Try downgrading JTAlert to an earlier version, try 2.16.16 or 2.16.15. Both are available on the JTAlert download page @ https://hamapps.com/JTAlert/
Just run the setup, no need to uninstall first. Your configuration is safe and will not be altered or deleted.

de Laurie VK3AMA


locked Re: Transverter support #FT8

Laurie, VK3AMA
 

On 6/02/2021 1:58 am, Tom Melvin wrote:
Not sure if this can be fixed/worked around - will depend I suspect on UDP message content

Testing a 13cm (2320) system - wsjt-x allows me to enter transverter offset so it knows what to set the rig to.

JTAlert reports the freq the rig is set to - is there a way to get JTAlert to report rig + offset?

2320 - offset (of  -2174) gives IF of 146 - JTAlert report 2m - which is correct for the rig but not to operating freq

Tom
GM8MJV
This is a WSJT-X issue. JTAlert reports only the frequency reported by WSJT-X in its UDP Status messages. If the Status frequency is wrong, then JTAlert will be wrong. JTAlert has no concept of Transverter use, CAT or Rig control.

A common software development phrase applicable to this situation, GIGO, "Garbage In, Garbage Out". Sorry, I can't help, try posting on the WSJT-X group.

de Laurie VK3AMA

2321 - 2340 of 35329