Date   

locked WSJT-X, JTAlert, Log4OM loading order ?

Andrew Buza
 

Been using above programs successfully for over a year.  I would run them in order,  Microham keyer II, then start Log4OM, then WSJT-X and finally JTAlert.  Last week log4OM lost it's configuration.  With over internet help from G4POP it was restored.
Now I must load WSJT-X first, followed by JTAlert and then Log4OM.  If I load Log4OM before the two others, I do not get any decodes in the JTAlert window and an error message expressing problem with the UDP connection comes up.  I'm running the server as 127.0.0.1 and port  2237.  All three boxes checked.
Wonder why the problem now with the loading order. I understand this may be a Log4OM problem but unsure of how JTAlert gets the info from the program.  No matter what, I always started WSJT-X before JTAlert as the UDP setup guide says JTAlert will automatically detect WSJT-X


locked Re: Double clicking on highlighted call in JT Alert no longer keys up Transmitter

HamApps Support (VK3AMA)
 

On 12/12/2020 7:04 am, Richard Philstrom wrote:
I no longer get the transmitter to key up if I double click on a highlighted call in the JT Alert window.
Not sure what changed.
Rnning the latest version of WSJT-x and JT alert


Dick W0TLE

JTAlert does not control keying of you transmitter. That responsibility is 100% controlled by WSJT-X.
JTAlert simply sends the appropriate command to WSJT-X and it is left to WSJT-X to decide if it will key your radio or not, typically based on the type of decode (was it a CQ or not).

If you're not seeing the Callsign being transferred to WSJT-X after the click event in JTAlert that would be caused by not having WSJT-X set correctly, specifically the "Accept UDP requests" checkbox.


BTW, you only need to use a single-click in JTAlert, the double-click requirement was retired a couple of years ago.

de Laurie VK3AMA


locked Double clicking on highlighted call in JT Alert no longer keys up Transmitter

Richard Philstrom
 

I no longer get the transmitter to key up if I double click on a highlighted call in the JT Alert window.
Not sure what changed.
Rnning the latest version of WSJT-x and JT alert


Dick W0TLE


locked Re: 2.16.17 Fails to log to DXKeeper

HamApps Support (VK3AMA)
 

On 12/12/2020 12:19 am, Stewart Wilkinson via groups.io wrote:
I have just found that for some reason 2.16.17 fails to log to DXKeeper - I get the folllowing shown by DXKeeper:



Stewart G0LGS

Your best to ask the DXKeeper people. The error message is not very helpful, the QSO could not be logged but there is nothing as to why it couldn't be logged., what was wrong that it couldn't log. The adif data looks correct, nothing unusual.

de Laurie VK3AMA


locked Re: Mouse is not working in JTAlert V2.16.17

HamApps Support (VK3AMA)
 

On 12/12/2020 12:46 am, Gerard de Veer wrote:

My mouse is not working anymore in JTAlert 
Can you give me advice how I solve this problem.
In futher releases I clicked on a station in JTAlert and I hat the station in JTDX.
If I now click there is notting happend.

Windows 10 Pro (up-to-date)
JTDX V2.2.RC153
JTAlert v2.16.17

Thanks in advance

Best 73

Gerard de Veer PD0GIP
You have posted the same question on 2 other occasions and I have replied
here https://hamapps.groups.io/g/Support/message/32262
and here https://hamapps.groups.io/g/Support/message/32516

You have never replied to either of those posts.

The problem is your JTDX settings.
You need to ensure "Accept UDP requests" is enabled in JTDX


If JTDX is not set to accept UDP requests, than mouse clicks in JTAlert will be ignored by JTDX. This is not a JTAlert problem but a JTDX setting problem.

de Laurie VK3AMA


locked Re: Copy configuration to other computer

José L. Oliva - EA4ZQ
 

Oh, I tried to found information in a huge ammount of post, when I decided post may question.. but answer is closer... thanks.


locked Re: 2.16.17 Fails to log to DXKeeper

Stewart Wilkinson
 

Seems it was some sot of issue with DXKeeper - a restart of DXKepeer seems to have resolved it.


locked Re: Mouse is not working in JTAlert V2.16.17

D. Scott MacKenzie
 

Is it working in other applications, or just in JTAlert?  I have had that happen when I get RFI into the mouse.  I wrapped a ferrite core around USB cable and the problem never occurred again.

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Gerard de Veer
Sent: Friday, December 11, 2020 8:46 AM
To: Support@HamApps.groups.io
Subject: [HamApps] Mouse is not working in JTAlert V2.16.17

 

Hello,

 

My mouse is not working anymore in JTAlert 

Can you give me advice how I solve this problem.

In futher releases I clicked on a station in JTAlert and I hat the station in JTDX.

If I now click there is notting happend.

 

Windows 10 Pro (up-to-date)

JTDX V2.2.RC153

JTAlert v2.16.17

 

Thanks in advance

 

Best 73

 

Gerard de Veer PD0GIP

Borodinstraat 166

5011 HE Tilburg

Tel. 0134555888 - 0640798489

 


locked Re: V2.16.17 - Color

Jim Denneny
 

Thanks Laurie.  Problem was at my end.  I only checked wanted DXCC.  There are very few I need.  That is why I did not see color.

73, Jim K7EG


locked Mouse is not working in JTAlert V2.16.17

