Date   

locked ARRL Field day

Michael
 

 

Anyone know what an FT8 setup with Wsjt-x, JTAlerts, and HRD should look like to log  the contacts  properly?

 

Thanks

 

Mike – W7OSG

Boise, Idaho  USA

 


locked JTAlert 2.16.8

Lawrence Godek
 

I find I get no constant flow of decodes on each receive cycle with this version in the decodes window. I am using it with WSJT-X v2.2.1.  If I go back to  JTAlert 2.16.7 it works as it should.
Larry/w0ogh 


locked Re: Not logging some QSOs to DXKeeper. #DXLAB

Carl - WC4H
 

HI Laurie.

I uploaded the error via the menu item in JTAlerts.

Thanks.
Carl - WC4H


locked Re: #TIP Continental Filter #TIP

Jim Nakajima
 

Dear Laurie,

Please forget about this post, I found my fault.
It came back all Asian stations when I checked "Asia" in "Alert"-"Filters"-"Show Continent Decodes".

JA9IFF Jim


locked Re: Not logging some QSOs to DXKeeper. #DXLAB

Dave AA6YQ
 

+ AA6YQ comments below

I have noticed that sometimes the QSO is not displayed in the window of the Log QSOs tab. I have been able to make it reappear by terminating and then restarting DXKeeper. My theory is that the pointer used for the display of the incore database records gets corrupted. When the file is closed and reopened the pointers are resynched. Only a guess at what may be happening, but try it next time you see the error.

+ There is no evidence supporting that guess. The next time it happens, Dave, remove any Log Page Display filtering by clicking the X button in the Filter panel at the bottom of DXKeeper's Main window's "Log QSOs" tab.

+ The errorlog that Carl WC4H sent me showed that for the missing QSO, DXKeeper never received a "Log QSO" directive from JT-Alert.

73,

Dave, AA6YQ


locked Re: #TIP Continental Filter #TIP

Jim Nakajima
 

Dear Laurie,

Since turned Asian Continental Filter "ON", "Callsign Display" shows less between 1/2 and 1/4 in these 2 weekends.
But I turned "OFF" (Save it), "callsign Display" did not show any Asian stations.
Reboot JTAlert (ver. 2.16.8) did not influence.
Any suggestion?

JA9IFF Jim


locked Re: Not logging some QSOs to DXKeeper. #DXLAB

DAVID BERNHEISEL
 

I have noticed that sometimes the QSO is not displayed in the window of the Log QSOs tab. I have been able to make it reappear by terminating and then restarting DXKeeper. My theory is that the pointer used for the display of the incore database records gets corrupted. When the file is closed and reopened the pointers are resynched. Only a guess at what may be happening, but try it next time you see the error.

Dave - N2DPF

On 6/25/2020 9:00 AM, Carl - WC4H via groups.io wrote:
Hi Bill.
I am absolutely sure.  It just happened againg.  That means that it was not the eQSL upload.  I mentioned eQSL for  full disclosure but as I now know, it is not the problem.
I have the debug log for day for this instance and I will now turn on the debug log for JTAlerts.  Like I said before, this is randome so there's no predicting when it will happen again.
Laurie:
I was sending some text messages during the use this time.  If the QSO partner is online, I often send a "Tnx QSO.  73.  Carl" message. Sometimes that leads to a few exchanges which are like an extended QSOs and can be very interesting.
I'll keep an eye on it to see if the messages interfere.
73.
Carl - WC4H


locked Re: Would like to know how to set the TCP port to talk to logger32

Jay Mason
 

Thank you for the response 
N3OW
Jay


locked Re: Would like to know how to set the TCP port to talk to logger32

Joe Subich, W4TV
 

I thought seance the udp port is being used between WSJT-X and JT
Alert I could use the TCP port. any idea how to set the TCP port or
what the port address is or even if this is a viable option.
This is not a viable option. JT Alert writes to supporting loggers
using either a logger provided API or by writing directly to the
log database. The developer of Logger32 declined to provide either
a documented API or documentation for the log database schema. As
such, Laurie has declined to provide any support for Logger32.

You can, of course, use the ADIF file by exporting/importing it
to Logger32 following each operating session. Details of import
to Logger32 are an exercise for the student - see any Logger32
documentation.

73,

... Joe, W4TV


On 2020-06-25 2:21 PM, Jay Mason wrote:
Good day
I would like to have the log information from JT Alert sent to Logger 32.
JT Alert talks to wsjt-x no problem but only writes to the JT Alert log .
I thought seance the udp port is being used between WSJT-X and JT Alert I could use the TCP port.
any idea how to set the TCP port or what the port address is or even if this is a viable option.
Thank you
N3OW
Jay


locked getting JT Alert to talk to logger 32 via TCP port

Jay Mason
 

is there a way to configure the TCP port used by JT alert so that i can log to logger32.
JT Alert work fine with WSJT-X and it log to JT Alert log but I would like to log to Logger as well.
SO with JT Alert talking to WsJT-X i figured that the UDP port is being used.
Thank you
Jay N3OW


locked Would like to know how to set the TCP port to talk to logger32

Jay Mason
 

Good day
I would like to have the log information from JT Alert sent to Logger 32.
JT Alert talks to wsjt-x no problem but only writes to the JT Alert log .
I thought seance the udp port is being used between WSJT-X and JT Alert I could use the TCP port.
any idea how to set the TCP port or what the port address is or even if this is a viable option.
Thank you
N3OW
Jay


locked Re: Manually adding Grid Squares worked B4?

wo4o RiC
 

Aha! Now I understand.
Thank you Laurie!
--------------------
73 de RiC wo4o
Grand Island FL


locked Re: Errorlog.txt - station not logged via JTAlerts

Dave AA6YQ
 

Thanks, Carl. The errorlog shows the receipt of log directives for QSOs with

KE0CH at 2020-06-25 13:41:03

WB9DLC at 2020-06-25 13:43:11

WW0E at 2020-06-25 13:44:44

The errorlog does not show DXKeeper receiving a directive to log a QSO with WZ9B.

73,

Dave, AA6YQ

-----Original Message-----
From: wc4h . [mailto:wc4h0001@gmail.com]
Sent: Thursday, June 25, 2020 10:06 AM
To: aa6yq@ambersoft.com
Subject: Errorlog.txt - station not logged via JTAlerts

Hi Dave.

Attached is the error log as you requested. I had to wait until this morning for the error to happen again. The station NOT logged was. WZ9B.


73 & Thanks.
Carl - WC4H


<http://www.avg.com/email-signature?utm_medium=email&;utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&;utm_source=link&utm_campaign=sig-email&utm_content=emailclient>


locked Re: Not logging some QSOs to DXKeeper. #DXLAB

Dave AA6YQ
 

+ AA6YQ comment sbelow

It's relatively recent, but yesterday it seems to have happened more frequently. PC restart is one of the first things I do.

I may have hit upon the solution. Last night, while having the DXKeeper debug on, I had previously turned off the logging to eQSL checkbox in JTAlerts. There may be an issue with my eQSL since I moved.

+ If that was the case, the failure should occur each time you log a QSO -- not sporadically.

However, in that case, I would expect that it would log it to DXKeeper and DXKeeper to give me an error that it was not uploaded to eQSL.

I'll continue using it and try the JTAlerts debugging and let you know.

If it's the eQSL issue, then it should not happen while I have that tuned off and I will let you know as well., If I go two or three days without the problem, then I will think it was the eQSL logging.

+ A DXKeeper errorlog that captures the failing scenario would eliminate the need for speculation. You can simultaneously enable the JT-Alert errorlogging that Laurie VK3AMA requested.

73,

Dave, AA6YQ


locked Re: Not logging some QSOs to DXKeeper. #DXLAB

Carl - WC4H
 

Hi Bill.

I am absolutely sure.  It just happened againg.  That means that it was not the eQSL upload.  I mentioned eQSL for  full disclosure but as I now know, it is not the problem.

I have the debug log for day for this instance and I will now turn on the debug log for JTAlerts.  Like I said before, this is randome so there's no predicting when it will happen again.

Laurie:

I was sending some text messages during the use this time.  If the QSO partner is online, I often send a "Tnx QSO.  73.  Carl" message.  Sometimes that leads to a few exchanges which are like an extended QSOs and can be very interesting.

I'll keep an eye on it to see if the messages interfere.

73.
Carl - WC4H


locked Re: Not logging some QSOs to DXKeeper. #DXLAB

g4wjs
 

On 25/06/2020 14:03, Carl - WC4H via groups.io wrote:
HI Laurie.

It's relatively recent, but yesterday it seems to have happened more frequently.  PC restart is one of the first things I do.

I may have hit upon the solution.  Last night, while having the DXKeeper debug on, I had previously turned off the logging to eQSL checkbox in JTAlerts.  There may be an issue with my eQSL since I moved.  However, in that case, I would expect that it would log it to DXKeeper and DXKeeper to give me an error that it was not uploaded to eQSL.

I'll continue using it and try the JTAlerts debugging and let you know.

If it's the eQSL issue, then it should not happen while I have that tuned off and I will let you know as well.,  If I go two or three days without the problem, then I will think it was the eQSL logging.

Thanks.
73.
Carl - WC4H
Carl,

