Sorry, clicked on the wrong 3D2 station.

Here's what happens with 3D2USU.

_._,_._,_

---

• Not having a logger enabled in JTAlert.
  
• JTAlert is looking at the wrong or empty log file.
• Protection software interference preventing JTAlert from reading the log file.
• In your example there are no FT8 QSOs with 3D2USU in your log.

What logger do you have enabled in JTAlert

Assuming you are using a log with JTAlert, are there any 3D2USU QSOs in that log recorded? If there are, for what mode?

de Laurie VK3AMA

Thanks, Laurie. Keeping fingers crossed :D

Paul, sq5nry

Worked B4 Operating Incorrectly In JTAlert

Hi All,
I've recently rediscovered the hobby and have just set up WSJT-X and JTAlert over the last couple of days. I'm currently only using QRZ.com for a log.
Everything seems to be working as it should, except for one aspect of JTAlert's worked B4 functionality.
I have worked 3D2USU once on two different bands. I'm getting grey a background on worked before stations in both WSJT-X and JTAlert, however when I right click on the worked B4 station in JTAlert and click on "Show QSO's History Popup", the popup states that it's not a worked B4 station.
It's all very odd since JTAlert does know that stations are worked before, but the "Show QSO's History Popup" alone doesn't seem to know about the worked B4 station.
Any ideas on how I can rectify the situation?
Thank you.
73 Mark
Worked B4 Operating Correctly In WSJT-X
Worked B4 Operating Correctly In JTAlert
Worked B4 Operating Incorrectly In JTAlert

As you said "If the original decode associated with a JTAlert callsign is no longer shown in JTDX than the callsign click event is ignored by JTDX."

I wanted to have two WSJTXs + one JTDX instance running each with its JTAlert. I can get WSJTXs+JTAlerts alone working but then trying to start JTAlert for JTDX fails, as if it's not identifying the JTDX. And vice versa, JTAlert+JTDX started first work okay but then adding WSJTx is not successful. Is there a way to get such a set working well?

Best regards, Paul, sq5nry

JTAlert seg faults with his Chrome browser when clicking the Q button.

I don't see any information in the debug logs that helps.

Changing his default browser to Edge fixes it....back to Chrome still seg faults.

Did the same on my system and Chrome (same version as his) works OK.

Can we maybe get some debug to find out what's going on?

Mike W9MDB

Hello, I'd like to suggest a feature request. I'm using one WSJTX+JTAlert for SAT work and I found I cannot easily define Wanted DXCC. Highest built-in band is 2m however WSJTX is duly configured to report real RX band, in this case 3cm. Reconfiguring WSJTX to report in 2m band would perhaps solve the problem but I wouldn't like to resign from proper freq reporting.

Best regards, Paul, sq5nry

I'm having difficulty trying to setup alerts for wanted grid squares. Any advice>

Herb KM6JBI

What is not working for you?

Setting up which grids are wanted requires that the "Settings -> Rebuild Alert Database" menu is executed. There is not option to manually set/unset needed grids.



de Laurie VK3AMA
 

Any advice

I'm having difficulty trying to setup alerts for wanted grid squares. Any advice>
Herb KM6JBI

I recently updated from a rather old version (2.2) on my Windows 10 PC. That version worked fine.
As required for neatest version, I set up Net 5 during installation process. Now Alerts work, but I cannot query QRZ XML. It is set up correctly under web services. Further when I click “Q” JTAlert shuts down. I also cannot bring up Support function under help. It will not connect.
Thanks in advance
Eli N6PF 

Hello, I'd like to suggest a feature request. I'm using one WSJTX+JTAlert for SAT work and I found I cannot easily define Wanted DXCC. Highest built-in band is 2m however WSJTX is duly configured to report real RX band, in this case 3cm. Reconfiguring WSJTX to report in 2m band would perhaps solve the problem but I wouldn't like to resign from proper freq reporting.

Best regards, Paul, sq5nry