Date   

locked Re: Need help with this error message

Anthony W. DePrato
 

GARY
Before you upgrade open your settings in wsjt-x and go to the freq's tab
and highlight and save to your desktop all the freqs, as the new version
does not install them. you can copy them to your new version later.
73 Tony WA4JQS.

In WSJT-X File/Settings/Reporting turn on the 3 UDP checkboxes under
"Network Services"

And you should upgrade to the final relase of 1.8.0 instead of the
release candidate. http://physics.princeton.edu/pulsar/K1JT/wsjtx.html

de Mike W9MDB


locked F5 Key fails to create the message screen. Have to close and restart app.

Walt Flesher, W6SA
 

First of all, Thank You for this great software.

Just found and signed up for the group.

I've been using JTAlert-X since I discovered WSJT-X and FT8. 

I update every time I see the Update notice and I am on the latest version.  Version makes no difference as this has been an ongoing issue for some time.

I checked out the prior messages regarding this issue.  The Thread was locked after 10/21/17, apparently, with no resolutiion.

I always make sure the window is active before clicking F5.  I often have a series of messages with a particular station and at some point it occasionally fails to generate a message form.

Is this a bug that still needs to be resolved or just a glitch on my end that I will need to accept?

It is mostly a minor inconvenience in most instances but occasionally it becomes a time critical issue.

Thanks.

Walt, W6SA





locked Re: Need help with this error message

Michael Black
 

In WSJT-X File/Settings/Reporting turn on the 3 UDP checkboxes under "Network Services"

And you should upgrade to the final relase of 1.8.0 instead of the release candidate.



de Mike W9MDB



On Monday, January 22, 2018, 1:37:04 PM CST, qww334 via Groups.Io <qww334@...> wrote:


I just started JTalert.

This is the error message I am getting

Unable to communicate with the WSJT-X process.

  UDP Port : 2237

  IP Address : 127.0.0.1

  Values read from WSJT-X config file...

    C:\Users\qww33\AppData\Local\WSJT-X\WSJT-X.ini

 

WSJT-X Detected Instance...

  Process Window Title : WSJT-X   v1.8.0-rc1   by K1JT

  Process Command Line : "C:\Users\qww33\Desktop\FT8\wsjtx\bin\wsjtx.exe"

 

Decode alerts and logging will be unavailable until corrected.

Need help on how to correct it

Tks

Gerry

K1NY


locked Re: Need help with this error message

Brian (N2MLP)
 

Open  UDP Port : 2237 in wsjt-x program

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of qww334 via Groups.Io
Sent: Monday, January 22, 2018 2:11 PM
To: Support@HamApps.groups.io
Subject: [HamApps] Need help with this error message

 

I just started JTalert.

This is the error message I am getting

Unable to communicate with the WSJT-X process.

  UDP Port : 2237

  IP Address : 127.0.0.1

  Values read from WSJT-X config file...

    C:\Users\qww33\AppData\Local\WSJT-X\WSJT-X.ini

 

WSJT-X Detected Instance...

  Process Window Title : WSJT-X   v1.8.0-rc1   by K1JT

  Process Command Line : "C:\Users\qww33\Desktop\FT8\wsjtx\bin\wsjtx.exe"

 

Decode alerts and logging will be unavailable until corrected.

Need help on how to correct it

Tks

Gerry

K1NY


locked Need help with this error message

Gerry S
 

I just started JTalert.

This is the error message I am getting

Unable to communicate with the WSJT-X process.

  UDP Port : 2237

  IP Address : 127.0.0.1

  Values read from WSJT-X config file...

    C:\Users\qww33\AppData\Local\WSJT-X\WSJT-X.ini

 

WSJT-X Detected Instance...

  Process Window Title : WSJT-X   v1.8.0-rc1   by K1JT

  Process Command Line : "C:\Users\qww33\Desktop\FT8\wsjtx\bin\wsjtx.exe"

 

Decode alerts and logging will be unavailable until corrected.

Need help on how to correct it

Tks

Gerry

K1NY


locked JTAlert logging to N3FJP VHF Contest Log

Rick Hall
 

