Date   

locked Re: IC7300-WSJT-X Keying Problem

Guy G4DWV 4X1LT
 

Hi Dean,

I have no problems here. If you could post a screenshot of your Settings > radio tab here, I am sure that we could nail it. Also, please let me gave any details of any other programs (loggers, Omni rig etc) that you have interacting with WSJT-X.

If you want faster reply, you could email me too. Please post to the group too so that the solution, even if it does not come from me, can be posted too for the common good.

73 de Guy G4DWV 4X1LT


locked Re: Wanted States Problem

Bill Stott W4XK
 

Laurie,
Thanks for the reply and the ideas to try. I did a Windows restart right after my original post with no difference.
I will try the other steps this afternoon when I have time to work on it, and will report back afterwards.

Thanks agn,
Bill W4XK


locked Re: ADIF log scan saying all needed

Dani YO5LD
 

Hello Stephen,

That's quite a workaround, which is strange that it's needed..
I have two days before I go QRT because of job/studies, I hope this will be fixed when I'm back to chasing DXCC and WAS..
Thanks,
Dani
YO5LD

2017-12-31 6:20 GMT+02:00 <stephen.smith@...>:

I have figured out a workaround for this, although I still don't know what is causing it.  There are two parts to the work around.  One involves altering a downloaded LoTW ADIF file to where JTAlertX is happy with it. The other involves some a subtle use case that will get JTAlertX to actually "Scan Log and Rebuild" the ADIF file.  It appears that several new fields are required in order to parse the Wanted States correctly. For example, the tags <FREQ_RX:7>3.57465<RST_RCVD:3>5NN<RST_SENT:3>5NN<QSO_COMPLETE:1>Y (and appropriate values) are all required or it skips the QSO.  There also cannot be comments after the STATE line, although comments on other lines seem to be OK.  I wrote a simple python script to adjust the LoTW ADIF file shown below (alter accordingly for your file and path)....

# -*- coding: utf-8 -*-
 
import os
fname=os.path.normpath("C:/Users/stephen/Desktop/lotwreport31Dec2017.adi")
foutname=os.path.normpath("C:/Users/stephen/Desktop/jtalertlog31Dec2017.adi")
 
out = open(foutname, "w")
# Write out a header to match a new JTAlertX log
out.write("<ADIF_VER:5>2.2.7\n<ProgramID:8>JTAlertX\n<ProgramVersion:6>2.10.7\n<APP_JTAlertX_Created:23>2016/12/20 20:33:58 UTC\n<EOH>\n")
 
eoh = 0 # to mark when we have scanned in the end of the header
with open(fname, "r") as f:
    for line in iter(f):
        # Skip lines until eoh is reached
        if not eoh:     
            if '<eoh>' in line:
                eoh = 1
        else:
            #  Make the RX freq match the freq as FREQ_RX is required
            if '<FREQ:' in line:
                out.write(line)
                out.write(line.replace('<FREQ:','<FREQ_RX:'))
            elif '<STATE:' in line:
                out.write(line.split(sep='/')[0]) # State cannot have // comments
            elif not '<' in line:
                print('Removed blank line') #blank lines not allowed?
            # Add extra lines JTAlertX requires now. RSTs are dummy 5NNs for now
            elif '<eor' in line:
                out.write("<RST_RCVD:3>5NN\n<RST_SENT:3>5NN\n<QSO_COMPLETE:1>Y\n<EOR>\n")
            elif '<APP_LoTW_EOF>' in line:
                out.write("\n") #blank lines allowed at end of file
            else:
                out.write(line)
f.close()
out.close()

