Date   

locked Re: WSJT-X v2.4.0-rc1 Q65

HamApps Support (VK3AMA)
 

On 11/02/2021 2:08 pm, William Thomas wrote:

When using the new Q65 mode, I only see my call letters displayed in JTAlert, not the station I’m working.  Another operator told me they are seeing the same thing. 


73 Bill WT0DX


At the time of the current 2.16.17 JTAlert release (December 6  2020) my "Crystal Ball" was in the shop for repair so I was unable to foresee the availability of the new Q65 mode with the release of WSJT-X 2.4.0-rc1 which occurred on February 3 2021, just shy of 2 months after the current JTAlert release.

The first I became aware of Q65 was in the release announcement of 2.4.0-rc from the post by K1JT. See https://sourceforge.net/p/wsjt/mailman/wsjt-devel/thread/4e54822e-3f67-c564-dd32-0ff13d486715%40princeton.edu/#msg37211965

The next release of JTAlert recognizes Q65 decodes.

de Laurie VK3AMA



locked Re: B4 Issue #FT8

Dave Garber
 

did you confirm that the operator was never at el09, before changing it.  he may have been portable somewhere, which may mean the entry was correct, and you needed the grid after all..

Dave Garber
VE3WEJ / VE3IE


On Thu, Feb 11, 2021 at 12:24 PM Charlie Hoffman <hoffmanc@...> wrote:
Dave had the correct answer for my case.

I found that the B4 grid information was pulled from my own local logbook (HRDLog)
while the grid info in the lower screen is what is actually decoded.  As soon as I changed
my old HRD log entry from EL09 to DM91, I no longer received an alert.

I don't know why the B4 grid location is not pulled from the XML lookup location.
What is the purpose of me specifying WEB/XML lookup location as QRZ and providing a password?
When does JTAlert use the XML lookup feature and what is it used for?

I need more training ....


locked Re: B4 Issue #FT8

Charlie Hoffman
 

Dave had the correct answer for my case.

I found that the B4 grid information was pulled from my own local logbook (HRDLog)
while the grid info in the lower screen is what is actually decoded.  As soon as I changed
my old HRD log entry from EL09 to DM91, I no longer received an alert.

I don't know why the B4 grid location is not pulled from the XML lookup location.
What is the purpose of me specifying WEB/XML lookup location as QRZ and providing a password?
When does JTAlert use the XML lookup feature and what is it used for?

I need more training ....


locked Re: Voice Alerts for 'POTA'?

Patrick Hung
 

