|
|
Post by Fred k1io on Mar 21, 2023 20:44:00 GMT
A nice feature for polite operation is "Halt TX if operator I called answered other operator." This is an option in the Sequencing part of Settings. I normally keep this on. But in a pile-up, especially when the DX is running MSHV (?) mode, I don't want it on. Hound mode of course disables it but I don't think that works in FT4 and may have other implications; for one thing it omits the "73" (Tx5). So rather than go deep into settings, it would be nice if that button were exposed, like AnsB4 is, or at least from a drop-down. That would make it easier to turn on and turn off. (writing this while iit's off, trying to complete a QSO to the 9X5 DXpedition!)
|
|
|
|
Post by Arvo ES1JA on Mar 21, 2023 20:56:54 GMT
I don’t see any need for this, sry. I never used this option from settings even. Use correctly configured counters there.
|
|
|
|
Post by Fred k1io on Mar 21, 2023 21:19:20 GMT
Do you just leave it off? The advantage of using it is that when you are not in a pile-up and have it on, it does NOT transmit while the guy who DID get the QSO (i.e., not you) is sending the signal report. So you are not transmitting as often, and can see, in the wide graph, if somebody else has slipped onto your frequency during your time slot. I then turn Enable TX back on just before it's time to answer the RR73.
I don't see a similar option in WSJT-X so I assume it's one of those nice improvements that JTDX made. I like it.
|
|
|
|
Post by Arvo ES1JA on Mar 22, 2023 6:02:58 GMT
OK, monitoring of own frequency is good point, still will not add nothing into main screen, but will try change functionality of this settings to Halt/Restore Tx. Restoring will take place when jtdx receives 73 like message or CQ from callsign caused stop tx and this call still in DX Call window.
This will be improvement of jtdx in mine mind.
|
|
|
|
Post by Fred k1io on Jun 18, 2023 22:15:26 GMT
I've come across another bug in the HaltTX feature which might be worked around by a button on the main screen, though a real fix would be nicer. If the DX is using Fox/Hound or, on a regular frequency, MSHV, and I call the DX, and have the Halt TX function set (polite mode, which I usually keep on), then when the DX calls me *and* simultaneously calls someone else, then it does not transmit. It prioritizes the fact that the DX called someone else over the fact that the DX also called me. So being called should restore TX at any time.
Here's an example:
220245 Tx 1785 ~ A71UN K1IO FN42 <- I call the DX
220300 -18 -1.1 1164 ~ EA8DNP A71UN -08 •Qatar <- The DX calls someone else. Enable TX goes off.
220300 -19 -1.1 1344 ~ K1IO A71UN -17 •Qatar <- The DX simultaneously calls me
220317 Tx 1785 ~ A71UN K1IO R-19 <- It did not transmit at the normal time so I pressed the Enable TX button manually, but was late
220330 -21 -1.1 1344 ~ K1IO A71UN -17 °Qatar <- He calls me again
220345 Tx 1785 ~ A71UN K1IO R-21 <- I try again, on time, but there's QSB
220400 -16 -1.1 1284 ~ GR4FKI A71UN -06 •Qatar <- He calls someone else but has given up on me
220416 Tx 1785 ~ A71UN K1IO R-21 <- I manually press Enable TX to try again
220430 -14 -1.1 1164 ~ GR4FKI A71UN +00 •Qatar
220447 Tx 1500 ~ A71UN K1IO FN42 <- I try again, manually
220500 -13 -1.1 1164 ~ GR4FKI A71UN RR73 °Qatar <- No QSO
Thanks... |
|
