Date   

locked Re: Configuration Log4OM

HamApps Support (VK3AMA)
 

On 14/10/2020 11:38 pm, Paul F6EXV wrote:
I am new to JTAlert.
I am using (or trying to) version 2.16.14 with Windows10, JTDX and Log4OM.
I have followed 2 different tutorials, but my JTAlert screen remains empty ! I do not care about the sound alert.
It does communicate with the log : the test within the Log4OM menu is passed OK.
Obviously, I am missing something. The port numbers seam to be OK, according to those tutorials.
What else should I check ?

Thanks + 73
Paul F6EXV

Paul,

The JTAlert help file contains the setup instructions , they are very simple.

Likely you have Log4OM configured to directly interface with JTDX and it has taken exclusive control of the UDP server port preventing JTAlert from receiving the UDP data from JTDX. You posted error message indicates that you are not using multicast for the JTDX UDP server further suggesting that Log4OM is taking exclusive control of the UDP port.

I suggest you get the JTAlert - JTDX combination working first then bring Log4OM into the mix.

See the "WSJT-X / JTDX UDP Setup" topic. I strongly suggest you use a multicast IP address like 239.255.0.0
Followed by the "Settings -> Logging -> Log4OM V2" topic.

de Laurie VK3AMA



locked Re: Configuration

Paul F6EXV
 

Here is the error message I am getting, if that helps

Unable to communicate with the JTDX process.
  UDP Port : 2237
  IP Address : 127.0.0.1
  Values read from JTDX config file...
    C:\Users\Utilisateur\AppData\Local\JTDX\JTDX.ini

JTDX Detected Instance...
  Process Window Title : JTDX  by HF community                                         v2.2.0-rc152 , derivative work based on WSJT-X by K1JT
  Process Command Line : "C:\JTDX64\F4KMA\bin\jtdx.exe"

Decode alerts and logging will be unavailable until corrected.


End of quote

Le 14/10/2020 à 14:38, Paul F6EXV a écrit :
Hi all
I am new to JTAlert.
I am using (or trying to) version 2.16.14 with Windows10, JTDX and Log4OM.
I have followed 2 different tutorials, but my JTAlert screen remains empty ! I do not care about the sound alert.
It does communicate with the log : the test within the Log4OM menu is passed OK.
Obviously, I am missing something. The port numbers seam to be OK, according to those tutorials.
What else should I check ?

Thanks + 73
Paul F6EXV



Garanti sans virus. www.avast.com


locked For the attention of David MM0HVU

Paul F6EXV
 

Sorry David, my computer decided to totally eliminate your email (not even in the dustbin) before I could read it.
Please send again
Thank you + 73
Paul F6EXV

--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


locked Configuration Log4OM

Paul F6EXV
 

Hi all
I am new to JTAlert.
I am using (or trying to) version 2.16.14 with Windows10, JTDX and Log4OM.
I have followed 2 different tutorials, but my JTAlert screen remains empty ! I do not care about the sound alert.
It does communicate with the log : the test within the Log4OM menu is passed OK.
Obviously, I am missing something. The port numbers seam to be OK, according to those tutorials.
What else should I check ?

Thanks + 73
Paul F6EXV

--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


locked Re: Still have issue where Worked B4 sometimes not working properly

Paul AC9O
 

I am using automatic logging. Just clicking OK when the logging window comes up. Yes, the logging success popup comes up.

Thanks and 73
Paul, AC9O


locked Re: Still have issue where Worked B4 sometimes not working properly

HamApps Support (VK3AMA)
 

On 13/10/2020 2:03 am, Paul AC9O wrote:
I am still having an issue with Worked B4. In the screenshot, you can see I worked LY5O and logged it to ACLog.
On the next cycle, LY5O is still showing up even though it shows word in the QSO popup and in ACLog.

This doesn't always happen, I would say about 30-40 percent of the time. I have been using the new Temp Ignore feature to clear it.

Let me know if you need anything else.

Thanks for all your support.

73
Paul, AC9O

Paul,

Is JTAlert performing the automatic logging to ACLog or are you manually logging the QSO via the ACLog interface? If JTAlert is performing the logging, are you getting a logging success popup?

Please use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA



locked Still have issue where Worked B4 sometimes not working properly

Paul AC9O
 

I am still having an issue with Worked B4. In the screenshot, you can see I worked LY5O and logged it to ACLog.
On the next cycle, LY5O is still showing up even though it shows word in the QSO popup and in ACLog.

This doesn't always happen, I would say about 30-40 percent of the time. I have been using the new Temp Ignore feature to clear it.

Let me know if you need anything else.

Thanks for all your support.

73
Paul, AC9O


locked Re: WSJT-X failed to start-up after it had been running successfully with JT-Alert.

neil_zampella
 

As this is a WSJT-X issue it should be directed there.   As you have already done that I would suggest you take Bill's (G4WJS) advice since he's one of the developers:


Hi Lewis,

as an initial guess I would say your Ani-Virus software is doing something it shouldn't. Try adding an AV scanning exclusion (aka whitelisting) for the directory where you have installed WSJT-X.

73
Bill
G4WJS.


locked WSJT-X failed to start-up after it had been running successfully with JT-Alert.

pete3240 <pete3240@...>
 

