Date   

locked Re: Finding Partial Contact JTAlert / WSJT-X

WB8ASI Herb
 

Hey Gary....thanks for the tip.  Wish I would have known you can do that.  Sure will save scrolling thru the miles of log. Herb WB8ASI.

On January 15, 2020 at 10:56 AM Gary - AC6EG <AC6EG@...> wrote:

Hi Bob
In the scenario you describe, I find it useful to open all.txt in Notepad.   I click on Edit > Find and enter his callsign and my callsign.  Now every time I press enter, the cursor will jump to the next time I made a transmission to that callsign.  The search begins from wherever the cursor is located in the text, so if I am researching a recent QSO,  I can start the search somewhere near the bottom of the file.  I can quickly find every interaction I've had with a given callsign.  



 


locked Re: Finding Partial Contact JTAlert / WSJT-X

Bob Willey
 

Thanks everyone.

I cannot locate any QSO for the one Incoming Confirmation Request.
Interesting....

Request ReceivedQSO DateCallsignActions
1  2020-01-14  07:42:02  2019-11-20   K3RLW de K6JMQ  

 

I did send an e-mail (got from QRZ page thankfully it was there), to ask for any details on what they saw as a contact.
Incase I missed something.
It is possible it was a SSB contact, but most of those I do an immediate "Log a NEW contact with K6JMQ"

Have not heard anything back from him.


locked Re: Finding Partial Contact JTAlert / WSJT-X

Gary - AC6EG
 

Hi Bob
In the scenario you describe, I find it useful to open all.txt in Notepad.   I click on Edit > Find and enter his callsign and my callsign.  Now every time I press enter, the cursor will jump to the next time I made a transmission to that callsign.  The search begins from wherever the cursor is located in the text, so if I am researching a recent QSO,  I can start the search somewhere near the bottom of the file.  I can quickly find every interaction I've had with a given callsign.  



locked Log4OM V2

Rich McCabe
 

Laurie, with version 2 of Log4om just about to be released how confident are you feeling about an updated JTAlert to work with that?

I will be installing Log4OM v2 as soon as it comes out so need to come up with a game plan for what I am going to do with WSJT.

Thanks and 73,

Rich


locked Re: Ignore option

Bill Barrett
 

Hello Laurie-
Running 2.15.0 when opening the decodes window the continents are blank. Can you think why nothing is populating in that window.
Also in 2.15.6 the decodes window does not open/display at all on my Win7 Pro PC. Ideas?
Thanks once again.
Bill W2PKY 

On Tue, Jan 14, 2020 at 7:34 PM Bill Barrett via Groups.Io <billbarrett174=gmail.com@groups.io> wrote:
Thanks Laurie will try your suggestion, will give it a try.

Bill W2PKY

On Tue, Jan 14, 2020 at 3:10 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 15/01/2020 2:31 am, Bill Barrett wrote:
Mainly interested DX and with the high number of decodes on bands like 40 & 20 would like an option to to "ignore USA" decodes. Looked around but failed to see that feature in the app. Did I miss it?.

Thanks, could not operate digital without your terrific app.

--
Bill Barrett W2PKY

Bill,

While JTAlert itself doesn't provide for explicit exclusion of Country of origin decodes, the Decodes window does. Make the "Country Name" column visible then right click the Country name of any USA decode and select hide. You can do this for multiple countries. You can save this as a Filter and apply it at any time. Once

If you don't want to use the Decodes window, you can always set JTAlert to not show any callsigns not generating an Alert via the "Alerts -> Filters" menu.

de Laurie VK3AMA



--
Bill Barrett
352-437-4758



--
Bill Barrett
352-437-4758


locked Re: Finding Partial Contact JTAlert / WSJT-X

Michael Black
 

You have to look in ALL.TXT -- same directory...from a cmd prompt.

For example to find your QSO with CT3HF...

find "K3RLW" all.txt | find "CT3HF"

de W9MDB


On Tuesday, January 14, 2020, 10:42:45 PM CST, Bob Willey <bobwilley@...> wrote:


