Date   

locked Re: Interfacing JTAlert with ACLog

James Tills W7JWT Stevens County DEM
 

It is very easy. If you want ACLog to also do DXSpotting and want to use it to control your rig when you select a DX Spot, you will need to use two cables, one to the USB port and one to the Remote port. This resolves the single com port issue. This gives you two com ports. I can send you all the configuration settings if you want. This is by far the best way to do it and all it requires is the second cable. E-Mail me if you want the details. You don't need any other rig control programs. This also works for FLDigi and Winlink. CUL. Jim. W7JWT

On Jul 25, 2020 1:45 PM, VE3QN <ars.ve3qn@...> wrote:
I've just begun using JTAlert. It's working fine but I am particularly interested in having JTAlert updates contacts to N3FJP's ACLog. I think I know how to do this but the one obstacle I have is that the interface my IC-7300 uses to both programs is the same COM port - COM 5. Neither program will run if the other is running. What's the easiest way around this? Thanks in advance. Bryan VE3QN


locked Re: JTAlert does crash rem

David De Coons
 

How do you have WSJT-X radio connection info set up?

Dave wo2x


On Jul 25, 2020, at 4:17 PM, asobel@... wrote:



I am using Win10, Flex 6600 + SmartSDR, 4 instances of WSJTX-X + JTAlert. all of the latest verston.
Every time I change frequencies by way of SmartSDR, One or more instances of JTAlert does cresh.
I have to kill the task of the fallen alert and start it again.
This is very annoying. Please help.

Amos 4X4MF.


locked Re: Interfacing JTAlert with ACLog

Michael Black
 

Wrong list really as this isn't JTAlert related.

But...there are two solutions.  One uses two copies of hamlib utilities and the other uses one copy of hamlib utilities and FLRig.

You will need virtual serial ports using something like com0com or Eltima's solution.

First thing is to shutdown WSJT-X.

#1 Test to see you can talk to your IC-7300 
rigctl-wsjtx -m 3074 -r COM1 -s 19200 f m
Adjust com port and baud rate to suit.  You should see the rig frequency, mode, and bandwidth be returned
#2 If #1 one works just change the line to this to start rigctld instead
rigctld-wsjtx -m 3074 -r COM1 -s 19200
#3 Start WSJT-X -- you'll get a rig error...click OK and for the rig selection pick "Hamlib NET rigctl".
#4 Now start the hamlib TS-2000 emulator -- say you have a serial port pair COM10/COM11
rigctlcom -m 2 -R COM10 -S 115200
#5 Start ACLog and set up COM11 , 115200, TS-2000

Second solution uses FLRig -- install it and get it connected to your rig.

#1 Select FLRig in WSJT-X
#2 rigctlcom -m 4 -R COM10 -S 115200
#3 Start ACLog and set up COM11 , 115200, TS-2000

Mike W9MDB





On Saturday, July 25, 2020, 04:16:32 PM CDT, VE3QN <ars.ve3qn@...> wrote:


I've just begun using JTAlert. It's working fine but I am particularly interested in having JTAlert updates contacts to N3FJP's ACLog. I think I know how to do this but the one obstacle I have is that the interface my IC-7300 uses to both programs is the same COM port - COM 5. Neither program will run if the other is running. What's the easiest way around this? Thanks in advance. Bryan VE3QN


locked Re: Interfacing JTAlert with ACLog

Larry Banks
 

I assuming you are using WSJT-X too.  Normally you would use WSJT-X to interface to your rig.  Then JTAlert can update ACLog via the API.

73 -- Larry -- W1DYJ

From: VE3QN
Sent: Saturday, July 25, 2020 16:45
Subject: [HamApps] Interfacing JTAlert with ACLog
 
I've just begun using JTAlert. It's working fine but I am particularly interested in having JTAlert updates contacts to N3FJP's ACLog. I think I know how to do this but the one obstacle I have is that the interface my IC-7300 uses to both programs is the same COM port - COM 5. Neither program will run if the other is running. What's the easiest way around this? Thanks in advance. Bryan VE3QN


locked Interfacing JTAlert with ACLog

VE3QN
 

I've just begun using JTAlert. It's working fine but I am particularly interested in having JTAlert updates contacts to N3FJP's ACLog. I think I know how to do this but the one obstacle I have is that the interface my IC-7300 uses to both programs is the same COM port - COM 5. Neither program will run if the other is running. What's the easiest way around this? Thanks in advance. Bryan VE3QN


locked JTAlert does crash rem

asobel@...
 

I am using Win10, Flex 6600 + SmartSDR, 4 instances of WSJTX-X + JTAlert. all of the latest verston.
Every time I change frequencies by way of SmartSDR, One or more instances of JTAlert does cresh.
I have to kill the task of the fallen alert and start it again.
This is very annoying. Please help.

