Topics

locked WSJT-X v2.4.0-rc1 Q65


William Thomas
 

When using the new Q65 mode, I only see my call letters displayed in JTAlert, not the station I’m working.  Another operator told me they are seeing the same thing. 


73 Bill WT0DX


neil_zampella
 

I'm not sure if Laurie has Q65 setup in JT-Alert, many of the EME modes (outside of JT65/JT9) are not covered either.   

Neil, KN3ILZ


Hasan Schiers N0AN
 

You won't see them in the Grid Display until Laurie adds them. If you are using JTA with a logging program, when call the station in X, it will show up with Call, Name, Grid etc
73, N0AN
Hasan


On Thu, Feb 11, 2021 at 7:29 AM neil_zampella <neilz@...> wrote:

I'm not sure if Laurie has Q65 setup in JT-Alert, many of the EME modes (outside of JT65/JT9) are not covered either.   

Neil, KN3ILZ


HamApps Support (VK3AMA)
 

On 11/02/2021 2:08 pm, William Thomas wrote:

When using the new Q65 mode, I only see my call letters displayed in JTAlert, not the station I’m working.  Another operator told me they are seeing the same thing. 


73 Bill WT0DX


At the time of the current 2.16.17 JTAlert release (December 6  2020) my "Crystal Ball" was in the shop for repair so I was unable to foresee the availability of the new Q65 mode with the release of WSJT-X 2.4.0-rc1 which occurred on February 3 2021, just shy of 2 months after the current JTAlert release.

The first I became aware of Q65 was in the release announcement of 2.4.0-rc from the post by K1JT. See https://sourceforge.net/p/wsjt/mailman/wsjt-devel/thread/4e54822e-3f67-c564-dd32-0ff13d486715%40princeton.edu/#msg37211965

The next release of JTAlert recognizes Q65 decodes.

de Laurie VK3AMA



Michael Black
 

And FST4W?

Mike W9MDB




On Thursday, February 11, 2021, 03:29:08 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 11/02/2021 2:08 pm, William Thomas wrote:

When using the new Q65 mode, I only see my call letters displayed in JTAlert, not the station I’m working.  Another operator told me they are seeing the same thing. 


73 Bill WT0DX


At the time of the current 2.16.17 JTAlert release (December 6  2020) my "Crystal Ball" was in the shop for repair so I was unable to foresee the availability of the new Q65 mode with the release of WSJT-X 2.4.0-rc1 which occurred on February 3 2021, just shy of 2 months after the current JTAlert release.

The first I became aware of Q65 was in the release announcement of 2.4.0-rc from the post by K1JT. See https://sourceforge.net/p/wsjt/mailman/wsjt-devel/thread/4e54822e-3f67-c564-dd32-0ff13d486715%40princeton.edu/#msg37211965

The next release of JTAlert recognizes Q65 decodes.

de Laurie VK3AMA



Joe Subich, W4TV
 

And FST4W?
FST4W *IS NOT A QSO MODE* it is a VLF replacement for WSPR (which
is also not supported by JTALERT for very good reason) a beacon
protocol and colossal waste of bandwidth.

73,

... Joe, W4TV


On 2021-02-11 4:32 PM, Michael Black via groups.io wrote:
And FST4W?
Mike W9MDB
On Thursday, February 11, 2021, 03:29:08 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@gmail.com> wrote:
On 11/02/2021 2:08 pm, William Thomas wrote:
When using the new Q65 mode, I only see my call letters displayed in JTAlert, not the station I’m working.  Another operator told me they are seeing the same thing.
73 Bill WT0DX
At the time of the current 2.16.17 JTAlert release (December 6  2020) my "Crystal Ball" was in the shop for repair so I was unable to foresee the availability of the new Q65 mode with the release of WSJT-X 2.4.0-rc1 which occurred on February 3 2021, just shy of 2 months after the current JTAlert release.
The first I became aware of Q65 was in the release announcement of 2.4.0-rc from the post by K1JT. See https://sourceforge.net/p/wsjt/mailman/wsjt-devel/thread/4e54822e-3f67-c564-dd32-0ff13d486715%40princeton.edu/#msg37211965
The next release of JTAlert recognizes Q65 decodes.
de Laurie VK3AMA


Jamie GOLLY
 

Laurie, thank you so much for your never ending improvements with. JT Alert!!!


Jamie
K6NGN

On Feb 11, 2021, at 2:30 PM, Joe Subich, W4TV <lists@subich.com> wrote:


And FST4W?
FST4W *IS NOT A QSO MODE* it is a VLF replacement for WSPR (which
is also not supported by JTALERT for very good reason) a beacon
protocol and colossal waste of bandwidth.

73,

... Joe, W4TV


On 2021-02-11 4:32 PM, Michael Black via groups.io wrote:
And FST4W?
Mike W9MDB
On Thursday, February 11, 2021, 03:29:08 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@gmail.com> wrote:
On 11/02/2021 2:08 pm, William Thomas wrote:
When using the new Q65 mode, I only see my call letters displayed in JTAlert, not the station I’m working. Another operator told me they are seeing the same thing.
73 Bill WT0DX
At the time of the current 2.16.17 JTAlert release (December 6 2020) my "Crystal Ball" was in the shop for repair so I was unable to foresee the availability of the new Q65 mode with the release of WSJT-X 2.4.0-rc1 which occurred on February 3 2021, just shy of 2 months after the current JTAlert release.
The first I became aware of Q65 was in the release announcement of 2.4.0-rc from the post by K1JT. See https://sourceforge.net/p/wsjt/mailman/wsjt-devel/thread/4e54822e-3f67-c564-dd32-0ff13d486715%40princeton.edu/#msg37211965
The next release of JTAlert recognizes Q65 decodes.
de Laurie VK3AMA





HamApps Support (VK3AMA)
 

On 12/02/2021 8:32 am, Michael Black via groups.io wrote:
And FST4W?


FST4 is already supported, but FST4W, like WSPR is not. Not much point in alerting on beacon modes, IMO.

de


William Thomas
 

Thanks Laurie, I never doubted that Q65 would be supported. 

73 Bill WT0DX