That was helpful, but it seems to only show completed one line per QSO transactions.
No the actual back and forth, is it failed for instance.
Here is a snippet around the time I am looking for as an example of what is in the log:
2019-11-14,18:43:00,2019-11-14,18:44:00,CT3HF,IM12,14.075907,FT8,-11,-10,,FT8  Sent: -11  Rcvd: -10,
2019-11-14,19:16:45,2019-11-14,19:17:45,KS4OT,EM83,14.075821,FT8,-08,-04,,FT8  Sent: -08  Rcvd: -04,
2019-11-14,19:42:00,2019-11-14,19:44:00,N5XXZ,EM45,14.074957,FT8,-01,+04,,FT8  Sent: -01  Rcvd: +04,
2019-11-14,20:03:45,2019-11-14,20:03:45,HK3JJH,FJ24,24.915499,FT8,,,,FT8,
2019-11-14,20:15:30,2019-11-14,20:16:30,V31MA,,18.100264,FT8,+05,+05,,FT8  Sent: +05  Rcvd: +05,
2019-11-14,20:20:00,2019-11-14,20:21:00,W7QDM,DN43,18.101891,FT8,-07,-08,,FT8  Sent: -07  Rcvd: -08,
2019-11-14,20:23:00,2019-11-14,20:24:00,N0GTO,,18.101497,FT8,-09,-15,,FT8  Sent: -09  Rcvd: -15,

This is the idea, but the log file I had seen before when someone questioned a QSO had multiple lines showing the whole interaction.  They had walked me thru it, but it was in JTAlert Messaging, and it doesn't go back, it gets purged apparently.

Is there another detailed log?




photo
Bob Willey
K3RLW

(410) 251-8960 | K3RLW@...

http://qrz.com/db/K3RLW

5161 Ocean Gateway, Trappe Maryland 21673-2023 USA

On Tue, Jan 14, 2020 at 9:54 PM Marion D. Kitchens <k4gok@...> wrote:
Bob,
With WSJTX running,  click on the File menu item.  Select "Open Log Directory", then open "wsjtx.log".  That is a standard text type file and you can do a "find" operation on the call sign of interest.
 
You can also open the ALL.TEXT file, but that is likely to be a huge file for doing a search.
 
Good Luck
 
de Marion,   K4GOK
 
 
 
On Tue, 14 Jan 2020 15:59:41 -0800 "Bob Willey" <bobwilley@...> writes:
The scenario is that either a QSO is rejected in QRZ or an Incoming Confirmation Request comes in

I know there is a way to interrogate the Log(s) to see any occurence of say a CALLSIGN
How?
I had done this with someones direction, but I believe it was in a JTAlert Message direct and they are not kept.

Can anyone direct me to how to find the threads of a QSO and whether an exchange on FT8 was made???

This would be extremely helpful to me.

Thanks in advance, 73's de K3RLW 
 


locked Re: Grid alert not showing except for CQ on some decodes, tied to distance/bearing not in popup?

HamApps Support (VK3AMA)
 

On 15/01/2020 2:04 pm, pphiliphome@... wrote:
I am running version 2.15.6 on Win10 Pro. I didn't see this in a previous version. I saw a CQ with a grid alert and afterwards, in the middle of a sequence, the same call is not highlighted/alerted. Also, the hover popup didn't show bearing and distance.

Other non-CQ decodes show grid alerts, and other popups, including the ones with grid alerts do show distance/bearing.

I assume these 2 conditions are related as you must use the grid for the calculation.

Am I missing something?

Thanks for the great program!
Paul, AC9O

Paul,

The only thing your missing is the next release (due in 2 days).
What you describe is a defect corrected in 2.15.7

From the 2.15.7 release notes..
    - Callsign Tooltip & Decodes Window: Missing Grid/Distance/Bearing data when
       decode doesn't contain a grid but earlier decodes did (the grid data was
       not being cached correctly).


de Laurie VK3AMA


locked Re: Finding Partial Contact JTAlert / WSJT-X

Bob Willey
 

