Date   

locked Re: B4 Behavior

Joe Subich, W4TV
 

On 2021-09-17 7:10 PM, Dave Garber wrote:
how do you rescan a log in wsjtx
WSJTX rereads the log every time it starts.

On Fri, Sep 17, 2021 at 9:42 AM WB5JJJ - George <wb5jjj@gmail.com
<mailto:wb5jjj@gmail.com>> wrote:
So I'm at a loss as to why WSJTx is sending it on as a wanted
contact.
JTAlert does not use the B4 information from WSJTX. When you use an
external log, JTAlert compares the "received" data to previously
logged data - Callsign, Grid, Band and mode (and date - if you have
have selected "Ignore QSOs B4"). JTAlert reads the log and caches a
copy in memory every time it starts.

If you are not closing JTAlert and your logging program after every
operating session, you risk damage to the cached image of your log
data through sleep/hibernate/shutdown that could cause inaccurate
QSO B4 behavior.

73,

... Joe, W4TV


On 2021-09-17 7:10 PM, Dave Garber wrote:
how do you rescan a log in wsjtx
Dave Garber
VE3WEJ / VE3IE
On Fri, Sep 17, 2021 at 9:42 AM WB5JJJ - George <wb5jjj@gmail.com <mailto:wb5jjj@gmail.com>> wrote:
I have seen this also in recent days/weeks.  I also noticed that
WSJTx does NOT honor a B4 status on some stations, thus triggering
the wanted status on to JTAlert.  Nothing special about the call or
any other information at all.
To test, I disconnected my log (HRD) from JTAlert and logged a fake
QSO in WSJTx for the actual B4 station that I'm currently seeing,
and then forced WSJTx to rescan its adif log.  That seemed to fix
the problem.  In comparing the previous adif log entry for that
non-B4 station and the new fake one, they appear to be identical in
Notepad++.  The next time this happens, I'm going to copy the fake
QSO in place of the original one, delete the fake one and then force
WSJTx to do a rescan.   Will be interesting to see what happens.
So I'm at a loss as to why WSJTx is sending it on as a wanted
contact.  (Reported to the developers group)  JTAlert is apparently
behaving as it should, based on the bad information it gets from
WSJTx, even though I think JTAlert should have recognized the entry
as a B4 itself.
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: B4 Behavior

Dave Garber
 

how do you rescan a log in wsjtx

Dave Garber
VE3WEJ / VE3IE


On Fri, Sep 17, 2021 at 9:42 AM WB5JJJ - George <wb5jjj@...> wrote:
I have seen this also in recent days/weeks.  I also noticed that WSJTx does NOT honor a B4 status on some stations, thus triggering the wanted status on to JTAlert.  Nothing special about the call or any other information at all.  

To test, I disconnected my log (HRD) from JTAlert and logged a fake QSO in WSJTx for the actual B4 station that I'm currently seeing, and then forced WSJTx to rescan its adif log.  That seemed to fix the problem.  In comparing the previous adif log entry for that non-B4 station and the new fake one, they appear to be identical in Notepad++.  The next time this happens, I'm going to copy the fake QSO in place of the original one, delete the fake one and then force WSJTx to do a rescan.   Will be interesting to see what happens.  

So I'm at a loss as to why WSJTx is sending it on as a wanted contact.  (Reported to the developers group)  JTAlert is apparently behaving as it should, based on the bad information it gets from WSJTx, even though I think JTAlert should have recognized the entry as a B4 itself.  

--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: Double click decode does not enable TX in WSJX

Michael Black
 

Also ensure Accept UDP requests is checked in WSJTX/Settings/Reporting

Mike W9MDB




On Friday, September 17, 2021, 10:37:17 AM CDT, Brian T Schmidt via groups.io <ni0p@...> wrote:


THX Gary. It is clicked and double click works on WSJTX but not in the JT Alert decodes window. i just did a fresh install of Windows and all my Ham software yesterday and still no double click in Decode window to TX>

VR
NI0P


locked Re: Double click decode does not enable TX in WSJX

Brian T Schmidt
 

I am also running the current version of JT Alert and WSJTX. I guess i should have stated that and Windows 10 with all the updates.

NI0P


locked Re: Double click decode does not enable TX in WSJX

Brian T Schmidt
 

THX Gary. It is clicked and double click works on WSJTX but not in the JT Alert decodes window. i just did a fresh install of Windows and all my Ham software yesterday and still no double click in Decode window to TX>

VR
NI0P


locked Re: B4 Behavior

WB5JJJ - George
 

I have seen this also in recent days/weeks.  I also noticed that WSJTx does NOT honor a B4 status on some stations, thus triggering the wanted status on to JTAlert.  Nothing special about the call or any other information at all.  

