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

Kenwood voice stop not working #1385

Closed
mdblack98 opened this issue Sep 16, 2023 · 0 comments
Closed

Kenwood voice stop not working #1385

mdblack98 opened this issue Sep 16, 2023 · 0 comments
Labels
bug fixed Issue has been fixed
Milestone

Comments

@mdblack98
Copy link
Contributor

OK The play works… but I think the Stop is problematic.

Currently the voice command for the Icom/Yaesu and TS590 is a single character for channel number, where 1 is the first channel and 0 channel is stop message.

The TS890 has two bytes for channel number and operation.

Here is the stop cmd you send.

15:14:50.723 Send Voice Memory Number 0 to rig

15:14:50.723 Hamlib: 2:rig.c(7105):rig_send_voice_mem entered

15:14:50.723 Hamlib: 3:kenwood.c(5347):kenwood_send_voice_mem entered

15:14:50.723 Hamlib: kenwood_transaction called cmd=PB101

15:14:50.723 Hamlib: kenwood_transaction: cmdstr = PB101

15:14:50.723 Hamlib: write_block(): TX 6 bytes, method=2

15:14:50.723 Hamlib: 0000 50 42 31 30 31 3b PB101;

Here you are sending 0 for channel number (stop for other radios) and 1 for operation, which is play on the 890. 0 is not a valid channel number on the 890….

To stop channel 1, the message would be PB110; Start channel 2, PB121; then stop channel 2 PB120;

I wonder if the 890S allows multiple messages to play at once. Anyway, I presume Hamlib doesn’t want to keep track of the channel number? So does that mean the api needs two parameters, or another function setVoiceChannelNumber(int chanNum)?

73 de David M0DGB/G8FKH

@mdblack98 mdblack98 added the bug label Sep 16, 2023
@mdblack98 mdblack98 added this to the 4.6 milestone Sep 16, 2023
@mdblack98 mdblack98 added needs test Patches have been submitted but need testing to close issue fixed Issue has been fixed labels Sep 16, 2023
@mdblack98 mdblack98 removed the needs test Patches have been submitted but need testing to close issue label Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug fixed Issue has been fixed
Projects
None yet
Development

No branches or pull requests

1 participant