Date   

locked Re: No decodes form WSJT-X showing in JTALERT-X call sign line

Joe Subich, W4TV
 

UDP server = 127.0.0.1
This *is not* a multicast address. See Help -> WSJT-X UDP Setup
in JTAlert and select a valid multicast address in the range
224.0.0.1 to 224.0.0.255 or 239.255.0.1 to 239.255.255.255.

I use the recommended 224.0.0.1

73,

... Joe, W4TV


On 2021-07-08 11:12 AM, lmeeny wrote:
Dave,
Here are the WSJT-X UDP network server settings I'm using.
UDP server = 127.0.0.1
UDP server port number = 2237
All three UDP option boxes are checked.
On JTALERT-X WSJT-X UDP multicast on loopback is selected.

From About JTALERT-X help
JTAlert Instance      : #1
JTAlert Start Params  : /wsjtx
WSJT-X Window Title   : WSJT-X   v2.2.2   by K1JT, G4WJS, and K9AN
WSJT-X Command Line   : "C:\WSJT\wsjtx\bin\wsjtx.exe"
WSJT-X   --rig-name   :
WSJT-X Config File    : C:\Users\Ed Machak\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version               :
WSJT-X Revision              :
WSJT-X Spec Op Mode          : None
WSJT-X UDP ID                :
WSJT-X UDP Port              : 2237
WSJT-X UDP Server            : localhost
WSJT-X UDP MCast on Loopback : True
WSJT-X UDP Max Schema        :
Are these the proper values? If so, where should I look next?
The current versions of the two programs have played nice in the past.
73
Ed W2GHD
On Thu, Jul 8, 2021 at 04:30 AM, Dave Garber wrote:


check your udp settings in wsjt.   I don't believe DAX has anything to do
with communication.. it's an audio interface of sorts.



Dave Garber
VE3WEJ / VE3IE

On Wed, Jul 7, 2021 at 5:14 PM lmeeny < emachak@stny.rr.com > wrote:

Hello,

I recently installed the FLEX SmartSDR suite (DAX) and have lost
communication between WSJT-X(2.2.2) and JTALERT-X (2.16.17). No decodes
are being passed to JTALERT-X.

When selecting the sound card in JTALERT-X what's the proper source?

73

Ed W2GHD





locked Re: No decodes form WSJT-X showing in JTALERT-X call sign line

lmeeny
 

Dave,

Here are the WSJT-X UDP network server settings I'm using.

UDP server = 127.0.0.1
UDP server port number = 2237
All three UDP option boxes are checked.

On JTALERT-X WSJT-X UDP multicast on loopback is selected.

From About JTALERT-X help

JTAlert Instance      : #1
JTAlert Start Params  : /wsjtx
WSJT-X Window Title   : WSJT-X   v2.2.2   by K1JT, G4WJS, and K9AN
WSJT-X Command Line   : "C:\WSJT\wsjtx\bin\wsjtx.exe"
WSJT-X   --rig-name   :
WSJT-X Config File    : C:\Users\Ed Machak\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version               :
WSJT-X Revision              :
WSJT-X Spec Op Mode          : None
WSJT-X UDP ID                :
WSJT-X UDP Port              : 2237
WSJT-X UDP Server            : localhost
WSJT-X UDP MCast on Loopback : True
WSJT-X UDP Max Schema        :

Are these the proper values? If so, where should I look next?

The current versions of the two programs have played nice in the past.

73

Ed W2GHD



On Thu, Jul 8, 2021 at 04:30 AM, Dave Garber wrote:
check your udp settings in wsjt.   I don't believe DAX has anything to do with communication.. it's an audio interface of sorts.
 
 
 
Dave Garber
VE3WEJ / VE3IE


On Wed, Jul 7, 2021 at 5:14 PM lmeeny <emachak@...> wrote:
Hello,

I recently installed the FLEX SmartSDR suite (DAX) and have lost communication between WSJT-X(2.2.2) and JTALERT-X (2.16.17). No decodes are being passed to JTALERT-X.

When selecting the sound card in JTALERT-X what's the proper source?

73

Ed W2GHD

 


locked Re: Unable to communicate

Eric Sutherland
 

Resolved, primary issue was not using desktop version of .NET (discovered thanks to FAQs). Logging does not seem to be working yet but I am just getting started on that.