Running in the ARRL VHF contest this weekend I was pleasantly surprised that I could directly log WSJT-X digital QSOs via JTAlert to N3FJP's VHF Contest Log software.  
All of the QSO information was properly added to the VHF Contest Log, however in each case JTAlert issued a 'failed to log' popup window.  Is there something that needs to be added or changed so that JTAlert will issue a 'log successful' popup when logging to the VHF Contest Log instead of ACLog?   Or am I missing a setting?   
Thanks,
Rick - K5GZR 


locked No Decode problem

Jason N3YUG
 

I am using WSJT-X 1.8.0 RC2 and the latest JTAlerts 2.10.10.  I setup on a band and start decoding with just WSJT-X on, and am decoding 10-13 stations per block, as soon as I turn on JTAlert, it stops decoding.  I opened up the settings on JTAlert, and things started decoding, but as soon as I close the settings, it quits decoding again. The strange thing is with JTAlerts on the waterfall even looks messed up.  Any ideas?

Jason
N3YUG


locked Re: jt alert question

Anthony W. DePrato
 

At 05:42 AM 1/21/2018, you wrote:
On 22/01/2018 12:49 PM, Anthony W. DePrato wrote:
i sent you the files tonight. from jt alert. saw that the config and session files were auto loaded great ideal.. thanks for any help.. or advise.
73 Tony WA4JQS

Tony,

Your config shows that you don't have the "Log Address returned from an XML or previous QSO lookup" option enabled. See the JTAlert Settings, Logging section.

Also, in your original message you indicated you were running the latest WSJT-X. That does not appear to be the case. Your session files show you running 1.8.0 rc1. The fist release candidate. There were 3 release candidates with many changes, optimisations and fixes before the final general release. You should be running the 1.8.0 release.

de Laurie VK3AMA
   


  Laurie 
   thank you very much for the info. thought i had the programs all up to date.. guess i need to check more often which i will start doing.. again thank you very much for a great program and your help.. i see what is going on with the updates now the RC-1 ect. i was looking only at ver 1.8 again thanks for the help
   have a great week\
   73 Tony WA4JQS
._,_._,_

Anthony W.DePrato WA4JQS since 1962
CQ DX HALL OF FAME  # 35
DXCC HONOR ROLL
DXPEDITION OF THE YEAR 1992 VP8SSI
DXPEDITION OF THE YEAR 1993/1994 3Y0PI
VP8SSI 3Y0PI VP8BZL V31SS ZD8JQS
 WA4JQS/ZS1 WA4JQS/KC4 WA4JQS/4K1


locked Re: jt alert question

HamApps Support (VK3AMA)
 

On 22/01/2018 12:49 PM, Anthony W. DePrato wrote:
i sent you the files tonight. from jt alert. saw that the config and session files were auto loaded great ideal.. thanks for any help.. or advise.
73 Tony WA4JQS

Tony,

Your config shows that you don't have the "Log Address returned from an XML or previous QSO lookup" option enabled. See the JTAlert Settings, Logging section.

Also, in your original message you indicated you were running the latest WSJT-X. That does not appear to be the case. Your session files show you running 1.8.0 rc1. The fist release candidate. There were 3 release candidates with many changes, optimisations and fixes before the final general release. You should be running the 1.8.0 release.

de Laurie VK3AMA
   


locked Re: jt alert question

Anthony W. DePrato
 

At 11:41 PM 1/19/2018, you wrote:
On 20/01/2018 3:31 AM, Anthony W. DePrato wrote:

   Laurie
   i have gone to the web settings and  qrz.com on line XML service is checked and my log in and password are set. it showed the  box below that last look up was jan 18th with no error messages. it still does not populate the address box on dxkeeper ect. also when the wsjt-x log box pops up after i send 73 i have to copy and paste the operators name from jt alert to the wsjt-x log box is this correct ? .
like your program very much. just figure i am missing something in the setup.
73 Tony wa4jqs / vp8bzl
Tony,

Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis. Only the most recent 24hours of activity is retained in the session files, so don't wait too long before sending.
   
de Laurie VK3AMA
 Laurie:

i sent you the files tonight. from jt alert. saw that the config and session files were auto loaded great ideal.. thanks for any help.. or advise.
73 Tony WA4JQS

