Date   

locked Re: JTAlert V2.15.18 - Log4OM V2 Thank You

neil_zampella
 
Edited

Just to let you know ... his 'team' is just one person, Laurie himself.   He puts in a lot of time to get things right.  Oh and its v2.15.8 ... to be precise :)

 

Neil, KN3ILZ


locked Re: Logging to DXKeeper Trouble #DXLAB

neil_zampella
 
Edited

Dale,

Are you really on v2.11.5 of JT-Alert?   The most current version is v2.15.8.   Unless you're on WinXP you should install the newer version and see what happens.  Also, the most current DXKeeper, as far as I can tell by what the Launcher says, is 15.3.1 .

 

Neil, KN3ILZ


locked Re: JTAlert error messages

neil_zampella
 

Michael ... I am saying that you have JT-Alert and WSJT-X both trying to send UDP packets on the same port.   Only one program can use the port at a time.   I would turn off the WSJT-X repeat as it will most likely be removed in the next version.   The JT-Alert will work.

However, you should not have to use it if the JT-Alert log settings for HRD v5/V6 are setup correctly.

 

Neil, KN3ILZ


locked Re: JTAlert error messages

Michael Ernst
 

Neil, KN3ILZ 

I was wondering if it was meant for me. 

I am unclear as to how you are saying I should have the settings.  I played around with this a year or so ago and this is how I found to make it work.  Can you send your recommended settings. Maybe dinner screen shots? 

Thanks and 73 
Mike,  AE8U



Sent from my T-Mobile 4G LTE Device


