Date   

locked Re: Wide Graph RED waterfall

Michael Black
 

Given that you don't even show 0dB on the dB graph on the left would indicate you have either the wrong audio device selected or the audio level between the rig and computer is wrong.

Audio device on the computer should be at 0dB (right click the level slider in the recording sound device to set dB) and adjust the rig's audio playback to get 30dB on a quiet spot.

Also need to check the mixer to ensure WSJT-X's level in there is correct too.

Plus there's the microphone privacy stuff to check.

de Mike W9MDB




On Wednesday, January 8, 2020, 07:49:58 PM CST, J F via Groups.Io <kk4hmq@...> wrote:


I searched the group and found this discussed in 2015 however the person that figured it out himself did not sign his name with call and their is no email.  So I am now posting this in the hopes someone can help me.  Below I will attach a screen shot of what I have going on.  It happened once before as you can see by the date. However I don't remember how I managed to solve it.  Radio is Icom 7200, Ham Radio Deluxe v.6.60.237, WSJT-X v2.1.2, JTAlert v2.15.6
  
 All I can remember is that it was something so simple.  Now I feel stupid for not having written down what seemed so simple at the time. 


locked Wide Graph RED waterfall

J F
 

I searched the group and found this discussed in 2015 however the person that figured it out himself did not sign his name with call and their is no email.  So I am now posting this in the hopes someone can help me.  Below I will attach a screen shot of what I have going on.  It happened once before as you can see by the date. However I don't remember how I managed to solve it.  Radio is Icom 7200, Ham Radio Deluxe v.6.60.237, WSJT-X v2.1.2, JTAlert v2.15.6
  
 All I can remember is that it was something so simple.  Now I feel stupid for not having written down what seemed so simple at the time. 


locked Re: No alert on North Macedonia

HamApps Support (VK3AMA)
 

On 8/01/2020 3:25 am, marsip@... wrote:
This should generate alerts on every callsign, but it doesn't.

See screen dump below.

The new settings are from 161245, and there are two callsigns wich doesn't have an alert.
It's seems random which callsigns are marked with alert or not.
In this case also no alerts were shown on JTAlert.


There is nothing wrong as best I can tell. JTAlert is correctly alerting based on your settings.

The Callsigns that are not being colored with the DXCC alert are likely not passing the Alert Filters you have set. In an earlier message you show that you had the "Lotw or Eqsl" filter set.

LZ2EC doesn't use either qsl service so wont generate an alert and subsequently does not get coloured.

IZ1ANK does use both qsl services and is not being coloured, very likely because you have the "Do not show B4 Callsigns" set and (this is a guess) you have worked him before and would not generate the DXCC alert.

I don't see any Z3 callsigns in your image so my guess is that you don't have "North Macedonia" set as needed.

de Laurie VK3AMA
 


locked Re: Unable to communicate with JTDX process #FT8

HamApps Support (VK3AMA)
 

On 8/01/2020 9:42 am, Bob Davet wrote:
I'm getting the above error. This is for my dad's set up. Mine has been up and running for a couple years now.

Got JTDX loaded and setup using the same settings as on my computer.
Got JTAlert loaded and setup using the same setting as on my computer.

When I load both programs this comes up right in the beginning:

"Unable to communicate with the JTDX process.
UDP Port: 2237
IP address: 127.0.0.1
Values read from JTDX config file...
C:\Users\My dads name\AppData\Local\JTDX\JTDX.ini

JTDX Detected Instance...
Process Window Title: JTDX by HF community  v2.1.0-rc145, derivative work
based on WSJT-X by K1JT
Process Command Line c:\JTDX\JTDX\bin\jtdx.exe

Decode alerts and logging will be unavailable until corrected."

I did not have this problem setting my system up way back when I did it.
I'm sure it is some simple setting, but have no idea where to start looking.

JTDX connects to everything, It receives and transmits like it should.

Is this a JTDX issue or a JTAlert issue, or both?

Just dont know where to start.

Thanks

