Date   

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


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

Andrew; KF6LU
 

Thanks Bill for quick reply.  My question though is why did the lines not appear when I downloaded v2.3 but others get them?


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

g4wjs
 

On 08/02/2021 15:28, Andrew Buza; KF6LU wrote:
I've been following topics in this group prior to upgrading to v2.3 of WSJT-x.  Downloaded v2.3 64 bit and installed.  First thing I noticed was that Outgoing interfaces and Multicast TTL lines did not appear on the Reporting screen of WSJT-x.  Attempted to make contacts and expected to receive error messages. Made FT4 and FT8 contacts on 12, 17 and 20. All contacts logged successfully to WSJT-x log, to Log4OM v-2 , my QRZ log and uploaded to LOTW by Log4OM.  All seems to be working fine without having those lines in the Reporting screen.  I see from a previous topic (JTAlert not triggering TX) that others downloaded  v2.3 and did not have the screens and had problems.  I'm at a lost as to why my download didn't have the line but still seems to be operating.  Downloaded from the Princeton site.
here's my WSJt-x screen.   I do have the Multicast on Loopback checked in JTalert.
I'll post on the WSJT-x group if no one has any ideas here.
Andrew,

nothing unexpected there, the outgoing interfaces and multicast TTL settings are only relevant if the target server is listening on a multicast group address. 127.0.0.1 is a unicast address.

73
Bill
G4WJS.



--
73
Bill
G4WJS.


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

Andrew; KF6LU
 

I've been following topics in this group prior to upgrading to v2.3 of WSJT-x.  Downloaded v2.3 64 bit and installed.  First thing I noticed was that Outgoing interfaces and Multicast TTL lines did not appear on the Reporting screen of WSJT-x.  Attempted to make contacts and expected to receive error messages. Made FT4 and FT8 contacts on 12, 17 and 20. All contacts logged successfully to WSJT-x log, to Log4OM v-2 , my QRZ log and uploaded to LOTW by Log4OM.  All seems to be working fine without having those lines in the Reporting screen.  I see from a previous topic (JTAlert not triggering TX) that others downloaded  v2.3 and did not have the screens and had problems.  I'm at a lost as to why my download didn't have the line but still seems to be operating.  Downloaded from the Princeton site.
here's my WSJt-x screen.   I do have the Multicast on Loopback checked in JTalert.
I'll post on the WSJT-x group if no one has any ideas here.


locked Re: JTAlert not working??

Morris WA4MIT
 

After a week of struggles with Alert today I finally managed to solve my problems. Today I did a computer restore to a date before I started having issues this did help some but I still was not displaying any decoded callsigns nor would 
Alert log to HRD I then went into the firewall and granted access to more parts of Alert and did a computer restart and everything went to working as it should. I still do not know what happened or why all this started but just
glad to have everything working again. 
73 Morris WA4MIT


locked Re: Transverter support #FT8

Tom Melvin
 

Lot of playing - now seems to be working ok.

I have no idea what I had wrong but all freq’s seem to match up.

Thanks for letting me know it should do it - that allowed me to move forward

Tom



On 6 Feb 2021, at 20:29, Tom Melvin <tom@...> wrote:

Hmm

I have wsjtx -> Setting -> Freq  - Station info 

Band Offset
13cms  -2,174.000 000

On main wsjt screen select 13cms from pull down - Freq Box shows 146.985   (ok it is in red as that is a beacon I am looking at)
Cat control working fine with correct offset being used for correct band etc.

When start JTAlert the freq shown on the ‘info bar - (freq, mode, logger etc) is showing 2m

Will try adding the beacon freq as a ‘valid’ mode just to see if that is what it is.
Just remember there is a agregator to monitor udp is there will run that up tomorrow.


On 6 Feb 2021, at 00:33, g4wjs <bill.8@...> wrote:

Hi Mike, Tom, and Laurie,

yes, which is exactly what it does.