After you have created the file, here is how you get JTAlertX to scan it (I know for a fact that it used to scan just fine, but my installation won't now unless I do this). First, open the well-adjusted ADIF file in WordPad (trust me, we are using this to cache the file as we are about to overwrite it). Click on Setting, Manage Settings, Logging, Standard ADIF File. Click "Create New" and select the well-adjusted ADIF file. Click Save.  A dialog will open that says Do you want to replace it.  Click Yes, but do not click "OK" in the next dialog box that comes up. Next, open Windows Explorer, navigate to C:\Users\<username>\AppData\Local\HamApps\KK4TJP\logs\JTAlertX and delete the *.sqlite file that is in the directory. Go to the WordPad window that still has the well-adjusted ADIF file cached and click save.  Now, click the "OK" in the Log File dialog box from earlier. JTAlertX will rebuild the sqlite file now.  Don't get in a hurry as this could take a minute.  My sqlite file was on the order of 600k when it was finished.
Now in the JTAlertX setting window, go to Scan Log and Rebuild and click Scan All and it will parse the file.  If it seems like it works, hit OK-Apply.

Once again, this is just a work around. I'm hoping a much more straightforward solution is easily obtainable.

73,
Stephen (KK4TJP)



locked New JTAlert 2.10.8 Available - ARRL Grid Chase + Fixes. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

New JTAlert 2.10.8 is available for download. *** Please review the Release Notes ***

IMPORTANT: ARRL 2018 Grid Chase participants need to use this version.
See the Help File, "Tutorials -> ARRL International Grid Chase 2018" topic for Grid Chase setup.

Visit HamApps.com for the download link and upgrade instructions.

Release Notes for 2.10.8
  Changes:
    - Decodes History Statistics refresh interval changed from once a minute to
       four times per minute inline with the FT8 T/R 15 second periods.

  Fixes:
    - Intermittent Callsign double-clicks not being conveyed to WSJT-X.
       (Tnx to Mike W9MDB for the testing and the inspired suggestion for a
        change in JTAlert UDP handling that resulted in the fix.)
    - Intermittent failure to log QSOs to Log4OM.
    - Decodes History FT8 counts displaying the JT9 counts.
    - Decodes History Callsign alert colors not matching the alert colors of
       the JTAlert callsigns display area. (2.10.4 defect)
    - Frequencies above 23cm incorrectly logged.
    - WSJT-X UDP Communications error message when opening the Settings soon
       after starting JTAlert (< 15 secs).
    - Wanted Grids Scan Log for the ARRL 2018 International Grid Chase event
       not resetting the worked grids list at the start of each calendar month.
    - Worked Callsigns still triggering the Wanted Grid alert despite showing
       the B4 when the Grid Chase event is enabled.

de Laurie VK3AMA


locked Re: Text message working?

HamApps Support (VK3AMA)
 

On 31/12/2017 2:09 PM, k4gok@... wrote:
Laurie,
Does the auto close timeout work on incoming messages, or only on the messages I am sending out?  Mine had been set for 20 seconds (defalut I think), but incoming messages were very short.  Too short for me to react to.   I did send myself a test message and a reply, inwhich the 20 seconds worked great.
Marion,   K4GOK
Marion,

Yes it does, just now tested with a 60 sec timeout.
Note the countdown to the left of the Reply button.

   

Does the countdown when it first appears match the value you have set in the Settings?

de Laurie VK3AMA
   


locked #Announcement : ARRL 2018 Grid Chase and JTAlert 2.10.7 / 2.10.8 #Announcement

HamApps Support (VK3AMA)
 

While the current release of JTAlert (2.10.7) has support for the Grid Chase there are some issues with B4 alerting when the Grid Chase is enabled. These were only discovered today as I was finalising the instructions to be published here in the forum.

People can still use 2.10.7 starting from Jan-1 2018 UTC for the Chase (you will need to execute a
Wanted Grids Scan Log after the start of the new UTC year). You will likely experience incorrect B4 alerting as you start to work new grids. These will have to be ignored. There is no penalty if you work someone again on the same band.

If you stay with 2.10.7 after 2.10.8 is released you will need to upgrade before the start of the new Month (February) after which 2.10.7 Wanted Grid Log Scans will not be reset and you will no longer get accurate alerts with all grids for the new month still showing as B4s when they should all be alerted as needed.

I expect to release JTAlert 2.10.8 later today or early tomorrow my local time which will still be before the start of the new 2018 UTC Year. 2.10.8 will have the all changes in place to fix the incorrect B4 alerting of Grid Chase Grids and a comprehensive Grid Chase setup tutorial in the Help file.

I hope all that wasn't too confusing.

de Laurie VK3AMA
   


locked Re: ADIF log scan saying all needed

radiodriven@...
 

I have figured out a workaround for this, although I still don't know what is causing it.  There are two parts to the work around.  One involves altering a downloaded LoTW ADIF file to where JTAlertX is happy with it. The other involves some a subtle use case that will get JTAlertX to actually "Scan Log and Rebuild" the ADIF file.  It appears that several new fields are required in order to parse the Wanted States correctly. For example, the tags <FREQ_RX:7>3.57465<RST_RCVD:3>5NN<RST_SENT:3>5NN<QSO_COMPLETE:1>Y (and appropriate values) are all required or it skips the QSO.  There also cannot be comments after the STATE line, although comments on other lines seem to be OK.  I wrote a simple python script to adjust the LoTW ADIF file shown below (alter accordingly for your file and path)....

# -*- coding: utf-8 -*-
 
import os
fname=os.path.normpath("C:/Users/stephen/Desktop/lotwreport31Dec2017.adi")
foutname=os.path.normpath("C:/Users/stephen/Desktop/jtalertlog31Dec2017.adi")
 
out = open(foutname, "w")
# Write out a header to match a new JTAlertX log
out.write("<ADIF_VER:5>2.2.7\n<ProgramID:8>JTAlertX\n<ProgramVersion:6>2.10.7\n<APP_JTAlertX_Created:23>2016/12/20 20:33:58 UTC\n<EOH>\n")
 
eoh = 0 # to mark when we have scanned in the end of the header
with open(fname, "r") as f:
    for line in iter(f):
        # Skip lines until eoh is reached
        if not eoh:     
            if '<eoh>' in line:
                eoh = 1
        else:
            #  Make the RX freq match the freq as FREQ_RX is required
            if '<FREQ:' in line:
                out.write(line)
                out.write(line.replace('<FREQ:','<FREQ_RX:'))
            elif '<STATE:' in line:
                out.write(line.split(sep='/')[0]) # State cannot have // comments
            elif not '<' in line:
                print('Removed blank line') #blank lines not allowed?
            # Add extra lines JTAlertX requires now. RSTs are dummy 5NNs for now
            elif '<eor' in line:
                out.write("<RST_RCVD:3>5NN\n<RST_SENT:3>5NN\n<QSO_COMPLETE:1>Y\n<EOR>\n")
            elif '<APP_LoTW_EOF>' in line:
                out.write("\n") #blank lines allowed at end of file
            else:
                out.write(line)
f.close()
out.close()

After you have created the file, here is how you get JTAlertX to scan it (I know for a fact that it used to scan just fine, but my installation won't now unless I do this). First, open the well-adjusted ADIF file in WordPad (trust me, we are using this to cache the file as we are about to overwrite it). Click on Setting, Manage Settings, Logging, Standard ADIF File. Click "Create New" and select the well-adjusted ADIF file. Click Save.  A dialog will open that says Do you want to replace it.  Click Yes, but do not click "OK" in the next dialog box that comes up. Next, open Windows Explorer, navigate to C:\Users\<username>\AppData\Local\HamApps\KK4TJP\logs\JTAlertX and delete the *.sqlite file that is in the directory. Go to the WordPad window that still has the well-adjusted ADIF file cached and click save.  Now, click the "OK" in the Log File dialog box from earlier. JTAlertX will rebuild the sqlite file now.  Don't get in a hurry as this could take a minute.  My sqlite file was on the order of 600k when it was finished.
Now in the JTAlertX setting window, go to Scan Log and Rebuild and click Scan All and it will parse the file.  If it seems like it works, hit OK-Apply.

Once again, this is just a work around. I'm hoping a much more straightforward solution is easily obtainable.

73,
Stephen (KK4TJP)


locked Re: Text message working?

Marion D. Kitchens
 

Laurie,
Does the auto close timeout work on incoming messages, or only on the messages I am sending out?  Mine had been set for 20 seconds (defalut I think), but incoming messages were very short.  Too short for me to react to.   I did send myself a test message and a reply, inwhich the 20 seconds worked great.
Marion,   K4GOK
 
On Sun, 31 Dec 2017 10:16:06 +1100 "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...> writes:

On 30/12/2017 11:43 PM, Kenneth Miller wrote:
Hi Gary, that was me. I was doing 3 things at once and did not see your reply until this morning. One thought, I believe the default setting for the text message window is to disappear after a few seconds. That used to bug me because the message would disappear sometimes while I was still reading it. I remember the setting was not too easy to find, in fact, I just looked through the settings and could not find it at all. Anyway, I somehow set my text window to stay open after a message so that I need not be staring at the screen all of the time. That might be a big part of the problem,

Ken K6WGX
The Text Message window can be set to remain open or auto close with a timeout between 10 secs to 180 secs.
The settings are easily found under the "Web Services" section of the Settings window.

   

de Laurie VK3AMA
   
 


locked Re: Wanted States Problem

HamApps Support (VK3AMA)
 

On 30/12/2017 1:06 PM, William Stott via Groups.Io wrote:
Tonight I was browsing my LoTW confirmations and decided that a 5BWAS was a worthy goal so I attempted to set up
wanted states in JTAlert. Everything worked exactly as I expected.......EXCEPT I cannot set a wanted state on 20 meters.
If I check one state (I only need one on 20) it still says I need 0 of 50. If I check all it says I need 50 of 50. If I then uncheck
1 state it says I need 0 of 50, but leaves 49 boxes checked. Saving and exiting does nothing. I have restarted JTAlert but
no difference.

Running v2.10.5 with WSJT-x v1.8.0 , Windows 10 Home Edition.  Any Ideas??????

Bill  W4XK

Bill,

Something is not right. The needed count display is automatically altered whenever a State checkbox is clicked. The count update code is directly tied into the click event handler for the checkboxes. I can't reproduce that behaviour no matter how hard I try. There have been no other reports of this behaviour.

When you restart JTAlert and open the Settings, without clicking any of the State checkboxes, is the needed count correct and matching the number of checkboxes ticked or is there still a mismatch? Does it match waht was displayed prior to the restart of JTAlert or is it different?

Have you performed a Windows "Restart" (not Reboot)? If not try that. If that still doesn't correct the problem, Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis.

de Laurie VK3AMA
   


locked Re: Trinidad and Tobago

HamApps Support (VK3AMA)
 

On 30/12/2017 9:40 AM, Kevin Utzy wrote:
More of a curiosity than a problem.  I notice that when JTAlert displays a 9Y or 9Z call, the country does not display.  I've gotten use to it, but sometimes I think it might be special until I look again.

Like I said, just wondering.

73,
Kevin
KX4KU
Kevin,

I need
some specific Callsigns to check.
I can't fault it here in my tests, eg
9Y4AA and 9Z4AA work correctly.

de Laurie VK3AMA
   


locked Re: Text message working?

w4ihi3
 

Thank you everyone for response and help. Thank you also Laurie for specific input.  I did send a message to myself and it did come back and I was able to respond to it.  It must be working. I also reset the time out for the text message drop down.  TNX again and hope everyone has a Blessed 2018
73,
Gary W4IHI


On Saturday, December 30, 2017 6:16 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 30/12/2017 11:43 PM, Kenneth Miller wrote:
Hi Gary, that was me. I was doing 3 things at once and did not see your reply until this morning. One thought, I believe the default setting for the text message window is to disappear after a few seconds. That used to bug me because the message would disappear sometimes while I was still reading it. I remember the setting was not too easy to find, in fact, I just looked through the settings and could not find it at all. Anyway, I somehow set my text window to stay open after a message so that I need not be staring at the screen all of the time. That might be a big part of the problem,

Ken K6WGX
The Text Message window can be set to remain open or auto close with a timeout between 10 secs to 180 secs.
The settings are easily found under the "Web Services" section of the Settings window.

   

de Laurie VK3AMA
   



locked Re: anyone has integrated N1MM and WSJT-X and JTAlert?

HamApps Support (VK3AMA)
 

On 30/12/2017 5:19 AM, Alan Muldawer wrote:
I don't know if this has been covered but has anyone has integrated N1MM and WSJT-X and JTAlert? I have it setup but I can't get the log data go from WSJT-X to go into N1MM. Any help would be much appreciated. 

73
Alan N3ALN

JTAlert can be used to automatically log QSOs to N1MM+ (must be running) while still using one of the other supported loggers for all the Wanted alerts and B4 checks.

JTAlert has a special DXPedition mode (I don't recommend using) that is documented in the Help file, "Tutorials -> DXPedition Mode with N1MM+ logging" section. Ignore the first part of that help page and look to the second part  titled "To Setup N1MM+ to monitor and log the JTAlert Last QSO Logged UDP broadcast." to correctly setup N1MM+ to monitor the last QSO logged UDP packet from JTAlert.

Note: N1MM+ is a contest logger, not a general purpose logger and lacks many data fields needed for JTAlert which is why it is not one of the supported loggers.

de Laurie VK3AMA
   


locked Re: anyone has integrated N1MM and WSJT-X and JTAlert?

Gerald Wilson
 

Alan    N3ALN,

You say, "Never mind, I figured it all out!"

Is your solution to integrating N1MM+ and WSJT-X & JTAlert the same as advised by Kevin KX4KU or is it a different solution to the same result?

Another interested inquiring party,
73,

   Jerry    K7VIT



On 12/29/2017 19:53, Alan Muldawer wrote:
Never mind, I figured it all out! Like the needle in the haystack! I works!

73
Alan N3ALN


locked Re: JTAlert Won't Start

kk5aa_fred
 

AWESOME!!!

THANK YOU!!


locked Re: IC7300-WSJT-X Keying Problem

Richard Griest_N4RWG
 

Contact N7BD Don.  He has the 7300 and is very active in FT8.

Regards,
Richard Griest - N4RWG

On Dec 30, 2017 6:03 PM, "roamer" <roamer@...> wrote:

I am going crazy!  Try as I might I can’t get  my 7300 to go into xmit when it should.  I have altered (methodically) every setting I can think of but alas, no fix.  It sometimes works once but not for 2 xmisslons.

 

Any Ideas?

 

Dean Norris. K7NO

 


locked Re: Vertical Listing

HamApps Support (VK3AMA)
 

On 31/12/2017 9:13 AM, JohnB wrote:
Laurie,

After using JTDX with band activity turned on, I find that it's easier to read down the list of callsigns and locations rather reading across as displayed in JTAlert.  Maybe it's because the callsigns are closer together.  Maybe because more callsigns are in my field of vision.  For whatever reason, I prefer vertical.   Have you ever considered having the option of listing the callsigns vertically?

. . . John (WA3CAS)
John,

A vertical display will be available with JTAlert V3 (still months away from release). The V3 Callsign window will be user-sizable to any shape you want, vertical, horizontal, full screen, etc.

There will be no vertical display with the current V2 code, sorry.

de Laurie VK3AMA
   


locked Re: Text message working?

HamApps Support (VK3AMA)
 

On 30/12/2017 11:43 PM, Kenneth Miller wrote:
Hi Gary, that was me. I was doing 3 things at once and did not see your reply until this morning. One thought, I believe the default setting for the text message window is to disappear after a few seconds. That used to bug me because the message would disappear sometimes while I was still reading it. I remember the setting was not too easy to find, in fact, I just looked through the settings and could not find it at all. Anyway, I somehow set my text window to stay open after a message so that I need not be staring at the screen all of the time. That might be a big part of the problem,

Ken K6WGX
The Text Message window can be set to remain open or auto close with a timeout between 10 secs to 180 secs.
The settings are easily found under the "Web Services" section of the Settings window.

   

de Laurie VK3AMA
   


locked Re: Text message working?

HamApps Support (VK3AMA)
 

On 30/12/2017 9:36 AM, w4ihi3 wrote:
I have sent several text messages out via JTAlertX(with latest update) but have not received a reply back from anyone since Dec 16th.  This is unusual as I often received replies back. Any thoughts? Maybe everyone turned them off or no one likes be anymore so won't respond HI
Thots
73,
Gary W4IHI
Gary,

You can test that messages are working by sending a message to your self. You won't get an instant reply, there will be a delay until the next check by JTAlert to see if you have a waiting message (the check is done 4 times per minute).

de Laurie VK3AMA
   


locked IC7300-WSJT-X Keying Problem

roamer
 

I am going crazy!  Try as I might I can’t get  my 7300 to go into xmit when it should.  I have altered (methodically) every setting I can think of but alas, no fix.  It sometimes works once but not for 2 xmisslons.

 

Any Ideas?

 

Dean Norris. K7NO

 


locked Vertical Listing

JohnB
 

Laurie,

After using JTDX with band activity turned on, I find that it's easier to read down the list of callsigns and locations rather reading across as displayed in JTAlert.  Maybe it's because the callsigns are closer together.  Maybe because more callsigns are in my field of vision.  For whatever reason, I prefer vertical.   Have you ever considered having the option of listing the callsigns vertically?

. . . John (WA3CAS)

19741 - 19760 of 37815