I've been shrinking the band activity columns that I don't use, thus it's about half the size for just FT4&8. Would also like to cancel out the bands I can't use.


Sent from Xfinity Connect Application

On 25/08/2019 6:05 am, wbr via Groups.Io wrote:

Hello, I'm a beginner and would like to know where the hamapps callsign database is installed on my computer.
I've searched but am not able find.  I've also tried to catch the path while program was installing but little window
goes by too fast.
Is it important to know where the call sign database is installed? probably not, but I'd still like to know.  Thanks
73, WF4R

"C:\ProgramData\HamApps\Databases\fcc_lotw_eqsl.sqlite"

I advise against trying to modify the data in the file.
If there is an error in the data report it here so it can be corrected for all users.

de Laurie VK3AMA

On 24/08/2019 11:07 pm, Vladimir Doroshenko wrote:

Hello!

Please help, not work scan Wanted Continent and Wanted Prefix. In scan
results I see Continents Needed : 7 and Prefix Not Needed : 0 in all
bands and modes:

[Prefixes : FT8 Modes Only]
Band : ANY - Prefix Not Needed : 0 (Previous : 0)
Band : 160 - Prefix Not Needed : 0 (Previous : 0)
Band : 80 - Prefix Not Needed : 0 (Previous : 0)
Band : 60 - Prefix Not Needed : 0 (Previous : 0)
Band : 40 - Prefix Not Needed : 0 (Previous : 0)
Band : 30 - Prefix Not Needed : 0 (Previous : 0)
Band : 20 - Prefix Not Needed : 0 (Previous : 0)
Band : 17 - Prefix Not Needed : 0 (Previous : 0)
Band : 15 - Prefix Not Needed : 0 (Previous : 0)
Band : 12 - Prefix Not Needed : 0 (Previous : 0)
Band : 10 - Prefix Not Needed : 0 (Previous : 0)
Band : 6 - Prefix Not Needed : 0 (Previous : 0)
Band : 2 - Prefix Not Needed : 0 (Previous : 0)


Other scans work correctly. For example:

[Grids : FT8 Modes Only]
Band : ANY - Grids Not Needed : 893 (Previous : 893)
Band : 160 - Grids Not Needed : 157 (Previous : 157)
Band : 80 - Grids Not Needed : 534 (Previous : 534)
Band : 60 - Grids Not Needed : 0 (Previous : 0)
Band : 40 - Grids Not Needed : 387 (Previous : 387)
Band : 30 - Grids Not Needed : 545 (Previous : 545)
Band : 20 - Grids Not Needed : 421 (Previous : 421)
Band : 17 - Grids Not Needed : 223 (Previous : 223)
Band : 15 - Grids Not Needed : 142 (Previous : 142)
Band : 12 - Grids Not Needed : 58 (Previous : 58)
Band : 10 - Grids Not Needed : 71 (Previous : 71)
Band : 6 - Grids Not Needed : 0 (Previous : 0)
Band : 2 - Grids Not Needed : 5 (Previous : 5)

ADIF file from AAlog 3.9

Thank you!

73!
UW5EKD
Vladimir

Vladimir,

Very likely that for the scans affected your adif log file doesn't contain the required information. Does it contain the <CONT> and <PFX> fields?

Please send me direct (not via this group) a copy of your adif file.

de Laurie VK3AMA

Was working fine, but after a freeze and reinstall of both WSJT-X and JTALERT 2.14.3, WSJT-X starts and runs fine. When I start Jtalert, I get the message: Windows cannot access the specified device, path or file. You may not have appropriate permissions to access them. I suspect a path problem, but don't know how to correct it. BTW the Windows is 10 64bit.
Dave KR4LU

Dave,

Sounds like the shortcut your using to start JTAlert is referencing an incorrect path or file. Is this a user-created shortcut or one automatically created during the JTAlert install? If the later, than very likely you virus protection may have removed the JTAlert.exe file.

Please post an image of the offending error window (pse don't post your entire desktop, just the error window is needed).

de Laurie VK3AMA

Speaking of the "!", it might be nice if it were in red to make it more noticeable.

Ed, K0KC

Ed,

While possible, coloring is unlikely to be implemented. An alternative is to use the Alternate Build of JTAlert which does away with this abbreviation,  instead using plain text, "(Updates)".

de Laurie VK3AMA

Hi Laurie,

Russian JT9 activity w/e.

73
Bill
G4WJS.

RR73

Is there a way to not show modes in which I am not interested? For example, if I'm running FT8, I have no real interest in say JT65. With the recent addition of the FT4 columns, the display is now using up a lot screen real estate - a very valuable commodity in my shack hihi.
Kind Regards,
Dennis W7DRW

Dennis,

It is on the todo list, added by myself when I first coded the F4 support as I knew the user request would be coming ;-)

