Date   

locked JTAlert Dark Mode

Frank IZ7AUH
 

Hello,
It would be nice to have Hamapps (JTAlert) in Dark Mode.
JTDX has also the function so to get it equal it would be nice that this would be added.
Thanks 

73 de Frank IZ7AUH


locked Re: Duplicate Logging in HRD and more...

neil_zampella
 

Do you have HRD setup to directly access WSJT-X??   That's the only way you could be getting duplicates.   Either just use JT-Alert, or just use the HRD connection.

Neil, KN3ILZ


locked Re: Running two instances of JT Alert on one computer

g4wjs
 

On 26/12/2020 23:18, Jim wrote:

all I did was copy two shortcuts to my desktop and then go in to the properties of the icon and change Target in the Shortcut tab to c:\WSJT\wsjtx\bin\wsjtx.exe --rig-name =IC-746 

Jim,

you said several things in your OP that seem wrong to me, you have failed to clarify what you are doing and when ask to you reply with unrelated details. Let;s try again with some specific queries:

  1. In you OP you stated "When I work a station on 2m (the second instance of JT Alert) the logging window in JTAlert pops up after I send my 73 but it never sends it to my DXkeeper only the WSJTx log." There is no JTAlert logging window, are you referring to the "Log QSO window of WSJT-X? If so, when you click OK do you get any follow up message from JTAlert either confirming the QSO is logged or saying that logging the QSO failed?
  2. You stated "I have all of the same stuff checked off in in both instances of WSJT-x and JT alert set ups", as far as I am aware there is only one common settings dialog when using multiple instances of JTAlert. Because of that this part of your OP does not make sense to me.
  3. You stated "I have copied two separate instances of the WSJT-x and JT Alert to my desktop and added the correct info in the copy to make it see themselves as separate installations of each app." What exactly did you do to "copy" and "add the correct info" with respect to JTAlert?

--
73
Bill
G4WJS.


locked Re: Running two instances of JT Alert on one computer

Jim
 

all I did was copy two shortcuts to my desktop and then go in to the properties of the icon and change Target in the Shortcut tab to c:\WSJT\wsjtx\bin\wsjtx.exe --rig-name =IC-746 


locked Re: Running two instances of JT Alert on one computer

g4wjs
 

On 26/12/2020 23:05, Jim wrote:
I do understand the UDP ports issues  one instance has a UDP port of 2237 and Server port 2333 while the second instance has a UDP port of 2238 and Server port 2334 or did I mess this up? and the primary and secondary are both checked but still not able to send data to DXkeeper. Did I miss something?
Hi Jim,

the secondary ports are not relevant. The two different ports for each WSJT-X instance should be fine so long as no other application is using those ports.

In you OP you talked about setting up different icons or shortcuts for the second JTAlert instance, that is not necessary and may well cause a problem. Is that what you have done or have you simply started JTAlert twice using the same icon or shortcut as I suggested?




--
73
Bill
G4WJS.


locked Re: Running two instances of JT Alert on one computer

Jim
 

I do understand the UDP ports issues  one instance has a UDP port of 2237 and Server port 2333 while the second instance has a UDP port of 2238 and Server port 2334 or did I mess this up? and the primary and secondary are both checked but still not able to send data to DXkeeper. Did I miss something?


locked Re: Running two instances of JT Alert on one computer

g4wjs
 

On 26/12/2020 22:21, Jim wrote:
Hi Bill,
Thanks for the quick reply... well the route you suggested is basically what I did only I did it in the shortcut directly on the desktop to the shortcut icon, this way it is persistent and never goes away unless deleted .. either way should work equally well. BUT what I didn't do was change the UDP port number. For whatever reason it didn't even dawn on me that I might have to do that.  OK so when I fix that I suppose everything else will take care of itself.. or put another way I don't need to change anything in DXlab to correspond to the new port number ?  I guess I will know in about 2 minutes when I go in try to log a contact.

humm  ok I put 2238 in the primary and 2234 for the secondary although it suspect from the wording I may not need the secondary.. However I was still not able to add to the DXKeeper log
Hi Jim,

this is nothing to do with DXKeeper, JTAlert transfers logged QSOs to DXKeeper regardless of how many WSJT-X and corresponding JTAlert instances you have running.

I am not sure you understand the issue about setting different UDP server ports for each WSJT-X instance, each instance will have its own settings, in "Settings->Reporting->UDP Server" you need each to have its own unique port number.



--
73
Bill
G4WJS.


locked Re: Running two instances of JT Alert on one computer

Jim
 

