Date   

locked Re: Callsign box slots

HamApps Support (VK3AMA)
 

On 2/10/2020 8:48 am, David Chavez wrote:
On the JTAlert  - I am having a problem with the callsign box slots to populate the WSJT-X program for transmit.  When I try to click on the box with the callsign, it does not do anything.   Has anyone had this problem and what the fix is.  
Thanks Dave N5CU

Check your WSJTX UDP Server settings. The "Accept UDP Requests" option needs to be enabled.


See the JTAlert help, "WSJT-X / JTDX UDP Setup" topic.

de Laurie VK3AMA


locked Re: Callsign box slots

David Chavez
 

Hi Dave,  It has been about a month when I last used wsjtx and jta, and all work well before and clicking on the jta callsign box.  wsjtx - it does work when I double click.  
Dave N5CU


locked Re: Callsign box slots

Dave Garber
 

I think they have to be calling cq, to click within jta.   does it work if you can double-click in wsjtx
Dave Garber
VE3WEJ / VE3IE


On Thu, Oct 1, 2020 at 7:29 PM David Chavez <dchavez5@...> wrote:
[Edited Message Follows]

On the JTAlert  - I am having a problem with the callsign box slots to populate the WSJT-X
program for transmit.  When I try to click on the box with the
callsign, it does not do anything.   Has anyone had this problem and what the fix
is.  
Thanks Dave N5CU







locked Callsign box slots

David Chavez
 
Edited

On the JTAlert - I am having a problem with the callsign box slots to populate the WSJT-X program for transmit.  When I try to click on the box with the callsign, it does not do anything.   Has anyone had this problem and what the fix is.  
Thanks Dave N5CU


locked JTAlert 2.16.14 is available. New Features & Fixes. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The latest JTAlert version 2.16.14 is now available @ https://hamapps.com/JTAlert/

de Laurie VK3AMA

Release Notes.

2.16.14 (01-Oct-2020)

  New Features:

    - New Alert Type: Wanted ITU Zones Alert.

    - New Alert Filter: Do not show NON ALERTING Callsigns under a set Km distance.
       Note: Callsigns that don't convey their gridsquare in the standard format
       CQ message will not be displayed (because of the unknown distance) when this
       Filter is active and the Callsign does not trigger an Alert.

    - Temporary Ignored Callsigns: Callsigns can be temporarily ignored for the
       current JTAlert session. Callsigns can be ignored by using the Callsign
       right-click context menu. The temporary ignored Callsign list is
       automatically cleared at JTAlert startup.

  Fixes:

    - Decodes Window: Randomly starting with no previous decodes visible and not
       showing new decodes.

    - Decodes Window: Fatal "Clipboard" error when using Chrome remote desktop.

    - Station Gridsquare: Not being set (is empty) after a mismatch with the WSJTX
       grid is reported and completing the update when prompted during startup.

    - Log4OM V1 & V2: Last QSO lookups were not returning the correct QSO in
       the log if the log had previously been updated using an adif import.


locked Re: WSJT-X errors when connecting to IC-7300 #FT8 #HRD

KL7NW
 

I have checked all the audio settings with no luck.  This issue started after a Microsoft update happened on 9/16.  His Windows 10 machine got many updates for Office products,   We have a sched to work with Mike Black who has offered to remote in and look at settings to help us.

 

Thanks,

John KL7NW

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Monty Wilson
Sent: Thursday, October 1, 2020 11:01
To: Support@HamApps.groups.io
Subject: Re: [HamApps] WSJT-X errors when connecting to IC-7300 #FT8 #HRD

 

HRD is designed to control the radio.  In that regard, WSJT-X should be set to Ham Radio Deluxe as in your first screen show of the Setting > Radio panel.

 

This is for control of the radio, not the audio path.

 

The problem appears to be with the Audio….so you should be trouble shooting the Audio path.  Make sure your computers audio controls are set correctly.  In the WSJT-X group there are numerous conversations about setting up the audio.  I would suggest joining that group and taking a look at the archives.

 