When WSJT-X v2.2,2 was installed, under Windows 7, it ran fine and with JT-Alert.  After hours and on many occasions the programs were manually closed.  The next time WSJT-X was started from desk top short cut an error message "The application fail to start because Qt platform plugin could be initialized. Reinstalling may fix this problem." The program was stopped and reinstalled. WSJT-X ran perfectly again and with JT-Alert. Each time I stop WSJTX the same thing occurs. When WSJT-X is running everything is normal, only when it is restarted.

I anyone has a suggestion, or esperience of solving this problem I would appreciate a reply.
Lewis, K4BOI 


locked Re: WSJT-X

Michael Black
 

#1 How much memory is in your computer?
#2 How much memory does task manager show free?
#3 Can you send a "Snip & Sketch" grab of task manager results?
Mike W9MDB

Inline image




On Saturday, October 10, 2020, 07:08:44 AM CDT, Roy Davis <sivad1rm@...> wrote:


OBTW: I am running the latest windows 10.  We will see if the problem persists today and be able to give better reports.

73

K5RMD


locked Re: WSJT-X

Roy Davis
 

OBTW: I am running the latest windows 10.  We will see if the problem persists today and be able to give better reports.

73

K5RMD


locked Re: WSJT-X

neil_zampella
 

Again, what version of Windows are you running?   If Windows 10, is it updated to the latest updates?  Which version of WSJT-X?  

Did you try using the Contact Support link under the HELP menu to send Laurie a message along with your support files which would give him a very good idea of what's happening?

 

Neil, KN3ILZ


locked Re: WSJT-X

Roy Davis
 

This error happens in the newest download of JT Alert.  The version ending in .14

I do not have a screen shot available at this moment.  It probably will happen again tomorrow.

73 

Roy K5RMD


locked Re: WSJT-X

Dave Garber
 

maybe let the list know software version #'s, OS version and type, all software running when the error comes up, and a small screen shot??   Laurie and his crew may be able to tell right away
Dave Garber
VE3WEJ / VE3IE


On Fri, Oct 9, 2020 at 5:16 PM Roy Davis <sivad1rm@...> wrote:
This box has autolt in the upper left corner and comes from the newest version of JT Alert.  The box saying  trouble allocating memory.  JT Alert freezes and you have to close all programs connected with WSJT-X.  Then there is the command box to shut down JT Alert.  

I hope this better explains the malady.

73,

K5RMD


locked Re: WSJT-X

Roy Davis
 

This box has autolt in the upper left corner and comes from the newest version of JT Alert.  The box saying  trouble allocating memory.  JT Alert freezes and you have to close all programs connected with WSJT-X.  Then there is the command box to shut down JT Alert.  

I hope this better explains the malady.

73,

K5RMD


locked WSJT-X

Roy Davis
 

I am getting a message.......Trouble allocating memory?  What is that and how do I solve this?????

73

K5RMD


locked Re: Worked before stations not appearing

bob.k6rwm
 

Well, age got me, I did not notice the Worked B4 setting under Miscellaneous Alerts; sorry for the inconvenience.
It was not something I changed, and several other items got changed as well and I may lay blame to my recently installed Win10 update. The soundcard settings had changed in WSJT-X and JTAlert, HRD Logbook had a issue, etc.
Thanks for all you do in the development and tech support for your great app.

73.
B0b -- K6RWM


locked Re: Worked before stations not appearing

Chuck Adams
 

TO: BOB -- k6rwm

 

Did you check to see if perchance you accidently have the shading and the text the same color for an alert you have already set?

 

73,

 

Chuck Adams

KV4VT

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of bob.k6rwm
Sent: 7 October, 2020 6:50 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Worked before stations not appearing

 

Hi Laurie:
Indeed the UDP boxes were not checked. The UDP server was set at 127.0.0.1, with the port 2237. Checking the boxes did not resolve the problem. I am not sure why the problem cropped up as everything was fine during my last session. The problem also is in WSJT-X; an orange box with no callsign information. Here are the snips you requested.

Thanks.


locked Re: Lost "Calling Y0U"

HamApps Support (VK3AMA)
 

On 8/10/2020 2:12 am, Dave Tucker Nu4N wrote:
Installed the latest version and now I have audio tests ok but when I get a station calling me I get no "Callng You"
Any help will be appreciated.
73

--
DAVE NU4N
Visit the "Alerts -> Own Call" Alert in the Settings window and set a path to the desired sound file. (Hint: use the default button).

de Laurie VK3AMA


locked Re: Worked before stations not appearing

HamApps Support (VK3AMA)
 

On 8/10/2020 9:49 am, bob.k6rwm wrote:
Hi Laurie:
Indeed the UDP boxes were not checked. The UDP server was set at 127.0.0.1, with the port 2237. Checking the boxes did not resolve the problem. I am not sure why the problem cropped up as everything was fine during my last session. The problem also is in WSJT-X; an orange box with no callsign information. Here are the snips you requested.

Thanks.
_._,_._,_



The Orange boxes is an easy fix.
They are due to an Alert being triggered and that Alert has both the Text color and the Background color set to the same color.
You will need to visit the Settings window and find which Alert has had that orange coloring applied. This coloring is not due to the 2.16.14 release but due to some change you have made previously.

de Laurie VK3AMA

5321 - 5340 of 36984