Date   

locked Re: Decode Window not showing all GRID squares. Need to fix this soonest.

John
 

I've noticed this too, but if you mouse over the alert, the op has not entered their grid square, I just look them up on QRZ, but sometimes the grid square isn't there either.

John
VE7KKQ


On Sat, Jun 12, 2021 at 10:49 AM Mark W2OR via groups.io <reston2010mm-orders=yahoo.com@groups.io> wrote:
The decodes window is showing grids for most stations, likewise Miles and SP Short Path info, yes, but for several call signs in the decodes window  that same info is missing.  Yes, the call sign data bases for JTA have been updated today. 

I've apparently missed something obvious. 

// mark 


locked Decode Window not showing all GRID squares. Need to fix this soonest.

Mark W2OR
 

The decodes window is showing grids for most stations, likewise Miles and SP Short Path info, yes, but for several call signs in the decodes window  that same info is missing.  Yes, the call sign data bases for JTA have been updated today. 

I've apparently missed something obvious. 

// mark 


locked Re: WSJT-X 2.5.0-rc1 / JTAlert 2.50.1 blank display #FT8

g4wjs
 

On 12/06/2021 17:14, ag5pc@outlook.com wrote:
I just upgraded both WSJT-X and JTAlert to the latest versions. WSJT-X works fine but JTAlert is blank. See attached screen shot. I get the UDP error message and I've been through the UDP setup in the help file to no avail. Per instructions, here is the status:

JTAlert Instance       : #1
JTAlert Start Params   : /wsjtx
WSJT-X Window Title    : WSJT-X   v2.5.0-rc1   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\Al\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  :
OM,

I am not sure if it matters, but you have checked the "Multicast on Loopback interface" option but you are not serving on a multicast address.

Also check no other application is serving on port 2237 on your PC.

Another possibility is that either JTAlert or WSJT-X is running with Administrator rights, neither should be.

Make sure there is no rule in your firewall that might block port 2237 or either of the applications.



--
73
Bill
G4WJS.


locked WSJT-X 2.5.0-rc1 / JTAlert 2.50.1 blank display #FT8

ag5pc@...
 

I just upgraded both WSJT-X and JTAlert to the latest versions. WSJT-X works fine but JTAlert is blank. See attached screen shot. I get the UDP error message and I've been through the UDP setup in the help file to no avail. Per instructions, here is the status:

JTAlert Instance       : #1
JTAlert Start Params   : /wsjtx
WSJT-X Window Title    : WSJT-X   v2.5.0-rc1   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\Al\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           : 60764 53991
JTAlertV2.Manager.exe : 61646 61647 61648
JTAlertV2.Decodes.exe : 
 
 
==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (Realtek High Definition Audio)
[2] DAX RESERVED IQ RX 1 (FlexRadio Systems DAX IQ)
[3] DAX RESERVED AUDIO RX 2 (FlexRadio Systems DAX Audio)
[4] DAX RESERVED MIC AUDIO (FlexRadio Systems DAX MIC Audio)
[5] DAX RESERVED IQ RX 4 (FlexRadio Systems DAX IQ)
[6] DAX RESERVED AUDIO RX 1 (FlexRadio Systems DAX Audio)
[7] DAX RESERVED IQ RX 2 (FlexRadio Systems DAX IQ)
[8] DAX RESERVED AUDIO RX 8 (FlexRadio Systems DAX Audio)
[9] DAX RESERVED AUDIO RX 6 (FlexRadio Systems DAX Audio)
[10] DAX RESERVED IQ RX 3 (FlexRadio Systems DAX IQ)
[11] DAX Audio TX (FlexRadio Systems DAX TX)
[12] DAX RESERVED AUDIO RX 3 (FlexRadio Systems DAX Audio)
[13] DAX RESERVED AUDIO RX 4 (FlexRadio Systems DAX Audio)
[14] DAX RESERVED AUDIO RX 7 (FlexRadio Systems DAX Audio)
[15] DAX RESERVED AUDIO RX 5 (FlexRadio Systems DAX Audio)
 
 
==================================================
JTAlertV2.Manager (2.50.1.0) status
(2021-06-12 15:52:23 utc)
--------------------------------------------------
CLR Version      : 5.0.7
NET Framework    : .NET 5.0.7
Architecture     : x64 64bit
--------------------------------------------------
UDP Router       : Initialized : YES (WSJT-X)
Audio            : Initialized : YES (15 output devices)
BandData         : Initialized : YES (started : 58)
Text Msgs        : Initialized : YES (started : 17)
HamSpots         : Initialized : YES
QRZ Xml          : Initialized : YES (AG5PC)
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      : Initialized : YES (started : 3600)
Maintenance      : Initialized : YES (started : 3600)
--------------------------------------------------
 


