Date   

locked Re: Lost UDP Connection with WSJT-X #FT8

w4lde
 

Rich,
looks like you have two programs trying to use the WSJT-x UDP port.
close the UDP port at Logger32 and restart JTAlert / WSJT-x.
73 de Ron W4LDE


locked Re: HRD 6 #HRD

HamApps Support (VK3AMA)
 

On 21/08/2018 3:42 PM, Ken Yates wrote:
I'm confused.  Y'all are saying that the latest version of JT-Alert (2.12.4) works with HRD logbook v6. ...but the JT-Alert page clearly says:

  • Automatic logging to these log types when QSO is logged in JT65-HF or WSJT-X
    • DXLab DXKeeper
    • ACLog
    • Log4OM
    • HRD Log V5
    • Standard ADIF 2.2 file
    • MixW CSV file
So, not mention at all about HRD 6.x logbooks being supported for automatic logging.  By automatic logging, I refer to the jt-alert 2.10.0 version generating a popup window at the end of a confirmed QSO and then automatically logging the contact into HRD 6.0 logbook without 'clicking' on anything.  (This feature is extremely important to me as I often log in to my home pc remotely to make QSOs from a police communications center during downtime.  If I suddenly get tied up on an emergency call, I don't want to 'lose' the qso.  

      de KI3N 
OM,

The HamApps web page had not been updated after HRD 6 support was reinstated within JTAlert. That has been corrected.

de Laurie VK3AMA


locked Re: UDP ports

HamApps Support (VK3AMA)
 

On 21/08/2018 6:07 PM, Tom Ramberg via Groups.Io wrote:
Hello. I'm extremely happy with the way JTAlert-X works with realtime logging to Eqsl.cc, qrz.com logbook and Clublog.org

Up to now I have imported the JTalert ADI logfile into my logger (Swisslog for Windows) and it works well enough, but the neat thing would be if I could also make Swisslog get the qsos dirctly from JTAlert. There are two sections in the settings for JTAlert, one is the rebroadcast of WSJT-X UDF packets, with the same page also mentioning the UDP port for N1MM+, and the other is the Last Qso, that also states a UDP port. Which of these should be set to 2334? I've set Swisslog to listen to UDP port 2334.

73 de Tom OH6VDA
Tom,

It depends on what Swisslog is listening for. Is it listening for an ADIF packet representing the logged QSO or is it listening for standard WSJT-X UDP traffic (decodes and logged QSO)?

If SwissLog is listening for UDP traffic, then enable the UDP rebroadcast.
If SwissLog is listening for a UDP packet (adif record) of the QSO just logged, then enable the last QSO API.

de Laurie VK3AMA


locked UDP ports

Tom Ramberg, OH6VDA
 

Hello. I'm extremely happy with the way JTAlert-X works with realtime logging to Eqsl.cc, qrz.com logbook and Clublog.org

Up to now I have imported the JTalert ADI logfile into my logger (Swisslog for Windows) and it works well enough, but the neat thing would be if I could also make Swisslog get the qsos dirctly from JTAlert. There are two sections in the settings for JTAlert, one is the rebroadcast of WSJT-X UDF packets, with the same page also mentioning the UDP port for N1MM+, and the other is the Last Qso, that also states a UDP port. Which of these should be set to 2334? I've set Swisslog to listen to UDP port 2334.

73 de Tom OH6VDA


Sendt fra min iPad Air 2


locked Re: HRD 6 #HRD

Ken Yates
 

I'm confused.  Y'all are saying that the latest version of JT-Alert (2.12.4) works with HRD logbook v6. ...but the JT-Alert page clearly says:

  • Automatic logging to these log types when QSO is logged in JT65-HF or WSJT-X
    • DXLab DXKeeper
    • ACLog
    • Log4OM
    • HRD Log V5
    • Standard ADIF 2.2 file
    • MixW CSV file
So, not mention at all about HRD 6.x logbooks being supported for automatic logging.  By automatic logging, I refer to the jt-alert 2.10.0 version generating a popup window at the end of a confirmed QSO and then automatically logging the contact into HRD 6.0 logbook without 'clicking' on anything.  (This feature is extremely important to me as I often log in to my home pc remotely to make QSOs from a police communications center during downtime.  If I suddenly get tied up on an emergency call, I don't want to 'lose' the qso.  

      de KI3N 


locked Re: JT alert has stopped working

Laurie, VK3AMA
 

On 20/08/2018 2:43 AM, ab9qu wrote:
Ok, I thought I would go back and check settings in WSJT. I know I had unticked the hound box.
When I just looked the hound box was still ticked. So I unticked the hound box and now all is well.
Thank you all for the very helpfull replyes.
Yes, my face is red.
Thaanks
73 de Bill AB9QU
Bill,

Thanks for the update. Good to hear all is working again.

Don't worry about the red face, we all have those moments, just try not to do it on air for the world to see (eg, Calling a DX simplex by not enabling split and discovering your Callsign plastered all over the Cluster, been there done that).

de Laurie VK3AMA


locked Re: JTAlert 2.12.4 is available for download

HamApps Support (VK3AMA)
 

On 20/08/2018 5:11 AM, Dennis wrote:
Should the port assignments be the same in each of the programs: ie WSJT-X, JTAlert, and WSJT-XDX Aggregator? I am using 2237 as indicated on the WSJT-XDX web site.
It will only populate WSJT-XDX Aggregator when "settings> manage settings" is open in JTAlert. Once closed it populates only one more time then stops. Reopening manage settings will again allow the process as long as it is open. If I don't open JTAlert (or close it) the process works fine.

Regards,
73 Dennis W7DRW
NO! don't set all three apps to the same port number. Leave WSJT-X at 2237, JTAlert will automatically start listening on that port. Have the JTAlert UDP rebroadcast enabled and set to a different port (it should not be 2237 and JTAlert will disable the rebroadcast if you set JTAlert to rebroadcast back to same port it is listening on for WSJT-X UDP data). Set DX Aggregator to listen on the JTAlert rebroadcast port (which is 2334 by default).

de Laurie VK3AMA


locked Re: CQ And Chimes Audio In FT8 Transmission

HamApps Support (VK3AMA)
 

On 20/08/2018 3:16 AM, Bud Governale wrote:
It’s been reported that my FT8 transmissions include intermittent “CQ” and triple chimes.
The CQ and triple chimes occupy the full FT8 bandwidth about 2.4 KHz when they sound.
 
We’ve diagnosed the source coming from JTAlert audio sounds.
 
The issue remains when the K3 mic setting is reduced to zero.
It also persists when the mic is disconnected from the K3.
 
Is there a solution other than turning the audio alerts off in the JTAlert settings?
 
73,
 
Bud W3LL
Bud,

If you only have a single soundcard, then your only option is to turn off JTAlert sounds and Windows Sounds and use that card exclusively for your Radio.

If you have more than one sound device, set JTAlert & Windows to one device and your Radio the other and importantly, don't allow Windows to set your Radio Sound device as the Windows default. Windows will often reassign the default device if USB cards are unplugged or disabled to save power and frequently after a Windows update.

This is why JTAlert uses sound card names rather than soundcard device numbers when restoring its settings. Soundcard device ID's can change, but the name doesn't. Your should always set the JTAlert soundcard to a specific device and not to the "Windows Default Sound Card". It avoids JTAlert playing audio on the wrong device if there have been Windows sound device reassignments.

de Laurie VK3AMA


locked Re: Setting up alerts for multiple instances of WSJT-X?

HamApps Support (VK3AMA)
 

On 20/08/2018 10:50 AM, Frank wrote:
Thanks much. So, currently I have three instances of WSJT-X running on this PC, monitoring 40m, 30m and 20m FT8. I went into the settings for each instance of WSJT-X and gave them the UDP port numbers of 2240, 2230 and 2220 respectively (so the port number would include the band name). I then started three instances of JTAlertX.

The 30m and 40m monitors are working fine. However, 20m is not. A JTAlert error box came up, "Unable to communicate with the WSJT-X process. UDP Port: 2220. ..."

In selecting the number 2220, did I choose one outside the accepted range of port numbers? If so, what is the range of port numbers?
I wouldn't bother with this sort of port numbering. The only applications that are aware of the ports are WSJT-X and JTAlert. I can't see any benefit is having the port number reflect the Band Number. My suggestion is to start with the default 2237 port and increment it by one for each instance, instance #1=2237, #2=2238, #3=2239, etc. Your less likely to run into the port being used by another application. The are a number of JTAlert/WSJT-X users running over 10 instances and this number scheme has worked for them.

de Laurie VK3AMA


locked Re: Lost UDP Connection with WSJT-X #FT8

HamApps Support (VK3AMA)
 

On 21/08/2018 6:07 AM, Richard Black via Groups.Io wrote:
I've been using JTAlertX 2.12.4 with nary a problem until this afternoon. I thought I'd work some CW so fired up the KX3 but didn't start WSJT-X or JTAlertX. Not hearing much activity I started WSJT-X followed by JTAlertX. I'm getting decodes in the WSJT-X window, but none in the JTAlertX window due to UDP communications failure. I'm stumped as to why since all the settings look OK to me. I've attached a few screen captures to illustrate the settings.

Tnx,
Rich - N0FXQ
Rich,

If there have been no settings changes within WSJT-X or JTAlert, then I suggest a PC restart. If the restart doesn't fix the problem let us know.

de Laurie VK3AMA


locked Re: Directional CQ

HamApps Support (VK3AMA)
 

On 21/08/2018 7:33 AM, Adrian wrote:
I need MD RI VT and DE

Adrian VK4KL 
If you have those States set as needed within JTAlert and the State alert enabled then you will get alerted.

de Laurie VK3AMA


locked Re: Directional CQ

HamApps Support (VK3AMA)
 

On 21/08/2018 6:11 AM, Frank Kirschner wrote:
Is there any way to get an alert on a CQ MD decode?

It won't come up often, but if someone needs a QSL from MD, I would be happy to help.

Thanks.

73,
Frank
KF6E
Frank,

Sorry, no way that I can think of.

de Laurie VK3AMA


locked Re: Error On Closing AC Log After Logging Through JTAlert

HamApps Support (VK3AMA)
 

On 21/08/2018 11:33 AM, W. Stanley Edwards wrote:

Laurie:

I have run into a consistent problem and have an established pattern.  I get this error only after I have been using WSJT-X with JTAlert, but it happens every time if I’ve logged a contact through JTAlert.  I never see this problem with normal use of ACLog or even with WSJT-X and JTAlert running if I don’t log a contact.  I ran it by Scott thinking it might be related to his logging software.  He suggested I relay the information to you as it seemed something was not closing properly when I exited JTAlert, keeping the log file open.  I always shut down WSJT-X and JTAlert prior to closing ACLog.

This is the latest version of your software as well as the latest versions of the other two application.  It runs under Windows 10 with all the latest updates.  My primary log file is on a networked drive and not the local drive, a drive that is mirrored in the local server and in a distant city (the reason I haven’t been too worried about the error).

Thanks for all you’ve done for the Amateur Radio community with your software development efforts.

Regards,

Stan Edwards, WA4DYD

Stan,



That error is ACLog generated. JTAlert would not be going anywhere near that backup directory, it would be unaware of it. JTAlert does establish a readonly connection to your log file to check for B4s. QSO history and to confirm logging.

Unless your Log is located within that Backup directory. I can't see how JTAlert can affect its permissions.

ACLog logging is done using the ACLog TCPIP API and the connection is only opened when logging a contact and closed immediately after. I doubt that could be the cause.

Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis.

de Laurie VK3AMA


locked Error On Closing AC Log After Logging Through JTAlert

Stan Edwards - WA4DYD
 

Laurie:

 

I have run into a consistent problem and have an established pattern.  I get this error only after I have been using WSJT-X with JTAlert, but it happens every time if I’ve logged a contact through JTAlert.  I never see this problem with normal use of ACLog or even with WSJT-X and JTAlert running if I don’t log a contact.  I ran it by Scott thinking it might be related to his logging software.  He suggested I relay the information to you as it seemed something was not closing properly when I exited JTAlert, keeping the log file open.  I always shut down WSJT-X and JTAlert prior to closing ACLog.

 

This is the latest version of your software as well as the latest versions of the other two application.  It runs under Windows 10 with all the latest updates.  My primary log file is on a networked drive and not the local drive, a drive that is mirrored in the local server and in a distant city (the reason I haven’t been too worried about the error).

 

Thanks for all you’ve done for the Amateur Radio community with your software development efforts.

 

Regards,

Stan Edwards, WA4DYD


locked Re: Directional CQ

Adrian
 

I need MD RI VT and DE

Adrian VK4KL 


On 21 Aug 2018, at 6:36 am, Michael Black via Groups.Io <mdblack98@...> wrote:

Put "MD" in Settings/Own Call in any box should do it and enable that alert.

de Mike W9MDB


On Monday, August 20, 2018, 3:11:41 PM CDT, Frank Kirschner <frank@...> wrote:


Is there any way to get an alert on a CQ MD decode?

It won't come up often, but if someone needs a QSL from MD, I would be happy to help.

Thanks.

73,
Frank
KF6E


locked Re: Directional CQ

Michael Black
 

Put "MD" in Settings/Own Call in any box should do it and enable that alert.

de Mike W9MDB


On Monday, August 20, 2018, 3:11:41 PM CDT, Frank Kirschner <frank@...> wrote:


Is there any way to get an alert on a CQ MD decode?

It won't come up often, but if someone needs a QSL from MD, I would be happy to help.

Thanks.

73,
Frank
KF6E


locked Re: Lost UDP Connection with WSJT-X #FT8

Richard Black
 

Nope.


On Monday, August 20, 2018, 4:11:08 PM EDT, Michael Black via Groups.Io <mdblack98@...> wrote:


Are you in Hound mode?

de MIke W9MDB





On Monday, August 20, 2018, 3:08:00 PM CDT, Richard Black via Groups.Io <jrblack99sa@...> wrote:


I've been using JTAlertX 2.12.4 with nary a problem until this afternoon. I thought I'd work some CW so fired up the KX3 but didn't start WSJT-X or JTAlertX. Not hearing much activity I started WSJT-X followed by JTAlertX. I'm getting decodes in the WSJT-X window, but none in the JTAlertX window due to UDP communications failure. I'm stumped as to why since all the settings look OK to me. I've attached a few screen captures to illustrate the settings.

Tnx,
Rich - N0FXQ


locked Directional CQ

Frank Kirschner
 

Is there any way to get an alert on a CQ MD decode?

It won't come up often, but if someone needs a QSL from MD, I would be happy to help.

Thanks.

73,
Frank
KF6E


locked Re: Lost UDP Connection with WSJT-X #FT8

Michael Black
 

Are you in Hound mode?

de MIke W9MDB





On Monday, August 20, 2018, 3:08:00 PM CDT, Richard Black via Groups.Io <jrblack99sa@...> wrote:


I've been using JTAlertX 2.12.4 with nary a problem until this afternoon. I thought I'd work some CW so fired up the KX3 but didn't start WSJT-X or JTAlertX. Not hearing much activity I started WSJT-X followed by JTAlertX. I'm getting decodes in the WSJT-X window, but none in the JTAlertX window due to UDP communications failure. I'm stumped as to why since all the settings look OK to me. I've attached a few screen captures to illustrate the settings.

Tnx,
Rich - N0FXQ


locked Lost UDP Connection with WSJT-X #FT8

Richard Black
 

I've been using JTAlertX 2.12.4 with nary a problem until this afternoon. I thought I'd work some CW so fired up the KX3 but didn't start WSJT-X or JTAlertX. Not hearing much activity I started WSJT-X followed by JTAlertX. I'm getting decodes in the WSJT-X window, but none in the JTAlertX window due to UDP communications failure. I'm stumped as to why since all the settings look OK to me. I've attached a few screen captures to illustrate the settings.

Tnx,
Rich - N0FXQ

15561 - 15580 of 36991