Date   

locked Re: Moving "QSO Logged" window?

HamApps Support (VK3AMA)
 

On 21/04/2021 10:38 pm, Bill - AA4M wrote:
That gave me an idea.  I moved the main JTAlert window around until it resulted an placing the QSO window where I wanted.  Tedious, but this worked.  But I look forward to a later version of JTAlert when the QSO window can be dragged and will stay where it's placed.

Thanks for this superior software and support Laurie!

73, Bill  AA4M

Bill,

An alternative, if you happy that JTAlert is logging the QSOs reliably without error, is to turn off the "logging success" popup but leave the "logging failure" popup enabled. See the "Window -> Popup Windows" section of the main JTAlert Settings window.

de Laurie VK3AMA


locked Re: No calls are showing up in Callsign window

HamApps Support (VK3AMA)
 

On 21/04/2021 12:06 pm, Charlie Rubenstein wrote:
I upgraded to the newest version, and am not getting any callsigns at all. The title bar shows the correct band, etc, but no decodes or callsigns.

I still have the UDP on port 2237 and all three boxes are checked in WSJT-X.

What am I doing wrong?

de Charlie KB8CR

See my answer to the other thread you started.
https://hamapps.groups.io/g/Support/message/34571

de Laurie VK3AMA


locked Re: Not having luck with UDP settings

HamApps Support (VK3AMA)
 

On 22/04/2021 3:46 am, Charlie Rubenstein wrote:
I have had no luck (execpt once when it spontaneously started working for a while) getting the decodes and callsigns to show up from WSJT-X.

Here are the settings from the "About window"
JTAlert Instance       : #1
JTAlert Start Params   : /wsjtx
WSJT-X Window Title    : WSJT-X   v2.3.1   by K1JT, G4WJS, and K9AN
WSJT-X Command Line    : "C:\WSJT\wsjtx\bin\wsjtx.exe" 
WSJT-X   --rig-name    : 
WSJT-X Config File     : C:\Users\KB8CR\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version         : 2.3.1
WSJT-X Revision        : 0e7224
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 : True
WSJT-X UDP Max Schema  : 3
 
Any help would be greatly appreciated.. I also can't get it to write logs to my HRD 6 logbook which worked fine before the upgrade.

73 de Charlie KB8CR

I see your using a Flex, does that indicate you're running multiple instances of JTAlert? If so, since you're using a unicast UDP address (127.0.0.1) you will need to give each WSJT-X a unique UDP port value, they cannot all be 2237. Setting to use multicast is a better solution than setting each wsjtx configuration to use a unique port.

If you're only running a single JTAlert instance, then likely you have another application trying to work with wsjtx and it is taking exclusive control of the port. In that situation, your best to configure wsjtx to use multicast UDP. See the JTAlert help file "WSJT-X UDP Setup" topic for correct wsjtx and jtalert setup. You will also need configure any other applications trying to work with wsjtx directly to us multicast as well.

My strong advice, regardless of whether you're running single or multiple instances is to use Multicast UDP.

de Laurie VK3AMA


locked Feature suggestion for variable filters for multiple instances #FT8

Pat N6PAT
 

I use a Flex 6700 which allows using up to 8 receivers (slices in Flex terminology) for different band/mode configurations  simultaneously.  I usually monitor 6 bands at the same time with each receiver having it's own JTAlert instance.

Currently, the filter criteria is configured on the settings page and all instances are controlled by the same single filter criteria. There is no independence between the instances.

My idea is to have the ability to configure numerous filters on the settings page and save them under unique names such as Just NA, NA LOTW, EU eQSL, CQ Only, etc.These would be created on the main settings page and could be made available to each instance via a drop down list at the bottom of the Call Sign Window.

So with that option in place I could have Receiver A dedicated to DX only , Receiver B for NA, Receiver C for EU, etc.or I could turn off the filter  on any or all instance with either a toggle switch or by selecting No Filter in the drop down list for a given receiver while not impacting other active receivers. This would be a major benefit for Flex users in particular but also for anyone running more than a single JTAlert instance

Another advantage would be eliminating the need to go back to the settings page to select a different filter or turn the filters off during operation. That could be done via the drop box.


