Well Jim, that lousy choke has worked wonders on multiple 

occasions and.  Won't argue too much about the ferrites, 

sometimes just a simple snap on worked, sometimes

you need multiple ferrites with multiple loops through each one.

I did forget to mention putting ferrites on speaker leads  

that go to the PC as well as on the power lines for the 

speakers. and monitor(s)

I always try the simple/easy stuff first before expending 

any more efforts.

To each their own. 

73,

Sam W2JDB

-----Original Message-----
From: Jim Brown <k9yc@...>
To: main@WSJTX.groups.io
Sent: Wed, Oct 6, 2021 12:16 am
Subject: Re: [WSJTX] #Cat_RigControl #IssueReport #protocol #stopped_working #Yaesu

On 10/5/2021 6:04 PM, John wrote:

> This is called a counterpoise.

While a counterpoise is an important part of most end-fed antennas, it
is NOT a substitute for proper grounding and bonding. It is something
that can be done IN ADDITION TO proper grounding bonding.

On 10/5/2021 7:09 PM, Sam Birnbaum via groups.io wrote:

> You might also want to connect (if possible) the chassis of the PC, ==
> FT817 and Amp to a single buss bar.

This is part of proper grounding and bonding, and it's the only part of
Sam's advice with which I agree. A coil of coax is a lousy choke, and
clamp-on ferrites for HF must be Fair-Rite #31, with multiple turns
wound through them to do much useful.

73, Jim K9YC

Thanks Doug
I copied (or perhaps moved and renamed by mistake) the rumlog adi file to the same directory as the original wsjtx_log.adi
and renamed the old one.  The old one had all the qsos from this year only.  I thought the rumlog would be complete...now I see ZERO worked-before when I rescan ADIF log.  However in Band Activity, I still see blue highlighting on new calls.  How can that be?
Should I just start over?  did I lose my >10 years of logging?  

Hi  Cliff,

That is normal operation when using split = rig. It is shifting the frequency so 

that your TX audio is in the middle of the band pass.  

FYI, you do not have to press the "VFOA=VFOB" The program will do that for you.

73,  

Sam W2JDB

-----Original Message-----
From: Cliff Fox (KU4GW) <cliffku4gw@...>
To: main@WSJTX.groups.io
Sent: Tue, Oct 5, 2021 6:26 pm
Subject: [WSJTX] VFO B Shifts From 7074 to 7073 On Transmit When Using Split On Yaesu FT-991A? #Cat_RigControl

I'm having an issue and I don't know why it's happening when operating on FT8 when I use the Split setting under the Settings, Radio tab. I was operating on 40 meters and set VFO A to 7074 kHz in DATA-U mode with AGC off and then pressed VFO A=VFO B  to copy the same settings to VFO B and if I'm transmitting as low as 400-800 Hz audio frequency when the FT-991A transmits it's shifting VFO B to 7073 for some reason. If I were transmitting at 1000 or above I would expect a shift up. I turned split off and chose "Fake It" in the WSJT-X settings because of it doing this. It had not been doing this until this past week it started happening, I'm thinking possibly due to operator error. Can anyone tell me what could be causing the shift on VFO B from 7074 to 7073 when I transmit and what would keep it from doing that when using the split VFO setting? Thanks in advance from a real greenhorn on a new to me mode.

Very 73 de Cliff, KU4GW

Read up on Menu 031 for the Band/Stack option and elsewhere in the manual about band stack.

I think you probably want the Band option.

You should be able to set up the band and press the band button to put it in the band stack.

WSJT-X should be sending a BS band stack command so should be remembering the antenna if it's put in the band stack correctly.

Mike W9MDB

On Tuesday, October 5, 2021, 07:59:56 PM CDT, John <ve3kkqve3kkq@...> wrote:

I have problems with WSJT-X and the FTdx-3000 rig in that my antennas (two) don't get selected as the bands change.

Someone involved with HamLab was helping by sending me a file to include in WSJT-X that would record what was going on. I sent these files as requested several times and suddenly the person "helping" stopped communicating.

So, I now use the FTdx-5000 as my rig as I did before I reported my problem and have no issues.

Hope you get better support than I did.

John

VE7KKQ

On Tue, Oct 5, 2021 at 4:06 PM <regiogringo@...> wrote:

[Edited Message Follows]

Bill,