locked Re: Single/double click within callsigns window not working

BOB K5HX
 

Ron,

Thanks for your reply.  
Yes,  I am using multicast and have the settings configured properly,

Bob K5HX


On Jul 8, 2021, at 7:37 AM, Ron W3RJW via groups.io <w3rjw@...> wrote:

Bob,

Have you told JTAlert you are using multi-cast ?

Settings, WSJT-X UDP Multicast on Loopback
--
73
Ron, W3RJW

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


locked Re: Unable to communicate

Eric Sutherland
 

This is a new installation and has never worked. I've used HRD for years, have just had wsjt-x installed for a couple of days and made a few contacts and decided to install JT Alert for the logging connection.


On Thu, Jul 8, 2021, 6:27 AM Dave Garber <ve3wej@...> wrote:
perhaps you had jtalert added to the mix before, and it was the go between needed to log to your old version of HRD


Dave Garber
VE3WEJ / VE3IE


On Wed, Jul 7, 2021 at 8:00 PM Eric Sutherland <sutherea@...> wrote:
Subject: Unable to communicate

I know you have seen this before but I have not found anything with the HRD 5 configuration So I do not know if it is related to that.

 

JT Alert 2.50.2

WSJT-X 2.4.0

HRD Logbook 5.24.0.38

 

Unable to communicate with the WSJT-X process.

  UDP Port : 2237

  IP Address : 127.0.0.1

  Values read from WSJT-X config file...

    C:\Users\papa_eric\AppData\Local\WSJT-X\WSJT-X.ini

 

WSJT-X Detected Instance...

  Process Window Title : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV

  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"

 

Decode alerts and logging will be unavailable until corrected.

 

I have tried changing the UDP port number.

 

I don’t know if there are any other files you might find helpful.

 

My register user info is: AJ4QR@...

Sent from Mail for Windows 10

 


locked Re: Single/double click within callsigns window not working

Ron W3RJW
 

Bob,

Have you told JTAlert you are using multi-cast ?

Settings, WSJT-X UDP Multicast on Loopback
--
73
Ron, W3RJW

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


locked Re: No decodes form WSJT-X showing in JTALERT-X call sign line

Dave Garber
 

check your udp settings in wsjt.   I don't believe DAX has anything to do with communication.. it's an audio interface of sorts.



Dave Garber
VE3WEJ / VE3IE


On Wed, Jul 7, 2021 at 5:14 PM lmeeny <emachak@...> wrote:
Hello,

I recently installed the FLEX SmartSDR suite (DAX) and have lost communication between WSJT-X(2.2.2) and JTALERT-X (2.16.17). No decodes are being passed to JTALERT-X.

When selecting the sound card in JTALERT-X what's the proper source?

73

Ed W2GHD


locked Re: Unable to communicate

Dave Garber
 

perhaps you had jtalert added to the mix before, and it was the go between needed to log to your old version of HRD


Dave Garber
VE3WEJ / VE3IE


On Wed, Jul 7, 2021 at 8:00 PM Eric Sutherland <sutherea@...> wrote:
Subject: Unable to communicate

I know you have seen this before but I have not found anything with the HRD 5 configuration So I do not know if it is related to that.

 

JT Alert 2.50.2

WSJT-X 2.4.0

HRD Logbook 5.24.0.38

 

Unable to communicate with the WSJT-X process.

  UDP Port : 2237

  IP Address : 127.0.0.1

  Values read from WSJT-X config file...

    C:\Users\papa_eric\AppData\Local\WSJT-X\WSJT-X.ini

 

WSJT-X Detected Instance...

  Process Window Title : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV

  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"

 

Decode alerts and logging will be unavailable until corrected.

 

I have tried changing the UDP port number.

 

I don’t know if there are any other files you might find helpful.

 

My register user info is: AJ4QR@...

Sent from Mail for Windows 10

 


locked Re: Single/double click within callsigns window not working

heath calhoun - kb5vai <hcalhoun@...>
 

Can you do a app rule for both like in windows 10 firewall?





-------- Original message --------
From: "BOB K5HX via groups.io" <k5hx@...>
Date: 7/7/21 18:53 (GMT-06:00)
To: Support@HamApps.groups.io
Subject: [HamApps] Single/double click within callsigns window not working

