Date   

locked Re: Empty Callsign box

Michael Black
 

You don't need the secondary UDP server.  Turn it off.
JTAlert does all the talking to ACLog.

Mike W9MDB




On Thursday, July 29, 2021, 07:52:01 AM CDT, Gilles beaulieu <ve3npi@...> wrote:


Hi Laurie, I think I have followed the steps you mentioned but still no further ahead. The problem still persist. If ACLog starts first and locks everything like you mentioned, is there a way that I could "unlock" it so that it would work? Just a thought.
I'm also sending you a pic, maybe you can figure it out.
Thanks
Gilles VE3NPI


locked Re: Empty Callsign box

Gilles beaulieu
 

Hi Laurie, I think I have followed the steps you mentioned but still no further ahead. The problem still persist. If ACLog starts first and locks everything like you mentioned, is there a way that I could "unlock" it so that it would work? Just a thought.
I'm also sending you a pic, maybe you can figure it out.
Thanks
Gilles VE3NPI


locked JTAlert and WSJTX in linux

Adrian Fewster <vk4tux@...>
 

I have JTAlert installed under crossover in debian 10 and also have linux wsjtx 2.5.0rc3 running.
JTAlert is waiting to see wsjtx to start before it will continue startup.
What is the detection method please, as I thought the udp port activity may have been the trigger ?

73

vk4tux


locked Re: Empty Callsign box

HamApps Support (VK3AMA)
 

On 29/07/2021 12:26 pm, Gilles beaulieu wrote:
Hi, just reinstalled everything (system crash)I have ACLog, WSJT-X running perfectly. I can save contacts no problems. The only problems that I have is, does not tell me if the contact was saved or not (no pop up window) and I don't get anything showing up in the Callsign box. That's the box where you see Callsign #1 and 1. callers and 2 Alerts only.
Any help would be appreciated.
Thanks
Gilles VE3NPI

If the Callsigns window is not being populated it will be because JTAlert is not receiving UDP traffic from WSJT-X. The same applies to JTAlert not showing the logging confirmation window, if it never sees the UDP logging message it wont log to ACLog and will not display a confirmation/failure popup because it didn't perform the logging as it was unaware that WSJT-X logging took place.

It sounds like you have WSJT-X set for unicast UDP, using 127.0.0.1 on port 2237 (the default values) and that ACLog has taken exclusive control of the UDP port effectively locking JTAlert out because it was started before JTAlert.

If you want to have both ACLog and JTAlert working with WSJT-X concurrently, you need to have WSJT-X configured to use multicast UDP. Use the JTAlert "Help -WSJT-X UDP Setup" menu to bring up the relevant section in the help file, it contains very simple 4 step instructions with pictures on how to enable multicast UDP in WSJT-X.

de Laurie VK3AMA


locked Re: Decode line not appearing after upgrade to 2.50.4

Jim Nortron
 

Following this. I’m trying to help a friend with this problem as to the Call Signs Window. He logs with HRD, with no problem though. WD4T 


locked Empty Callsign box

Gilles beaulieu
 

Hi, just reinstalled everything (system crash)I have ACLog, WSJT-X running perfectly. I can save contacts no problems. The only problems that I have is, does not tell me if the contact was saved or not (no pop up window) and I don't get anything showing up in the Callsign box. That's the box where you see Callsign #1 and 1. callers and 2 Alerts only.
Any help would be appreciated.
Thanks
Gilles VE3NPI


locked Re: JTAlert 2.50.4

Laurie, VK3AMA
 

