Date   

locked Re: Scan log

Steve, N3SL
 

BINGO!

As I mentioned in a different email, the QSO examples were from long ago - 1990s.  That was a Colorado QTH, and on the "homeQTH" section, only Iowa was selected!  I presume I did that when setting up JTAlert vs it being a default.  But matters not...  That (appears to have) fixed the situation!  At least the scan/rebuild now puts Panama and The Gambia in the worked column.

Thanks, Laurie!

On Sun, Jan 5, 2020 at 10:03 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 6/01/2020 12:27 pm, Steve, N3SL wrote:
Exactly what is being scanned (using DXLab here) when this is invoked?  I'm seeing incorrect alerts repeatedly - as in day-to-day.  I only have DXCC alerts checked (zones, prefixes, continents, etc - all UNchecked).  

For example: 20m FT8 today alerted on HP and C5 --> "new" DXCC, "new" prefix  Neither is true.  My log has 4 confirmed HP digital Qs on 20, and 2 C5 Qs.  Yet a scan/rebuild leaves both Panama and The Gambia in the "unworked" window for 20m  (settings are individual bands/any digital mode).

What am I missing/doing wrong?  And I do wait at least a minute before starting a scan once I've chosen that option....

Thanks for any insight or education!

73,
Steve
Steve,

Do you have any DXKeeper homeQTH selections enabled for the DXCC Alert? If you do and the Log QSOs don't have a homeQTH recorded or have a homeQTH not enabled for that Alert than they will be excluded from the scan.

Have a look under the "Logging -> DXLab DXKeeper -> homeQTH selections" section of the Settings window.

Let me know if this is the cause.

de Laurie VK3AMA


locked Re: US State count equals DXCC count

vk5kx
 

Well that didn’t go to well for 1st post J

I noticed about 4-5 updates ago that the ‘US State’ #count shows the same value as the ‘DXCC’ #count.

All the worked & confirmed ‘ticks’ are present and accounted for J

Cheers


Peter/vk5kx


locked Re: 2.15.6 Needed State Alert Issue

Tom NS8K
 

Laurie,
Nice job.  I did the re-install and there is now a male (as well as female) version of Michigan.  The male version is an improvement over the female version that used to get installed whether you selected Male or Female.

I agree, they do all sound pretty good.  Especially when you consider all 81 files total a little over 3 Meg.  That's quite amazing actually.

73 es tnx,
Tom


locked Re: 2.15.6 Needed State Alert Issue

HamApps Support (VK3AMA)
 

On 6/01/2020 10:50 am, Tom NS8K wrote:
By the way, the Michigan announcement is difficult to understand and there is no male version of it, only female.
Tom,

The MI.wav file for both Male and Female are in the installer file, I just now did fresh installs and it definitely gets installed (typically to C:\ProgramData\HamApps\Sounds\ ). You may want to try a new install. There should be 81 .wav files in that directory.

I agree the Female MI announcement is not very good. There is a limit to what can be done with computer generated voice files. They are still pretty good for computer generated IMO.

de Laurie VK3AMA




locked Re: Scan log

HamApps Support (VK3AMA)
 

On 6/01/2020 12:27 pm, Steve, N3SL wrote:
Exactly what is being scanned (using DXLab here) when this is invoked?  I'm seeing incorrect alerts repeatedly - as in day-to-day.  I only have DXCC alerts checked (zones, prefixes, continents, etc - all UNchecked).  

For example: 20m FT8 today alerted on HP and C5 --> "new" DXCC, "new" prefix  Neither is true.  My log has 4 confirmed HP digital Qs on 20, and 2 C5 Qs.  Yet a scan/rebuild leaves both Panama and The Gambia in the "unworked" window for 20m  (settings are individual bands/any digital mode).

What am I missing/doing wrong?  And I do wait at least a minute before starting a scan once I've chosen that option....

Thanks for any insight or education!

73,
Steve
Steve,

Do you have any DXKeeper homeQTH selections enabled for the DXCC Alert? If you do and the Log QSOs don't have a homeQTH recorded or have a homeQTH not enabled for that Alert than they will be excluded from the scan.

Have a look under the "Logging -> DXLab DXKeeper -> homeQTH selections" section of the Settings window.

Let me know if this is the cause.

de Laurie VK3AMA


locked Re: 2.15.6 Needed State Alert VIRUS Issue

neil_zampella
 

There is nothing for Laurie to fix.

You need to exclude the HAMAPPS directory from your antivirus.  

Neil, KN3ILZ


locked Re: Scan log

HamApps Support (VK3AMA)
 

