Re: [wsjt-devel] Unwanted CQ in FT8
There are peoples "hunting" and other "working QSO's en masse". Dennis want to go to CQ just after QSO. FT8 do what he needs. He works like "QSO>CQ>QSO>CQ etc. Of course FT8 made it possible. I do not negate this kind of work. I don't ask to kick-out CQ from FT8. I ask to make another path to hunting without the possibility sending CQ during QSO (usually mistakenly). Dennis, believe me I want to send nothing instead of CQ during QSO with rare DX If there is nothing sent then DX think it is QSB and repeats the last transmission. When I send CQ then DX station think I don't copy him and answer to another station. If the DX is 7O/DL7ZM and You lost QSO with him, next 7O will be QRV in 10 years and on 50 MHz maybe in 20 years. Jeff, for me "hunting" means to work rary stations like this 7O. There was a proposal for me to do a custom installation. We have in Poland a Genius who did own version of such a program. It is The Robot Version of WSJT-X. I don't like such robots. 24/4 active and QRMing. Another Genius from Bulgaria did a multicanal version of WSJT-X. There is a mess when a station uses it. F/H or multicanal, which period to call him are questions on the cluster. Both periods in use, total mess. Only the WSJT-X Team should make changes to WSJT-X. Actually WSJT-X is oriented to do as many QSO's as possible. WSJT Team needs big traffic in FT8 channels. I think it was needed just after the first release of WSJt-X. Today WSJT-X is #1 Mode in the Amateur World. Maybe it is time to not press on Quantity rather on Quality of QSO's. Why is it that what I write now is pressing to make many QSO's on CQ? We start WSJT-X and this circle CQ is chosen. We decided to call a station with raport TX2. We checked TX2 and did QSO. After logging QSO TX2 is unchecked, now TX6 is checked (CQ). Again WSJT-X prompt to call CQ. Of course if we double-click a callsign we will send TX2 Anyway WSJT-X is ready to call CQ when you click Enable Tx (even mistakenly). For rary DX Hunters it is cumbersome, it is very easy to start unwanted CQ. Of course we can easy stop CQ, but if You are on 50 MHz and opening to a rare DX is 3-4 minutes, then one period lost is a big loss even causing loss of QSO. It is why I ask another path to do hunting without the possibility of mistakenly sending CQ during QSO. When will QSO end? WSJT-X told :after RR73 Conservative EME users say there must be more confirmations using 73. In reality they want the system RR73 73 73 mean 3 times 73. Rary DX has his rules and if You want to be logged You must follow his rules. And now the end: I know how WSJT-X actually works and how to set up WSJT-X. Citates from HELP aren't needed. 73 Henryk SP3E czw., 14 lip 2022 o 15:15 Jeff Stillinger via wsjt-devel < wsjt-devel@lists.sourceforge.net> napisał(a): > I think everyone here is slightly confused... > > Henryk, > > Two things need to be checked in WSJT-X settings.On the General Tab in > Settings, check the following two items: > > "Double Click on Call sets TX enable", and, "Disable Tx after sending 73" > > What these two setting do for you is after you send the RR73 sequence, TX > will be disabled. Puts you back into "hunting mode" automatically, > defaults to TX6 as a place holder.Then, when you see a callsign or CQ > in the band activity box you wish to work, double clicking on the callsign > will enable TX and transmit the response sequence to the station. > > What you are asking to do is already done. However, WSJT-X is open > source, if you want a custom installation and add a TX 7 box, you are free > to do so. > > > On 7/13/22 14:35, Henryk Majcher via wsjt-devel wrote: > > Hi Neil > > You completely didn't understand what I asked. > The frame "TX 7" should be empty. It is a stand by position. > No transmit, when it is checked. > Resume: "TX 7" is not a macro. > > Henryk SP3E > > śr., 13 lip 2022 o 14:28 Neil Zampella via wsjt-devel < > wsjt-devel@lists.sourceforge.net> napisał(a): > >> That can be done using the 'Free Text' area and macros from JT >> Alert. No need to add another standard message. As far as >> 'unwanted' CQs, uncheck the CALL 1ST checkbox. >> >> Neil, KN3ILZ >> >> On 7/12/2022 7:31 PM, Henryk Majcher wrote: >> > I propose a small change in WSJT-X. >> > Scenario: >> > The users of WSJT-X are >> > * CQ fans >> > * Hunters (Squares, DXCC, Zones) >> > Actually after QSO (even incomplete) the circle left of TX6 is checked >> > and WSJT-X is ready to send CQ. >> > It is super nice for CQ fans. >> > What WSJT-X offers for Hunters? Nothing >> > >> > I propose to put an additional frame "TX 7". >> > It will be named "Stand By". >> > If someone don't planning CQ, then if "TX 7" is checked, WSJT-X wait >> > ttil the Hunter chooses one of "TX 1", "TX 2" , "TX 3", "TX4". >> > This way unwanted CQ is impossible. >> > >> > If during QSO DX repeat report R-XX it is better not to transmit one >> > period and choose again "TX 4" and click Enable TX >> >
Re: [wsjt-devel] Unwanted CQ in FT8
I think everyone here is slightly confused... Henryk, Two things need to be checked in WSJT-X settings. On the General Tab in Settings, check the following two items: "Double Click on Call sets TX enable", and, "Disable Tx after sending 73" What these two setting do for you is after you send the RR73 sequence, TX will be disabled. Puts you back into "hunting mode" automatically, defaults to TX6 as a place holder. Then, when you see a callsign or CQ in the band activity box you wish to work, double clicking on the callsign will enable TX and transmit the response sequence to the station. What you are asking to do is already done. However, WSJT-X is open source, if you want a custom installation and add a TX 7 box, you are free to do so. On 7/13/22 14:35, Henryk Majcher via wsjt-devel wrote: Hi Neil You completely didn't understand what I asked. The frame "TX 7" should be empty. It is a stand by position. No transmit, when it is checked. Resume: "TX 7" is not a macro. Henryk SP3E śr., 13 lip 2022 o 14:28 Neil Zampella via wsjt-devel napisał(a): That can be done using the 'Free Text' area and macros from JT Alert. No need to add another standard message. As far as 'unwanted' CQs, uncheck the CALL 1ST checkbox. Neil, KN3ILZ On 7/12/2022 7:31 PM, Henryk Majcher wrote: > I propose a small change in WSJT-X. > Scenario: > The users of WSJT-X are > * CQ fans > * Hunters (Squares, DXCC, Zones) > Actually after QSO (even incomplete) the circle left of TX6 is checked > and WSJT-X is ready to send CQ. > It is super nice for CQ fans. > What WSJT-X offers for Hunters? Nothing > > I propose to put an additional frame "TX 7". > It will be named "Stand By". > If someone don't planning CQ, then if "TX 7" is checked, WSJT-X wait > ttil the Hunter chooses one of "TX 1", "TX 2" , "TX 3", "TX4". > This way unwanted CQ is impossible. > > If during QSO DX repeat report R-XX it is better not to transmit one > period and choose again "TX 4" and click Enable TX > as send UNWANTED CQ if unfortunately first click "Enable TX". > > To do fully automatic we need in frame CQ: > None > First > Max Dist > to add one more row > "Stand By". > > When this Stand By is checked by Hunter, after QSO WSJT-X will check > the circle near "TX 7". > > Unwanted CQ is now impossible. > > I lost a few new DXCC when in pile-up heart pulse was 200/min > and the unwanted CQ ruined QSO... > > 73 > Henryk SP3E > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- Jeff Stillinger - KB6IBB KB6IBB Laboratories, Wylie Tx http://kb6ibb-15.ham-radio-op.net/ ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Unwanted CQ in FT8
Henryk, It sounds as though you are mixing CQ Fans with Hunters, if I understand you correctly. If you are hunting, why would you quickly re-enable the ENABLE TX button after sending 73? Shouldn’t you wait until you receive RR73 or 73 from the other station? I don’t believe there is a need for a TX7 because WSJT-X does not automatically send the next CQ unless the operator has enabled it. Even if there was a TX 7 and it was blank, I would think that WSJT-X would enable transmit and not send anything, and only if the operator had quickly re-enabled ENABLE TX. Therefore, you would still not solve the problem you are describing. You would not be resending TX 4 or TX 5 to the other station. You would have your TX enabled but be sending nothing. However, if I have missed something in your description, a possible solution is to clear the TX 6 field yourself during the QSO and that will give you the blank field that you are suggesting. I personally would not want a blank TX 7 and WSJT-X defaulting to it after I send 73. This would require another click on my part to generate my next CQ. --Dennis NE6I From: Henryk Majcher via wsjt-devel Sent: Wednesday, July 13, 2022 12:35 PM To: WSJT software development Cc: Henryk Majcher Subject: Re: [wsjt-devel] Unwanted CQ in FT8 Hi Neil You completely didn't understand what I asked. The frame "TX 7" should be empty. It is a stand by position. No transmit, when it is checked. Resume: "TX 7" is not a macro. Henryk SP3E śr., 13 lip 2022 o 14:28 Neil Zampella via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net> > napisał(a): That can be done using the 'Free Text' area and macros from JT Alert. No need to add another standard message. As far as 'unwanted' CQs, uncheck the CALL 1ST checkbox. Neil, KN3ILZ On 7/12/2022 7:31 PM, Henryk Majcher wrote: > I propose a small change in WSJT-X. > Scenario: > The users of WSJT-X are > * CQ fans > * Hunters (Squares, DXCC, Zones) > Actually after QSO (even incomplete) the circle left of TX6 is checked > and WSJT-X is ready to send CQ. > It is super nice for CQ fans. > What WSJT-X offers for Hunters? Nothing > > I propose to put an additional frame "TX 7". > It will be named "Stand By". > If someone don't planning CQ, then if "TX 7" is checked, WSJT-X wait > ttil the Hunter chooses one of "TX 1", "TX 2" , "TX 3", "TX4". > This way unwanted CQ is impossible. > > If during QSO DX repeat report R-XX it is better not to transmit one > period and choose again "TX 4" and click Enable TX > as send UNWANTED CQ if unfortunately first click "Enable TX". > > To do fully automatic we need in frame CQ: > None > First > Max Dist > to add one more row > "Stand By". > > When this Stand By is checked by Hunter, after QSO WSJT-X will check > the circle near "TX 7". > > Unwanted CQ is now impossible. > > I lost a few new DXCC when in pile-up heart pulse was 200/min > and the unwanted CQ ruined QSO... > > 73 > Henryk SP3E > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Unwanted CQ in FT8
Hi Neil You completely didn't understand what I asked. The frame "TX 7" should be empty. It is a stand by position. No transmit, when it is checked. Resume: "TX 7" is not a macro. Henryk SP3E śr., 13 lip 2022 o 14:28 Neil Zampella via wsjt-devel < wsjt-devel@lists.sourceforge.net> napisał(a): > That can be done using the 'Free Text' area and macros from JT > Alert. No need to add another standard message. As far as > 'unwanted' CQs, uncheck the CALL 1ST checkbox. > > Neil, KN3ILZ > > On 7/12/2022 7:31 PM, Henryk Majcher wrote: > > I propose a small change in WSJT-X. > > Scenario: > > The users of WSJT-X are > > * CQ fans > > * Hunters (Squares, DXCC, Zones) > > Actually after QSO (even incomplete) the circle left of TX6 is checked > > and WSJT-X is ready to send CQ. > > It is super nice for CQ fans. > > What WSJT-X offers for Hunters? Nothing > > > > I propose to put an additional frame "TX 7". > > It will be named "Stand By". > > If someone don't planning CQ, then if "TX 7" is checked, WSJT-X wait > > ttil the Hunter chooses one of "TX 1", "TX 2" , "TX 3", "TX4". > > This way unwanted CQ is impossible. > > > > If during QSO DX repeat report R-XX it is better not to transmit one > > period and choose again "TX 4" and click Enable TX > > as send UNWANTED CQ if unfortunately first click "Enable TX". > > > > To do fully automatic we need in frame CQ: > > None > > First > > Max Dist > > to add one more row > > "Stand By". > > > > When this Stand By is checked by Hunter, after QSO WSJT-X will check > > the circle near "TX 7". > > > > Unwanted CQ is now impossible. > > > > I lost a few new DXCC when in pile-up heart pulse was 200/min > > and the unwanted CQ ruined QSO... > > > > 73 > > Henryk SP3E > > > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Unwanted CQ in FT8
That can be done using the 'Free Text' area and macros from JT Alert. No need to add another standard message. As far as 'unwanted' CQs, uncheck the CALL 1ST checkbox. Neil, KN3ILZ On 7/12/2022 7:31 PM, Henryk Majcher wrote: I propose a small change in WSJT-X. Scenario: The users of WSJT-X are * CQ fans * Hunters (Squares, DXCC, Zones) Actually after QSO (even incomplete) the circle left of TX6 is checked and WSJT-X is ready to send CQ. It is super nice for CQ fans. What WSJT-X offers for Hunters? Nothing I propose to put an additional frame "TX 7". It will be named "Stand By". If someone don't planning CQ, then if "TX 7" is checked, WSJT-X wait ttil the Hunter chooses one of "TX 1", "TX 2" , "TX 3", "TX4". This way unwanted CQ is impossible. If during QSO DX repeat report R-XX it is better not to transmit one period and choose again "TX 4" and click Enable TX as send UNWANTED CQ if unfortunately first click "Enable TX". To do fully automatic we need in frame CQ: None First Max Dist to add one more row "Stand By". When this Stand By is checked by Hunter, after QSO WSJT-X will check the circle near "TX 7". Unwanted CQ is now impossible. I lost a few new DXCC when in pile-up heart pulse was 200/min and the unwanted CQ ruined QSO... 73 Henryk SP3E ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
