Date   

locked Re: New JTAlert 2.13.4 available.

Carey, WB4HXE
 

Laurie,
Thank you for this amazing piece of software and your incredible ability to turn on a dime to support new developments in the other apps!
73, Carey, WB4HXE

On Wed, May 1, 2019 at 11:14 AM Howard W6HDG <w6hdg@...> wrote:
Laurie, 
Thank you for all you do. I can't believe you updated for FT4 call sign display within hours. Amazing.  You deserve a raise :) 

73, Howard W6HDG 



--
Carey Fisher


locked Re: New JTAlert 2.13.4 available.

Howard W6HDG
 

Laurie, 
Thank you for all you do. I can't believe you updated for FT4 call sign display within hours. Amazing.  You deserve a raise :) 

73, Howard W6HDG 


locked Re: New JTAlert 2.13.4 available.

Michael Black
 

Thanks ever-so-much for the FT4 capability Laurie.  Helps a lot during the testing.....

It appears the CQ "*" and "#" indicators are not working for FT4.

de Mike W9MDB


locked Re: UDP Error With JTDX

Ed Wilson
 

Thanks, Laurie!

I may go back to 2.13.2 although I have been testing FT4 and would like to have the changes that you  made to at least partially accommodate that mode. Take  your time...I am patient!

Ed, K0KC

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


On Wednesday, May 1, 2019, 8:16:38 AM EDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 1/05/2019 8:22 pm, Ed Wilson via Groups.Io wrote:
Here is the screen shot:

Inline image


Ed, K0KC
OK, I have been able to replicate the problem.
It is caused by the 2.13.2 changes made to work with 64bit WSJT-X when it is using a --rig-name parameter.

Until I release a new JTAlert build, you will need to run JTDX without a --rig-name parameter or stay with 2.13.2

de Laurie VK3AMA


locked New JTAlert 2.13.4 available.

Bob WB2NVR
 

TNX for the quick release of this update, Laurie.

The new release works FB.  Amazing how lost I felt using FT4 without JTAlert showing B4!

JTAlert and DXKeeper, along with WSJT, are great programs, and the support is phenomenal.

I just wanted to say Thank You one more time - I really appreciate all your hard work to make this software available.

73 ES GUD DX,

Bob WB2NVR


locked Re: FT4

Neil Foster
 

Hello Neil
Glad to see we both spell our name correctly!  
No it was on 20 meters

Neil    N4FN


locked Re: UDP Error With JTDX

HamApps Support (VK3AMA)
 

On 1/05/2019 8:22 pm, Ed Wilson via Groups.Io wrote:
Here is the screen shot:




Ed, K0KC
OK, I have been able to replicate the problem.
It is caused by the 2.13.2 changes made to work with 64bit WSJT-X when it is using a --rig-name parameter.

Until I release a new JTAlert build, you will need to run JTDX without a --rig-name parameter or stay with 2.13.2

de Laurie VK3AMA


locked Re: UDP Error With JTDX

Ed Wilson
 

Laurie,

FYI, I am not using the 64-bit compiled version of WSJT-X (The error occurs with JTDX) but I am usiing a --rig-name parameter for JTDX.

Ed, K0KC

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


On Wednesday, May 1, 2019, 5:29:15 AM EDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 1/05/2019 7:00 pm, Ed Wilson via Groups.Io wrote:
When using 2.13.3 with JTDX I get a UDP setup error message which I do not get with 2.13.2. I am using JTDX v2.0.1-rc136_10 which worked fine with JTAlert 2.13.2.


Please post an image of the error window (not your entire desktop), I need to see the detail presented in the dialog.

It may be related to the change made in 2.13.3.
    - Not reading correct WSJT-X config file for 64bit compiled versions of
       WSJT-X running with a --rig-name parameter.

de Laurie VK3AMA


locked Re: UDP Error With JTDX

Ed Wilson
 

Laurie,

Here is the screen shot:

Inline image


Ed, K0KC

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


On Wednesday, May 1, 2019, 5:29:15 AM EDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 1/05/2019 7:00 pm, Ed Wilson via Groups.Io wrote:
When using 2.13.3 with JTDX I get a UDP setup error message which I do not get with 2.13.2. I am using JTDX v2.0.1-rc136_10 which worked fine with JTAlert 2.13.2.


