toggle quoted message
Show quoted text
Is Menu 030 the same on both rigs? Looks like they should behave the same.
You can test this yourself -- adjust com port and baud rate to suit. See if the antenna selection follows the band change.
rigctl -m 1037 -r /dev/ttyS0 -s 9600
Rig command: w BSX;
Where the X is the band
Hopefully there's no error shown (like ?) but you will see a timeout occur as there should be no response to this command.
On Wednesday, October 6, 2021, 12:20:33 AM CDT, John <ve3kkqve3kkq@...> wrote:
For roughly the last year I have been only on FT8. It has only been in the last few months that I put up an end fed half wave, that is when the antenna selection problem started.
So I don't see how Band Stacking has much to do with it as I said, I have only been running FT8, nothing else.
If it were band stacking, then why does the FTdx-5000 selection work yet the FTdx-3000 not, doesn't the FTdx-5000 have Band Stacking?
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.
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.
[Edited Message Follows]
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.