Date   

locked Re: Announcements cutoff only on 160m #FT8

HamApps Support (VK3AMA)
 

On 1/05/2018 12:42 AM, WB5JJJ wrote:
I've been running WSJT-x and JTAlert FT8 on 160m for a while.  However recently, I've noticed that the audio announcement from JTA is cut off after the first second of speech.  The sequence starts out with say Tennessee as the only contact displayed it's speaking Tena.... and Calling Me is just Call... and this ONLY happens on 160m and it is always when WSJT-x is in the TX Enable mode.  Apparently when the FT8 tones are started, the announcement is cut off.  With TX Enable disabled, the complete announcement is heard. 

However if I watch the "meter" in the Windows System Volume Mixer (by clock on the task bar), the complete announcements are still going on, just not making it to the speakers.  It looks like a conflict between JTA and WSJT-x only on 160m as all other bands are announced just fine with TX Enable active. 

Running latest versions of WSJT-x (rc4) and JTA (17) as well as HRD (806). 

George
George,

Typically the cause of Band-specific software anomalies is RF in your shack.
Is your sound card an internal or external card?

I suggest you look at running into a dummy load or wind the power right down to see if the problem persists.

Let us know what you discover.

de Laurie VK3AMA
   


locked Re: For Laurie: Alerts taking too long to appear

HamApps Support (VK3AMA)
 

On 30/04/2018 10:02 PM, jeff29754 wrote:
Hi Laurie, despite sending in three sets of session files, I've yet to recieve a response to my problem, which is ....

By the time an alert appears, the WSJT-X cycle of 15 is already in it's 6th or 7th phase, I've checked the sorting and dupe removal box in performance settings with no noticeable effect. This didn't happen before version 2.10.16. When the alerts for wanted stations appear and i click on them, they dissapear after 2 or 3 seconds and if they don't call CQ again, it's a lost opportunity to snag a wanted DXCC etc.

With respect .... can this problem PLEASE be addressed ?

Thanks in advance

Jeff M1BCM
Jeff,

I only see the one support request (from yesterday my time) in my pending queue.

What does "the WSJT-X cycle of 15 is already in it's 6th or 7th phase" mean? Are you saying that it takes 6 or 7  15 sec periods before alerts are generated for the period preceding those 6 or 7 periods? I'm confused.

I reviewed your session files. There are no exceptional delays in processing of the received decodes, while not the best, they are reasonable given your PC environment. I have no way of knowing if the decodes received are for the current period or for a past period.

BUT, I have serious concerns about PC capabilities to effectively handle the CPU-intensive FT8 wile simultaneously running Log4OM, Firefox and JTAlert plus the numerous Windows background services and you Virus protection (what is it?).

JTAlert takes a snapshot of your PC environment within 30 to 60 secs after starting, during a time when neither JTAlert or WSJT-X are actively processing decodes. That snapshot  indicates that your PC is heavily CPU and Memory loaded. Part of that snapshot...
2018-04-30 10:52:05 Memory :    Memory Load : 75 %
2018-04-30 10:52:05 Memory :      Total RAM :  3,558,512 K
2018-04-30 10:52:05 Memory :      Avail RAM :    876,044 K
2018-04-30 10:52:05 Memory : Total Pagefile :  6,442,096 K
2018-04-30 10:52:05 Memory : Avail Pagefile :  2,338,216 K
2018-04-30 10:52:05 Memory :  Total virtual :  4,194,176 K
2018-04-30 10:52:05 Memory :  Avail virtual :  3,992,600 K
......................................................................................................................................................
2018-04-30 10:52:05 CPU : X64
2018-04-30 10:52:06 CPU : Count : 2
2018-04-30 10:52:06 CPU :    #1 : 100 %
2018-04-30 10:52:06 CPU :    #2 : 100 %
2018-04-30 10:52:06 CPU : Total : 100 %

Part of the snapshot showing WSJT-X and JTAlert CPU and Memory usage...
2018-04-30 10:52:06 ......................................................................................................................................................
2018-04-30 10:52:07 Processes :    ID :   PID : CPU :  Memory (KB) : Commandline
2018-04-30 10:52:09 Processes :  9048 :   664 :   0 :       10,736 : "C:\Program Files (x86)\HamApps\JTAlert\JTAlert.exe" /wsjtx
2018-04-30 10:52:09 Processes :  3568 :  1784 :   0 :          400 : C:\WSJT\wsjtx\bin\wsjtx.exe
2018-04-30 10:52:09 Processes :  3104 :     0 :   3 :        3,992 : C:\WSJT\wsjtx\bin\jt9
2018-04-30 10:52:09 Processes :  5204 :  2044 :   0 :        7,068 : "C:\Program Files (x86)\HamApps\JTAlert\plugin\JTAlertHelper.exe"
2018-04-30 10:52:09 Processes :  7360 :   500 :   0 :        5,156 : "JTHamSpots.plugin"
2018-04-30 10:52:10 Processes :  1540 :   588 :   0 :          952 : "JTBandData.plugin"
2018-04-30 10:52:10 Processes :  7932 :   772 :   0 :        1,452 : "JTTxtMsg.plugin"
2018-04-30 10:52:10 Processes :  7140 :  5380 :   0 :        8,260 : "JTEnvironment.plugin"

