Date   

locked Re: Decodes WIndow Active Filters

Laurie, VK3AMA
 



On 27/11/2020 2:21 am, David Ross wrote:
Solved.

Had to go to View Filter Controls and select any callsign there then click the "X" to delete that call. Window is now populating.

David VA3MJR

Even easier, use the "Filter -> Clear Callsign/Location" menu.


de Laurie VK3AMA



locked Re: Jtalerts support for JS8?

Jonathan
 

I concur that JS8 unfortunately seems to be used primarily as a beacon instead of QSO. That's too bad because the Fast and Turbo modes can be quite conversational.

Jonathan WD6BNY


locked Re: Decodes WIndow Active Filters

David Ross
 

Solved.

Had to go to View Filter Controls and select any callsign there then click the "X" to delete that call. Window is now populating.

David VA3MJR


locked Decodes WIndow Active Filters

David Ross
 

The Decodes window is not showing any activity.

I have somehow set a filter for KN4CNU. How do I delete this filter and get the Decodes window filling again?

David VA3MJR


locked Re: Jtalerts support for JS8?

Hasan Schiers N0AN
 

...and if you  have ever tried to use JS8CALL in a real conversation, you would find it tedious at best. At the throughput involved, one could hardly consider what takes place a "conversation".

It's one thing to have very low throughput to work rare and weak DX, it is entirely another to advertise something with horrid throughput as a "conversational" tool. 

..and yes, I did test it out when it was being ballyhooed by all the missionaries. 

73, N0AN
Hasan


On Wed, Nov 25, 2020 at 6:44 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
Short Answer:
  • Most likely never.
Long Answer:
  • Despite JS8/JS8Call being advertised as a conversation mode, the reality is that it tends to be used primarily as a beacon mode.

  • A frequent complaint of new JS8 users is the lack of QSOs, often complaining of many hours sending CQ's without a response. They check PSKReporter or HamSpots and see that many stations are receiving their signal. They send out heartbeats (is that the correct term?) and receive ACKs from many stations, but are still unable to raise a QSO.

  • Clearly there are many unattended JS8 stations that are auto-responding to heartbeats but with no-operator in attendance to actually engage in a QSO.

  • A frequent response from the JS8 community to complaints of a lack of QSOs is that the user should try a specific band at specific times to try and increase the chances of getting a Station with an operator in attendance to respond. Or to arrange a sked ahead of time.

JTAlert is designed to alert to decoded stations based on the users needs/wants.
Alerting on Beaconing stations (sending ACKs) is worthless, IMO, and is not suitable for JTAlert.

 
de Laurie, VK3AMA


locked Re: Jtalerts support for JS8?

HamApps Support (VK3AMA)
 

Short Answer:
  • Most likely never.
Long Answer:
  • Despite JS8/JS8Call being advertised as a conversation mode, the reality is that it tends to be used primarily as a beacon mode.

  • A frequent complaint of new JS8 users is the lack of QSOs, often complaining of many hours sending CQ's without a response. They check PSKReporter or HamSpots and see that many stations are receiving their signal. They send out heartbeats (is that the correct term?) and receive ACKs from many stations, but are still unable to raise a QSO.

  • Clearly there are many unattended JS8 stations that are auto-responding to heartbeats but with no-operator in attendance to actually engage in a QSO.

  • A frequent response from the JS8 community to complaints of a lack of QSOs is that the user should try a specific band at specific times to try and increase the chances of getting a Station with an operator in attendance to respond. Or to arrange a sked ahead of time.

JTAlert is designed to alert to decoded stations based on the users needs/wants.
Alerting on Beaconing stations (sending ACKs) is worthless, IMO, and is not suitable for JTAlert.

 
de Laurie, VK3AMA


locked Re: Jtalerts support for JS8?

Hasan Schiers N0AN
 

The question is, when is JS8call going to properly support JTAlert
Chicken vs Egg
73, N0AN
Hasan


