Feature #4879
closedKenwood: Save versus live editing
0%
Description
I have an F6A and a V71A.
I can save configuration files from Kenwood MCP programs for the F6A and V71A. I get a message when I run CHIRP that CHIRP can't save its files. I understand "live" editing, but wonder why Kenwood can save these files and CHIRP can't. In the example below, editing does not appear to be live for the V71A.
I...
- Read a base file from the V71A using MCP. Changed several memories.
- Saved it. Closed MCP. Verified V71A not changed.
- Started MCP. Opened saved file. Verified that radio was not changed.
- Uploaded to V71A. Verified that memories were changed.
This looks to me a lot like what I do with Baofeng. I don't know about other Kenwood models, but both of mine act the same way.
Updated by Tom Hayward over 7 years ago
- Status changed from New to Feedback
The F6A and V71A support two different protocols for editing memories, MCP and "live". Chirp utilizes the live protocol because it supports validation. If Chirp sends bad data to the radio, the radio can reject it. Since Kenwood does not publish their MCP protocol, this is a lot more reliable than guessing the MCP protocol and hoping you don't introduce an error that locks up the radio, etc.
Updated by Bernhard Hailer almost 5 years ago
- Status changed from Feedback to Closed