Date   

locked Re: Timing Adjustment.

Jim Cooper
 


Click the line that says LOGGING ... not
one of the log selections ...  


On 14 Sep 2020 at 0:13, JoAnn Donaldson via groups.io wrote:

 I hate to say this but that menu does not exist on my JTALert. Here
is what it says on mine.


    On Sunday, September 13, 2020, 4:03:09 PM CDT, HamApps Support
(VK3AMA) <vk3ama.ham.apps@...> wrote:
 
  On 14/09/2020 6:17 am, JoAnn Donaldson via groups.io wrote:

I do not see any entry for Asjustment under Logging or under
Miscellaneous. Under Miscellaneous I see         Hot Keys
  Thats it. No Entry to adjust the Timing. Under Logging I see
          Last QSO API           Last B4 Database
          Standard ADIF File         + DXLAb DXkeeper
        HDR V5/V6         Log4OM V1        
Log4OM V2       +ACLog
 
 Click the "Logging" entry in the left tree-view display.
    
 
 de Laurie VK3AMA
 



  


locked Re: Decodes window and chrome remote desktop

HamApps Support (VK3AMA)
 

On 14/09/2020 8:49 am, rogich via groups.io wrote:
As soon as I remote DT into my win 10 box, decode window crashes with an exception when I click on it remotely. Says clipboard operation failed.
Everything else is ok. 
2.16.13, win 10 home 1909, RD 1.5, other end is Android 9 S6 tablet (also crashes on S10e). Nov 5,2019 version.
Also crashes on MacBook Air 2017 with Edge or Chrome extension.
Not a big issue. Just fyi


I remote desktop into my Ham PC 99.9% of the time, I rarely sit in front of the PC, without this problem. Admittedly I am not using Chrome. I am not sure what could be the cause. This is the first report I have received of this behavior.

How long since you restarted your Win10PC?

What part of the Decodes window are you clicking on?

Please post a capture of the error message window. That will help with diagnosis.

de Laurie VK3AMA


locked Re: Timing Adjustment.

HamApps Support (VK3AMA)
 

On 14/09/2020 10:13 am, JoAnn Donaldson via groups.io wrote:
I hate to say this but that menu does not exist on my JTALert. Here is what it says on mine.

Seriously!

Your image shows your not even selecting the "Logging" entry as has been advised several times.
You have selected the "Standard ADIF File" entry (blue/white highlight)


Select the "Logging" entry pointed to by the big red arrow.

If you don't get the "Logging" entry highlighted you have not selected it. Like so...


de Laurie VK3AMA


locked Re: JT Alert intermittent

James Bricker <jhbricker@...>
 

Thanks Jim N6VH

Updating to 2.16.13 solved the problem of intermittent announcements.

Virus-free. www.avast.com


locked Re: JT Alert intermittent

James Bricker <jhbricker@...>
 

It totally ignores my call sign.  No highlighting or change of color and doesn't play the .wav file.  Other times it works fine.  No detectable pattern to when it works or doesn't.
When it does work it often picks up on the call sign when the other person sends a 73.

Virus-free. www.avast.com


locked Re: Timing Adjustment.

JoAnn Donaldson
 

I hate to say this but that menu does not exist on my JTALert. Here is what it says on mine.Inline image


On Sunday, September 13, 2020, 4:03:09 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 14/09/2020 6:17 am, JoAnn Donaldson via groups.io wrote:
I do not see any entry for Asjustment under Logging or under Miscellaneous.
Under Miscellaneous I see
        Hot Keys

Thats it. No Entry to adjust the Timing. Under Logging I see
          Last QSO API
          Last B4 Database
          Standard ADIF File
        + DXLAb DXkeeper
        HDR V5/V6
        Log4OM V1
        Log4OM V2
      +ACLog

Click the "Logging" entry in the left tree-view display.
   

de Laurie VK3AMA


locked Re: JTAlert unable to confirm QSO logged

Jake Groenhof
 

Thanks, Laurie. A simple checking of the TCP box did it.


locked Decodes window and chrome remote desktop

rogich@...
 

As soon as I remote DT into my win 10 box, decode window crashes with an exception when I click on it remotely. Says clipboard operation failed.
Everything else is ok. 
2.16.13, win 10 home 1909, RD 1.5, other end is Android 9 S6 tablet (also crashes on S10e). Nov 5,2019 version.
Also crashes on MacBook Air 2017 with Edge or Chrome extension.
Not a big issue. Just fyi


