Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FTDX3000 Antenna not changing #756

Closed
mdblack98 opened this issue Aug 4, 2021 · 1 comment
Closed

FTDX3000 Antenna not changing #756

mdblack98 opened this issue Aug 4, 2021 · 1 comment
Labels
bug JTDX Bugs affecting JTDX operations piWebCat RigPi Issues affecting RigPi operations WSJTX Bugs affecting WSTJ-X operations

Comments

@mdblack98
Copy link
Contributor

Hello Bill,

I don't know if you are the person to inform about this, but here it is.

I've been using WSJT-X plus JTAlert quite happily for some time now.

I have two antennas, a 43ft non resonant vertical with 30 burred radials of varying length and a EFHW approx 130 ft long chucked up into a tree.

Lately I noticed that as I change bands with WSJT-X that the antennas were not changing as set up, Menu item 31 set to BAND.

I tried HRD, all is well, N1MM+ again all is well and I tried Win4YaesuSuite and all is well again, ants change as band changes.

I concluded to great relief that my rig was not in need of surgery.

So I remembered some time back that the FTdx-3000 was not a rig choice and that we 3k owners needed to use the FTdx5000 as our rig, so I tried that selection, now the antennas change as the band is changed.

I'm not saying the rig file is broken as I haven't seen anyone else bringing this to light on the Groups.io site.

Perhaps I have some corrupted data somewhere?

What are your thoughts?

Thanks es 73,
John
VE7KKQ

@mdblack98 mdblack98 added bug WSJTX Bugs affecting WSTJ-X operations RigPi Issues affecting RigPi operations JTDX Bugs affecting JTDX operations piWebCat labels Aug 4, 2021
@mdblack98 mdblack98 added this to the 4.3 milestone Aug 4, 2021
@mdblack98
Copy link
Contributor Author

The command sequence below was the only one that worked properly. You have to move both K4 VFOs to the same band and mode first, before you invoke split mode (otherwise you get "ER59 Cross-mode split not allowed in DATA modes").

rigctl -m 2047 -r COM6 -s 38400 -Y -vvvvv -Z V VFOA F 14074000 M PKTUSB 2800 S 0 VFOB K 14073500 PKTUSB 2800 S 1 VFOB

Note...need to test separating the VS1;BSn;VS0; command string to see if some delay between BSn and VS0 fixes this. Might just be too fast.

mdblack98 added a commit that referenced this issue Aug 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug JTDX Bugs affecting JTDX operations piWebCat RigPi Issues affecting RigPi operations WSJTX Bugs affecting WSTJ-X operations
Projects
None yet
Development

No branches or pull requests

1 participant