On 29/07/2021 10:44 am, charles miller wrote:
JTAlert 2.50.4 N2BTX [???M,,NO LOG, #1]
The "???M" in the titlebar text indicates that JTAlert has net established UDP comms with WSJT-X. I suggest using the JTAlert "Help -> WSJT-X UDP Setup" menu and follow the simple setup instructions provided for configuring Multicast UDP in WSJT-X and JTAlert.

de Laurie VK3AMA


locked Re: JTAlert 2.50.4

HamApps Support (VK3AMA)
 

On 29/07/2021 10:44 am, charles miller wrote:
I downloaded the JTAlert 2.50.4 program, however, I only get the header showing: JTAlert 2.50.4 N2BTX [???M,,NO LOG, #1] Alert   Settings   View   Sound On    Help

The is no grid or call signs. 

Need to know how to fix this issue.

Thanks

Charlie  N2BTX

There is nothing to fix. The Callsigns display grid of the main JTAlert window was replaced with a no-callsign-limit resizable window starting with version 2.50.0

de Laurie VK3AMA


locked Re: JTAlert 2.50.4

John
 

Have you installed net framework 5 or above?

John


On Wed, Jul 28, 2021 at 6:16 PM charles miller <ltcolcwmiller@...> wrote:
I downloaded the JTAlert 2.50.4 program, however, I only get the header showing: JTAlert 2.50.4 N2BTX [???M,,NO LOG, #1] Alert   Settings   View   Sound On    Help

The is no grid or call signs. 

Need to know how to fix this issue.

Thanks

Charlie  N2BTX
                                               


locked JTAlert 2.50.4

charles miller
 

I downloaded the JTAlert 2.50.4 program, however, I only get the header showing: JTAlert 2.50.4 N2BTX [???M,,NO LOG, #1] Alert   Settings   View   Sound On    Help

The is no grid or call signs. 

Need to know how to fix this issue.

Thanks

Charlie  N2BTX
                                               


locked Re: 13 Second Lag Between Visual and Audible Alert #FT8

HamApps Support (VK3AMA)
 

On 26/07/2021 4:33 am, HamApps Support (VK3AMA) via groups.io wrote:
On 26/07/2021 12:25 am, Glen Jenkins WB4KTF wrote:
The Sound Play Limit was set at 'NO LIMIT', so that is not the cause.
I'll continue to test various things and report back when I figure more out.
I did try rebooting the Surface and restarting both WSJT-X and JTAlert, no change so far.
The alert sound still starts to play at the 10-11th second of the following cycle after the decode in WXJT-X and Callsigns/All Decodes window is filled.
--
Glen, WB4KTF, Austin, TX


Glen,

I previously asked but got no answer...
Does using the "Sound -> Test Sound Output" menu produce the same delay?
This question is important. The test function uses the same code and an identical execution path though JTAlert to the Manager process (that plays the audio) as that used by Sound events when an Alert is triggered. If there is a delay it should also show up in that test.

Using your config in my tests produced no sound play delays. All looks normal in your session files except there is only a very small number of sound play events. That is likely because you have CQ only filtering enabled and some of the enabled Alerts don't have a sound file set.
Does turning off the "CQ Only" filter fixed the audio lag?

I personally can't fault your config. I left thinking that due to the low number of sound play events that you may be misinterpreting the sounds that do play as being from an earlier period.

I also note a very large number of Internet timeout errors when spots are being uploaded to HamSpots and when checking the online for messages status of decoded callsigns. Do you have a flaky or very slow Internet connection? Not that it should matter as the sound play is on a different, independent, code thread from that used for uploading spots. A timeout on one should not affect the other, but I could be wrong, there may be an unidentified defect in the code. Try turning off spotting to HamSpots and turning of Messaging. Turn off Messaging via the main JTAlert window Settings.

   

de Laurie VK3AMA



locked Re: JT Alert not ready for prime time

John
 

One straw short of a load...

John
VE7KKQ


On Tue, Jul 27, 2021 at 8:50 PM neil_zampella <neilz@...> wrote:

There's another phrase from my military days .. "Short between the headsets".

Neil, KN3ILZ


locked Re: JT Alert not ready for prime time

neil_zampella
 

There's another phrase from my military days .. "Short between the headsets".

Neil, KN3ILZ


locked Re: JTAlert is famous. 2 new QEX Japan articles and another Funk Amateur article.

Jim W
 

Laurie, it is well deserved. You have helped so many hams achieve their goals and dreams, in Amateur Radio, with the assistance of JTAlert, and that includes me as well!!!. Hip Hip Hooray!!! 😊

 

Jim VA3XOV

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: July 26, 2021 10:52 PM
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlert is famous. 2 new QEX Japan articles and another Funk Amateur article.

 

What a surprise when I visited my local post office today, after being stuck at home the last 3 weeks under a Covid lockdown imposed on a few million of us here in Melbourne VK.

Two issues of QEX Japan with very lengthy 10 page reviews of JTAlert in both issues. Also a new issue of Funk Amateur with a second article about JTAlert.

While, I cannot read Japanese or German I can tell that a lot of effort was put into the articles.

I want to thank Masa JR1AQN and Willi DJ6JZ for their efforts in writing the JTAlert reviews and getting them published.

Thanks very much guys!
73
de Laurie VK3AMA

 


Scanned by McAfee and confirmed virus-free.

 


locked Re: Question and suggestion about Ignore B4 Status before this date

HamApps Support (VK3AMA)
 

On 26/07/2021 11:16 am, Paul AC9O wrote:
Thanks for a wonderful program. It works great for me and I have few problems, usually solved by someone here in this forum.

I use the Ignore B4 Status Before This Date so that when I work someone and a QSL has not been received, I have the opportunity after some time for another QSO. I find I have to remember to change the date regularly to keep it at a useful interval.

I am curious as to why a specific date is specified instead of a number of days. I would set it to 25 or 30 days and wouldn't have to keep going back to advance the Ignore B4 Date. Perhaps an either date or #days option in a future release?

Thanks again!
73
Paul, AC9O

Paul,

Having the B4 check based on the age of the QSOs rather than a fixed date has been on my todo list for quite a while now.
The good news is that I have pulled out my finger and got it coded. It will be in the next release. Check your email I have sent you a link to a new test build to test.

de Laurie VK3AMA


locked Re: JT Alert not ready for prime time

HamApps Support (VK3AMA)
 

On 28/07/2021 12:35 am, Radio K0HB wrote:
Bravo Zulu to Laurie.




BTW I know what that means.
It brought back memories of my days as a Cadet Midshipman in the RAN running around the Quarterdeck at HMAS Creswell (RAN Naval College) hoisting signal flags. My service was short however, I left the RAN to pursue opportunities outside the military.

de Laurie VK3AMA


locked Re: Call sign Window - Clearing Eacht Time a QSO is Logged

HamApps Support (VK3AMA)
 

On 28/07/2021 7:11 am, Greg Foster wrote:

I am running Ver. 2.50.4 and using Standard ADIF File for logging. Recently the Call Sign window clears once I click the WSJT-X Confirm QSO window. This happens whether or not I have the JTAlert logging confirmation turned on.  

 

Have I click something or is this the way it is supposed to run?

 

Greg Foster

VE3PJ

Cell   613-328-6538


Turn off "Clear Callsigns display after logging" in the JTAlert settings window, Logging section. You will need to scroll the "Logging Options" to bring the setting into view.

   

de Laurie VK3AMA



locked Re: jt alert not working.

HamApps Support (VK3AMA)
 

On 28/07/2021 5:13 am, deni wrote:
Hey all,

I am trying to get jtalert working with jtdx.  At this point I am being unsuccessful.  I have used the standard setup under reporting in jtdx, but stilll nothing happens.  It just sets there and does nothing.  I am a little lost with jtalert.

Any help appreciated

73 - deni
WBØTAX
Likely you have ACLog set to work with JTDX/WSJT-X directly. Per your image, you're using unicast UDP (127.0.0.1) on port 2237 and it is likely that ACLog has taken exclusive control of the port preventing JTAlert from receiving UDP data from JTDX/WSJT-X. You can confirm this by stopping ACLog then restarting JTAlert, it should start reporting the Band and Mode in the titlebar and displaying decoded Callsings.

ACLog supports multicast comms with JTDX/WSJT-X. Switch JTDX/WSJT-X to using multicast and change ACLog accordingly. Use the JTAlert "Help -> WSJT-X UDP Setup" menu to bring up the help file. Follow the simple 4 seep instructions provided.

de Laurie VK3AMA


locked Re: jt alert not working.

deni
 


David, I am not sure either, but there are no filters turned on and it is not decoding or passing along log info to ACL.  Have never had this problem before.

I am going to give a detailed version as I understand it to keep Jim Cooper happy.

The current computer I am using is brand new.  Has a fresh install of jtdx with the pertinent.  jtdx seems to be working just fine.  It logs to itself, so contacts are updated in the *.adif file.  It seems that jtalert is not decoding at all and as a result is not logging to ACL.
After the clean install I did copy the files per the help file to the new computer, hoping to keep my old databases.  This has provided no luck either.

So Mr. Cooper, I am no longer on a Mountain top in Colorado asking for help.  In the previous message I sent a photo of the jtdx udp setup.  I do believe it to be correct.

Still at wits end.
deni
WBØTAX

It also has a fresh install of 2.50.1 upgraded to 2.50.4

On 7/27/2021 3:12 PM, DAVID MM0AMW via groups.io wrote:
Deni,


I'm not sure why the title bar isn't showing which band you're on but it looks like you have some filter/filters enabled which may be blocking any decodes showing in the Callsign window. Click Alerts from the menu and then check the Filters menu to see what filters you have enabled.


73

David

MM0AMW


------ Original Message ------ From: "deni" <deni@...> To: support@hamapps.groups.io Sent: Tuesday, 27 Jul, 21 At 20:13 Subject: [HamApps] jt alert not working. Hey all, I am trying to get jtalert working with jtdx. At this point I am being unsuccessful. I have used the standard setup under reporting in jtdx, but stilll nothing happens. It just sets there and does nothing. I am a little lost with jtalert. Any help appreciated 73 - deni WBØTAX


locked Re: jt alert not working.

Joe Subich, W4TV
 

Since your title bar shows "???m", the most likely issue is that
UDP communication is not working between JTDX and JTAlert.

1) Did you start JTAlert with the right shortcut?

2) Are either JTDX or JTAlert running with elevated permissions
("run as administrator")? If so, *DO NOT* run as administrator.

3) See "Help -> WSJTX UDP Setup" in JTAlert and follow those
instructions.

4) Are any other programs running that use UDP connections -
logging software, etc.?

73,

... Joe, W4TV

On 2021-07-27 3:13 PM, deni wrote:
Hey all,
I am trying to get jtalert working with jtdx.  At this point I am being unsuccessful.  I have used the standard setup under reporting in jtdx, but stilll nothing happens.  It just sets there and does nothing.  I am a little lost with jtalert.
Any help appreciated
73 - deni
WBØTAX

941 - 960 of 37287