Amos 4X4MF.


locked Re: No sound JTALERT 2.16.9

John
 

Hi Ed,

I also have the same problem. I've been "fighting" it for a while. I tried a very earlier version (2.13.10) that started every time.
If you try starting JTAlert a few times it might start. Once I got it started I never shut it down, just minimize it. That works fine until one of your other programs does or needs a computer re-start.
I've been working with Laurie about this.
Send in a Contact Support message, under "Help"

73,
John

    
On 7/24/2020 11:02 AM, lmeeny wrote:
Hello,

I'm having a recurring problem. Selected alerts and test sound card .wav files are not being played.?? Under settings I've verified the .wav files are present and selected. Playing an individual .wav file via windows works OK.

Suggestions please.

73

Ed W2GHD


Virus-free. www.avg.com


locked Re: No sound JTALERT 2.16.9

lmeeny
 

Hello,

An additional bit of information. JTALERT does not show up in the volume mixer during test sound card or while  another alert is commanded.

Also, Task Manager, under APPS, lists WSJT-X (Jtalert alt. layout) 32 bit and, under Background Processes, JTALERTV2 manager, 32 bit.

73,

Ed W2GHD


locked No sound JTALERT 2.16.9

lmeeny
 

Hello,

I'm having a recurring problem. Selected alerts and test sound card .wav files are not being played.  Under settings I've verified the .wav files are present and selected. Playing an individual .wav file via windows works OK.

Suggestions please.

73

Ed W2GHD


locked Re: # ?

wo4o RiC
 

Thank you Dave and Ron!

Good to know.

73 de RiC wo4o
Grand Island FL


locked Re: DXCC abbreviations inconsistent with LoTW, ClubLog and others

WB5JJJ - George
 

Yes, Carey, there are unique DXCC numbers, but those by themselves don't mean much to most folks.  And if you do a cross reference, then you are in the same boat.  

I just finished building a crude spreadsheet where I can cut and paste from LoTW with their entity name for each band and it does a VLookUp and grabs the JTA naming convention for each entry.  I just sort the band spreadsheet tabs and it all now jives.  As a country changes name, a simple edit will correct it, once I see it in JTA.  Also I have the spreadsheet marked every 13 entries, so it's a very quick process to see where a DXCC needs to be added, now that the "s" abbreviations are modified.  And since I only check against LoTW, the rest are irrelevant.  

I use JTA to keep track of ALL of my QSO's from day one back in 1973.  I'm not trying for WAS or DXCC on FT8, so all I want to know is that it's an ATNO on a specific band for me PERIOD.  That's why I go through all of this.  As JTA has become a single point of reference for me.  I can't scan my log in JTA since it will delete all non-digital QSO's I've entered.  Found that out the hard way a couple years ago.  I had well over 200 mixed DXCC before FT8, and now I've added about 75 new ones on FT8, and a few more on SSB and CW as well.  
--
73's
George - WB5JJJ


locked Re: DXCC abbreviations inconsistent with LoTW, ClubLog and others

Carey, WB4HXE
 

Don't all entities have a DXCC number irrespective of the text name? Using the number should solve the problem. Maybe?
73, Carey, WB4HXE

On Thu, Jul 23, 2020 at 8:13 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 23/07/2020 2:44 am, Jim Reisert AD1C wrote:
I don't make
changes like this anymore, unless the entity name has really changed,
like Swaziland -> eSwatini

-- Jim Reisert AD1C

Jim,

Even using eSwatini it could be argued that is still not correct as it is missing the leading "Kingdom of " of the true name. Just my 2 cents, and not a dig at your choice of names.

de Laurie VK3AMA



--
Carey Fisher


locked Re: Statistic Window

HamApps Support (VK3AMA)
 

On 23/07/2020 12:05 am, WB8ASI Herb wrote:
I've had a couple occasions where deleting the "decodes" files turning out to be the fix.  It would be nice if there was a "reset" choice maybe under the Decodes Window "view" tab that could delete them without drilling down thru the localappdata path.

Herb,

Unless your keen to keep the decodes from previous JTAlert sessions visible, set the Decodes window (via its Settings menu) to delete all records on startup. Under-the-hood, JTAlert simply deletes the database file and creates a new file rather than executing an sql query to delete all records.
   

If you want the decodes from the last JTAlert session to be available (so the above is not suitable) and need a quick way to delete the database when it appears to be malfunctioning, do the above, restart the Decodes window and then change the startup option back to your original setting.

de Laurie VK3AMA


locked Re: Wanted US States status updates

HamApps Support (VK3AMA)
 

On 24/07/2020 9:58 am, HamApps Support (VK3AMA) via groups.io wrote:
My guess is that you don't have all the options checked matching how ACLog is determining/reporting your WAS status.