Anthony W.DePrato WA4JQS since 1962
CQ DX HALL OF FAME  # 35
DXCC HONOR ROLL
DXPEDITION OF THE YEAR 1992 VP8SSI
DXPEDITION OF THE YEAR 1993/1994 3Y0PI
VP8SSI 3Y0PI VP8BZL V31SS ZD8JQS
 WA4JQS/ZS1 WA4JQS/KC4 WA4JQS/4K1


locked Re: jt alert question

Anthony W. DePrato
 

At 11:41 PM 1/19/2018, you wrote:
On 20/01/2018 3:31 AM, Anthony W. DePrato wrote:

   Laurie
   i have gone to the web settings and  qrz.com on line XML service is checked and my log in and password are set. it showed the  box below that last look up was jan 18th with no error messages. it still does not populate the address box on dxkeeper ect. also when the wsjt-x log box pops up after i send 73 i have to copy and paste the operators name from jt alert to the wsjt-x log box is this correct ? .
like your program very much. just figure i am missing something in the setup.
73 Tony wa4jqs / vp8bzl
Tony,

Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis. Only the most recent 24hours of activity is retained in the session files, so don't wait too long before sending.
   
de Laurie VK3AMA
 Laurie:

i sent you the files tonight. from jt alert. saw that the config and session files were auto loaded great ideal.. thanks for any help.. or advise.
73 Tony WA4JQS

Anthony W.DePrato WA4JQS since 1962
CQ DX HALL OF FAME  # 35
DXCC HONOR ROLL
DXPEDITION OF THE YEAR 1992 VP8SSI
DXPEDITION OF THE YEAR 1993/1994 3Y0PI
VP8SSI 3Y0PI VP8BZL V31SS ZD8JQS
 WA4JQS/ZS1 WA4JQS/KC4 WA4JQS/4K1


locked Re: JT Alert X 2.10.7 won't log to HRD logbook 6.4

HamApps Support (VK3AMA)
 



On 22/01/2018 12:15 PM, Robert De Forge via Groups.Io wrote:
Laurie,
    The strange thing is that when I had the problem in December (virus protection) the data is the same as todays. I had printed both out then and now. Same trouble. Some where there is a door that the information can't get thru. So If I have this correct JT Alert X is seeing HRD and sending the WSJT X log information to HRD. The trouble is HRD isn't logging it and returning a confirmation. Does this sound correct? Is there any way to run a pathway/ping test to see where it stops? Any thing else I could check?
73
Bobby  KC2BBI
The text... "Ham Radio Deluxe Version Release 6.4.0.787
[c] Found 33 Valid Fields...
Added 33 Fields to KC2BBI..."

is the response from HRDLogbook.
This response is telling JTAlert that HRDLogbook logged the QSO. This response also confirms that the TCP communications channel between JTAlert and HRDLogbook is working.

Your correct, HRD is at fault for not logging the QSO, despite its acknowledgement that it wrote the data to its log. This defect was first identified and reported
over 2 years ago to HRDLLC and has been reported many times since.

Despite this positive response of logging success, JTAlert ignores that response and performs its own lookup of the logbook to confirm if the QSO was indeed logged and logged with the correct data. JTAlert is only recording the response for diagnostic purposes and was done as a means of providing evidence to the HRD LLC that their logging API is buggy (and still is).

FWIW, JTAlert performs this direct log read, as a logging confirmation check, rather than relying on any data received back fro the logger, for all the supported loggers (DXKeeper, HRD, ACLog, Log4OM, and ADIF).

de Laurie VK3AMA
   


locked Re: JT Alert X 2.10.7 won't log to HRD logbook 6.4

Robert De Forge
 

Laurie,
    The strange thing is that when I had the problem in December (virus protection) the data is the same as todays. I had printed both out then and now. Same trouble. Some where there is a door that the information can't get thru. So If I have this correct JT Alert X is seeing HRD and sending the WSJT X log information to HRD. The trouble is HRD isn't logging it and returning a confirmation. Does this sound correct? Is there any way to run a pathway/ping test to see where it stops? Any thing else I could check?
73
Bobby  KC2BBI
 
 

-----Original Message-----
From: Laurie, VK3AMA <hamapps.support@...>
To: Support <Support@HamApps.groups.io>
Sent: Sun, Jan 21, 2018 6:29 pm
Subject: Re: [HamApps] JT Alert X 2.10.7 won't log to HRD logbook 6.4


