-
Notifications
You must be signed in to change notification settings - Fork 24
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
CW Macros might not working on CW for contests fields on v0.40. #517
Comments
I think it should be EXCHSTR, give that a shot.
Michael, AA5SH
…On Sun, Nov 24, 2024 at 3:41 PM vazquezrodjoel ***@***.***> wrote:
Had problems with the CW macros for contest exchange... was either not
sending the exchange or sending the whole string like
"5NN EXCHSTR TU"
Also, no the help when I hover the Profile fields, it says the field shold
be EXCSTR, but the initial settings wiki says MYEXCHSTR, so maybe Im just
entering the wrong shortcut...
—
Reply to this email directly, view it on GitHub
<#517>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUEEMXTZ6MYZEYMYEIOFQPL2CJPY5AVCNFSM6AAAAABSMYNCOOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGY4DQNRUGY3DSNA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Ok, I find out that after making changes on the settings for the macros, I had to change the CW Profile on the CW Console. It does not apply them right away. Which is interesting, because when I set wrongly <MYEXCHSTR>, it did transmited that as a text, like 5NN MYEXCHSTR TU, so its weird... So lesson learned, when making changes to the CW Profile, change the profile back and forward to apply the changes. |
Had problems with the CW macros for contest exchange... was either not sending the exchange or sending the whole string like
"5NN EXCHSTR TU"
Also, no the help when I hover the Profile fields, it says the field shold be EXCSTR, but the initial settings wiki says MYEXCHSTR, so maybe Im just entering the wrong shortcut... Here are my settings:

The text was updated successfully, but these errors were encountered: