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

TS-2000 setlevel format incorrect #304

Closed
mdblack98 opened this issue Jun 15, 2020 · 1 comment
Closed

TS-2000 setlevel format incorrect #304

mdblack98 opened this issue Jun 15, 2020 · 1 comment
Labels
Milestone

Comments

@mdblack98
Copy link
Contributor

There seems to be an issue with setlevel and getlevel volume with the TS2000.

The protocol specifies:

Read –

AGx; where x is 0 for main/1 for sub.

Response is –

AGxyyy; where x is 0 for main/1 for sub and yyy is the returned level.

Set should be –

AGxyyy; where x is 0 for main/1 for sub and yyy is the requested level.

Looking at the trace the read/response is correct. But the setlevel is missing the main/sub number.

Trace below…

73 de David M0DGB/G8FKH

13:16:21.428 Hamlib: rig_get_level called

13:16:21.428 Hamlib: rig_has_get_level called

13:16:21.428 Hamlib: kenwood_transaction called

13:16:21.428 Hamlib: kenwood_transaction: cmdstr = AG0

13:16:21.428 Hamlib: serial_flush called

13:16:21.428 Hamlib: serial_flush: tcflush

13:16:21.428 Hamlib: write_block called

13:16:21.428 Hamlib: write_block(): TX 4 bytes

13:16:21.428 Hamlib: 0000 41 47 30 3b AG0;

13:16:21.428 Hamlib: read_string called

13:16:21.452 Hamlib: read_string(): RX 7 characters

13:16:21.452 Hamlib: 0000 41 47 30 30 32 35 3b AG0025;

13:16:21.168 Hamlib: rig_set_level called

13:16:21.168 Hamlib: rig_has_set_level called

13:16:21.168 Hamlib: kenwood_set_level called

13:16:21.168 Hamlib: kenwood_transaction called

13:16:21.168 Hamlib: kenwood_transaction: cmdstr = AG017

13:16:21.168 Hamlib: serial_flush called

13:16:21.168 Hamlib: serial_flush: tcflush

13:16:21.168 Hamlib: write_block called

13:16:21.168 Hamlib: write_block(): TX 6 bytes

13:16:21.168 Hamlib: 0000 41 47 30 31 37 3b AG017;


@mdblack98 mdblack98 added the bug label Jun 15, 2020
@mdblack98 mdblack98 added this to the 4.0RC1 milestone Jun 15, 2020
mdblack98 added a commit that referenced this issue Jun 15, 2020
Some rigs say 0 is the default and need to find out if 1 causes an error
If it does we need to have rig exceptions -- hopefully it's ignored
#304
@mdblack98
Copy link
Contributor Author

You found a bug that's been there for a LONG time....
Should be working now.
Mike W9MDB

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

No branches or pull requests

1 participant