Date   

locked Re: Logging Wrong Rcv Freq to DXKeeper

Jim N6VH
 


On 7/12/2021 2:01 PM, Dale Drake wrote:
Okay, so none of the comments so far have helped me solve my problem.  I know that JTAlert creates a 1 QSO ADIF file that includes both the xmt and rcv freq that is read by DXKeeper and it is logged as presented.  So why does JTAlert list my xmt freq as the rcv freq if I'm running split in FT8 in WSJT-X?  If my dial freq is 50.313 and I'm listening on 500Hz audio and transmitting on 2500 Hz audio JTAlert should show my xmt as 50.315.5 and my  rcv as either 50.313 or 50.3135 but it doesn't.
_._,_._,_


Dale,

The xmt & rcv freqs that JTAlert puts in the file are what is sent to JTAlert by WSJT-X. JTALert is not connected to the rig, and has no direct knowledge of the frequencies. JTAlert can only know what is sent to it. For that matter, both the wsjtx.log and the wsjtx_log.adi only list one frequency.

73,

Jim N6VH


locked Re: Logging Wrong Rcv Freq to DXKeeper

HamApps Support (VK3AMA)
 

On 12/07/2021 11:32 pm, Tom Melvin wrote:
I run an old Windows 7 PC and have no issues with latest WSJTX, JTAlert or the .Net components needed.

Tom
GM8MJV
Tnx Tom,

That is the information I have been receiving.

Installs of the NET 5.0.x Desktop Runtime on Win7, both Home and Pro variants, works despite the official Microsoft documentation indicating otherwise. Whether that is the case in the long-term is unknown. I suspect eventually the NET install will fail with some future release given the age of Win7 and that is now long out of official support.

de Laurie VK3AMA


locked Re: Logging Wrong Rcv Freq to DXKeeper

HamApps Support (VK3AMA)
 

On 12/07/2021 11:27 pm, Dale Drake wrote:
I can't upgrade to the latest version because I can't get .NET5 to run on my old Win 7 PC.

Any help resolving this would be appreciated.
--
Dale, AA1QD

Are you getting an error message when you try to install the NET 5.0.x Desktop Runtime? Or is it that JTAlert 2.50.x doesn't work correctly after installing the runtime?

Post an image of the offending error message window. Please not your entire desktop, just the error window.

Typically the causes of 2.50.x troubles is caused by not following the NET install instructions. Installing the NET 5.0.7 Runtime when it should be the NET 5.0.7 Desktop Runtime (note the emphasis on the work "Desktop"). Other cause of problems is trying to mix non-compatible architecture type versions (
x86 and x64) of the software. The JTAlert installer needs to match the NET 5 installer architecture type, either x86 for 32bit windows or x64 for 64bit windows.

de Laurie VK3AMA


locked Re: Logging Wrong Rcv Freq to DXKeeper

Dale Drake
 

Okay, so none of the comments so far have helped me solve my problem.  I know that JTAlert creates a 1 QSO ADIF file that includes both the xmt and rcv freq that is read by DXKeeper and it is logged as presented.  So why does JTAlert list my xmt freq as the rcv freq if I'm running split in FT8 in WSJT-X?  If my dial freq is 50.313 and I'm listening on 500Hz audio and transmitting on 2500 Hz audio JTAlert should show my xmt as 50.315.5 and my  rcv as either 50.313 or 50.3135 but it doesn't.


locked Re: Some worked grids showing as not worked

HamApps Support (VK3AMA)
 

On 13/07/2021 5:15 am, Jim Cary wrote:
Some (not not all) grids shown as worked in the "worked grids box" for a band are showing up as needed on WSJT-X.  Weird.

Any thoughts?

Jim
W2SM

If JTAlert is showing a Grid (or any of the needed entities) as previously worked, a B4, yet WSJT-X does not that indicates that the WSJT-X adi file it uses doesn't contain the same entries as the log file that you have JTAlert set to use to determine the worked B4 status. This tends to happen when a user deletes the WSJT-X adi file. You can do an adif export from your logger and replace the WSJT-X adi file with that export or turn off the B4 coloring in WSJT-X and follow the coloring that JTAlert applies to the WSJT-X decodes.