Hope this helps….

 

Cheers

 

 

Monty, NR0A

 

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of KL7NW
Sent: Wednesday, September 30, 2020 08:39 PM
To: Support@HamApps.groups.io
Subject: [HamApps] WSJT-X errors when connecting to IC-7300 #FT8 #HRD

 

I am helping a friend with Ham Radio Deluxe version 6.7.0.301, WSJT-X version 2.2.2, and JTAlert version 2.16.13 running on Microsoft Windows 10 64bit.  He has an IC-7300 with the Icom USB cable and Icom driver installed.  Everything worked properly prior to a Microsoft update on 9/16.

 

Microsoft updated his Operating System on 9/16 and he has not been able to get WSJT-X to communicate with the IC-7300 since.  We have tried numerous settings, but these are the two errors with screen shots of the settings when each error pops up:

 

   caused with these settings using HRD to communicate with the IC-7300.  This worked fine before the OS updates:

 

 

 
We then tried settings found on a website that recommended what to use for the IC-7300 and that did not change anything.

  This different error happens with these settings without using HRD to control the communications:

 

 

We uninstalled the USB Codec audio drivers and uninstalled the Icom USB cable made for this radio from device manager.  We then disconnected the USB cable, rebooted the computer, then re-installed the Icom driver and re-connected the cable.  The USB cable showed up under Ports and the USB Codec audio drivers under audio inputs and devices.  The errors persist!  What can we do to correct this?  Searches on the internet  produce no resolution and most are from similar errors from 2018, none current.


locked Re: WSJT-X errors when connecting to IC-7300 #FT8 #HRD

Monty Wilson, NR0A
 

HRD is designed to control the radio.  In that regard, WSJT-X should be set to Ham Radio Deluxe as in your first screen show of the Setting > Radio panel.

 

This is for control of the radio, not the audio path.

 

The problem appears to be with the Audio….so you should be trouble shooting the Audio path.  Make sure your computers audio controls are set correctly.  In the WSJT-X group there are numerous conversations about setting up the audio.  I would suggest joining that group and taking a look at the archives.

 

Hope this helps….

 

Cheers

 

 

Monty, NR0A

 

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of KL7NW
Sent: Wednesday, September 30, 2020 08:39 PM
To: Support@HamApps.groups.io
Subject: [HamApps] WSJT-X errors when connecting to IC-7300 #FT8 #HRD

 

I am helping a friend with Ham Radio Deluxe version 6.7.0.301, WSJT-X version 2.2.2, and JTAlert version 2.16.13 running on Microsoft Windows 10 64bit.  He has an IC-7300 with the Icom USB cable and Icom driver installed.  Everything worked properly prior to a Microsoft update on 9/16.

 

Microsoft updated his Operating System on 9/16 and he has not been able to get WSJT-X to communicate with the IC-7300 since.  We have tried numerous settings, but these are the two errors with screen shots of the settings when each error pops up:

 

   caused with these settings using HRD to communicate with the IC-7300.  This worked fine before the OS updates:

 

 

 
We then tried settings found on a website that recommended what to use for the IC-7300 and that did not change anything.

  This different error happens with these settings without using HRD to control the communications:

 

 

We uninstalled the USB Codec audio drivers and uninstalled the Icom USB cable made for this radio from device manager.  We then disconnected the USB cable, rebooted the computer, then re-installed the Icom driver and re-connected the cable.  The USB cable showed up under Ports and the USB Codec audio drivers under audio inputs and devices.  The errors persist!  What can we do to correct this?  Searches on the internet  produce no resolution and most are from similar errors from 2018, none current.


locked Re: WSJT-X errors when connecting to IC-7300 #FT8 #HRD

Tom Melvin
 

This is really a WSJT-X question

Just to let you know, the main WSJT-X support forum is https://wsjtx.groups.io.    

This one is mainly for JT-Alert issues.


