To support this, I would add "It might be your log, but it is not exclusively your QSO." w8lvn -- --w8lvn--

It is indeed your log and you can enter QSOs into it on whatever basis you choose, but by not logging a QSO when you send your RR73 you're potentially not logging perfectly valid QSOs. The final 73

Hi Chris, this is expected behaviour and was changed in v2.4.0-rc4. It creates ambiguity if an amended signal report is sent in repeats as you cannot be certain which signal report your QSO partner

You’re not alone... My new computer (son designed and built this gaming computer) also mutes the sound every once in a while. Sometimes a couple times a day, then it will stay unmuted for days???

I was operating 30 metres FT8 this morning and believe that a behavior has changed in sending the signal reports. When a station didn't copy the TX2 sent report and responded again with TX1, each time

Agreed. Same thoughts. Larry W0OGH

The following definition of a QSO is approved by the IARU (International Amateur Radio Union) Region 1, here extracted from the last version of The HF Managers’ Handbook: 2.1.1 QSO-DEFINITION

Hi Roy, Thanks for responding. Is this a suggestion in order to "clean up" and reduce the miscellaneious signals? Or some other reason? Thx, Jeff

HI Alan, Thanks for responding. I did some testing with an attenuator in line, but no luck yet. Have to do some more testing with it and some other's suggestions as well. Thx, Jeff

It appears that Split Operation using Rig mode is not functioning correctly in both versions 2.3.1 and 2.4.0-rc4. Running Split | Rig with my Yaesu FT-817 when switching to transmit the FT-817

After further investigation, it seems that certain NTP servers cause Apple's "timed" to get confused. However the Apple server time.apple.com works fine. So if you see a time offset with macOS Big

Just because you can, build yourself a simple 20m low-pass filter for the SI output. You can find the required component values by looking at the assembly manual for the QRP-Labs low-pass filter kits.

That's well and good until you are on the other side ... Say you are working a rare DX (or rare state for WAS, etc.), he sends you RR73 and someone else (who also needs him) calls right on top of

If you don't receive '73' in response to your 'RR73' message, do you re-send 'RR73 '? Or, do you just silently not log the QSO? 73, Ed W0YK

Just for curiosity. If you are the one to receive RR73 do you consider it as a 73? 73, Reino OH3mA Lähettäjä: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Puolesta Charlie

Try using manufacture’s drivers rather than MS provided generic drivers. My tech guy (#1 grandson, IT trained) says problems of this type are often due to MS making changes and breaking things that

I send RR73. When I receive a 73 then the QSO is complete. If I don't receive a 73 then I consider the contact incomplete. I don't log a QSO until I receive a 73 from the other station. My log - my

?? I was taught as a Novice 33 years ago that Roger meant the report was received, 73 meant good wishes. RR73 means the report was received and best wishes. Pretty simple to me. 73 de NØIGU Jon

A write up of my PIC + DDS Beacon source for FST4 / FST4W http://g4jnt.com/FST4_Beacon_Source.pdf Andy G4JNT

It's even simpler than that. A QSO is complete if both stations copy R from the other. If the other station sends R-10 again, it means he didn't copy your RRR or RR73. If he calls CQ (or calls another