Lee, I have 2 year old mac book air, and I have used it fine with many of my radios. I make my own cables based on an ftdi board and have no problems except the icom880, (I will try my 2120 as well) I have used chip on windows XP and on Raspberry Pi. I gave up on microsoft when I got this mac.
I don't even see chirp as slow, so don't give up on anything but the cables. I did some of the development on the tyt9800 and all the later testing I did was mac! I have also used the Btech uv5x3, some ken woods, and a jet stream (lexian) with no problems on the Mac. I think the Icom issue is unique. I have used my FTDI based cables on windows with the icom so I know its not my cable. I think I also programmed a different Icom for a neighbor from my mac (after making him an fetid base cable.
For the cable issue in general I recommend using the FTDI boards available for Sparkfun, eBay, Amazon or even banggood. Search for “FT232RL FTDI USB to TTL Serial Adapter Module for Arduino Mini” This breaks outage usb to logic level serial then use the diagrams on Miklor or other sites for making the rest of your cable. Not sure if he has an Icom up there but I can give you that.
James
On Nov 28, 2016, at 2:53 PM, Lee Reynolds llyran@gmail.com wrote:
It's a MBP Retina Mid 2015, running 10.12.x, and before that 10.11.xx .
The most recent is the Yaesu SCU-18 cable. It loads the driver. RATOC Systems, Inc driver product 0xb03a, vendor 0x0584, version 4.00 ..
The problem is that chirp doesn't recognize that as a valid device in the port dropdown box. I have a /dev/cu.Bluetooth-Incoming-Port, and /dev/cu.IPhone-WirelessAP device, but nothing else is available or selectable.
So somehow I haven't found the right combination of cable, driver and setting to allow chirp to talk to my radio. I'm running the most recent CHIRP daily-20161123
Lee
On Mon, Nov 28, 2016 at 9:37 AM, Peter J. McClosky <pmcclosky@earthlink.net mailto:pmcclosky@earthlink.net> wrote: Lee,
How old is your Macbook Pro?
On my older Macbook (running 10.5.8), I had to run Chirp on a later OS.
It worked, but ran slowly. I also uploaded drivers for that OS.
Good luck,
Peter, N7IY
Peter J. McClosky, N7IY Eugene, Oregon pmcclosky@earthlink.net mailto:pmcclosky@earthlink.net n7iy@arrl.net mailto:n7iy@arrl.net http://home.earthlink.net/~pmcclosky/ http://home.earthlink.net/~pmcclosky/
On Nov 28, 2016, at 7:10 AM, Lee Reynolds <llyran@gmail.com mailto:llyran@gmail.com> wrote:
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.
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!
Lee KC7HAN
On Mon, Nov 28, 2016 at 6:59 AM, jml <jml@jmlzone.com mailto:jml@jmlzone.com> wrote: 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.
On Nov 28, 2016, at 3:23 AM, Kamikaze Joe <kamikazejoe@gmail.com mailto:kamikazejoe@gmail.com> wrote:
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.
- Verified the Port. Selected "Icom" as the vendor. And "IC-2200H" as the Model.
- 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.
- Again Verified the Port, Vendor, and Model as stated above.
- Before clicking "OK", I pressed the button on my Icom to start sending data.
- 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 mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to James Lee at jml@jmlzone.com mailto:jml@jmlzone.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Lee Reynolds at llyran@gmail.com mailto:llyran@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Peter at pmcclosky@earthlink.net mailto:pmcclosky@earthlink.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Lee Reynolds at llyran@gmail.com mailto:llyran@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to James Lee at jml@jmlzone.com mailto:jml@jmlzone.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com