I have traced the inability of a single click within the callsign window of JTAlert to activate WSJT-x to ZoneAlarm security software.  If I shutdown ZoneAlarm all works as expected.  However, if I temporarily suspend the firewall within ZoneAlarm,  I still get no communication between WSJT-x and JTAlert which is strange.  Also,  I attempted to configure the firewall to allow inbound and outbound UDP traffic on port 2237 but wasn't sure if that was correct.  In any event it didn't solve the problem.

My JT-Alert info is as follows:

JTAlert Instance       : #1

JTAlert Start Params   : /wsjtx

WSJT-X Window Title    : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV

WSJT-X Command Line    : "C:\WSJT\wsjtx\bin\wsjtx.exe" 

WSJT-X   --rig-name    : 

WSJT-X Config File     : C:\Users\Bob\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Version         : 2.4.0

WSJT-X Revision        : c19d62

WSJT-X Spec Op Mode    : None

WSJT-X UDP ID          : WSJT-X

WSJT-X UDP Port        : 2237

WSJT-X UDP Server      : 239.255.0.1

WSJT-X UDP MCast on LB : True

WSJT-X UDP Max Schema  : 3

 

==================================================

UDP Ports used

--------------------------------------------------

JTAlert.exe           : 62399 60379

JTAlertV2.Manager.exe : 61968 61969 61970

JTAlertV2.Decodes.exe : 

 

 

==================================================

Audio output devices

--------------------------------------------------

[1] Speakers (Dell AC511 USB SoundBar)

[2] DELL U2414H (Intel(R) Display Audio)

[3] Navigator Transmit (2- USB Audio CODEC )

[4] DELL U2417H-4 (NVIDIA High Definition Audio)

 

 

==================================================

JTAlertV2.Manager (2.50.2.0) status

(2021-07-07 23:49:30 utc)

--------------------------------------------------

CLR Version       : 5.0.6

NET Framework     : .NET 5.0.6

Architecture      : x64 64bit

--------------------------------------------------

UDP Router        : Initialized : YES (WSJT-X)

Audio             : Initialized : YES (4 output devices)

Activity Service  : Initialized : YES (started : 58)

Messaging Service : Initialized : YES (started : 17)

HamSpots Service  : Initialized : YES

QRZ Xml           : Initialized : YES (K5HX)

HamQth Xml        : Initialized : YES 

QRZ Log           : Initialized : YES 

HamQth Log        : Initialized : YES 

ClubLog Log       : Initialized : YES 

Eqsl Log          : Initialized : YES 

HrdLog Log        : Initialized : YES 

DXLab DDE         : Initialized : YES

User Alert        : Initialized : YES

Updates Check     : Initialized : YES (started : 3600)

Environment Check : Initialized : YES (started : 3600)

Maintenance       : Initialized : YES (started : 3600)

--------------------------------------------------

Any suggestions are appreciated.

Bob   K5HX
 


locked Re: Failure to Alert On 13 Colonies European Calls

Stan Edwards - WA4DYD
 

Seems like you were right, Laurie.  Someone replied directly with a suggestion that I check "No WSL Filters, pass all Alerts" and that seems to work.  I tried it on some calls from a special event station in Slovenia, going back and forth between checking that an "LOTW OR eQSL(AG) member," and that did the trick, so I believe that solves the mystery.  Now to remember that between now and next Independence Day!  Perhaps I'll leave it set with the "No QSL Filters" option.

Thanks, Jim, for the tip.  You were a great help.

73,
Stan Edwards, WA4DYD


locked Unable to communicate

Eric Sutherland
 

Subject: Unable to communicate

I know you have seen this before but I have not found anything with the HRD 5 configuration So I do not know if it is related to that.

 

JT Alert 2.50.2

WSJT-X 2.4.0

HRD Logbook 5.24.0.38

 

Unable to communicate with the WSJT-X process.

  UDP Port : 2237

  IP Address : 127.0.0.1

  Values read from WSJT-X config file...

    C:\Users\papa_eric\AppData\Local\WSJT-X\WSJT-X.ini

 

WSJT-X Detected Instance...

  Process Window Title : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV

  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"

 

Decode alerts and logging will be unavailable until corrected.

 

I have tried changing the UDP port number.

 

I don’t know if there are any other files you might find helpful.

 

My register user info is: AJ4QR@...