I like your workaround, and will use it till the feature is added (if it's added).
--
73,

Patrick - W6AJR


locked Re: WSJT-X v2.4.0-rc1 Q65

Hasan Schiers N0AN
 

You won't see them in the Grid Display until Laurie adds them. If you are using JTA with a logging program, when call the station in X, it will show up with Call, Name, Grid etc
73, N0AN
Hasan


On Thu, Feb 11, 2021 at 7:29 AM neil_zampella <neilz@...> wrote:

I'm not sure if Laurie has Q65 setup in JT-Alert, many of the EME modes (outside of JT65/JT9) are not covered either.   

Neil, KN3ILZ


locked Re: WSJT-X v2.4.0-rc1 Q65

neil_zampella
 

I'm not sure if Laurie has Q65 setup in JT-Alert, many of the EME modes (outside of JT65/JT9) are not covered either.   

Neil, KN3ILZ


locked Decode Window Does Not Completely Update

Marlo Montanaro - KA2IRQ
 
Edited

Hi - 

V2.16.17 on Win10, I would have receive going while I was surfing the web.  I'd hear the alert for a new DXCC entity, and I would quickly open the Decode window to see what was there.  I sometimes do not see anything highlighted, indicating the alert.

Hmmmmm.

Then I would open JTAlert's main screen and I would see the highlighted callsign there.

At the end of the *next* cycle, as stations start to populate the decode window, the alert will show up there, usually with two other lines (total of three).  It always seems to be if the alert was in the top 3 lines of the decode window, it *may* not show up at the end of the proper time slot.  It always shows up in the correct time slot (as indicated by the alternating colors of each time slot), just a bit late.


73,

Marlo- KA2IRQ


locked WSJT-X v2.4.0-rc1 Q65

William Thomas
 

When using the new Q65 mode, I only see my call letters displayed in JTAlert, not the station I’m working.  Another operator told me they are seeing the same thing. 


73 Bill WT0DX


locked Re: B4 Issue #FT8

Cleon Rose
 

I was having the same problem. Laurie had me change the alert filter to no QSL and it solved it. 

Cleon WA7RCT


locked Voice Alerts for 'POTA'?

Glen Jenkins WB4KTF
 

Is there an easy way to create a VOICE ALERT in JTAlert what could vocalize "WANTED POTA" (the O vowel is a 'long' O).  Now with many hams activating Parks on The Air, they are sending "CQ POTA CALLSIGN".  I'd like the software to let me know.  I did set up (added the CALL POTA) a visual alert/highlighting of CQs that contain POTA, using the alert for a WANTED CALLSIGN, but it says "Wanted Call"..
Could this be a possible addition to a future release?
--
Glen, WB4KTF, Austin, TX


locked Re: B4 Issue #FT8

Dave Garber
 

the difference i see is you qso before reports a different grid than whan the k5 station is sending.   the dark green is grid wanted, i believe.  that is why the alert.  

Dave Garber
VE3WEJ / VE3IE


On Wed, Feb 10, 2021 at 1:15 AM Charlie Hoffman <hoffmanc@...> wrote:
I'm having a problem with the B4 filter.
I have it turned on so that I should not see any calls worked B4.
It does not always work correctly.
I also have CQ alerts turned on.
Some calls are still highlighted as a new CQ call even when shows on the same page as worked B4 like the call K5DGC
in this capture.  This is not the first time this has happened.   I've called stations and had them tell me that I worked them B4.
It's embarrassing...
Is this a bug or is there a setting that I need to change.


locked B4 Issue #FT8

Charlie Hoffman
 

I'm having a problem with the B4 filter.
I have it turned on so that I should not see any calls worked B4.
It does not always work correctly.
I also have CQ alerts turned on.
Some calls are still highlighted as a new CQ call even when shows on the same page as worked B4 like the call K5DGC
in this capture.  This is not the first time this has happened.   I've called stations and had them tell me that I worked them B4.
It's embarrassing...
Is this a bug or is there a setting that I need to change.


locked SL

Cleon Rose
 

Tnx Laurie for your quick response.  That solved it.  Changed to no QSL filters and all is well.
73, Cleon


locked Re: Worked B4

HamApps Support (VK3AMA)
 

On 10/02/2021 8:27 am, Cleon Rose via groups.io wrote:
Hi.  Maybe some can help me.  In the screen shot I've outlined KD8PGL.  I worked him about 10 minutes ago and now he doesn't show as worked B4.  Also, his call is not showing in JTAlert.  The decoded count shows 5, but in JTAlert there are only 4 callsigns omitting KD8PGL.  This has been a regular occurrence since I downloaded the latest versions.  Any suggestions?  Or is this a flaw in the latest version of either WSJT-X or JTAlert?  
Thanks
Cleon WA7RCT

Did KD8PGL show in JTAlert prior to your working him, I suspect not.
The difference in WSJT-X decode counts and the displayed Callsigns count in JTAlert is because you have one or more Alert Filters engaged. Note the word  "Filter" in the JTAlert title-bar.

Looking at what Callsigns did display, my guess is that your have a QSL type filter enabled. I note that KD8PGL is not known to QSL via either LoTW or Eqsl, so having one of those as an active Filter will cause his Callsign to not be displayed.

No Flaws in either WSJT-X or JTAlert, just operator error, IMO.

de Laurie VK3AMA


locked Worked B4

Cleon Rose
 

Hi.  Maybe some can help me.  In the screen shot I've outlined KD8PGL.  I worked him about 10 minutes ago and now he doesn't show as worked B4.  Also, his call is not showing in JTAlert.  The decoded count shows 5, but in JTAlert there are only 4 callsigns omitting KD8PGL.  This has been a regular occurrence since I downloaded the latest versions.  Any suggestions?  Or is this a flaw in the latest version of either WSJT-X or JTAlert?  
Thanks
Cleon WA7RCT


locked Virus reported by Bitdefender

James Gill
 

I had just installed a new version of Bitdefender, my virus software on Win10.

Last night it reported a virus in JTAlert: Gen:Suspicious.Cloud.2.2.BC2DFCC4000. The file was quarantined. I attempted to reinstall from the setup file, but the virus report was repeated. I then downloaded the latest version and attempted to install it on my C drive. (It was previous installed on my G). The virus alert was repeated.

I had seen the virus checks that HamApps does so I submitted a "false positive" report to Bitdefender. They will get back to me in 3 days.

I had been thinking about moving JTAlert and WSJT-X to my C drive because it is an SSD and should be faster. I had been avoiding using it because it was always full. I had worked on moving things off the C drive so it appears now to have room. So, I will need some advice or direction to help files on how to recreate whatever files, databases etc. JTAlert uses.

I will report back when I hear from Bitdefender.

73s

Jim - W4GMU


locked Re: v2.16.17 build 0023

Michael Black
 

We got Dwight working by moving his monitor with JTAlert to above another monitor and then the window magically adjusted itself to stay inside the monitor border...I thought we would be able to see the bottom of the window so we could click the gear icon but the window readjusted itself.  The window move doesn't work when the window position is locked.

I think we need a keyboard shortcut to open the settings on all the new windows so we can make it easier to fix this in the future.

Mike W9MDB




On Tuesday, February 9, 2021, 10:54:43 AM CST, Dwight Bosselman <ns9i@...> wrote:


also doing a Alt-SPacebar-M won't give me the special little cursor either

On 2/9/2021 7:44 AM, Michael Black via groups.io wrote:
Hover your mouse over the JTAlert icon your task bar.
Then right-click the Messaging window and selecvt "Move".
Place the special cursor that appears over the Messaging window -- click and drag.

Then click the gear icon in the bottom right corner and you'll probably see "position locked" selected.  You may want to disasble that.

Mike W9MDB




On Tuesday, February 9, 2021, 07:00:50 AM CST, Dwight Bosselman <ns9i@...> wrote:


Messaging window is stuck at the bottom of the screen, 1/2 below the
bottom edge, and nothing will move it anywhere.

73 Dwight NS9I








locked Re: WSJT-x v2.3 installed; No Outgoing interfaces or Multicast TTL; but working

Ron W3RJW
 
Edited

Perhaps the others were already using multicast in which case it will be used.

The program does not know. As soon as you enter a multicast address the other lines will appear.  You can go back and forth whenever you want.  You do not have to reinstall the program, just change the adr.
--
73
Ron, W3RJW


locked Re: WSJT-x v2.3 installed; No Outgoing interfaces or Multicast TTL; but working

Andrew; KF6LU
 

Ron;  I am confused as to why when some downloaded v2.3 the Outgoing interfaces and the Multicast TLL "lines" appeared in the Setting, Reporting screen of WSJT-x.
But when I installed the  program they were not there.  When running the install program how does the program know I'm running a "multicast or unicast:?
If I later decide to change my UDP server to say 239.255.0.1 do I then have to reinstall v.2.3.    Sorry I'm not fully understanding the program.


locked Re: WSJT-x v2.3 installed; No Outgoing interfaces or Multicast TTL; but working

Ron W3RJW
 

Buza,

I'm confused  What "lines" are you looking for ?   If you want to use multicast then you have enter a multicast address in WSJT-X.  

Unicast still works just fine (127.0.0.1) if you have no need for multicast (I don't).  Uncheck the option for multicast in JTAlert.

I am using JTDX 2.3.0, JTAlert 2.16.17 and HRD.
--
73
Ron, W3RJW

3401 - 3420 of 36454