Date   

locked Re: Decode not clearing

Dave Garber
 

under 'callers'  of callsign tab, there is an option for auto clear old.   check to see if you have inadvertently set it to no auto clear.   could that cause it....
Dave Garber
VE3WEJ / VE3IE


On Sat, May 22, 2021 at 12:32 PM John Holmes W9ILY <w9ily@...> wrote:
Laurie,
I just tried it again  with the results as shown. The received calls display appears to refresh at the 8 second mark in the decoding process on JTDX.
John


locked Re: Decode not clearing

John Holmes W9ILY
 

Laurie,
I just tried it again  with the results as shown. The received calls display appears to refresh at the 8 second mark in the decoding process on JTDX.
John


locked Re: Worked B4 still generating alert

OM Marlon, DW3CWM
 

Hi Paul,

 

AFAIK when we rebuild our JTalert database, it will refer and scan LOG4OM dbase SQLite, when a qso is not yet confirmed, JTDX and WSJtx see it as worked before but JT Alert triggers an audio alert if not LOTW confirmation for Logger. Must be the same with your.

 

73 de Marlon

 

Sent from Mail for Windows 10

 

From: Paul F6EXV
Sent: Saturday, 22 May 2021 6:07 pm
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Worked B4 still generating alert

 

Thanks !

Le 22/05/2021 à 10:09, OM Marlon, DW3CWM via groups.io a écrit :

Try this.

 

 

 

I can only suspect that play alert when decoded call worked b4 is also ticked with your config as mine

 

 

Marlon, DW3CWM

 

 

 

Sent from Mail for Windows 10

 

From: Paul F6EXV
Sent: Saturday, 22 May 2021 3:03 pm
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Worked B4 still generating alert

 

Hi Marlon
I search everywhere in the config, and cannot find the screen to check on that...
Please help me
73
Paul F6EXV

Le 22/05/2021 à 08:38, OM Marlon, DW3CWM via groups.io a écrit :

It happens to me as well. Am using the 3 softwares except that I have upgraded to the corrected rc156.  It would most likely be that you have configured for LOTW and/or eQsl confirmation and the qso have not yet been confirmed. It happens to me with  a Vietnam QSO. It generates an audio alert until the DXCC alert  has been cleared by another call confirmed QSO. I nornally will put that callsign, he has no LOTW anw, hihi, to temporary ignored list.

 

73 de Marlon DW3CWM

 

Sent from Mail for Windows 10

 

From: Paul F6EXV
Sent: Saturday, 22 May 2021 6:22 am
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Worked B4 still generating alert

 

No, both are the same callsign
I worked him, logged him OK, and in the next decodes, the alarm sounds again... It should not...
73
Paul F6EXV

Le 22/05/2021 à 00:06, Michael Black via groups.io a écrit :

It's probably either logged without the ZA prefix or you are seeing a decode without the ZA prefix.

 

Sound right?

 

Mike W9MDB

 

 

 

 

On Friday, May 21, 2021, 05:03:24 PM CDT, Paul F6EXV <f6exv@...> wrote:

 

 

Hi all

Using JTAlert version 2.50.1, JTDX version 2.2.0-rc152 and Log4OM

version 2.13.0.0

I work ZA/IK2RLM on 80m because I get an alert (new country on this

band). It logs OK. But next time this callsign appears, it still

triggers a new country alert.

It does show as B4 in JTDX. And I have configued JTAlert to not show

worked b4.

 

What am I missing ?

 

Thanks + 73

Paul F6EXV

 

--

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.

 

 

 

 

 

 

 

 

Garanti sans virus. www.avast.com

 

 

 

 

 


locked Re: Worked B4 still generating alert

Paul F6EXV
 

Thanks !

Le 22/05/2021 à 10:09, OM Marlon, DW3CWM via groups.io a écrit :

Try this.

 

 

 

I can only suspect that play alert when decoded call worked b4 is also ticked with your config as mine

 

 

Marlon, DW3CWM

 

 

 

Sent from Mail for Windows 10

 

From: Paul F6EXV
Sent: Saturday, 22 May 2021 3:03 pm
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Worked B4 still generating alert

 

Hi Marlon
I search everywhere in the config, and cannot find the screen to check on that...
Please help me
73
Paul F6EXV

Le 22/05/2021 à 08:38, OM Marlon, DW3CWM via groups.io a écrit :

It happens to me as well. Am using the 3 softwares except that I have upgraded to the corrected rc156.  It would most likely be that you have configured for LOTW and/or eQsl confirmation and the qso have not yet been confirmed. It happens to me with  a Vietnam QSO. It generates an audio alert until the DXCC alert  has been cleared by another call confirmed QSO. I nornally will put that callsign, he has no LOTW anw, hihi, to temporary ignored list.

 

73 de Marlon DW3CWM

 

Sent from Mail for Windows 10

 

From: Paul F6EXV
Sent: Saturday, 22 May 2021 6:22 am
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Worked B4 still generating alert

 

No, both are the same callsign
I worked him, logged him OK, and in the next decodes, the alarm sounds again... It should not...
73
Paul F6EXV

Le 22/05/2021 à 00:06, Michael Black via groups.io a écrit :

It's probably either logged without the ZA prefix or you are seeing a decode without the ZA prefix.

 

Sound right?

 

Mike W9MDB

 

 

 

 

On Friday, May 21, 2021, 05:03:24 PM CDT, Paul F6EXV <f6exv@...> wrote:

 

 

Hi all

Using JTAlert version 2.50.1, JTDX version 2.2.0-rc152 and Log4OM

version 2.13.0.0

I work ZA/IK2RLM on 80m because I get an alert (new country on this

band). It logs OK. But next time this callsign appears, it still

triggers a new country alert.

It does show as B4 in JTDX. And I have configued JTAlert to not show

worked b4.

 

What am I missing ?

 

Thanks + 73

Paul F6EXV

 

--

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.

 

 

 

 

 

 

 

 

Garanti sans virus. www.avast.com

 

 

 



locked Re: Worked B4 still generating alert

OM Marlon, DW3CWM
 

Try this.

 

 

 

I can only suspect that play alert when decoded call worked b4 is also ticked with your config as mine

 

 

Marlon, DW3CWM

 

 

 

Sent from Mail for Windows 10

 

From: Paul F6EXV
Sent: Saturday, 22 May 2021 3:03 pm
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Worked B4 still generating alert

 

Hi Marlon
I search everywhere in the config, and cannot find the screen to check on that...
Please help me
73
Paul F6EXV

Le 22/05/2021 à 08:38, OM Marlon, DW3CWM via groups.io a écrit :

It happens to me as well. Am using the 3 softwares except that I have upgraded to the corrected rc156.  It would most likely be that you have configured for LOTW and/or eQsl confirmation and the qso have not yet been confirmed. It happens to me with  a Vietnam QSO. It generates an audio alert until the DXCC alert  has been cleared by another call confirmed QSO. I nornally will put that callsign, he has no LOTW anw, hihi, to temporary ignored list.

 

73 de Marlon DW3CWM

 

Sent from Mail for Windows 10

 

From: Paul F6EXV
Sent: Saturday, 22 May 2021 6:22 am
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Worked B4 still generating alert

 

No, both are the same callsign
I worked him, logged him OK, and in the next decodes, the alarm sounds again... It should not...
73
Paul F6EXV

Le 22/05/2021 à 00:06, Michael Black via groups.io a écrit :

It's probably either logged without the ZA prefix or you are seeing a decode without the ZA prefix.

 

Sound right?

 

Mike W9MDB

 

 

 

 

On Friday, May 21, 2021, 05:03:24 PM CDT, Paul F6EXV <f6exv@...> wrote:

 

 

Hi all

Using JTAlert version 2.50.1, JTDX version 2.2.0-rc152 and Log4OM

version 2.13.0.0

I work ZA/IK2RLM on 80m because I get an alert (new country on this

band). It logs OK. But next time this callsign appears, it still

triggers a new country alert.

It does show as B4 in JTDX. And I have configued JTAlert to not show

worked b4.

 

What am I missing ?

 

Thanks + 73

Paul F6EXV

 

--

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.

 

 

 

 

 

 

 

 

Garanti sans virus. www.avast.com

 

 

 


locked Dual callsign

Paul F6EXV
 

Hi again
I am struggling very hard again on how to configure for 2 callsigns.
It was working fine with my previous version, now all messed up...
Let me explain :
I have 2 callsigns, which I want to be able to swich to easily.
I am using Log4OM as a logging program. I have the 2 profiles set there, and I can switch from one call to the other fine.
For one callsign, all works fine with JTDX and JTAlert.
For the other callsign, JTDX does decode OK, but the link betwenn JTAlert and JTDX no longer works.