With your CPU pegged at 100% during a time when WSJT-X and JTAlert are effectively idling (0% cpu usage) this is little that I can recommend, sorry.

de Laurie VK3AMA
    


locked Re: JTAlertX not auto-logging to QRZ logbook

hermit@...
 

Hi Laurie -

Mike Black and I had a phone concersation last evening abt the problem.  I think the problem is my computer caused by McAfee antivirus unimstall.  Worst resources consuming antivirus I have ever used.  I think getting rid of it is the cause - maybe registry issues.  Gonna take over another computer here and I'll see what happens.

Thanks for the help.

73

Rich KB3OMJ


From: "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...>
To: Support@HamApps.groups.io
Sent: Friday, April 27, 2018 6:03:39 PM
Subject: Re: [HamApps] JTAlertX not auto-logging to QRZ logbook

On 27/04/2018 9:01 PM, hermit@... wrote:
Hi Laurie -

I've attempted twice to send you the Configuration and Session files - the upload status bar makes one pass, then a small window pops up saying "Sending your email to HamApps Support"  "Connecting to HamApps Server"  nothing happens, just chokes up,then "Email to Support (Not Responding).

Rich

Rich,

Are you able to use your browser to connect to HamSpots.net or HamApps.com? I wonder if your public IP address is blocked at the firewall. If you cant browse those sites, send me your IP address to
direct vk3ama.ham.apps [at] gmail.com

If your not IP blocked at the firewall, then you can try manually zipping up some JTAlert files and sending them to me, not via the group but to the above address.

Use Windows File Explorer and navigate to %localappdata%\HamApps\
KB3OMJ\session\JTAlertX\ and zip-up all the files in that directory and send the resulting zip file.

de Laurie VK3AMA
   



locked Announcements cutoff only on 160m #FT8

WB5JJJ - George
 

I've been running WSJT-x and JTAlert FT8 on 160m for a while.  However recently, I've noticed that the audio announcement from JTA is cut off after the first second of speech.  The sequence starts out with say Tennessee as the only contact displayed it's speaking Tena.... and Calling Me is just Call... and this ONLY happens on 160m and it is always when WSJT-x is in the TX Enable mode.  Apparently when the FT8 tones are started, the announcement is cut off.  With TX Enable disabled, the complete announcement is heard. 

However if I watch the "meter" in the Windows System Volume Mixer (by clock on the task bar), the complete announcements are still going on, just not making it to the speakers.  It looks like a conflict between JTA and WSJT-x only on 160m as all other bands are announced just fine with TX Enable active. 

Running latest versions of WSJT-x (rc4) and JTA (17) as well as HRD (806). 

George


locked Re: Hamspots DT

Michael Black
 

Well yeah....but that doesn't show your own DT.
And a well-placed warning would be of use to the community as this is a common question/problem.

Mike




On Monday, April 30, 2018, 8:24:12 AM CDT, Jim - N4ST <newsgroup@...> wrote:


Can't you just look at your decoded signal DTs and if the majority are off, you have a timing problem?
I guess if your timing is far enough off there won't be any decoded signals, but that should be a clue.
_____________
73,
Jim - N4ST

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Michael Black via Groups.Io
Sent: Monday, April 30, 2018 00:13
To: Hamapps Groups Support <support@hamapps.groups.io>
Subject: [HamApps] Hamspots DT

Just a thought...might be nice if DT could also be reported and shown on hamspots.net.
And a line on there explaining that "If you see a majority of DT's > 1 second the your computer clock is off or you have some other timing problem".

de Mike W9MDB






locked Re: Hamspots DT

Michael Black
 

Ya' know I've never used that page.  Was always on the FT8/Chat page.  Maybe it could be added there too?

Thanks


Mike


On Monday, April 30, 2018, 5:41:12 AM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 30/04/2018 2:13 PM, Michael Black via Groups.Io wrote:
Just a thought...might be nice if DT could also be reported and shown on hamspots.net.
And a line on there explaining that "If you see a majority of DT's > 1 second the your computer clock is off or you have some other timing problem".