To test, I disconnected my log (HRD) from JTAlert and logged a fake QSO in WSJTx for the actual B4 station that I'm currently seeing, and then forced WSJTx to rescan its adif log.  That seemed to fix the problem.  In comparing the previous adif log entry for that non-B4 station and the new fake one, they appear to be identical in Notepad++.  The next time this happens, I'm going to copy the fake QSO in place of the original one, delete the fake one and then force WSJTx to do a rescan.   Will be interesting to see what happens.  

So I'm at a loss as to why WSJTx is sending it on as a wanted contact.  (Reported to the developers group)  JTAlert is apparently behaving as it should, based on the bad information it gets from WSJTx, even though I think JTAlert should have recognized the entry as a B4 itself.  

--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: B4 Behavior

n7eal@...
 


I've also seen a bunch of stations that I have worked, on the same band not show as B4 a few days after the contact, date is set way back in the past.

n7eal


locked Re: Double click decode does not enable TX in WSJX

n7eal@...
 


since upgrading to jtalert 2.50.6 couple days ago I also have had double clicking in Jtalert and in the wsjt-x windows stop working after a few min to a few hours, I have to close wsjt-x and re-open it and it works again, for awhile.. Dose not switch to that callsign or enable the tx.

and yes double click is set to enable tx, it's now suddenly intermittent.
wsjt-x ver 2.4.0

n7eal


locked Re: Double click decode does not enable TX in WSJX

Gary - AC6EG
 

In the WSJT-X Settings, make sure you have enabled "Double-click on call sets TX enable"  You will find this option on the "General" tab of the Settings window.


locked Re: Double click decode does not enable TX in WSJX

Brian T Schmidt
 

More info double click is enabled in the "gear" in JT Alert Decode window.


locked Double click decode does not enable TX in WSJX

Brian T Schmidt
 

In the decodes box, when I double click on a decode it does not enable TX in WSJTX.

It worked on my old computer but not this newer one. Any suggestions?

NI0P
Brian


locked Re: 2.50.6 Callsigns Window #1

Ed Wilson
 

Thanks, Laurie...I will try the exclusion idea. Other members of the group have offered additional suggestions which I will try...thanks, guys!

Ed, K0KC


locked Re: B4 Behavior

Craig
 

Hello Laurie - I wanted to confirm with you that you received the DXKeeper logfile and also the JTAlert files.  Please let me know if you need anything additional.  Thanks again for your assistance.
--
Craig
NZ4CW


locked Re: SSL/TLS failure

Michael Black
 

Do you have the 64-bit version of WSJT-X though?  That's what has to match the SSL version.

Mike W9MDB




On Wednesday, September 15, 2021, 08:20:21 PM CDT, Mike Wilson <mwilson1946@...> wrote:


I have resolved all of my issues with WSJT-X and JTAlert.  But the problem with retrieving the csv file from LoTW still issues a failure notice that SSL service is not installed. I have followed all of the recommendations, I have downloaded and installed the openSSL (64) lite package and installed it. I have uninstalled the ssl and started over. Each task I perform is followed by a restart of the PC. Nothing I do resolves the error. The PC is 64 bit. I have manually downloaded the csv and put it in the log directory but there is no indication that it is being used.

 

Any one have a suggestions?

 

 

73 de KE5WCT

Mike Wilson

Sent from Mail for Windows 10

 

 


locked SSL/TLS failure

Mike Wilson <mwilson1946@...>
 

I have resolved all of my issues with WSJT-X and JTAlert.  But the problem with retrieving the csv file from LoTW still issues a failure notice that SSL service is not installed. I have followed all of the recommendations, I have downloaded and installed the openSSL (64) lite package and installed it. I have uninstalled the ssl and started over. Each task I perform is followed by a restart of the PC. Nothing I do resolves the error. The PC is 64 bit. I have manually downloaded the csv and put it in the log directory but there is no indication that it is being used.

 

Any one have a suggestions?

 

 

73 de KE5WCT

Mike Wilson

Sent from Mail for Windows 10

 

 


locked Re: 2.50.6 Callsigns Window #1

DAVID BERNHEISEL
 

Is it possible that this could be caused by accidentally starting 2 instances of JTALERT?

If the first instance makes the config file busy, then the second instance would not have access to it.

Closing the 'wrong' instance of JTALERT might then make the 'preferred' instance a copy of the default config file.

Dave N2DPF

On 9/15/2021 2:29 PM, Laurie, VK3AMA wrote:


On 15/09/2021 11:22 pm, Ed Wilson via groups.io wrote:
I make a number of changes to the Callsigns Window #1 using the gear icon on the lower right hand of the window. I also shut down JTAlert each evening and start it up again the next morning. I find that approximately half of the time JTAlert starts with the Callsigns window reverting to its original defaults rather than to my preferred settings. I need to resize it and change to my preferred settings again which takes less than a minute but is a bit annoying. Approximately half of the time, my settings are remembered just fine.

Am I doing something wrong when I shut down JTAlert in the evening or when I launch it again in the morning?

Thanks,

Ed, K0KC

Ed, there is no special requirement for closing JTAlert or the Callsigns window. My preferred method is to simply close JTAlert and let it manage closing the other windows automatically.

When you say reverts to default does that also include the desktop position of the window?

There have been a very small number of reports of the Callsigns window being resized quite small to approx 1 inch square with its size and position locked. Is that the affect your seeing?

The Callsigns window will default to the 3-panel display, "All Decodes". "Callers" and "Alerts Only", views when the config file for the window is not found when first opening the window or if JTAlert is being prevented from reading the config file. This is a default window when opening without a config file.
���

The config file for the Callsigns window, for you, is located at %localappdata%\HamApps\JTAlert\K0KC\Config\ and is named Callsigns_1.config

Is there a possibility the file is being deleted as part of some file maintenance activity on your PC?
You may have to add an exclusion of the above directory to your PC Protection software.

de Laurie VK3AMA




--
73,
Dave, N2DPF


locked Re: 2.50.6 Callsigns Window #1

Laurie, VK3AMA
 



On 15/09/2021 11:22 pm, Ed Wilson via groups.io wrote:
I make a number of changes to the Callsigns Window #1 using the gear icon on the lower right hand of the window. I also shut down JTAlert each evening and start it up again the next morning. I find that approximately half of the time JTAlert starts with the Callsigns window reverting to its original defaults rather than to my preferred settings. I need to resize it and change to my preferred settings again which takes less than a minute but is a bit annoying. Approximately half of the time, my settings are remembered just fine.

Am I doing something wrong when I shut down JTAlert in the evening or when I launch it again in the morning?

Thanks,

Ed, K0KC

Ed, there is no special requirement for closing JTAlert or the Callsigns window. My preferred method is to simply close JTAlert and let it manage closing the other windows automatically.

When you say reverts to default does that also include the desktop position of the window?

There have been a very small number of reports of the Callsigns window being resized quite small to approx 1 inch square with its size and position locked. Is that the affect your seeing?

The Callsigns window will default to the 3-panel display, "All Decodes". "Callers" and "Alerts Only", views when the config file for the window is not found when first opening the window or if JTAlert is being prevented from reading the config file. This is a default window when opening without a config file.
   

The config file for the Callsigns window, for you, is located at %localappdata%\HamApps\JTAlert\K0KC\Config\ and is named Callsigns_1.config

Is there a possibility the file is being deleted as part of some file maintenance activity on your PC?
You may have to add an exclusion of the above directory to your PC Protection software.

de Laurie VK3AMA




locked Re: F5 chat window always "on top"

Laurie, VK3AMA
 



On 16/09/2021 3:51 am, WB5JJJ - George wrote:
Rebooting only fixed the minimize option.  The root cause was having JTA "docked" to WSJTx on top.  It was like the middle option (JTAlert always on top of other windows) was checked, which it wasn't.  I toggled it as well, and it made no difference.  But undocking solved the problem.  
--
73's
George - WB5JJJ

George,

Sounds like you have the "Follow JTAlert window" option enabled.
   

With that option set, any change in the main JTAlert window bring-forward/minimize/restore window state will be reflected in any of the other windows with the "Follow JTAlert" option set. With JTAlert docked to WSJTX and WSJTX coming to the top of other windows, JTAlert will be dragged forward  and that state change is also applied to the other "Follow JTAlert" enabled windows.

de Laurie VK3AMA


locked Re: 2.50.6 Callsigns Window #1

Dave Garber
 

I shut down, when not using ft8 or ft4, and when I restart, everything goes right where I left it


smartsdr, jtalert,wsjtx,log4om, and there sub windows

Dave Garber
VE3WEJ / VE3IE


On Wed, Sep 15, 2021 at 9:22 AM Ed Wilson via groups.io <ed.wilson=ymail.com@groups.io> wrote:
Laurie,

I make a number of changes to the Callsigns Window #1 using the gear icon on the lower right hand of the window. I also shut down JTAlert each evening and start it up again the next morning. I find that approximately half of the time JTAlert starts with the Callsigns window reverting to its original defaults rather than to my preferred settings. I need to resize it and change to my preferred settings again which takes less than a minute but is a bit annoying. Approximately half of the time, my settings are remembered just fine.

Am I doing something wrong when I shut down JTAlert in the evening or when I launch it again in the morning?

Thanks,

Ed, K0KC


locked Re: F5 chat window always "on top"

WB5JJJ - George
 

Rebooting only fixed the minimize option.  The root cause was having JTA "docked" to WSJTx on top.  It was like the middle option (JTAlert always on top of other windows) was checked, which it wasn't.  I toggled it as well, and it made no difference.  But undocking solved the problem.  
--
73's
George - WB5JJJ
Hamshack Holine #4969

921 - 940 of 37825