locked Re: JTAlert 2.50.1 NO SOUND

Craig
 

Thanks Ron for taking the time to suggest a few things.... Finally have things working now.  There was a separate 5.0.7 runtime program that was out of add / remove .NET sequence that I was missing.  Once I found that program and removed it, 5.0.6 loaded correctly, and all is working fine again.  What a pain... just love MS when things like this occur!  Thanks again.  73, Craig


locked Re: JTAlert 2.50.1 NO SOUND

Ron W3RJW
 

Craig (call?).

A few places to look:

First  check "Speakers" in System Tray ( the lower right toolbar) .....  ))) good or x bad (off)   click to reset

Often Windoz 10 turns off audio devices.

Right Click on 'Start'
Choose 'Settings'
Sound
Sound Control Panel(Right side in blue)
Playback Tab
Select your output device CODEC etc.for radio
Properties
Levels

Look for Red X. .... if Red X click to restore audio.


If all OK, then you will have to look elsewhere.

--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.4.0, JTAlert 2.50.1 beta, HRD Deluxe v6.7.0.357
FTdx-3000, SignaLink USB


locked Re: JTAlert 2.50.1 NO SOUND

Craig
 

Have uninstalled and rolled back to 5.0.6 (64) without success.  Still have no JTAlert audio... just popping sounds.  C


locked Re: Logging prompt set at 5 seconds, up for 10 seconds

Jim Cooper
 

On 12 Jun 2021 at 12:16, WU9D wrote:

And your next unnecessary observation is?
seems like such sarcasm is not called for here.


locked Re: Logging process Log4OM v2 - Wsjt-x and JTAlert after Windows 10 update july 2021

Gerrit
 

Hello Mike,

 

Thanks for your quick reply.

I made the setup i.a.w. the (old) JTAlert help file.

Have little knowledge about broadcasts, rebroadcasts and UDP ports etc.

So i am always dependent on examples and help files.

 

The problem is solved, the problem was indeed the 2237 port.

 

Changed it into 2235 and all logging again.

Strange, i did not made any changes into the settings before the MS update !

I will change the secondary and rebroadcast settings as you advised.

 

Again many thanks for your helping hand Mike.

 

Please stay safe and see you on the bands.

 

73’s

Gerrit – PA3DJY

 

 

 

 

 

Van: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] Namens Michael Black via groups.io
Verzonden: zaterdag 12 juni 2021 14:01
Aan: Support@HamApps.groups.io
Onderwerp: Re: [HamApps] Logging process Log4OM v2 - Wsjt-x and JTAlert after Windows 10 update july 2021

 

You've got the JTAlert Log4OM port as 2237 -- it should be 2235 as that is port you have set up in Log4OM.

 

Why do you have the secondary broadcast turn on in WSJT-X?

 

Why do you have another JTAlert rebroadcast port in Log4OM?

 

Neither of those are necesary.

 

Mike W9MDB

 

 

 

 

 

On Saturday, June 12, 2021, 06:56:04 AM CDT, Gerrit via groups.io <hf-sparks@...> wrote:

 

 

Dear reader(s),

 

I installed a major Microsoft update today and since then i have a problem with logging. I am still using the JTAlert 2.16.13 version together with Wsjt-x 2.2.2 en Log4OM 2.14.1.0. The logging was done from Wsjtx to JTAlert and Log4OM, all worked flawlessly. After the Windows update i received a JTAlert Error that Log4OM was unable to confirm QSO logged. The QSO was also not logged in Log4OM. So i guess that there is something wrong with the channel between JTAlert and Log4OM (settings).

I made screenshot of JTAlert, Log4OMV2 and Wsjtx settings if you need any. Any idea what happened?

 

