Date   

locked Help please: WSJT-x Changing Window View Font Sizes

Mark W2OR
 

Greetings.  The WSJT-x User Guide mentions a simple procedure for altering the visual fonts for the Band Activity window and Rx Frequency window.  One has to first find the "Installation Directory" and then add a simple .txt file, which easy to make, per the instructions.  Since my eyesight is not that good, I need to increase the fonts using this procedure.  But I need help :  

Would someone here kindly let me (us) know where exactly this Installation Directory is located, so i can follow the instructions and add the small .txt file.  Thank you.  I just can't find it.  We would need to know:  The exact name of the "Installation Directory" file at installation time.  What is the name of its 'parent umbrella file'  (my term) where it is found?  Thank you.

// Mark


locked Re: Can 4M be added?

Frank PH2M
 

Hello Laurie,

I 'am looking forward to the 4M implantation :-).
I was mistaken about 60M (my laptop JTAlert screen is different from my shacks screen), it is indeed visible in the shack!

73 de Frank PH2M

Op 5-8-2018 om 03:47 schreef HamApps Support (VK3AMA):

On 2/08/2018 8:36 PM, Frank de Wilde wrote:
Hello Laurie,

Can 4M be added to the JTAlertX main window, mine jumps from 6M to the 2M band, also 60M is missing I think ( I 'am on my laptop now, so can't proper check!) ?

73 de Frank PH2M - JO22HC13 (mainly QRV on 6M, 4M & 2M - FT8)
Frank,

It is on the todo list, but implementation is not imminent, sorry.

Adding 4m will be part of a major overhaul that will also add 630m. The changes are not trivial however and will require a significant redesign of all the Settings window sections where Band select is available, a new layout in the main window to add an additional 2 bands, changes to the Band Activity display and the Callsign history widows.

60m is already available. Where is it missing for you?

de Laurie VK3AMA



locked Re: Hamspots load

Michael Black
 

On the "Your call spotted" so it would be easier to find if somebody is spotting you.

Mike




On Saturday, August 4, 2018, 8:29:25 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 4/08/2018 11:45 PM, Michael Black via Groups.Io wrote:
Hi Laurie,
A while ago you had changed the spots on hamspots.net to sort the call signs but I think you removed it due to server load or some other reason.

I was think that perhaps only updating when the window is visible might reduce the server load considerably as I doubt many people keep that window visible...but quite possible running in the background.

There's a visibility.js script that should help....and maybe we can sort again?


de Mike W9MDB
Mike,

Refresh my memory, where on HamSpots did I change the display sorting?

de Laurie VK3AMA


locked Re: Can 4M be added?

HamApps Support (VK3AMA)
 

On 2/08/2018 8:36 PM, Frank de Wilde wrote:
Hello Laurie,

Can 4M be added to the JTAlertX main window, mine jumps from 6M to the 2M band, also 60M is missing I think ( I 'am on my laptop now, so can't proper check!) ?

73 de Frank PH2M - JO22HC13 (mainly QRV on 6M, 4M & 2M - FT8)
Frank,

It is on the todo list, but implementation is not imminent, sorry.

Adding 4m will be part of a major overhaul that will also add 630m. The changes are not trivial however and will require a significant redesign of all the Settings window sections where Band select is available, a new layout in the main window to add an additional 2 bands, changes to the Band Activity display and the Callsign history widows.

60m is already available. Where is it missing for you?

de Laurie VK3AMA


locked Re: LAST QSO API - UDP function

HamApps Support (VK3AMA)
 

On 5/08/2018 8:19 AM, w4lde wrote:

Laurie,


I tested the API - UDP port #52001 log output with HamQTH data add running several different setups trying to determine where the data stream stopped.

Ist - regardless of the port selections and methods selected for logging the internal WSJT-x and JTAlert logging worked100% of the time during my tests.

The logging program I use which is Logger32 has both TCP and UDP capabilities.  For my initial test I select the UDP port in Logger32 to match the port number from either WSJT-x in standalone, #2237,  WSJT-x and JTAlert using the API-UDP port #52001 and finally the Relay of WSJT-x data stream via the relay data selection under the WSJT-s setup in JTAlert I used port number #2234

1.Using only running WSJT-x on port 2237 and Logger32 in monitor UDP every time we hit the log QSO it logged to two (2) places, WSJT-x and Logger32.  The data in the log was as provided by WSJT-x..  JTAlert was not operating.

2. I then started JTAlert which is set to auto start WSJT-x.  The Last QSO API UDP port setting was #52001.  I set the Logger32 UDP port to monitor 52001.  When manually set to log, no data was transferred to Logger32 but did log WSJT-x and JTAlert correctly.

3.  I then changed the UDP port in Logger32 to 2234  and set the API UDP port to 2234 after I had disabled the WSJT-x relay function in JTAlert. When manually set to log both JTAlert and WSJT-x logs logged as expected but no data was transferred to Logger32.  So now we had two (2) UDPports set in the Last QSO API UDP port and neither would transfer the data.