That was helpful, but it seems to only show completed one line per QSO transactions.
No the actual back and forth, is it failed for instance.
Here is a snippet around the time I am looking for as an example of what is in the log:
2019-11-14,18:43:00,2019-11-14,18:44:00,CT3HF,IM12,14.075907,FT8,-11,-10,,FT8  Sent: -11  Rcvd: -10,
2019-11-14,19:16:45,2019-11-14,19:17:45,KS4OT,EM83,14.075821,FT8,-08,-04,,FT8  Sent: -08  Rcvd: -04,
2019-11-14,19:42:00,2019-11-14,19:44:00,N5XXZ,EM45,14.074957,FT8,-01,+04,,FT8  Sent: -01  Rcvd: +04,
2019-11-14,20:03:45,2019-11-14,20:03:45,HK3JJH,FJ24,24.915499,FT8,,,,FT8,
2019-11-14,20:15:30,2019-11-14,20:16:30,V31MA,,18.100264,FT8,+05,+05,,FT8  Sent: +05  Rcvd: +05,
2019-11-14,20:20:00,2019-11-14,20:21:00,W7QDM,DN43,18.101891,FT8,-07,-08,,FT8  Sent: -07  Rcvd: -08,
2019-11-14,20:23:00,2019-11-14,20:24:00,N0GTO,,18.101497,FT8,-09,-15,,FT8  Sent: -09  Rcvd: -15,

This is the idea, but the log file I had seen before when someone questioned a QSO had multiple lines showing the whole interaction.  They had walked me thru it, but it was in JTAlert Messaging, and it doesn't go back, it gets purged apparently.

Is there another detailed log?




photo
Bob Willey
K3RLW

(410) 251-8960 | K3RLW@...

http://qrz.com/db/K3RLW

5161 Ocean Gateway, Trappe Maryland 21673-2023 USA


On Tue, Jan 14, 2020 at 9:54 PM Marion D. Kitchens <k4gok@...> wrote:
Bob,
With WSJTX running,  click on the File menu item.  Select "Open Log Directory", then open "wsjtx.log".  That is a standard text type file and you can do a "find" operation on the call sign of interest.
 
You can also open the ALL.TEXT file, but that is likely to be a huge file for doing a search.
 
Good Luck
 
de Marion,   K4GOK
 
 
 
On Tue, 14 Jan 2020 15:59:41 -0800 "Bob Willey" <bobwilley@...> writes:
The scenario is that either a QSO is rejected in QRZ or an Incoming Confirmation Request comes in

I know there is a way to interrogate the Log(s) to see any occurence of say a CALLSIGN
How?
I had done this with someones direction, but I believe it was in a JTAlert Message direct and they are not kept.

Can anyone direct me to how to find the threads of a QSO and whether an exchange on FT8 was made???

This would be extremely helpful to me.

Thanks in advance, 73's de K3RLW 
 


locked Grid alert not showing except for CQ on some decodes, tied to distance/bearing not in popup?

Paul AC9O
 

I am running version 2.15.6 on Win10 Pro. I didn't see this in a previous version. I saw a CQ with a grid alert and afterwards, in the middle of a sequence, the same call is not highlighted/alerted. Also, the hover popup didn't show bearing and distance.

Other non-CQ decodes show grid alerts, and other popups, including the ones with grid alerts do show distance/bearing.

I assume these 2 conditions are related as you must use the grid for the calculation.

Am I missing something?

Thanks for the great program!
Paul, AC9O


locked Re: Finding Partial Contact JTAlert / WSJT-X

Marion D. Kitchens
 


Bob,
With WSJTX running,  click on the File menu item.  Select "Open Log Directory", then open "wsjtx.log".  That is a standard text type file and you can do a "find" operation on the call sign of interest.
 
You can also open the ALL.TEXT file, but that is likely to be a huge file for doing a search.
 
Good Luck
 
de Marion,   K4GOK
 
 
 
On Tue, 14 Jan 2020 15:59:41 -0800 "Bob Willey" <bobwilley@...> writes:

The scenario is that either a QSO is rejected in QRZ or an Incoming Confirmation Request comes in

I know there is a way to interrogate the Log(s) to see any occurence of say a CALLSIGN
How?
I had done this with someones direction, but I believe it was in a JTAlert Message direct and they are not kept.

Can anyone direct me to how to find the threads of a QSO and whether an exchange on FT8 was made???

This would be extremely helpful to me.

Thanks in advance, 73's de K3RLW 
 


locked Re: Ignore option

Bill Barrett
 

Thanks Laurie will try your suggestion, will give it a try.

Bill W2PKY

On Tue, Jan 14, 2020 at 3:10 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 15/01/2020 2:31 am, Bill Barrett wrote:
Mainly interested DX and with the high number of decodes on bands like 40 & 20 would like an option to to "ignore USA" decodes. Looked around but failed to see that feature in the app. Did I miss it?.

