Date   

locked JtAlert Not Logging to HRD or N3jhp #FT8

Ken Hendrickson
 

JTAlertx has quick logging to my HRD logbook. I installed the latest version 2.11.5. I have the latest Wsjt-x and HRD. I get this message when trying to log to HRD. This message repeats itself over and over again until I close JTAlertx

FAILURE : QSO Not logged!
 
ERROR Message : HRD : Unsupported ODBC DSN
 
Callsign : KI0E
Frequency : 18.101551 MHz

Logged Mode : FT8
 
This message has been placed in the Windows clipboard.
 
HRD TCP Logging command result returned =>

Ken Hendrickson - w6bzy
 
 


locked Wanted Call

Don Farrar
 

I have am using JTAlertX v2.11.3 and N3FJP ACLog v6.2
JTAlert is announcing that VE1PZ in Grid FN85 as a wanted grid.
If I check ACLog it shows I have worked FN85 many times and it is confirmed by LoTW
Did a Scan Log and Rebuild and get the same results.
It also shows that I have worked 92 Grids on 6 meters (Not including FN85) and a check with ACLog shows 379 on 6 (Including FN85)
JTAlert and ACLog seem to be logging properly.
When the band is open like yesterday, there is little time to double check each Grid Wanted Alert.
Is there a way to update JTAlert so it recognizes the Grids I have worked on 6 meters?

Thanks,  73,

Don VA3ZV


locked Re: How do you disable 4-meter spots on hamspots.net?

HamApps Support (VK3AMA)
 

On 22/06/2018 3:07 AM, Don Hill AA5AU wrote:
Is there a way of disabling 70 MHz spots on hamspots.net? There does not appear to be a check box for 4 meters. Since 4 meters is not available here, I'd prefer not to see them.

Thanks,
Don AA5AU
Don,

4m spots have only just been turned on so that the database gets some data. The ability to filter these spots is coming later today hopefully.

de Laurie VK3AMA


locked Re: Machine.Learning.Analomolous.100%

HamApps Support (VK3AMA)
 

On 22/06/2018 1:30 AM, philp51@... wrote:
My Malwarebytes keeps flagging Machine.Learning.Analomolous.100% as malware. If  I remove it, the latest version of JT-Alert won't run. Is this really malware? Tnx...Phil NS2R
Which file is being flagged?

de Laurie VK3AMA


locked Re: Not passing info to DXview until after QSO

HamApps Support (VK3AMA)
 

On 22/06/2018 1:41 AM, w7psk wrote:
Not sure what setting I messed up, but JTAlert isnt passing over to DXview until QSO is complete.
PS I did send the support Email

Scotty W7PSK
JTAlert Settings, "Applications -> DXLab Suite" section. Enable the DXView lookup.

de Laurie VK3AMA


locked Re: Decodes History Comments and Question

David - AK2L
 

Sounds great and I look forward to using it.

73, David


locked How do you disable 4-meter spots on hamspots.net?

Don Hill AA5AU
 

Is there a way of disabling 70 MHz spots on hamspots.net? There does not appear to be a check box for 4 meters. Since 4 meters is not available here, I'd prefer not to see them.

Thanks,
Don AA5AU


locked Not passing info to DXview until after QSO

Rick W7PSK
 
Edited

Not sure what setting I messed up, but JTAlert isnt passing over to DXview until QSO is complete.
PS I did send the support Email

Scotty W7PSK


locked Re: Machine.Learning.Analomolous.100%

Michael Black
 

Far too many vendors flag JTAlert as a problem when it is not on every new version until they whitelist it.
Just create an exception in Malwarebytes for the program folder.

de Mike W9MDB




On Thursday, June 21, 2018, 10:30:38 AM CDT, philp51@... <philp51@...> wrote:


My Malwarebytes keeps flagging Machine.Learning.Analomolous.100% as malware. If  I remove it, the latest version of JT-Alert won't run. Is this really malware? Tnx...Phil NS2R


locked Machine.Learning.Analomolous.100%

philp51
 

My Malwarebytes keeps flagging Machine.Learning.Analomolous.100% as malware. If  I remove it, the latest version of JT-Alert won't run. Is this really malware? Tnx...Phil NS2R


locked Feature request - callsign check

@OE3NHW
 

Hi, would be so nice for me...I have ONE logbook 44.000 qsos from Peru OA6Q + OA6/OE3NHW + OA4/OE3NHW and 4000 qsos from Austria OE3NHW. I use this way to know if we really worked before. On HF I workred abt. 4000 qsos from Peru in Mode FT8 (Oct.1st 2017- Feb. 2018). So it happens  many times iAlertX tells me "Bt4" but that was from Peru and not from OE. I suppose it wouldn't be so much difficult to check my current call/country with the log book and let pass through only if equal. On 6m its not a problem as I didn't work Europe out from Peru.
Thanks for reading my point and 73


locked Re: Decodes History Comments and Question

HamApps Support (VK3AMA)
 

On 21/06/2018 8:42 AM, David wrote:
Thank you Laurie for JTAlertX.  WSJT-X is incomplete without it.

My operating has been exclusively with FT8.  Since an FT8 QSO can consume a minute or more, alerts in the main window are often deleted before I can try to contact the next target.  Recently I have been using the Decodes History window as it gives me a chance to see what I may have missed.

Is there a way, or are there any plans to allow an entry in the Decodes History to be used for the next WSJT QSO?  Currently I am entering the call sign and grid manually into WSJT.

73 de David, AK2L
Dave,

In the past the Decodes History was coded to accept a double-click to setup a WSJT-X QSO, similar to the double-click (now single-click since 2.11.4) of the Callsign slots on the main JTAlert display. That code was never reliable and didn't get past the Beta Team testing so was disabled.

