|
locked
Re: Which version of JT Alert works now with my HRD v6.7.0.391 Release
No problem here logging with the latest of the 3 programs mentioned either. They run well together.
73, Antony G4CUS
|
|
|
|
locked
Re: Which version of JT Alert works now with my HRD v6.7.0.391 Release
Roger- AC6BW
I too am using the latest versions of HRD, WSJT-X and JTAlert, and I've noticed no problems.
Furthermore, I was a Beta tester for the current version of HRD, and to my knowledge, there were no changes made to the DB format that would affect interoperation with WSJT-X. -- 73, Roger AC6BW
|
|
|
|
locked
JTAlert 2.50.7 extended docking feature
Hello Laurie.
Last night installed and configured JTAlert-2.50.7 with WSJT-X-2.5.0 Both work together O.K. Excellent job! Would be it feasible to have the choice to dock JTAlert at bottom right side of WSJT-X too, please? See attached picture. Best regards -- Tom - SP2L ------------------------------------ It is nice to be important. But it is more important to be nice! Nobody is mistaken - so do I. -- Ta wiadomość została sprawdzona na obecność wirusów przez oprogramowanie antywirusowe Avast. https://www.avast.com/antivirus
|
|
|
|
locked
Re: Config
Michael Black
From JTAlert's FAQ ================== If your preferred logger is not supported, it is best to select the ADIF log, as it will record additional QSO data (Name, QTH, Grid, DXCC, State, ITU zone, CQ zone and QSL request), that can be imported by your logger at a future time. Worked B4 checking will use this log. Important: This IS NOT the adif file produced by WSJT-X (wsjtx_log.adi). If you select the WSJT-X log file, logging will be disabled and a warning message generated. So you can set up the ADIF logging in JTAlert and it will track all your QSOs independently of the logger. You just can't use JTDX's log. Mike W9MDB
On Sunday, October 17, 2021, 07:12:32 AM CDT, Paul F6EXV <f6exv@...> wrote:
Hi Mike Isn't there a way for JTAlert to read the JTDX log ? I just want to have alerts for FT8 new 'things". I have JTDX log to Logger32 (easy) but what about JTAlert talking with JTDX, regardless of log ? Thanks + 73 Paul F6EXV Le 17/10/2021 à 13:20, Michael Black
via groups.io a écrit :
|
|
|
|
locked
Re: What do the symbols mean on the left side of each decoded call within the callsign box
Joe Subich, W4TV
Click Settings -> Select Callsigns
toggle quoted messageShow quoted text
73, ... Joe, W4TV
On 2021-10-17 8:50 AM, Dave Taylor wrote:
Sorry couldnt find a descriptor
|
|
|
|
locked
Re: Which version of JT Alert works now with my HRD v6.7.0.391 Release
Joe, Vince,
I can't say that I have seen anything to support what Joe is saying regarding the actions of developers at HRD re:WSJT-X. JTAlert has continued to function well here for several iterations. On my current Win10 Pro 21H1 box, I am successfully running: HRD current make 6.7.0.391 HRD control and logging work with all 3 radios and the current software version below:. WSJT-X v2.4.0 c19d62 and JTAlertV2.Manager (2.50.7.0) with current config: ========== 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\lusername\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 : 127.0.0.1 WSJT-X UDP MCast on LB : False WSJT-X UDP Max Schema : 3 ================================================== UDP Ports used -------------------------------------------------- JTAlert.exe : 62422 62637 JTAlertV2.Manager.exe : 50092 50093 50094 JTAlertV2.Decodes.exe : 51567 ================================================== Audio output devices -------------------------------------------------- [1] Speakers (High Definition Audio Device) [2] IC-7300 TX Out (USB Audio CODEC ) [3] XENYX Mixer Out (2- USB Audio CODEC ) [4] IC-9700 TX Out (3- USB Audio CODEC ) [5] DELL U2414H (NVIDIA High Definition Audio) [6] IC-705 TX Out (7- USB Audio CODEC ) ================================================== JTAlertV2.Manager (2.50.7.0) status (2021-10-17 13:29:27 utc) -------------------------------------------------- CLR Version : 5.0.11 NET Framework : .NET 5.0.11 Architecture : x64 64bit -------------------------------------------------- UDP Router : Initialized : YES (WSJT-X) Audio : Initialized : YES (6 output devices) Activity Service : Initialized : YES (started : 58) Messaging Service : Initialized : YES (started : 17) HamSpots Service : Initialized : YES QRZ Xml : Initialized : YES (KD4IZ) HamQth Xml : Initialized : YES QRZ Log : Initialized : YES (1515-81FF-7263-25C0) HamQth Log : Initialized : YES (KD4IZ) ClubLog Log : Initialized : YES (KD4IZ) 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) Note that the start up order is important - HRD, WSJT-X, then JTAlert. I hope this helps Vince get his set up working. Jack - KD4IZ
|
|
|
|
locked
What do the symbols mean on the left side of each decoded call within the callsign box
Dave Taylor
Sorry couldnt find a descriptor
Dave n1fcc
|
|
|
|
locked
Re: Config
Paul F6EXV
Hi Mike
toggle quoted messageShow quoted text
Isn't there a way for JTAlert to read the JTDX log ? I just want to have alerts for FT8 new 'things". I have JTDX log to Logger32 (easy) but what about JTAlert talking with JTDX, regardless of log ? Thanks + 73 Paul F6EXV
Le 17/10/2021 à 13:20, Michael Black
via groups.io a écrit :
|
|
|
|
locked
Re: Which version of JT Alert works now with my HRD v6.7.0.391 Release
Barry VA7GEM
On Sat, Oct 16, 2021 at 06:30 PM, Joe Subich, W4TV wrote:
I do know that HRD have changed their database (log) format in theJoe Just to keep the record straight , I use the latest version of Win10 Home, HRD, WSJTX, JTA. I am seeing no issues at all. cheers Barry va7gem
|
|
|
|
locked
Re: Config
Michael Black
Not supported by JTAlert...but is supported by WSJT-X. If you want to use JTAlert alerts you will have to change logging programs. Your other choice would be to generate an ADIF file from logger32 and have JTAlert use that ADIF file but that would be a manual job. Mike W9MDB
On Sunday, October 17, 2021, 01:53:44 AM CDT, Paul F6EXV <f6exv@...> wrote:
Hi all Wanting to use Logger32 + JTDX (version 2.2.0 rc152) and JTAlert (2.50) Because JTAlert cannot log direct to Logger32, where can I find a tutorial on how to configure this setup ? I want JTDX to log to L32, but I also want JTAlert to get the info it requires to get the alarms correct. I fail tyo understand UDP vocabulary, primary and secondary, etc... Thank you + 73 Paul F6EXV
|
|
|
|
Michael Black
Split frequency does not change your TX frequency. Remember that USB is suppressed carrier. The only thing you are transmitting is the FT8 tones and they are always at the same frequency as the waterfall reflects (e.g. 14074000+1500 offset) regardless of the split frequency. The split adjusts the base frequency so that the audio always appears 1500-2000Hz above the suppressed carrier. So...if your offset is 1000-1499 split will adjust 14074000 to 14073500 and the 1000 offset becomes a relative 1500 offset...but still appears to all receivers at 1000 offset. This is not like split mode in CW at all. Mike W9MDB
On Sunday, October 17, 2021, 05:36:03 AM CDT, andrew@... <andrew@...> wrote:
I've been wondering for a while why the WSJT-X log contains only a single frequency. This is interpreted by my logging programs (e.g., DXKeeper, etc...) as TX==RX and recorded accordingly. In general, my FT8 operation is split frequency, so all these log entries are technically wrong/inaccurate. Am I missing something? Is there a flag somewhere? I just spent a few hours searching the group and elsewhere but didn't uncover anything. Thanks for any insights, VE7UM
|
|
|
|
andrew@...
I've been wondering for a while why the WSJT-X log contains only a single frequency. This is interpreted by my logging programs (e.g., DXKeeper, etc...) as TX==RX and recorded accordingly. In general, my FT8 operation is split frequency, so all these log entries are technically wrong/inaccurate. Am I missing something? Is there a flag somewhere? I just spent a few hours searching the group and elsewhere but didn't uncover anything. Thanks for any insights,
VE7UM
|
|
|
|
locked
Config
Paul F6EXV
Hi all
Wanting to use Logger32 + JTDX (version 2.2.0 rc152) and JTAlert (2.50) Because JTAlert cannot log direct to Logger32, where can I find a tutorial on how to configure this setup ? I want JTDX to log to L32, but I also want JTAlert to get the info it requires to get the alarms correct. I fail tyo understand UDP vocabulary, primary and secondary, etc... Thank you + 73 Paul F6EXV
|
|
|
|
locked
2.50.7 sizing problem
As you can see, the screenshot from v2.50.6 is how I've had the Callsign window configured since 2.50 came out at 145%. This is on a 3rd monitor about 5' from my chair and needs larger text to be easily seen. I only show LoTW stations as those are the only ones I'm interested in calling, so my list is typically short. As for some DXPeditions or DXCC stations that don't use LoTW, I'm on the watch for them by other means or "Wanted Call" notifications.
But with 2.50.7, the initial screen shows the Callsign window really small at the same 145%, which I find impossible to read at the 5' distance. Finally, with the Callsign window like I need it for 5' away and it's now at 300%. My monitors are set at 1280 x 1024, which is their max. And if I go to the Colors setup menu and others, they extend way off the bottom of the monitor and don't scroll. I have to resize everything to make any changes on some menu screens. Is this normal? Seems like the menu dialog boxes should remain a constant size. And I've also noticed that the Callsigns are updated at about half the speed of previous 2.50 releases. In the meantime, I've rolled back to v2.50.6 as that's a format that works best for me. -- 73's George - WB5JJJ Hamshack Holine #4969
|
|
|
|
locked
Re: Which version of JT Alert works now with my HRD v6.7.0.391 Release
Joe Subich, W4TV
Could you tell me which version to go to that will continue workingThe developers of HRD have been systematically burning interoperation with WSJT-X. In addition, Laurie can no longer test with HRD so it is not possible to answer your question. Either the current version of WSJT-X works with the current version or it does not - if it does not, there is no way for Laurie to "fix" the interopertion as HRD are actively blocking and seeking to replace WSJT-X. I do know that HRD have changed their database (log) format in the current version which makes it highly likely that any function in WSJT-X that requires access to your log will not work. 73, ... Joe, W4TV On 2021-10-16 3:52 PM, Vince Loschiavo wrote: Hi Laurie,
|
|
|
|
locked
Re: JTAlert not communicating with WSJT-X
Joe Subich, W4TV
What logging program and/or other WSJT-X add-on are you running?
toggle quoted messageShow quoted text
Switch to Multicast UDP as documented in JTAlert -> Help -> WSJT-X UDP Settings. 73, ... Joe, W4TV
On 2021-10-16 8:15 PM, Ed Crosby - W7UJ wrote:
Here are my settings:
|
|
|
|
locked
Re: JT Alert quit working after Windows 10 Update
Joe Subich, W4TV
What logging program and/or other WSJT-X add-on are you running?
toggle quoted messageShow quoted text
Switch to Multicast UDP as documented in JTAlert -> Help -> WSJT-X UDP Settings. 73, ... Joe, W4TV
On 2021-10-16 8:37 PM, Tommy Evans wrote:
Attached are screen shots of the settings in WSJT and JTAlert.
|
|
|
|
locked
Re: JT Alert quit working after Windows 10 Update
Tommy Evans
Attached are screen shots of the settings in WSJT and JTAlert.
|
|
|
|
locked
JTAlert not communicating with WSJT-X
Ed Crosby - W7UJ
Here are my settings:
JTAlert Instance : #1
JTAlert Start Params : /wsjtx
WSJT-X Window Title : WSJT-X v2.1.2 by K1JT
WSJT-X Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"
WSJT-X --rig-name :
WSJT-X Config File : C:\Users\w7uj\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 : 127.0.0.1
WSJT-X UDP MCast on LB : True
WSJT-X UDP Max Schema :
==================================================
UDP Ports used
--------------------------------------------------
JTAlert.exe : 60922 50236
JTAlertV2.Manager.exe : 56044 56045 56046
JTAlertV2.Decodes.exe :
==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (SoundMAX Integrated Digital High Definition Audio)
==================================================
JTAlertV2.Manager (2.50.7.0) status
(2021-10-17 00:10:11 utc)
--------------------------------------------------
CLR Version : 5.0.6
NET Framework : .NET 5.0.6
Architecture : x64 64bit
--------------------------------------------------
UDP Router : Initialized : YES (WSJT-X)
Audio : Initialized : YES (1 output devices)
Activity Service : Initialized : YES (started : 58)
Messaging Service : Initialized : YES (started : 17)
HamSpots Service : Initialized : YES
QRZ Xml : Initialized : YES
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)
--------------------------------------------------
It was working great for about a year and then nothing. Any ideas?
|
|
|
|
locked
Re: JT Alert quit working after Windows 10 Update
Laurie, VK3AMA
On 17/10/2021 9:39 am, Tommy Evans wrote:
Program loads but is not communicating with WSJT. All the settings look correct. Has anyone else had this issue ?The first thing to look at if there is failed comms with WSJTX is the UDP Server settings in WSJTX. Use the JTAlert "Help -> WSJT-X UDP Setup" menu to bring up the help file and check that you have WSJTX & JTAlert setup correctly. Since the Callsigns window is opening that excludes an incorrect .NET Desktop Runtime install as the culprit so you can ignore trouble-shooting advice. de Laurie VK3AMA
|
|
|