My post presents the fact that even in Log4OM2 the comments are not showing up in eQSL. And the JTAlert workaround shows that the ADIF data generated by JTAlert is displayed in eQSL. Additionally, tha

#DXLAB

FYI, The rebuild has no effect on B4 reporting. The rebuild only concerns itself with the alert-able entities like dxcc, zones, states, etc. For corrected B4 reporting after an erroneous log entry has

#HamSpots #DXLAB

Yeah...the About not opening was the big clue. Mike

#DXLAB

Since there is wsjtx restarting in a multi-instance setup you will need to restart all JTAlert instances. While JTAlert can handle, in a single instance setup, a restart of wsjt and the resulting chan

#FT8 #DXLAB

Dick, Very good. Glad you got it working. 73, Jim N6VH

#FT8 #DXLAB

The fix for this is in the next public release of JTAlert. I have sent you a link to a beta build to test, check your inbox. de Laurie VK3AMA

#DXLAB

Greetings All Thanks to many of you and especially to AA6YQ/Dave, Everything is working correctly and I am a 'happy-camper'. The last problem of getting JTAlert/WSJT-X/DXKeeper to upload to LOTW was a

#DXLAB #FT8

Hello Joe OK, I've made the suggested changes and will see if this corrects the problem. I will report back later with results. 73 Dick/w7wkr

#DXLAB #FT8

There is no JTAlert log. The log JTAlert uses is what you have enabled, in your case DXKeeper. JTAlert does keep a dedicated B4 log for users who don't have a logger enabled but that is irrelevant to

#DXLAB

I have a question. What letter is rebuild data base looking for when doing a rebuild of confirmed calls in DXKeeper? I keep working already confirmed calls that show confirmed after I start to call th

#DXLAB

The worked B4 consider the current Band, Mode and transmitted Grid in determining the B4 status. You will find that this callsigns was likely transmitting a different Grid from that previously logged

#DXLAB

Thank you Laurie 73 De Thierry F5SIB

#DXLAB

JTAlert doesn't record the high-volume spot traffic, so there is nothing to examine in the JTAlert session files, but you can examine the SpotCollector "ErrorLog.txt" file located in your SC install d

#DXLAB

Hello, I have run thru the description http://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesWithJTAlert serval times and set all the switches asked for. But I still do not get a correct indi

#DXLAB

How old is your copy of JTAlert? Fifth from the bottom is "Rebuild Alert Database" de Laurie VK3AMA

#DXLAB

Dave, Does this track by band (separate map for each band) or is there only one map that is updated regardless of any band the grid is worked/confirmed? 73, John, N8WNA

#DXLAB #HamSpots #FT8

There are more options, you need to scroll down. Did you miss the highlighted vertical scrollbar (on the right) in my original post?

#DXLAB

The JTA grid alert is now working properly, finally, after reverting back to normal configurations (in JTAlert, DXKeeper, WSJT) after the VHF contest. Once I determine what had gone wrong earlier, dur

#DXLAB

Hi Laurie, I understand that but just because you have called TCPCloseSocket doesn't mean that the DXKeeper TCP/IP server has finished and closed its end of the connection. Do you get a reply from DXK

#DXLAB

Have you tried sharing the log file via a cloud service like Dropbox? Neil, KN3ILZ

#DXLAB