Date   

locked Re: multiple instances JTAlert #HRD

ON5UN
 

Dear Laurie,

 

First of all, my apologies for not replying faster, but I have been abroad until  Monday.

 

I have followed your very clear instructions and that seems to work fine, however I have one question.

In the second identity wsjt-x , when I open the log directory, I cannot see a wsjtx_log file and several other files I see the first identity directory are also missing such as call3 old, timer out etc..Where should I copy the second identity wsjtx_log.adi file so the second XSTT-X instance will show also correct info and colors?

 

Rest me to say : BIG Thank you to you, you are an example for Ham spirit and a Ham with a very big “H

 

73 de Erwin, ON5UN

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Friday, November 3, 2017 11:09 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] multiple instances JTAlert #HRD

 

On 4/11/2017 8:55 AM, HamApps Support (VK3AMA) wrote:

Now that you have new XYL specific shortcuts for WSJT-X and JTAlert do the following...

  • Start WSJT-X using the XYL shortcut.
  • Open the WSJT-X Settings and setup as required, being sure to specific the XYL Callsign. You will need to adjust other settings, Radio, Audio, etc. (as they will be the defaults, they are not copied from your original setup.
  • Leave WSJT-X running.
  • Start JTAlert.
  • Open the JTAlert Settings and setup the HRD logging to use the XYL log.
  • Adjust the Wanted Alert settings and then perform a Scan Log.
  • Adjust any other JTAlert settings as they are not copied from your original (OM) settings.

 

Slight correction. Bullet point 4 should be Start JTAlert using the XYL shortcut.

de Laurie VK3AMA
   


locked Re: Band activity indicator

Ian
 

Sorry Laurie, its Ian VK6CR.  This Yahoo account was left over from my days of playing with African 419 scammers. 


locked Re: JTAlert not alerting to wanted states/intermittently not reading states from log file #FT8

HamApps Support (VK3AMA)
 

On 9/11/2017 7:40 AM, Lawrence Godek wrote:
Is that why when starting JTAlert there are several receive intervals before i see a station listed.  I figured that the size of my FT8 QSo's has something to do with that.

Larry
W0OGH

Larry,

No. When JTAlert first starts, it doesn't know your operating frequency, and will not generate any alerts until it receives the first UDP packet from WSJT-X. When the frequency is first detected, JTAlert will perceive this as a Band change and will ignore any decodes received within the first Rx period as the band change code doesn't know if the decodes received relate to the initial band or the new band. The end result is that it can take up to a minute after first starting for JTAlert to start displaying callsigns.

de Laurie VK3AMA
   


locked Re: Band activity indicator

HamApps Support (VK3AMA)
 

On 8/11/2017 4:30 PM, ranjeeh via Groups.Io wrote:
I'm mainly referring to the coloured band indication rather than the window:
For example, if I'm working JT65 and keeping an eye out for inactive bands to become active, the plethora of FT8 users will probably show bands as busy, regardless of JT use.

Its not a big deal, it just crossed my mind to mention it.

OM (what's you name/callsign)?

I understand now and agree. For non-FT8 users the level counts per band that influence the color of the bands should not use the FT8 band counts, but should use the JT65/JT9 counts. This will be changed for the next release (hopefully).

de Laurie VK3AMA
    


locked Re: latitude, longitute from QRZ Xml Data

HamApps Support (VK3AMA)
 

On 8/11/2017 4:18 PM, thierry ben via Groups.Io wrote:
Hello Laurie ,
what ever the call/country,geocoded or user supplied ,it s always a long/lat finishing by 15"N / 30 " W or 45"N 30" E
example with KC9WPS (user supplied) , long/lat on dxview 42 54' 14" N _ 88 1' 20" W ,but when i log i have 42 55" 15 N 88 1' 30" W

another example YO3GNF44 28' 45" N 26 3' 55" E result after log 44 28' 45" N  26 2' 30" E 
this is not a huge problem, but i like to understand 

73
Thierry F5SIB 
Thierry,

For those 2 callsigns you provided, what were the gridsquares logged?
Were they 4 or 6 character grids?

de Laurie VK3AMA
   


locked Re: JTAlert not alerting to wanted states/intermittently not reading states from log file #FT8

Lawrence Godek
 

Is that why when starting JTAlert there are several receive intervals before i see a station listed.  I figured that the size of my FT8 QSo's has something to do with that.

Larry
W0OGH

On Mon, Nov 6, 2017 at 4:42 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 5/11/2017 11:12 PM, W0ASB via Groups.Io wrote:
Hello,
I am noticing that there seems to be no alerts for wanted US States (except for Alaska, but that seems to be treated as a separate DXCC entity), is this the intended operation of the alerts? Additionally, when scanning the log file, intermittently all my wanted states will be erased. I haven't figured out how to reliably reproduce my results, either reading correctly or incorrectly. Is this a known issue as well?

I am using FT-8 with JTAlert 2.10.3 with WSJT-X 1.8.0-rc3; I am using the Standard ADIF Logging option, and uploading my log file as it has been downloaded from LotW to get my QSL information.

73,
Barrett, W0ASB

Barrett,

If not getting State alerts, that suggests that you don't have the HamApps Callsign database installed. This database is needed to identify US States, LoTW and eQSL(AG) memberships.

Regarding the the Scan Log intermittently not identifying the States confirmed in you ADIF log, this is likely due to JTAlert not having finished a background import of your adif file prior to starting the Scan. This can happen if the ADIF file is very large (large number of QSOs) and starting the Scan immediately after starting JTAlert. I can advise more if I can examine your session files. Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your files for analysis.
   
de Laurie VK3AMA
   



locked Re: Band activity indicator

Ian
 

I'm mainly referring to the coloured band indication rather than the window:
Inline image
For example, if I'm working JT65 and keeping an eye out for inactive bands to become active, the plethora of FT8 users will probably show bands as busy, regardless of JT use.

Its not a big deal, it just crossed my mind to mention it.


locked Re: latitude, longitute from QRZ Xml Data

thierry ben
 

Hello Laurie ,
what ever the call/country,geocoded or user supplied ,it s always a long/lat finishing by 15"N / 30 " W or 45"N 30" E
example with KC9WPS (user supplied) , long/lat on dxview 42 54' 14" N _ 88 1' 20" W ,but when i log i have 42 55" 15 N 88 1' 30" W

another example YO3GNF44 28' 45" N 26 3' 55" E result after log 44 28' 45" N  26 2' 30" E 
this is not a huge problem, but i like to understand 

73
Thierry F5SIB 


locked Re: latitude, longitute from QRZ Xml Data

Karel G J Bezuidenhout ZS6WN
 

I checked that website with my own call and it is way off. The data I entered on QRZ.com is correct, however.

73 de ZS6WN

Karel


locked Re: Alert Emails???

William Ockert
 

Thank you Laurie,

Looks like I have a learning curve ahead of me.   Appreciate the information!!

73 de Bill ND0B


locked Re: Alert Emails???

HamApps Support (VK3AMA)
 

On 8/11/2017 10:26 AM, William Ockert wrote:
Thank you for one of the neatest programs I have loaded in a long time.   JTAlert is truly awesome and a great help in my main activity which is chasing states on FT8.

I have figured out how to do everything I want to do with one exception and I suspect this is a feature request more than a howto.   I have multiple bands in which I am down to a state or two.   My operating tendency is to sit on a band waiting for those states to show up with the global "Wanted State" alert turned on.   However I am not always in the shack to hear this so...

Is there any way to send an email when an alert occurs?    This would be sent to the text message server of my cell provider so I get a cell phone text when an alert happens.

If not is there any chance this could become a feature in a future revision?

Again, thanks so much for the program!

73 de Bill ND0B

Bill,

JTAlert doesn't have an email option for alerts, but does provide a more flexible option that will execute a file (e.g. batch file) of your choice and you can have that batch file perform any function your willing to design.

The "User Defined Alert" is what you want. See the Settings, Alerts -> Miscellaneous Alerts -> User Defined Alert". Use the Help button when viewing that page to get detailed instruction. Provided in the help file is a sample batch file using the free Blat.exe command-line smtp mailer to email alerts.

de Laurie VK3AMA
   


locked Alert Emails???

William Ockert
 

Thank you for one of the neatest programs I have loaded in a long time.   JTAlert is truly awesome and a great help in my main activity which is chasing states on FT8.

I have figured out how to do everything I want to do with one exception and I suspect this is a feature request more than a howto.   I have multiple bands in which I am down to a state or two.   My operating tendency is to sit on a band waiting for those states to show up with the global "Wanted State" alert turned on.   However I am not always in the shack to hear this so...

Is there any way to send an email when an alert occurs?    This would be sent to the text message server of my cell provider so I get a cell phone text when an alert happens.

If not is there any chance this could become a feature in a future revision?

Again, thanks so much for the program!

73 de Bill ND0B


locked Re: latitude, longitute from QRZ Xml Data

Dave AA6YQ
 

Note that QRZ has two ways of determining a user's location: "user-supplied" and "geocoded".

- "user-supplied" means the user specified a latitude and longitude, or a grid square.

- "geocoded means that QRZ "computed" the latitude, longitude, and gridsquare from the user's postal address.

A "geocoded" location is fine for computing the correct bearing to aim a directional antenna, but is not accurate enough for pursuing awards like VUCC. Using geocoded location information, you can be fooled into thinking that you worked a grid square that you didn't; this becomes painfully clear when a QSL card, LoTW confirmation, or eQSL confirmation arrives.

QRZ makes it possible to determine whether its location information for a callsign is user-supplied or geocoded.

73,

Dave, AA6YQ

-----Original Message-----
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Phil & Anne Irons
Sent: Tuesday, November 07, 2017 3:51 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] latitude, longitute from QRZ Xml Data

Laurie & Thierry,

It has been my experience that amateurs in general, with no specific nationality, either have no idea what their correct grid square is, or if they have moved or are on some kind of expedition, neglect to change the QTH info, including grid square. This is frequently seen in contests where some amateurs operate mobile or from some location other than their home QTH. To use an old computer acronym, GIGO [Garbage In, Garbage Out].

Here is a URL that will give the correct grid square for any qth in the world: http://www.levinecentral.com/ham/grid_square.php <http://www.levinecentral.com/ham/grid_square.php> I have found it to be very useful; I hope you will too.

73,

Phil/VE1BVD [FN96vd]
Sydney, NS

On Tue, Nov 7, 2017 at 3:39 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@gmail.com> wrote:



On 5/11/2017 3:23 PM, thierry ben via Groups.Io wrote:


Hi all, i would like to know if there is an option in JTalert to send the latitude longitude just taken from QRZ xml data .
in my case jtalert + dxkeeper ,when i log the qso ,i receive wrong lat/long, until i made a manual search in dxkeeper and save it
regards
F5SIB Thierry


Thierry,

There is no option to log the Lat/Lon values returned from an XML lookup.

JTAlert determines the Lat/Lon based on the on-air gridsquare used by a station. If the Gridsquare returned from an XML lookup is 6 characters and the first 4 characters match the on-air Gridsquare then the more precise XML Gridsquare is used in the Lat/Lon calculations.

Are all JTAlert logged Lat/Lon values incorrect or is it random? Is it only Lat/Lon values from some Countries that are wrong?

Please give an example where the JTAlert logged Lat/Lon is incorrect. The Callsign, the JTAlert logged values and the values returned from the XML lookup.

de Laurie VK3AMA














--

Phil & Anne Irons
Sydney, Nova Scotia


<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>


locked Re: latitude, longitute from QRZ Xml Data

Phil & Anne Irons
 

Laurie & Thierry,

It has been my experience that amateurs in general, with no specific nationality, either have no idea what their correct grid square is, or if they have moved or are on some kind of expedition, neglect to change the QTH info, including grid square.  This is frequently seen in contests where some amateurs operate mobile or from some location other than their home QTH.  To use an old computer acronym, GIGO  [Garbage In, Garbage Out].

Here is a URL that will give the correct grid square for any qth in the world: http://www.levinecentral.com/ham/grid_square.php  I have found it to be very useful; I hope you will too.

73,

Phil/VE1BVD [FN96vd]
Sydney, NS

On Tue, Nov 7, 2017 at 3:39 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 5/11/2017 3:23 PM, thierry ben via Groups.Io wrote:
Hi all, i would like to know if there is an option in JTalert to send the latitude longitude just taken from QRZ xml data .
in my case jtalert + dxkeeper ,when i log the qso ,i receive wrong lat/long, until i made a manual search in dxkeeper and save it
regards
F5SIB Thierry 

Thierry,

There is no option to log the Lat/Lon values returned from an XML lookup.

JTAlert determines the Lat/Lon based on the on-air gridsquare used by a station. If the Gridsquare returned from an XML lookup is 6 characters and the first 4 characters match the on-air Gridsquare then the more precise XML Gridsquare is used in the Lat/Lon calculations.

Are all JTAlert logged Lat/Lon values incorrect or is it random? Is it only Lat/Lon values from some Countries that are wrong?

Please give an example where the JTAlert logged Lat/Lon is incorrect. The Callsign, the JTAlert logged values and the values returned from the XML lookup.

de Laurie VK3AMA
   





--
Phil & Anne Irons
Sydney, Nova Scotia


locked Re: latitude, longitute from QRZ Xml Data

HamApps Support (VK3AMA)
 

On 5/11/2017 3:23 PM, thierry ben via Groups.Io wrote:
Hi all, i would like to know if there is an option in JTalert to send the latitude longitude just taken from QRZ xml data .
in my case jtalert + dxkeeper ,when i log the qso ,i receive wrong lat/long, until i made a manual search in dxkeeper and save it
regards
F5SIB Thierry 

Thierry,

There is no option to log the Lat/Lon values returned from an XML lookup.

JTAlert determines the Lat/Lon based on the on-air gridsquare used by a station. If the Gridsquare returned from an XML lookup is 6 characters and the first 4 characters match the on-air Gridsquare then the more precise XML Gridsquare is used in the Lat/Lon calculations.

Are all JTAlert logged Lat/Lon values incorrect or is it random? Is it only Lat/Lon values from some Countries that are wrong?

Please give an example where the JTAlert logged Lat/Lon is incorrect. The Callsign, the JTAlert logged values and the values returned from the XML lookup.

de Laurie VK3AMA
   



locked Re: Delayed B4 Alert #FT8

HamApps Support (VK3AMA)
 

On 8/11/2017 6:22 AM, kk5aa_fred via Groups.Io wrote:
Just had something happen I've never seen before.

I saw a call I wanted a contact with. Thought I had worked them before but thew B4 alert was not showing.
I double clicked on his call and waited. He sent CQ a few more times and each time JTAlert displayed his call in the green box.
I clicked on transmit to work him and the instant the radio started transmitting, the B4 warning lit up.
It has never done this in the past.

What do I need to check or what can I do?

Fred - KK5AA

Fred,

That doesn't sound right. The way the code is structured, the will be no change in the B4 reporting until after the QSO is logged.

I will need to examine your session files. Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your files for analysis. Include a note of the Callsign and an approximate UTC time when you observed this behaviour. Only the most recent 24hours of activity is retained in the session files, so don't wait too long before sending.
   
de Laurie VK3AMA
   


locked Delayed B4 Alert #FT8

kk5aa_fred
 
Edited

Just had something happen I've never seen before.

I saw a call I wanted a contact with. Thought I had worked them before but the B4 alert was not showing.
I double clicked on his call and waited. He sent CQ a few more times and each time JTAlert displayed his call in the green box.
I clicked on transmit to work him and the instant the radio started transmitting, the B4 warning lit up.
It has never done this in the past.

What do I need to check or what can I do?

Fred - KK5AA


locked Re: Apologies in advance for what is probably a dumb question. All Callsigns one Color

Rich McCabe
 

I am using Log4OM.  I was just caught off guard when everything turned orange after running the scan log and update. It appeared I couldn't click anything (even the calling CQ stations).

So what exactly does that do?

I am working now but only have Decode Keywords and CQ and QRZ checked. What is default?

Thanks Laurie :)

RIch


locked Re: JTAlert how to receive Text Message

Solo JA1SJV
 

Thank you Laurie!!
Enabled the setting and incoming messages are visible.
Arigatou and 73's

Solo


locked Re: Band activity indicator

HamApps Support (VK3AMA)
 

On 7/11/2017 5:19 PM, ranjeeh via Groups.Io wrote:
Any chance of breaking down the band activity indication, so as to limit it to either JT65/9 or FT8 rather than both?

Why?
Nothing will be gained, except for a small reduction in screen space occupied by the window.

Without a compelling reason for such a change, I expect it will stay as it is.

FWIW, what you want will likely be available
in JTAlert V3, along with other Band Activity display customisations.

de Laurie VK3AMA
   

19901 - 19920 of 37225