Date   

locked Worked B4 conflicting (some callsigns)

nd2k@...
 

Running JTAlert 2.50.5/WSJT 2.4.0/Log4OM V2 2.17.0.0

I have noticed with a small handful of calls, the Confirmed/Worked Bands Display
will correctly show a callsign worked (e.g. the 20M FT4 worked box is checked)
but the same callsign in the Callsigns Window does not show "B4"; nor is it
"grayed out" in the WSJT Band Activity column (indicating worked B4).

Again, this is only a small handful of callsigns, with not rhyme or reason to them
having anything in common. I rebuilt the database, but still no change.

Any ideas??

Al ND2K


locked Re: Log data not transferring to Logger32

Gerard Arsenault <jerrya@...>
 

Thanks Laurie. Obviously I have very little understanding of the coding involved. What I can't grasp is why for a number of years logging worked automatically and continuously between WSJT-X and Logger 32 before updates and a new radio. I will follow your advice and check with the Logger 32 forum.
73,

Jerry VE9CD


locked Re: Callsign window actions not enabling WSJT "enable tx"

Jim Cary
 

Thanks Laurie.  Accept UDP requests was not clicked on.

Jim


locked Re: Callsign window actions not enabling WSJT "enable tx"

ON4AVJ@...
 

Hello,
I have the same problem, but I'm using JTDX. What are the setting there?
73
Jacques ON4AVJ


locked Re: enhancement request

HamApps Support (VK3AMA)
 

On 4/09/2021 8:44 am, Joe wrote:

In the new version of JTAlert (2.50.5), I note that for some windows, like the Decodes window, it makes sense to clear the panel after each decode, while for others, like the Callers panel, one can set the persistence of the information shown in that panel, from "no auto clear" down to 1 minute.  I would like to be able to set this same parameter for clearing the DXCC Alert window, so that I can see, what DX I might have missed while I was away from my station.  This is valuable information in that it lets you know, especially over a few days, when a DX entity was being decoded at your station.  Is there already a way to do this, or would this be a reasonable thing to add??

When I initially saw the drop down box with "Callers (own call alert)" I thought this was going to be a drop down that allowed me to select a panel for configuration.  Changing it so that it does, in fact, work that way doesn't seem like a major change, but I fully realize it may be more difficult that it appears, and/or, the priority of such a modification might be so far down the list as to be not likely in the near future.  Alternatively, and maybe even better, would be a separate window that simply captured every (time stamped) DXCC alert until cleared, if enabled.

Should I get my hopes up ;-)

Joe,

Persisting callsigns in the different Alert views of the Callsigns window, similar to the "Callers" view is already on my todo list. When I coded the persisting Callsigns for the "Callers" view I realized that this would be useful for other views. The underlying code framework is partially coded but not ready for going live. You can see some of that work in the Hamburger menu (3 horizontal line icon) of each view having a "Clear Callsigns" entry. Rest assured it will be happening, I just don't know when, soon I hope, but not in the next release I can say with confidence.

de Laurie VK3AMA


locked Re: JTAlert Main Window not Visible SOLVED

HamApps Support (VK3AMA)
 

On 6/09/2021 5:04 am, Robie - AJ4F wrote:
The JTalert main screen issue was resolved by deleting the ini file and letting JTAlert regenerate it,


The issue of no communication between WSJT-X and JTAlert was intermittent an has not recurred after switching JTAlert & WSJT-X to multicast.


Thanks for all the assistance!

Robie - AJ4F 
Thanks for the update.

I don't know what ini file you are referring to, JTAlert doesn't use ini files.

de Laurie VK3AMA


locked Re: Log data not transferring to Logger32

HamApps Support (VK3AMA)
 

On 4/09/2021 3:58 am, Gerard Arsenault wrote:
I believe I have set up Multicast correctly but wsjt-x log info does not transfer over. Am I missing some setting?

JTAlert has no involvement in logging WSJTX contacts in Logger32. You will need to take this up with the Logger32 people.