Hi Bill,
Thanks for the quick reply... well the route you suggested is basically what I did only I did it in the shortcut directly on the desktop to the shortcut icon, this way it is persistent and never goes away unless deleted .. either way should work equally well. BUT what I didn't do was change the UDP port number. For whatever reason it didn't even dawn on me that I might have to do that.  OK so when I fix that I suppose everything else will take care of itself.. or put another way I don't need to change anything in DXlab to correspond to the new port number ?  I guess I will know in about 2 minutes when I go in try to log a contact.  

humm  ok I put 2238 in the primary and 2234 for the secondary although it suspect from the wording I may not need the secondary.. However I was still not able to add to the DXKeeper log


locked Re: Running two instances of JT Alert on one computer

g4wjs
 

On 26/12/2020 16:29, Jim wrote:
I have copied two separate instances of the WSJT-x and JT Alert to my desktop and added the correct info in the copy to make it see themselves as separate installations of each app.
Hi Jim,

the part above seems wrong. For WSJT-X you can copy the shortcut used to start it and add a --rig-name= option to its command line, for JTAlert all you need do is start JTAlert a second time. AFAIK the only specific setup you need is to use a different UDP Server port in each WSJT-X instance, JTAlert will automatically start the server on the respective port specified in the WSJT-X settings.



--
73
Bill
G4WJS.


locked Running two instances of JT Alert on one computer

Jim
 

Good morning to all,
I am running two transceivers (on different bands of course) and run two instances of WSJT-x and two instances of JT alert. Everything is working correctly with the system EXCEPT that I cant get the second instance of JT alert (running on my 2M receiver) to send the data from a contact to the log to the DXlab application DXKeeper. The first instance(my IC-7300) is controlled by DXlabs Commander application and works just fine. When I work a station on 2m (the second instance of JT Alert) the logging window in JT alert pops up after I send my 73 but it never sends it to my DXkeeper only the WSJTx log.

I have all of the same stuff checked off in in both instances of WSJT-x and JT alert set ups except the radio specific and audio specific stuff which are each set to there respective radio settings. Both radios work as they should and transmits FT8 correctly. Every other function of the software appears to work as it should.

I have copied two separate instances of the WSJT-x and JT Alert to my desktop and added the correct info in the copy to make it see themselves as separate installations of each app.

So what do I do I need to do to be able to send entries to my DXKeeper log? Or maybe the question is what did I do wrong? So below is a list of what the setup:

Computer: Dell 3300Mhz with two displays
Operating system: WIndows 7 Pro
Software controlling IC-7300:DXlab Suite of software
Software Controlling IC-746: WSJTx
WSJTx: V2.2.2
JT Alert: 2.16.17

Maybe I am asking for something that is beyond either WSJTx or JT Alert if so please let me know so the rest of my hair doesnt turn grey

Jim K3ybn


locked Re: DX Marathon Wanted and B4

Jon KM8V
 

Well, strangely, without changing anything else - except posting this message! :) - the B4 station is now properly highlighted as Marathon Wanted, after being B4 highlighted for an hour.


locked Re: DX Marathon Wanted and B4

Jon KM8V
 

Worked B4 is not available in the alerts priority settings window.


locked Re: DX Marathon Wanted and B4

Jim Cooper
 

On 26 Dec 2020 at 6:15, Jon KM8V wrote:

> It looks like B4 highlighting is
> taking precedence over Marathon
> Wanted status - Marathon should
> alert even if it is worked B4, or
> there should be an option to ignore
> B4 for wanted Marathon stations, I
> would think?

In the alert priority list, do you have
"Worked B4" below the "Wanted CQ Marathon"?

graphic

Use F1 to get the above window.

w2jc

  


locked Duplicate Logging in HRD and more...

Craig
 

With HRD supporting Google Earth Pro, the logging record must have the blank fields populated, specifically LAT / LON.  Under HRD --> Tools --> Configure --> QSO forwarding, there are two UDP Receive check boxes that enable the lookup and filling of this data.  To work with the WSJT-X / JTAlert combo the checkbox for receiving QSO UDP notifications via WSJT-X needs to be checked.  This action, along with requiring JTAlert to have HRD logging enabled generates a duplicate HRD logging entry, one of which (from JTAlert) is not populated completely as needed, the other from WSJT-X which contains all of the populated fields required.

The dilemma is turning off the UDP receive from WSJT-X leaves the JTAlert logging record, which is missing the data required.  Turning off JTAlert HRD logging disables the important tracking functionality wanted in JTAlert. 

So the issue is not limited to getting rid of a duplicate log entry, but to ensuring that the record that is logged includes the populated field data.  Otherwise, the logging record has to be edited separately with the lookup / update options.

Has anyone been able to get this to work?  Appreciate any guidance on this.  73, Craig


locked DX Marathon Wanted and B4

Jon KM8V
 

It looks like B4 highlighting is taking precedence over Marathon Wanted status - Marathon should alert even if it is worked B4, or there should be an option to ignore B4 for wanted Marathon stations, I would think?

