|
|
Post by Fred k1io on Nov 13, 2022 20:33:10 GMT
I don't think this is a setting I'm missing but please correct me if I am... If I am calling a DX station and decide to abort the call with Halt TX, like for example because I hit Enable TX at the wrong time and it enabled rather than disabled (I hate toggles...), then it not only halts the transmission, but it clears the DX from the window and puts me in CQ mode (Tx6). I'd rather not clear the DX until I really mean to. Could this be an option? I don't think WSJT-X behaves this way, though I prefer JTDX for various other reasons.
|
|
|
|
Post by Arvo ES1JA on Nov 13, 2022 21:27:41 GMT
Halt Tx is intended for emergency break wrong current transmission, but it will not clear DX window, if DX window is cleared then reason for this is something else, probably some QSO counter overflow. For knowing why, enable in Settings/Reporting decoded and debug messages into ALL.TXT
Then if You see disappearing callsign from DX window, look from this file why DX window is cleared. ALL.TXT file is recorded in log dir.
|
|
|
|
Post by Fred k1io on Nov 15, 2022 18:24:52 GMT
What may actually be happening is actually a different issue. I have "Halt TX if operator called answered a different operator", so I don't call someone again until he 73s. But that clears the DX window. I'd rather it leave the DX there so I don't have to double click on it again when he 73s, just reenable TX. Maybe this should be an option.
|
|
|
|
Post by Fred k1io on Nov 15, 2022 18:29:14 GMT
BTW what I just described is inconsistent. I called EA8JK several times and every time he answered another station, the window cleared. Then I called PJ7FM and it didn't clear when he called someone else, it just disabled TX, as desired. (My peanut whistle doesn't have a very high hit rate on DX.)
|
|
|
|
Post by Arvo ES1JA on Nov 16, 2022 7:53:35 GMT
As I sad enable debug and see why DX is cleared or Tx halted or both. Maybe there is also error in program, but from debug will be clear where.
|
|
|
|
Post by Fred k1io on Nov 17, 2022 4:26:57 GMT
Okay, I think I have an example. I tried calling E7BOSNIA and he called someone else (K8LY). That turned off Enable TX based on the polite option I had set. I waited the usual 30 seconds until the QSO would have been ready for the next call and re-enabled TX, but it sent CQ instead: 20221117_041015 -14 0.1 1089 ~ CQ W4SBH EL96
20221117_041015 -14 -0.1 1005 ~ K8LY E7BOSNIA -04
20221117_041029.196(0) Halt Tx triggered at RX: readFromStdout, not owner of the frequency or reply to other
20221117_041015 -13 -0.1 1546 ~ HA5BP KI8JP -09
20221117_041015 -13 0.1 427 ~ R4FS IK0HBN -12
20221117_041015 -15 0.1 2021 ~ RA4DR SV1ABB -16
20221117_041015 -9 0.4 868 ~ TF2MSN W6GLR EM74
20221117_041015 -10 0.8 976 ~ <...> OK2SFP JN99
20221117_041015 -15 -0.4 617 ~ WA1HCO R2ZA -13
20221117_041015 -15 0.6 1230 ~ RA4DR HA1BF 73 ^
20221117_041015 -16 0.1 585 ~ CQ YY4RCT FK50 ^
20221117_041015 -19 0.1 2589 ~ KD2FRX MM0DGR -21
20221117_041015 -18 0.3 354 ~ UV5EEO F5OYA/P 73
20221117_041015 -12 0.1 1305 ~ <...> N0PUI EN34
20221117_041015 -13 0.1 1146 ~ K1JEA YO4DG -12
20221117_041015 -20 0.0 472 ~ K1NV ZS1CF RRR ^
20221117_041029.312(0) hisCall:E7BOSNIA time:14985 autoseq: status: RCQ count: 0 prio: 8
20221117_041029.312(0) DX Call E7BOSNIA cleared, RCQ/SCALL/SREPORT count reached
Counters: answerCQ-On value=4; answerInCall-On value=3; sentRReport-On value=5; sentRR7373-On value=5
20221117_041029.327(0) Decoding finished
20221117_041043.430(0) JTDX v2.2.1592a0e2b Transmitting 7.074 MHz + 2197Hz FT8: CQ K1IO FN42
AF TX/RX 2197/1005Hz AutoSeq2-On AutoTx-On SShotQSO-On Hound mode-Off
Skip Tx1-Off HaltTxReplyOther-On
20221117_041043.662(0) handle_transceiver_update started, current rig state: PTT Off, requested state: PTT On, m_tx_when_ready: true, g_iptt=1
20221117_041043.662(0) ptt1Timer started
20221117_041043.662(0) handle_transceiver_update PTT On Split On s.frequency:7074000 s.tx_frequency:7074500
20221117_041043.767(0) Modulator started
20221117_041044.232(0) handle_transceiver_update started, current rig state: PTT On, requested state: PTT Off, m_tx_when_ready: false, g_iptt=0
20221117_041044.232(0) handle_transceiver_update PTT Off Split On s.frequency:7074000 s.tx_frequency:7074500
20221117_041044.452(0) handle_transceiver_update started, current rig state: PTT Off, requested state: PTT Off, m_tx_when_ready: false, g_iptt=0
20221117_041044.452(0) handle_transceiver_update PTT Off Split On s.frequency:7074000 s.tx_frequency:7074500
20221117_041058.811(0) Decoder started SWL Off, cycles: 1
I never hit the Clear DX or Tx 6 buttons.
I watched it again and the "Clear DX" function happened by itself the moment E7BOSNIA answered someone else after I had only called it twice: 042130 Tx 2080 ~ E7BOSNIA K1IO FN42
042145 -14 0.0 1012 ~ PZ5MA VE6TOM DN49 Canada **This just happened to be on the E7's frequency so it's in the RX window
042145 -17 -0.1 1005 ~ KO4VTJ E7BOSNIA -12 •Bosnia-Herzegovina ** He called someone else
20221117_042145 -17 -0.1 1005 ~ KO4VTJ E7BOSNIA -12
20221117_042159.286(0) Halt Tx triggered at RX: readFromStdout, not owner of the frequency or reply to other
20221117_042145 -22 0.1 1497 ~ KA1VV NA4C +02
20221117_042145 -23 0.2 538 ~ KO4DRY HB9JNM JN47 ^
20221117_042145 -20 0.5 782 ~ PZ5MA AA6XX -05 ^
20221117_042159.302(0) hisCall:E7BOSNIA time:15690 autoseq: status: SCALL count: 1 prio: 8
20221117_042159.317(0) DX Call E7BOSNIA cleared, RCQ/SCALL/SREPORT count reached
Counters: answerCQ-On value=4; answerInCall-On value=3; sentRReport-On value=5; sentRR7373-On value=5
20221117_042159.317(0) Decoding finished
20221117_042205.822(0) handle_transceiver_update started, current rig state: PTT Off, requested state: PTT Off, m_tx_when_ready: false, g_iptt=0
20221117_042205.822(0) handle_transceiver_update PTT Off Split Off s.frequency:7074000 s.tx_frequency:0
20221117_042206.033(0) handle_transceiver_update started, current rig state: PTT Off, requested state: PTT Off, m_tx_when_ready: false, g_iptt=0
20221117_042206.033(0) handle_transceiver_update PTT Off Split Off s.frequency:7074000 s.tx_frequency:0
|
|
|
|
Post by Arvo ES1JA on Nov 17, 2022 10:11:05 GMT
20221117_041015 -14 -0.1 1005 ~ K8LY E7BOSNIA -04 20221117_041029.196(0) Halt Tx triggered at RX: readFromStdout, not owner of the frequency or reply to other At this point Enable Tx cleared, You have enabled Halt Tx when operatorI called answered to other operator further in same decodeing period 20221117_041029.312(0) DX Call E7BOSNIA cleared, RCQ/SCALL/SREPORT count reached Counters: answerCQ-On value=4; answerInCall-On value=3; sentRReport-On value=5; sentRR7373-On value=5 20221117_041029.327(0) Decoding finished there is reason why DX call is cleared second fragment is the same. Halt triggered by reply to other and Dx Call cleared by first counter overflow. For understanding counter values longer fragment needed.
And use Autoseq3 and enable Early start of decoder.
|
|
|
|
Post by Fred k1io on Nov 17, 2022 16:38:53 GMT
I did have early start of decoder set; I can switch to Autoseq 3.
I'm not sure that the counters are correct. I never got a callback from the DX. I tried calling several times but the RR73 counter to that station should have been 0 or so. I did make multiple attempts to call him but those counters should not clear the DX window. I wonder if the wrong counter is being incremented.
|
|
|
|
Post by Fred k1io on Nov 26, 2022 5:23:05 GMT
Here's another example from tonight. I wanted to call K4IO. I called him at 044048, but he called CQ again after my call:
20221126_044044.289(0) Decoding finished
20221126_044048.833(0) double click on call processed: K4IO; EnableTx On, AutoTx On
20221126_044048.870(0) JTDX v2.2.1592a0e2b Transmitting 7.074 MHz + 2007Hz FT8: K4IO K1IO FN42
AF TX/RX 2007/643Hz AutoSeq3-On AutoTx-On SShotQSO-On Hound mode-Off
Skip Tx1-Off HaltTxReplyOther-On
20221126_044049.033(0) handle_transceiver_update started, current rig state: PTT Off, requested state: PTT On, m_tx_when_ready: true, g_iptt=1
I answered his CQ again 30 seconds later. I guess he couldn't hear me on the split frequency I was on. Then he answered someone else and I had a QSO with an HA1. Several minutes later, after unsuccessfully calling SV5AZP, I heard K4IO again, in a QSO with EA7HHJ, and called him.
20221126_044815 -19 0.1 2164 ~ CQ KE3QZ FM18 *
20221126_044829.274(0) hisCall:SV5AZP time:17280 autoseq: status: RCQ count: 2 prio: 20
20221126_044829.274(0) Decoding finished
20221126_044841.390(0) double click on call processed: K4IO; EnableTx On, AutoTx On
20221126_044843.796(0) Decoder started SWL Off, cycles: 1
20221126_044830 -3 0.1 1051 ~ CQ W4MJH EM63 ^
20221126_044830 -13 0.2 643 ~ EA7HHJ K4IO R-11
20221126_044843.975(0) Halt Tx triggered at RX: readFromStdout, not owner of the frequency or reply to other
And when his QSO was finished I thought I was going to call him again, and may have had Enable TX off before this:
20221126_044844.226(0) hisCall:K4IO time:17190 autoseq: status: RCQ count: 0 prio: 6
20221126_044844.226(0) DX Call K4IO cleared, RCQ/SCALL/SREPORT count reached
Counters: answerCQ-On value=4; answerInCall-On value=3; sentRReport-On value=5; sentRR7373-On value=5
20221126_044844.226(0) Decoding finished
20221126_044845.054(0) JTDX v2.2.1592a0e2b Transmitting 7.074 MHz + 2344Hz FT8: CQ K1IO FN42
AF TX/RX 2344/643Hz AutoSeq3-On AutoTx-On SShotQSO-On Hound mode-Off
Skip Tx1-Off HaltTxReplyOther-On
In other words, just as I was calling him after his RR73, the DX window cleared and JTDX called CQ instead. So I waited another cycle before calling him again.
Ironically, some minutes after I finally had the QSO with K4IO, and logged it, that QSO remained in the DX window, so to send CQ I would need to press TX6. (1 QSO is set.) But I would prefer this (leaving the window full) to having it clear when I don't want it to!
|
|
|
|
Post by Arvo ES1JA on Nov 26, 2022 8:12:26 GMT
Hopefully I got the root of problem.
|
|
|
|
Post by pa3dai on Mar 30, 2023 13:47:49 GMT
As I sad enable debug and see why DX is cleared or Tx halted or both. Maybe there is also error in program, but from debug will be clear where. Arvo, I have the same problem :TX stop, DX Call RZ1O cleared. This says All.txt: 20230330_124915 -3 0.2 1816 ~ R1CBS/P RZ1O LP04 20230330_124915 -19 0.6 1758 ~ DL4GK R6DRW R-03 20230330_124915 -13 0.3 1017 ~ CQ WB2BIN FN23 ^ 20230330_124930.342(0) Decoding finished 20230330_124944.705(0) Decoder started SWL On, cycles: 1 20230330_124930 -2 0.6 1694 ~ CQ EA7LZ IM76 ^ What's the problem ? David Pa3DAI |
|
|
|
Post by Arvo ES1JA on Mar 30, 2023 16:22:52 GMT
Here not seen any cleared actions, probably to short fragment.
|
|
|
|
Post by pa3dai on Mar 31, 2023 9:22:24 GMT
Sorry Arvo, here 2 cleared bug reports:
20230330_115245 -16 0.3 844 ~ GM0MEM VK3AXI RR73
20230330_115245 -11 0.4 672 ~ US7TX EA4WC -03 ^
20230330_115245 -13 0.3 1806 ~ DO2SBS RV6F LN14
20230330_115245 -24 0.1 1673 ~ YO8TVD EA3CSK JN11 ^
20230330_115300.573(0) hisCall:RZ1O time:42660 autoseq: status: SCALL count: 3 prio: 0
20230330_115300.580(0) DX Call RZ1O cleared, RCQ/SCALL/SREPORT count reached
Counters: answerCQ-On value=4; answerInCall-On value=4; sentRReport-Off value=3; sentRR7373-Off value=2
20230330_115300.582(0) Decoding finished
20230330_115314.707(0) Decoder started SWL On, cycles: 1
20230330_115300 3 0.9 1263 ~ CQ EA5GXE IM99
20230330_115300 1 0.4 1571 ~ CQ EA1ISE IN83 ^
20230330_115300 3 0.3 1065 ~ PB7Z TF1A RR73 ^
20230330_115915 -21 0.1 1360 ~ CQ 7Z1AL LL56 *
20230330_115915 -20 0.3 867 ~ CQ DL2FHS JN49 *
20230330_115930.098(0) JTDX v2.2.159000000 Transmitting 21.074 MHz + 1130Hz FT8: RZ1O PA3DAI JO21
AF TX/RX 1130/667Hz AutoSeq1-On AutoTx-On SShotQSO-On Hound mode-Off
Skip Tx1-Off HaltTxReplyOther-Off
20230330_115930.313(0) handle_transceiver_update started, current rig state: PTT Off, requested state: PTT On, m_tx_when_ready: true, g_iptt=1
20230330_115930.313(0) ptt1Timer started
20230330_115930.314(0) handle_transceiver_update PTT On Split On s.frequency:21074000 s.tx_frequency:21073500
20230330_115930.324(0) hisCall:RZ1O time:43170 autoseq: status: SCALL count: 0 prio: 0
20230330_115930.331(0) DX Call RZ1O cleared, RCQ/SCALL/SREPORT count reached
Counters: answerCQ-On value=4; answerInCall-On value=4; sentRReport-Off value=3; sentRR7373-Off value=2
20230330_115930.333(0) Halt Tx triggered at TX: m_singleshot, counter triggered 21.074 MHz FT8: RZ1O PA3DAI JO21
20230330_115930.333(0) Decoding finished
20230330_115930.381(0) handle_transceiver_update started, current rig state: PTT On, requested state: PTT On, m_tx_when_ready: false, g_iptt=1
20230330_115930.382(0) handle_transceiver_update PTT On Split On s.frequency:21074000 s.tx_frequency:21073500
20230330_115930.426(0) Modulator started
20230330_115931.082(0) handle_transceiver_update started, current rig state: PTT On, requested state: PTT Off, m_tx_when_ready: false, g_iptt=0
20230330_115931.084(0) handle_transceiver_update PTT Off Split On s.frequency:21074000 s.tx_frequency:21073500
20230330_115931.371(0) handle_transceiver_update started, current rig state: PTT Off, requested state: PTT Off, m_tx_when_ready: false, g_iptt=0
20230330_115931.373(0) handle_transceiver_update PTT Off Split On s.frequency:21074000 s.tx_frequency:21073500
20230330_115944.525(0) Decoder started SWL On, cycles: 1
20230330_115930 partial loss of data d
20230330_115930 -1 0.4 737 ~ EA8DIC IW9FRA JM68 ^
20230330_115930 -18 0.4 1046 ~ CQ GJ0KYZ IN89 ^
20230330_115930 -3 1.8 456 ~ CQ EA4ZI IM78
|
|