Having said that check the ‘Audio’ tab (in WSJT-X) and make sure the 7300 is set, check the levels (in Window) - if the setup was working with HRD then stick with that - far too many other options to check/set if going direct via COMx - error does suggest is is Audio related not with ‘connection’ to the 7300.

Tom

 --
73

Tom
GM8MJV (IO85)





On 1 Oct 2020, at 02:39, KL7NW <john.kl7nw@...> wrote:

I am helping a friend with Ham Radio Deluxe version 6.7.0.301, WSJT-X version 2.2.2, and JTAlert version 2.16.13 running on Microsoft Windows 10 64bit.  He has an IC-7300 with the Icom USB cable and Icom driver installed.  Everything worked properly prior to a Microsoft update on 9/16.

 

Microsoft updated his Operating System on 9/16 and he has not been able to get WSJT-X to communicate with the IC-7300 since.  We have tried numerous settings, but these are the two errors with screen shots of the settings when each error pops up:

 

   caused with these settings using HRD to communicate with the IC-7300.  This worked fine before the OS updates:

 

 


 
We then tried settings found on a website that recommended what to use for the IC-7300 and that did not change anything.

  This different error happens with these settings without using HRD to control the communications:

 


 

We uninstalled the USB Codec audio drivers and uninstalled the Icom USB cable made for this radio from device manager.  We then disconnected the USB cable, rebooted the computer, then re-installed the Icom driver and re-connected the cable.  The USB cable showed up under Ports and the USB Codec audio drivers under audio inputs and devices.  The errors persist!  What can we do to correct this?  Searches on the internet  produce no resolution and most are from similar errors from 2018, none current.


locked WSJT-X errors when connecting to IC-7300 #FT8 #HRD

KL7NW
 

I am helping a friend with Ham Radio Deluxe version 6.7.0.301, WSJT-X version 2.2.2, and JTAlert version 2.16.13 running on Microsoft Windows 10 64bit.  He has an IC-7300 with the Icom USB cable and Icom driver installed.  Everything worked properly prior to a Microsoft update on 9/16.

 

Microsoft updated his Operating System on 9/16 and he has not been able to get WSJT-X to communicate with the IC-7300 since.  We have tried numerous settings, but these are the two errors with screen shots of the settings when each error pops up:

 

   caused with these settings using HRD to communicate with the IC-7300.  This worked fine before the OS updates:

 

 


 
We then tried settings found on a website that recommended what to use for the IC-7300 and that did not change anything.

  This different error happens with these settings without using HRD to control the communications:

 


 

We uninstalled the USB Codec audio drivers and uninstalled the Icom USB cable made for this radio from device manager.  We then disconnected the USB cable, rebooted the computer, then re-installed the Icom driver and re-connected the cable.  The USB cable showed up under Ports and the USB Codec audio drivers under audio inputs and devices.  The errors persist!  What can we do to correct this?  Searches on the internet  produce no resolution and most are from similar errors from 2018, none current.


locked HamApps in Dark Mode

Stefan Braun
 

Hello,

It would be nice to have Hamapps (JTAlert) in Dark Mode.
JTDX has also the function so to get it equal it would be nice that this would be added.

Thanks 

73 de Stefan HB9GFX/DG9BDI


locked Re: changing callsign for hamspots.net site #HamSpots

Jaroslaw Gorczynski
 

Hi Laurie,

Thank you very much for your help and for a fantastic job for the whole hams family.

Vy 73 de HF5A


locked Re: changing callsign for hamspots.net site #HamSpots

Laurie, VK3AMA
 



On 30/09/2020 11:03 pm, Jaroslaw Gorczynski via groups.io wrote:
Hi Laurie,

I'm moving from Scotland to Poland and I change my callsign from MM0LGS to HF5A. I would like to update it in my registration for HamSpots.net. Unfortunately I found no mean to alter this setting (the only option is to update the password).  I would gladly register a new account with the new callsign, but that fails too, because I'm using the same email address...