On 6/01/2020 12:27 pm, Steve, N3SL wrote:
Exactly what is being scanned (using DXLab here) when this is invoked?  I'm seeing incorrect alerts repeatedly - as in day-to-day.  I only have DXCC alerts checked (zones, prefixes, continents, etc - all UNchecked).  

For example: 20m FT8 today alerted on HP and C5 --> "new" DXCC, "new" prefix  Neither is true.  My log has 4 confirmed HP digital Qs on 20, and 2 C5 Qs.  Yet a scan/rebuild leaves both Panama and The Gambia in the "unworked" window for 20m  (settings are individual bands/any digital mode).

What am I missing/doing wrong?  And I do wait at least a minute before starting a scan once I've chosen that option....

Thanks for any insight or education!

73,
Steve
Steve,

Exactly what is being scanned is dependent on the QSL requirements you have set for the DXCC alert.

How are the QSOs in question confirmed in your DXKeeper log?

If you certain your log has QSOs matching your DXCC scan settings yet the dxccs in question are not being removed from the Wanted Lists after the scan, I will need to see your JTAlert config file and your DXKeeper log file. Do the following...
  1. Please use the "Help" (or "? ") -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files. Include a note in that request of the Callsigns being incorrectly alerted (one HP and one C5 will be sufficient.
  2. Send me direct (not bivia this group) a copy of your zipped log file.

de Laurie VK3AMA



locked No Sound

sv1hep@...
 

Hi
I'm switch from ver 2.15.0 to 2.15.6
I have try any combination without success to bring the sound back. Restart JTAlert- reinstall - reboot - etc.
The sound has been lost in the deep space.
My PC has the default sound card. HD VIA Audio. My IC-7300 use the USB IN & OUT. Not any mixing sounds on this setup to bother other station with blink and blonk at transmitting time.
The JTAlert refuse to play any kind of sound. Also not showing in windows sound devices the JTAlert Plugins Helper like before.
Any advice to bring back the sound will be appreciated.
Thank you
Chris


locked Re: 2.15.6 Needed State Alert VIRUS Issue

Michael K. Boyea
 

Thanks for a great program, I'm stuck using older version due to a virus or non-virus indication which my computers will not allow me to install.
I tried to override and program installed.  But, once rebooted, it wiped out the exe file and informed me of a virus and deleted files.

I hope you have time in your schedule to look into this and find a fix as version 2.13.10 does not seem to have the problem.
Tnx agn, and 73, Mike KE4KMG


locked US State count equals DXCC count

vk5kx
 

Hi,


locked Scan log

Steve, N3SL
 

Laurie,

Exactly what is being scanned (using DXLab here) when this is invoked?  I'm seeing incorrect alerts repeatedly - as in day-to-day.  I only have DXCC alerts checked (zones, prefixes, continents, etc - all UNchecked).  

For example: 20m FT8 today alerted on HP and C5 --> "new" DXCC, "new" prefix  Neither is true.  My log has 4 confirmed HP digital Qs on 20, and 2 C5 Qs.  Yet a scan/rebuild leaves both Panama and The Gambia in the "unworked" window for 20m  (settings are individual bands/any digital mode).

What am I missing/doing wrong?  And I do wait at least a minute before starting a scan once I've chosen that option....

Thanks for any insight or education!

73,
Steve


locked Re: 2.15.6 Needed State Alert Issue

Tom NS8K
 

Laurie,

Man, are you quick! I use individual state.  I figured timing also especially with how you have sped up things.  By the way, the Michigan announcement is difficult to understand and there is no male version of it, only female.

JTAlert, fantastic and getting better all the time!

73 es tnx,

Tom


locked Re: Date error in ALL.TXT

Dave Garber
 

the only thing I notice is there is no frequency for the 2020 dates,    cat error maybe???
Dave Garber
VE3WEJ / VE3IE


On Fri, Jan 3, 2020 at 2:02 PM <marsip@...> wrote:
Sorry, my fault. Nothing wrong. I misinterpreted the values.


locked Re: Second question - grayed out Log fields

HamApps Support (VK3AMA)
 

On 6/01/2020 5:05 am, Rick wrote:
Another problem is View>Show log fields  is grayed out. Again, a setting
somewhere...

Thanks again, 73 Rick W3BI
The menu to display the Log fields is deliberately disabled when you running JTAlert without an enabled logger. That is the JTAlert titlebar status text is showing "NO Log".

Any data in the log fields area would not be logged if running without a Log so there is no point is making it visible.

de Laurie VK3AMA


locked Re: Old question - No State abbreviation.

HamApps Support (VK3AMA)
 

On 6/01/2020 5:57 am, Martin Blaise wrote:
This is probably an old question but anyway why do some call signs show up without the two letter state designation?

JTAlert determines the 2 character State abbreviation via a Callsign database lookup. This only applies to US Callsigns. If the Callsign is not showing the State code then likely it is a relatively new Callsign that was not present in the FCC database the last time the Callsign database was updated (this happens approx every 2 to 3 weeks).

Another possibility is your running an old JTAlert version (prior to 2.14.4) and don't have the Callsign database installed. Starting with JTAlert 2.14.4 the Callsign database is no longer optional and is now included with the JTAlert installer.

de Laurie VK3AMA


locked Re: 2.15.6 Needed State Alert Issue

HamApps Support (VK3AMA)
 

On 6/01/2020 7:49 am, Tom NS8K wrote:
I've been experiencing wanted states not being announced with version 2.15.6.  Here are the circumstances.

Mode FT8, Decode set to Normal or Deep (AP setting doesn't matter).  When receiving, calls can appear in JTAlert in little bursts or groups.  I know this is normal and caused by the Normal or Deep decode setting in WSJT-X.

The problem is that wanted states after the first group of decoded calls are often not announced although they are of the proper color in the JTAlert display.  I went back to 2.15.3 and did not see this behavior.  2.15.5 also seems to work correctly.  FT4 works fine in all versions.  If I set Decode to Fast in WSJT-X, all versions seem to work just fine too.

This problem doesn't require busy band conditions.  It can happen with as few as 2 wanted states.  When there are wanted states, they are announced elegantly from the end of the JTAlert display back to the beginning (accommodating duplicate states) in the working versions.  In 2.15.6 the order appears "jumbled" when it is in error.

Running updated Windows 10 on a moderate computer.  WSJT-X is ver 2.1.2.  Rig is IC-7300.  Log is Log4OM.  Everything else is working beautifully!

Oops, I stand corrected.  With a little more testing, FT4 also exhibits this same behavior when Decode is set to Normal or Deep.

73 es tnx,
Tom - NS8K
Tom,

Thanks for the report. This sounds like a timing issue, I will investigate.

Thanks for the update confirming that it also occurs for FT4, as I was scratching my head trying to come up with a possible mode dependent (FT8 only) cause.

Question, do you use individual State announcements or a single generic "New State" announcement?

de Laurie VK3AMA


locked Re: Message dates

HamApps Support (VK3AMA)
 

On 6/01/2020 1:24 am, Bill - AA4M wrote:
I just received a message through JTAlert and I responded.  Then I noticed both were dated 2019-13-05 . . . the 13th month of 2019!  An easy fix, I'm sure.

73, Bill - AA4M
Bill,

Tnx for the report. I can confirm the defect.

The error is due to a badly coded 3rd party library I was using for converting unix epoch timestamps to human readable date/time strings. I abandoned that code and wrote my own.

de Laurie VK3AMA



locked 2.15.6 Needed State Alert Issue

Tom NS8K
 
Edited

I've been experiencing wanted states not being announced with version 2.15.6.  Here are the circumstances.

Mode FT8, Decode set to Normal or Deep (AP setting doesn't matter).  When receiving, calls can appear in JTAlert in little bursts or groups.  I know this is normal and caused by the Normal or Deep decode setting in WSJT-X.

The problem is that wanted states after the first group of decoded calls are often not announced although they are of the proper color in the JTAlert display.  I went back to 2.15.3 and did not see this behavior.  2.15.5 also seems to work correctly.  FT4 works fine in all versions.  If I set Decode to Fast in WSJT-X, all versions seem to work just fine too.

This problem doesn't require busy band conditions.  It can happen with as few as 2 wanted states.  When there are wanted states, they are announced elegantly from the end of the JTAlert display back to the beginning (accommodating duplicate states) in the working versions.  In 2.15.6 the order appears "jumbled" when it is in error.

Running updated Windows 10 on a moderate computer.  WSJT-X is ver 2.1.2.  Rig is IC-7300.  Log is Log4OM.  Everything else is working beautifully!

Oops, I stand corrected.  With a little more testing, FT4 also exhibits this same behavior when Decode is set to Normal or Deep.

73 es tnx,
Tom - NS8K


locked Old question

Martin Blaise
 

This is probably an old question but anyway why do some call signs show up without the two letter state designation?


locked Second question

Rick
 

Another problem is View>Show log fields  is grayed out. Again, a setting
somewhere...

Thanks again, 73 Rick W3BI


--


Only losers need rally caps.