Gerard de Veer <gerard@...>
 

Hello,

My mouse is not working anymore in JTAlert 
Can you give me advice how I solve this problem.
In futher releases I clicked on a station in JTAlert and I hat the station in JTDX.
If I now click there is notting happend.

Windows 10 Pro (up-to-date)
JTDX V2.2.RC153
JTAlert v2.16.17

Thanks in advance

Best 73

Gerard de Veer PD0GIP
Borodinstraat 166
5011 HE Tilburg
Tel. 0134555888 - 0640798489


locked Re: Feature Request - LoTW Last Upload Filtering

Ron W3RJW
 
Edited

On Thu, Dec 10, 2020 at 05:41 PM, Dev Null wrote:
Whoa. I have received both paper and LOTW confirmations for needed countries five to seven years or more later. Good luck.
Yes that is true, but a thing to know about the LOTW users list is that if you have ever uploaded to LOTW, you are on the list forever.

If one is seeking confirmation for an award, you would like to have reasonable expectations of a timely response.  It doesn't mean you won't work the station, it just means he uses LOTW on a regular basis and I have a better chance of getting a quicker confirmation.. WSJT-x allows for one day increments for the its LOTW user alarm. I use 60 days. HRD has no time limit filters on showing LOTW users.

If I really want to know their last upload, I go to the ARRL LOTW website, "Find Call" tab.

These are alarms, not rejections.
 
--
73
Ron, W3RJW


locked Re: Copy configuration to other computer

Michael Black
 

Help/FAQ
Inline image


Mike W9MDB


On Friday, December 11, 2020, 02:35:34 AM CST, José L. Oliva - EA4ZQ <joseluis.oliva@...> wrote:


Hi, group.

I need copy configuration to other computer. Is this possible?
Manual clonning config is not so easy if computers aren't together...
Thanks.


locked 2.16.17 Fails to log to DXKeeper

Stewart Wilkinson
 

Hi,

I have just found that for some reason 2.16.17 fails to log to DXKeeper - I get the folllowing shown by DXKeeper:



Stewart G0LGS


locked Copy configuration to other computer

José L. Oliva - EA4ZQ
 

Hi, group.

I need copy configuration to other computer. Is this possible?
Manual clonning config is not so easy if computers aren't together...
Thanks.


locked Re: 2.16.16 crashes

Dennis
 

Just wanted to update what I did to eliminate my JTAlert crashes.  I uninstalled the program, deleted the
..\appdata\local\HamApps, folder, reinstalled 2.6.17, and reconfigured JTAlert.

Fingers crossed, no crashes in 90 minutes of use, had been failing about every third or fourth decode
cycle.
--
73, de N4QM


locked Re: Feature Request - LoTW Last Upload Filtering

Dev Null
 

I find that even 1 year as a time limit is too long.  If I am looking for a contact for an ARRL award, I want to have confidence that the QSL will occur sooner than that.
Whoa. I have received both paper and LOTW confirmations for needed countries five to seven years or more later. Good luck.

Larry N8KU


locked Feature Request - LoTW Last Upload Filtering

David
 

Using JTAlert 2.16.17

JTAlert can be set to flag callsigns whose stations have uploaded to LoTW within the past 1, 2, 3, 4 or 5 years.  The setting is under
     Miscellaneous Alerts --> LoTW / eQSL(AG) Flags --> LoTW Last Upload Filtering

I find that even 1 year as a time limit is too long.  If I am looking for a contact for an ARRL award, I want to have confidence that the QSL will occur sooner than that.

Request: Change the current filter list from
     1 Year / 2 Years / 3 Years / 4 Years  / 5 Years
to
     24 months / 18 months / 12 months / 6 months / 3 months

Thank you.

David, AK2L


locked Re: V2.16.17 - Color

HamApps Support (VK3AMA)
 

On 10/12/2020 3:15 am, Jim Denneny wrote:
The alert colors are not evident with this release.  I have not found a procedure in Settings to turn them on.

73, Jim K7EG

There have been no other reports of missing Alert colors in JTAlert.

There were no changes to Alert colors in this new release (there haven't been any color changes for many versions). Colors will only be displayed when its corresponding Alert is enabled and a Decode/Callsign generates that Alert.

Are you sure you have your Alerts enabled? Open the "View -> Alert Types Summary Window" it will give you an overview of all your set colors and the enabled state of the Alerts. eg..

   

de Laurie VK3AMA


locked Re: Text MSG indicator

HamApps Support (VK3AMA)
 

On 11/12/2020 1:13 am, Ron W3RJW via groups.io wrote:
As far as I can tell they both indicate the same thing.  Depending on your monitor resolution, the underline can be hard to see.
 
--
73
Ron, W3RJW

That's correct, both indicate the same thing. The square indicator was introduced because of visibility issues with the underline.
While I added an enable option for the square indicator, I neglected to add an enable option for the underline, That will likely be in the next release.

de Laurie VK3AMA


locked Re: Text MSG indicator

Ron W3RJW
 

On Wed, Dec 9, 2020 at 06:27 AM, Komkit Listisard wrote:
I also see the underline under the callsign as well. Isn't it indicates the very same thing?
As far as I can tell they both indicate the same thing.  Depending on your monitor resolution, the underline can be hard to see.
 
--
73
Ron, W3RJW

381 - 400 of 32879