locked Re: JTAlert unable to confirm QSO logged

HamApps Support (VK3AMA)
 

On 14/09/2020 6:54 am:
I cannot get WSJT-X, JTAlert and AC Logger to work together to log QSOs. A message pops up:
ERROR Message: ACLOG File: unable to confirm QSO logged. I assume there is a simple fix, but would appreciate some direction.
Is this a JTAlert issue or ACLog?

OM,

Does the QSO actually get logged in ACLog despite the error message?
  • If yes, see the Help File, "Frequently Asked Questions -> Warning about QSO not logged when it is logged" topic.

  • If No, see the Help File, "Settings -> Logging -> ACLog" topic. ACLog must be running and have its TCP API enabled.

de Laurie VK3AMA


locked Re: JTAlerts - WSJT-X communications failure

HamApps Support (VK3AMA)
 

On 13/09/2020 11:23 pm, Mike Cooper wrote:
Thank for the info 239.255.0.0 is working. I did have it set to 192.168.0.17 and that had been working since this past January up until yesterday. I tried 192.168.0.8 but that did not work,as well. If the firewall is blocking that I have been unable to find out how to fix it.

Thanks 
73

Mike - W7OSG

Mike,

Thanks for reporting that using multicast is working.

JTAlert doesn't listen to specific IP addresses, it listens to all addresses defined on your PC network interface.
My guess is that
192.168.0.17 and 192.168.0.8 while being valid for your local Lan, my not be defined for your PC network interface.

de Laurie VK3AMA


locked Re: JTAlerts - WSJT-X communications failure

HamApps Support (VK3AMA)
 

On 13/09/2020 3:05 am, g4wjs wrote:

either JTAlert is not listening for connections on your local subnet (192.168.0/8) or your firewall is blocking it. Since JTAlert requires that WSJT-X be run on the same host as itself you should use either 127.0.0.1 or better still a suitable multicast group IP address like 239.255.0.0. Set that in WSJT-X "Settings->Reporting->UDP Server".

--
73
Bill
G4WJS.
Bill,

My guess it is a firewall/pc protection issue.

JTAlert doesn't listen to any explicit IP, or subnet. The socket binds to a local endpoint using IPAddress.Any
The relevant code...
var localEp = new IPEndPoint(IPAddress.Any, port);
serverSocket.Bind(localEp);
de Laurie VK3AMA


locked Re: Timing Adjustment.

HamApps Support (VK3AMA)
 

On 14/09/2020 6:17 am, JoAnn Donaldson via groups.io wrote:
I do not see any entry for Asjustment under Logging or under Miscellaneous.
Under Miscellaneous I see
        Hot Keys

Thats it. No Entry to adjust the Timing. Under Logging I see
          Last QSO API
          Last B4 Database
          Standard ADIF File
        + DXLAb DXkeeper
        HDR V5/V6
        Log4OM V1
        Log4OM V2
      +ACLog

Click the "Logging" entry in the left tree-view display.
   

de Laurie VK3AMA


locked JTAlert unable to confirm QSO logged

Jake Groenhof
 

I cannot get WSJT-X, JTAlert and AC Logger to work together to log QSOs. A message pops up:
ERROR Message: ACLOG File: unable to confirm QSO logged. I assume there is a simple fix, but would appreciate some direction.
Is this a JTAlert issue or ACLog?


locked Re: Timing Adjustment.

Jim Cooper
 


graphic

On 13 Sep 2020 at 20:17, JoAnn Donaldson via groups.io wrote:

> Sorry about the images sizes. I do not see any entry for Asjustment
> under Logging or under Miscellaneous.
> Under Miscellaneous I see
>         Hot Keys
>
>
> Thats it. No Entry to adjust the Timing. Under Logging I see
>           Last QSO API
>           Last B4 Database
>           Standard ADIF File
>         + DXLAb DXkeeper
>         HDR V5/V6
>         Log4OM V1
>         Log4OM V2
>       +ACLog
>
>
> Again nothing about Timing Adjustment.
>
>
> I am using JTALert V 2.16.13

  


locked Re: Timing Adjustment.

JoAnn Donaldson
 