4.  I then tried to use the TCP server function in Logger32 using SOCAT to convert UDP to TCP. 
The port setting was 52001 under Last QSO AOI and also Socate, no logging data was transmitted.  I closed that API Last QSO and 52001 and opened the relay port data under the JTAlert setup for WSJT-x and selected port 52001
.  I then changed the port input on SOCAT to agree with 52001 and logging data was transferred to all three programs.

5.  I then disabled the HamQTH lookup in JTAlert thinking that just maybe the timimg of lookup by JTAlert and transfer to the UDP port #52001 maybe a the cause but no it didn’t make any difference.


Conclusion unless you want me to test something else is:

UDP Data is correctly transferred from WSJT-x to either Logger32 or JTAlert with correct port settings.

UDP Data is correctly transferred via the relay function in WSJT-x setup in JTAlert to Logger32 with all three logging correctly, hoever no call book services are available.

UDP data from the relay function in WSJT-x in JTAlert port #52001 is correctly read by the Logger32 TCP server.  All three programs correctly logged the data, no call book data is avaiable.

UDP data from port with in the Last QSO API port seems to work occasionally on startup but is not consistent and for all practial means "dead" on my system.

I am going to continue to test various port settings and methods and will as you may suggest.  I will also in the enxt few days set the debug functions as per your earlier request.

TU for all your help and recommendations.

73 de Ron W4LDE

Ron,

Good to see some extensive testing. I don't have an answer to what your observing until I get some debug data to analyse.

A couple of points.
  1. Regardless of the UDP settings, HamQTH lookups should not be affected. The XML lookups are done using standard http (port 80) or https (port 443) web access. Missconfigured UDP ports should not be affecting them. The XML lookups are independent and if they are breaking then something significant is happening, likely some sort of application interference in the lookup mechanism. XML lookups are only executed at the time the DX Call in WSJT-X is changed so are finished long before any logging actions are performed.

  2. I don't know if Logger32 is expecting TCP or UDP. If it is TCP, then that will be a problem as the last QSO API is UDP only, there is none of the handshaking required with TCP, the packet is simply sent regardless of the ready status of any application waiting for a packet of the port.

  3. There is no port configuration involved in JTAlert logging of WSJT-X QSOs, the port used is determined by examining the UDP port settings within the WSJT-X config file and is not related to the last QSO API port.

de Laurie VK3AMA


locked Re: Hamspots load

HamApps Support (VK3AMA)
 

On 4/08/2018 11:45 PM, Michael Black via Groups.Io wrote:
Hi Laurie,
A while ago you had changed the spots on hamspots.net to sort the call signs but I think you removed it due to server load or some other reason.

I was think that perhaps only updating when the window is visible might reduce the server load considerably as I doubt many people keep that window visible...but quite possible running in the background.

There's a visibility.js script that should help....and maybe we can sort again?


de Mike W9MDB
Mike,

Refresh my memory, where on HamSpots did I change the display sorting?

de Laurie VK3AMA


locked Re: Wanted alert for "CQ DX" fail

HamApps Support (VK3AMA)
 

On 1/08/2018 11:47 AM, HamApps Support (VK3AMA) wrote:
There might be something unusual with your config, Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis.
Franco,

Thanks for sending your files. Unfortunately there is nothing in you config that could account for the problem you reported. You will need to enable debug recording in JTAlert and submit a new support request next time this happens.
Do the following...
  1. Enable debug recording via the "Settings -> Enable Debug Recording" JTAlert title-bar menu.
  2. Restart JTAlert, that is close JTAlert and then start JTAlert.
  3. Operate as normal.
  4. Once you observe the problem, send another support email with details of the utc time and Callsign calling CQ DX that did not alert correctly.
  5. Leave the "Enable Debug Recording" menu enabled.
  6. Once a solution is found for your problem you can turn off debugging.
It is OK to leave debug recording enabled for days/weeks until you observe the problem.

de Laurie VK3AMA


locked Keeping or Deleting old WSJT-x .wav files, unwanted WSJT .c2 Files. Benefits and Hazzards.

Mark W2OR
 

It might be beneficial for newbies to read on this (great) list serve the benefits and hazzards of deleting, or keeping, the relatively unused .wav and .c2 files in WSJT-x.  Other than the Sample lessons, perhaps someone could explain what they are, why they are kept on disc, how they are sometimes used, and how much disc space they can take up as the months pass by, using WSJT-X.  Thank you.   

p.s.  Ctrl+O opens the file location where one can observe the number and size of these files.


locked Re: LAST QSO API - UDP function

w4lde
 

Laurie,


I tested the API - UDP port #52001 log output with HamQTH data add running several different setups trying to determine where the data stream stopped.

Ist - regardless of the port selections and methods selected for logging the internal WSJT-x and JTAlert logging worked100% of the time during my tests.

The logging program I use which is Logger32 has both TCP and UDP capabilities.  For my initial test I select the UDP port in Logger32 to match the port number from either WSJT-x in standalone, #2237,  WSJT-x and JTAlert using the API-UDP port #52001 and finally the Relay of WSJT-x data stream via the relay data selection under the WSJT-s setup in JTAlert I used port number #2234

1.Using only running WSJT-x on port 2237 and Logger32 in monitor UDP every time we hit the log QSO it logged to two (2) places, WSJT-x and Logger32.  The data in the log was as provided by WSJT-x..  JTAlert was not operating.

