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.

Sign up for GitHub

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

Jump to bottom

send_morse for Yaesu rigs broken #1368

Closed
mdblack98 opened this issue Aug 19, 2023 · 1 comment
Closed

send_morse for Yaesu rigs broken #1368

mdblack98 opened this issue Aug 19, 2023 · 1 comment
Labels
bug
Milestone
4.6

Comments

@mdblack98
Copy link
Contributor

Yaesu KY command sends memory messages and not real-time text.
So we need to store text in memory and then transmit the memory location.
Should be able to support longer than 40 chars too.
@mdblack98 mdblack98 added the bug label Aug 19, 2023
@mdblack98 mdblack98 added this to the 4.6 milestone Aug 19, 2023
mdblack98 added a commit that referenced this issue Aug 19, 2023
@mdblack98
Increase send_morse size to use maximum for rigs or 20 chars (if mors…
b40da0f 
…e_qsize unknown)

This will still allow for up to 1023 characater to queue up.
No guarantees on which rigs allow for this queuing though.
Kenwood rigs can at least find the buffer status to wait for room but not all rigs do.
#1368
@mdblack98
Copy link
Contributor Author

This has been fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
4.6
Development

No branches or pull requests
1 participant
@mdblack98