locked Wildcard in Wanted Callsign - not triggered?

 

Greetings.

I have added the following callsigns and callsign prefixes with wildcard into the Wanted Callsign Alert list.

When a callsign is decoded in the CQ period, that matches a wildcard callsign prefix, JTAlert does not alert.

Here is a screen grab of my settings and the CQ decode:



Am I doing this incorrectly?

Thanks,

73 de NW7US dit dit

SKCC Nr. 4758s / FISTS Nr. 7055 / LICW Nr. 653 
NW7US on QRZ / NW7US on YouTubeTwitterFacebookBlog
Space weather and radio propagation editor for 
      - CQ Amateur Radio Magazine, and,
      - The Spectrum Monitor magazine. 

..


locked Re: JT Alert 2.50.0 stopped by FrameworkCheck

alchowiake@...
 

I have 32bit Windows 10 Home version 20H2 (which is the latest) with Net 5 and FrameworkCheck claims it's incompatible with my system so I can't get 2.50 to run. If I try to ignore this and run 2.50 anyway it just generates a bunch of error messages.


locked Re: Not having luck with UDP settings

g4wjs
 

On 21/04/2021 18:46, Charlie Rubenstein wrote:
I have had no luck (execpt once when it spontaneously started working for a while) getting the decodes and callsigns to show up from WSJT-X.
Hi Charlie,

having WSJT-X UDP communications working, but only occasionally, when you are using a unicast server address like 127.0.0.1 is a sign that more than one server is trying to listen for traffic. That will not work reliably and traffic will only be delivered to one server. You clearly have JTAlert as one server listening for WSJT_X UDP traffic on port 2237, do you have any others? If you do then you must configure all of them for multicast UDP before your setup will work correctly, alternatively close down the other servers that are "stealing" the traffic.



--
73
Bill
G4WJS.


locked Re: Not having luck with UDP settings

AB8WD-Willie
 
Edited

Try downloading slicemaster it should configure HRD and wsjt and jtalert to play nice together just a thought AB8WD
and rebooting pc and reconnecting flex afterward sometimes a good reboot helps.


locked Not having luck with UDP settings

Charlie Rubenstein
 

I have had no luck (execpt once when it spontaneously started working for a while) getting the decodes and callsigns to show up from WSJT-X.

Here are the settings from the "About window"
JTAlert Instance       : #1
JTAlert Start Params   : /wsjtx
WSJT-X Window Title    : WSJT-X   v2.3.1   by K1JT, G4WJS, and K9AN
WSJT-X Command Line    : "C:\WSJT\wsjtx\bin\wsjtx.exe" 
WSJT-X   --rig-name    : 
WSJT-X Config File     : C:\Users\KB8CR\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version         : 2.3.1
WSJT-X Revision        : 0e7224
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 : True
WSJT-X UDP Max Schema  : 3
 
==================================================
UDP Ports used
--------------------------------------------------
JTAlert.exe           : 63118 49212
JTAlertV2.Manager.exe : 50349 50350 50351
JTAlertV2.Decodes.exe : 
 
 
==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (Realtek High Definition Audio)
[2] DAX RESERVED AUDIO RX 1 (FlexRadio Systems DAX Audio)
[3] DAX RESERVED AUDIO RX 6 (FlexRadio Systems DAX Audio)
[4] CABLE Input (VB-Audio Virtual Cable)
[5] DAX RESERVED IQ RX 2 (FlexRadio Systems DAX IQ)
[6] DAX RESERVED IQ RX 3 (FlexRadio Systems DAX IQ)
[7] DAX RESERVED IQ RX 4 (FlexRadio Systems DAX IQ)
[8] DAX RESERVED AUDIO RX 7 (FlexRadio Systems DAX Audio)
[9] DAX RESERVED AUDIO RX 8 (FlexRadio Systems DAX Audio)
[10] DAX RESERVED IQ RX 1 (FlexRadio Systems DAX IQ)
[11] DAX RESERVED AUDIO RX 2 (FlexRadio Systems DAX Audio)
[12] DAX RESERVED MIC AUDIO (FlexRadio Systems DAX MIC Audio)
[13] DAX RESERVED AUDIO RX 5 (FlexRadio Systems DAX Audio)
[14] DAX RESERVED AUDIO RX 3 (FlexRadio Systems DAX Audio)
[15] DAX Audio TX (FlexRadio Systems DAX TX)
[16] DAX RESERVED AUDIO RX 4 (FlexRadio Systems DAX Audio)
 
 
==================================================
JTAlertV2.Manager (2.50.0.0) status
(2021-04-21 17:43:57 utc)
--------------------------------------------------
CLR Version      : 5.0.5
NET Framework    : .NET 5.0.5
--------------------------------------------------
UDP Router       : Initialized * : YES (WSJT-X)
Audio            : Initialized * : YES (16 output devices)
BandData         : Initialized * : YES (started : 58)
Text Msgs        : Initialized * : YES (started : 17)
HamSpots         : 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      : Initialized * : YES (started : 3600)
Maintenance      : Initialized * : YES (started : 3600)
--------------------------------------------------

