Topics

locked Jtalerts support for JS8?


Gordon Brown
 

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


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!


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!


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


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


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