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

[Feature Request]: Tune function for antenna tuners #778

Open
deejdeej opened this issue Aug 17, 2024 · 6 comments · May be fixed by #828
Open

[Feature Request]: Tune function for antenna tuners #778

deejdeej opened this issue Aug 17, 2024 · 6 comments · May be fixed by #828

Comments

@deejdeej
Copy link
Collaborator

deejdeej commented Aug 17, 2024

Problem Description

Add a second tune button, or make the existing tune button user configurable to send out a solid tone that can be used to tune an antenna tuner. First press activates transmits the tune tone, and it stays transmitting until pressed a second time to stop the tune transmission. This allows plenty of time for an external antenna tuner to process and select the best SWR.

Proposed Solution

The current tune button does not stay transmitting long enough for some antenna tuners to work. A solid tune tone seems to work better on some antenna tuners for matching SWR versus sending a data packet.

Alternatives Considered

n/a

Additional Information

I am thinking of the use case of an external antenna tuner. For example, I have a Hardrock-50 external ATU/amp attached to one of my radios, and it requires the radio to be transmitting a signal then press a button on the ATU to start the tuning process. When using WSJT-X, I press the TUNE button which transmits a tone (not a data packet) which allows me to press the button on the ATU to start the tuning process. Once the ATU is finished, I then press the TUNE button in WSJT-X a second time to stop the transmission.

@DJ2LS
Copy link
Owner

DJ2LS commented Sep 30, 2024

I'm not that happy with the "start stop" thing as it feels, it might lead to problems. Case: Tune is pressed, then we have high interference on computer because of tuning process, which maybe leads to a not accessible server.

What about pressing "tune" with an adjustable timer, so Tune stays in tune for 5, 10, 15, 20 seconds, then tune will be released automatically.

@deejdeej
Copy link
Collaborator Author

What about pressing once to start the tune, pressing a second time to stop the tune, and have a maximum time that the tune function can stay active before shutting off automatically? This would emulate exactly the way that WSJT-X does it which has worked well for a number of years.

@DJ2LS
Copy link
Owner

DJ2LS commented Sep 30, 2024

ready for testing with latest develop, see Tune section

@DJ2LS DJ2LS linked a pull request Sep 30, 2024 that will close this issue
@deejdeej
Copy link
Collaborator Author

The Transmit Sine Start/Stop and default of 30 seconds timeout works great!
I'm not sure the signal being sent out is quite right, though.
If I set my rig to 100 watts, and click the test-frame transmit for 5 seconds, I see 75 watts out on my meter which seems correct.
If I click the Transmit-Sine button, I only see 30 watts out. I would expect to see 100 watts or close to it, unless I am misunderstanding something.

@DJ2LS
Copy link
Owner

DJ2LS commented Oct 1, 2024

I have to check, I think we should combine the sine with the volume settings. So they are sticking together and maybe adjusting default settings.

@DJ2LS
Copy link
Owner

DJ2LS commented Oct 1, 2024

sending sine now respects the audio level, I also increased volume per default ( +3dB ). So I think as a first start it's working and we can close this one. Audio level normalization is a bigger topic, as we also have to check the data modes. But for doing this I need much more time.

In other words: I like to close this one, if you are fine with this, @deejdeej

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In review
Development

Successfully merging a pull request may close this issue.

2 participants