de Laurie VK3AMA


locked Re: Defect in Swedish Audio file

HamApps Support (VK3AMA)
 

On 12/07/2021 3:07 pm, Björn SM7IUN wrote:
The Swedish audio file uses the word "tillstånd" for state which is amusing but wrong.
"Tillstånd" is the Swedish word for "state" as in "state of mind" or "state machine". 
The Swedish word for state as in "governmental entity" is "stat".

Björn SM7IUN

Tnx Björn.

This type of incorrect pronunciation is caused by how the audio files are automatically generated. Its a 2 step process utilizing some online tools to perform the translations and audio generation.

  1. Translate the English text to the target language.
  2. Generate the target language audio file using the translated text from step 1.

Step 1. is the problem. A single word or a short phrase can be taken out of context when it is not part of a much longer sentence. When used in a sentence it helps infer the correct context, but it becomes difficult to extract the correct translation without human intervention.

I have updated the translation database per your advice. I note in the database that some of the "New ..." translations are "ny ..." and some are "nytt ...". Which is correct "ny" or "nytt"? Let me know and I will also include those for new audio file generation.

I will try an find time to get the audio files recreated and republished to the HamApps website over the next couple of days. Once I do I will send you the changed files for review.

de Laurie VK3AMA


locked #Announcement #NewRelease " JTAlert 2.50.3 is available - New Directed CQ Alert + FFMA Grid changes + fixes #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The latest JTAlert version 2.50.3 is now available @ https://hamapps.com/JTAlert/

Please review the release notes at the end of this message.

de Laurie VK3AMA

Release Notes.

2.50.3 (2021-Jul-12)

  *** Includes Callsign database file version 2021-07-12 (2021-Jul-12)

  New:

    - Wanted Grid Alert: New option to restrict audio alerts to FFMA grids only when
       operating on 6m. The default is for this setting to be off so all 6m alerted
       grids will generate the audio alert.
       See the "Alerts, Wanted Grid" section of the main JTAlert window Settings.

    - Alerts: New "Directed CQ" Alert, with user-settable colors and sound file.
       This Alert will trigger on any directed CQ decode that has a direction
       word set in the settings. eg SOTA, POTA, TEST, FD, VK, etc.
       See the "Alerts, Directed CQ" section of the main JTAlert window Settings.

    - Callsigns Window: New "Alert Directed CQ" View. Callsigns generating a
       "Directed CQ" Alert (see above) will be displayed in this view.
       Note: Non-alerting directed CQs will not appear in this view.

    - Callsigns Window: New "Portable decodes" View. Callsigns operating portable
       signing their callsigns with "/P" or "/R" will be shown in this Display View.

    - Callsigns Window: "CQ decodes" View has options to include Directed CQ and
       RR73 or 73 decodes.


  Changes:

    - WSJT-X / JTDX UDP: JTAlert will no longer show an error window if there has
       been no received UDP messages. Previously an error window would be shown
       after 2 minutes of no UDP messages following JTAlert startup.


  Fixes:

    - Callsigns Window: QSL and Online symbols being reset and changes to symbol
      selection not being remembered. (2.50.2 defect)

    - Marathon Alert: Alerted callsigns not being displayed in the Callsigns window
       "Alert Marathon" display view. (2.50.2 defect)



locked Some worked grids showing as not worked

Jim Cary
 

Hi Laurie,

Some (not not all) grids shown as worked in the "worked grids box" for a band are showing up as needed on WSJT-X.  Weird.

Any thoughts?

Jim
W2SM


locked Re: Logging Wrong Rcv Freq to DXKeeper

Joe Subich, W4TV
 

On 2021-07-12 9:27 AM, Dale Drake wrote:
A few days ago while running WSJT-X 2.1.2 and JTAlert 2.16.17
JTAlert 2.16.17 is badly out of date. The current version is 2.50.2