de Laurie VK3AMA


locked Re: Missing start menu with version 2.50.5

HamApps Support (VK3AMA)
 

On 6/09/2021 2:25 am, Raymond Mikula wrote:
ok, if I look at the task bar I do see two "notes"  The note that is shown in my attached screen capture does not activate the missing/floating window.  I do have four displays in use and have carefully searched all of them but there is no menu to be found.  I also include a screen capture of the tasks that are running.

Ray/W9NZ

Your images shows that the main JTAlert process (the main window) is running and there is a taskbar entry.

       

If clicking the taskbar entry does not bring the JTAlert main window into view then it is likely positioned off-screen. Google "Recover off-screen window" will produce millions of results for instruction on how to recover an off-screen window, a very common Windows problem.

de Laurie VK3AMA


locked Re: New Computer installation No operator call sign box

HamApps Support (VK3AMA)
 

On 5/09/2021 5:29 am, Tom Harson wrote:
I just got a new computer and, installed 2.50. When I envoke the program for the first time, NO call sign box appears. I have tried a lot of things but I have not solved this issue. I have the same issue with version 2.16.16 and 2.16.17. Obviously need some help !

73 de Tom K5VJZ

The Callsign is stored within the Registry. If JTAlert cannot find an entry (when first installed) it should show a popup window allowing you to enter the Callsign. Likely that window is showing behind another window and is automatically closing after the 30 second timeout for entry has elapsed.

You will need manually add an entry to the Registry if you're unable to see the Callsign input window.

Using Regedit navigate to the "HKEY_CURRENT_USER\SOFTWARE\HamApps\" entry and add a new REG_SZ value with your callsign.

   

If you're uncomfortable making manual changes to the Registry, let me know and I will send you a file that will apply the change for you.

de Laurie VK3AMA



locked Re: Callsign window actions not enabling WSJT "enable tx"

HamApps Support (VK3AMA)
 

On 6/09/2021 6:49 am, Jim Cary wrote:
When I double click on either a staton calling CQ or my call in the Callsign #1 window, the "Enable TX" button on WSJT-X does not activate.  I have the "callsign Options" wsjtx reply set to "double click"  But that doesn't seem to have any effect.  Tried "single click" but the same thing happens.

What am I doing wrong?

Jim
W2SM

If the Callsign is being sent to WSJTX correctly when you click it within JTAlert, than JTAlert is working as designed.

JTAlert has no control over how WSJTX responds to Callsigns sent to it via the UDP API. WSJTX determines whether it enables TX based on its own settings, there is nothing in the API that will allow JTAlert to control that behavior.

My guess is that you don't have this setting enabled in WSJTX.
   

If the Callsigns is not being transferred to WSJTX from JTAlert than likely you don't have this setting enabled in WSJTX.
   

de Laurie VK3AMA


locked Re: JTAlert problem with FT4 contacts

HamApps Support (VK3AMA)
 

On 6/09/2021 8:15 am, Rich Force wrote:
I just updated my hrd for ft4 i.e. mode=MFSK submode = ft4.  Now Jtalert will not read my ft4 contacts.   It has put me back to 0 states and 0 dxcc on ft4.  What did I do wrong?

What version of JTAlert?
What version of HRD?
Please don't say "the latest" quote the actual version numbers.

de Laurie VK3AMA


locked JTAlert problem with FT4 contacts

Rich Force
 

I just updated my hrd for ft4 i.e. mode=MFSK submode = ft4.  Now Jtalert will not read my ft4 contacts.   It has put me back to 0 states and 0 dxcc on ft4.  What did I do wrong?


locked Callsign window actions not enabling WSJT "enable tx"

Jim Cary
 

When I double click on either a staton calling CQ or my call in the Callsign #1 window, the "Enable TX" button on WSJT-X does not activate.  I have the "callsign Options" wsjtx reply set to "double click"  But that doesn't seem to have any effect.  Tried "single click" but the same thing happens.

What am I doing wrong?

Jim
W2SM


