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

2023-10-24 Thread AOL Mail. via wsjt-devel
-devel Sent: Monday, October 23, 2023 12:50 AM To: wsjt-devel@lists.sourceforge.net Cc: Sam W2JDB Subject: Re: [wsjt-devel] No 73 allowed after RR73?   >From the WSJT-X User guide:     Section 7.1 : Standard messages - " The RR73 message should be used only if you are reasonably c

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

2023-10-22 Thread Grant via wsjt-devel
should be considered. Regards, Grant VK5GR From: Sam W2JDB via wsjt-devel Sent: Monday, October 23, 2023 12:50 AM To: wsjt-devel@lists.sourceforge.net Cc: Sam W2JDB Subject: Re: [wsjt-devel] No 73 allowed after RR73? >From the WSJT-X User guide: Section 7.1 : Stand

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

2023-10-22 Thread Sam W2JDB via wsjt-devel
me. 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: [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.

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

2023-10-22 Thread Jim Shorney via wsjt-devel
sin Sähköpostiista > > Lähettäjä: Reino Talarmo via wsjt-devel > Lähetetty: sunnuntai 22. lokakuuta 2023 8.49 > Vastaanottaja: 'WSJT software development' > Kopio: Reino Talarmo > Aihe: Re: [wsjt-devel] No 73 allowed after RR73? > > Hi Andy and all, > The protocol is flexible o

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

2023-10-22 Thread Black Michael via wsjt-devel
@lists.sourceforge.net Cc: Andy Durbin Subject: [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

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

2023-10-22 Thread Andrew Neumeier via wsjt-devel
: Andrew Neumeier Subject: 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, there is a good chance that I

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

2023-10-22 Thread sdegroff via wsjt-devel
ThxSent from my Verizon, Samsung Galaxy smartphone Original message From: Black Michael via wsjt-devel Date: 10/22/23 12:28 AM (GMT-05:00) To: sdegroff via wsjt-devel Cc: Black Michael Subject: Re: [wsjt-devel] No 73 allowed after RR73? Fox/HoundFor dxpeditions...see

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

2023-10-22 Thread sdegroff via wsjt-devel
ThxSent from my Verizon, Samsung Galaxy smartphone Original message From: Hasan N0AN via wsjt-devel Date: 10/22/23 6:49 AM (GMT-05:00) To: WSJT software development Cc: Hasan N0AN Subject: Re: [wsjt-devel] No 73 allowed after RR73? Fox/Hound modeHasanOn Sat, Oct 21, 2023

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

2023-10-22 Thread Hasan N0AN via wsjt-devel
sjt-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, Samsung Galaxy smartphone > > > Original message

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

2023-10-22 Thread OG55W via wsjt-devel
1,8 – 70 MHz Lähetetty Windowsin Sähköpostiista Lähettäjä: Reino Talarmo via wsjt-devel Lähetetty: sunnuntai 22. lokakuuta 2023 12.56 Vastaanottaja: 'WSJT software development' Kopio: Reino Talarmo Aihe: Re: [wsjt-devel] No 73 allowed after RR73? Keijo, which bands you have used? Perhaps HF

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

2023-10-22 Thread James Shaver (N2ADV) 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 bain of the mode.  Ron, WV4P On Sat, Oct 21, 2023 at 2:55 PM Andy Durbin via wsjt

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

2023-10-22 Thread Reino Talarmo via wsjt-devel
-devel <mailto:wsjt-devel@lists.sourceforge.net> Lähetetty: sunnuntai 22. lokakuuta 2023 8.49 Vastaanottaja: 'WSJT software development' <mailto:wsjt-devel@lists.sourceforge.net> Kopio: Reino Talarmo <mailto:reino.tala...@kolumbus.fi> Aihe: Re: [wsjt-devel] No 73 allowed

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

2023-10-22 Thread OG55W via wsjt-devel
software development' Kopio: Reino Talarmo Aihe: 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

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

2023-10-21 Thread Reino Talarmo via wsjt-devel
, Reino OH3mA From: Andrew Neumeier via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Sunday, October 22, 2023 1:05 AM To: Neil Zampella via wsjt-devel Cc: Andrew Neumeier Subject: Re: [wsjt-devel] No 73 allowed after RR73? In some cases the use of RR73 is problematic. I

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

2023-10-21 Thread Ed W0YK via wsjt-devel
Original message From: Andrew Neumeier via wsjt-devel Date: 10/21/23 15:08 (GMT-08:00) To: Neil Zampella via wsjt-devel Cc: Andrew Neumeier Subject: Re: [wsjt-devel] No 73 allowed after RR73? In some cases the use of RR73 is problematic.  I operate FT8 almost exclusively on 2

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

2023-10-21 Thread Ed W0YK via wsjt-devel
: [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

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

2023-10-21 Thread Ed W0YK via wsjt-devel
+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

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

2023-10-21 Thread Jim Shorney via wsjt-devel
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?

2023-10-21 Thread Black Michael via wsjt-devel
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, Samsung Galaxy smartphone Original message From: Andy Durbin via wsjt-devel Date: 10/21/23 7:06 PM (GMT-05:00) To: wsjt-devel

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

2023-10-21 Thread sdegroff via wsjt-devel
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?

2023-10-21 Thread sdegroff via wsjt-devel
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

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

2023-10-21 Thread Andy Durbin via wsjt-devel
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?

2023-10-21 Thread Gary McDuffie via wsjt-devel
> 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?

2023-10-21 Thread Andrew Neumeier via wsjt-devel
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?

2023-10-21 Thread Neil Zampella via wsjt-devel
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?

2023-10-21 Thread sdegroff via wsjt-devel
@lists.sourceforge.net Cc: Andy Durbin Subject: [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

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

2023-10-21 Thread Ron WV4P via wsjt-devel
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?

2023-10-21 Thread Andy Durbin via wsjt-devel
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