-------- Original message --------
From: neil_zampella <neilz@...>
Date: 1/25/20 07:37 (GMT-05:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert error messages

That was in reply to your email and screen caps.

 

Neil, KN3ILZ


locked Logging to DXKeeper Trouble #DXLAB

Dale Drake
 

For some apparent reason, now, when I log a QSO if it's with a station not previously logged, the DXCC prefix and CQ zone are blank and the ITU zone is logged as 0.  As far as I can remember I made to changes to JTAlert settings that would cause this to start happening. I tried uninstalling and reinstalling JTAlert and DXKeeper but the problem persists.  JTAlert version 2.11.5 , WSJTX version 2.1.2 and DXKeeper version 1541.

Any ideas of what is causing this and how to fix it?
--
Dale, AA1QD


locked JTAlert V2.15.18 - Log4OM V2 Thank You

Nolan - KI5IO
 
Edited

Laurie - VK3AMA,

I want to express my thanks for the hard work from you and your team to get JTAlert adjusted to work with the new Log4OM V2 db structure.

As a member of the Log4OM Alpha Team I've been testing the beta releases and very pleased with the final v2.15.8.  Your configuration notes and
screen clips are concise and clear for easy use by all OMs.

Again ... thank you very much.

73 - Nolan K.  -  KI5IO


locked Re: JTAlert error messages

neil_zampella
 

That was in reply to your email and screen caps.

 

Neil, KN3ILZ


locked Re: QSO Not Logged! Log4OM v2

g4iua.uk@...
 

All good!  I'm embarrassed to admit that I didn't see the 'enable V2' at the top of the logging select window.  User error!  Everything is now on the latest versions (Log4OM and JTAlert).

Thanks everyone for your help.  Great software, both Log4OM and JTAlert.

Jeff - G4IUA


locked Re: JTAlert error messages

Michael Ernst
 

Bill G4WJS,

I normally read the messages on my cell phone, a Galaxy Note 8. I use the email client on the phone.  Your message came across on my phone with the message you replied to, but his did not.  Since yours did, I fo not feel like it is my email client.  I am not sure why his came across with no reference to anything. 

73,
Mike,  AE8U



Sent from my T-Mobile 4G LTE Device


-------- Original message --------
From: g4wjs <bill.8@...>
Date: 1/25/20 05:12 (GMT-05:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert error messages

On 25/01/2020 05:50, Michael Ernst wrote:
> Neil, KN3ILZ,
>
> You should either include the message you are replying to, or start
> off with the name and call sign of the person you are replying to.
>
> Your email makes no sense otherwise and thus is not helpful to anyone.
>
> 73,
> Mine. AE8U

Mine,

that is not correct. Neil's message was in reply to a previous message
from Bill, KC8WSM: https://hamapps.groups.io/g/Support/message/27405 .
The messages should be grouped in a thread by your email client, if not
then you need to get a better email client, or if you are viewing on the
Groups.io web client then they appear like this:
https://hamapps.groups.io/g/Support/topic/jtalert_error_messages/70074099?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,70074099
when listed in the "Topic" reader.



--
73
Bill
G4WJS.




locked Re: JTAlert error messages

g4wjs
 

On 25/01/2020 05:50, Michael Ernst wrote:
Neil, KN3ILZ,

You should either include the message you are replying to, or start off with the name and call sign of the person you are replying to.

Your email makes no sense otherwise and thus is not helpful to anyone.

73,
Mine. AE8U
Mine,

that is not correct. Neil's message was in reply to a previous message from Bill, KC8WSM: https://hamapps.groups.io/g/Support/message/27405 . The messages should be grouped in a thread by your email client, if not then you need to get a better email client, or if you are viewing on the Groups.io web client then they appear like this: https://hamapps.groups.io/g/Support/topic/jtalert_error_messages/70074099?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,70074099 when listed in the "Topic" reader.



--
73
Bill
G4WJS.


locked Re: JTAlert error messages

Michael Ernst
 

Neil, KN3ILZ,

You should either include the message you are replying to, or start off with the name and call sign of the person you are replying to. 

Your email makes no sense otherwise and thus is not helpful to anyone. 

73,
Mine. AE8U


Sent from my T-Mobile 4G LTE Device


-------- Original message --------
From: neil_zampella <neilz@...>
Date: 1/24/20 23:58 (GMT-05:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert error messages

Um .. you do realize that you're having WSJT-X  >>> AND <<< JT-Alert try to use the SAME port to send the SAME UDP packet, right?

Turn off the WSJT-X rebroadcast as that setting is 'deprecated' which means it will probably go away in the next version of WSJT-X.  it was only added for N1MM+ before they created a different method of connecting to WSJT-X, and is no longer used by it.

Just keep the JT-Alert rebroadcast if you have to.    In reality, all you should need is to use the HRD V5/V6 logging setup and no rebroadcast is needed.

 

Neil, KN3ILZ


locked Re: QSO Not Logged! Log4OM v2

neil_zampella
 

Try downloading the final release of v2.15.8, which is the latest with all the Log4OM updates.  Then see if this still occurs.

 

Neil, KN3ILZ


locked Re: JTAlert error messages

neil_zampella
 

Um .. you do realize that you're having WSJT-X  >>> AND <<< JT-Alert try to use the SAME port to send the SAME UDP packet, right?

Turn off the WSJT-X rebroadcast as that setting is 'deprecated' which means it will probably go away in the next version of WSJT-X.  it was only added for N1MM+ before they created a different method of connecting to WSJT-X, and is no longer used by it.

Just keep the JT-Alert rebroadcast if you have to.    In reality, all you should need is to use the HRD V5/V6 logging setup and no rebroadcast is needed.

 

Neil, KN3ILZ


locked Re: jtalerts shortcut

HamApps Support (VK3AMA)
 

On 25/01/2020 12:35 pm, richard clare wrote:
When I attempt to start jtalerts along with wsjtx I get a message: [JTAlert started directly (without using a shortcut) or with an incorrect shortcut target parameter. Select the jt mode application that jtalert will use.]  I have set up in settings; applications;autostart the location of wsjtx. Is there something I'm missing? Thanks, Richard wb6ewm
You need to start JTAlert using one of the shortcuts created during the software installation. They may be on your desktop if you enabled that, but they are always created in the "HamApps JTAlert" group of the Windows start menu.

de Laurie VK3AMA


locked jtalerts shortcut

richard clare
 

When I attempt to start jtalerts along with wsjtx I get a message: [JTAlert started directly (without using a shortcut) or with an incorrect shortcut target parameter. Select the jt mode application that jtalert will use.]  I have set up in settings; applications;autostart the location of wsjtx. Is there something I'm missing? Thanks, Richard wb6ewm


locked Re: QSO Not Logged! Log4OM v2

HamApps Support (VK3AMA)
 

On 25/01/2020 10:56 am, g4iua.uk@... wrote:
I've also noticed that using Beta version 1.15.7 Build 0003 under Manage Settings/Logging both Log4OM V1 and V2 are shown.  V1 is BOLD and V2 is not and cannot be selected.
OM,

You are way behind if your running Beta build 0003. The builds, each with Log4OM V2 specific fixes/changes went up to 0006.
All those build are now superseded by the new non-Beta public release, 2.15.8, which you should install else in approx 3 weeks, the Beta expires and becomes non-functional.

V1 showing Bold while V2 doesn't indicates that you have enabled V1 as your logger with JTAlert. If you want to use Log4OM V2 with JTAlert, select the "Log4OM V2" line in the left-hand tree-view and then tick the enable checkbox on the settings view for V2, the entry will then become bold.

JTAlert treat Log4OM V1 and Log4OM V2 as two separate logger applications due to the significant differences in the Log file schemas and config files of the two versions.

de Laurie VK3AMA




locked Re: QSO Not Logged! Log4OM v2

g4iua.uk@...
 
Edited

I've also noticed that using Beta version 1.15.7 Build 0003 under Manage Settings/Logging both Log4OM V1 and V2 are shown.  V1 is BOLD and V2 is not and cannot be selected.


locked Re: Interesting sound issue - Update

John Petrocelli
 

Hello again,

  Here is a screen shot of when this happened just a bit earlier.
  Note the order of 2 particular callsigns in the JTAlert window (5T5PA and then W9TMW which was a reply to me)
  The 5T5PA generated the "CQ" alert sound but the "WA2HIP W9TMW R-09" did not trigger the "Own Call" alert tone.

   Maybe this will help.
   I COMPLETELY understand that the other issue with Log4OM took priority.

73
John - WA2HIP


John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com
On 1/24/2020 10:57 PM, HamApps Support (VK3AMA) wrote:

On 24/01/2020 1:35 pm, John Petrocelli via Groups.Io wrote:
I have been much more vigilant as to the anomaly happening.

I am getting an  even stronger sense that it will happen if "Own Call" is decoded after a "CQ".  The result is, as I stated, that the "CQ" alert sounds but the "Own Call" does not.

Thus it would seem that in this situation, the "CQ" sound preempts the "Own Call" sound.

Note that I also have WSJT-X set to decode at the deepest level, although I doubt that this is a contributing factor.

Thanks again
John - WA2HIP
John,

In all honesty, I have not yet looked at the code, I have been thinking about the issue, but the unexpected release of Log4OM V2 diverted all my energies to getting it supported asap.

Very likely there are a couple of bits to the puzzle, the recent JTAlert changes to improve the speedup of Callsign alerting/displaying which required a change in how quickly JTAlert handles the incoming UDP decodes feed from WSJT-X and the multi-pass decoding performed by WSJT-X, especially since your running with Deep decoding.

Question: When you see this behavior is the Station Calling you on your TX frequency? Is there difference in the alerting depending on where the Calling Station is Tx?

de Laurie, VK3AMA




locked Re: Interesting sound issue - Update

HamApps Support (VK3AMA)
 

On 24/01/2020 1:35 pm, John Petrocelli via Groups.Io wrote:
I have been much more vigilant as to the anomaly happening.

I am getting an  even stronger sense that it will happen if "Own Call" is decoded after a "CQ".  The result is, as I stated, that the "CQ" alert sounds but the "Own Call" does not.

Thus it would seem that in this situation, the "CQ" sound preempts the "Own Call" sound.

Note that I also have WSJT-X set to decode at the deepest level, although I doubt that this is a contributing factor.

Thanks again
John - WA2HIP
John,

In all honesty, I have not yet looked at the code, I have been thinking about the issue, but the unexpected release of Log4OM V2 diverted all my energies to getting it supported asap.

Very likely there are a couple of bits to the puzzle, the recent JTAlert changes to improve the speedup of Callsign alerting/displaying which required a change in how quickly JTAlert handles the incoming UDP decodes feed from WSJT-X and the multi-pass decoding performed by WSJT-X, especially since your running with Deep decoding.

Question: When you see this behavior is the Station Calling you on your TX frequency? Is there difference in the alerting depending on where the Calling Station is Tx?

de Laurie, VK3AMA



locked Re: Double click on spot - with JTDX

HamApps Support (VK3AMA)
 

On 25/01/2020 9:00 am, Doug Munday wrote:
Single click on decode does forward the call to JTDX, IF the decode is a CQ
This is what I am seeing in testing. The JTAlert code to send the appropriate instruction to JTDX or WSJT-X doesn't change with the decode type. WSJT-X accepts the JTAlert commands regardless, JTDX only actions the command if it is for a CQ decode.

This is not a JTAlert defect, but either a feature/defect within JTDX. This has been like this for quite some time (many months I believe). I don't know which JTDX version first introduced this behavior

de Laurie VK3AMA