2. I then started JTAlert which is set to auto start WSJT-x.  The Last QSO API UDP port setting was #52001.  I set the Logger32 UDP port to monitor 52001.  When manually set to log, no data was transferred to Logger32 but did log WSJT-x and JTAlert correctly.

3.  I then changed the UDP port in Logger32 to 2234  and set the API UDP port to 2234 after I had disabled the WSJT-x relay function in JTAlert. When manually set to log both JTAlert and WSJT-x logs logged as expected but no data was transferred to Logger32.  So now we had two (2) UDPports set in the Last QSO API UDP port and neither would transfer the data.

4.  I then tried to use the TCP server function in Logger32 using SOCAT to convert UDP to TCP. 
The port setting was 52001 under Last QSO AOI and also Socate, no logging data was transmitted.  I closed that API Last QSO and 52001 and opened the relay port data under the JTAlert setup for WSJT-x and selected port 52001
.  I then changed the port input on SOCAT to agree with 52001 and logging data was transferred to all three programs.

5.  I then disabled the HamQTH lookup in JTAlert thinking that just maybe the timimg of lookup by JTAlert and transfer to the UDP port #52001 maybe a the cause but no it didn’t make any difference.


Conclusion unless you want me to test something else is:

UDP Data is correctly transferred from WSJT-x to either Logger32 or JTAlert with correct port settings.

UDP Data is correctly transferred via the relay function in WSJT-x setup in JTAlert to Logger32 with all three logging correctly, hoever no call book services are available.

UDP data from the relay function in WSJT-x in JTAlert port #52001 is correctly read by the Logger32 TCP server.  All three programs correctly logged the data, no call book data is avaiable.

UDP data from port with in the Last QSO API port seems to work occasionally on startup but is not consistent and for all practial means "dead" on my system.

I am going to continue to test various port settings and methods and will as you may suggest.  I will also in the enxt few days set the debug functions as per your earlier request.

TU for all your help and recommendations.

73 de Ron W4LDE


locked Hamspots load

Michael Black
 

Hi Laurie,
A while ago you had changed the spots on hamspots.net to sort the call signs but I think you removed it due to server load or some other reason.

I was think that perhaps only updating when the window is visible might reduce the server load considerably as I doubt many people keep that window visible...but quite possible running in the background.

There's a visibility.js script that should help....and maybe we can sort again?


de Mike W9MDB



locked Re: JTAlert 2.12.3 Updated and is not working properly at all..

HamApps Support (VK3AMA)
 

On 4/08/2018 2:15 PM, kw7m07 via Groups.Io wrote:
Hi all, here we go.. I just made the update on JTAlert from 2.11.? to the latest 2.12.3. Let me tell you, I sure did not expect this.. All fields are fully populated with call signs from all over the country. The program will not respond to WSJT - X 1.9.1 when decode is complete. JTAlert continuously populates the call signs about every 8 seconds. And none of the calls are what is showing on WSJT screen after a decode. I also cannot get any of the highlight selections from WSJT to appear in the JTAlert Call selection for Name, QTH, GRID,  ect…  I am running Windows 10, with Signalink to an FT-890 Yaesu, I have match all the setting to the previouse and have triple checked!!  Have not had any issues what so ever since the first of the year with this program. It has been flawless, so, You can imagine my surprise and confusion. I have rebooted after each download, I have uninstalled  and reinstalled about a half a dozen times the whole program and still to this point no success. Hoping for a directional pointer at this point.. Help!!

Mike
KW7M
Mike,

If JTAlert appears to be in a loop repeatedly displaying the same old decodes, the likely cause is having the UDP received packets rebroadcast enabled and the port incorrectly set to the same port JTAlert is receiving UDP data from WSJT-X.

Open the JTAlert Settings, Applications->WSJT-X section. Is the UDP rebroadcast enabled? If so what port is being used, is it 2237?

Unless your using the rebroadcast for applications like GridTracker, turn it off. If you need it on, change the port to a port different from what WSJT-X has set for the UDP Server port.

Let me know what you discover.

de Laurie VK3AMA


locked JTAlert 2.12.3 Updated and is not working properly at all..

kw7m07@...
 

Hi all, here we go.. I just made the update on JTAlert from 2.11.? to the latest 2.12.3. Let me tell you, I sure did not expect this.. All fields are fully populated with call signs from all over the country. The program will not respond to WSJT - X 1.9.1 when decode is complete. JTAlert continuously populates the call signs about every 8 seconds. And none of the calls are what is showing on WSJT screen after a decode. I also cannot get any of the highlight selections from WSJT to appear in the JTAlert Call selection for Name, QTH, GRID,  ect…  I am running Windows 10, with Signalink to an FT-890 Yaesu, I have match all the setting to the previouse and have triple checked!!  Have not had any issues what so ever since the first of the year with this program. It has been flawless, so, You can imagine my surprise and confusion. I have rebooted after each download, I have uninstalled  and reinstalled about a half a dozen times the whole program and still to this point no success. Hoping for a directional pointer at this point.. Help!!

Mike
KW7M


