Date   

locked Re: JTDX issues with latest JTAlert release. #JTDX

HamApps Support (VK3AMA)
 

On 13/07/2021 8:44 am, Alan Sorum WL7CG wrote:
I downloaded the 64bit version. Looking a the Task Manager, JTAlert comes and goes.

Alan WL7CG

I think you mean JTAlertV2.Manager.exe comes and goes, is that correct? You would not have been able to get to the "Help -> About" menu if JTAlert is not running.

I am running the 64bit version here without problem on 2 PCs.

Sounds like your Protection software is interfering. What are you using, is it MS Defender? If so, try forcing an update of its definitions files. JTAlert was submitted yesterday to MS for Virus/Malware analysis and they confirmed it to be infection free but did include a note to ensure definitions are up-to-date.

de Laurie VK3AMA


locked 2.50.3 Intalled but not worked

Masaaaki Maeda
 
Edited

_Lurie,

I installed newest version. But call sign window does not appear, even dropdown menu has stars. Message window comes appear periodically.

Over all very slow. (sound does not appear too)  Framewok check is ok. (.NET 5.0.7 X64)
I am using WSJT-X. If I go to Program update, at first all error but click Check for update, it fixed. 

Where should I change?

 

Masa

JR1AQN

 


locked Re: JTDX issues with latest JTAlert release. #JTDX

Alan Sorum WL7CG
 

I downloaded the 64bit version. Looking a the Task Manager, JTAlert comes and goes.

Alan WL7CG


locked Re: JTDX issues with latest JTAlert release. #JTDX

HamApps Support (VK3AMA)
 

On 13/07/2021 8:35 am, Alan Sorum WL7CG wrote:
Additionally, I can't open the "About" window.

Alan WL7CG

An inability to open the About window, and the other 2.50.x windows, Callsigns, Activity, BandHeat & Messaging is a clear indication that the JTAlertV2.Manager.exe process is not running. What does TaskManager show? Is it not running or perhaps stopping & starting every couple of seconds?

What bit version of JTAlert did you install, the 64bit (x64) or the 32bit (x86)?

de Laurie VK3AMA


locked Re: JTDX issues with latest JTAlert release. #JTDX

Alan Sorum WL7CG
 

Additionally, I can't open the "About" window.

Alan WL7CG


locked Re: Logging Wrong Rcv Freq to DXKeeper

HamApps Support (VK3AMA)
 

On 13/07/2021 7:38 am, Dale Drake wrote:
Please take save your unhelpful comments for another group.

I'll decide who can post to this group and the types of messages and their content.
This topic is now locked.

de Laurie VK3AMA


locked JTDX issues with latest JTAlert release. #JTDX

Alan Sorum WL7CG
 

All,

I upgraded to the newest version of JTAlert (2.50.3). The first thing I noticed is the Callsigns Window (F3) is gone. I'm not getting at decodes as well, the Decodes Window (F4) is blank. I tried changing the TCP and UDP numbers in JTDX, but I'm fairly sure I have them wrong now. I looked at the help files for the 2.50 upgrade, but haven't found anything that looks like the new callsigns window yet. I'm hoping to use the alerts for POTA stations, if I can get this to work.

Any hints would be appreciated. Thanks.

73 Alan WL7CG


locked Re: Logging Wrong Rcv Freq to DXKeeper

HamApps Support (VK3AMA)
 

On 13/07/2021 7:28 am, Joe Subich, W4TV wrote:
Because *WSJTX* ONLY REPORTS ONE FREQUENCY.  If you have a problem
with that take it up with the developers of WSJTX.  Note: *UPDATE*
to WSJTX 2.4.0 (the current release level) *BEFORE* reporting any
"BUG".

JTAlert can only report what WSJTX gives it.

73,

   ... Joe, W4TV

Exactly!
JTAlert logs what it receives .

WSJT-X does not provide separate tx & rx frequencies in the logging data.

An examination of the wsjt_log.adi file shows that only a single frequency is recorded, <freq> which per the adif standard is the TX frequency. The Dial + Tx offset. eg a test QSO logged, dial = 7.074, Tx offset = 3000Hz giving a Tx freq of 7.077000
<call:6>VK3AMA <gridsquare:0> <mode:3>FT8 <rst_sent:0> <rst_rcvd:0> <qso_date:8>20210712 <time_on:6>220931 <qso_date_off:8>20210712 <time_off:6>220931 <band:3>40m <freq:8>7.077000 <station_callsign:6>VK3AMA <my_gridsquare:6>QF22PF <eor>

JTAlert does not use the
wsjt_log.adi file for logging, it uses the "QSO Logged" UDP message.
Note the absence of separate Tx, Rx or Dial frequencies fields. Just a single "Tx frequency (Hz)" field which is the same as the adi file, Dial + Tx offset.
 * QSO Logged    Out       5                      quint32
 *                         Id (unique key)        utf8
 *                         Date & Time Off        QDateTime
 *                         DX call                utf8
 *                         DX grid                utf8
 *                         Tx frequency (Hz)      quint64
 *                         Mode                   utf8
 *                         Report sent            utf8
 *                         Report received        utf8
 *                         Tx power               utf8
 *                         Comments               utf8
 *                         Name                   utf8
 *                         Date & Time On         QDateTime
 *                         Operator call          utf8
 *                         My call                utf8
 *                         My grid                utf8
 *                         Exchange sent          utf8
 *                         Exchange received      utf8

de Laurie VK3AMA


locked Re: No decodes form WSJT-X showing in JTALERT-X call sign line