I agree that it's an issue of Rig control...

There are three tabs that need to be setup, "GENERAL," where call letters and grid square are entered, then the "RIG" section, which should contain the model number of the rig you intend to use, then there is the "AUDIO" tab section, which contains various selections.  If I am conflating Rig Control with Audio, it's because WSJT-X labels the third tab in setup as "AUDIO.  I don't know why they call the third tab "Audio," but that's what WSJT-X calls it, and that's why I refer to it as such, so the reader will know which tab I'm referring to.

So, when exclusively using WSJT-X as rig control, I enter my Rig's model number, under "RIG," and then I enter any of the selections offered under the "AUDIO" tab, which then yields the HAMLIB error message.

The model number for my rig is elementary, a Yaesu FT-991, and that's what I have entered.  I've also tried each and every selection under the "AUDIO" tab,  and I get the HAMLIB error message ("AUDIO" is their term for the tab, not mine). 

When I setup WSJT-X using FLRiG as rig control , the Yaesu (Silicon Labs) USB drivers show up under the tab entitled "AUDIO," but I have to select FLRIG under the tab entitled "RIG," and not the actual Rig's model number.  I also have to fire FLRIG first, before I fire WSJT-X, in order for WSJT-X to work. But, under this scenario, I do NOT get a HAMLIB error message, and WSJT-X works perfectly. 

So, yes, it's a matter of Rig Control, evidenced by my having to select FLRIG first as RIG Control under the tab entitled "RIG," rather than specifying my rig's actual model number under the "RIG" tab. When I select FLRIG as my rig model number under the WSJT-X "RIG" tab, and the Yaesu (Silicon Labs) USB drivers show up to be selected under the "AUDIO" tab, that suggests to me that there may be a USB driver issue as well, since the Yaesu (Silicon Labs) USB drivers do not show up for selection if I setup things solely using WSJT-X as rig control.

I can only report what I'm experiencing, and I have no comprehension as to why I'm getting these HAMLIB error messages, or why WSJT-X won't work when I designate my rig model number for rig control, and select what WSJT-X provides under their "AUDIO" tab to select from. 

Thank you!

Randy
KG0BA
73

[Edited Message Follows]

Bill,

I agree that it's an issue of Rig control...

There are three tabs that need to be setup, "GENERAL," where call letters and grid square are entered, then the "RIG" section, which should contain the model number of the rig you intend to use, then there is the "AUDIO" tab section, which contains various selections.  If I am conflating Rig Control with Audio, it's because WSJT-X labels the third tab in setup as "AUDIO.  I don't know why they call the third tab "Audio," but that's what WSJT-X calls it, and that's why I refer to it as such, so the reader will know which tab I'm referring to.

So, when exclusively using WSJT-X as rig control, I enter my Rig's model number, under "RIG," and then I enter any of the selections offered under the "AUDIO" tab, which then yields the HAMLIB error message.

The model number for my rig is elementary, a Yaesu FT-991, and that's what I have entered.  I've also tried each and every selection under the "AUDIO" tab,  and I get the HAMLIB error message ("AUDIO" is their term for the tab, not mine). 

When I setup WSJT-X using FLRiG as rig control , the Yaesu (Silicon Labs) USB drivers show up under the tab entitled "AUDIO," but I have to select FLRIG under the tab entitled "RIG," and not the actual Rig's model number.  I also have to fire FLRIG first, before I fire WSJT-X, in order for WSJT-X to work. But, under this scenario, I do NOT get a HAMLIB error message, and WSJT-X works perfectly. 

So, yes, it's a matter of Rig Control, evidenced by my having to select FLRIG first as RIG Control under the tab entitled "RIG," rather than specifying my rig's actual model number under the "RIG" tab. When I select FLRIG as my rig model number under the WSJT-X "RIG" tab, and the Yaesu (Silicon Labs) USB drivers show up to be selected under the "AUDIO" tab, that suggests to me that there may be a USB driver issue as well, since the Yaesu (Silicon Labs) USB drivers do not show up for selection if I setup things solely using WSJT-X as rig control.

I can only report what I'm experiencing, and I have no comprehension as to why I'm getting these HAMLIB error messages, or why WSJT-X won't work when I designate my rig model number for rig control, and select what WSJT-X provides under their "AUDIO" tab to select from. 

Thank you!

Randy
KG0BA
73