Date   

locked Re: JTAlert missing "bands" = 4m-band

HamApps Support (VK3AMA)
 

Here you go, the latest JTAlert build with full 4m support.

There was a lot of code changes so I might have broken something.
Please provide some feedback regarding the changes. Do they work correctly, is anything broken or missing, etc?

https://dnl.HamApps.com/Beta/JTAlert.2.16.6.build.0008.Beta.Setup.exe

de Laurie VK3AMA


locked Re: Callsign Display Decays

HamApps Support (VK3AMA)
 

On 5/06/2020 1:22 am, Bob Craig wrote:
I have just updated from 2.12.8 to 2.16.6. Everything is great with one exception:

The JTAlert panel quits displaying callsigns after 5-12 minutes have elapsed since program start. 

The behavior at failure is WSJT (FT8) will complete a decode but the JTAlert callsign display will not update and continue to display the callsigns from the previous decode cycle.
At the 2nd WSJT decode after this failure the JTAlert display will be cleared but nothing will be displayed even though WSJT continues to decode and display normally.
Closing, then restarting the JTAlert/WSJT combo will restore function again temporarily.

There is no correlation between number of calls decoded and the failure point. That is, on 20 meters with a busy band, it can take as long as 12 minutes to fail while on 10m during an E opening it has failed after only 5 minutes of 1 or 2 calls decoded per 15 second cycle.
73, Bob, K8RC
Bob,

Update your WSJT-X version, 2.0.1 is rather old.

de Laurie VK3AMA


locked Callsign Display Decays

Bob Craig, K8RC
 

I have just updated from 2.12.8 to 2.16.6. Everything is great with one exception:

The JTAlert panel quits displaying callsigns after 5-12 minutes have elapsed since program start. 

The behavior at failure is WSJT (FT8) will complete a decode but the JTAlert callsign display will not update and continue to display the callsigns from the previous decode cycle.
At the 2nd WSJT decode after this failure the JTAlert display will be cleared but nothing will be displayed even though WSJT continues to decode and display normally.
Closing, then restarting the JTAlert/WSJT combo will restore function again temporarily.

There is no correlation between number of calls decoded and the failure point. That is, on 20 meters with a busy band, it can take as long as 12 minutes to fail while on 10m during an E opening it has failed after only 5 minutes of 1 or 2 calls decoded per 15 second cycle.
73, Bob, K8RC


locked Re: Incomplete Exchange in FD mode

Robert T
 

Bill,
It was never a JTAlert issue as we're not using JTAlert.  We are direct from WSJT-X to N1MM.
 Long story short, he was not using tab 1, he was on tab 2.
Thanks from both of us,
73,
Bob, K2RET & Skip, N1IBM

On June 4, 2020 at 9:35 AM g4wjs <bill.8@...> wrote:

On 04/06/2020 14:30, Robert T wrote:
Good Morning,

Trying to help a friend set up his N1MM and WSJT-X for field day.
We have done on air testing and all works well except for when his prompt to log window opens, it does not have his report sent filled in in the "Exch Sent" area at the bottom.
I have called CQ FD, he has answered me, I receive his FD exchange, he receives mine, 73's are sent. When my prompt to log qso window opens, both my sent and received exchanges are there.  His sent exchange is blank.


What are we missing here?
We have closed both WSJT-X and N1MM and restarted them several times and this keeps happening.

Bob, K2RET

Hi Bob,

this is not a JTAlert issue.

Is your QSO partner using the Tab 1 messages in WSJT-X?


--
73
Bill
G4WJS.

 


locked Re: Incomplete Exchange in FD mode

g4wjs
 

On 04/06/2020 14:30, Robert T wrote:
Good Morning,

Trying to help a friend set up his N1MM and WSJT-X for field day.
We have done on air testing and all works well except for when his prompt to log window opens, it does not have his report sent filled in in the "Exch Sent" area at the bottom.
I have called CQ FD, he has answered me, I receive his FD exchange, he receives mine, 73's are sent. When my prompt to log qso window opens, both my sent and received exchanges are there.  His sent exchange is blank.


What are we missing here?
We have closed both WSJT-X and N1MM and restarted them several times and this keeps happening.

Bob, K2RET

Hi Bob,

this is not a JTAlert issue.

Is your QSO partner using the Tab 1 messages in WSJT-X?


--
73
Bill
G4WJS.


locked Incomplete Exchange in FD mode

Robert T
 


Good Morning,

Trying to help a friend set up his N1MM and WSJT-X for field day.
We have done on air testing and all works well except for when his prompt to log window opens, it does not have his report sent filled in in the "Exch Sent" area at the bottom.
I have called CQ FD, he has answered me, I receive his FD exchange, he receives mine, 73's are sent. When my prompt to log qso window opens, both my sent and received exchanges are there.  His sent exchange is blank.


What are we missing here?
We have closed both WSJT-X and N1MM and restarted them several times and this keeps happening.

Bob, K2RET



locked Re: Yet Another N1MM+ & JTAlert Post....

Scott Straw
 

Todd,

Thank you for the detailed and well-document procedure. I’ll give it a try...


Scott, KB4KBS
Roswell, Georgia USA
(EM74)
Sent from my iPhone6

On Jun 4, 2020, at 08:24, Todd Shiffer <n3pkj@qsl.net> wrote:

Funny I use WSJT_X, JTAlert & N1MM every day without a hitch no double logging or anything.


locked Re: Yet Another N1MM+ & JTAlert Post....

Todd Shiffer (N3PKJ)
 
Edited

Scott

Funny I use WSJT_X, JTAlert & N1MM every day without a hitch no double logging or anything. I however don't use the digital interface in N1MM for WSJT-X. My WSJT-X, JTAlert & N1MM complete setup can be found here https://qsl.net/n3pkj/wsjt-x/. Been running this setup ever since they made that one change to N1MM that made it unusable over a year ago or so. Took some time figure out but I did, finally!

73
Todd (N3PKJ)
Meadville, Pa.
EN91


locked Re: Non-coloring of WSJT-X 2.2.0 GA

Norbert Graf - DD3KF
 

Laurie,

 

thank you for your explanation.

 

I now understand better what I have observed.

 

I have changed the ALERT PRIORITY:

 

- WANTED DXCC,

- WANTED GRID

 

now have a higher priority than CQ.

 

73

 

______________

Norbert Graf

D D 3 K F

 

Von: Support@HamApps.groups.io <Support@HamApps.groups.io> Im Auftrag von HamApps Support (VK3AMA)
Gesendet: Donnerstag, 4. Juni 2020 02:27
An: Support@HamApps.groups.io
Betreff: Re: [HamApps] Non-coloring of WSJT-X 2.2.0 GA

 

On 3/06/2020 4:31 pm, Norbert Graf - DD3KF wrote:

Hello Laurie,

 

Installed WSJT-X 2.2.0 GA 64bit.

 

I would like to inform you about a new issue I discovered today.

 

JTAlert signaled DX  but the display in WSJT-X 2.2.0 GA was partially missing.

 

Please see the enclosed 2 Screen Shot.

 

Related Calls:

- XE1KK,

- V22NYR (odd GRID – real station?)

 

My working environment:

- Windows 10, 64 bit

- WSJT-X 2.2.0 GA 64 bit

- JTAlert 2.16.6

- HRD Log 6.7.0.277, logging via JTAlert

 

TU for your help beforehand.

 

73


There is no issue. WSJT-X is displaying the colors matching those shown in JTAlert, it is working correctly.

