Re: [Hamlib-developer] Elecraft K3 power output problem.

[Nate B. <n0...@n0...>]

So, digging into this with my K3 I find that my radio is returning a
different string than the manual states with four digits instead of
three.  The first three digits appear to be the set power level and the
fourth the PA in use with 0 being the built-in and 1 being the KPA-100.
It is quite apparent when the 12/13W switch point is crossed:

Rig command: w
rigctl_parse: input_line: w
Command: pc;
rigctl_parse: vfo_opt=0
rigctl_parse.c(5172):rigctl_send_cmd entered
rigctl_send_cmd: backend_num=2
rigctl_send_cmd: KENWOOD
rigctl_send_cmd: arg1=pc;
rigctl_send_cmd: bufcmd=pc;
rigctl_send_cmd: text protocol, send_cmd_term=0x0a 0x0d 0x00
rigctl_send_cmd: rigport=5, bufcmd=pc;, cmd_len=3
write_block(): TX 3 bytes
0000    70 63 3b                                            pc;             
rigctl_send_cmd: debug Cmd
read_string_generic(): RX 7 characters, direct=1
0000    50 43 30 34 35 31 3b                                PC0451;         
rigctl_parse.c(5479):rigctl_send_cmd returning2(0) 
Reply: PC0451;rigctl_parse: called, interactive=1

Rig command: w pc;
rigctl_parse: input_line: w pc;
rigctl_parse: vfo_opt=0
rigctl_parse.c(5172):rigctl_send_cmd entered
rigctl_send_cmd: backend_num=2
rigctl_send_cmd: KENWOOD
rigctl_send_cmd: arg1=pc;
rigctl_send_cmd: bufcmd=pc;
rigctl_send_cmd: text protocol, send_cmd_term=0x0a 0x0d 0x00
rigctl_send_cmd: rigport=5, bufcmd=pc;, cmd_len=3
write_block(): TX 3 bytes
0000    70 63 3b                                            pc;             
rigctl_send_cmd: debug Cmd
read_string_generic(): RX 7 characters, direct=1
0000    50 43 30 31 33 31 3b                                PC0131;         
rigctl_parse.c(5479):rigctl_send_cmd returning2(0) 
Reply: PC0131;rigctl_parse: called, interactive=1

Rig command: w pc;
rigctl_parse: input_line: w pc;
rigctl_parse: vfo_opt=0
rigctl_parse.c(5172):rigctl_send_cmd entered
rigctl_send_cmd: backend_num=2
rigctl_send_cmd: KENWOOD
rigctl_send_cmd: arg1=pc;
rigctl_send_cmd: bufcmd=pc;
rigctl_send_cmd: text protocol, send_cmd_term=0x0a 0x0d 0x00
rigctl_send_cmd: rigport=5, bufcmd=pc;, cmd_len=3
write_block(): TX 3 bytes
0000    70 63 3b                                            pc;             
rigctl_send_cmd: debug Cmd
read_string_generic(): RX 7 characters, direct=1
0000    50 43 31 32 30 30 3b                                PC1200;         
rigctl_parse.c(5479):rigctl_send_cmd returning2(0) 
Reply: PC1200;rigctl_parse: called, interactive=1

Rig command: w pc;
rigctl_parse: input_line: w pc;
rigctl_parse: vfo_opt=0
rigctl_parse.c(5172):rigctl_send_cmd entered
rigctl_send_cmd: backend_num=2
rigctl_send_cmd: KENWOOD
rigctl_send_cmd: arg1=pc;
rigctl_send_cmd: bufcmd=pc;
rigctl_send_cmd: text protocol, send_cmd_term=0x0a 0x0d 0x00
rigctl_send_cmd: rigport=5, bufcmd=pc;, cmd_len=3
write_block(): TX 3 bytes
0000    70 63 3b                                            pc;             
rigctl_send_cmd: debug Cmd
read_string_generic(): RX 7 characters, direct=1
0000    50 43 30 35 30 30 3b                                PC0500;         
rigctl_parse.c(5479):rigctl_send_cmd returning2(0) 
Reply: PC0500;rigctl_parse: called, interactive=1

Rig command: w pc;
rigctl_parse: input_line: w pc;
rigctl_parse: vfo_opt=0
rigctl_parse.c(5172):rigctl_send_cmd entered
rigctl_send_cmd: backend_num=2
rigctl_send_cmd: KENWOOD
rigctl_send_cmd: arg1=pc;
rigctl_send_cmd: bufcmd=pc;
rigctl_send_cmd: text protocol, send_cmd_term=0x0a 0x0d 0x00
rigctl_send_cmd: rigport=5, bufcmd=pc;, cmd_len=3
write_block(): TX 3 bytes
0000    70 63 3b                                            pc;             
rigctl_send_cmd: debug Cmd
read_string_generic(): RX 7 characters, direct=1
0000    50 43 30 30 30 30 3b                                PC0000;         
rigctl_parse.c(5479):rigctl_send_cmd returning2(0) 
Reply: PC0000;rigctl_parse: called, interactive=1

Rig command: w pc;
rigctl_parse: input_line: w pc;
rigctl_parse: vfo_opt=0
rigctl_parse.c(5172):rigctl_send_cmd entered
rigctl_send_cmd: backend_num=2
rigctl_send_cmd: KENWOOD
rigctl_send_cmd: arg1=pc;
rigctl_send_cmd: bufcmd=pc;
rigctl_send_cmd: text protocol, send_cmd_term=0x0a 0x0d 0x00
rigctl_send_cmd: rigport=5, bufcmd=pc;, cmd_len=3
write_block(): TX 3 bytes
0000    70 63 3b                                            pc;             
rigctl_send_cmd: debug Cmd
read_string_generic(): RX 7 characters, direct=1
0000    50 43 30 30 31 30 3b                                PC0010;         
rigctl_parse.c(5479):rigctl_send_cmd returning2(0) 
Reply: PC0010;rigctl_parse: called, interactive=1


My questions now are, what firmware revision changed this?  Does yours
return three or four digits?

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819