Date   

locked Re: Signal report - Assumptions are important

Mark Basel <mb02731@...>
 

Lived the acronyms world of a 2G logistics planner in the AF, It was nuts. Ive seen SIPRnet message traffic that was almost nothing but🤪 glad I XB3'd most of them🥸

On Jun 26, 2021, at 1:45 AM, Laurie, VK3AMA <hamapps.support@vkdxer.com> wrote:



On 26/06/2021 3:40 pm, Jim Cooper wrote:
would you mind defining 'ARO'?

use of acronyms without first defining them
can put many readers at a disadvantage for
understanding your post.

w2jc

[I'm GUESSING it means Amateur Radio Operator]
AROs to me suggests it is coming from some Government department bureaucratic licensing document.

At my local club we are all HAMs, not AROs, which coincidentally has the same number of characters ;-)

While I am proud to call myself a HAM, I do use the phrase "Amateur Radio Operator" when communicating with non-Hams, especially when trying to explain the meaning of my Car registration plates, "VKDXER". I have to explain about Ham (Amateur) Radio, what the "VK" stands for in relation to the thousands of like-minded individuals around the world, and what is "DX" and why I call myself a "DXer". I never have to explain the meaning to another Ham, except for the occasional newly-minted Ham.

de Laurie VK3AMA






locked Re: Unable to rebuild alert database. Just get brief blink of window

chas cartmel
 

The updates tag refers to data downloads and not the alerts database.
Check the website for latest data downloads

73 Charlie

G4EST

www.g4est.me.uk

Stay safe out there

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Gareth, M5KVK
Sent: 26 June 2021 12:08
To: Support@HamApps.groups.io
Subject: [HamApps] Unable to rebuild alert database. Just get brief blink of window

 

I'm running 2.50.2 with WSJT-X v2.3.1 on Windows 10
I've not been on for a while, but when I tried to rebuild the alert database and clicked on "Rebuild All (enabled" all I see is a window blinking once and then disappearing; the main wind freezes for a second or two, and then goes back to normal, and the (updates) tag is still there on the main window header.
I've enabled debug logging but I don't know where the log file is located.

Gareth - M5KVK


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com


locked Re: Unable to rebuild alert database. Just get brief blink of window

Michael Black
 

Sounds like your anti-virus is causing problems create an exception in your antivirus program for The JTAlert program folder and reinstall.


On Jun 26, 2021, at 7:54 AM, Gareth, M5KVK <Gareth.m5kvk@...> wrote:

I'm running 2.50.2 with WSJT-X v2.3.1 on Windows 10
I've not been on for a while, but when I tried to rebuild the alert database and clicked on "Rebuild All (enabled" all I see is a window blinking once and then disappearing; the main wind freezes for a second or two, and then goes back to normal, and the (updates) tag is still there on the main window header.
I've enabled debug logging but I don't know where the log file is located.

Gareth - M5KVK


locked Unable to rebuild alert database. Just get brief blink of window

Gareth, M5KVK
 

I'm running 2.50.2 with WSJT-X v2.3.1 on Windows 10
I've not been on for a while, but when I tried to rebuild the alert database and clicked on "Rebuild All (enabled" all I see is a window blinking once and then disappearing; the main wind freezes for a second or two, and then goes back to normal, and the (updates) tag is still there on the main window header.
I've enabled debug logging but I don't know where the log file is located.

Gareth - M5KVK


locked Re: Signal report - Assumptions are important

Laurie, VK3AMA
 

On 26/06/2021 3:40 pm, Jim Cooper wrote:
would you mind defining 'ARO'?

use of acronyms without first defining them
can put many readers at a disadvantage for
understanding your post.

w2jc

[I'm GUESSING it means Amateur Radio Operator]
AROs to me suggests it is coming from some Government department bureaucratic licensing document.

At my local club we are all HAMs, not AROs, which coincidentally has the same number of characters ;-)

While I am proud to call myself a HAM, I do use the phrase "Amateur Radio Operator" when communicating with non-Hams, especially when trying to explain the meaning of my Car registration plates, "VKDXER". I have to explain about Ham (Amateur) Radio, what the "VK" stands for in relation to the thousands of like-minded individuals around the world, and what is "DX" and why I call myself a "DXer". I never have to explain the meaning to another Ham, except for the occasional newly-minted Ham.