I can't upgrade to the latest version because I can't get .NET5 to
run on my old Win 7 PC.
.NET 5.0.7 is reported to be running fine on many Win 7 systems.
However, with Windows 7 out of support by Microsoft, you should
be updating to an operating system that is being supported with
current security updates if you are connected to the internet in
any way.

I noticed that when logging FT8 QSO's to DXKeeper my transmit freq
was being logged as both the rcv and xmt freq.
My WSJTX 2.4.0/2.5.0-rc3 and JTAlert 2.50.2 system also logs the
TX and RX frequencies the same. AFAIK, that is the way they are
reported by WSJTX.

73,

... Joe, W4TV


On 2021-07-12 9:27 AM, Dale Drake wrote:
A few days ago while running WSJT-X 2.1.2 and JTAlert 2.16.17 I noticed that when logging FT8 QSO's to DXKeeper my transmit freq was being logged as both the rcv and xmt freq.  I don't think I changed anything to cause this.  I can't find anything in settings that can explain it.  Rebooting the PC didn't help.
I can't upgrade to the latest version because I can't get .NET5 to run on my old Win 7 PC.
Any help resolving this would be appreciated.
--
Dale, AA1QD


locked Re: Logging Wrong Rcv Freq to DXKeeper

Tom Melvin
 

FYI

I run an old Windows 7 PC and have no issues with latest WSJTX, JTAlert or the .Net components needed.

Don’t assume that someone says it will not work that it won’t.  May be other reasons unknown to me but suggest give it a try - you can always roll back the apps.

Tom
GM8MJV
 

On 12 Jul 2021, at 14:27, Dale Drake <daleaa1qd@...> wrote:

A few days ago while running WSJT-X 2.1.2 and JTAlert 2.16.17 I noticed that when logging FT8 QSO's to DXKeeper my transmit freq was being logged as both the rcv and xmt freq.  I don't think I changed anything to cause this.  I can't find anything in settings that can explain it.  Rebooting the PC didn't help.  

I can't upgrade to the latest version because I can't get .NET5 to run on my old Win 7 PC.

Any help resolving this would be appreciated.
--
Dale, AA1QD


locked Logging Wrong Rcv Freq to DXKeeper

Dale Drake
 

A few days ago while running WSJT-X 2.1.2 and JTAlert 2.16.17 I noticed that when logging FT8 QSO's to DXKeeper my transmit freq was being logged as both the rcv and xmt freq.  I don't think I changed anything to cause this.  I can't find anything in settings that can explain it.  Rebooting the PC didn't help.  

I can't upgrade to the latest version because I can't get .NET5 to run on my old Win 7 PC.

Any help resolving this would be appreciated.
--
Dale, AA1QD


locked Re: "Indicators" in call sign boxes

Gordon Brown
 

The symbls can be represent what ever you want them to represent. They are usersettable. Look under th e  "Callsigns" section of the Options popup  of the Callsigns window. CLick the gear icon or press F2.

GB


locked Re: "Indicators" in call sign boxes

Jim Cooper
 

On 11 Jul 2021 at 22:36, Radio K0HB wrote:

Where can I find the definitions of
the triangles and squares in the
corners of the callsign boxes?
F2 is the magic access code for SETTINGS in
any of the windows now.

Callsign window ... F2 ... Callsigns ... Callsign Options

at the bottom, YOU can pick what symbol means what,
and what size you want it to be.


locked "Indicators" in call sign boxes

Radio K0HB
 

Where can I find the definitions of the triangles and squares in the corners of the callsign boxes?
--
73, de Hans, KØHB
"Just a boy and his radio"™


locked Defect in Swedish Audio file

Björn SM7IUN
 

The Swedish audio file uses the word "tillstånd" for state which is amusing but wrong.
"Tillstånd" is the Swedish word for "state" as in "state of mind" or "state machine". 
The Swedish word for state as in "governmental entity" is "stat".

Björn SM7IUN


locked Re: Callsign Options Symbols dropdowns not sticking - DEFECT CONFIRMED

HamApps Support (VK3AMA)
 

On 12/07/2021 8:39 am, Carey, WB4HXE wrote:
Thank you Laurie!