Thanks, could not operate digital without your terrific app.

--
Bill Barrett W2PKY

Bill,

While JTAlert itself doesn't provide for explicit exclusion of Country of origin decodes, the Decodes window does. Make the "Country Name" column visible then right click the Country name of any USA decode and select hide. You can do this for multiple countries. You can save this as a Filter and apply it at any time. Once

If you don't want to use the Decodes window, you can always set JTAlert to not show any callsigns not generating an Alert via the "Alerts -> Filters" menu.

de Laurie VK3AMA



--
Bill Barrett
352-437-4758


locked Finding Partial Contact JTAlert / WSJT-X

Bob Willey
 

The scenario is that either a QSO is rejected in QRZ or an Incoming Confirmation Request comes in

I know there is a way to interrogate the Log(s) to see any occurence of say a CALLSIGN
How?
I had done this with someones direction, but I believe it was in a JTAlert Message direct and they are not kept.

Can anyone direct me to how to find the threads of a QSO and whether an exchange on FT8 was made???

This would be extremely helpful to me.

Thanks in advance, 73's de K3RLW 


locked Re: JT alert and QRZ Logbook

Ken Desjardins
 

Oh, I did not receive a link. I just looked in my spam folder too.


locked Re: Ignore option

neil_zampella
 

Also understand that the contest modes (other than F/H) have been removed from the WSJT-X code base in that program

 

Neil, KN3ILZ


locked Re: TCP: QSP Data Transfer Socket Operation Timed out #FT8

Bob Davet
 

You could be right. Was not sure which program initiated it.

I only get over to my dad's 1 or 2 times a week. So when I get there I will get the picture and post it.

Bob
W8RID


locked Re: JT alert and QRZ Logbook

HamApps Support (VK3AMA)
 

On 15/01/2020 7:10 am, Ken Desjardins wrote:
Hi Laurie, Any progress with this issue?

Ken,

I previously sent you a link to the latest JTAlert Beta build (sent 2-Jan), did that not correct your QRZ problem?
I couldn't find a response from you so I assume you didn't try it, is that the case?

All other users who received the Beta builds reported back that it corrected their intermittent problems with online logging, xml lookups, DXLab DDE, etc.

The next public release of JTAlert is 2 days away, you may want to for that and report back if your problems persist.

de Laurie VK3AMA


locked Re: TCP: QSP Data Transfer Socket Operation Timed out #FT8

HamApps Support (VK3AMA)
 

On 15/01/2020 6:11 am, Bob Davet wrote:
"TCP QSO Data transfer socket operation timed out"

Click on OK and it goes away.

This comes up when it logs the QSO into HRD.

This does not appear (as best I can remember) to be a JTAlert generated error message. Is this a Windows or HRD message?

Please post an image of the offending error window. DON'T post a capture of your entire desktop, just the error window is all that is needed.

de Laurie VK3AMA


locked Re: Ignore option

HamApps Support (VK3AMA)
 

On 15/01/2020 2:58 am, WB5JJJ - George wrote:
But on a busy band, 75% of the callsigns fall into the "I don't need/want them" category, but still clutter the display. 

--
73's
George - WB5JJJ

Simple, set JTAlert to not show any callsigns not generating an Alert via the "Alerts -> Filters" menu.

de Laurie VK3AMA


locked Re: Ignore option

HamApps Support (VK3AMA)
 

On 15/01/2020 2:31 am, Bill Barrett wrote:
Mainly interested DX and with the high number of decodes on bands like 40 & 20 would like an option to to "ignore USA" decodes. Looked around but failed to see that feature in the app. Did I miss it?.

Thanks, could not operate digital without your terrific app.

--
Bill Barrett W2PKY

Bill,

While JTAlert itself doesn't provide for explicit exclusion of Country of origin decodes, the Decodes window does. Make the "Country Name" column visible then right click the Country name of any USA decode and select hide. You can do this for multiple countries. You can save this as a Filter and apply it at any time. Once

If you don't want to use the Decodes window, you can always set JTAlert to not show any callsigns not generating an Alert via the "Alerts -> Filters" menu.

de Laurie VK3AMA


locked Re: JT alert and QRZ Logbook

Ken Desjardins
 

Hi Laurie, Any progress with this issue?