Date   

locked Changing name of Receiver in 2.13

Mark Hatch
 

First off, what a big improvement! The work done in the Decodes History makes  JTAlert so much easier to use. I no longer have to be "quick on the draw" to start a QSO with a desirable station. Buy looking at the Decodes history I can figure out who matches my time, relative signal strength, etc. Thank you!

One question....  Where is the name of the Receiver set? I am seeing "Default" in the decodes history window. I am using omnirig, log40m, and win4icom suite if these matter.

73
Mark


locked Re: JTAlertX 2.13.0 Update #FT8 #JTDX

HamApps Support (VK3AMA)
 

On 10/03/2019 12:12 pm, BOBBY E Chandler wrote:

Same problem with WSJTX. Back to prior JTAlert version and all OK.

Bobby/N4AU

What problem is that?

Are you referring to the problem reported by JTDX users? I can't see how that would be the case as their problem is related to how JTDX is coded internally.

Does this help...
https://hamapps.groups.io/g/Support/message/23581

de Laurie VK3AMA


locked Re: JTAlertX 2.13.0 Update #FT8 #JTDX

BOBBY E Chandler <bobbye@...>
 

Same problem with WSJTX. Back to prior JTAlert version and all OK.

Bobby/N4AU

-- 


  Bobby Chandler
bobbye@...
   n4au@...  


locked Re: changing callsign for hamspots.net site

Razvan Popescu
 

Thank you so much, Laurie!
R


locked Re: changing callsign for hamspots.net site

HamApps Support (VK3AMA)
 

On 10/03/2019 11:31 am, Razvan Popescu wrote:
I've changed my callsign and 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)??

Thanks,
Razvan
W2RP 
(previously WA2RP)
Razvan.

Unfortunately the Callsign management code used by HamSpots doesn't allow for users to change their Callsign. It is manual process performed by an Administrator.

I have made the Callsign change for you. Your password remains unchanged.

de Laurie VK3AMA


locked changing callsign for hamspots.net site

Razvan Popescu
 

Hi,
I've changed my callsign and 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)??

Thanks,
Razvan
W2RP 
(previously WA2RP)


locked Re: DOUBLE CLICK TO TX #FT8

HamApps Support (VK3AMA)
 

On 10/03/2019 11:10 am, Michael Paul wrote:
prior to JTAlertX 2.13.0 I was able to double click on a call in JTAlert and it would initiate a TX in JTDX.  After updating to JTAlertX 2.13.0 no amount of double clicking on call signs will enable a TX.  Double click on Callsign inside JTDX still initiates a reply. 

I have had a quick look over JTAlertX 2.13.0 settings and cannot find a double click to reply setting.

Anyone else found the same change in 2.13.0?

Mick.
See this message... https://hamapps.groups.io/g/Support/message/23581

Let me know if this corrects the JTDX problems you experienced.

de Laurie VK3AMA


locked Re: DOUBLE CLICK TO TX #FT8

Dave Garber
 

there is a click box, on the settings/general page of wsjt |" double click on call sets tx enable"

is that what you need??
Dave Garber
VE3WEJ / VE3IE


On Sat, Mar 9, 2019 at 7:10 PM Michael Paul <mickwpaul@...> wrote:
prior to JTAlertX 2.13.0 I was able to double click on a call in JTAlert and it would initiate a TX in JTDX.  After updating to JTAlertX 2.13.0 no amount of double clicking on call signs will enable a TX.  Double click on Callsign inside JTDX still initiates a reply. 

I have had a quick look over JTAlertX 2.13.0 settings and cannot find a double click to reply setting.

Anyone else found the same change in 2.13.0?

Mick.


locked DOUBLE CLICK TO TX #FT8

Michael Paul
 

prior to JTAlertX 2.13.0 I was able to double click on a call in JTAlert and it would initiate a TX in JTDX.  After updating to JTAlertX 2.13.0 no amount of double clicking on call signs will enable a TX.  Double click on Callsign inside JTDX still initiates a reply. 

I have had a quick look over JTAlertX 2.13.0 settings and cannot find a double click to reply setting.

Anyone else found the same change in 2.13.0?

Mick.


locked Re: JTAlertX 2.13.0 Update #FT8 #JTDX

Ed Wilson
 

Laurie,

I did find a few minutes to check out the suggestion in the link below and it seemed to take care of the problem...thanks!

Ed, K0KC

k0kc@...
http://k0kc.us/


On Saturday, March 9, 2019, 4:15:48 PM EST, Ed Wilson via Groups.Io <ed.wilson@...> wrote:


Laurie,

I will have to give that a try tomorrow my time...I will let you know.

Ed, K0KC

k0kc@...
http://k0kc.us/


On Saturday, March 9, 2019, 2:53:25 PM EST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 10/03/2019 1:20 am, Ed Wilson via Groups.Io wrote:
I experienced a similar problem when using JTDX 2.0.2 rc133_2...went back to JTAlert 2.12.10 and things seem to be working fine.

Ed, K0KC
Ed,