Should the second callsign JTAlert config be identical to the first, or, if it must be different, what must change ?

The other option is to use JTAlert with 2 callsigns, but I just cannot figure out how to set it up...
Thanks + 73
Paul F6EXV



--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


locked Re: Worked B4 still generating alert

Paul F6EXV
 

Hi Marlon
I search everywhere in the config, and cannot find the screen to check on that...
Please help me
73
Paul F6EXV

Le 22/05/2021 à 08:38, OM Marlon, DW3CWM via groups.io a écrit :

It happens to me as well. Am using the 3 softwares except that I have upgraded to the corrected rc156.  It would most likely be that you have configured for LOTW and/or eQsl confirmation and the qso have not yet been confirmed. It happens to me with  a Vietnam QSO. It generates an audio alert until the DXCC alert  has been cleared by another call confirmed QSO. I nornally will put that callsign, he has no LOTW anw, hihi, to temporary ignored list.

 

73 de Marlon DW3CWM

 

Sent from Mail for Windows 10

 

From: Paul F6EXV
Sent: Saturday, 22 May 2021 6:22 am
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Worked B4 still generating alert

 

No, both are the same callsign
I worked him, logged him OK, and in the next decodes, the alarm sounds again... It should not...
73
Paul F6EXV

Le 22/05/2021 à 00:06, Michael Black via groups.io a écrit :

It's probably either logged without the ZA prefix or you are seeing a decode without the ZA prefix.

 

Sound right?

 

Mike W9MDB

 

 

 

 

On Friday, May 21, 2021, 05:03:24 PM CDT, Paul F6EXV <f6exv@...> wrote:

 

 

Hi all

Using JTAlert version 2.50.1, JTDX version 2.2.0-rc152 and Log4OM

version 2.13.0.0

I work ZA/IK2RLM on 80m because I get an alert (new country on this

band). It logs OK. But next time this callsign appears, it still

triggers a new country alert.

It does show as B4 in JTDX. And I have configued JTAlert to not show

worked b4.

 

What am I missing ?

 

Thanks + 73

Paul F6EXV

 

--

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.

 

 

 

 

 

 

 

 

Garanti sans virus. www.avast.com

 



locked Re: Worked B4 still generating alert

Paul F6EXV
 

Hi Joe
When he calls CQ, he gives no grid (his portable call does not allow it I think)
Every QSO I have with him has the same grid.
So the issue is somewhere else...
Now , I just saw something : when I check the log link in JTAlert, it does point to the correct log BUT the latest QSOs do not appear. The last QSO mentioned is dated several days ago. And the log indicated shows a lot of missing QSOs (in terms of number of QSOs).
A mess in my computer ?

73
Paul F6EXV

Le 22/05/2021 à 04:32, Joe Subich, W4TV a écrit :