HamApps Support (VK3AMA)
 

On 13/07/2021 7:42 am, lmeeny wrote:
I still haven't determined the cause of the on again off again working combination of Flexradio & WSJT-X. However when I'm in the failed state closing all the software and powering off the PC then restarting gets me running again. Rather than tie myself in knots I've decided to enjoy operating before chasing the root cause of the fault.

Thank you,

Ed W2GHD

Ed,

What happens if you simply restart the applications without the PC restart? Do you still experience the failed condition?

de Laurie VK3AMA


locked Re: 2.50.3 problems

HamApps Support (VK3AMA)
 

On 13/07/2021 7:47 am, Andy k3wyc wrote:
I installed 2.50.3 and cannot display any "Views" from View menu. Clicking Callsigns, Messaging, Activity, or Band heat opens no windows.  

If I install 2.50.0 all Views are displayable.  If I re-install 2.50.3 no Views are displayable.

Is this a know issue and, if so, what is the solution.

Thanks and 73,
Andy, k3wyc

Andy,

Not a known issue. If it was I would never have posted the new release. Neither myself nor the Test Team have observed this problem.

Please post an image of the 2.50.3 Callsigns window showing the no views state. Also include in that image the Callsigns window Options popup open to the "Panels" section.

de Laurie VK3AMA


locked Re: New JTalert 2.50.3 missing callsign window

 

I am having the same problem.  I installed the recommended .NET v5 Desktop framework, but when I look in the registry, I don't see it.  Odd.  Thoughts?

73, Greg, KM5GT


locked Re: I know I did it before? - - change color of new grid spots

 

Yes, that changes the new "DX Callsign" block for new grids, but how do you change the "Grid" block for new grids so they are the same color. 


locked New JTalert 2.50.3 missing callsign window

Tom Hone AA0GP
 

Installed JTALERT 2.50.3 64 bit version on windows 10 and now have no callsign window, I do have main window of alerts, settings etc……..I reloaded the download three times with same results



AA0GP
Tom Hone
tom@cowboytom.com
www.cowboytom.com





--
Tom Hone
AA0GP
tom@cowboytom.com


locked 2.50.3 problems

Andy k3wyc
 

I installed 2.50.3 and cannot display any "Views" from View menu. Clicking Callsigns, Messaging, Activity, or Band heat opens no windows.  

If I install 2.50.0 all Views are displayable.  If I re-install 2.50.3 no Views are displayable.

Is this a know issue and, if so, what is the solution.

Thanks and 73,
Andy, k3wyc


locked try to post

Tom Hone AA0GP
 

Can I get approved to posting, having problems with new JTALERT?

AA0GP
Tom Hone
tom@cowboytom.com
www.cowboytom.com





--
Tom Hone
AA0GP
tom@cowboytom.com


locked Re: No decodes form WSJT-X showing in JTALERT-X call sign line

lmeeny
 

I still haven't determined the cause of the on again off again working combination of Flexradio & WSJT-X. However when I'm in the failed state closing all the software and powering off the PC then restarting gets me running again. Rather than tie myself in knots I've decided to enjoy operating before chasing the root cause of the fault.

Thank you,

Ed W2GHD


locked Re: Logging Wrong Rcv Freq to DXKeeper

Dale Drake
 

having dispatched that.  I have managed to get the .NET 5.0 running on my PC and now have the latest versions of JTAlert and WSJT-X running but the problem persists.


locked Re: Logging Wrong Rcv Freq to DXKeeper

Dale Drake
 

Jim,  Maybe I like my log to be accurate.  Please take save your unhelpful comments for another group.


locked Re: Logging Wrong Rcv Freq to DXKeeper

Jim Cooper
 

On 12 Jul 2021 at 14:01, Dale Drake wrote:

If my dial freq is 50.313 and I'm
listening on 500Hz audio and
transmitting on 2500 Hz audio JTAlert
should show my xmt as 50.315.5 and
my  rcv as either 50.313 or 50.3135
but it doesn't.
WHY on Earth does it even matter ???
other than uptight, nit-picking?


locked Re: Logging Wrong Rcv Freq to DXKeeper

Joe Subich, W4TV
 

On 2021-07-12 5:01 PM, Dale Drake wrote:

So why does JTAlert list my xmt freq as the rcv freq if I'm running split in FT8 in WSJT-X? If my dial freq is 50.313 and I'm listening
on 500Hz audio and transmitting on 2500 Hz audio JTAlert should
show my xmt as 50.315.5 and my rcv as either 50.313 or 50.3135 but
it doesn't.
Because *WSJTX* ONLY REPORTS ONE FREQUENCY. If you have a problem
with that take it up with the developers of WSJTX. Note: *UPDATE*
to WSJTX 2.4.0 (the current release level) *BEFORE* reporting any
"BUG".

JTAlert can only report what WSJTX gives it.

73,

... Joe, W4TV


On 2021-07-12 5:01 PM, Dale Drake wrote:
Okay, so none of the comments so far have helped me solve my problem.  I know that JTAlert creates a 1 QSO ADIF file that includes both the xmt and rcv freq that is read by DXKeeper and it is logged as presented.  So why does JTAlert list my xmt freq as the rcv freq if I'm running split in FT8 in WSJT-X?  If my dial freq is 50.313 and I'm listening on 500Hz audio and transmitting on 2500 Hz audio JTAlert should show my xmt as 50.315.5 and my  rcv as either 50.313 or 50.3135 but it doesn't.

1761 - 1780 of 37662