Any help would be greatly appreciated.. I also can't get it to write logs to my HRD 6 logbook which worked fine before the upgrade.

73 de Charlie KB8CR


locked Re: Moving "QSO Logged" window?

Bill - AA4M
 

That gave me an idea.  I moved the main JTAlert window around until it resulted an placing the QSO window where I wanted.  Tedious, but this worked.  But I look forward to a later version of JTAlert when the QSO window can be dragged and will stay where it's placed.

Thanks for this superior software and support Laurie!

73, Bill  AA4M


On 04/20/2021 12:09:05, HamApps Support (VK3AMA) wrote:
On 20/04/2021 11:24 pm, Bill - AA4M wrote:
I'm using version 2.50.0 of JTAlert.  For some reason the little "QSO Logged" window has moved to the bottom of the screen.  Is there any way I can relocate it?

73, Bill  AA4M

That popup cannot be moved. Its position is fixed to the location of the parent window that presented the popup, in this case the main JTAlert window. This is behavior that as existed for many years.

JTAlert is in transition moving from the old code-base to the new .NET code. That popup is still living in the old code. Eventually it will switch over to the new code and no longer be tied to the old JTAlert main window. Notifications in the new code will be handled in a different manner avoiding the current hard-coded positioning of these popups that scroll up out of the JTAlert window title-bar.

de Laurie VK3AMA



locked Re: Windows Defender false positive : Release 2.50.0

Dave Garber
 

tell defender to ignore hamapps folder in scans


Dave Garber
VE3WEJ / VE3IE


On Tue, Apr 20, 2021 at 1:21 PM Jay <jay.n4nqy@...> wrote:
I never had JTAlert issues until 2.5.0.  Windows Defender quarantines the "Settings" exe file, making it impossible to change any settings.

Also, I keep working stations over and over because not all Call Signs show up as Worked B4.   Seems restarting JTAlert resets something of the database entries.

I love the new app, but simply can no longer run it, since JTAlert will not start without the "Settings" exe.  "Trojan:Win32/Hynamer.A!ml"

73  jb  N4NQY


locked Re: Possible Anomaly In Message Window

John Petrocelli
 

I just saw that & thanks.

I likely missed that one

John
John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com
On 2021-04-21 03:05, Gordon Brown wrote:
Laurie already replied to earlier message about this.
https://hamapps.groups.io/g/Support/message/34549
He said the fix is in the next JTA
:-)



Virus-free. www.avast.com


locked Feature suggestion - option to partition call window for DX vs Domestic #FT8

Pat N6PAT
 

Another from my wish list:

An option to allow splitting DX vs domestic call signs into separate partitions within the call sign window. Allow the user to turn  the option on or off as they wish.

What do you think?


locked Re: Possible Anomaly In Message Window

Gordon Brown
 

Laurie already replied to earlier message about this.
https://hamapps.groups.io/g/Support/message/34549
He said the fix is in the next JTA
:-)


locked JTAlert 2.50 Won't start

alchowiake@...
 

I have windows 10 with ALL Microsoft updates installed. I have Net 5 runtime installed but when I load 2.50 Frameworkcheck says "This app can't run on your PC" and a bunch of other random error messages follow.


locked Possible Anomaly In Message Window

John Petrocelli
 