On 22/01/2018 10:21 AM, Robert De Forge via Groups.Io wrote:
Laurie,
    They all show like this:
[c] [c]
2018-01-21 15:44:12 __logqso_HRD() : FAILURE : Repeating check
2018-01-21 15:44:14 __logqso_HRD() : FAILURE : Unable to confirm QSO logged
2018-01-21 16:15:02 __logqso_HRD() : Send : db add "KC2BBI" {CALL="AD5XD" DXCC="291" COUNTRY="United States" QSO_DATE="20180121" QSO_DATE_OFF="20180121" TIME_ON="161315" TIME_OFF="161415" FREQ="14075963" FREQ_RX="14075964" BAND="20m" BAND_RX="20m" MODE="FT8" RST_SENT="+11" RST_RCVD="-05" GRIDSQUARE="EM12px" DISTANCE="2100" TX_PWR="30" LAT="N032 58.750" LON="W096 42.500" COMMENT="FT8  Sent: +11  Rcvd: -05" NAME="Milton O Withers" QTH="Richardson" STATE="TX" CNTY="Dallas" CQZ="5" ITUZ="6" PFX="AD5" CONT="NA" MY_LAT="40.5" MY_LON="-75" MY_GRIDSQUARE="FN20" MY_CQ_ZONE="5" MY_ITU_ZONE="8" STATION_CALLSIGN="KC2BBI" }
2018-01-21 16:15:03 __logqso_HRD() : Received : Ham Radio Deluxe Version Release 6.4.0.787
[c] Found 33 Valid Fields...
Added 33 Fields to KC2BBI...
    Laurie your program has worked  fantastic. This was out of the blue trouble. It happened only after Microsoft updates. I ran virus protection and nothing was found or quarantined. I also turned off firewall and virus protect with no change in current problem.
 
Bobby KC2BBI

Bobby,