I missed the following in my original replay... For example you may have JTAlert set to only consider LoTW QSLs when rebuilding the Alert database during the scan of your log, while ACLog may be considering Card, Eqsl and LoTW confirmations.

de Laurie VK3AMA


locked Re: DXCC abbreviations inconsistent with LoTW, ClubLog and others

HamApps Support (VK3AMA)
 

On 23/07/2020 2:44 am, Jim Reisert AD1C wrote:
I don't make
changes like this anymore, unless the entity name has really changed,
like Swaziland -> eSwatini

-- Jim Reisert AD1C

Jim,

Even using eSwatini it could be argued that is still not correct as it is missing the leading "Kingdom of " of the true name. Just my 2 cents, and not a dig at your choice of names.

de Laurie VK3AMA


locked Re: DXCC abbreviations inconsistent with LoTW, ClubLog and others

HamApps Support (VK3AMA)
 

On 23/07/2020 12:52 am, WB5JJJ - George wrote:
This is a minor issue at best, but one that appears could be easily changed. 

I compare with LoTW frequently to insure that DXCC's are staying in sync between JTA and LoTW.  When I see that JTA and LoTW disagree, I do a compare.  But when I get to the "S" group, the JTA abbreviations really put a kink in what would otherwise be a very quick compare.  Also "Republic of South Africa" is listed in JTA as just "South Africa".  There are other variations in the "U" group as well.   A few others almost look like a totally different DXCC until you realize there is no other choice. 

Would you consider adjusting these DXCC entries to the more conventional syntax that LoTW, ClubLog and others use?  I know that I would really appreciate it, and perhaps others as well. 
--
73's
George - WB5JJJ

George,

Depending on the Country, even LoTW and Clublog disagree on the correct name. Unfortunately, there is not a single "Master" source of DXCC Country names.

Even the ADIF standard Country name enumeration is not consistent, having applied some recent Country name changes but not others. It still lists "SWAZILAND" while the ARRL list has correctly been updated to "Kingdom of Eswatini". Yet both lists have updated "Auckland and Campbell" to "New Zealand Subantarctic Islands" as examples. Why are some entity names updated and not others is any one's guess.

"South Africa" is used by both the ADIF and ARRL and JTAlert has followed that lead, yet looking at DXKeeper, it lists "Republic of South Africa", who is right/wrong in this situation?

de Laurie VK3AMA


locked Re: Wanted US States status updates

HamApps Support (VK3AMA)
 

On 23/07/2020 10:22 am, Kim Leong wrote:
I have JTAlert 2.16.9 and AC Log 6.6.  I have all states worked on 7 bands.When I run Rebuild Alert Database and then look at Wanted US States, it still shows a multitude of states needed on those bands.  Is there a particular field and information that Rebuild looks for in AC Log to update as no longer needed state?  Currently the Recv Conf By field on these contacts has at least a C, in addition to L and/or Q.

Thank you and 73

Kim Leong  N6YJ

What QSL confirmation types do you have set for the "Wanted State alert" under the "Rebuild Alert Database" section of the Settings?  My guess is that you don't have all the options checked matching how ACLog is determining/reporting your WAS status.

de Laurie VK3AMA


locked Re: Will not launch - error

HamApps Support (VK3AMA)
 

On 23/07/2020 5:20 am, Joe Roth wrote:
I updated to v 2.16.9 from 2.16.8. Now I get the error shown here (AutoIt Error). I went back to v 2.16.8 and got it again. I un-installed the program including registry and folder.
Installed 2.26.9 fresh and still get the error.
Who can help here?
v 2.16.8 worked fine before the update. Using Win10 and high-end PC.

My only suggestion is a complete uninstall of JTAlert including a manual deletion of all files and directories located under the %localappdata%\HamApps\ directory. Be warned that deleting the %localappdata%\HamApps\ directory will delete your JTAlert config. If after doing this you still cannot start JTAlert after a new install, my only thoughts are that your PC protection software is interfering.

de Laurie VK3AMA


locked Re: Windows notification sounds

HamApps Support (VK3AMA)
 

On 23/07/2020 5:13 am, Joe wrote:
it's no good having the same sound for both a successful QSO log and and a failed QSO log

The next JTAlert release has individual sounds for "Errors & Warnings" and "Success & Notifications" .

de Laurie VK3AMA


locked Re: Windows notification sounds

HamApps Support (VK3AMA)
 

On 23/07/2020 2:10 am, Ron W3RJW via groups.io wrote:
Along these same lines I now get both the "windows Notification" sound and the "Text Message" sound when a text message comes in, one after the other.
That's a defect. Already corrected for the next release.

de Laurie VK3AMA

5481 - 5500 of 36374