<div dir="ltr">Honestly, chirp seems pretty hopeless on my Macbook Pro. I know it's not chirp, but the cables I've tried (3 of them). I can't get the drivers to load, and finally got tired of buying new cables. Course, I'm kind of hijacking this thread, since I'm using a Yaesu. <div><br></div><div>It would be nice if there was a guide for Mac. But this cable, from this location, with the driver from here. Otherwise trying to get it to work on a mac is pretty frustrating!</div><div><br></div><div>Lee</div><div>KC7HAN</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 28, 2016 at 6:59 AM, jml <span dir="ltr"><<a href="mailto:jml@jmlzone.com" target="_blank">jml@jmlzone.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Not sure if this is related, but it has been reported that for the id880h, chirp is fine for windows and not for mac. I want to take some time and see if I can figure out what is happening. Been bogged down with many other issues first so I have not gotten back to it. From my recollection I was OK with the id880h with the same cable on some platforms while it did not work ok on the other platforms. I don't have a 2200 but I do have a 2120 and an id880 I can test on with XP. Mac and Pi.<br>
<div><div class="h5"><br>
<br>
> On Nov 28, 2016, at 3:23 AM, Kamikaze Joe <<a href="mailto:kamikazejoe@gmail.com">kamikazejoe@gmail.com</a>> wrote:<br>
><br>
> Was hoping I could find some help getting my IC-2200H programmed.<br>
><br>
> I've tried downloading from the radio using a generic brand cable I bought off Amazon.<br>
> The procedures I've tried:<br>
><br>
> Example 1:<br>
> 1) Put my Icom in cloning mode.<br>
> 2) Select "Download from Radio" from the Radio menu in the Chirp application.<br>
> 3) Verified the Port. Selected "Icom" as the vendor. And "IC-2200H" as the Model.<br>
> 4) Click "OK"<br>
><br>
> 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".<br>
><br>
> Example 2:<br>
> 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.<br>
><br>
> Example 3:<br>
> 1) Put my Icom in cloning mode.<br>
> 2) Select "Download from Radio" from the Radio menu in the Chirp application.<br>
> 3) Again Verified the Port, Vendor, and Model as stated above.<br>
> 4) Before clicking "OK", I pressed the button on my Icom to start sending data.<br>
> 5) Then I clicked "OK" in the Chirp application.<br>
><br>
> 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".<br>
><br>
> 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.<br>
><br>
> 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.<br>
><br>
> Any further suggestions would be appreciated.<br>
><br>
> Thanks in advance<br>
><br>
> -Joe<br>
</div></div>> ______________________________<wbr>_________________<br>
> chirp_users mailing list<br>
> <a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.<wbr>danplanet.com</a><br>
> <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/<wbr>mailman/listinfo/chirp_users</a><br>
> This message was sent to James Lee at <a href="mailto:jml@jmlzone.com">jml@jmlzone.com</a><br>
> To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@<wbr>intrepid.danplanet.com</a><br>
<br>
______________________________<wbr>_________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.<wbr>danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/<wbr>mailman/listinfo/chirp_users</a><br>
This message was sent to Lee Reynolds at <a href="mailto:llyran@gmail.com">llyran@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@<wbr>intrepid.danplanet.com</a><br>
</blockquote></div><br></div>