Best regards,

Gerrit PA3DJY

 


locked Re: Logging prompt set at 5 seconds, up for 10 seconds

WU9D <mike@...>
 

And your next unnecessary observation is?

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of neil_zampella via groups.io
Sent: Friday, June 11, 2021 11:54 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Logging prompt set at 5 seconds, up for 10 seconds

 

That's not a "Logging Prompt" .. that's JTAlert saying it checked the logger you're using and it verifed that the QSO was successfully logged.

Neil, KN3ILZ


locked Re: Logging process Log4OM v2 - Wsjt-x and JTAlert after Windows 10 update july 2021

Michael Black
 

You've got the JTAlert Log4OM port as 2237 -- it should be 2235 as that is port you have set up in Log4OM.

Why do you have the secondary broadcast turn on in WSJT-X?

Why do you have another JTAlert rebroadcast port in Log4OM?

Neither of those are necesary.

Mike W9MDB





On Saturday, June 12, 2021, 06:56:04 AM CDT, Gerrit via groups.io <hf-sparks@...> wrote:


Dear reader(s),

 

I installed a major Microsoft update today and since then i have a problem with logging. I am still using the JTAlert 2.16.13 version together with Wsjt-x 2.2.2 en Log4OM 2.14.1.0. The logging was done from Wsjtx to JTAlert and Log4OM, all worked flawlessly. After the Windows update i received a JTAlert Error that Log4OM was unable to confirm QSO logged. The QSO was also not logged in Log4OM. So i guess that there is something wrong with the channel between JTAlert and Log4OM (settings).

I made screenshot of JTAlert, Log4OMV2 and Wsjtx settings if you need any. Any idea what happened?

 

Best regards,

Gerrit PA3DJY

 


locked Logging process Log4OM v2 - Wsjt-x and JTAlert after Windows 10 update july 2021

Gerrit
 

Dear reader(s),

 

I installed a major Microsoft update today and since then i have a problem with logging. I am still using the JTAlert 2.16.13 version together with Wsjt-x 2.2.2 en Log4OM 2.14.1.0. The logging was done from Wsjtx to JTAlert and Log4OM, all worked flawlessly. After the Windows update i received a JTAlert Error that Log4OM was unable to confirm QSO logged. The QSO was also not logged in Log4OM. So i guess that there is something wrong with the channel between JTAlert and Log4OM (settings).

I made screenshot of JTAlert, Log4OMV2 and Wsjtx settings if you need any. Any idea what happened?

 

Best regards,

Gerrit PA3DJY

 


locked Re: question [Request regarding the database registration]

Dave Garber
 

if they are all going to be /xxx60, why not just not use the 60 at the end, and have qrz updated for each call using the suffix.   also will they be including suffix in eqsl or lotw, or just there basic call


Dave Garber
VE3WEJ / VE3IE


On Fri, Jun 11, 2021 at 11:31 PM JP1LRT <jp1lrt@...> wrote:
Hello everyone. Thanks to the development team for your help.
 
This time I would like to make a request regarding the database registration.
As I'm sure many of you already know, the amateur radio station in Okinawa Prefecture, the westernmost prefecture in Japan, is operating with its own callsign followed by, for example, /OKA60 as part of the 60th anniversary of amateur radio in 2021.
 
In FT8, when using a non-standard callsign, only 13 characters can be sent due to the character limit. For example, if I, JP1LRT, try to call CQ as JP1LRT/OKA60, the message will be [CQ JP1LRT/OKA6]. In fact, there are many stations that operate in this way. In the JT Alert database, OKA/60 is correctly recognized as "Japan", but /OKA6 is recognized as Czechoslovakia.
 
/OKA60 /DNA60 /IEJ60 /ISG60 /MMY60 /SHI60 /KJP60 /AGJ60 /MMD60 /KTD60 /UEO60 /TRA60 /OGN60 /HTR60, those without the last character "0", could  you please register them as "Japan" in the database only during 2021?

Best Regards

Yoshiharu Tsukuura JP1LRT
https://www.qrz.com/db/JP1LRT


locked Re: Logging prompt set at 5 seconds, up for 10 seconds

neil_zampella
 

That's not a "Logging Prompt" .. that's JTAlert saying it checked the logger you're using and it verifed that the QSO was successfully logged.