I suspect your referring to "XE1KK" which generated a DXCC alert and a CQ Alert. JTAlert can only color a callsign with one color, if a callsign generates multiple alerts, only the highest priority alert will be used to color the callsign. You appear to have CQs set with a higher priority than DXCCs. You need to make DXCC alerts higher priority than CQ. The default is CQ is lower in priority than DXCC so you must have changed the priorities sometime in the past.

de Laurie VK3AMA


locked Re: JTAlert missing "bands" = 4m-band

Norbert Graf - DD3KF
 

Laurie,

thank you. This is a real good news.

I understand that such a far-reaching intervention in version 2 is not
practically feasible and would delay the development of version 3.

I looking forward to the solution in the future version 3.

73

______________
Norbert Graf
D D 3 K F

-----Ursprüngliche Nachricht-----
Von: Support@HamApps.groups.io <Support@HamApps.groups.io> Im Auftrag von
HamApps Support (VK3AMA)
Gesendet: Donnerstag, 4. Juni 2020 02:27
An: Support@HamApps.groups.io
Betreff: Re: [HamApps] JTAlert missing "bands" = 4m-band

On 4/06/2020 1:57 am, Norbert Graf - DD3KF wrote:
I sincerely hope that this request is feasible, perhaps in the future
version 3.

TU es 73!


PS:
According to my observations the digital modes on 23 cm and above are not
used very often. An extension to these bands is not necessary in my opion.

4m inclusion in the Alert tracking for JTAlertV2 is on the todo list. It is
a major undertaking to implement and in all honesty may not make it.
JTAlertV3 is a totally different animal, coding wise, it supports all bands
from 2200m to 2m. Inclusion of additional bands is a rather trivial matter
as is the inclusion of any new modes.

de Laurie VK3AMA


locked Yet Another N1MM+ & JTAlert Post....

Scott Straw
 

From The N1MM+ set-up guide for WSJT-X/JTDX:

Compatibility with JTAlert – Can I run JTAlert (and N1MM+) at the same time?
No. The current versions of JTAlert and N1MM+ do not permit port sharing. You must close JTAlert for the WSJT Decode List to function. Furthermore, if you enable both the WSJT-X -to- N1MM+ logging interface and the JTAlert logging interface (without using the WSJT Decode List window in N1MM+), your contacts will be double-logged into the N1MM+ contest database.

Laurie,
I am so addicted to your JTAlert program.  It is a masterful piece of work. Thank you for this labor of love!  I'm sure you are tired by now of everyone pushing you to make it do "more, more, more!"  I won't do that here, directly, but rather ask for some insight to someone who knows absolutely zero about coding.  It seems the barrier to being able to use JTAlert and N1MM+ is something called "port sharing".  Is this something that is impossible, difficult, impractical, or time consuming? Some or all of the above?

I have come to accept that if I want to contest with N1MM+, using WSJT-X (like in the ARRL North American Field Day event at the end of this month), I'm going to have to "suck it up" and fly without JTAlert.  I'm simply curious about the degree of difficulty in overcoming the shared port obstacle.

I must close by telling you that for day-to-day logging I run WSJT-X and JTAlert along with Dave Bernstein's DXLabs Suite.  I've configured  the programs to have all of the decodes forward from JTAlert to the Spot Collector program.  I then have a filter for "Needed DX" that serves as a reinforcement of the audible alert.  I can also quickly see if the station is workable or just a "one-shot minus 24 signal that wafted through like an aroma on a passing breeze".

Again, thank you for the JTAlert program that has revolutionized how WSJT-X ad JTDX are used.

Scott, KB4KBS
Roswell, Georgia, USA


locked Re: Email Preferences

HamApps Support (VK3AMA)
 

On 3/06/2020 12:24 am, Rickey via groups.io wrote:
If I missed any notices I apologize but do we no longer receive email updates?
I have not received any notifications since early May. Thanks.
--
Rickey Gilliland

Your membership shows your email preferences set to a single daily summary email. Perhaps you missed that one email per day or it is getting redirected to you spam folder.

de Laurie VK3AMA