Bob
W8RID

Check that you have JTDX setup correctly, specifically the UDP Server section on the Reporting tab of the JTDX settings. Make sure that you are not running JTDX with elevated privileges (set to run as Administrator) on the non-working PC. Check both the shortcut used to start JTDX and the jtdx.exe file itself to ensure they are not set to run as administrator.

de Laurie VK3AMA


locked Re: ACLog/JTalert help

HamApps Support (VK3AMA)
 

On 9/01/2020 8:33 am, Ron Ochu wrote:
I am running ACLog 6.4 and JTAlert 2.15.1.  JTalert is posting the call sign, name and QTH of a worked FT8 station on ACLog but nothing else such as report or mode.  There used to be a pop-up window informing me that the contact was logged, but now it doesn't exist.  JTAlert used to completely work, but now it only partially works with ACLog.  I've checked the settings on both programs and they appear to be fine.  Has anyone else experienced a similar issue? 

Thank you for viewing this post.

73,  Ron KO0Z

If JTAlert is not providing a Logging success/failure message and you haven't turned off those confirmation popups, than very likely your not clicking the "OK" button of the WSJT-X "Log QSO" window.  You need to log the QSO in WSJT-X for JTAlert to detect the logging event and send the QSO details to ACLog. The report and Mode will get sent to ACLog only as part of the logging process.

de Laurie VK3AMA


locked ACLog/JTalert help

Ron Ochu
 

Hello to the group,

I am running ACLog 6.4 and JTAlert 2.15.1.  JTalert is posting the call sign, name and QTH of a worked FT8 station on ACLog but nothing else such as report or mode.  There used to be a pop-up window informing me that the contact was logged, but now it doesn't exist.  JTAlert used to completely work, but now it only partially works with ACLog.  I've checked the settings on both programs and they appear to be fine.  Has anyone else experienced a similar issue? 

Thank you for viewing this post.

73,  Ron KO0Z


locked Re: Is Link to DXLab Suite Broken?

Joe Polcari
 

I have the same problem.

JTAlert 2.15.6
DXView 4.6.2
WSJT-X 2.1.2
Win 7 Ultimate 64bit
16GB Memory
Dell XPS L502x w/i7-2630QM@2GHz


locked Re: Is Link to DXLab Suite Broken?

Joe Polcari
 

I fixed it.
I use ZoneAlarm and all I had to do was re-add jtalert.exe to Application control.
Weird that it still didn't work when I paused both AntiVirus and Firewall, but adding it again to Application Control allowed it to talk to DXView again.


locked Re: Unable to communicate with JTDX process #FT8

Bob Davet
 

I believe my dad is using McAffee.


locked Re: Unable to communicate with JTDX process #FT8

neil_zampella
 
Edited

Are you using any specific antivirus or firewall program?   

 

Neil, KN3ILZ


locked Re: Unable to communicate with JTDX process #FT8

Bob Davet
 

Forgot to mention that we both are using HRD for rig control and logging.

Thanks

Bob
W8RID


locked Unable to communicate with JTDX process #FT8

Bob Davet
 

I'm getting the above error. This is for my dad's set up. Mine has been up and running for a couple years now.

Got JTDX loaded and setup using the same settings as on my computer.
Got JTAlert loaded and setup using the same setting as on my computer.

When I load both programs this comes up right in the beginning:

"Unable to communicate with the JTDX process.
UDP Port: 2237
IP address: 127.0.0.1
Values read from JTDX config file...
C:\Users\My dads name\AppData\Local\JTDX\JTDX.ini

JTDX Detected Instance...
Process Window Title: JTDX by HF community  v2.1.0-rc145, derivative work
based on WSJT-X by K1JT
Process Command Line c:\JTDX\JTDX\bin\jtdx.exe

Decode alerts and logging will be unavailable until corrected."

I did not have this problem setting my system up way back when I did it.
I'm sure it is some simple setting, but have no idea where to start looking.

JTDX connects to everything, It receives and transmits like it should.