On Wed, Nov 25, 2020 at 2:00 PM Gordon Brown <mr.hot.saab@...> wrote:
When is JTalerts going to support JS8call? It would be cool to support!


locked Re: Jtalerts support for JS8?

Bill Pence
 

Its js8 that needs to change as I understand the js8 devs removed the code needed to interoperate with other apps... 


On Wed, Nov 25, 2020, 3:00 PM Gordon Brown <mr.hot.saab@...> wrote:
When is JTalerts going to support JS8call? It would be cool to support!


locked Jtalerts support for JS8?

Gordon Brown
 

When is JTalerts going to support JS8call? It would be cool to support!


locked Re: LOTW data is often wrong

Barry VA7GEM
 

VP8LP also responded on LOTW 27DEC2009
Barry


locked Re: Mouse is not working in JTAlert latest version.

HamApps Support (VK3AMA)
 

On 25/11/2020 9:43 pm, Gerard de Veer wrote:
My mouse is not working anymore on JTAlert.
When I click on a alert it comes not in JTDX as a station that I can work.
Can you advice me.

Best 73

Gerard PD0GIP

It's not the mouse or JTAlert that is the problem. The problem is your JTDX settings.
You need to ensure "Accept UDP requests" is enabled in JTDX


de Laurie VK3AMA


locked Re: LOTW data is often wrong

Greg Yates
 

Same here, I have sent 4 times with green stamps going back to 2013 and no LOTW

 

Greg

WB2BIN

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Carlo - IK2RPE
Sent: Wednesday, November 25, 2020 2:21 AM
To: Support@hamapps.groups.io
Subject: Re: [HamApps] LOTW data is often wrong

 

VP8LP: Neil, you were very lucky! I sent requests directly to him (with Green stamps) three (!) times - the last one also as registered letter - and NO answer.

He does not answer to my mails. 

Others had same experience? 

 

Carlo IK2RPE 

 

(sorry, it is out of topic, here) 

 

Il mar 24 nov 2020, 14:21 Neil Foster <archernf@...> ha scritto:

VP8LP does NOT show as a user of LoTW, and has not for a long time in my system. However he responds quickly to a QSL card request.
Neil   N4FN


locked Mouse is not working in JTAlert latest version.

Gerard de Veer <gerard@...>
 

My mouse is not working anymore on JTAlert.
When I click on a alert it comes not in JTDX as a station that I can work.
Can you advice me.

Best 73

Gerard PD0GIP


locked Re: LOTW data is often wrong

Carlo - IK2RPE
 

VP8LP: Neil, you were very lucky! I sent requests directly to him (with Green stamps) three (!) times - the last one also as registered letter - and NO answer.
He does not answer to my mails. 
Others had same experience? 

Carlo IK2RPE 

(sorry, it is out of topic, here) 


Il mar 24 nov 2020, 14:21 Neil Foster <archernf@...> ha scritto:
VP8LP does NOT show as a user of LoTW, and has not for a long time in my system. However he responds quickly to a QSL card request.
Neil   N4FN


locked Re: LOTW data is often wrong

HamApps Support (VK3AMA)
 

On 25/11/2020 12:42 am, Torsten - DL9GTB wrote:
Sorry that I have not commented on this topic. I was on a business trip and unfortunately had little time. I have now taken a close look at it. The mistake is on my side, JTAlert is doing everything right. I trusted the data from QRZ.com. For example there is no LOTW with the callsigns EB3DIM or M0LMK. But these callsigns are entered in the LOW user list. I'm sorry for the confusion. But I also noticed differences to the data from Gridtracker in the past. Now I've found out why that is the case. I have set the LOTW upload filter to 1 year in the JTAlert settings, but not in Gridtracker. Sorry again for the false alarm, I guess I'm too old for this hobby. :-(

73 de Torsten - DL9GTB
Tnx Torsten.

The problem with QRZ is the LoTW membership flagging does not use the official LoTW membership list. It is left to the individual Callsign owners to set a flag as to whether they use Lotw. In the past I have encountered QRZ listed callsigns that indicate they use Lotw when they don't. There are no checks involved when an owner sets the state of the Lotw membership setting for their callsign. It cannot be relied upon to be reliable.