de Mike W9MDB
Mike,

Go to the myspots page https://hamspots.net/myspots/ the DT is already available.
Note if the spots are received from PSKReporter ("P" under the "S" column) there will be no DT.

de Laurie VK3AMA
   


locked Re: Hamspots DT

Jim - N4ST
 

Can't you just look at your decoded signal DTs and if the majority are off, you have a timing problem?
I guess if your timing is far enough off there won't be any decoded signals, but that should be a clue.
_____________
73,
Jim - N4ST

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Michael Black via Groups.Io
Sent: Monday, April 30, 2018 00:13
To: Hamapps Groups Support <support@hamapps.groups.io>
Subject: [HamApps] Hamspots DT

Just a thought...might be nice if DT could also be reported and shown on hamspots.net.
And a line on there explaining that "If you see a majority of DT's > 1 second the your computer clock is off or you have some other timing problem".

de Mike W9MDB


locked For Laurie: Alerts taking too long to appear

jeff29754 M1BCM
 

Hi Laurie, despite sending in three sets of session files, I've yet to recieve a response to my problem, which is ....

By the time an alert appears, the WSJT-X cycle of 15 is already in it's 6th or 7th phase, I've checked the sorting and dupe removal box in performance settings with no noticeable effect. This didn't happen before version 2.10.16. When the alerts for wanted stations appear and i click on them, they dissapear after 2 or 3 seconds and if they don't call CQ again, it's a lost opportunity to snag a wanted DXCC etc.

With respect .... can this problem PLEASE be addressed ?

Thanks in advance

Jeff M1BCM


locked Re: Hamspots DT

HamApps Support (VK3AMA)
 

On 30/04/2018 2:13 PM, Michael Black via Groups.Io wrote:
Just a thought...might be nice if DT could also be reported and shown on hamspots.net.
And a line on there explaining that "If you see a majority of DT's > 1 second the your computer clock is off or you have some other timing problem".

de Mike W9MDB
Mike,

Go to the myspots page https://hamspots.net/myspots/ the DT is already available.
Note if the spots are received from PSKReporter ("P" under the "S" column) there will be no DT.

de Laurie VK3AMA
   


locked Re: eQsl WSJT-x Log4OM + HRD v5

2e0keh@...
 

Laurie
Thanks for the reply  how do you multi quote on groups.io  I would like to keep replies neat and less confusing. :-}

example
Larurie  
my reply

Frode 
my reply


Regards
Pete


locked Re: eQsl WSJT-x Log4OM + HRD v5

2e0keh@...
 

Frode
Thank you for a very informative reply, this has given me several points to think about.

Regards
Pete 


locked Hamspots DT

Michael Black
 

Just a thought...might be nice if DT could also be reported and shown on hamspots.net.
And a line on there explaining that "If you see a majority of DT's > 1 second the your computer clock is off or you have some other timing problem".

de Mike W9MDB


locked JTAlert to N1MM+

Joe WB9SBD
 

When doing this,
https://hamapps.groups.io/g/Support/topic/how_to_setup_n1mm_to/10290315?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,10290315

What contest should the logger be set up to be running?

Joe WB9SBD
--

The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com


locked Re: Not getting spots I've seen

grn@...
 

Thanks Laurie,

That was the problem but no idea how it got unchecked as it just stopped reporting onhampsots while I was working stations. I know I din't touch the JTAlert settings.

73 2E0NGN


locked Re: Question for Laurie - JTAlertX's UDP Message Format Document

HamApps Support (VK3AMA)
 

On 30/04/2018 10:04 AM, RED wrote:

Hello Laurie,

My confusion lays within the JTAlertX’s: Settings à Logging à Log4OM à Log4OM UDP Server UDP Port: 2236.  I thought JTAlert might be using this port for something that it may be in direct communication with. Therefore, how is this port actually being used?

Anyway, thank you for the GIFT by providing a rebroadcast of WSJT-X UDP Messages!  I have been listening on its port using my logging program written in C# ASP.NET.  Now both my UDP listener and JTAlert can be used simultaneously.

As a background job, my logging program receives all QSOs from WSJT-X, logs these events as they occur, and stores them as records in an ODBC database.

When started as a foreground job it uploads the current JTAlert log.adi file.  During upload, it merges QRZ’s data with each log.adi record, adds log-event records as they occur, then stores all records in an ODBC database with controlled locking. (Unlike another logging program.)  For display and record editing, I am using Gridview. 

As you can see, any data ports you may have or are thinking about, I would sure like to know about them.