On Sun, Jul 11, 2021 at 3:47 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 11/07/2021 12:51 am, Carey, WB4HXE wrote:

JTAlert 2.50.2. Under the Callsign Options window, Callsigns selection, the dropdowns for Lotw, Eqsl and Online don't seem to be working. I can select from the dropdown but when I release the mouse button, the item turns blank. See attached snip.

--
73, Carey, WB4HXE

Tnx Carey.

I can confirm the defect, and am seeing it here repeatedly. It went unnoticed as I am currently non-active using WSJT-X/JTAlert, haven't been for a couple of years!

Since this is reproducible in my tests, it should be painless, I hope, to identify the cause and produce a fix in time for the next public release.

de Laurie VK3AMA

--
Carey Fisher


--
73, Carey, WB4HXE

I can confirm this is fixed for the new release. That will be this week sometime.

Currently, if you want the symbol changes to stick you need to not close the Callsigns window and then reopen while JTAlert is running. If you leave the Callsigns window open for the duration of your JTAlert session, the symbols are remembered. Its an obscure fault condition that I had a heck of a time finding the circumstances under which it was triggered. It affected only the symbols and none of the many other options stored in the Callsigns window config file which made it a more confusing debug session.

de Laurie VK3AMA
 


locked Re: Callsign Options Symbols dropdowns not sticking - DEFECT CONFIRMED

Carey, WB4HXE
 

Thank you Laurie!

On Sun, Jul 11, 2021 at 3:47 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 11/07/2021 12:51 am, Carey, WB4HXE wrote:

JTAlert 2.50.2. Under the Callsign Options window, Callsigns selection, the dropdowns for Lotw, Eqsl and Online don't seem to be working. I can select from the dropdown but when I release the mouse button, the item turns blank. See attached snip.

--
73, Carey, WB4HXE

Tnx Carey.

I can confirm the defect, and am seeing it here repeatedly. It went unnoticed as I am currently non-active using WSJT-X/JTAlert, haven't been for a couple of years!

Since this is reproducible in my tests, it should be painless, I hope, to identify the cause and produce a fix in time for the next public release.

de Laurie VK3AMA

--
Carey Fisher


--
73, Carey, WB4HXE


locked Re: JTAlert 2.50.2 About doesn't appear, no comm from WSJT-X

Gary N6DM
 

Hi Laurie, it was the runtime.  I had the wrong version installed (x86 vs x64).  It's working now.  I thought it was an x86 box (hey programs are in the x86 folder), but it is 64 bit, so anyway, all fixed.  Tnx for the help, Gary


locked Re: What happened to Ignore callsign option

WB5JJJ - George
 

I believe that was a default setting before.  I keep forgetting about the "gear" in the Callsigns window after I initially set thing up.  Would be nice to see that temporary ignore (session) as a default again.  

Once I made those selections, all is back to before 2.50 operations, I think.  Maybe I've just not needed something that was there before.  
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: JTAlert 2.50.2 About doesn't appear, no comm from WSJT-X

HamApps Support (VK3AMA)
 

On 12/07/2021 6:29 am, Gary wrote:
I've been trying to get WSJT-X (2.4.0) to send decodes to JTAlert (2.50.2) on my Win10 box but no success.  I tried reinstalling JTAlert, but same result.  I've followed all the instructions in the JTAlert Help under WSJT-X UDP Setup without success.  And at the end of the Setup it says to open the JTAlert About window but the About window never appears.  What have I missed?
Gary
The About window display is controlled by the JTAlertV2.Manager.exe process. If the process is not running or is continually stopping and restarting than the About window will not show and you will not be able to establish UDP comms with WSJT-X.

What does TaskManager show for the JTAlertV2.Manager process? Is it running or stopping & restarting.

Typical causes of the Manager not running is PC protection software interference or the incorrect NET runtime installed, usually the non-desktop version rather than the required "Desktop Runtime" version.

See this FAQ link for correct runtime install... https://hamapps.groups.io/g/Support/message/35794 <https://hamapps.groups.io/g/Support/message/35794>

de Laurie VK3AMA

1781 - 1800 of 37662