Radio is powered by bench supply, so no batteries. Just checked for you to be sure the cable was in all the way.
The volume suggested was a good one though. One I hadn't considered. It was likely I had the volume all the way down before. Alas, excitedly I just jumped up to try it without any luck. I tried it at both half-volume and maxed out. I got the same results as mentioned originally.
Also, I found the debug.log file. If it means anything to anyone, here's the error:
[2016-11-28 22:30:30,418] chirp.ui.mainapp - DEBUG: User selected Icom IC-2200H on port /dev/ttyUSB0 [2016-11-28 22:30:30,527] chirp.ui.clone - DEBUG: Clone thread started [2016-11-28 22:30:31,029] chirp.ui.reporting - DEBUG: Throttling... [2016-11-28 22:30:31,029] chirp.ui.common - ERROR: -- Exception: -- [2016-11-28 22:30:31,030] chirp.ui.common - ERROR: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/chirp/ui/clone.py", line 249, in run self.__radio.sync_in() File "/usr/lib/python2.7/site-packages/chirp/drivers/icf.py", line 616, in sync_in self._mmap = clone_from_radio(self) File "/usr/lib/python2.7/site-packages/chirp/drivers/icf.py", line 322, in clone_from_radio raise errors.RadioError("Failed to communicate with the radio: %s" % e) RadioError: Failed to communicate with the radio: Unexpected response from radio [2016-11-28 22:30:31,030] chirp.ui.common - ERROR: ---------------- [2016-11-28 22:30:31,030] chirp.ui.clone - ERROR: Clone failed: Failed to communicate with the radio: Unexpected response from radio [2016-11-28 22:30:31,316] chirp.ui.clone - DEBUG: Clone thread ended [2016-11-28 22:30:31,317] chirp.ui.reporting - DEBUG: Reporting model usage: Icom_IC-2200H,download,True [2016-11-28 22:30:31,318] chirp.ui.reporting - DEBUG: Reporting exception [2016-11-28 22:30:31,318] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Failed to communicate with the radio: Unexpected response from radio --- [2016-11-28 22:30:31,318] chirp.ui.inputdialog - ERROR: None [2016-11-28 22:30:31,319] chirp.ui.inputdialog - ERROR: ----------------------------
---
Preserve your right to privacy. When replying to this email, I encourage you to make use of PGP compliant encryption. My key ID is A50DB9BC.
On Mon, Nov 28, 2016 at 9:33 PM, Glenn glennervin@cableone.net wrote:
Joe, Some folks have had trouble from either not getting the cable pushed in far enough. Also, they say to turn the volume up all the way on the radio. Is the battery on the radio charged enough? HTH. Glenn
----- Original Message ----- *From:* Kamikaze Joe kamikazejoe@gmail.com *To:* chirp_users@intrepid.danplanet.com *Sent:* Monday, November 28, 2016 2:23 AM *Subject:* [chirp_users] Trouble with programming ICOM IC-2200H
Was hoping I could find some help getting my IC-2200H programmed.
I've tried downloading from the radio using a generic brand cable I bought off Amazon. The procedures I've tried:
Example 1:
- Put my Icom in cloning mode.
- Select "Download from Radio" from the Radio menu in the Chirp
application. 3) Verified the Port. Selected "Icom" as the vendor. And "IC-2200H" as the Model. 4) Click "OK"
Result: Before I can even hit the button on my Icom that starts sending the data, Chirp briefly flashes the "Cloning" progress bar and then throws an error of "Unexpected response from Radio".
Example 2: If I repeat the above steps, but instead select "Detect" as the Model, I immediately get an error saying it can't detect the radio. I didn't expect it to work, but I wanted to rule it out.
Example 3:
- Put my Icom in cloning mode.
- Select "Download from Radio" from the Radio menu in the Chirp
application. 3) Again Verified the Port, Vendor, and Model as stated above. 4) Before clicking "OK", I pressed the button on my Icom to start sending data. 5) Then I clicked "OK" in the Chirp application.
Result: I tried this pressing the start button on the Icom before clicking "OK" in Chirp, and I've tried pressing them simultaneously. This method returns an error saying "Out of sync with radio".
I've search through the archive and see the same errors I'm seeing, but on posts that are several years old. The responses usually recommend checking for a driver issue, but I've done that. The cable itself seems to be functional to some degree, at least to me. I wouldn't get the "Out of sync with radio" error if the application didn't receive anything at all, right? While I don't have another device to test this particular cable with, I do have another cable that I use to program my Baofeng UV-82 with. The alternate cable uses the same chip (PL2303) and therefor the same driver/module, and that works just fine. I am able to download and program my Baofeng without any issues. So to the best of my troubleshooting abilities, the cable doesn't seem likely.
Additionally, the previous posts also reference Windows machines, but I am running Linux and I do not have a Windows computer at my disposal. I am also using the chirp-daily package on my system and made sure it was updated. Currently on "CHIRP daily-20161123" at the time of this writing.
Any further suggestions would be appreciated.
Thanks in advance
-Joe
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Glenn at glennervin@cableone.net To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Kamikaze Joe at kamikazejoe@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com