Did you try rebooting pc?

I recently installed JTAlert 2.50.7 and it no longer logs to DXKeeper, a problem that I have not had through all the upgrades.  Under "Logging" and "DXLab DXKeeper, "Enable DXLab KXKeeper Logging" is checked.  What am I missing?  Should I revert back to version 2.50.6?

Thanks for your help.

Ed K5YZW

Thanks... will give it a try.

73
Ken-W9KB

The latest one works correctly.
Thanks.

Hi Laurie,
Not sure did you receive my mail
Unfortunately version which you sent me, didnot work. I got window with information that JTAlertSettings.exe was missing

Same issue here, working on Windows 11

What issue? What are you not seeing?

If you're referring to the log fields area of the main JTAlert window is not being displayed, use the "View -> Show Log Fields" menu.

de Laurie VK3AMA

Laurie,

Thank you. That corrected my problem.  I know it must be something that I had not configured correctly.

73 Lloyd - W1BM

You can send it by checking here.

Same issue here, working on Windows 11

Thanks.

Thank you for your quick reply.  As you suggested I reviewed the "Accept UDP", this was and always has been checked.  Below I'm including a partial screenshot from this morning of what I and seeing.  The Callsigns #1 panel is clickable but the Caller and possibly the Alerts Only panels are not clickable.

Lloyd - W1LBM

JTDX Settings 2.2.0-rc155


From JTAlert 2.50.7

On Sun, Oct 24, 2021 at 05:18 AM, Stewart Wilkinson wrote:

Where do I find those settings ? - I am looking but I don't see them.

Set for each category:



Also you need to be connected to an enabled log.
 
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x Improved Widescreen 2.5.1, JTAlert 2.50.7, HRD Deluxe v6.7.0.391
FTdx-3000, SignaLink USB

Where do I find those settings ? - I am looking but I don't see them.

Some very extensive tests were run with Direwolf software looking at
decoding efficiency vs. Soundcard quality. At that time they provided
test files, so you could verify the results yourself.

Direwolf is an AX.25 package. It did not perform any testing with
standard RTTY, or any of the "Joe Taylor modes". I can assure you
that I can copy many more stations with a good high reference 24 bit
ADC and low internal noise receiver than I can with the same receiver
and a "commodity" 16 bit ADC like those found in the common USB dongle,
SignaLink or even the internal 16-bit USB CODEC/ADC in many of the
current transceivers.

73,

... Joe, W4TV


On 2021-10-23 8:17 PM, Hasan Schiers N0AN wrote:

Hi Joe,
Some very extensive tests were run with Direwolf software looking at decoding efficiency vs. Soundcard quality. At that time they provided test files, so you could verify the results yourself.
They could find no improvement in decode efficiency with higher end sound cards vs. a 5 dollar USB dongle (1200 baud packet)
The testers concluded there was little or nothing to gain spending the extra money, as it did not produce enhanced results.
That was quite a few years ago, maybe things have changed, but I doubt it.
73, N0AN
On Sat, Oct 23, 2021, 2:08 PM Joe Subich, W4TV <lists@subich.com <mailto:lists@subich.com>> wrote:
On 2021-10-23 1:44 PM, Hasan Schiers N0AN wrote:
 > There is no advantage to spending a bunch of money for a fancy sound
 > card for the digital modes. They don't need it, and you gain
nothing.
This is only true when speaking about 16bit CODECs running off a 3.3
or 5V supply.  If the sound card has a 24 bit ADC with a higher
voltage reference you can obtain several dB more dynamic range if
the receiver and sound card preamp are well designed (low noise).
This does rule out most of the JA rigs and commodity sound cards but
saying the 24 bit sound cards are of no value is certainly an over-
simplification.
73,
    ... Joe, W4TV

I think it's great how JTAlert keeps track of heard callsigns in the Caller panel.  My question is why aren't these callsigns clickable?  I end up having to scroll up through the RX Frequency window of JTDX to find them.  Am I missing some configuration that would allow that?

Lloyd - W1LBM

JTAlert  2.50.7, JTDX v2.2.0-rd155

All callsigns are clickable. There is no difference between the different display panels of the window. JTAlert makes no distinction, all displayed callsigns have the same back-end code for the click-processing.

I see you're running JTDX, very likely you have the "Accept UDP Reply messages" settings set to a subset of the decodes, perhaps CQ only decodes.

"Caller" decodes are never classed as CQ decodes. Check your JTDX settings.

de Laurie VK3AMA

I think it's great how JTAlert keeps track of heard callsigns in the Caller panel.  My question is why aren't these callsigns clickable?  I end up having to scroll up through the RX Frequency window of JTDX to find them.  Am I missing some configuration that would allow that?

Lloyd - W1LBM

JTAlert  2.50.7, JTDX v2.2.0-rd155

Click the gear icon in the bottom right and check the "On Top" item.

Mike W9MDB

Wrong window. That's the Callsigns window. The Decodes window, which is old pre-2.50.x series code does not have the gear icon.

de Laurie VK3AMA

I use Decodes window as alternative to JTDX decodes window. It works preaty well, but there is no possibility to set JTAlert Decodes windows 'always on top'.
Can you consider add this feature ? Or maybe I miss something and this is already implemented ?
73! Mek sq3rx

Mek,

A worthwhile change to keep the Decodes window functionality inline with the other JTAlert windows.

The Decodes window is old code, while the new 2.50.x introduced windows are new code that all support the "On Top" functionality.

I have modified the Decodes window to support an "On Top" setting.
Check your email, I have sent a new build for you to test.

de Laurie VK3AMA