I have often wondered why the radio manufactures are so tight fisted with the protocols, I guess it all comes down to money. You would think that they would be happy to share with Chirp, I guess not.
Keep up the good work guys.
Best Regards Chuck KP4DJT
On Fri, May 4, 2018 at 1:16 PM, Tom Hayward tom@tomh.us wrote:
On Fri, May 4, 2018 at 3:55 AM Rich Messeder NE1EE@hotmail.com wrote:
I recall having problems with this, too (F6A, V71A). I found that MCP was not "live" and would capture snapshots of all the memories, but CHIRP won't. I don't understand why CHIRP insists that updating must be live, when MCP doesn't. Awkward.
MCP and live mode are two completely different protocols supported by the F6, V71, and D710. The reasoning for Chirp using live mode has been discussed here many times. Chiefly, in live mode, the radio has the ability to reject a channel as invalid. This is really valuable when you're relying on guessing the protocol specification, like Chirp does. MCP toggles bits on the radio without any validation, so you better know what you're doing when toggling something. The writers of the MCP software had the advantage of being able to reference Kenwood's internal protocol documentation.
Tom KD7LXL
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com