Is this a JTDX issue or a JTAlert issue, or both?

Just dont know where to start.

Thanks

Bob
W8RID


locked Re: jtalertsetting missing

Michael Black
 

What antivirus are you using?
Can you create an exception for that folder?  If McAffee it own't let you exempt a folder...you have to do it file-by-file.

de Mike W9MDB




On Tuesday, January 7, 2020, 04:19:40 PM CST, CW Carpenter <nmchas39@...> wrote:


I have been using JTalert for quite a long time. Recently, within the past week, I have had to delete JTalert and reload both from the web site and the loading files on hand. JTAlert works fine after reloading. BUT if I quit the program, WSJT-x and JTAlert, JTAlert will not start start when I restart WSJT-X. I get an error message saying that the file "JTAlertsettings" is missing from the download package Plugin  section.
I have not added nor removed any programs in the past month. And this also happens on my laptop if I use it.
Any one have any idea as to what is going on. Why does the file"JTAlertsettings go missing after I sign off.

73, Charlie K4SHA


locked jtalertsetting missing

CW Carpenter <NMCHAS39@...>
 

I have been using JTalert for quite a long time. Recently, within the past week, I have had to delete JTalert and reload both from the web site and the loading files on hand. JTAlert works fine after reloading. BUT if I quit the program, WSJT-x and JTAlert, JTAlert will not start start when I restart WSJT-X. I get an error message saying that the file "JTAlertsettings" is missing from the download package Plugin  section.
I have not added nor removed any programs in the past month. And this also happens on my laptop if I use it.
Any one have any idea as to what is going on. Why does the file"JTAlertsettings go missing after I sign off.

73, Charlie K4SHA


locked Re: No alert on North Macedonia

marsip@...
 

Se my previous posts.
I thought the mode change (to "Any mode") had solved my problem. But has not.
In order to learn more about this, I set the Alerts settings for DXCC to wanting all prefixes.
This should generate alerts on every callsign, but it doesn't.

See screen dump below.

The new settings are from 161245, and there are two callsigns wich doesn't have an alert.
It's seems random which callsigns are marked with alert or not.
In this case also no alerts were shown on JTAlert.


locked Re: JTAlert QRZ Lookup stopping

Morris WA4MIT
 
Edited

To update this issue: Using JTAlert 15.6 now. It did not occur over the weekend but is now happening again this AM when occurs the program does not start up with the latest program update info showing. The calls it will not lookup are in QRZ I can hit the lookup button
and QRZ page comes up with callsign info it is just not doing this when inserting callsign from a double click in JTDX. If the callsign in question is in my log the data shows up. I can only remedy this by doing a computer restart. 

73 Morris WA4MIT


locked Re: JTAlert QRZ Lookup stopping

Antony
 

Anyone got a way around this problem? (Using the latest release of JTAlert).


locked Re: Icom 7300/wsjt/JTalert/AClog

Scott Davis
 

Hi Laurie,

I wrote you direct on December 12th with some thoughts on QSO verification.  It's nothing urgent and there is no need to reply.  I just wanted to make sure you received the e-mail.

73, Scott
N3FJP
 
Serving the Amateur Radio community with contesting and general logging software since 1997.
 
1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


locked Re: No alert on North Macedonia

marsip@...
 

I changed the mode in "Alerts/Wanted DXCC/Any Band" from "Any Digital Mode" to "Any mode". Now I get alerts for Z3, with FT8.

Is it wrong to set "Any Digital Mode" for FT8 with WSJT-X?

/Markku


locked No alert on North Macedonia

marsip@...
 

I'm hunting DXCC, and need North Macedonia.
I have North Macedonia Z3, confirmed on eQSL, but not on LoTW.
I have done a log scan with only LoTW enabled.
In Alerts, Wanted DXCC, Any band, North Macedonia is in the wanted list, which is ok.

Filters:


But Z3 stations doesn't generate alerts. They are marked green (already confirmed).

Markku/SM5FLM