Date   

locked JTalert and Log4OM2 start up issue

geoff wiggins
 

Using Flex 5000a, wsjt-x 2.2.2. Win 10.
I have noticed that if Log4OM2 is started before JTAlert then the band in use is not shown in the title bar, ie JTAlert 2.6.16, callsign[20m etc.......]. A series of ??? are shown instead. If JTAlert is started first then this issue does not occur. This is 100% repeatable.
Not a big deal but I would be interested as to why this is.

73 Geoff.
G4XMJ


locked Double-quote in JTAlert's QSO Confirmation Comments

twallace12@...
 

I recently built a 185" vertical antenna to experiment with and I started making contacts on several bands. I noticed that these contacts were not being logged to QRZ even though the QSOs were showing up in the ADIF file. I finally figured out the problem.

In the Comments box of JTAlert's QSO confirmation window, I had put

185" experimental vertical 

Later, I realized that logging to QRZ had stopped with as soon as I put in the comment with the double quote. I took out the double quote and everything is back to normal this morning.


locked Re: JTAlert name

Laurie, VK3AMA
 

On 23/11/2020 7:48 am, Michael Black via groups.io wrote:
Muchos gracias Laurie...

Mike
Mike,

Minor change in the name, the /id parameter clashes with the same param I am using in some other code. Use /myid instead.

de Laurie VK3AMA


locked Re: Request for better options for vertical based display

Jason Garneau
 

Hi Laurie,

It looks like the "decodes" window is more in line with what I'm looking for.  I'll definitely try out the new view you're working on once that's available, as well.

Thanks!
Jason / K1LOL


locked Re: JTAlert name

Michael Black
 

Muchos gracias Laurie...

Mike




On Sunday, November 22, 2020, 02:45:14 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 23/11/2020 6:13 am, HamApps Support (VK3AMA) via groups.io wrote:
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

In addition, if an "/id" parameter is defined, it's value will be displayed in the JTAlert title-bar status area. That will be available with the next public release.

de Laurie VK3AMA


locked Re: JTAlert name

HamApps Support (VK3AMA)
 

On 23/11/2020 6:13 am, HamApps Support (VK3AMA) via groups.io wrote:
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

In addition, if an "/id" parameter is defined, it's value will be displayed in the JTAlert title-bar status area. That will be available with the next public release.

de Laurie VK3AMA


locked Re: Request for better options for vertical based display

HamApps Support (VK3AMA)
 

On 23/11/2020 6:44 am, Jason Garneau wrote:
I had no idea this window existed.  How is this not the default view?   Thanks again - this should solve my situation.

73,
Jason / K1LOL

Make sure you enable the decodes, Settings window, "Window -> Decodes" section, top left corner. If you don't the Decodes window will remain empty. Also note the Decodes window has its own Settings dialog, separate from the main JTAlert Settings where you enable the decodes collection.

de Laurie VK3AMA


locked Re: Request for better options for vertical based display

Jason Garneau
 

Thanks, Herb!

I had no idea this window existed.  How is this not the default view?   Thanks again - this should solve my situation.

73,
Jason / K1LOL


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


1061 - 1080 of 33325