are you certain that these QSOs are not being logged to DXKeeper? I ask because a failure to upload to eQSL should not stop the QSO being logged to DXKeeper when requested to do so by JTAlert. What can happen is that the logging is delayed by online lookups, which take variable amounts of time, and when JTAlert attempts to confirm that the QSO has been successfully logged it sometimes doesn't find the record. This is due to timing issues as JTAlert does not know when the QSO is actually logged, it simply uses a timer to wait a while, you set that timer in the JTAlert settings.



--
73
Bill
G4WJS.


locked Re: Not logging some QSOs to DXKeeper. #DXLAB

Carl - WC4H
 

HI Laurie.

It's relatively recent, but yesterday it seems to have happened more frequently.  PC restart is one of the first things I do.

I may have hit upon the solution.  Last night, while having the DXKeeper debug on, I had previously turned off the logging to eQSL checkbox in JTAlerts.  There may be an issue with my eQSL since I moved.  However, in that case, I would expect that it would log it to DXKeeper and DXKeeper to give me an error that it was not uploaded to eQSL.

I'll continue using it and try the JTAlerts debugging and let you know.  

If it's the eQSL issue, then it should not happen while I have that tuned off and I will let you know as well.,  If I go two or three days without the problem, then I will think it was the eQSL logging.  

Thanks.
73.
Carl - WC4H


locked Re: Defender quarantines files

wazzan1@...
 

Update reinstalled JTAlert and is working again
Wayne VK4WTN 


locked Re: Manually adding Grid Squares worked B4?

HamApps Support (VK3AMA)
 

On 25/06/2020 12:26 am, wo4o RiC wrote:
Thank you Laurie for confirming this about manual adds. Recently I began using only WSJT-X for logging to casually chase new Grid Squares on 6m. However, prior to using WSJT-X, I uploaded many 6m logs from N1MM+ logger to Logbook of the World. I've downloaded my lotwreport.adi (comprised of confirmed 6m QSOs with Grid Squares) with the expectation to add/scan it for JTA to 'block' worked B4 alerts.

That leads me to my next question, which I've failed to find the answer after searching. How is a lotwreport.adi to be scanned? 

I've hesitated to merge my lotwreport.adi with wsjtx_log.adi (if this is necessary to accomplish my objective) because the file structures appear to be different. My ignorance about the process is why I wanted to manually add the worked Grid Squares to JTA in an effort to improve my efficiency in calling only stations in new Grid Squares in reaching some personal goals. However, if there is a way to scan my lotwreport.adi, that seems to be the better (perhaps only "as is") solution.

If this issue has already been addressed elsewhere online, which was missed during my search, please point me in the right direction.

Your invested time, effort to reply are appreciated.

Thanks for all you do to make our hobby/service more enjoyable!

73 de RiC wo4o

Ric,

First, JTAlert doesn't care about the WSJT-X adi file, it doesn't look at it and never goes near it.

If you want to get your LoTW confirmed Grids into JTAlert, set JTAlert to use ADIF logging and select the lotwreport.adi as the file. Whatever log is enabled in JTAlert is what is used for the "Scan Log" process to update the different Alert lists, including the Grid Alert.

The Lotw adi file doesn't specify any LoTW confirmed fields in the file despite all the QSOs being for LoTW confirmed QSOs, so you need to set the Scan Confirmation option to "No QSL Confirmation..."

   

If you want the Callsigns in that LoTW adi file to be flagged as worked B4 just leave the ADIF logging enabled as all B4 checks are done against the enabled log type.

de Laurie VK3AMA


locked Re: Not logging some QSOs to DXKeeper. #DXLAB

HamApps Support (VK3AMA)
 

On 25/06/2020 10:54 am, Carl - WC4H via groups.io wrote:
No it does not log it to DX Keeper.  That is why I posted the error.  It then will continue to log other QSOs but it will fail again.  There's no predicting when.

I ALWAYS start DXKeeper and WSJT-X before JTAlerts.

73.
Carl - WC4h

Tnx Carl,

If the QSOs are randomly not being logged, rather than just an erroneous not-logged report from JTAlert, that gives us somewhere to look.

Is this random non-logging a recent problem or have you been experiencing it in previous JTAlert releases? If it is only recent, a Windows Restart may be all that is needed, especially with the recent activity in Windows updates, a sure recipe for application misbehavior (in my experience and not just with JTAlert).

If a Windows restart doesn't correct the problem please do the following...

  • Enable debug recording via the "Settings -> Enable Debug Recording" JTAlert menu.
  • Restart JTAlert, that is close JTAlert and then start JTAlert.
  • Operate as normal logging QSOs to DXKeeper.
  • Once you encounter a failed logging use the "Help -> Contact Support" menu, to send me your JTAlert files for analysis. Include a note of the Callsign and UTC time of the failed logging.
  • Turn off debug recording.

de Laurie VK3AMA

2421 - 2440 of 32886