de Laurie VK3AMA


locked Re: Signal report - Assumptions are important

TomK
 

Apologies. I'm not immune to occasionally using acronyms w/o thoroughly weighing their recognizability in a given venue.

 

                ARO … Amateur Radio Operator.

 

It's an older, literal variant, TLA that avoids the demeaning, less intuitive, but more recognizable moniker of "HAM".

By less intuitive, I don’t mean less recognizable.  To wit, “ARO” at least makes literal sense whereas “HAM” does not.

 

<laugh> In case you are asking, "TLA" is the old well-known recursive acronym meaning "Three Letter Acronym".

It is mostly used in jocular wry interchanges making fun of the use of acronyms. Hence the recursive attribution.

 

Hope that answers your question.

TomK 73

 

-----Original Message-----
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Jim Cooper
Sent: Saturday, June 26, 2021 1:41 AM
To: TomK <QSO@...>
Cc: Support@HamApps.groups.io
Subject: Re: [HamApps] Signal report - Assumptions are important

 

On 26 Jun 2021 at 1:14, TomK wrote:

 

> Active AROs

 

would you mind defining 'ARO'?

 

use of acronyms without first defining them can put many readers at a disadvantage for understanding your post.

 

w2jc

 

[I'm GUESSING it means Amateur Radio Operator]

 

 

 

 

 

 


locked Re: Signal report - Assumptions are important

Jim Cooper
 

On 26 Jun 2021 at 1:14, TomK wrote:

Active AROs
would you mind defining 'ARO'?

use of acronyms without first defining them
can put many readers at a disadvantage for
understanding your post.

w2jc

[I'm GUESSING it means Amateur Radio Operator]


locked Re: Signal report - Assumptions are important

TomK
 

To bug reporter:  I think you’ve made a few incorrect assumptions.

If you see the QSO in question in YOUR OWN log, then JTA is uploading correctly.

 

I go to their page on QRZ.COM and check their log to see if was good contact and no it's not there."

Ok, so you’re saying you don’t see YOUR CALL in the log of ANOTHER QRZ user with whom you had a QSO?

I assume you mean in the “Logbook” widget of the other party’s QRZ profile lookup page?

 

To see your call in another QRZ user’s log, then (at least) the following conditions must be met:
Forgive me if some are painfully obvious. I just want to be logically complete.

  1. You & They (obviously) need to be QRZ members who are maintaining active logs.
  2. You & They must BOTH have uploaded the QSO sometime earlier (Nothing is immediate).
  3. The QSO needs to fit in the short time window of the “Logbook” widget (it’s only 15 entries).
    Active AROs log many calls in short periods so a QSO can fall outside the short widget in minutes.
    Adding to time (say) 15-60 mins to allow all DB updates, then your QSO may never show in that widget.
    To wit: If the other ARO is active and logs many QSOs, then by the time the system updates,
    you are already past the bottom of the time window.

 

Re advice that “QRZ not a reliable source”.

That was meant to say “AROs do not necessarily upload to QRZ in real-time.”

As a result, inspecting the other party’s log on QRZ is “is not a reliable source” to verify your QSO upload.

Why would you even want to do that? Your QSO upload is all that matters.

If you see your QSO uploaded,  then everything is working as intended.

What happens with the other party’s upload has nothing to do with JT-Alert or QRZ.

 

All-in-all, QRZ has an outstanding record for database availability when compared to other web logs.

LoTW and the others often have outages on a daily basis. QRZ’s DB has fared much better.

Many perceived JTA and/or QRZ issues are often related to other things like LoTW on the back end.

 

Hope that helps clarify the issue.

TomK / KT1TK / 73

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Friday, June 25, 2021 6:14 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Signal report

 

On 26/06/2021 7:53 am, Bob wrote:

I'm using wsjt-x windows 10 .Not using any contest mode. When I say gong to their page I mean I go to their page on QRZ.COM and check their log to see if was good contact and no it's not there. ALT + Q Will take you there. When I get pop-up to confirm QSO There isn't any signal report for me just the report I gave him/her and the time for Sent and received is the same it looks like not enough time. Is there a setting for increasing time for contact  to complete. Let me know your thoughts. Thank you kb1yxn 


Not everyone uploads their QSOs to QRZ, either manually or in real-time. QRZ is not a reliable source in this regard.
I personally never upload to QRZ.

As for missing signal report and QSO start/stop times, JTAlert will only log what it has received from WSJT-X when you log the QSO. You should check the "Log QSO" window fields before hitting the OK button and adjust any incorrect or missing data.

de Laurie VK3AMA


locked Re: Unable to log to DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

yes the QSO makes it to the DX keeper log but does not automatically upload to Lotw which is why Im running this two
programs to begin with. I have increased the delay to 20 seconds time to log the QSO, still no luck. Guess I can do them manually
but thats a PITA and defeats the reason to use DXKeeper in the first place...


If 20 seconds is insufficient time for DXKeeper to write the QSO to its log file that suggests to me that DXKeeper is hanging while
it tries to upload the QSO to LoTW. My understanding is that DXKeeper doesn't write the QSO to the physical log gile until after it
has completed any online uploads .

+ Not correct; DXKeeper first logs the QSO, and then performs the uploads.

See this response <https://hamapps.groups.io/g/Support/message/35796> from Dave AA6YQ the DXLab author to help isolate the cause of
LoTW upload failing.

+ Mark sent me the errorlog.txt file I created, which revealed that the component DXKeeper employs to upload and download files via
the internet is not properly registered with Windows. This was signified by the presence of the words "See DXKeeper Errorlog.txt" in
the title bar of DXKeeper's Main window.

+ If DXKeeper was unable to register the component because of interference from Windows' access control mechanism, the instructions
I sent Mark should overcome that problem. We'll see...

+ DXKeeper users: if the words "See DXKeeper Errorlog.txt" appear in the title bar of DXKeeper's Main window, then examine the
Configuration window's General tab to see if the "log debugging information" box has been checked; if so, uncheck it, and restart
DXKeeper. If not, then please attach the errorlog.txt file from your DXKeeper folder to an email message, and send the message to me
via

aa6yq (at) ambersoft.com

+ No "pre-approval" from me is required.

73,

Dave, AA6YQ


locked Re: No output devices kusted anong other problems in JTALERT

HamApps Support (VK3AMA)
 

On 26/06/2021 1:03 pm, ed fay wrote:
Maybe I am missing something in JTALERT. It was working fine with WSJT-X. I load it all up and JTALERT acted like a new fresh install. So I entered my callsign. Notice it was not displaying any callsigns then also noticed it listed no sound devices for my computer. I uninstalled it, deleted any files left behind, rebooted, and reinstalled it. Same thing. No decodes and no sound devices listed. Latest versions of both software on Win10.

Sounds like the JTAlertV2.Manager.exe process is being actively interfered with by your PC Protection software.

Non-display of Callsigns and no-listed sound-devices are all symptoms of the Manager process not running or the UDP comms between it and the main JTAlert.exe process are being blocked.

de Laurie VK3AMA


locked Re: No output devices kusted anong other problems in JTALERT

ed fay
 

I did fix the prob temp by going back to the previous version (2.16.17)


locked No output devices kusted anong other problems in JTALERT

ed fay
 

Maybe I am missing something in JTALERT. It was working fine with WSJT-X. I load it all up and JTALERT acted like a new fresh install. So I entered my callsign. Notice it was not displaying any callsigns then also noticed it listed no sound devices for my computer. I uninstalled it, deleted any files left behind, rebooted, and reinstalled it. Same thing. No decodes and no sound devices listed. Latest versions of both software on Win10.


locked Re: Unable to log to DXKeeper

Robert Lorenzini
 

If I have an internet and upload failure I go to dxkeeper and  upload the contact again. NP
I prefer it that way, it's satisfying to put it where it won't go away.
Bob - wd6dod

On 6/25/2021 5:53 PM, HamApps Support (VK3AMA) wrote:
My understanding is that DXKeeper doesn't write the QSO to the physical log file until after it has completed any online uploads .


de Laurie VK3AMA




locked Re: Unable to log to DXKeeper

HamApps Support (VK3AMA)
 

On 26/06/2021 9:44 am, Mark Basel wrote:
yes the QSO makes it to the DX keeper log but does not automatically upload to Lotw which is why Im running this two programs to begin with. I have increased the delay to 20 seconds time to log the QSO, still no luck. Guess I can do them manually but thats a PITA and defeats the reason to use DXKeeper in the first place...

If 20 seconds is insufficient time for DXKeeper to write the QSO to its log file that suggests to me that DXKeeper is hanging while it tries to upload the QSO to LoTW. My understanding is that DXKeeper doesn't write the QSO to the physical log file until after it has completed any online uploads .

See this response from Dave AA6YQ the DXLab author to help isolate the cause of LoTW upload failing.

Until your LoTW upload failings are resolved, turn off the LoTW upload setting in JTAlert, under the Settings window, "Logging -> DXLab DXKeeper" section. This will stop the "Unable to Confirm" popups. Once your LoTW uploads failures are resolved, do a bulk upload of un-submitted to LoTW QSOs from within DXKeeper.

FWIW, I never upload to LoTW (via DXKeeper) with each logged QSO. I simply do a bulk upload at the end-of0the-day, sometimes only once a week. I personally don't understand why some feel the need to upload each QSO in real-time, unless your QSO partner is doing the same, there will not be that instant gratification, you still need to wait for them to upload.

de Laurie VK3AMA



locked Re: Unable to log to DXKeeper

HamApps Support (VK3AMA)
 

On 26/06/2021 9:44 am, Mark Basel wrote:
yes the QSO makes it to the DX keeper log but does not automatically upload to Lotw which is why Im running this two programs to begin with. I have increased the delay to 20 seconds time to log the QSO, still no luck. Guess I can do them manually but thats a PITA and defeats the reason to use DXKeeper in the first place...

If 20 seconds is insufficient time for DXKeeper to write the QSO to its log file that suggests to me that DXKeeper is hanging while it tries to upload the QSO to LoTW. My understanding is that DXKeeper doesn't write the QSO to the physical log gile until after it has completed any online uploads .

See this response from Dave AA6YQ the DXLab author to help isolate the cause of LoTW upload failing.

Until your LoTW upload failings are resolved, turn off the LoTW upload setting in JTAlert, under the Settings window, "Logging -> DXLab DXKeeper" section. This will stop the "Unable to Confirm" popups. Once your LoTW uploads failures are resolved, do a bulk upload of un-submitted to LoTW QSOs from within DXKeeper.

FWIW, I never upload to LoTW (via DXKeeper) with each logged QSO. I simply do a bulk upload at the end-of0the-day, sometimes only once a week. I personally don't understand why some feel the need to upload each QSO in real-time, unless your QSO partner is doing the same, there will not be that instant gratification, you still need to wait for them to upload.

de Laurie VK3AMA



locked Re: Unable to log to DXKeeper

Dave AA6YQ
 

Hello, yes the QSO makes it to the DX keeper log but does not automatically upload to Lotw which is why Im running this two programs to begin with. I have increased the delay to 20 seconds time to log the QSO, still no luck. Guess I can do them manually but thats a PITA and defeats the reason to use DXKeeper in the first place...

+ To determine why the logged QSO is not being submitted to LoTW, please do the following:

1. on the General tab of DXKeeper's Configuration window, check the "Log debugging info" box

2. terminate DXKeeper

3. start DXKeeper

4. log a QSO from JT-Alert

5. on the General tab of DXKeeper's Configuration window, uncheck the "Log debugging info" box

6. attach the errorlog.txt file from your DXKeeper folder to an email message, and send the email message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


locked Re: Unable to log to DXKeeper

Mark Basel <mb02731@...>
 

Hello, yes the QSO makes it to the DX keeper log but does not automatically upload to Lotw which is why Im running this two programs to begin with. I have increased the delay to 20 seconds time to log the QSO, still no luck. Guess I can do them manually but thats a PITA and defeats the reason to use DXKeeper in the first place...


On Jun 25, 2021, at 4:33 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


Subject Line changed to reflect true nature of problem.

On 26/06/2021 7:12 am, Mark Basel wrote:
Hello! if I'm following correctly, im using DX Keeper not HRD so in need to find the correct file for DX keeper to use? Can you tell me which one?  My log file path I see in both JTAlert and DX keeper is C:\DXLab\DXKeeper\Databases\KF0AOC.mdb Sorry for being a knuckle head, not computer savvy

I picked up the HRD log reference in another members signature and incorrectly took it as part of your message.

If JTAlert and DXKeeper are agreeing on the same Log file path, which they should as JTAlert automatically determines the current active DXKeeper log file by examining the same Registry entry that DXKeeper uses to record the Log file path.

Does the QSO actually make it into DXKeeper despite the JTAlert warning popup? Yes or No?
  • If Yes, see the "Frequently Asked Questions (FAQ)" help topic. Look for the "Warning about QSO not logged when it is logged" entry. Access via the Main JTAlert window "Help" menu.

  • If No, then the comms between JTAlert and DXKeeper are likely being blocked. The most common causes are Protection software interference or running DXKeeper with elevated privileges (Set to Run as Administrator). There is normally no need to run DXKeeper (or DXLab Launcher) elevated if the DXLab suite is installed correctly outside the protected "Program Files (X86)" directory tree.

de Laurie VK3AMA




locked #FAQ : Installing the correct compatible versions of JTAlert and the .NET 5.x Desktop Runtime #FAQ

HamApps Support (VK3AMA)
 
Edited

  1. Determine which bit version of Windows you are running, 32bit (x86) or 64bit (x64). See this helpful link from How-To Geek.

  2. Install the .NET 5 Desktop Runtime choosing the bit version that matches your Windows bit version determined in step 1.
    Download from here. It is Important to choose the ".NET Desktop Runtime" NOT the non-desktop ".NET Runtime".

    At the time of this writing, the latest is .NET 5.0.13. Direct download links are ...

  3. Download and install the latest JTAlert version from here.

    At the time of this writing, the latest is JTAlert 2.50.9. Direct download link ...

  4. After installing the .NET Desktop Runtime and JTAlert. Run the ".NET Framework Check" shortcut installed under the "HamApps JTAlert" Windows start-menu group (which is automatically created by the JTAlert installer). If all has been installed correctly, you should see a window similar to this...


    Note: This image is from a 64bit (X64) Windows environment. The results will be similar for a 32bit (x86) Windows environment with changes in the bit version and OS Architecture reported.


de Laurie VK3AMA


locked Re: Signal report

HamApps Support (VK3AMA)
 

On 26/06/2021 7:53 am, Bob wrote:
I'm using wsjt-x windows 10 .Not using any contest mode. When I say gong to their page I mean I go to their page on QRZ.COM and check their log to see if was good contact and no it's not there. ALT + Q Will take you there. When I get pop-up to confirm QSO There isn't any signal report for me just the report I gave him/her and the time for Sent and received is the same it looks like not enough time. Is there a setting for increasing time for contact  to complete. Let me know your thoughts. Thank you kb1yxn 

Not everyone uploads their QSOs to QRZ, either manually or in real-time. QRZ is not a reliable source in this regard.
I personally never upload to QRZ.

As for missing signal report and QSO start/stop times, JTAlert will only log what it has received from WSJT-X when you log the QSO. You should check the "Log QSO" window fields before hitting the OK button and adjust any incorrect or missing data.

de Laurie VK3AMA


locked Re: Signal report

Bob
 

I'm using wsjt-x windows 10 .Not using any contest mode. When I say gong to their page I mean I go to their page on QRZ.COM and check their log to see if was good contact and no it's not there. ALT + Q Will take you there. When I get pop-up to confirm QSO There isn't any signal report for me just the report I gave him/her and the time for Sent and received is the same it looks like not enough time. Is there a setting for increasing time for contact  to complete. Let me know your thoughts. Thank you kb1yxn 

2881 - 2900 of 38435