locked Re: JTAlert-X won't send QSO's to HRD anymore

Rick Wines
 

Mike is just that, a guy who was put here to help those of us who don’t know the program as Mike does. He CALLED me and we spent about 2 hours going over the settings, so were right, many were not. He also found a glitch in my reception side of WSJT-X that the company is still researching on and can’t wait until I hear from them. He is indeed a “wealth of knowledge”.

 

Rick, W5FKW

Round Rock, TX

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Robert
Sent: Thursday, August 2, 2018 7:26 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert-X won't send QSO's to HRD anymore

 

I want to say a sincere thanks to Mike Black, W9MDB, for his help and knowledge of many things, of primary interest to me was getting WSJT-X working again.
That took Mike about 60 seconds to fix, after he found out that I used to be running a Beta version of WSJT-X, and somehow, it was updated to 1.9.1 and the upgrade wiped out everything in the Settings/Frequencies tab.  Somehow, I can't remember exactly how he did it, he repopulated this tab, and everything was working fine once again.
  But he also showed me a great deal about WSJT-X, JTAlertX, and proper use of my radio, and the SignaLink for best use in all the digital modes.
I am simply amazed at his wealth of knowledge and thankful for his help and suggestions for tweaking all this complexity to work at it's peak without stressing the radio while maintaining a powerful, but clean signal.

Now I have to write everything down so in case of something else going awry, I can put it back.  

Thanks,

Robert AC2MM

 

On 8/1/2018 11:31 PM, Michael Black via Groups.Io wrote:

Signalink is PTT only via VOX triggering from the PC side.  No CAT.

 

de Mike W9MDB

 

 

 

 

On Wednesday, August 1, 2018, 8:04:00 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

 

 

Robert,

So much going on in your description.

Does the SignalLink support CAT control?
I suggest, you get WSJT-X HRD Cat Control working first, then move onto
Getting JTAlert Logging working.

de Laurie VK3AMA