Sent from Mail for Windows 10

 


locked Single/double click within callsigns window not working

BOB K5HX
 

I have traced the inability of a single click within the callsign window of JTAlert to activate WSJT-x to ZoneAlarm security software.  If I shutdown ZoneAlarm all works as expected.  However, if I temporarily suspend the firewall within ZoneAlarm,  I still get no communication between WSJT-x and JTAlert which is strange.  Also,  I attempted to configure the firewall to allow inbound and outbound UDP traffic on port 2237 but wasn't sure if that was correct.  In any event it didn't solve the problem.

My JT-Alert info is as follows:

JTAlert Instance       : #1

JTAlert Start Params   : /wsjtx

WSJT-X Window Title    : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV

WSJT-X Command Line    : "C:\WSJT\wsjtx\bin\wsjtx.exe" 

WSJT-X   --rig-name    : 

WSJT-X Config File     : C:\Users\Bob\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Version         : 2.4.0

WSJT-X Revision        : c19d62

WSJT-X Spec Op Mode    : None

WSJT-X UDP ID          : WSJT-X

WSJT-X UDP Port        : 2237

WSJT-X UDP Server      : 239.255.0.1

WSJT-X UDP MCast on LB : True

WSJT-X UDP Max Schema  : 3

 

==================================================

UDP Ports used

--------------------------------------------------

JTAlert.exe           : 62399 60379

JTAlertV2.Manager.exe : 61968 61969 61970

JTAlertV2.Decodes.exe : 

 

 

==================================================

Audio output devices

--------------------------------------------------

[1] Speakers (Dell AC511 USB SoundBar)

[2] DELL U2414H (Intel(R) Display Audio)

[3] Navigator Transmit (2- USB Audio CODEC )

[4] DELL U2417H-4 (NVIDIA High Definition Audio)

 

 

==================================================

JTAlertV2.Manager (2.50.2.0) status

(2021-07-07 23:49:30 utc)

--------------------------------------------------

CLR Version       : 5.0.6

NET Framework     : .NET 5.0.6

Architecture      : x64 64bit

--------------------------------------------------

UDP Router        : Initialized : YES (WSJT-X)

Audio             : Initialized : YES (4 output devices)

Activity Service  : Initialized : YES (started : 58)

Messaging Service : Initialized : YES (started : 17)

HamSpots Service  : Initialized : YES

QRZ Xml           : Initialized : YES (K5HX)

HamQth Xml        : Initialized : YES 

QRZ Log           : Initialized : YES 

HamQth Log        : Initialized : YES 

ClubLog Log       : Initialized : YES 

Eqsl Log          : Initialized : YES 

HrdLog Log        : Initialized : YES 

DXLab DDE         : Initialized : YES

User Alert        : Initialized : YES

Updates Check     : Initialized : YES (started : 3600)

Environment Check : Initialized : YES (started : 3600)

Maintenance       : Initialized : YES (started : 3600)

--------------------------------------------------

Any suggestions are appreciated.

Bob   K5HX
 


locked Re: Failure to Alert On 13 Colonies European Calls

Laurie, VK3AMA
 

For those curious or want to check on the 13 Colonies stations and there last upload date, the Lotw membership activity file can be downloaded from here... https://lotw.arrl.org/lotw-user-activity.csv

de Laurie VK3AMA


locked Re: Failure to Alert On 13 Colonies European Calls

Laurie, VK3AMA
 

On 8/07/2021 1:02 am, Stan Edwards - WA4DYD wrote:
saw TM13COL many times without a single alert showing up.  I'm not familiar with the information passed between the two applications, so cannot speak to any reasoning why the two XX13COL calls do not seem to be crossing over, especially when others have seen success.
TM13COL and GB13COL didn't alert or even display in JTAlert because of your filtering. You have the "LoTW or eQSL"  filter set. Any decoded callsigns that doesn't meet those QSL requirements will not be alerted or displayed.

You need to turn of the Filter if you want alerting on those callsigns.

Callsign QSL usage is recorded in the HamApps Callsign database. Neither TM13COL and GB13COL are in that database because at the time it was created neither station was using LoTW or Eqsl.

I just now (within the last hour) did a callsign database rebuild in preparation for distribution. Both Callsigns are still not listed.

