Date   

locked Re: JTAlert name

HamApps Support (VK3AMA)
 

On 22/11/2020 8:22 am, Michael Black via groups.io wrote:
Yes...that work's...but you said it won't work in the future.

Mike
OK,

What I'll do is guarantee support for a dedicated user-defined command-line "id" parameter. eg
"/id=xxx"

While any arbitrarily named parameter is currently supported that is undocumented and not guaranteed for future releases, especially as the code base moves over to new .NET technology. I will guarantee support for a "/id=xxx" parameter in all future versions.

de Laurie VK3AMA


locked Re: Does JTAlert Decode Fox/Hound Mode?

neil_zampella
 

JT-Alert's display really does not work with F/H mode.  Considering that you're trying to get ONE station, and WSJT-X handles the QSO, all JT-Alert is needed for is to interface with your logging program.

Neil< kN3ILZ


locked Re: v 216 15 text messages not working #FT8

Laurie, VK3AMA
 

On 23/11/2020 12:23 am, David Michael Gaytko // WD4KPD wrote:
text messages not working any more. (used too).  tcp port checker shows all ports fail.
how to ensure that ports are turned on ?

david/wd4kpd
What is this "tcp port checker" your using? JTAlert has not provided that sort of diagnostic mechanism for many versions now.
What port numbers are you checking?

de Laurie VK3AMA


locked Re: Request for better options for vertical based display

Laurie, VK3AMA
 



On 22/11/2020 1:36 pm, Jason Garneau wrote:
I'd really like the option to make JTAlert more usable in a vertical layout.  WSJT-X and JTDX both take up a lot of vertical real estate, especially with as many decodes most of us are now that FT8 is so popular.  I feel it would be a huge benefit to move away from the horizontal-based layout of JTAlert so that thos of us running full 1920x1080 screens could put the app over on the side of the screen, allowing us to expand the decode screen more, and also giving a ton more real estate to JTAlert.  I would envision something like one to two columns by X number of rows, which I also think would be a lot easier to scan over with my eyes, instead of the multiple columns.  I'd love for it to fill up the red box drawn in here:


The current view options do not seem to allow for a configuration like this.

Anyway, just a thought.  Thank you for developing such useful software!

73,
Jason / K1LOL

A new callsign display window is coming. It offers complete flexibility to its sizing and placement, with no limit on the number of callsigns displayed. See this previous post https://hamapps.groups.io/g/Support/message/31987

Three sample images of the same decode period...



de Laurie VK3AMA


locked Re: Request for better options for vertical based display

WB8ASI Herb
 

The Decodes Window will provide what you are looking for.  You can select zero rows for the main callsign window thus trimming down the horizontal info.  The Decodes Window will fit perfectly in your red box.  You can select just the few columns you want to view.  ...and you are correct that it is much easier to scan columns quickly, and the callsigns remain on the list into the future cycles.  Once you have it set up, it will open to the same view when you start JTAlert.  This is how I have my screen arranged and find it works great.  73, Herb WB8ASI


locked Re: v 216 15 text messages not working #FT8

Michael Black
 

I just sent you a test message -- you can test sending yourself a message.
Works fine here.

Reboot is first consideration.

Firewall would be 2nd.

Mike W9MDB




On Sunday, November 22, 2020, 07:23:59 AM CST, David Michael Gaytko // WD4KPD <wd4kpd@...> wrote:


text messages not working any more. (used too).  tcp port checker shows all ports fail.
how to ensure that ports are turned on ?

david/wd4kpd


locked v 216 15 text messages not working #FT8

David Michael Gaytko // WD4KPD
 

text messages not working any more. (used too).  tcp port checker shows all ports fail.
how to ensure that ports are turned on ?

david/wd4kpd


locked Does JTAlert Decode Fox/Hound Mode?

Marlo Montanaro - KA2IRQ
 

Trying to work Malawi on 40 M Fox/Hound mode, and I'm only getting standard decodes...  When JTAlert sees something like:

025430 0 0.4 284 ~ WA4ZXV RR73; UA4PT <7Q7RU> -16

it doesn't seem to decode anything or produces a bogus decode in the decode window- it certainly does not match WSJT-X.

Is this by design?  Not a big deal, really- Usually if you're in F/H Mode you really don't need JTAlert anyway (although I do leave it running).

WSJT-X V2.2.2 and JTAlert V2.16.16 on Win10.

Just curious...

73,
Marlo
KA2IRQ


locked Re: NE9U not highilghted as wanted callsign

Jim Reisert AD1C
 

The Callsigns that are not being colored as "Wanted Callsigns" are being colored by a higher priority Alert (your Cyan Alert in this case). If you want the "Wanted Callsign" alert to take priority over all other Alert types than you need to adjust the priorities bringing the Wanted Callsign Alert to the top of the list or at least above the Alert types that you don't mind missing.

When a Callsign generates multiple Alert types, only the highest priority Alert will dictate the coloring applied. All triggered Alert sounds will be applied however.
OK. I thought I had fixed the priority a long time ago. I guess not.
It's fixed now. Callsigns are at the TOP of the list.

Sorry for the bandwidth.

--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://www.ad1c.us


locked Request for better options for vertical based display

Jason Garneau
 

