Date   

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)


locked Re: Email Preferences

neil_zampella
 

I'd check to see if they're in your SPAM folder, or perhaps your ISP is blocking the list.
I get the 'digest' and see updates all the time.

Neil, KN3ILZ


locked TenTec Orion JTAlert

Greg Yates
 

Help,

 

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.  I am at your disposal.  I can be reached at 315-939-4419.

 

Thanks,

Greg WB2BIN


locked JTAlert missing "bands" = 4m-band

Wilhelm.Rauh@...
 

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)


locked Swisslog and JTAlert

Jorge Diez - CX6VM <cx6vm.jorge@...>
 

hello

I am new with JTAlert

What I still don´t know is how JTAlert know my DXCC, WAZ, ......status to give me the alerts

May I need to manually import a ADIF file from my logging (Swisslog) or is there a way to do it automatically?

thanks!

73,
Jorge
CX6VM/CW5W


locked Non-coloring of WSJT-X 2.2.0 GA

Norbert Graf - DD3KF
 

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

 

PS:

The previously reported problem of stations worked B4 with the missing display in WSJT-X appears to have been resolved at first glance.

 

 

______________

Norbert Graf

D D 3 K F


locked Re: "QSO Not Logged"

Ed Ireland
 

Thanks Michael.  I will try increasing the time to log.  I had not paid attention to that parameter.  Thanks!


On Tue, Jun 2, 2020 at 10:49 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Change the time here

Inline image





On Tuesday, June 2, 2020, 10:31:19 PM CDT, Ed Ireland <ed@...> wrote:


I get the message "QSO not logged" from time to time but the QSO is always logged in DXKeeper. Any idea why this message comes up?


locked Re: "QSO Not Logged"

Michael Black
 

Change the time here

Inline image





On Tuesday, June 2, 2020, 10:31:19 PM CDT, Ed Ireland <ed@...> wrote:


I get the message "QSO not logged" from time to time but the QSO is always logged in DXKeeper. Any idea why this message comes up?


locked Re: "QSO Not Logged"

David Burden
 

You possibly may have some autologging function enabled to QRZ, Clublog, EQSL, LOTW or other that has failed for that contact. Worth checking.

73 David VK3BDX


locked "QSO Not Logged"

Ed Ireland
 

I get the message "QSO not logged" from time to time but the QSO is always logged in DXKeeper. Any idea why this message comes up?


locked Re: Non-coloring of WSJT-X 2.2.0 -rc decodes by JTAlert - cause identified.

jushamn@...
 

Hi All
I'm running WSJT-x v2.1.2 0068f9 and JTAlert v2.16.2 and I have the same problem. I'm not inclined to run the release candidates. Attached is my system specs file created with Speccy by Piriform. I looked in Setup> Applications>WSJT-X/JTDX and appears good there.

Hope this info helps. Laurie maybe you can pass this on to WSJT-X dev-list.
Let me know if there is something else I can do.


locked Another Possible Security Hurdle with New Windows 10 2004

Stephen Taylor - K6SJT
 

Just a heads up I ran into after the Windows 10 2004 Update - And note I already have Windows Defender set to allow all JTAlert folders and files.

In my situation, JTAlert would not open after the Windows update. I tracked it down Windows Defender:  'App & browser control'  >  'Exploit protection'  >  'Data Execution Prevention (DEP)'.

Only after I set that to 'Off by default' and restarted the computer would JTAlert (v2.16.6.1) again open and perform correctly.

Others may not have this issue, but in case you do, this may save you some time tracking it down.

Stephen Taylor - K6SJT


locked Re: Non-coloring of WSJT-X 2.2.0 -rc decodes by JTAlert - cause identified.

Tony Dixon G4CJC
 
Edited

On Tue, Jun 2, 2020 at 01:55 PM, Tony Dixon G4CJC wrote:
On Mon, Jun 1, 2020 at 11:41 PM, HamApps Support (VK3AMA) wrote:
I finally tracked down the JTAlert non-coloring of decodes in the release candidates.
WSJT-X2.1.2 works correctly, but the -rcs don't when the decode string contains a positive report. Reports that are negative are colored correctly.
Tested both rc2 & rc3

eg.

"AA1AA VK3AMA +12" & "AA1AA VK3AMA R+12" - FAIL

"AA1AA VK3AMA -12" & "AA1AA VK3AMA R-12" - OK

JTAlert sending the coloring command containing the "VK3AMA R-12" string correctly colors while "VK3AMA R+12" fails with the only difference is the number sign in the string sent to WSJT-X.

This report has already been sent to the WSJT-X dev-list.

de Laurie VK3AMA

 Wow, kudos to you Laurie. Even when I knew what to look for it took me ages to spot.
Where did you get the clues for that one?
All the best
Tony G4CJC
This fault persists in the latest version of WSJT-X v2.2

Tony G4CJC


locked Email Preferences

Rickey
 

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
k4rky@...


locked Re: Callsigns disappearing in 2.16.6 (beta)

Jim Reisert AD1C
 

