Good evening. I did what I should never do and cleaned up and rearranged my shack. The good news, I can now see all my radios about eye height and reach all of them without much leaning or stretching.

Read my posts from several days ago about similar action when changing the TX offset and see whether you are having similar problems. Also how is your split handled, rig or "fake it"? Gene NG1H

Been mean to reply to this for a day or two. I am not sure if we are talking the same thing. I have JTAlert in the Settings Menu to alert me when an unworked DX station has appeared. I don't have

I meant to say 500Hz not kHz in my reply earlier (brain-keyboard error) -- The content of this email is confidential and intended for the recipient specified in message only. It is strictly

Two possibilities: 1) WSJT-x will shift your Tx frequency by 500 Hz (not KHz) in order to keep the Tx audio in the presumed middle of your T audio filters. Works as designed, don’t try to correct

This is by design, WSJT-X will shift your VFO frequency up/down in 500kHz steps and your transmit audio frequency to always stay within 1500-2000kHz in the sweet spot of most radio's

Wayne, are you sure the Tx frequency is shifting down by 500 kHz? A -500 Hz Tx VFO dial frequency shift, when your Tx offset is between 1000 Hz and 1499 Hz, is normal and correct

I know there’s probably a simple explanation for this, but WSJTX is dropping the frequency on the transmitter by 500 KHz every time it transmits a CQ. This means that I have to constantly correct

If the incorrect file name is "xxxxx.ADI.TXT​ then just delete the .TXT leaving the .ADI at the end and you will be fine. ​Regards, ​Steve - VE3USP

Bill, the Com40 is a com0com pair (com40 and com41). Com40 is for the WSJT-X and Com41 is for the Win4Icom Client at my home QTH. The Win4Icom Server of course is at the remote site connected via a

Hello Willie, Clarification: On the PC under Settings/Sound at the OUTPUT Master Volume bar, I have it set at 91, during transmission the horizontal indicating bar starts at the 91 reading and then

OM, do you intend that the icon of the document is the notepad one? Don't worry, it just indicates that you will open adi files with notepad by default. File is still ADI. Pietro I2OIM PS: sign your

Hi Gene, what is providing COM4 on your local machine? 73 Bill G4WJS.

Did you add a file type (.txt or something) to the end of the filename? You might have to enable ’see file types’ or right-click and show properties to determine if it’s a file type

OM, there is no such thing as a "Notepad document", notepad is a basic text editor. If MS Windows identifies the file as an ADI type file then there is nothing to fix. 73 Bill G4WJS.

I had been using WSJT-X FT8 v2.5.0-rc4 without a rig control error message. However, when I began using v2.5.0-rc5 or -rc6 this week, I would receive a Hamlib error: IO error message. This was when

I made the mistake of trying to correct a callsign in my adi log, and mistakenly saved the result as a Notepad document. The document still is identified in the "type" column as an "adi." Any way to

This regrettably late reply responds to comments by Allan ZS1LS in Digest #2090 on 25 August 2021, andby Bill G4WJS and Mike W9MDB in Digest #2075 on 20 August 2021. In our clubstation, we have now

To All, I have published another FT8 Transciever Project called Pocket_FT8 on github at https://github.com/chillmf/Pocket-FT8. This project uses a Teensy 3.6 to send and receive FT8 messages on 17

Kenwood TS-590sg, not using internal tuner. Only using the MFJ-998RT in the shack, 1500w autotuner. Hasan