Please post an image of the error window (not your entire desktop), I need to see the detail presented in the dialog.

It may be related to the change made in 2.13.3.
    - Not reading correct WSJT-X config file for 64bit compiled versions of
       WSJT-X running with a --rig-name parameter.

de Laurie VK3AMA


locked Re: UDP Error With JTDX

HamApps Support (VK3AMA)
 

On 1/05/2019 7:00 pm, Ed Wilson via Groups.Io wrote:
When using 2.13.3 with JTDX I get a UDP setup error message which I do not get with 2.13.2. I am using JTDX v2.0.1-rc136_10 which worked fine with JTAlert 2.13.2.

Please post an image of the error window (not your entire desktop), I need to see the detail presented in the dialog.

It may be related to the change made in 2.13.3.
    - Not reading correct WSJT-X config file for 64bit compiled versions of
       WSJT-X running with a --rig-name parameter.

de Laurie VK3AMA


locked Re: UDP Error With JTDX

Anton Iriawan
 

Same problem here with JTDX v2.0.1 rc136-10 with JTalert 2.13.3 and 2.13.4, now downgrade back to 2.13.2 which worked fine.

 

73

Anton – YB5QZ

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Ed Wilson via Groups.Io
Sent: Rabu, 01 Mei 2019 16.01
To: Hamapps Groups Support <support@hamapps.groups.io>
Subject: [HamApps] UDP Error With JTDX

 

Laurie,

 

I am having the same problem with 2.13.4...any suggestions?

 

Laurie,

 

When using 2.13.3 with JTDX I get a UDP setup error message which I do not get with 2.13.2. I am using JTDX v2.0.1-rc136_10 which worked fine with JTAlert 2.13.2.

 

 

 

 


locked Re: UDP Error With JTDX

Ed Wilson
 

By the way, both 2.13.3 and 2.13.4 work fine with WSJT-X.

Ed, K0KC

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


On Wednesday, May 1, 2019, 5:00:54 AM EDT, Ed Wilson via Groups.Io <ed.wilson@...> wrote:


Laurie,

I am having the same problem with 2.13.4...any suggestions?

Laurie,

When using 2.13.3 with JTDX I get a UDP setup error message which I do not get with 2.13.2. I am using JTDX v2.0.1-rc136_10 which worked fine with JTAlert 2.13.2.

Ed, K0KC

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



Ed, K0KC

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


locked UDP Error With JTDX

Ed Wilson
 

Laurie,

I am having the same problem with 2.13.4...any suggestions?

Laurie,

When using 2.13.3 with JTDX I get a UDP setup error message which I do not get with 2.13.2. I am using JTDX v2.0.1-rc136_10 which worked fine with JTAlert 2.13.2.

Ed, K0KC

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



Ed, K0KC

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


locked Re: New JTAlert 2.13.4 available.

Tom WA9WSJ
 

Thank You!


PS, I like your sense of humor!



On Tuesday, April 30, 2019, 9:28:54 PM MDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 1/05/2019 12:24 pm, Tom WA9WSJ via Groups.Io wrote:
I normally download the current version of programs to keep up with the newest and greatest, but I would like to verify something.

I'm not using FT4 so, if I use this new version 2.13.4, will I still need to delete the two files you mention below?

I'm thinking yes.

thanks,

Tom wa9wsj
Tom,

You should be ok with not deleting the databases.
If in the future you decide to test FT4 and observe the lack of entries in the Decodes History, stop JTAlert, delete the databases and start up JTAlert, they will be auto-created. Due to the fast-track nature of the release, I didn't have time to code and test suitable database update routines, so deleting the files was the quick solution, just like this release was a quick solution to stop the flow of support requests hitting my inbox ;)

de Laurie VK3AMA


locked Re: New JTAlert 2.13.4 available.

HamApps Support (VK3AMA)
 

On 1/05/2019 12:24 pm, Tom WA9WSJ via Groups.Io wrote:
I normally download the current version of programs to keep up with the newest and greatest, but I would like to verify something.