I was seeing the same issue and worked through it with Laurie on
the beta group (since I'm using beta software).

Check the grid ZA/IK2RLM is using on the air vs. the grid you have
logged.

In my case, I worked OY1R who continued to alert.  When I checked
the log, the QSO had been logged as grid IP61nv due to a 10 year
old CW QSO.  Apparently, I tail-ended OY1R and did not get a grid
so either JTAlert or DXKeeper filled in the grid from the previous
QSO.

73,

   ... Joe, W4TV


On 2021-05-21 6:21 PM, Paul F6EXV wrote:
No, both are the same callsign
I worked him, logged him OK, and in the next decodes, the alarm sounds again... It should not...
73
Paul F6EXV

Le 22/05/2021 à 00:06, Michael Black via groups.io a écrit :
It's probably either logged without the ZA prefix or you are seeing a decode without the ZA prefix.

Sound right?

Mike W9MDB




On Friday, May 21, 2021, 05:03:24 PM CDT, Paul F6EXV <f6exv@hotmail.com> wrote:


Hi all
Using JTAlert version 2.50.1, JTDX version 2.2.0-rc152 and Log4OM
version 2.13.0.0
I work ZA/IK2RLM on 80m because I get an alert (new country on this
band). It logs OK. But next time this callsign appears, it still
triggers a new country alert.
It does show as B4 in JTDX. And I have configued JTAlert to not show
worked b4.

What am I missing ?

Thanks + 73
Paul F6EXV




--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


locked Re: Worked B4 still generating alert

OM Marlon, DW3CWM
 

It happens to me as well. Am using the 3 softwares except that I have upgraded to the corrected rc156.  It would most likely be that you have configured for LOTW and/or eQsl confirmation and the qso have not yet been confirmed. It happens to me with  a Vietnam QSO. It generates an audio alert until the DXCC alert  has been cleared by another call confirmed QSO. I nornally will put that callsign, he has no LOTW anw, hihi, to temporary ignored list.

 

73 de Marlon DW3CWM

 

Sent from Mail for Windows 10

 

From: Paul F6EXV
Sent: Saturday, 22 May 2021 6:22 am
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Worked B4 still generating alert

 

No, both are the same callsign
I worked him, logged him OK, and in the next decodes, the alarm sounds again... It should not...
73
Paul F6EXV

Le 22/05/2021 à 00:06, Michael Black via groups.io a écrit :

It's probably either logged without the ZA prefix or you are seeing a decode without the ZA prefix.

 

Sound right?

 

Mike W9MDB

 

 

 

 

On Friday, May 21, 2021, 05:03:24 PM CDT, Paul F6EXV <f6exv@...> wrote:

 

 

Hi all

Using JTAlert version 2.50.1, JTDX version 2.2.0-rc152 and Log4OM

version 2.13.0.0

I work ZA/IK2RLM on 80m because I get an alert (new country on this

band). It logs OK. But next time this callsign appears, it still

triggers a new country alert.

It does show as B4 in JTDX. And I have configued JTAlert to not show

worked b4.

 

What am I missing ?

 

Thanks + 73

Paul F6EXV

 

--

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.

 

 

 

 

 

 

 

 

Garanti sans virus. www.avast.com

 


locked Re: USB Port Shortage

Jim Denneny
 

Sent in error to wrong group.  Please ignore


locked Re: USB Port Shortage

Jim Denneny
 

You are right.  This belongs on K1EL Group.  I don't know what happened to cause this.  My error


locked Re: Worked B4 still generating alert

Joe Subich, W4TV
 

I was seeing the same issue and worked through it with Laurie on
the beta group (since I'm using beta software).

Check the grid ZA/IK2RLM is using on the air vs. the grid you have
logged.

In my case, I worked OY1R who continued to alert. When I checked
the log, the QSO had been logged as grid IP61nv due to a 10 year
old CW QSO. Apparently, I tail-ended OY1R and did not get a grid
so either JTAlert or DXKeeper filled in the grid from the previous
QSO.

73,

... Joe, W4TV

On 2021-05-21 6:21 PM, Paul F6EXV wrote:
No, both are the same callsign
I worked him, logged him OK, and in the next decodes, the alarm sounds again... It should not...
73
Paul F6EXV
Le 22/05/2021 à 00:06, Michael Black via groups.io a écrit :
It's probably either logged without the ZA prefix or you are seeing a decode without the ZA prefix.

Sound right?

Mike W9MDB




On Friday, May 21, 2021, 05:03:24 PM CDT, Paul F6EXV <f6exv@hotmail.com> wrote:


Hi all
Using JTAlert version 2.50.1, JTDX version 2.2.0-rc152 and Log4OM
version 2.13.0.0
I work ZA/IK2RLM on 80m because I get an alert (new country on this
band). It logs OK. But next time this callsign appears, it still
triggers a new country alert.
It does show as B4 in JTDX. And I have configued JTAlert to not show
worked b4.

What am I missing ?

Thanks + 73
Paul F6EXV


locked Re: USB Port Shortage

David De Coons
 

Wrong group but my two cents, get a powered USB 2.0 hub.

Dave wo2x


On May 21, 2021, at 7:57 PM, neil_zampella <neilz@...> wrote:



OM .. I think you posted in the wrong group ... this is the JTAlert support group.

 

Neil, KN3ILZ

 

On Fri, May 21, 2021 at 06:29 PM, Jim Denneny wrote:

Hi.  I have a WinKeyer USB.  I have run out of USB ports on my PC.  In fact WinKeyer USB shares a comport with DXL Suites WinWarbler app.  I need to eliminate the conflict.  I have a 4 port Edgeport device with two DB9 ports available.  I cannot find a convertor that will enable me to use the keyer with a DB9 connection.

I am tempted to purchase the original WinKeyer as it has a DB9 interface.  Is it available assembled?  I am open to any suggestion to get my usb keyer off my pc usb port.

73, Jim K7EG


locked Re: USB Port Shortage

neil_zampella
 

OM .. I think you posted in the wrong group ... this is the JTAlert support group.

 

Neil, KN3ILZ

 

On Fri, May 21, 2021 at 06:29 PM, Jim Denneny wrote:

Hi.  I have a WinKeyer USB.  I have run out of USB ports on my PC.  In fact WinKeyer USB shares a comport with DXL Suites WinWarbler app.  I need to eliminate the conflict.  I have a 4 port Edgeport device with two DB9 ports available.  I cannot find a convertor that will enable me to use the keyer with a DB9 connection.

I am tempted to purchase the original WinKeyer as it has a DB9 interface.  Is it available assembled?  I am open to any suggestion to get my usb keyer off my pc usb port.

73, Jim K7EG


locked Re: USB Port Shortage

AB8WD-Willie
 

My 2 cents you can buy cards and usb hubs not sure where this is going


locked USB Port Shortage

Jim Denneny
 

Hi.  I have a WinKeyer USB.  I have run out of USB ports on my PC.  In fact WinKeyer USB shares a comport with DXL Suites WinWarbler app.  I need to eliminate the conflict.  I have a 4 port Edgeport device with two DB9 ports available.  I cannot find a convertor that will enable me to use the keyer with a DB9 connection.

I am tempted to purchase the original WinKeyer as it has a DB9 interface.  Is it available assembled?  I am open to any suggestion to get my usb keyer off my pc usb port.

73, Jim K7EG


locked Re: Worked B4 still generating alert

Paul F6EXV
 

No, both are the same callsign
I worked him, logged him OK, and in the next decodes, the alarm sounds again... It should not...
73
Paul F6EXV

Le 22/05/2021 à 00:06, Michael Black via groups.io a écrit :
It's probably either logged without the ZA prefix or you are seeing a decode without the ZA prefix.

Sound right?

Mike W9MDB




On Friday, May 21, 2021, 05:03:24 PM CDT, Paul F6EXV <f6exv@...> wrote:


Hi all
Using JTAlert version 2.50.1, JTDX version 2.2.0-rc152 and Log4OM
version 2.13.0.0
I work ZA/IK2RLM on 80m because I get an alert (new country on this
band). It logs OK. But next time this callsign appears, it still
triggers a new country alert.
It does show as B4 in JTDX. And I have configued JTAlert to not show
worked b4.

What am I missing ?

Thanks + 73
Paul F6EXV

--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.








Garanti sans virus. www.avast.com


locked Re: Worked B4 still generating alert

Michael Black
 

It's probably either logged without the ZA prefix or you are seeing a decode without the ZA prefix.

Sound right?

Mike W9MDB




On Friday, May 21, 2021, 05:03:24 PM CDT, Paul F6EXV <f6exv@...> wrote:


Hi all
Using JTAlert version 2.50.1, JTDX version 2.2.0-rc152 and Log4OM
version 2.13.0.0
I work ZA/IK2RLM on 80m because I get an alert (new country on this
band). It logs OK. But next time this callsign appears, it still
triggers a new country alert.
It does show as B4 in JTDX. And I have configued JTAlert to not show
worked b4.

What am I missing ?

Thanks + 73
Paul F6EXV

--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.







locked Worked B4 still generating alert

Paul F6EXV
 

Hi all
Using JTAlert version 2.50.1, JTDX version 2.2.0-rc152 and Log4OM version 2.13.0.0
I work ZA/IK2RLM on 80m because I get an alert (new country on this band). It logs OK. But next time this callsign appears, it still triggers a new country alert.
It does show as B4 in JTDX. And I have configued JTAlert to not show worked b4.

What am I missing ?

Thanks + 73
Paul F6EXV

--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


locked Re: Decode not clearing

John Holmes W9ILY
 
Edited

Laurie,

i rolled back to RC155 and there was no change. I think you are correct in that the call clear instruction is not being received. When I double click on the number of QSOs, it sometimes clears but other times a "waiting" circular image is shown like the CPU is maxed out. I have included several screen shots including one where of Task Manager where JTAlert is not running. JTAlert is using a lot of processing. I had completely rebooted and reloaded the JTAlert program after all this started and there was no difference.
John W9ILY

2901 - 2920 of 37815