Date
1 - 5 of 5
Did TX enable function change in call roster?
|
John Morphet
In the past, I would click on callsign in call roster. If the callsign was calling CQ, Gridtracker would enable transmit in WSJT-X. If the callsign was somewhere else in the process, Gridtracker would tell WSJT-X to monitor the caller and not transmit. Now it tells WSJT-X to enable transmit no matter where in the process the caller happens to be. I did install the latest version of WSJT-X (2.6) at the same time as the latest version of Gridtracker, so I am not sure which program changed. Does anyone know if there is a setting that can modified to get it to operate the old way?
John, W0ZI |
|
|
|
Charles Albert
I wonder if the same function is available with JTDX On Mon, Jan 9, 2023 at 10:01 AM John Morphet <jmorphet@...> wrote: In the past, I would click on callsign in call roster. If the callsign was calling CQ, Gridtracker would enable transmit in WSJT-X. If the callsign was somewhere else in the process, Gridtracker would tell WSJT-X to monitor the caller and not transmit. Now it tells WSJT-X to enable transmit no matter where in the process the caller happens to be. I did install the latest version of WSJT-X (2.6) at the same time as the latest version of Gridtracker, so I am not sure which program changed. Does anyone know if there is a setting that can modified to get it to operate the old way? --
de KC6UFM Charles |
|
|
|
Andrew B., KF6LU
Same action with newest version 123.0110. I prefer the way it worked before as W0ZI described.
|
|
|
|
Andrew B., KF6LU
Any plan in the future to revert to the previous function as explained by John. I can't believe that others find going directly to transmit except on a CQ call is a good way to operate.
|
|
|
|
I agree. Was this something to do with the RR73 issue?
Bob G8HGN |
|
|