I'm not using FT4 so, if I use this new version 2.13.4, will I still need to delete the two files you mention below?

I'm thinking yes.

thanks,

Tom wa9wsj
Tom,

You should be ok with not deleting the databases.
If in the future you decide to test FT4 and observe the lack of entries in the Decodes History, stop JTAlert, delete the databases and start up JTAlert, they will be auto-created. Due to the fast-track nature of the release, I didn't have time to code and test suitable database update routines, so deleting the files was the quick solution, just like this release was a quick solution to stop the flow of support requests hitting my inbox ;)

de Laurie VK3AMA


locked Re: New JTAlert 2.13.4 available.

Tom WA9WSJ
 

Hello Laurie,

I normally download the current version of programs to keep up with the newest and greatest, but I would like to verify something.

I'm not using FT4 so, if I use this new version 2.13.4, will I still need to delete the two files you mention below?

I'm thinking yes.

thanks,

Tom wa9wsj




On Tuesday, April 30, 2019, 5:10:57 PM MDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


The Latest JTAlert version 2.13.4 is now available @ https://HamApps.com

This release has two fixes for FT4, please review the release notes.
It is important that Decodes History users delete their old databases.

The Release Notes...
  *** Important Note:
  *** Decodes History users will need to manually delete two database files
  *** before running this version for the first time. This only needs to be
  *** done once. Old decodes in the History will be lost.
  *** Using Windows File Explorer delete "decodes.sqlite" and "lookup.sqlite"
  *** which are located at %localappdata%\HamApps\JTAlert\YOUR_CALLSIGN\Decodes\
  ***
  *** FT4 support is only partial. There is no Alerting for F4 DXCCs, States, etc.
  *** Accurate FT4 B4 checks and FT4 logging are fully supported.

  Fixes:
    - FT4 Callsigns not being displayed in the Callsign display.
    - FT4 decodes not being displayed in the Decodes History window.

de Laurie VK3AMA


locked Re: FT4

neil_zampella
 

What band ?? If you're talking 40 meters early evening, that's because the frequency being used is near the ARRL's W1AW CW code broadcasts.   Didn't realize how close they were when they chose it.

Problem is finding a 40m area that's available.

 

Neil, KN3ILZ


locked FT4

Neil <n4fn.neil@...>
 

I have downloaded the new version of JTAlert (.4) and I have only listened to FT4 and not tried to TX. I notice a periodic tone  happening and wonder if this is generated by JTAlert or is it from WSJT-X? I never had that before
Thanks Laurie for a great program addition and support
Neil   N4FN


locked New JTAlert 2.13.4 available. FT4 fixes. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The Latest JTAlert version 2.13.4 is now available @ https://HamApps.com

This release has two fixes for FT4, please review the release notes.
It is important that Decodes History users delete their old databases.

The Release Notes...
  *** Important Note:
  *** Decodes History users will need to manually delete two database files
  *** before running this version for the first time. This only needs to be
  *** done once. Old decodes in the History will be lost.
  *** Using Windows File Explorer delete "decodes.sqlite" and "lookup.sqlite"
  *** which are located at %localappdata%\HamApps\JTAlert\YOUR_CALLSIGN\Decodes\
  ***
  *** FT4 support is only partial. There is no Alerting for F4 DXCCs, States, etc.
  *** Accurate FT4 B4 checks and FT4 logging are fully supported.

  Fixes:
    - FT4 Callsigns not being displayed in the Callsign display.
    - FT4 decodes not being displayed in the Decodes History window.

de Laurie VK3AMA


locked Re: FT4 Decodes History Widow v0.1.5

Hasan Schiers N0AN
 

Thanks so much, Laurie
73, N0AN
Hasan


On Tue, Apr 30, 2019 at 4:02 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 1/05/2019 12:34 am, Hasan Schiers N0AN wrote:
I do hope that you will retain what does work

I will. Except for some exceptional situations, I have always tried to retrain existing functionality within JTAlert as it is extended.
The existing FT4 logging will remain. There will be further JTAlert changes to accommodate FT4, whether they include full alerting (by Band/Mode) like FT8/JT65/JT9 is unknown at this time.

de Laurie VK3AMA

13241 - 13260 of 37225