Is there a way to change the callsign associated with this account (and keep the email address)?

Thank you for your help

Vy 73, Jarek - HF5A
(previously MM0LGS)
_._,_._,_



Changing registration Callsign while retaining the same email address is only possible via a direct edit of the accounts database by an Administrator following a request by the account holder.

I have just now made the change.

de Laurie VK3AMA


locked changing callsign for hamspots.net site #HamSpots

Jaroslaw Gorczynski
 

Hi Laurie,

I'm moving from Scotland to Poland and I change my callsign from MM0LGS to HF5A. I would like to update it in my registration for HamSpots.net. Unfortunately I found no mean to alter this setting (the only option is to update the password).  I would gladly register a new account with the new callsign, but that fails too, because I'm using the same email address...

Is there a way to change the callsign associated with this account (and keep the email address)?

Thank you for your help

Vy 73, Jarek - HF5A
(previously MM0LGS)


locked Re: Radio Turn On w/ JTAlert Startup

Michael Black
 

That's really a WSJT-X question and not JTAlert.

You now have to add a hamlib_settings.json file in the same place as WSJT-X.ini

It should contain this

{
     "config": {
             "auto_power_on": "1"
     }
}

de Mike W9MDB





On Tuesday, September 29, 2020, 03:36:33 PM CDT, Thomas Webb <tmwebb@...> wrote:


Just loaded Ver 2.16.13 without incident.  However, I just loaded WSJT-X Ver 2.3 Rc-1.  With this combination, I no longer have the automatic radio turn-on feature.  Is there some function in one or both programs that needs to be activated to regain this function?

Tom, WA9AFM/5


locked Re: PROBLEM WITH A POP-UP LOG ERROR MESSAGE

Cliff Fox (KU4GW)
 

Thanks Neil. I joined today and didn't know until I did that K3UK Andy was the owner.moderator. I hadn't seen Andy in a long time and had wondered what had become of him.

73, Cliff KU4GW


locked Radio Turn On w/ JTAlert Startup

Thomas Webb
 

Just loaded Ver 2.16.13 without incident.  However, I just loaded WSJT-X Ver 2.3 Rc-1.  With this combination, I no longer have the automatic radio turn-on feature.  Is there some function in one or both programs that needs to be activated to regain this function?

Tom, WA9AFM/5


locked Re: JTAlert want connect

g4wjs
 

On 29/09/2020 17:52, Thomas Mills wrote:
JTAlert want reconnect to WSJTX after changing the configuration in wsjtx.  This seems to have started after the last upgrade to 2.16.13.  I'm using UDP 239.0.0.3 to work Grid Tracker.  I'm not sure if that has anything to do with it, but has anyone seen this problem?  To clear the problem I close JTAlert and reopen.

Thanks Tom
Hi Tom,

do you have the same UDP server settings in each of your WSJT-X configurations ("Settings->Reporting->UDP Server")?

73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked JTAlert want connect

Thomas Mills
 

JTAlert want reconnect to WSJTX after changing the configuration in wsjtx.  This seems to have started after the last upgrade to 2.16.13.  I'm using UDP 239.0.0.3 to work Grid Tracker.  I'm not sure if that has anything to do with it, but has anyone seen this problem?  To clear the problem I close JTAlert and reopen.

Thanks Tom


locked Wanted digital

Neil <n4fn.neil@...>
 

Be nice at one point that in the alerts we could see if a particular country/entity has been worked or even confirmed in a mode. 
we have a variety of alerts available in the dropdown but unless I am missing it it is not available
I know that a German ham has written a program that will do that in DX Lab Spot Collector, but I do not use it.
Neil   N4FN


locked Re: JTAlert for HRD5

neil_zampella
 

As previously said, the latest version of JT-Alert will work fine, HOWEVER, you need to properly select the version used in the JT-Alert Logging settings.

Neil, KN3ILZ

6841 - 6860 of 38444