locked Re: WJST-X v2.2.0 Release & JTAlert v2.16.6

HamApps Support (VK3AMA)
 

On 4/06/2020 8:54 am, Chip Harleman wrote:
Will we be seeing a new release, a 2.16.7 to complement the 2.2.0.  I notice a minor decode/display timing issue which has already been reported.  Been running for a few hours with no other issues.  Have seen a beta version is available, I'm good for a formal release.  JTAlert is a great tool with more capabilities than I presently enable.  But over time, I find new and interesting ways to take advantage of making the environment even more enjoyable.  Great Job!

If you want the early decodes clearing fix you will need to use the previously published JTAlert Beta. I don't normally make Beta releases public, but this was the exception due to the number of users reporting the problem and I wanted to get a lot of users using it to ensure that the fix was working correctly (I wasn't experiencing the problem myself in testing)

The next JTAlert public release date is unknown at this time as I am in the middle of tracking down other issues that will require a new release and I want to see what plays out with the current WSJT-X 2.2.0-GA defects.

de Laurie VK3AMA


locked Re: TenTec Orion JTAlert

HamApps Support (VK3AMA)
 

On 3/06/2020 9:26 pm, Greg Yates via groups.io wrote:

I was trying to connect my TenTec Orion 2 thru Omni Rig to JT Alert along with my 7610 and I think I have screwed up both.  Mike helped me before.  Also anyone that might be familiar with JT Alert and N3FPJ Field Day logging program.

I am not much of  a computer person so any help would be appreciated.

Thanks,

Greg WB2BIN


JTAlert doesn't do CAT control. It has no concept of Rigs and their instruction set, nor that of com/usb ports. Are you perhaps referring to getting WSJT-X and N3FPJ working with your rig? I suggest you ignore JTAlert until you get that mix working then your can get the JTAlert integration working (it is very easy with simple instructions included in the Help file).

de Laurie VK3AMA


locked Re: Non-coloring of WSJT-X 2.2.0 GA

HamApps Support (VK3AMA)
 

On 3/06/2020 4:31 pm, Norbert Graf - DD3KF wrote:

Hello Laurie,

 

Installed WSJT-X 2.2.0 GA 64bit.

 

I would like to inform you about a new issue I discovered today.

 

JTAlert signaled DX  but the display in WSJT-X 2.2.0 GA was partially missing.

 

Please see the enclosed 2 Screen Shot.

 

Related Calls:

- XE1KK,

- V22NYR (odd GRID – real station?)

 

My working environment:

- Windows 10, 64 bit

- WSJT-X 2.2.0 GA 64 bit

- JTAlert 2.16.6

- HRD Log 6.7.0.277, logging via JTAlert

 

TU for your help beforehand.

 

73


There is no issue. WSJT-X is displaying the colors matching those shown in JTAlert, it is working correctly.

I suspect your referring to "XE1KK" which generated a DXCC alert and a CQ Alert. JTAlert can only color a callsign with one color, if a callsign generates multiple alerts, only the highest priority alert will be used to color the callsign. You appear to have CQs set with a higher priority than DXCCs. You need to make DXCC alerts higher priority than CQ. The default is CQ is lower in priority than DXCC so you must have changed the priorities sometime in the past.

de Laurie VK3AMA


locked Re: JTAlert missing "bands" = 4m-band

HamApps Support (VK3AMA)
 

On 4/06/2020 1:57 am, Norbert Graf - DD3KF wrote:
I sincerely hope that this request is feasible, perhaps in the future version 3.

TU es 73!


PS:
According to my observations the digital modes on 23 cm and above are not used very often. An extension to these bands is not necessary in my opion.
4m inclusion in the Alert tracking for JTAlertV2 is on the todo list. It is a major undertaking to implement and in all honesty may not make it.
JTAlertV3 is a totally different animal, coding wise, it supports all bands from 2200m to 2m. Inclusion of additional bands is a rather trivial matter as is the inclusion of any new modes.