Untick the "Clear callsigns display after logging" option under the Logging section of the JTAlert Settings window (scroll the section down, it is the last checkbox).
Done, thanks.

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


locked Re: Non-coloring of WSJT-X 2.2.0 -rc decodes by JTAlert - cause identified.

Tony Dixon G4CJC
 

On Mon, Jun 1, 2020 at 11:41 PM, HamApps Support (VK3AMA) wrote:
I finally tracked down the JTAlert non-coloring of decodes in the release candidates.
WSJT-X2.1.2 works correctly, but the -rcs don't when the decode string contains a positive report. Reports that are negative are colored correctly.
Tested both rc2 & rc3

eg.

"AA1AA VK3AMA +12" & "AA1AA VK3AMA R+12" - FAIL

"AA1AA VK3AMA -12" & "AA1AA VK3AMA R-12" - OK

JTAlert sending the coloring command containing the "VK3AMA R-12" string correctly colors while "VK3AMA R+12" fails with the only difference is the number sign in the string sent to WSJT-X.

This report has already been sent to the WSJT-X dev-list.

de Laurie VK3AMA

 Wow, kudos to you Laurie. Even when I knew what to look for it took me ages to spot.
Where did you get the clues for that one?
All the best
Tony G4CJC


locked Re: JTAlert two instance, two two different resended ports

Robert, SP8SN
 

OK thank You
--
Robert, SP8SN


locked Re: Non-coloring of WSJT-X 2.2.0 -rc decodes by JTAlert - cause identified.

Norbert Graf - DD3KF
 

Hello Laurie,

 

yesterday I made another odd observation:

 

I decoded stations from a NEW GRID calling CQ:

 

JTALERT:

- Showing DXl with green background for CQ,

- only Audio Alert for NEW GRID,

- TX1 by DX showing light blue background for NEW GRID.

(sorry, no screen shot).

 

WSJT-X RC

pse see sample screen shot.

DX: DL3TW

 

My working environment:

- Windows 10, 64 bit

- WSJT-X 2.2.0 RC3 64 bit

- JTAlert 2.16.6

- HRD Log 6.7.0.277, logging via JTAlert

Alter priority:

- NEW GRID

- CQ

 

I dont know if this is related to your following post.

 

73!

 

______________

Norbert Graf

D D 3 K F

 

Von: Support@HamApps.groups.io <Support@HamApps.groups.io> Im Auftrag von HamApps Support (VK3AMA)
Gesendet: Dienstag, 2. Juni 2020 00:42
An: Support@HamApps.groups.io
Cc: main@HamAppsBeta.groups.io
Betreff: [HamApps] Non-coloring of WSJT-X 2.2.0 -rc decodes by JTAlert - cause identified.

 

I finally tracked down the JTAlert non-coloring of decodes in the release candidates.
WSJT-X2.1.2 works correctly, but the -rcs don't when the decode string contains a positive report. Reports that are negative are colored correctly. Tested both rc2 & rc3

eg.

"AA1AA VK3AMA +12" & "AA1AA VK3AMA R+12" - FAIL

"AA1AA VK3AMA -12" & "AA1AA VK3AMA R-12" - OK

JTAlert sending the coloring command containing the "VK3AMA R-12" string correctly colors while "VK3AMA R+12" fails with the only difference is the number sign in the string sent to WSJT-X.

This report has already been sent to the WSJT-X dev-list.

de Laurie VK3AMA


locked Re: Worked B4 sometimes not working

HamApps Support (VK3AMA)
 

On 1/06/2020 10:12 pm, Steve Weeks wrote:
Laurie - I have noted two different anomalies repeatedly since loading rc3.  

1.  The one previously discussed in other messages, where JTAlert shows B4 entries colored correctly (grey in my case) but the coloring sporadically shows up on some, but not all, of the corresponding entries in the WSJT-X Band Activity list.

2.  Not all of the time, but not rarely either, the first 1 to 3 entries in the Band Activity window for a cycle do not show up at all in the JTAlert boxes.  Typically this happens when such early entries are very strong (+15 dB or higher) and I am guessing it may be a timing issue.  rc3 now displays decodes as they are decoded rather than collecting all of them for a phase of decoding and putting them in frequency order to display, and it starts the first phase of decoding (of the 3 phases that it now uses) before the 12.6 second Tx window is even completed.  If there are strong signals, they are decoded first and come out much earlier in the cycle than in prior versions, possibly (just a guess) before JTAlert is expecting them.

Maybe these issues are related.

Thank you for your amazing efforts in developing and maintaining this essential product.

73, Steve AA8SW

1. is due to a WSJT-X anomaly. If you look closely you will see that the non-colored decodes in WSJT-X (when they should be) have a positive signal report. I discovered this earlier today. See https://hamapps.groups.io/g/Support/message/30069
The WSJT-X devs are looking into it.

2. is fixed in the 2.16.6 build 0001 beta. See https://hamapps.groups.io/g/Support/message/30015

de Laurie VK3AMA

6561 - 6580 of 36473