Try 2.13.0 again.
See this message... https://hamapps.groups.io/g/Support/message/23581

Let me know if this corrects the JTDX problems you experienced.

de Laurie VK3AMA


locked Re: JTAlertX 2.13.0 Update #FT8 #JTDX

Ed Wilson
 

Laurie,

I will have to give that a try tomorrow my time...I will let you know.

Ed, K0KC

k0kc@...
http://k0kc.us/


On Saturday, March 9, 2019, 2:53:25 PM EST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 10/03/2019 1:20 am, Ed Wilson via Groups.Io wrote:
I experienced a similar problem when using JTDX 2.0.2 rc133_2...went back to JTAlert 2.12.10 and things seem to be working fine.

Ed, K0KC
Ed,

Try 2.13.0 again.
See this message... https://hamapps.groups.io/g/Support/message/23581

Let me know if this corrects the JTDX problems you experienced.

de Laurie VK3AMA


locked Re: JTAlertX 2.13.0 Update #FT8 #JTDX

HamApps Support (VK3AMA)
 

On 10/03/2019 1:20 am, Ed Wilson via Groups.Io wrote:
I experienced a similar problem when using JTDX 2.0.2 rc133_2...went back to JTAlert 2.12.10 and things seem to be working fine.

Ed, K0KC
Ed,

Try 2.13.0 again.
See this message... https://hamapps.groups.io/g/Support/message/23581

Let me know if this corrects the JTDX problems you experienced.

de Laurie VK3AMA


locked Re: Version 2.13.0, cannot scan log after upgrade

HamApps Support (VK3AMA)
 

On 10/03/2019 2:29 am, Jim N6VH wrote:
Apparently, this issue only affected those using ADIF logging. I have had no problems using Log4OM.

73,

Jim N6VH

That's correct. Specifically, the ADIF import executable was aborting import. The ADIF logging part was still working.

de Laurie VK3AMA


locked Re: JTAlertX 2.13.0 Update #FT8 #JTDX

HamApps Support (VK3AMA)
 

On 10/03/2019 1:12 am, Bob Davet wrote:
Weird issue here.
I upgraded today. Using JTDX and JTAlertX. Everything was seemingly working fine. Click on a call sign in JTAlertX and it triggered JTDX. Logged fine. Then clicked on a call sign and it triggered JTDX. The call sign did not come back to me right away  so JTDX kept calling. The call sign went into a QSO with another call. JTDX kicked the Enable TX out which it should. I waited for him or any other call sign to click on. Could not get JTAlertX to activate JTDX anymore. I could click on the callsign in JTDX and it functioned fine. JTAlertX was still showing call signs as it should but I couldnt get it to activate JTDX.
I closed JTDX and JTAlertX. Restarted them. That seemed to clear the problem or so I thought. Same issue started up again with another contact.
So I closed the programs again. Restarted them. Problem remained from the beginning this time.
Restarted the computer. Everything cleared and worked. Then it happened again.
Closed program and restarted. Cleared the problem. A little while later it was back.

Reinstalled JTAlertX 2.12.10.

So far that problem has not reappeared.
I don't even know where to start to figure this one out. Very random.

Bob
W8RID
Bob,

Try 2.13.0 again, but this time go into the JTAlert Settings and turn off Callsign Coloring. "Applications -> WSJT-X" section of the Settings window.

   

Let me know if that corrects the JTDX behaviour.

de Laurie VK3AMA


locked Re: Version 2.13.0, cannot scan log after upgrade

HamApps Support (VK3AMA)
 

On 10/03/2019 12:59 am, John H. Long Jr. wrote:
How can we tell if we have the latest version of V2.13.0  ?
 
John H. Long Jr.
KW7A
John,

The fix for the broken ADIF importing was to bundle the correct version (latest) dll files into the Setup executable. I decided to not bump the version number for JTAlert for this trivial task but to just upload a corrected Setup executable.

You can check if you have the correct file by examining its size (right click on file and view the Properties) and comparing with the size published on the JTAlert download page @ HamApps.com. Comparing the MD5 hash is another option.

   

de Laurie VK3AMA


locked Re: Version 2.13.0, cannot scan log after upgrade

Jim N6VH
 

On 3/8/2019 6:09 PM, HamApps Support (VK3AMA) wrote:

I have identified & corrected the issue and confirmed in Testing the ADIF import is now working.
Please download 2.13.0 again
de Laurie VK3AMA
_._,_._,_
Laurie,

Apparently, this issue only affected those using ADIF logging. I have had no problems using Log4OM.

73,

Jim N6VH


locked Re: JTAlertX 2.13.0 Update #FT8 #JTDX

Ed Wilson
 

Whoops...I was using JTDX 2.0.1 rc133_2. Sorry!

Ed, K0KC

k0kc@...
http://k0kc.us/


On Saturday, March 9, 2019, 9:20:33 AM EST, Ed Wilson via Groups.Io <ed.wilson@...> wrote:


I experienced a similar problem when using JTDX 2.0.2 rc133_2...went back to JTAlert 2.12.10 and things seem to be working fine.

Ed, K0KC

k0kc@...
http://k0kc.us/


On Saturday, March 9, 2019, 9:13:00 AM EST, Bob Davet <davet354tfd@...> wrote:


Weird issue here.
I upgraded today. Using JTDX and JTAlertX. Everything was seemingly working fine. Click on a call sign in JTAlertX and it triggered JTDX. Logged fine. Then clicked on a call sign and it triggered JTDX. The call sign did not come back to me right away  so JTDX kept calling. The call sign went into a QSO with another call. JTDX kicked the Enable TX out which it should. I waited for him or any other call sign to click on. Could not get JTAlertX to activate JTDX anymore. I could click on the callsign in JTDX and it functioned fine. JTAlertX was still showing call signs as it should but I couldnt get it to activate JTDX.
I closed JTDX and JTAlertX. Restarted them. That seemed to clear the problem or so I thought. Same issue started up again with another contact.
So I closed the programs again. Restarted them. Problem remained from the beginning this time.
Restarted the computer. Everything cleared and worked. Then it happened again.
Closed program and restarted. Cleared the problem. A little while later it was back.

Reinstalled JTAlertX 2.12.10.

So far that problem has not reappeared.
I don't even know where to start to figure this one out. Very random.

Bob
W8RID


locked Re: JTAlertX 2.13.0 Update #FT8 #JTDX

Ed Wilson
 

I experienced a similar problem when using JTDX 2.0.2 rc133_2...went back to JTAlert 2.12.10 and things seem to be working fine.

Ed, K0KC

k0kc@...
http://k0kc.us/


On Saturday, March 9, 2019, 9:13:00 AM EST, Bob Davet <davet354tfd@...> wrote:


Weird issue here.
I upgraded today. Using JTDX and JTAlertX. Everything was seemingly working fine. Click on a call sign in JTAlertX and it triggered JTDX. Logged fine. Then clicked on a call sign and it triggered JTDX. The call sign did not come back to me right away  so JTDX kept calling. The call sign went into a QSO with another call. JTDX kicked the Enable TX out which it should. I waited for him or any other call sign to click on. Could not get JTAlertX to activate JTDX anymore. I could click on the callsign in JTDX and it functioned fine. JTAlertX was still showing call signs as it should but I couldnt get it to activate JTDX.
I closed JTDX and JTAlertX. Restarted them. That seemed to clear the problem or so I thought. Same issue started up again with another contact.
So I closed the programs again. Restarted them. Problem remained from the beginning this time.
Restarted the computer. Everything cleared and worked. Then it happened again.
Closed program and restarted. Cleared the problem. A little while later it was back.

Reinstalled JTAlertX 2.12.10.

So far that problem has not reappeared.
I don't even know where to start to figure this one out. Very random.

Bob
W8RID


locked JTAlertX 2.13.0 Update #FT8 #JTDX

Bob Davet
 

Weird issue here.
I upgraded today. Using JTDX and JTAlertX. Everything was seemingly working fine. Click on a call sign in JTAlertX and it triggered JTDX. Logged fine. Then clicked on a call sign and it triggered JTDX. The call sign did not come back to me right away  so JTDX kept calling. The call sign went into a QSO with another call. JTDX kicked the Enable TX out which it should. I waited for him or any other call sign to click on. Could not get JTAlertX to activate JTDX anymore. I could click on the callsign in JTDX and it functioned fine. JTAlertX was still showing call signs as it should but I couldnt get it to activate JTDX.
I closed JTDX and JTAlertX. Restarted them. That seemed to clear the problem or so I thought. Same issue started up again with another contact.
So I closed the programs again. Restarted them. Problem remained from the beginning this time.
Restarted the computer. Everything cleared and worked. Then it happened again.
Closed program and restarted. Cleared the problem. A little while later it was back.

Reinstalled JTAlertX 2.12.10.

So far that problem has not reappeared.
I don't even know where to start to figure this one out. Very random.

Bob
W8RID


locked Re: Version 2.13.0, cannot scan log after upgrade

John H. Long Jr.
 

How can we tell if we have the latest version of V2.13.0  ?
 
 
John H. Long Jr.
KW7A
1370 N 150 E
Nephi, UT 84648
USA
 
(435) 888-LONG
 
 

--------- Original Message ---------
Subject: Re: [HamApps] Version 2.13.0, cannot scan log after upgrade
From: "Dragan Djordjevic 4O4A" <dragan@...>
Date: 3/9/19 6:42 am
To: Support@HamApps.groups.io

On Sat, Mar 9, 2019 at 03:09 AM, HamApps Support (VK3AMA) wrote:
Dragan,

I have identified & corrected the issue and confirmed in Testing the ADIF import is now working.
Please download 2.13.0 again

de Laurie VK3AMA

Thanks, Laurie.

I also confirm - it is OK now!

 

Regards,
Dragan, 4O4A

13801 - 13820 of 37311