While TM13COL is shown on the Lotw website as having done an upload at 2021-07-06 12:33:59Z, that is not reflected in the latest membership download file provided by Lotw, the file upon which the the database is created. That file list the most recent uploads as
2012-07-04, nothing later.

Until the Lotw membership file is updated with more recent activity there is nothing I can do about the inaccuracies with the JTAlert Callsigns database. I don't know how frequently the LoTW membership file is updated or on what day of the week.

My recommendation... If you're going to chase special events like 13 Colonies turn off the Filtering you have set in JTAlert to avoid stations not displaying/alerting.

de Laurie VK3AMA


locked No decodes form WSJT-X showing in JTALERT-X call sign line

lmeeny
 

Hello,

I recently installed the FLEX SmartSDR suite (DAX) and have lost communication between WSJT-X(2.2.2) and JTALERT-X (2.16.17). No decodes are being passed to JTALERT-X.

When selecting the sound card in JTALERT-X what's the proper source?

73

Ed W2GHD


locked Re: Failure to Alert On 13 Colonies European Calls

Jim N6VH
 


On 7/7/2021 8:02 AM, Stan Edwards - WA4DYD wrote:
Laurie, these are screen shots of the two pages referenced.  Sorry I missed what you were looking for.  I tried both formats of the call I saw in the decoded display on WSJT-X as you will see in the screen shot of wanted calls.  I tried all afternoon yesterday and saw TM13COL many times without a single alert showing up.  I'm not familiar with the information passed between the two applications, so cannot speak to any reasoning why the two XX13COL calls do not seem to be crossing over, especially when others have seen success.  Are their other filters I'm overlooking?  It is puzzling that all the other calls worked and the problem seems confined to these two.  It's the first time I've tried using this feature for the special callsigns.

Thanks again for taking a look.

Regards,
Stan Edwards, WA4DYD
_._,_._,_


Stan,

I see one thing that might be causing the problem. You have "LOTW or eQSL(AG) member" checked. Even though TM13COL has uploaded to LOTW, I don't think the call has made it into the most recent database that Laurie uses. I checked the database "fcc_lotw_eqsl.sqlite" and didn't find the call there.

A new database comes out frequently, so that call might be in the next one. In the meantime, uncheck that filter and see if that helps.

73,

Jim N6VH


locked Re: CAT control Log4OM2 & WSJT-X & mcHF SDR

Michael Lizzio
 

will do Thanks.

On Wed, Jul 7, 2021 at 4:22 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Sounds like a permissions problem.

Try deleting \Users\[username]\fldigi.files

Mike




On Wednesday, July 7, 2021, 11:16:52 AM CDT, Michael Lizzio <ml2772@...> wrote:


Hi Mike,

I've been trying to help David Wilson who lives in Scotland with his Port Audio problem. I met with him via Google meet today to observe the issue he was having. For some reason he is unable to select Port Audio and the File I/O always stays checked. 
  • Tried this with the radio plugged into the USB port
  • Tried with the Radio unplugged from the computer
  • He uninstalled the program and reinstalled and still no luck
Is it possible that the File with his Profile ( Call Sign & other settings) is holding this setting and needs to be deleted too?

On the PC that I have where Fldigi is working, I can toggle between Port Audio and the File I/O all day long with the Radio Plugged in or not.

Just seems like there are a lot of strange things going on with Windows these days and was wondering if you had any ideas on what we can look for to get him going. Also note that I can't get Fldigi to run on my main pc anymore. It won't run at all.

Thanks in advance for your help.


Mike WA2TOP

image.png

On Tue, Jul 6, 2021 at 12:57 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Nothing to do with JTAlert.....

But....change WSJT-X to use OmniRig too.  OmniRig can't use COM3 if WSJT-X is using it.

Mike W9MDB




On Tuesday, July 6, 2021, 07:54:53 AM CDT, PH7R - Ronald <rpmeier.ned@...> wrote:


Not sure if this is the right forum but I fail to have CAT control active in Log4OM2.
Configuration: mcHF SDR into WSJT-X into Log4OM2. In WSJT-X I am using rig Yaesu FT-817 via Com3.

In Log4OM2 activated Omni-rig for FT-817 com3 but still Cat frequency is still Offline. What am I missing?

73 Ronald


locked Re: CAT control Log4OM2 & WSJT-X & mcHF SDR