de Laurie VK3AMA


locked WJST-X v2.2.0 Release & JTAlert v2.16.6

Chip Harleman
 

Will we be seeing a new release, a 2.16.7 to complement the 2.2.0.  I notice a minor decode/display timing issue which has already been reported.  Been running for a few hours with no other issues.  Have seen a beta version is available, I'm good for a formal release.  JTAlert is a great tool with more capabilities than I presently enable.  But over time, I find new and interesting ways to take advantage of making the environment even more enjoyable.  Great Job!


locked Re: JTAlert missing "bands" = 4m-band

Tom Melvin
 

No no settings for 4m

4m Support I have been told will be in V3

With the recent Es over here as you guy will be familiar with it shows how handy JTAlert is. I really miss it on 70Mhz.

I got round it slightly by using one copy of WSJT-X dedicated to 4m, make sure all your 4m calls are in adf file. Set wsjt-x colours for new grid etc. and use it as a monitor - see a call, switch over to main system and work them, update adf file. Long winded I know but save a lot of ‘new grid’ warnings.

Tom


73

Tom
GM8MJV (IO85)

On 3 Jun 2020, at 20:04, Willi Passmann <wpassmann@web.de> wrote:

Am 03.06.2020 um 17:57 schrieb Norbert Graf - DD3KF:
I support this request to include the 4m tape in your very useful program JTAlert.
I already wondered if I missed a setting that would activate 4m...

I support this suggestion.

vy 73,
Willi, DJ6JZ





locked Re: JTAlert missing "bands" = 4m-band

Willi Passmann
 

Am 03.06.2020 um 17:57 schrieb Norbert Graf - DD3KF:
I support this request to include the 4m tape in your very useful program JTAlert.
I already wondered if I missed a setting that would activate 4m...

I support this suggestion.

vy 73,
Willi, DJ6JZ


locked Re: JTAlert missing "bands" = 4m-band

Norbert Graf - DD3KF
 

Hello, Laurie,

I support this request to include the 4m tape in your very useful program JTAlert.

Why?

In Europe the activity on this band is increasing. One reason is certainly that in the meantime transceivers with 4m capabilities are available, e.g. ICOM IC 7100, IC 7300 or Kenwood TS 890S.

To prove the increased activity on 4m here is the number of 4 digit GRID´s I worked May 2020 (using indoor antennas):
- 6m 170,
- 4m 70.

I often work with 2 instances of WSJT-X and JTAlert at the same time on 6m and 4m.

It is very irritating that on 4m every station that has not been worked before is signalled as NEW GRID.

In my opinion, the inclusion of the 4m band in JTALert would be a great enhancement and a great benefit to the users.

I sincerely hope that this request is feasible, perhaps in the future version 3.

TU es 73!


PS:
According to my observations the digital modes on 23 cm and above are not used very often. An extension to these bands is not necessary in my opion.


______________
Norbert Graf
D D 3 K F
Ringstr. 32
52078 Aachen
Germany


-----Ursprüngliche Nachricht-----
Von: Support@HamApps.groups.io <Support@HamApps.groups.io> Im Auftrag von Wilhelm Rauh
Gesendet: Mittwoch, 3. Juni 2020 11:17
An: Support@HamApps.groups.io; Wilhelm Rauh <Wilhelm.Rauh@online.de>
Betreff: [HamApps] JTAlert missing "bands" = 4m-band

Hello JTAlert-Team,

I have been using JTAlert together with JTDX for quite some time now and I enjoy it very much. I can no longer imagine FT8 without JTAlert.
So thank you very much for this excellent tool.

Unfortunately the 4m-band (70MHz) is missing under "bands".
Could you please add this ?

Many thanks in advance

Have further much fun with the common hobby.

73, Wilhelm (DL5MCG)

3301 - 3320 of 33231