Until it is implemented, I suggest you don't have the Band Activity window open and rely on a periodic mouse-hover over the Band Activity status to temporarily show the popup window.

de Laurie VK3AMA

Does anyone know the reason for the sudden increase?

de Laurie VK3AMA

Hi Laurie,

Russian JT9 activity w/e.

73
Bill
G4WJS.

--
73
Bill
G4WJS.

I have noticed over the last 2 days, a significant increase in JT9 activity as shown in the JTAlert Band Activity popup and on HamSpots and PSKReporter. Is there a JT9 specific contest on at the moment?

As I type this message 19:30 utc, the daily peak in PSKReporter activity, the top 3 reported modes (last 2 hours) on PSKReporter are FT8, FT4, JT9.
   

Does anyone know the reason for the sudden increase?

de Laurie VK3AMA

What does the (!) mean on the title bar of JT Alert?

It indicates an Update is available, either JTAlert or the Callsigns database if installed.

BTW, the "!" symbol is an exclamation mark, not an apostrophe.

de Laurie VK3AMA

JTAlert title line shows 2.14.3 and has exclamation mark at end
When I use settings / check for updates it showsI am using 2.14.2
and vers 2.14.3 is available.
I have tried to attach picture showing this
TVM
Barry

Barry,

Looks like the file holding version information on the current installed version did not get updated during the update.

Simply rerunning the JTAlert setup again should fix it, there is no need to uninstall first, the setup can be run multiple times without any ill effect.

de Laurie VK3AMA

Was working fine, but after a freeze and reinstall of both WSJT-X and JTALERT 2.14.3, WSJT-X starts and runs fine. When I start Jtalert, I get the message: Windows cannot access the specified device, path or file. You may not have appropriate permissions to access them. I suspect a path problem, but don't know how to correct it. BTW the Windows is 10 64bit.
Dave KR4LU

Updates available 

What does the (!) mean on the title bar of JT Alert? Running JT Alert 2.13.10 and WSIT-X 2.1.0. I am not seeing many DX callsigns in the grid like I used to,  mostly USA/VE. 

In addition to the work around I recently posted I have used this one and it works just fine.  Somewhat of a chore if you have a great number of confirmed LOTW QSOs.  Hopefully. the HRD team will get their app fixed.

73
Al
W1JHU

On Sat, Aug 24, 2019 at 08:27 PM, Barry wrote:

I agree with Ron
I use HRD5.0 and this works 100%
GL de Barry

For now the easy work around to show match(verified) in HRD is two steps:

1) You must go into the Logbook, "Tools", "Configure", "Modes" and add Mode=FT4 and ADIF=FT4 for your contacts to be shown as FT4 in LOTW ... (Once the FT4 contacts are matched in LOTW, they are confirmed contacts, but will not show in HRD LOTW downloads and subsequently in a JTA scan)

Note Added: Under 'logging' in JTA do not select "Log FT4 as ADIF 3.1.0 Compliant Mode=MFSK, Submode=FT4 HRD is not yet ADIF 3.1.0 Compliant ...

2) The updating of HRD for confirmations has to be done manually (a work around) ---- From the shown tabs in the of ALE window (Show:Tabs, LOTW) select LOTW, Under 'Rcvd.' select 'Verified(Match)' for each verified contact.

73
Ron, W3RJW

Please let me explain that item 1 was the only change I made in HRD5.0 
and no other changes were needed to do correct upload and verified download.
cheers de
Barry

I'm fairly sure you should NOT change anything in TQSL .. it is properly setup for FT4 and will store FT4 QSOs on LoTW.     The latest TQSL configuration file has the correct mode conversion for uploads to LOTW.

 

The issue is HRD, and the fact that LoTW exports in the latest ADIF specification, which HRD has not implemented even though Submodes have been part of the ADIF specification for the past six years.    

Again, do not add any mode conversion to LoTW, if and when HRD gets fixed, you may forget that that mode conversion is there, and cause other issues.  It will also cause issues if other MFSK mode protocols are created, and you forget to remove that 'MFSK -> FT4" conversion.

 

Neil, KN3ILZ