Thanks & 73 - Love JT-Alert!


locked Re: Feature Request: QSO Pop-up

John AA6ZT
 

Sure it pops up, but nothing helpful is showing. The sub-menu when right clicking on an alerting call sign displays many vital information choices. The "Show QSOs History Popup" is not reflected in the F3 choice.


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

Dick Bingham
 

Hello Laurie

I guess it is Merry Christmas time down there in VK-Land now. I hope it is a
merry one for you and your family.

Now regarding your ===>
While more memory is always good, CPU usage is the most critical. What is taskmanager telling you when WSJT-X is busy 
processing decodes at the end of a period? What CPU usage is it indicating? If your hitting 80% or greater than that is a problem,
it will cause WSJT-X (and everything else on your PC) to be slowed.

The Underline indicates that that Callsign has the Text Messages function of JTAlert enabled and is set to receive messages.

de Laurie VK3AMA 
 
 I observed my CPU usage for 5-minutes or so and observed a max-usage of the CPU to be close to
65-percent during decode processing. Most of the time CPU usage runs in the mid-40's.

Again, I'm seeing up to 65-seconds for the WSJT-X logging pop-up window to finish once I click
on the "OK" after my "73" transmission finishes. During the 65-second period the main WSJT-X
screen is frozen (according to the 'clock' feature on the main WSJT-X window) and then jumps
to the correct time once the logging window collapses.

I will shut-down the computer and restart everything and observe what happens during the logging
process.

OK on the under-lining - doubt I will use it.

73  Dick/w7wkr at CN97uj

BIG SNIP


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

HamApps Support (VK3AMA)
 

On 24/12/2020 10:52 am, Dick Bingham wrote:

I guess I did not make myself clear . I am decoding call signs OK but when the CQer is 
sending "CQ DX VK3AMA QF##" I do not see the "DX" part in the 'cell' with the callsign.
The State and VE parts display fine.

No change when I expand to 4 X 9 display presentation. Once I'm certain what needs to
be seen is there, the main window for WSJT-X can be collapsed and only use the JTAlert
display.

Great software ! How many development MAN-Years does JTTAlert represent ? 

73  Dick/w7wkr at CN97uj

RRR.

"DX" is never explicitly displayed like a State or Province. There is however a directed CQ indicator (see the Alerts -> CQ section of the Settings) that can be displayed, "#" versus the "*" for a non-directed CQ. There is also a colored border option  that will wrap the Callsign, you can set a different color for directed CQs.

The copyright notice for JTAlert indicates it was first produced in 2011, so 10 years.

de Laurie VK3AMA

de Laurie VK3AMA


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

HamApps Support (VK3AMA)
 

On 24/12/2020 11:16 am, Dick Bingham wrote:
Hello again

I highly suspect my DELL Laptop E6510 W7 with 4G of RAM is the problem.
when the following SW is running:

- PowerSDR OpenHPSDR mRX PS v3.4.7
- Voicemeeter Banana
- WSJT-X v2.2.2
- DXKeeper 15.7.2
- JTAlert 2.16.17

The available free RAM drops below 350MB according to Win Task Manager.
I now only click "OK" in the pop-up logging window after my last transmission
has cleared. I have a reasonably fast internet connection and use a router to
connect with remote computers.

JTAlert DOES present a success or failure message after the logging has finished.
Same for the pop-up window associated with the WSJT-X logger. 

What is the significance of a call displayed as AA7Aw - AZ VS AA7AW - AZ
where one 'cell' is underlined and another is not underlined ?

73  Dick/w7wkr at CN97uj

While more memory is always good, CPU usage is the most critical. What is taskmanager telling you when WSJT-X is busy processing decodes at the end of a period? What CPU usage is it indicating? If your hitting 80% or greater than that is a problem, it will cause WSJT-X (and everything else on your PC) to be slowed.

The Underline indicates that that Callsign has the Text Messages function of JTAlert enabled and is set to receive messages.

de Laurie VK3AMA


locked Re: Feature Request: QSO Pop-up

HamApps Support (VK3AMA)
 

On 25/12/2020 6:58 am, John Maguire AA6ZT wrote:

The QSO Pop-up is a helpful tool.

However, it should include:

1. Timed appearance. 5 seconds is enough, or a user choice
2. Smaller. It could be smaller if there is no activity to report
3. Position. It should be movable to another place on the screen as the user chooses


73s, John AA6ZT


Use the F3 hotkey to bring up the "Callsign History Window" which is the same as the popup you refer to. It is a standalone window that can be positioned anywhere. It will auto-track the DXCall in WSJT-X. If you have the hotkeys turned off, the "View -> Callsign History Window" menu does the same.

de Laurie VK3AMA

4661 - 4680 of 37287