Thank you for all the help you are providing us!

73’s, Bob K0SIR

Bob,

Now I understand, I didn't notice the 2236 port number compared to the WSJT-X default 2237 port number.

Port 2236 is used for Log4OM logging, that is the default port for the Log4OM UDP Server (see the Log4OM help file). The UDP implementation for this port is determined by Log4OM, JTAlert is simply following the rules of the API.

de Laurie VK3AMA
   


locked Re: eQsl WSJT-x Log4OM + HRD v5

HamApps Support (VK3AMA)
 

On 28/04/2018 4:48 PM, 2e0keh@... wrote:
Hi
Can WSJT-X upload to eQsl or has it got to be done through HRD logbook Im using v5 log.

Can HRD v5 b2983 cat control with or without HRD logbook be intergrated with JTalert-x  WSJT-x and Log4OM = lot to ask but would be good ;-}

Thanks 73
Pete
_._,_._,_
Pete,

No, WSJT-X doesn't upload QSOs to any of the online logs, WSJT-X is not designed as a logger.

Your always best to use the online log uploading of your Logger.

If HRD 5 doesn't provide that facility, JTAlert has an option to upload each logged QSO to eQSL, open the Settings and navigate to the "Web Services -> Online Logbooks" section.

de Laurie VK3AMA
   


locked Re: Not getting spots I've seen

HamApps Support (VK3AMA)
 

On 30/04/2018 10:10 AM, grn@... wrote:
For over a day, I've not been getting any reports for calls I've seen but am getting reports for my calls that are spotted. I've checked the TCPIP ports and they are all OK. Anybody have any suggestions?

Thanks,
2E0NGN
OM,

I assume your referring to spots on HamSpots.net, top of the JTAlert "Settings" menu, enable "Send Spots to HamSpots.net".

de Laurie VK3AMA
   


locked Not getting spots I've seen

grn@...
 

For over a day, I've not been getting any reports for calls I've seen but am getting reports for my calls that are spotted. I've checked the TCPIP ports and they are all OK. Anybody have any suggestions?

Thanks,
2E0NGN


locked Re: Question for Laurie - JTAlertX's UDP Message Format Document

RED
 

Hello Laurie,

 

My confusion lays within the JTAlertX’s: Settings à Logging à Log4OM à Log4OM UDP Server UDP Port: 2236.  I thought JTAlert might be using this port for something that it may be in direct communication with. Therefore, how is this port actually being used?

 

Anyway, thank you for the GIFT by providing a rebroadcast of WSJT-X UDP Messages!  I have been listening on its port using my logging program written in C# ASP.NET.  Now both my UDP listener and JTAlert can be used simultaneously.

 

As a background job, my logging program receives all QSOs from WSJT-X, logs these events as they occur, and stores them as records in an ODBC database.

 

When started as a foreground job it uploads the current JTAlert log.adi file.  During upload, it merges QRZ’s data with each log.adi record, adds log-event records as they occur, then stores all records in an ODBC database with controlled locking. (Unlike another logging program.)  For display and record editing, I am using Gridview. 

 

As you can see, any data ports you may have or are thinking about, I would sure like to know about them.

 

Thank you for all the help you are providing us!

 

73’s, Bob K0SIR

Rochester, MN EN34rb

K0SIR@...

HTTP://K0SIR.COM

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Sunday, April 29, 2018 4:34 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Question for Laurie - JTAlertX's UDP Message Format Document

 

On 30/04/2018 1:49 AM, RED wrote:

I’m assuming the JTAlertX “Message Format” document would not be identical, therefore, that is the one I need. 

de Bob K0SIR

Bob,

JTAlert is acting as a UDP Server, simply waiting for received UDP traffic from a connected UDP client (WSJT-X). WSJT-X defines the message format that is used, not JTAlert. JTAlert has to follow the format defined by WSJT-X other wise nothing would work.

What is JTAlert doing that makes you think that it is using its own message format? I'm somewhat confused by your request.

de Laurie VK3AMA
   


locked Re: Font Size for JTAlert latest version for WSJT-X

HamApps Support (VK3AMA)
 

On 30/04/2018 9:17 AM, k6vib@q.com wrote:
Is there a way to reduce the screen size of JTAlert callsign boxes or the font size to accomplish same?
OM,

Increase the number of Callsign displayed (via the View menu) will effectively reduce the size of the individual callsign boxes.

If your wanting to reduce the horizontal size of the JTAlert window, that is not possible with JTAlert V2. JTAlert V3 (still under development and many months away from release) has no restrictions on the Window size.

de Laurie VK3AMA
   

18621 - 18640 of 38532