Tom, have you selected the right band in WSJT-X? The band you set the IF offset for is the one you select. For example you might have -116 MHz as the offset for the 2m band in "Settings->Frequencies->Station Information". Then simply select a 2m frequency in WSJT-X and your 10m IF rig will be controlled as expected.

73
Bill
G4WJS.

On 05/02/2021 15:02, Michael Black via groups.io wrote:
Seems to me WSJT-X should be reporting the correct frequency since it knows what's going on.

Mike W9MDB




On Friday, February 5, 2021, 08:58:20 AM CST, Tom Melvin <tom@...> wrote: 


All

Not sure if this can be fixed/worked around - will depend I suspect on UDP message content

Testing a 13cm (2320) system - wsjt-x allows me to enter transverter offset so it knows what to set the rig to. 

JTAlert reports the freq the rig is set to - is there a way to get JTAlert to report rig + offset?

2320 - offset (of  -2174) gives IF of 146 - JTAlert report 2m - which is correct for the rig but not to operating freq

Tom
GM8MJV



-- 
73
Bill
G4WJS.



locked Re: JTAlert Crash After Viewing Or Changing Settings

David - AK2L
 

Laurie,

I responded too soon that the program was operating normally.

I just looked at a setting in JTAlert, but changed nothing and clicked <cancel>.  JTAlert silently quit as I previously described.

I will use the "new computer" procedure for a more complete re-install, unless you have a different suggestion.

AK2L


locked Re: Double logging when running DXKeeper and JTAlert.

Duncan Campbell
 

Problem appears to be the use of both JTAlert (DXLAB DXKEEPER Logging) and Spotcollector using WSJT-X as a spot source.  Turning off either of these stops the double logging.

73 de duncan


locked Double logging when running DXKeeper and JTAlert.

Duncan Campbell
 

I am receiving double logging when I use JTAlert with DXKeeper.  I turned off Enable DXLAB DXKeeper logging, which fixed the problem, but I lost the information at the bottom of the JTAlert Screen (Current contact and information).  Is there a way to keep the JTAlert Window with out the double logging?
73 de duncan


locked Re: I upgraded my wsjt-x and now my JTalert will not connect.

Jim N6VH
 

On 2/6/2021 6:56 PM, docdga@bellsouth.net wrote:
That was it. Thank you
Glad you got it working.

73,

Jim N6VH


locked Re: More CQ Marathon info

Phil Cooper
 

Hi Jim,

 

Not sure what is happening, but when I went on today, I am not seeing Marathon alerts for countries (well, one at least!) worked on other bands this year.

One was 3B8CW, who I hadn't worked on 15m before, but I had worked 3B8BAP on 17m, so I am now even more puzzled.

 

I didn't get a chance to check that logging entry, as I had a bit of a pile-up going, so was quickly working through that.

 

Will have to see what the coming week shows....

 

73 de Phil GU0SUP

 

-----Original Message-----
From: "Jim N6VH" <N6VH@...>
Sent: Sunday, 7 February, 2021 01:13
To: Support@HamApps.groups.io
Subject: Re: [HamApps] More CQ Marathon info

 

On 2/6/2021 2:44 PM, Phil Cooper via groups.io wrote:

Hi Jim,

 

Yes, it is in the Not Wanted list, and is not in the Wanted list.

I also re-checked all other settings, and I cannot see anything untoward.

 

73 de Phil GU0SUP

 

Since everything is set the way it should be, there shouldn't be any unwanted alerts. If they continue, something is definitely wrong. One other question. After you click the Log QSO button for any QSO, do you get a box like this? See attached picture.

73,

Jim N6VH

 

 


locked Re: JT Alert Not Triggering TX

neil_zampella
 

FWIW ... v2.4.0-RC1 is a open BETA program to help work out the issues with the new Q65 mode, and also to insure that any issues have not been introduced by adding this mode to WSJT-X.

If you use it, you are strongly encouraged to report any issues to the WSJT-X development mailing list as listed in the Release notes, and on the WSJT-X webpage.

 

Neil, KN3ILZ

3321 - 3340 of 36363