Michael Black
 

Sounds like a permissions problem.

Try deleting \Users\[username]\fldigi.files

Mike




On Wednesday, July 7, 2021, 11:16:52 AM CDT, Michael Lizzio <ml2772@...> wrote:


Hi Mike,

I've been trying to help David Wilson who lives in Scotland with his Port Audio problem. I met with him via Google meet today to observe the issue he was having. For some reason he is unable to select Port Audio and the File I/O always stays checked. 
  • Tried this with the radio plugged into the USB port
  • Tried with the Radio unplugged from the computer
  • He uninstalled the program and reinstalled and still no luck
Is it possible that the File with his Profile ( Call Sign & other settings) is holding this setting and needs to be deleted too?

On the PC that I have where Fldigi is working, I can toggle between Port Audio and the File I/O all day long with the Radio Plugged in or not.

Just seems like there are a lot of strange things going on with Windows these days and was wondering if you had any ideas on what we can look for to get him going. Also note that I can't get Fldigi to run on my main pc anymore. It won't run at all.

Thanks in advance for your help.


Mike WA2TOP

image.png

On Tue, Jul 6, 2021 at 12:57 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Nothing to do with JTAlert.....

But....change WSJT-X to use OmniRig too.  OmniRig can't use COM3 if WSJT-X is using it.

Mike W9MDB




On Tuesday, July 6, 2021, 07:54:53 AM CDT, PH7R - Ronald <rpmeier.ned@...> wrote:


Not sure if this is the right forum but I fail to have CAT control active in Log4OM2.
Configuration: mcHF SDR into WSJT-X into Log4OM2. In WSJT-X I am using rig Yaesu FT-817 via Com3.

In Log4OM2 activated Omni-rig for FT-817 com3 but still Cat frequency is still Offline. What am I missing?

73 Ronald


locked Re: CAT control Log4OM2 & WSJT-X & mcHF SDR

Michael Lizzio
 

Hi Mike,

I've been trying to help David Wilson who lives in Scotland with his Port Audio problem. I met with him via Google meet today to observe the issue he was having. For some reason he is unable to select Port Audio and the File I/O always stays checked. 
  • Tried this with the radio plugged into the USB port
  • Tried with the Radio unplugged from the computer
  • He uninstalled the program and reinstalled and still no luck
Is it possible that the File with his Profile ( Call Sign & other settings) is holding this setting and needs to be deleted too?

On the PC that I have where Fldigi is working, I can toggle between Port Audio and the File I/O all day long with the Radio Plugged in or not.

Just seems like there are a lot of strange things going on with Windows these days and was wondering if you had any ideas on what we can look for to get him going. Also note that I can't get Fldigi to run on my main pc anymore. It won't run at all.

Thanks in advance for your help.


Mike WA2TOP

image.png

On Tue, Jul 6, 2021 at 12:57 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Nothing to do with JTAlert.....

But....change WSJT-X to use OmniRig too.  OmniRig can't use COM3 if WSJT-X is using it.

Mike W9MDB




On Tuesday, July 6, 2021, 07:54:53 AM CDT, PH7R - Ronald <rpmeier.ned@...> wrote:


Not sure if this is the right forum but I fail to have CAT control active in Log4OM2.
Configuration: mcHF SDR into WSJT-X into Log4OM2. In WSJT-X I am using rig Yaesu FT-817 via Com3.

In Log4OM2 activated Omni-rig for FT-817 com3 but still Cat frequency is still Offline. What am I missing?

73 Ronald


locked Re: Failure to Alert On 13 Colonies European Calls

Stan Edwards - WA4DYD
 

Laurie, these are screen shots of the two pages referenced.  Sorry I missed what you were looking for.  I tried both formats of the call I saw in the decoded display on WSJT-X as you will see in the screen shot of wanted calls.  I tried all afternoon yesterday and saw TM13COL many times without a single alert showing up.  I'm not familiar with the information passed between the two applications, so cannot speak to any reasoning why the two XX13COL calls do not seem to be crossing over, especially when others have seen success.  Are their other filters I'm overlooking?  It is puzzling that all the other calls worked and the problem seems confined to these two.  It's the first time I've tried using this feature for the special callsigns.

Thanks again for taking a look.

Regards,
Stan Edwards, WA4DYD

2761 - 2780 of 38543