Hi Joseph, The updated ARRL rules are clear: HCAT.2.1. Use of spotting assistance is permitted. Exception: spotting information obtained from any source outside the station circle via a closed or

Greetings, I just upgraded to v2.5.4. I am using Windows 10. My logging program is Logger32 and I use ADIF broadcast to log my contacts. Previously this worked fine, but now I get this error when

Yes, you were.  But the specific rules for a contest supersede the general rules.   The new rules replace those old general rules.  Again, from the RTTY RU rules page: Contest rules are now

Larry, Concerning prohibited actions, I was referencing the "General Rules for ARRL Contests Below 30 MHz", not the RTTY RU Rules.

Everyone: 1. Apologies for the poor formatting of my message. I took a lot of time to format the message so that it was readable, but the system dramatically changed it. 2. Thanks for the

Hi Joseph, You are interpreting that backward.  It means that the use of FT8, as it is a multi-channel decoder, is prohibited in unassisted categories. From the RTTY RU Rules: * 3. Categories

What computer language -- not OS. C, C++ , C#, Pascal, VB? Mike W9MDB

Sorry, I should have said, Windows.

Tony & Larry, After much weeping and gnashing of teeth, yes, indeed. If you are running WSJT-X on FT-4 or 8 for RTTY RU you are by default operating and classified as SOU - Single Operator Unlimited.

Pietro, thx for reply. Yes, Log4OM always set to OmniRig. As I understand it, OmniRig is what allows multiple pgms to "share" one Port, which is exactly my setup. That's what I meant by "sharing

Michael Thanks for suggestions, will give them a try. My temporary workaround for FT8 only: - Uninstall Omnirig - Change wsjt Radio settings back to 7610 - Not use any "Rig" connects to Log4OM to

Some more information. After an abnormal termination of WSJT-X, N1MM was restarted. Then WSJT-X was restarted from pulldown. There was some message about a lock file that needed to be cleared and if I

Hi, if you can control the rig as you described originally it seems like you have no problem with your Hamlib. Hamlib is used for controlling the rig. If you don't see a signal coming into WSJT-X you

Paul, I'm using wsjt-x ànd Log4OM together, both using omnirig as interface. This is why omnirig born. I'm not at PC now, but I'll send here the setup as soon as I was back to the radio. Pietro

You can run Log4OM and WSJT-X and JTDX and FLDigi all simultaneously using FLRig. Log4OM will use the Hamlib interface to FLRig. Can also do it using rigctld but FLRig gives a nice user interface for

Hi Pietro, I wasn't aware of the inability to share a com port, Thx. Would the following scenario work to allow the two programs to share the same USB cable AND the same instance of OmniRig? 1.

Thank you for your response. I don't have any of the choices you mention. I don't think I have the latest hamlib version. I've been a little confused on which to chose. Intel 64bit processor and

You don't say what language -- just doing a search comes up with a couple of examples. Python https://github.com/rstagers/WSJT-X Node-Red https://github.com/rstagers/WSJT-X Format is in

I participate in the 'Worked all Britain' (WAB) Award Schemes and have developed a WAB dedicated Logbook using Visual Fox Pro (VFP) which displays various details of squares worked etc for each award.

Al - one thing that looks odd in your photo is the fact that nothing is seen below 1000 Hz, not even noise. It might help to know what frequency the receiver was tuned to. Or, did you have a narrow