Re: [wsjt-devel] No 73 allowed after RR73?

Hi Andy and all, The protocol is flexible on that issue. The original weak signal QSO do contain a “RRR” that is “confirmed” by a “73” to keep both sizes of the QSO happy. The “RR73” is really intended for “strong signal” QSO’s and then the “73” is not needed to keep the QSO time short.

Re: [wsjt-devel] No 73 allowed after RR73?

If you don't print the RR73,  then repeat your QSL/exchange message.  If you never receive the RR73, then don't log the QSO.   How many times you repeat your QSL/exchange message is a judgment call.  It's a tradeoff between completing the QSO and moving on to the next one.73,Ed W0YK

Re: [wsjt-devel] No 73 allowed after RR73?

RR73 completes the QSO.   Both QSO partners have sent calls, exchanges and QSLs.  Am additional 73 message is a waste of time.73,Ed W0YK Original message From: sdegroff via wsjt-devel Date: 10/21/23 13:18 (GMT-08:00) To: WSJT software development Cc: sdegroff Subject: Re:

Re: [wsjt-devel] No 73 allowed after RR73?

+173,Ed W0YK Original message From: Ron WV4P via wsjt-devel Date: 10/21/23 13:02 (GMT-08:00) To: WSJT software development Cc: Ron WV4P Subject: Re: [wsjt-devel] No 73 allowed after RR73? I wish this was THE way, the useless final 73 should have never existed and is the

Re: [wsjt-devel] No 73 allowed after RR73?

You CQ DX message should be in TX6. 73 -Jim NU0C On Sat, 21 Oct 2023 19:33:18 + Andy Durbin via wsjt-devel wrote: > After a review of ALL.TXT I no longer think this was related to prior use of > F/H mode. I had set TX5 to a "CQ DX message" and that was auto sequenced > after RR73 was

Re: [wsjt-devel] No 73 allowed after RR73?

Fox/Hound For dxpeditions...see the Help Mike W9MDB On Saturday, October 21, 2023 at 11:24:46 PM CDT, sdegroff via wsjt-devel wrote: What is F/H mode ? Sent from my Verizon, Samsung Galaxy smartphone Original message From: sdegroff via wsjt-devel Date: 10/21/23

Re: [wsjt-devel] No 73 allowed after RR73?

What is F/H mode ?Sent from my Verizon, Samsung Galaxy smartphone Original message From: sdegroff via wsjt-devel Date: 10/21/23 11:22 PM (GMT-05:00) To: WSJT software development Cc: sdegroff Subject: Re: [wsjt-devel] No 73 allowed after RR73? Huh?Sent from my Verizon,

Re: [wsjt-devel] No 73 allowed after RR73?

Huh?Sent from my Verizon, Samsung Galaxy smartphone Original message From: Andy Durbin via wsjt-devel Date: 10/21/23 7:06 PM (GMT-05:00) To: wsjt-devel@lists.sourceforge.net Cc: Andy Durbin Subject: Re: [wsjt-devel] No 73 allowed after RR73? After a review of ALL.TXT I no

Re: [wsjt-devel] No 73 allowed after RR73?

After a review of ALL.TXT I no longer think this was related to prior use of F/H mode. I had set TX5 to a "CQ DX message" and that was auto sequenced after RR73 was received. I'll need to be careful to ensure TX5 is set correctly when in QSO. 73, Andy, k3wyc

Re: [wsjt-devel] No 73 allowed after RR73?

> On Oct 21, 2023, at 16:04, Andrew Neumeier via wsjt-devel > wrote: > > If I am working a very weak station, and that station chooses to use RR73 > instead of 73, there > is a good chance that I have not received it, especially if I am waiting for > a qsb peak on the signal. And that’s

Re: [wsjt-devel] No 73 allowed after RR73?

In some cases the use of RR73 is problematic.  I operate FT8 almost exclusively on 2 meters, weak signal.  If I am working a very weak station, and that station chooses to use RR73 instead of 73, thereis a good chance that I have not received it, especially if I am waiting for a qsb peak on

Re: [wsjt-devel] No 73 allowed after RR73?

FWIW ... if you received an RR73 .. there is no need to reply. The station is saying that RR I got your last, and 'over and out' ... The other party is not waiting for your reply, they're on to another contact. Neil, KN3ILZ On 10/21/2023 1:14 PM, Andy Durbin wrote: WSJT-X ver 2.6.1, Win

Re: [wsjt-devel] No 73 allowed after RR73?

I don't know what F/H is,  but i have seen wsjtx hang and not complete the qso after RR73.Stan DeGroff W8SRDSent from my Verizon, Samsung Galaxy smartphone Original message From: Andy Durbin via wsjt-devel Date: 10/21/23 3:49 PM (GMT-05:00) To:

Re: [wsjt-devel] No 73 allowed after RR73?

I wish this was THE way, the useless final 73 should have never existed and is the bain of the mode. Ron, WV4P On Sat, Oct 21, 2023 at 2:55 PM Andy Durbin via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > WSJT-X ver 2.6.1, Win 8.1. > > I have observed several times that I could not

[wsjt-devel] No 73 allowed after RR73?

WSJT-X ver 2.6.1, Win 8.1. I have observed several times that I could not complete a QSO by sending 73 after I had received an RR73. This is expected operation with F/H active but not when F/H is not active. I suspect that something is latched in software if F/H mode has been used but is

Re: [wsjt-devel] Extra characters in ALL.TXT for F/H

AP Decode see section 12.1 of User Guide wsjt.sourceforge.io

Re: [wsjt-devel] Extra characters in ALL.TXT for F/H

Glenn Please read section 12 of the online documentation. It explains what you want to know. Dennis W1UE On Sat, Oct 21, 2023 at 8:27 AM Glenn Williams via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi, > The following line of text is found once in my huge ALL.TXT file. Note >

Re: [wsjt-devel] Extra characters in ALL.TXT for F/H

Search the Help file for "a4" or "a3". Mike W9MDB On Saturday, October 21, 2023 at 07:26:27 AM CDT, Glenn Williams via wsjt-devel wrote: Hi, The following line of text is found once in my huge ALL.TXT file.  Note the "a4" far to the right. V2.6.1  Windows 10 USB-USB to TS590SG

[wsjt-devel] Extra characters in ALL.TXT for F/H

Hi, The following line of text is found once in my huge ALL.TXT file. Note the "a4" far to the right. V2.6.1 Windows 10 USB-USB to TS590SG DATA port, Special Op F/H, Split->Rig "231005_00530024.911 Rx FT8-20 0.0 720 AF8C RR73; NR4N -14 a4" The following 2 lines of