Date   

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


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

WU9D <mike@...>
 

Check QSO Log Record. I checked JTDX and there isn't a timer setting. Everything used to work at 5 seconds until the recent problems. It is definitely a JTAlert window, not WSJT-X or JTDX, and labelled such.


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

JTAlert Support (VK3AMA)
 

On 12/06/2021 7:00 am, WU9D wrote:

For some reason I cannot get the logging prompt to display for 5 seconds. It now is displaying for 10. 5.0.6 again?

 

Mike WU9D


JTAlert doesn't have a logging prompt window. Are you referring to the WSJT-X "Log QSO" window? If so, it doesn't have a display time limit, it stays open until the "OK" button is clicked.

de Laurie VK3AMA


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

WU9D <mike@...>
 

For some reason I cannot get the logging prompt to display for 5 seconds. It now is displaying for 10. 5.0.6 again?

 

Mike WU9D


locked Re: Help Requested installing JTAlert 2.16.17

Laurie, VK3AMA
 

On 12/06/2021 5:23 am, Jim wrote:
I had to remove .net5 before reinstalling 4.7.2
Something is not right your end.

NET 5 runtime and NET 4.7.2 framework are two totally different products, despite the Microsoft confusing naming and version numbering.
They can both be installed concurrently and will need to be for JTAlert.

Shame you don't have a screen-grab of the error message that leads you to think one has to be uninstalled before installing the other.

de Laurie VK3AMA


locked Re: Help Requested installing JTAlert 2.16.17

Jim
 

Laurie   yes I did and that was the start of all of this.  It hung while trying to run .net5  and then when I tried to go back it would not let me and kept giving me an error message which seemed to indicate I had to remove .net5 before reinstalling 4.7.2 ... UGH  its been a long journey unfortunately.   I am not sure I am going to be able to get it working at this point and I really dont like windows 8 or 10 so I dont want to reformat and reload either of them. 
I appreciate any help you may be able to give me. 

Jim


locked Re: Help Requested installing JTAlert 2.16.17

JTAlert Support (VK3AMA)
 

On 12/06/2021 4:26 am, Jim wrote:
I am running Windows 7 and obviously the newest JTAlert does not install because I need .net 5 which will not install on windows 7.

Did you actually try installing the NET 5 desktop runtime? While officially win7 is not supported, many Win7 users have reported that installing it and running JTAlert 2.50.x works fine.
Just be aware of the current problems with version 5.0.7 of the runtime and JTAlert audio. Install the 5.0.6 version. See https://hamapps.groups.io/g/Support/message/35446

de Laurie VK3AMA


locked Help Requested installing JTAlert 2.16.17

Jim
 

I am running Windows 7 and obviously the newest JTAlert does not install because I need .net 5 which will not install on windows 7.
So I went back to JTAlert 2.16.17 which gives me a popup saying this version requires .net 4.7.2 and to visit HamApps.com for the required setup file. Unfortunately this file is no where to be found (maybe my eyes are deceiving me I am old)  I have downloaded the .net 4.7.2 in both the version that is stand alone and the web version and attempted to install them and both get part way through and then start trying to reload the file as if there is a problem with the data. What did I do wrong ... or is there actually a problem with the file.  Hopefully someone will have a good .net4.7.2  so that I can operate some of the VHF contest tomorrow.  

Jim K3YBN


locked Re: Net 5.0.7 question

JTAlert Support (VK3AMA)
 

On 11/06/2021 10:36 pm, Jim Spears wrote:
does this problem affect only users who are using JTalert audio alerts or all JTalert users?

in other words, if I have no audio alerts of any kind enabled, will I be affected by the Microsoft update?

Jim/N1NK

The defect is only triggered when an Alert sound is played.
If you don't have any audio alerts enabled or if the JTAlert Sound menu is set to OFF the defect is not triggered so there is no need to downgrade from NET 5.0.7

de Laurie VK3AMA

4521 - 4540 of 39823