Date   

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.12. Direct download links are ...

  3. Download and install the latest JTAlert version from here. Choose the bit version that matches your Windows bit version and the .NET 5 Desktop Runtime bit version.

    At the time of this writing, the latest is JTAlert 2.50.8. 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 


locked Re: Unable to log to DXKeeper

HamApps Support (VK3AMA)
 

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 Re: wont talk to wsjt

Mark Basel <mb02731@...>
 

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😕

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


On 26/06/2021 5:30 am, Mark Basel wrote:
still receiving the unable to confirm qso. Any additional guidance is welcome

That message tells me that you don't need to worry about UDP setup with WSJT-X as that is working as JTAlert correctly received a logging messaged from WSJT-X.

That message indicates that JTAlert was unable to find the newly logged QSO in your HRD log file. That is typically caused by JTAlert not being set to use the correct log file. Double-check the Settings to see if JTAlert has been set to use the correct log, it likely has not.

de Laurie VK3AMA




locked Re: Reason for UDP problems: Malwarebytes

HamApps Support (VK3AMA)
 

On 26/06/2021 6:27 am, Willi Passmann wrote:
I just found the reason for logging problems on my Win7 Prof. system.

There was no transfer of logs from JTDX via JTAlert (or GridTracker) to
Log4OM, although all CAT commands worked ok, as well as PTT. All
settings were correct, too.

The software Malwarebytes blocked the UDP transfers; as soon as I
disabled the program, everything worked again.

vy 73,
Willi, DJ6JZ

Tnx Willi.

In my opinion, Protection software that interferes in program operation without notifying the user that blocks have been implemented or files deleted/quarantined is not much better than the malicious software it is trying to protect the user from. That is, the Protection software is interfering without notification in a similar manner to the operation of true malicious software.

de Laurie VK3AMA


locked Reason for UDP problems: Malwarebytes

Willi Passmann
 

I just found the reason for logging problems on my Win7 Prof. system.

There was no transfer of logs from JTDX via JTAlert (or GridTracker) to
Log4OM, although all CAT commands worked ok, as well as PTT. All
settings were correct, too.

The software Malwarebytes blocked the UDP transfers; as soon as I
disabled the program, everything worked again.

vy 73,
Willi, DJ6JZ


locked Re: wont talk to wsjt

HamApps Support (VK3AMA)
 

On 26/06/2021 5:30 am, Mark Basel wrote:
still receiving the unable to confirm qso. Any additional guidance is welcome

That message tells me that you don't need to worry about UDP setup with WSJT-X as that is working as JTAlert correctly received a logging messaged from WSJT-X.

That message indicates that JTAlert was unable to find the newly logged QSO in your HRD log file. That is typically caused by JTAlert not being set to use the correct log file. Double-check the Settings to see if JTAlert has been set to use the correct log, it likely has not.

de Laurie VK3AMA




locked Re: wont talk to wsjt

Mark Basel <mb02731@...>
 

Set up the option for wsjt udp multicast on loopback, no joy,  still receiving the unable to confirm qso. Any additional guidance is welcome...

thanks
mark


locked Re: wont talk to wsjt

mb02731@...
 

Thanks Ron, I will set that up! 


On Jun 25, 2021, at 8:11 AM, Ron W3RJW via groups.io <w3rjw@...> wrote:

If you decide you need to use multicast, then you must set the option in JTAlert.: Settings, "WSJT-X UDP multicast  on loopback"
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.5.0, rc1, JTAlert 2.50.1 beta, HRD Deluxe v6.7.0.357
FTdx-3000, SignaLink USB


locked Re: wont talk to wsjt

Ron W3RJW
 

If you decide you need to use multicast, then you must set the option in JTAlert.: Settings, "WSJT-X UDP multicast  on loopback"
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.5.0, rc1, JTAlert 2.50.1 beta, HRD Deluxe v6.7.0.357
FTdx-3000, SignaLink USB


locked Re: JTAlert confirmation error

mb02731@...
 

Still  receiving the error message...


locked Re: JTAlert confirmation error

mb02731@...
 

Thanks Mike. Changed the Check QSO log delay to 15 seconds, the TCP Network Service port is 52000 and the log file path is good. Will see if this works, thanks


locked Re: JTAlert confirmation error

mb02731@...
 

Thanks, they are in the WSJT-X ADIF file but do. Ot go to Lotw automatically as I had hoped...


locked Re: JTAlert confirmation error

Michael Black
 

Are your QSOs still logging or not?

If they are getting logged anyways you can increase the timeout value here
Inline image
Also make sure you have the correct path to your database
Inline image



Mike W9MDB




On Thursday, June 24, 2021, 05:50:25 PM CDT, <mb02731@...> wrote:


Hello! New user of JTAlert and DX Keeper so my apologies if this has been addressed. Getting this confirmation error window after every QSO. Have tried reading through the online help but i'm pretty lost. Would really appreciate some guidance. Thanks
Mark

 




 


locked JTAlert confirmation error

mb02731@...
 

Hello! New user of JTAlert and DX Keeper so my apologies if this has been addressed. Getting this confirmation error window after every QSO. Have tried reading through the online help but i'm pretty lost. Would really appreciate some guidance. Thanks
Mark

 




 

2121 - 2140 of 37662