locked Re: JTAlert Main Window not Visible SOLVED

Robie - AJ4F
 

The JTalert main screen issue was resolved by deleting the ini file and letting JTAlert regenerate it,


The issue of no communication between WSJT-X and JTAlert was intermittent an has not recurred after switching JTAlert & WSJT-X to multicast.


Thanks for all the assistance!

Robie - AJ4F 

On Tue, Aug 31, 2021, 9:46 PM Laurie, VK3AMA <hamapps.support@...> wrote:


On 1/09/2021 11:50 am, Robie - AJ4F wrote:
> Both WSJT-X and JTAlert are set up for unicast.

If you're using Unicast then it is likely that ACLog is seizing
exclusive control of the UDP port and preventing JTAlert from receiving
the UDP messages. Either turn off ACLog integration with WSJTX or switch
both WSJTX and ACLog to multicast, JTAlert automatically detects if
multicast is being used, but you need to ensure that the "Settings ->
WSJT-X UDP Multicast on loopback" menu is ticked. See the JTAlert "Help
-WSJTX UDP Setup" menu.

de Laurie VK3AMA









locked Re: Floating title bar?

John Miller K8UMF
 

Thanks Mike, it has been awhile since I used JTalert.

John


locked Re: Missing start menu with version 2.50.5

Raymond Mikula
 

ok, if I look at the task bar I do see two "notes"  The note that is shown in my attached screen capture does not activate the missing/floating window.  I do have four displays in use and have carefully searched all of them but there is no menu to be found.  I also include a screen capture of the tasks that are running.

Ray/W9NZ


On Sat, Sep 4, 2021 at 08:31 PM, Michael Black wrote:
The "menu at the top" is now a separate window.
It should be the 1st thing to come up followed shortly by the call window.
 
Hover over the JTAlert icon in the task bar and you should see the other window.
You might have to move it if it's off screen.


locked Re: SNR Not showing in Callsign window

Michael Black
 

That shows when your current QSO partner is also running JTAlert and has text message capability.

Mike W9MDB




On Sunday, September 5, 2021, 08:08:50 AM CDT, Neil Foster <archernf@...> wrote:


Mike....when the box marked Online is checked, what does that refer too? The LOTW and eQSL I understand
TNX and stay well     Neil    N4FN


locked Re: SNR Not showing in Callsign window

Neil Foster
 

Mike....when the box marked Online is checked, what does that refer too? The LOTW and eQSL I understand
TNX and stay well     Neil    N4FN


locked Re: Floating title bar?

Ron W3RJW
 

On Sat, Sep 4, 2021 at 04:33 PM, John Miller K8UMF wrote:
Not sure what I am doing wrong but the main window is separated from the title bar/options.
John,

The separate windows give you much flexibility in your screen layout. Here's just one example. You can still lock the JTAlert title bar to WSJT-x if you want to.


 
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.5.0, rc3 Improved, JTAlert 2.50.4, HRD Deluxe v6.7.0.357
FTdx-3000, SignaLink USB


locked Re: Floating title bar?

Michael Black
 

That's how it behaves now -- it's a separate window.
The floating bar is the old AutoIT code which will eventually disappear.

Maybe Laurie can confirm the future behavior...hope to see all those options in the new callsign menu rather than another window.

Mike W9MDB


On Saturday, September 4, 2021, 04:59:37 PM CDT, John Miller K8UMF <imtekms@...> wrote:


jtalertProblem.jpg
Here is the floating title bar problem.

Thank you!

John


On Sat, Sep 4, 2021 at 4:50 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Can you post a screen shot of that?

Not clear what you're saying.

Mike W9MDB




On Saturday, September 4, 2021, 03:33:20 PM CDT, John Miller K8UMF <imtekms@...> wrote:


Not sure what I am doing wrong but the main window is separated from the title bar/options. It took a bit of playing around to get the .net stuff working but problem persists after uninstall/reinstall.

Thanks,

John

1741 - 1760 of 38532