CHIRP

Yes, I'll take a look. My natural suspicion is when I added the raw support: https://chirp.danplanet.com/projects/chirp/repository/revisions/ebcb6aeda1b8 since that is the only of my changes that could affect other drivers.

I don't have an IC2200h, but it would be helpful if possible if the reporter could compare chirp versions and determine at which version support actually broke. That would help narrow down and confirm if my change caused the regression.

John, do you know when this first happened?

Also if you could describe the way it fails: does it fail to read from the radio? Write to the radio? Recognize the radio? Something else?

Okay, I believe I realize what happened. When I refactored my original patch into the two-phase patch and introduced an IcomRawCloneModeRadio I inadvertently BCD-encoded all day for the original radio type. Previously, it would BCD-encode only the memory contents, and other commands, such as getting the model or putting the radio into clone mode, were sent raw. This will be an easy fix.