That last entry shows that HRDLogbook responded ("Received : Ham Radio Deluxe Version Release 6.4.0.787
[c] Found 33 Valid Fields...
Added 33 Fields to KC2BBI...") to the JTAlert logging command. If HRDLogbook didn't log the QSO despite responding that it added the fields indicates a problem with HRD.

de Laurie VK3AMA
   


locked Re: JT Alert X 2.10.7 won't log to HRD logbook 6.4

Laurie, VK3AMA
 


On 22/01/2018 10:21 AM, Robert De Forge via Groups.Io wrote:
Laurie,
    They all show like this:
[c] [c]
2018-01-21 15:44:12 __logqso_HRD() : FAILURE : Repeating check
2018-01-21 15:44:14 __logqso_HRD() : FAILURE : Unable to confirm QSO logged
2018-01-21 16:15:02 __logqso_HRD() : Send : db add "KC2BBI" {CALL="AD5XD" DXCC="291" COUNTRY="United States" QSO_DATE="20180121" QSO_DATE_OFF="20180121" TIME_ON="161315" TIME_OFF="161415" FREQ="14075963" FREQ_RX="14075964" BAND="20m" BAND_RX="20m" MODE="FT8" RST_SENT="+11" RST_RCVD="-05" GRIDSQUARE="EM12px" DISTANCE="2100" TX_PWR="30" LAT="N032 58.750" LON="W096 42.500" COMMENT="FT8  Sent: +11  Rcvd: -05" NAME="Milton O Withers" QTH="Richardson" STATE="TX" CNTY="Dallas" CQZ="5" ITUZ="6" PFX="AD5" CONT="NA" MY_LAT="40.5" MY_LON="-75" MY_GRIDSQUARE="FN20" MY_CQ_ZONE="5" MY_ITU_ZONE="8" STATION_CALLSIGN="KC2BBI" }
2018-01-21 16:15:03 __logqso_HRD() : Received : Ham Radio Deluxe Version Release 6.4.0.787
[c] Found 33 Valid Fields...
Added 33 Fields to KC2BBI...
    Laurie your program has worked  fantastic. This was out of the blue trouble. It happened only after Microsoft updates. I ran virus protection and nothing was found or quarantined. I also turned off firewall and virus protect with no change in current problem.
 
Bobby KC2BBI

Bobby,

That last entry shows that HRDLogbook responded ("Received : Ham Radio Deluxe Version Release 6.4.0.787
[c] Found 33 Valid Fields...
Added 33 Fields to KC2BBI...") to the JTAlert logging command. If HRDLogbook didn't log the QSO despite responding that it added the fields indicates a problem with HRD.

de Laurie VK3AMA
   


locked Re: JT Alert X 2.10.7 won't log to HRD logbook 6.4

Robert De Forge
 

Laurie,
    They all show like this:
[c] [c]
2018-01-21 15:44:12 __logqso_HRD() : FAILURE : Repeating check
2018-01-21 15:44:14 __logqso_HRD() : FAILURE : Unable to confirm QSO logged
2018-01-21 16:15:02 __logqso_HRD() : Send : db add "KC2BBI" {CALL="AD5XD" DXCC="291" COUNTRY="United States" QSO_DATE="20180121" QSO_DATE_OFF="20180121" TIME_ON="161315" TIME_OFF="161415" FREQ="14075963" FREQ_RX="14075964" BAND="20m" BAND_RX="20m" MODE="FT8" RST_SENT="+11" RST_RCVD="-05" GRIDSQUARE="EM12px" DISTANCE="2100" TX_PWR="30" LAT="N032 58.750" LON="W096 42.500" COMMENT="FT8  Sent: +11  Rcvd: -05" NAME="Milton O Withers" QTH="Richardson" STATE="TX" CNTY="Dallas" CQZ="5" ITUZ="6" PFX="AD5" CONT="NA" MY_LAT="40.5" MY_LON="-75" MY_GRIDSQUARE="FN20" MY_CQ_ZONE="5" MY_ITU_ZONE="8" STATION_CALLSIGN="KC2BBI" }
2018-01-21 16:15:03 __logqso_HRD() : Received : Ham Radio Deluxe Version Release 6.4.0.787
[c] Found 33 Valid Fields...
Added 33 Fields to KC2BBI...
    Laurie your program has worked  fantastic. This was out of the blue trouble. It happened only after Microsoft updates. I ran virus protection and nothing was found or quarantined. I also turned off firewall and virus protect with no change in current problem.
 
Bobby KC2BBI
 
 

-----Original Message-----
From: HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
To: Support <Support@HamApps.groups.io>
Sent: Sun, Jan 21, 2018 4:24 pm
Subject: Re: [HamApps] JT Alert X 2.10.7 won't log to HRD logbook 6.4

On 22/01/2018 6:17 AM, Robert De Forge via Groups.Io wrote:
Hello to all,
      My trouble is my QSO will log to WSJT X 1.8.0 logbook but won't allow JT Alert X 2.10.7 to log it to HRD 6.4 logbook. I had the same problem in December after a Microsoft Defender security update shut it down because it thought it was a threat. I found files quarantined. After a few Defender update this problem was solved. Everything has been running smooth. I was going to update to the latest JT Alert at the end of the month. As of today I am back to 1/21/18 I am having the logging trouble again. My last working QSO that entered was on 1/18/18 22:29 UTC. Since then I have had 3 three Defender updates and two other Microsoft quality rollup for net framework/ windows 7 64bit. Today I am getting the  failure QSO not logged. Error due to defect in HRD logbook. I don't believe either program is responsible for the problem right now. The Microsoft update is but I can't find out what happened. All firewall setting look ok. Any ideas? Any help will be very much appreciated.
73
Bobby  KC2BBI
Bobby,

Is JTAlert recording any errors in the HRDLogbook trace file?

The file can be opened using a text editor like notepad and for you can be found here...
%localappdata%\HamApps\KC2BBI\session\JTAlertX\HRDLogbook.trace

What do the last dozen lines of that file show?

de Laurie VK3AMA
   


locked Re: JT Alert X 2.10.7 won't log to HRD logbook 6.4

Robert De Forge
 

Hi Steve,
   At this point no issue with HRD logbook closing. It may be a Windows 10 issue but I am still using Windows 7. I will keep a look out for any activity like that.
Bobby KC2BBI 

Sent from my iPod

On Jan 21, 2018, at 2:47 PM, Steve R via Groups.Io <oldjavadrinker@...> wrote:

Bobby,

Question? Does your HRD logbook randomly close sometimes? There is a fix for this in the HRD reflector. I posted it again today having to do with Windows 10 Build update 1709. One needs to change the properties in the HRDlogbook.exe
The logbook is closing and when you try to send the log entry from JT Alerts to HRD it cannot find the log because it is no longer open. 

Not sure if your problem is the same but it might be worth a try and run the recommended change from HRD Support. Although my issue was a bit different from yours, it did take care of the problem.

Steve
KM4FLF
VA3FLF


locked Re: JT Alert X 2.10.7 won't log to HRD logbook 6.4

HamApps Support (VK3AMA)
 

On 22/01/2018 6:17 AM, Robert De Forge via Groups.Io wrote:
Hello to all,
      My trouble is my QSO will log to WSJT X 1.8.0 logbook but won't allow JT Alert X 2.10.7 to log it to HRD 6.4 logbook. I had the same problem in December after a Microsoft Defender security update shut it down because it thought it was a threat. I found files quarantined. After a few Defender update this problem was solved. Everything has been running smooth. I was going to update to the latest JT Alert at the end of the month. As of today I am back to 1/21/18 I am having the logging trouble again. My last working QSO that entered was on 1/18/18 22:29 UTC. Since then I have had 3 three Defender updates and two other Microsoft quality rollup for net framework/ windows 7 64bit. Today I am getting the  failure QSO not logged. Error due to defect in HRD logbook. I don't believe either program is responsible for the problem right now. The Microsoft update is but I can't find out what happened. All firewall setting look ok. Any ideas? Any help will be very much appreciated.
73
Bobby  KC2BBI
Bobby,

Is JTAlert recording any errors in the HRDLogbook trace file?

The file can be opened using a text editor like notepad and for you can be found here...
%localappdata%\HamApps\KC2BBI\session\JTAlertX\HRDLogbook.trace

What do the last dozen lines of that file show?

de Laurie VK3AMA
   


locked #Warning #JTDX - Bad Mode Spotting to PSKReporter from JTDX #JTDX

HamApps Support (VK3AMA)
 

Please be advised, Current builds of JTDX are producing Bad Mode spots, FT8 spotted as T10,JT9 or JT65 sent direct to PSKReporter.

It appears that if a user is monitoring FT8 activity and changes their mode to T10/JT9/JT65 the next group of FT8 decodes is posted to PSKReporter with the new incorrect mode.

I have been seeing many of these bad mode spots on HamSpots recently and upon closer investigation they are all coming in via the PSKReporter feed and are from JTDX. I have not seen this with WSJT-X users posting to PSKReporter. This appears to be a design defect within JTDX.
 
JTAlert is not affected by this as it ignores the first batch of decodes received after a JTDX/WSJT-X mode change.

de Laurie VK3AMA
    


locked New JTAlert 2.10.10 Available. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

New JTAlert 2.10.10 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.10
  New Features:
    - Works with new 5.4 version of JT65-HF HB9HQX Edition.
       (Important Note: Only JT65-Log, the default, is supported)
    - Option to ignore warning and continue to log QSO when Logged Callsign is
       different from Current QSO Partner Callsign (or DX CAll cleared).
       (Default: OFF, Settings Section: Logging)

  Changes:
    - Many code tweaks & optimizations to improve repsonsiveness and
       facilitate defect diagnosis.

  Fixes:
    - With Grid Chase enabled, some Callsigns may not be detected as a B4,
       resulting in possible inappropriate alerting or non-alerting.

de Laurie VK3AMA


locked Re: JT Alert X 2.10.7 won't log to HRD logbook 6.4

Robert De Forge
 

I don't think that will help. I definitely won't hurt either . My last problem occurred  with 2.10.6. I stuck with that until the problem was solved then upgraded to 2.10.7. Nothing changed same HRD, JT Alert X and WSJT X. Need have some ideas before updating.
Bobby KC2BBI 



Sent from my Samsung device

-------- Original message --------
From: Mike Anderson <mike@...>
Date: 1/21/18 2:43 PM (GMT-05:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JT Alert X 2.10.7 won't log to HRD logbook 6.4

I believe you will  have to update to the latest  2.10.9   now to be
functional


Mike K5NAN




18761 - 18780 of 37225