JTAlert uses the official LoTW membership list provided by the ARRL.

de Laurie VK3AMA



locked Re: DX boxes only display my own call on the 630 meter band?

HamApps Support (VK3AMA)
 

On 25/11/2020 2:04 am, Ken Miller wrote:

On 630 meters JTAlert does not display any DX contacts in the boxes.  It does displays my own callsign in those boxes when a DX station answers my CQ?  If two stations call at same time, two boxes light up with my call in them. 

Again, this only happens on 630 meters, all other bands display the callsign activity received on the bands as expected.

I suspect it might have something to do with the new mode FST4 that I only use on 630 meters perhaps?

I am using Windows 10, with DXKeeper 15.8.5 and WSJT-X v2.3.0-rc2 


JTAlert currently does not support FST4.

It does report the mode correctly and the logging facilities work, but there is no FST4 alerting. There is no ETA on that being available and it is not under development at this time.

de Laurie VK3AMA


 


locked Re: Directed CQ

HamApps Support (VK3AMA)
 

On 25/11/2020 10:07 am, Michael Black via groups.io wrote:
Is there a way to distinguish directed CQ's in the new Exp call window?
Mike W9MDB
Wrong group.

But yes, it simply follows the settings you have set in the JTAlert. It doesn't use the "*" or "#" indicators, but does use the colored border indicator.
This has previously been discussed in the Test group.

de Laurie VK3AMA


locked Re: Two instances of JT Alert

JoAnn Donaldson
 

I am using a Python Script to do the logging. I don't care about B4 stuff. All I want to do is have it Alert me of stations that I need.

JoAnn
AB8YZ


On Monday, November 23, 2020, 04:16:52 PM CST, Michael Black via groups.io <mdblack98@...> wrote:


You can use just an ADIF file.
Logger is highly recommended though.

Make sure you back up whatever log you use.

Mike W9MDB




On Monday, November 23, 2020, 04:04:51 PM CST, JoAnn Donaldson via groups.io <joannplano2005@...> wrote:


Can JTAlert work without having to connect to a Logger?

JoAnn
AB8YZ

On Monday, November 23, 2020, 3:42:14 PM CST, sp5apw <sp5apw@...> wrote:


In the beginning I didn't... But finally, when I did it all worked great!
Thank you so much Mike!
73
Jacek SP5APW

pon., 23 lis 2020 o 22:27 Michael Black via groups.io <mdblack98=yahoo.com@groups.io> napisał(a):

Did you change the Report port in the 2nd instance?  Each instance has to have a unique port.

Mike W9MDB
Inline image




On Monday, November 23, 2020, 03:22:54 PM CST, sp5apw <sp5apw@...> wrote:


Thanks for the quick answer! However the second JT Alert doesn't connect to WSJT-X:
image.png
Jacek SP5APW

pon., 23 lis 2020 o 22:07 Michael Black via groups.io <mdblack98=yahoo.com@groups.io> napisał(a):
Should be automatic....just run JTAlert twice after your start your WSJT-X instances.

Mike W9MDB




On Monday, November 23, 2020, 03:05:22 PM CST, sp5apw <sp5apw@...> wrote:


Hi,
I am working two instances of WSJT-X and would also like to have two instances of JT Alert, each one connected to a suitable instance of WSJT-X. Is it possible? If yes, how can it be configured?
I will appreciate your advice.
73
Jacek SP5APW


locked Directed CQ

Michael Black
 

Is there a way to distinguish directed CQ's in the new Exp call window?
Mike W9MDB



locked Re: LOTW data is often wrong

John Becker
 

For those who are having this issue, I hope you are aware that you need to have the latest version of the HamApps Callsign Database installed. This currently is at v2020.11.18. Scroll to the bottom of the page at https://hamapps.com/.

73,

John, K9MM

3141 - 3160 of 35446