I'd really like the option to make JTAlert more usable in a vertical layout.  WSJT-X and JTDX both take up a lot of vertical real estate, especially with as many decodes most of us are now that FT8 is so popular.  I feel it would be a huge benefit to move away from the horizontal-based layout of JTAlert so that thos of us running full 1920x1080 screens could put the app over on the side of the screen, allowing us to expand the decode screen more, and also giving a ton more real estate to JTAlert.  I would envision something like one to two columns by X number of rows, which I also think would be a lot easier to scan over with my eyes, instead of the multiple columns.  I'd love for it to fill up the red box drawn in here:




The current view options do not seem to allow for a configuration like this.

Anyway, just a thought.  Thank you for developing such useful software!

73,
Jason / K1LOL


locked Re: NE9U not highilghted as wanted callsign

HamApps Support (VK3AMA)
 

On 22/11/2020 1:19 pm, Jim Reisert AD1C wrote:
The call I added was WB0CPW.  Just transmitted again.  Still cyan.
Other calls on the same band in the same sequence turned purple
OK, I know what is going on. The "Cyan" is the clue.

The Callsigns that are not being colored as "Wanted Callsigns" are being colored by a higher priority Alert (your Cyan Alert in this case). If you want the "Wanted Callsign" alert to take priority over all other Alert types than you need to adjust the priorities bringing the Wanted Callsign Alert to the top of the list or at least above the Alert types that you don't mind missing.

When a Callsign generates multiple Alert types, only the highest priority Alert will dictate the coloring applied. All triggered Alert sounds will be applied however.

de Laurie VK3AMA


locked Re: NE9U not highilghted as wanted callsign

HamApps Support (VK3AMA)
 

On 22/11/2020 1:16 pm, Jim Reisert AD1C wrote:
I don't see any way
to select worked B4 bands.
You can't select Worked B4 bands, all bands are considered. A band that is considered worked B4 is determined from examining your Log.

Since I have some concrete examples of Callsigns failing for you, the next step is for me to try reproduce the problem using a setup similar to yours. Please use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis. In a separate email send me a copy of your log file (send to vk3ama.ham.apps [at] gmail.com)

de Laurie VK3AMA



locked Re: NE9U not highilghted as wanted callsign

Jim Reisert AD1C
 

Unchecking the "Ignore grid square" box made no difference.

--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://www.ad1c.us


locked Re: NE9U not highilghted as wanted callsign

Jim Reisert AD1C
 

The call I added was WB0CPW. Just transmitted again. Still cyan.
Other calls on the same band in the same sequence turned purple.

--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://www.ad1c.us


locked Re: NE9U not highilghted as wanted callsign

Jim Reisert AD1C
 

I just added another call, WB0-something. Never worked before, ever.
Originally Cyan background. Did not turn purple on his next
transmission.

I added the call, then got interrupted with my previous E-mail reply,
so forget what it was.

--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://www.ad1c.us


locked Re: NE9U not highilghted as wanted callsign

Jim Reisert AD1C
 

What Band/Mode/Grid options do you have set for the "Worked B4" Alert?
I have "Ignore Gridsquare" checked, nothing else. I don't see any way
to select worked B4 bands.

--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://www.ad1c.us


locked Re: NE9U not highilghted as wanted callsign

HamApps Support (VK3AMA)
 

On 22/11/2020 12:52 pm, Jim Reisert AD1C wrote:
I assume if the call is on a different
band it won't be considered "worked before" and will display
highlighted.

What Band/Mode/Grid options do you have set for the "Worked B4" Alert?

de Laurie VK3AMA




locked Re: NE9U not highilghted as wanted callsign

Jim Reisert AD1C
 

"Alert when decoded Callsign worked B4" is checked. In general, I
probably want that unchecked. I assume if the call is on a different
band it won't be considered "worked before" and will display
highlighted.

--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://www.ad1c.us


locked Re: NE9U not highilghted as wanted callsign

Jim Reisert AD1C
 

On Sat, Nov 21, 2020 at 6:39 PM HamApps Support (VK3AMA) via groups.io <vk3ama.ham.apps=gmail.com@groups.io> wrote:

Does NE9U already exist in your log for those 2 bands? If so he wont be alerted unless your enable the "Alert when decoded Callsign worked B4" setting for the Wanted Callsign Alert.

No, I have only worked him on 30m FT8, but the spots were on 17m and 15m.  They did not highlight.

I just added K2HT.  He's calling CQ on 80m.  I have a 15m QSO.  The new call is being highlighted correctly.

I wish I could figure out the pattern!

I wishI wish I could figure out the pattern..._.__,

--
Jim Reisert AD1C, <jjreisert@...>, https://www.ad1c.us


locked Re: Color in the box

HamApps Support (VK3AMA)
 

On 22/11/2020 9:20 am, Neil Foster wrote:
I know I asked about this before but it appears I have not done something correctly.
In JT Alert when a South American station appears the box in JT Alert has a yellow background. While not a problem how do I get the tint gone?. Either I am dense
at age 86 or I am not doing something correctly.
Thanks
Neil   N4FN
If a callsign is getting its background colored than it is because that Callsign is generating an Alert. If you don't want the coloring then you will need to turn off that Alert type. Or alternatively you can change the color for that Alert to something more suitable.

You can get a quick overview of all the Alert color combinations you have set by opening the "Alert Types Summary Window" via the view menu.

de Laurie VK3AMA

4641 - 4660 of 36897