There have been some significant changes in the code since then, including the use of a new compiler version for creating JTAlert. Your question prompted me to revisited the old code and run some tests. I
t looked promising with no adverse effects. The decodes History allowed initiating a WSJT-X QSO even when the decode was a couple of hours old (provided the decodes have not been cleared in WSJT-X).

I will be sending a new JTAlert build to the Beta Testers later today. If they have a trouble-free experience with the changes, I will release a new public build with the feature
enabled (i.e.. single-click in Decodes History to initiate a WSJT-X QSO).

de Laurie VK3AMA


locked Re: Differentiating Needed State or Country and Calling CQ or not

Stephen - K6SJT
 

Thank you Laurie, that works


locked Re: Differentiating Needed State or Country and Calling CQ or not

HamApps Support (VK3AMA)
 

On 21/06/2018 8:59 AM:

Question on setting Alerts –

 

If someone calls CQ and I haven’t worked them before on a Band, the Alert is GREEN

 

I also have alerts set for specific States on specific Bands so they show up as Yellow, but of course wanted States show up yellow whether or not they’re calling CQ.

 

For the last couple days I’ve been working 6M 10M and 12M and I’m sometimes getting YELLOW alerts for 6 or more States, but of course some are in the middle of a QSO and others are calling CQ.

 

Is there a method to set an alert that allows a quick look to see those wanted States (YELLOW) that are actually calling CQ - a hybrid of Wanted State and Calling CQ that shows up as a unique color.

 

Thanks -


OM,

Easy, turn on the CQ indicator character and or border. You can also differentiate between standard and directional CQs. See the JTAlert Settings, Alerts -> CQ and QRZ section. Look under the "Options (for WSJT-X ... group). Yes, I know that group title needs changing.

Alternatively, you could enable the CQ only Alert Filter (see the Alerts -> Filters title-bar menu). With the CQ only filter enabled, all Callsigns displayed in JTAlert, regardless of the alert color shown, will be a CQ.

de Laurie VK3AMA
 


locked Differentiating Needed State or Country and Calling CQ or not

Stephen - K6SJT
 

Question on setting Alerts –

 

If someone calls CQ and I haven’t worked them before on a Band, the Alert is GREEN

 

I also have alerts set for specific States on specific Bands so they show up as Yellow, but of course wanted States show up yellow whether or not they’re calling CQ.

 

For the last couple days I’ve been working 6M 10M and 12M and I’m sometimes getting YELLOW alerts for 6 or more States, but of course some are in the middle of a QSO and others are calling CQ.

 

Is there a method to set an alert that allows a quick look to see those wanted States (YELLOW) that are actually calling CQ - a hybrid of Wanted State and Calling CQ that shows up as a unique color.

 

Thanks -


locked Decodes History Comments and Question

David - AK2L
 

Thank you Laurie for JTAlertX.  WSJT-X is incomplete without it.

My operating has been exclusively with FT8.  Since an FT8 QSO can consume a minute or more, alerts in the main window are often deleted before I can try to contact the next target.  Recently I have been using the Decodes History window as it gives me a chance to see what I may have missed.

Is there a way, or are there any plans to allow an entry in the Decodes History to be used for the next WSJT QSO?  Currently I am entering the call sign and grid manually into WSJT.

73 de David, AK2L


locked JTAlert 2.11.5

Henryk Skalimowski
 

I downloaded ver 2.11.15 - works OK. Thank you so much.

Win XP ;-)

Henryk
SP4L

--------------------------------------------------
Od: "HamApps Support (VK3AMA)" <vk3ama.ham.apps@gmail.com>
Data: 19 czerwca 2018 23:39
Do: <Support@HamApps.groups.io>
Temat: [HamApps] #Announcement #NewRelease : JTAlert 2.11.5 is available for download - Defect Fixes (still with XP/Vista support)

While I previously announced that 2.11.4 will be the last release for
XP/Vista, this 2.11.5 release contains bug fixes so I have extended the
XP/Vista support to this version as well.

Visit https://HamApps.com <https://HamApps.com/#jtalert> for the
download link and upgrade/install instructions.

Release Notes...
2.11.5 (20-JUN-2018)

Fixes:
- Help file missing content (2.11.4 defect).
- Some users (WinXP) not able to download version data (2.11.4
defect).
de Laurie VK3AMA


locked Re: JTAlert 2.11.4 Fixed Help File available

Bill Hanrahan <wjhanrahan@...>
 

I just finished rebooting per Mike's suggestion and it worked.

Thank you both.

Bill  W1WH


On Tue, Jun 19, 2018 at 6:30 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 20/06/2018 8:22 AM, Bill Hanrahan wrote:
Laurie, I'm receiving an error when I try to install 2.11.5.  It is stating that it is attempting to remain a file and returns error code 183. 

Bill W1WH
Restart your PC to ensure any file locks are removed. Then run the setup.

de Laurie VK3AMA


locked Re: JTAlert 2.11.4 Fixed Help File available

HamApps Support (VK3AMA)
 

On 20/06/2018 8:22 AM, Bill Hanrahan wrote:
Laurie, I'm receiving an error when I try to install 2.11.5.  It is stating that it is attempting to remain a file and returns error code 183. 

Bill W1WH
Restart your PC to ensure any file locks are removed. Then run the setup.

de Laurie VK3AMA


locked Re: JTAlert 2.11.4 Fixed Help File available

Michael Black
 

Reboot and try again.

de Mike W9MDB




On Tuesday, June 19, 2018, 5:22:59 PM CDT, Bill Hanrahan <wjhanrahan@...> wrote:


Laurie, I'm receiving an error when I try to install 2.11.5.  It is stating that it is attempting to remain a file and returns error code 183. 

Bill W1WH

17001 - 17020 of 37666