Neil, KN3ILZ


locked question [Request regarding the database registration]

Yoshi - JP1LRT
 

Hello everyone. Thanks to the development team for your help.
 
This time I would like to make a request regarding the database registration.
As I'm sure many of you already know, the amateur radio station in Okinawa Prefecture, the westernmost prefecture in Japan, is operating with its own callsign followed by, for example, /OKA60 as part of the 60th anniversary of amateur radio in 2021.
 
In FT8, when using a non-standard callsign, only 13 characters can be sent due to the character limit. For example, if I, JP1LRT, try to call CQ as JP1LRT/OKA60, the message will be [CQ JP1LRT/OKA6]. In fact, there are many stations that operate in this way. In the JT Alert database, OKA/60 is correctly recognized as "Japan", but /OKA6 is recognized as Czechoslovakia.
 
/OKA60 /DNA60 /IEJ60 /ISG60 /MMY60 /SHI60 /KJP60 /AGJ60 /MMD60 /KTD60 /UEO60 /TRA60 /OGN60 /HTR60, those without the last character "0", could  you please register them as "Japan" in the database only during 2021?

Best Regards

Yoshiharu Tsukuura JP1LRT
https://www.qrz.com/db/JP1LRT


locked Re: JTAlert/WSJT-X problems #FT8

Chris Levingston
 

Hi, Laurie, and thanks.

BTW, UDP settings are clicked in WSJT-X, in case you may think that as the problem.

It works in v2.16.4 but not in 2.50.0.
Clicking on the View menu brings it up but clicking on the stars for F3, F5, F11 and F12 does not work, nor does pressing the function keys.
The others work.

I have removed Desktop Runtime 5.07 and replaced it with v5.06.

Any and all assistance greatly appreciated.

73s,

Chris    VK5SA


locked Test

Al Bailey (K8SIX)
 

Just a test to see if I am being seen.

 

73 de Al, K8SIX

 


locked Re: Help Requested installing JTAlert 2.16.17

WU9D <mike@...>
 

And maybe it’s bad programming. Software developers need to keep up with updates from Microsoft if they are going to use their platforms. I for one don’t like this Dot Net 5.0.5, 5.0.6, 5.0.7 nonsense but unless you are an ostrich you must move with the leaders.

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Jim via groups.io
Sent: Friday, June 11, 2021 4:51 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Help Requested installing JTAlert 2.16.17

 

Evening Laurie,  Late update. I figured it out... when I could not get .net4.7.2 to run I opened up the log file that contained the errors and also opened a command window a opened the directory referenced in the error log. I found the file referenced (said to delete it) ..... I just ran it from the command line and it installed 4.7.2 perfectly so then I ran JTAlert 2.16.17 and it installed as well. Apparently like many of the windows system files you cant run a second occurrence of the file without either deleting the original or running the original, meaning the file in the operating directory.   I chose to run it and it worked... WHO KNEW   Sometimes I think Windows is  as a friend from down under used to say windows was "WAHOS"  (for those of you that are not AUSSIE... it means  :WHAT A HUNK OF SXXT)

In any event it is working now.. 

Thanks for the help 

Jim  K3YBN


locked Re: Logging prompt set at 5 seconds, up for 10 seconds

WU9D <mike@...>
 



Displays 10 seconds when setting is 5 seconds.


locked Re: Help Requested installing JTAlert 2.16.17

Jim
 

Evening Laurie,  Late update. I figured it out... when I could not get .net4.7.2 to run I opened up the log file that contained the errors and also opened a command window a opened the directory referenced in the error log. I found the file referenced (said to delete it) ..... I just ran it from the command line and it installed 4.7.2 perfectly so then I ran JTAlert 2.16.17 and it installed as well. Apparently like many of the windows system files you cant run a second occurrence of the file without either deleting the original or running the original, meaning the file in the operating directory.   I chose to run it and it worked... WHO KNEW   Sometimes I think Windows is  as a friend from down under used to say windows was "WAHOS"  (for those of you that are not AUSSIE... it means  :WHAT A HUNK OF SXXT)

In any event it is working now.. 

Thanks for the help 

Jim  K3YBN

1681 - 1700 of 36991