Hello,

  I think I see an interesting behavior or anomaly in the Message Window in version 2.50.x.

 The scenario .............

  Receive a text message from station "XXXXX"
  Start to reply to the message

  See another station "YYYYY" calling CQ and reply to that stations CQ
  Switch back to the Message Window and finish typing the text to station "XXXXX"
  Send the message and realize that the message is actually sent to station "YYYYY"
  as the target/recipient has changed to the current station that one is working.

  Is this by design or is it something else.

  Thanks in advance to Laurie and all who reply

John
 
-- 


John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com

Virus-free. www.avast.com


locked Re: 2.5.0 -- AutoIt Error

David Merchant - K1DLM
 

I'm getting an AutoIT error every time I try to launch JTAlert 2.50.  Specifically, the error says "Line 6817 (File C:\Program Files(x86)\HamApps\JTAlert\JTAlert.exe)  Error: Subscript used on non-accessible variable.

I was able to get it to load initially and was using the software.  However, it wouldn't let me select a station for my next QSO, so I tried restarting it.  That's when the error occured.

Any suggestions?

Thanks & 73,

Dave
K1DLM


locked Re: Wanted county #FT8

Paul&Tracy Richards
 

Hello Laurie

Some further info here.

The County Hunting game is a bit divided at present.

We have the CQ Magazine sponsored WACA which has been around for donkeys years but frankly has fallen into a bit of disarray. CQ accept paper cards and Eqsl but only if the US based Eqsl user has authorised status. As you have noted, even finding a list of counties that qualify for their award is now problematic. Due to the difficulties in non US hams getting confirmations for this program and the old fashioned card checking process this award is mainly chased by US based hams. CQ do not accept LOTW.

The newer player in town is QRZ who have their own Counties Award using a slightly different county list which is easily obtained.
QRZ accept confirmations via their own logging program and LOTW - but not EQSL. For non US hams, confirmations are easy to obtain, the QRZ system auto tallies your worked counties and applying for the award is as easy as pressing one button.

Gridtracker appears to be setup with the QRZ county list. This makes sense as the CQ Award has never demonstrated any interest in appealing to FT8 users or non US based hams in my opinion. Everyday there are county activators who drive around the USA activating rare counties but I have never once seen these activators on digital modes. I am told no station has ever worked all counties on digital (even in the USA) - it seems the CQ Award is focused on ssb and cw and thus probably not a great match for JTAlert.

Currently I chase both programs in the forlorn hope that one day CQ may get their act together with this Award.

It is worth comparing the tired old CQ Award with the Russian Districts Award - the Russians have a fantastic new webpage, easy online tracking, electronic confirmations and electronic award application and issuance.

I hope this info is helpful should you decide to add county tracking down the line - in short - the QRZ program may be better aligned to JTAlert users

Cheers
Paul - vk4ma


locked Re: DT explanation request

Alessandro Gorobey
 

Hi Laurie,
thanks for the quick response, but the value is always +1,0 (one comma zero) and never change.

now my clock is off 0.294ms and there is over 20 decodes per cycle

last 100 DT are
 -2.2  -1.0  -0.6  -0.6  -0.6  -0.4  -0.2  -0.2  -0.2  -0.2  -0.1  -0.1  -0.1  -0.1  -0.1  -0.1  -0.0   0.0   0.0  -0.0  -0.0   0.0   0.0   0.0   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.1   0.2   0.2   0.2   0.2   0.2   0.2   0.2   0.2   0.2   0.3   0.3   0.3   0.3   0.3   0.3   0.4   0.4   0.5   0.6   0.6   0.6   0.6   0.7   0.7   0.8   0.8   0.8   0.9   0.9   1.0   1.2

the media give me a value of about 0.1 as expected

Compliments again


73 Sandro IW3RAB




locked Line 10385

Gabriel - M0JHV
 

Hi Laurie,

Config - Windows 10 Home - 64-bit up-to-date and WSJT-X 2.3.0
JTAlert 2.50.0 is crashing at every launch after 10-60 s with
Line 10385 Error: Variable used without being declared.
Please advise.

Thanks in advance,
73 de M0JHV Gabriel

2661 - 2680 of 36991