Sorry about the images sizes. I do not see any entry for Asjustment under Logging or under Miscellaneous.
Under Miscellaneous I see
        Hot Keys

Thats it. No Entry to adjust the Timing. Under Logging I see
          Last QSO API
          Last B4 Database
          Standard ADIF File
        + DXLAb DXkeeper
        HDR V5/V6
        Log4OM V1
        Log4OM V2
      +ACLog

Again nothing about Timing Adjustment.

I am using JTALert V 2.16.13


JoAnn Donaldson - AB8YZ


On Saturday, September 12, 2020, 3:56:51 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 13/09/2020 3:31 am, JoAnn Donaldson via groups.io wrote:
Reading the JTAlert Docs, it mentions that you can adjust the how to adjust the Check QSO Log Record time in JTAlert' but I can not find it under Settings/Manage Settings/Misc. See the two attach files. One shows it. This is from the N3FJP Digital Hits Page and the other which does not show it is from Settings/Manage Settings/MISc. has this setting been removed? I am having problems with JTAlert not confirming contact with my ACLog.

JoAnn - AB8YZ

First some housekeeping. Please don't post cell-phone images they typically end up being excessively large in both physical size and dimensions. A better option is to use the tools provided by Windows to capture an individual window or part of a window, see this pinned topic https://hamapps.groups.io/g/Support/message/20528

If you insist on using cell-phone images, take the time to reduce the size before posting. You current image size of ~4MB at 4096 x 2304 pixels is unnecessarily large. For an image like this, it doesn't need to be any more than ~500px in width with a more manageable less than 100KB file size.

Regarding the timing adjustment setting, it is under the Logging section of the Settings window. Documented under the "Frequently Asked Questions -> Warning about QSO not logged when it is logged" help file topic.

From the Logging section of the Settings...


de Laurie VK3AMA


locked Re: JTAlerts - WSJT-X communications failure

John L. Broughton
 

I was having this problem with v. 2.16.6, so I re-installed v. 2.16.5 and the problem disappeared.

One problem I have had with most all versions is, for some reason, the voice notification function stops or doesn't work at startup. I test the voice alert function to make sure it isn't working, then, I just close and reopen the program. That usually fixes it, but one or two times I had to do it twice. It is a little annoying, but not a major concern for me.

73,

John, WB9VGJ

On 9/12/2020 9:56 AM, Michael wrote:
I get the following error message The JTAlerts help file and the "About"  for 2.16.13 listing do  not match so I cannot see what is wrong. Windows ten updated last week to the listing below






Mike W7OSG

Virus-free. www.avg.com


locked Re: GB1COR

Jim N6VH
 


On 9/12/2020 7:31 PM, HamApps Support (VK3AMA) wrote:
On 12/09/2020 6:44 am, Jim N6VH wrote:
I just looked, and I don't see Shetland Islands in the Marathon list in JTAlert. Laurie might want to fix that.

73,

Jim
All WAE entities are grouped at the head of the alphabetic dxcc names listing.



de Laurie VK3AMA


Laurie,

Yes, sorry. When I started looking, I just went down to the "S" part of the list, and skipped everything above.

73,

Jim N6VH


locked Re: JTAlerts - WSJT-X communications failure

Mike Cooper
 

Bill,

Thank for the info 239.255.0.0 is working. I did have it set to 192.168.0.17 and that had been working since this past January up until yesterday. I tried 192.168.0.8 but that did not work,as well. If the firewall is blocking that I have been unable to find out how to fix it.

Thanks 
73

Mike - W7OSG


locked Re: GB1COR

HamApps Support (VK3AMA)
 

On 12/09/2020 6:44 am, Jim N6VH wrote:
I just looked, and I don't see Shetland Islands in the Marathon list in JTAlert. Laurie might want to fix that.

73,

Jim
All WAE entities are grouped at the head of the alphabetic dxcc names listing.



de Laurie VK3AMA


locked Re: GB1COR

Jim N6VH
 


On 9/12/2020 9:03 AM, John Holmes W9ILY wrote:
It's at the very top of the Marathon list, Jim. Just another call to add to the database.
John W9ILY
_._,_._,_


John,

Yes, that's why I didn't see it. I was looking for Shetland in the "S" section of the list. My mistake.

73,

Jim N6VH