On 2/08/2018 10:03 AM, Robert wrote:
> This is one of those issue where you don't know who to ask because
> there are several things in play here.
>
> My understanding of JTAlert-X is that it is responsible for looking up
> the QSO info on QRZ.com, and installing the name and such to the
> completed QSO from WSJT, and sending it on it's way to the HRD
> Logbook, "My Logbook".
> While I have been using this successfully for about a year now with no
> problems with my Kenwood TS-590S and HRD, I had to install a SignaLink
> sound card for other reasons.  I don't use the Kenwood internal
> soundcard anymore.
>
> Rather than get Carpel Tunnel from retyping everything, let me paste
> my question I posted recently to the WSJT Users Group.
> Please understand that the most important part of these two problems
> (for me) is to get JTAlert-X to send a completed QSO to the HRD
> Logbook.   That's why I'm here.
>
> I'm having a problem setting up WSJT-X (1.9.1) / JTAlertX  to work with
> HRD like it used to.
> To simplify digital mode control, I eliminated using the Kenwood TS-590S
> sound card, and reinstalled my SignaLink sound card instead.  HRD helped
> me with the setup and the DM-780 is working fine for all digital modes,
> logging included.
>
> WSJT / JTAlertX used to work perfectly with HRD before this point also,
> logging all my contacts from WSJT/JTAlertX into HRD, changing the radio
> frequency as I switched WSJT to different bands/modes, etc. Perfect.
>
> Two problems:  (HRD running as normal)
> 1.  I have no CAT control.  I can't change bands, in fact the bands
> window doesn't show you what band you are on.  Before using the
> SignaLink, I would simply change to another band/frequency using the
> dropdown box, then the radio would change to that band/frequency, as
> well as the SteppIR antenna.
> It transmits fine, receives fine, and the Power and Receive levels are
> controlled via the SignaLink as they should be now.  Strangely enough,
> if I change the band on the radio, WSJT will follow suit, but the
> dropdown box will not work that shows you what frequency you should be on.
>
> 2.  It logs the QSO's into the WSJT ADIF file, but JTAlertX does not
> transfer the completed QSO into HRD anymore.
>
> Here is my setup as best i can describe it.
>
> HRD for software.
> Kenwood TS-590S
> SignaLink sound card.
> Win10 OS.
>
> Kenwood TS-590S, Menu #63 Set to ACC2 port for Data Communication.
> One cable from the Kenwood ACC2 Port into the SignaLink USB port, then
> the outgoing SignaLink port (Radio) going to USB #5 Codec in the computer.
> One cable from the Kenwood USB port direct to the USB #8 Codec in the
> computer. (for HRD control)
>
> WSJT Settings
>
> Tab "Radio"
> Rig:  Kenwood TS-590S
> Left Pane:  COM 4   (USB #5 Codec), Eight, two, Hardware
> Right Pane:   CAT, Rear Data, USB, None
>
> Tab "Audio"
> Audio:   Both Input & Output  (5-USB Audio Codec)
>
> JTAlertX Settings
>
> Enable HRD V5/VB6 Logging, Checked
> Settings / HRD V5/V6 / PC IPv4 Address  127.0.0.1
> Settings / Sound Card / [3] Speakers / headphones (Realtek)  (This
> enables JTAlertX to announce the wanted Countries, etc through the
> stereo speaker system)
>
> That's everything I can think of to describe my situation.
> I had a previous WSJT situation which I won't go into now because adding
> the SignaLink cured that problem. (as well as some others)
>
> So the current status is that WSJT and JTAlert-X is working as it's
> own entity.
> 1.  JTAletrs-X won't send completed logs to HRD.
> 2.  I have no CAT control using WSJT.
>
> These are probably related, I don't know, but I'm looking for help
> from wherever I can get it.
>
> Thanks in advance,
> Robert  AC2MM



 


--
Being an absolute "newbie" to JTAlert (four days), what does the asterisk denote to the left of the callsign in the callsign bars?

Rick Wines, W5FKW


locked Re: JTAlert-X won't send QSO's to HRD anymore

Robert <Robert@...>
 

I want to say a sincere thanks to Mike Black, W9MDB, for his help and knowledge of many things, of primary interest to me was getting WSJT-X working again.
That took Mike about 60 seconds to fix, after he found out that I used to be running a Beta version of WSJT-X, and somehow, it was updated to 1.9.1 and the upgrade wiped out everything in the Settings/Frequencies tab.  Somehow, I can't remember exactly how he did it, he repopulated this tab, and everything was working fine once again.
  But he also showed me a great deal about WSJT-X, JTAlertX, and proper use of my radio, and the SignaLink for best use in all the digital modes.
I am simply amazed at his wealth of knowledge and thankful for his help and suggestions for tweaking all this complexity to work at it's peak without stressing the radio while maintaining a powerful, but clean signal.

Now I have to write everything down so in case of something else going awry, I can put it back.  

Thanks,

Robert AC2MM


On 8/1/2018 11:31 PM, Michael Black via Groups.Io wrote:
Signalink is PTT only via VOX triggering from the PC side.  No CAT.

de Mike W9MDB




On Wednesday, August 1, 2018, 8:04:00 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


Robert,

So much going on in your description.

Does the SignalLink support CAT control?
I suggest, you get WSJT-X HRD Cat Control working first, then move onto
Getting JTAlert Logging working.

de Laurie VK3AMA

On 2/08/2018 10:03 AM, Robert wrote:
> This is one of those issue where you don't know who to ask because
> there are several things in play here.
>
> My understanding of JTAlert-X is that it is responsible for looking up
> the QSO info on QRZ.com, and installing the name and such to the
> completed QSO from WSJT, and sending it on it's way to the HRD
> Logbook, "My Logbook".
> While I have been using this successfully for about a year now with no
> problems with my Kenwood TS-590S and HRD, I had to install a SignaLink
> sound card for other reasons.  I don't use the Kenwood internal
> soundcard anymore.
>
> Rather than get Carpel Tunnel from retyping everything, let me paste
> my question I posted recently to the WSJT Users Group.
> Please understand that the most important part of these two problems
> (for me) is to get JTAlert-X to send a completed QSO to the HRD
> Logbook.   That's why I'm here.
>
> I'm having a problem setting up WSJT-X (1.9.1) / JTAlertX  to work with
> HRD like it used to.
> To simplify digital mode control, I eliminated using the Kenwood TS-590S
> sound card, and reinstalled my SignaLink sound card instead.  HRD helped
> me with the setup and the DM-780 is working fine for all digital modes,
> logging included.
>
> WSJT / JTAlertX used to work perfectly with HRD before this point also,
> logging all my contacts from WSJT/JTAlertX into HRD, changing the radio
> frequency as I switched WSJT to different bands/modes, etc. Perfect.
>
> Two problems:  (HRD running as normal)
> 1.  I have no CAT control.  I can't change bands, in fact the bands
> window doesn't show you what band you are on.  Before using the
> SignaLink, I would simply change to another band/frequency using the
> dropdown box, then the radio would change to that band/frequency, as
> well as the SteppIR antenna.
> It transmits fine, receives fine, and the Power and Receive levels are
> controlled via the SignaLink as they should be now.  Strangely enough,
> if I change the band on the radio, WSJT will follow suit, but the
> dropdown box will not work that shows you what frequency you should be on.
>
> 2.  It logs the QSO's into the WSJT ADIF file, but JTAlertX does not
> transfer the completed QSO into HRD anymore.
>
> Here is my setup as best i can describe it.
>
> HRD for software.
> Kenwood TS-590S
> SignaLink sound card.
> Win10 OS.
>
> Kenwood TS-590S, Menu #63 Set to ACC2 port for Data Communication.
> One cable from the Kenwood ACC2 Port into the SignaLink USB port, then
> the outgoing SignaLink port (Radio) going to USB #5 Codec in the computer.
> One cable from the Kenwood USB port direct to the USB #8 Codec in the
> computer. (for HRD control)
>
> WSJT Settings
>
> Tab "Radio"
> Rig:  Kenwood TS-590S
> Left Pane:  COM 4   (USB #5 Codec), Eight, two, Hardware
> Right Pane:   CAT, Rear Data, USB, None
>
> Tab "Audio"
> Audio:   Both Input & Output  (5-USB Audio Codec)
>
> JTAlertX Settings
>
> Enable HRD V5/VB6 Logging, Checked
> Settings / HRD V5/V6 / PC IPv4 Address  127.0.0.1
> Settings / Sound Card / [3] Speakers / headphones (Realtek)  (This
> enables JTAlertX to announce the wanted Countries, etc through the
> stereo speaker system)
>
> That's everything I can think of to describe my situation.
> I had a previous WSJT situation which I won't go into now because adding
> the SignaLink cured that problem. (as well as some others)
>
> So the current status is that WSJT and JTAlert-X is working as it's
> own entity.
> 1.  JTAletrs-X won't send completed logs to HRD.
> 2.  I have no CAT control using WSJT.
>
> These are probably related, I don't know, but I'm looking for help
> from wherever I can get it.
>
> Thanks in advance,
> Robert  AC2MM






locked Re: LAST QSO API - UDP function

HamApps Support (VK3AMA)
 

On 3/08/2018 6:51 AM, w4lde wrote:
that will help identify were the problem lies.
Ron,

If you discover the cause of the logging failure through your packet sniffing, please advise, even if it is not something within JTAlert.

Thanks,
de Laurie VK3AMA


locked Re: LAST QSO API - UDP function

HamApps Support (VK3AMA)
 

On 3/08/2018 4:55 AM, w4lde wrote:

I have been using WSJT-x and JTAlert for a long time and about a year ago successfully used a program called "Socat" to listen to a

UDP broadcast on port 52001 and automatically transfer the data to a TCP 127.0.0.1 port #52001 for logging to a non-supported log program which is "Logger32".

Some time within the last month I started to see that, after starting WSJT-x and Socat through the auto start feature of JTAlert, only the first

logged QSO would transfer and logging occur in logger32.  I thought a firewall maybe the problem but have tested and temporarily stop the firewalls and antivirus program with no change.

The logging from both JTAlert and WSJT-x occur as expected.  The QSO log API does indeed save the last QSO.  O.S. is Win10 ver-1803, both JTAlert and Logger32 are current.

Can anyone suggest a program that can monitor a UDP packet ADIF transmission from JTAlert or any other hints?

This isn't a show stopper since I'm grateful for the functions that JTAlert provides and I can always import the saved logs saved by either WSJT-x or JTAlert.  A nice convenience is missed.

Thanks de Ron W4LDE

Ron,

There is nothing special about the UDP broadcast of the last logged QSO. A socket connection is opened to the destination IP/Port, the data is sent and then the socket is closed. This sequence is repeated for each logging.

JTAlert does capture any error conditions encountered associated with this. Do the following...

  • Enable debug recording via the "Settings -> Enable Debug Recording" JTAlert title-bar menu.
  • Restart JTAlert, that is close JTAlert and then start JTAlert.
  • Operate as normal.
  • Once the logging failure occurs send a JTAlert support request (the "? -> Contact Support" menu). Include a note of the Callsign and UTC time.
  • Leave the "Enable Debug Recording" menu enabled.
  • Once a solution is found for your problem you can turn off debugging.

de Laurie VK3AMA


locked Re: JTAlert-X won't send QSO's to HRD anymore

Dave Garber
 

Are you running wsjt in usb.   Or usb data?


On Thu, Aug 2, 2018, 4:43 PM Robert, <Robert@...> wrote:
Hi Dave,
I recently switched over to the SignaLink due to too many issues with the KW soundcard, WinOS, etc.

On the rear of the 590S, HRD said I need the Kenwood USB to computer COM cable for HRD to work.  Done.   HRD works fine.

The KW ACC2 Port, normally used for Data Communications, is once again hooked to the SignaLink on one side, the outgoing side goes to the other Com port on the computer.  the KW Menu #63 is set for ACC2, for Data Communications.

The DB9 Serial connector is connected to my SteppIR antenna, SDA 100 Controller.

Everything is set for 9600 Baud, because that's what the SteppIR requires.   Before the SignaLink, when I was running WSJT & JTAlert-X, if I made a band change in WSJT, the radio would switch to that frequency, and so would the antenna.


Now, when I'm running the DM-780 program, that's the way it works with the SignaLink installed.  Perfect.  When I switch bands, radio and antenna follows.
Can't do the same thing using WSJT however.
If I make a Radio change, WSJT will follow.
But WSJT can't initiate a change anymore without Cat control.

I know it's a setting somehow in WSJT, but neither I nor HRD can find it.

Thanks,

Robert AC2MM


On 8/1/2018 9:18 PM, Dave Garber wrote:
I have hrd on a ts590sg, with cat , if I can help.  you must have the db9 connection on the back, while the signalink should be set to vox, for ptt.  do you have the serial port via a usb adapter??

need more info on how you expect cat...  not via the signalink usb


Dave Garber
VE3WEJ / VE3IE

On Wed, Aug 1, 2018 at 9:16 PM, Robert <Robert@...> wrote:
de Laurie,
Oops, I know you didn't see my latest post because I asked the Moderator to pull the post itself.  I got it working again, most likely due to a reboot, but it's sending logs normally now again to HRD.  Sorry about that miscommunication.

Thanks,

Robert AC2MM


On 8/1/2018 9:09 PM, Robert wrote:
de Laurie,
If you saw my latest post, the JTAlert-X/Logging issue is resolved.
The CAT issue remains the final problem I need help with.

Thanks,

Robert AC2MM


On 8/1/2018 9:03 PM, HamApps Support (VK3AMA) wrote:
Robert,

So much going on in your description.

Does the SignalLink support CAT control?
I suggest, you get WSJT-X HRD Cat Control working first, then move onto Getting JTAlert Logging working.

de Laurie VK3AMA

On 2/08/2018 10:03 AM, Robert wrote:
This is one of those issue where you don't know who to ask because there are several things in play here.

My understanding of JTAlert-X is that it is responsible for looking up the QSO info on QRZ.com, and installing the name and such to the completed QSO from WSJT, and sending it on it's way to the HRD Logbook, "My Logbook".
While I have been using this successfully for about a year now with no problems with my Kenwood TS-590S and HRD, I had to install a SignaLink sound card for other reasons.  I don't use the Kenwood internal soundcard anymore.

Rather than get Carpel Tunnel from retyping everything, let me paste my question I posted recently to the WSJT Users Group.
Please understand that the most important part of these two problems (for me) is to get JTAlert-X to send a completed QSO to the HRD Logbook.   That's why I'm here.

I'm having a problem setting up WSJT-X (1.9.1) / JTAlertX  to work with
HRD like it used to.
To simplify digital mode control, I eliminated using the Kenwood TS-590S
sound card, and reinstalled my SignaLink sound card instead. HRD helped
me with the setup and the DM-780 is working fine for all digital modes,
logging included.

WSJT / JTAlertX used to work perfectly with HRD before this point also,
logging all my contacts from WSJT/JTAlertX into HRD, changing the radio
frequency as I switched WSJT to different bands/modes, etc. Perfect.

Two problems:  (HRD running as normal)
1.  I have no CAT control.  I can't change bands, in fact the bands
window doesn't show you what band you are on.  Before using the
SignaLink, I would simply change to another band/frequency using the
dropdown box, then the radio would change to that band/frequency, as
well as the SteppIR antenna.
It transmits fine, receives fine, and the Power and Receive levels are
controlled via the SignaLink as they should be now.  Strangely enough,
if I change the band on the radio, WSJT will follow suit, but the
dropdown box will not work that shows you what frequency you should be on.

2.  It logs the QSO's into the WSJT ADIF file, but JTAlertX does not
transfer the completed QSO into HRD anymore.

Here is my setup as best i can describe it.

HRD for software.
Kenwood TS-590S
SignaLink sound card.
Win10 OS.

Kenwood TS-590S, Menu #63 Set to ACC2 port for Data Communication.
One cable from the Kenwood ACC2 Port into the SignaLink USB port, then
the outgoing SignaLink port (Radio) going to USB #5 Codec in the computer.
One cable from the Kenwood USB port direct to the USB #8 Codec in the
computer. (for HRD control)

WSJT Settings

Tab "Radio"
Rig:  Kenwood TS-590S
Left Pane:  COM 4   (USB #5 Codec), Eight, two, Hardware
Right Pane:   CAT, Rear Data, USB, None

Tab "Audio"
Audio:   Both Input & Output  (5-USB Audio Codec)

JTAlertX Settings

Enable HRD V5/VB6 Logging, Checked
Settings / HRD V5/V6 / PC IPv4 Address  127.0.0.1
Settings / Sound Card / [3] Speakers / headphones (Realtek) (This
enables JTAlertX to announce the wanted Countries, etc through the
stereo speaker system)

That's everything I can think of to describe my situation.
I had a previous WSJT situation which I won't go into now because adding
the SignaLink cured that problem. (as well as some others)

So the current status is that WSJT and JTAlert-X is working as it's own entity.
1.  JTAletrs-X won't send completed logs to HRD.
2.  I have no CAT control using WSJT.

These are probably related, I don't know, but I'm looking for help from wherever I can get it.

Thanks in advance,
Robert  AC2MM















locked Re: LAST QSO API - UDP function

w4lde
 

Thanks Mike, that will help identify were the problem lies.


locked Re: JTAlert-X won't send QSO's to HRD anymore

Robert <Robert@...>
 

Hi Dave,
I recently switched over to the SignaLink due to too many issues with the KW soundcard, WinOS, etc.

On the rear of the 590S, HRD said I need the Kenwood USB to computer COM cable for HRD to work.  Done.   HRD works fine.

The KW ACC2 Port, normally used for Data Communications, is once again hooked to the SignaLink on one side, the outgoing side goes to the other Com port on the computer.  the KW Menu #63 is set for ACC2, for Data Communications.

The DB9 Serial connector is connected to my SteppIR antenna, SDA 100 Controller.

Everything is set for 9600 Baud, because that's what the SteppIR requires.   Before the SignaLink, when I was running WSJT & JTAlert-X, if I made a band change in WSJT, the radio would switch to that frequency, and so would the antenna.


Now, when I'm running the DM-780 program, that's the way it works with the SignaLink installed.  Perfect.  When I switch bands, radio and antenna follows.
Can't do the same thing using WSJT however.
If I make a Radio change, WSJT will follow.
But WSJT can't initiate a change anymore without Cat control.

I know it's a setting somehow in WSJT, but neither I nor HRD can find it.

Thanks,

Robert AC2MM


On 8/1/2018 9:18 PM, Dave Garber wrote:
I have hrd on a ts590sg, with cat , if I can help.  you must have the db9 connection on the back, while the signalink should be set to vox, for ptt.  do you have the serial port via a usb adapter??

need more info on how you expect cat...  not via the signalink usb


Dave Garber
VE3WEJ / VE3IE

On Wed, Aug 1, 2018 at 9:16 PM, Robert <Robert@...> wrote:
de Laurie,
Oops, I know you didn't see my latest post because I asked the Moderator to pull the post itself.  I got it working again, most likely due to a reboot, but it's sending logs normally now again to HRD.  Sorry about that miscommunication.

Thanks,

Robert AC2MM


On 8/1/2018 9:09 PM, Robert wrote:
de Laurie,
If you saw my latest post, the JTAlert-X/Logging issue is resolved.
The CAT issue remains the final problem I need help with.

Thanks,

Robert AC2MM


On 8/1/2018 9:03 PM, HamApps Support (VK3AMA) wrote:
Robert,

So much going on in your description.

Does the SignalLink support CAT control?
I suggest, you get WSJT-X HRD Cat Control working first, then move onto Getting JTAlert Logging working.

de Laurie VK3AMA

On 2/08/2018 10:03 AM, Robert wrote:
This is one of those issue where you don't know who to ask because there are several things in play here.

My understanding of JTAlert-X is that it is responsible for looking up the QSO info on QRZ.com, and installing the name and such to the completed QSO from WSJT, and sending it on it's way to the HRD Logbook, "My Logbook".
While I have been using this successfully for about a year now with no problems with my Kenwood TS-590S and HRD, I had to install a SignaLink sound card for other reasons.  I don't use the Kenwood internal soundcard anymore.

Rather than get Carpel Tunnel from retyping everything, let me paste my question I posted recently to the WSJT Users Group.
Please understand that the most important part of these two problems (for me) is to get JTAlert-X to send a completed QSO to the HRD Logbook.   That's why I'm here.

I'm having a problem setting up WSJT-X (1.9.1) / JTAlertX  to work with
HRD like it used to.
To simplify digital mode control, I eliminated using the Kenwood TS-590S
sound card, and reinstalled my SignaLink sound card instead. HRD helped
me with the setup and the DM-780 is working fine for all digital modes,
logging included.

WSJT / JTAlertX used to work perfectly with HRD before this point also,
logging all my contacts from WSJT/JTAlertX into HRD, changing the radio
frequency as I switched WSJT to different bands/modes, etc. Perfect.

Two problems:  (HRD running as normal)
1.  I have no CAT control.  I can't change bands, in fact the bands
window doesn't show you what band you are on.  Before using the
SignaLink, I would simply change to another band/frequency using the
dropdown box, then the radio would change to that band/frequency, as
well as the SteppIR antenna.
It transmits fine, receives fine, and the Power and Receive levels are
controlled via the SignaLink as they should be now.  Strangely enough,
if I change the band on the radio, WSJT will follow suit, but the
dropdown box will not work that shows you what frequency you should be on.

2.  It logs the QSO's into the WSJT ADIF file, but JTAlertX does not
transfer the completed QSO into HRD anymore.

Here is my setup as best i can describe it.

HRD for software.
Kenwood TS-590S
SignaLink sound card.
Win10 OS.

Kenwood TS-590S, Menu #63 Set to ACC2 port for Data Communication.
One cable from the Kenwood ACC2 Port into the SignaLink USB port, then
the outgoing SignaLink port (Radio) going to USB #5 Codec in the computer.
One cable from the Kenwood USB port direct to the USB #8 Codec in the
computer. (for HRD control)

WSJT Settings

Tab "Radio"
Rig:  Kenwood TS-590S
Left Pane:  COM 4   (USB #5 Codec), Eight, two, Hardware
Right Pane:   CAT, Rear Data, USB, None

Tab "Audio"
Audio:   Both Input & Output  (5-USB Audio Codec)

JTAlertX Settings

Enable HRD V5/VB6 Logging, Checked
Settings / HRD V5/V6 / PC IPv4 Address  127.0.0.1
Settings / Sound Card / [3] Speakers / headphones (Realtek) (This
enables JTAlertX to announce the wanted Countries, etc through the
stereo speaker system)

That's everything I can think of to describe my situation.
I had a previous WSJT situation which I won't go into now because adding
the SignaLink cured that problem. (as well as some others)

So the current status is that WSJT and JTAlert-X is working as it's own entity.
1.  JTAletrs-X won't send completed logs to HRD.
2.  I have no CAT control using WSJT.

These are probably related, I don't know, but I'm looking for help from wherever I can get it.

Thanks in advance,
Robert  AC2MM















locked Re: Wanted state or country option if callsign is LOTW or eQSL only?

Ross KE4BCN
 

Thank you that is what I was looking for.

16001 - 16020 of 37225