[chirp_users] I had a driver, then I lost it. (Mac OS issue)
I had installed the driver for a USB cable from Valley Enterprise for my Yaesu FT-60. Three installs and it (Mac) finally recognized the driver and cable. That was six months back. I acquired another cable for my Yaesu FT-29 2m radio. I must have got an OS update (High Sierra OS, version 10.13.6) that I cannot call up the drivers for either one (it should be only one driver upgrade). I haven’t even got to the part of trying to get Chirp to frustrate me! I know there are folks out there that have more computer smarts than I, especially when it comes to Mac. Anyone have any ideas, short of becoming a programmer? Thanks.
Tip N9MVX Mascoutah, IL
My only suggestion, get a known good OEM cable, and never worry about the driver or an update again. But that's just me. Others seem to enjoy the challenge, I just want it to work when I need it.
Vy73 – Mike – KD5KC El Paso, Texas – DM61rt
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com On Behalf Of T.E. Klamberg Klamberg via chirp_users Sent: Wednesday, July 25, 2018 8:51 PM To: chirp_users chirp_users@intrepid.danplanet.com Subject: [chirp_users] I had a driver, then I lost it. (Mac OS issue)
I had installed the driver for a USB cable from Valley Enterprise for my Yaesu FT-60. Three installs and it (Mac) finally recognized the driver and cable. That was six months back. I acquired another cable for my Yaesu FT-29 2m radio. I must have got an OS update (High Sierra OS, version 10.13.6) that I cannot call up the drivers for either one (it should be only one driver upgrade). I haven’t even got to the part of trying to get Chirp to frustrate me! I know there are folks out there that have more computer smarts than I, especially when it comes to Mac. Anyone have any ideas, short of becoming a programmer? Thanks.
Tip N9MVX Mascoutah, IL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to mike-2007@elp.rr.com at mike-2007@elp.rr.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
I have 3 cables. One I bought. The other two came in a box of stuff I bought.
On Windows 10 in Device Manager
*#1 is recognized as:*
With this driver:
These driver files:
------------------------------------------------------------------------
#2 is recognized as:
With this driver:
These driver files:
------------------------------------------------------------------------
#3 is recognized as:
With this driver:
These driver files:
They all work, you just have to do YOUR homework and install the right drivers.
Dennis M. Wage (W9BOQ)
245 Corum Hill Road Castalian Springs, TN 37031 (615) 310-4242 Cell (615) 562-5128 Home http://hammondb3organ.net http://overdubs.net
On Thu, Jul 26, 2018 at 7:38 AM, mike-2007@elp.rr.com wrote:
My only suggestion, get a known good OEM cable, and never worry about the driver or an update again. But that's just me. Others seem to enjoy the challenge, I just want it to work when I need it.
Vy73 – Mike – KD5KC El Paso, Texas – DM61rt
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com < chirp_users-bounces@intrepid.danplanet.com> On Behalf Of T.E. Klamberg Klamberg via chirp_users Sent: Wednesday, July 25, 2018 8:51 PM To: chirp_users chirp_users@intrepid.danplanet.com Subject: [chirp_users] I had a driver, then I lost it. (Mac OS issue)
I had installed the driver for a USB cable from Valley Enterprise for my Yaesu FT-60. Three installs and it (Mac) finally recognized the driver and cable. That was six months back. I acquired another cable for my Yaesu FT-29 2m radio. I must have got an OS update (High Sierra OS, version 10.13.6) that I cannot call up the drivers for either one (it should be only one driver upgrade). I haven’t even got to the part of trying to get Chirp to frustrate me! I know there are folks out there that have more computer smarts than I, especially when it comes to Mac. Anyone have any ideas, short of becoming a programmer? Thanks.
Tip N9MVX Mascoutah, IL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to mike-2007@elp.rr.com at mike-2007@elp.rr.com 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 Dennis Wage at dwage@dwage.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
Dennis. With due respect, no, I don’t have to do any homework. Using the USB cables I have, windows update NEVER screws with the cable drivers. N-E-V-E-R. I have several different cables, I think three cables for Yaesu and two for Icom, and only one cable for Wouxun. All cables by RT-Systems. All the cables use the exact same driver. The driver is written by RT-Systems specifically for their cables. Windows does not touch that driver. As I mentioned earlier, I just moved platforms here, from Win-7 to Win-10. I downloaded a fresh driver from RT-Systems, and it worked first time I plugged it in. The only “difficulty” was figuring out which comm-port it was assigned to when I plugged in the various cables.
The cable DRIVER issue is only for those folks who take the route that leads them to the cloned chipset troubles. And it is up to them to “do their homework”. Each can decide if their time is worth the frustration and the few $$$$ saved with the cheaper cables. I don’t need to program my radios often. When I do, I just want it to work. I don’t want to find out something broke and now I have to spend time figuring out what broke. I don’t want to waste time “rolling back” until it works again. I want to program the radio and get on with my project. That is worth the extra cost of the cables to me. That value may not apply to all, and that is fine. It’s a personal choice after all.
For anyone interested in investigating RT-Systems cables after reading this, sign up for their newsletter. Periodically they have sales, and you can save a few $$$ buying during the sale.
NOTE: I have no connection with RT-Systems in any way. I will not make a penny if you buy 100 cables. I am just a satisfied customer. Very satisfied since the Win-10 upgrade went so perfectly with that part of the changeover. I just want it to work. And it does. Every time I plug in a cable - it works. Looking forward to several years of painless use on Win-10 now.
Vy73 – Mike – KD5KC
El Paso, Texas – DM61rt
From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com On Behalf Of Dennis Wage Sent: Thursday, July 26, 2018 7:25 AM To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Subject: Re: [chirp_users] I had a driver, then I lost it. (Mac OS issue)
I have 3 cables. One I bought. The other two came in a box of stuff I bought.
On Windows 10 in Device Manager
#1 is recognized as:
With this driver:
These driver files:
------------------------------------------------------------------------
#2 is recognized as:
With this driver:
These driver files:
------------------------------------------------------------------------
#3 is recognized as:
With this driver:
These driver files:
They all work, you just have to do YOUR homework and install the right drivers.
Dennis M. Wage (W9BOQ)
245 Corum Hill Road
Castalian Springs, TN 37031
(615) 310-4242 Cell
(615) 562-5128 Home http://hammondb3organ.net/ http://hammondb3organ.net
http://overdubs.net http://overdubs.net
On Thu, Jul 26, 2018 at 7:38 AM, <mike-2007@elp.rr.com mailto:mike-2007@elp.rr.com > wrote:
My only suggestion, get a known good OEM cable, and never worry about the driver or an update again. But that's just me. Others seem to enjoy the challenge, I just want it to work when I need it.
Vy73 – Mike – KD5KC El Paso, Texas – DM61rt
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com mailto:chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com mailto:chirp_users-bounces@intrepid.danplanet.com > On Behalf Of T.E. Klamberg Klamberg via chirp_users Sent: Wednesday, July 25, 2018 8:51 PM To: chirp_users <chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com > Subject: [chirp_users] I had a driver, then I lost it. (Mac OS issue)
I had installed the driver for a USB cable from Valley Enterprise for my Yaesu FT-60. Three installs and it (Mac) finally recognized the driver and cable. That was six months back. I acquired another cable for my Yaesu FT-29 2m radio. I must have got an OS update (High Sierra OS, version 10.13.6) that I cannot call up the drivers for either one (it should be only one driver upgrade). I haven’t even got to the part of trying to get Chirp to frustrate me! I know there are folks out there that have more computer smarts than I, especially when it comes to Mac. Anyone have any ideas, short of becoming a programmer? Thanks.
Tip N9MVX Mascoutah, IL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to mike-2007@elp.rr.com mailto:mike-2007@elp.rr.com at mike-2007@elp.rr.com mailto:mike-2007@elp.rr.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 This message was sent to Dennis Wage at dwage@dwage.com mailto:dwage@dwage.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
Mike,
I wasn't responding to you.
Dennis M. Wage (W9BOQ)
245 Corum Hill Road Castalian Springs, TN 37031 (615) 310-4242 Cell (615) 562-5128 Home http://hammondb3organ.net http://overdubs.net
On Thu, Jul 26, 2018 at 5:12 PM, mike-2007@elp.rr.com wrote:
Dennis. With due respect, no, I don’t have to do any homework. Using the USB cables I have, windows update NEVER screws with the cable drivers. N-E-V-E-R. I have several different cables, I think three cables for Yaesu and two for Icom, and only one cable for Wouxun. All cables by RT-Systems. All the cables use the exact same driver. The driver is written by RT-Systems specifically for their cables. Windows does not touch that driver. As I mentioned earlier, I just moved platforms here, from Win-7 to Win-10. I downloaded a fresh driver from RT-Systems, and it worked first time I plugged it in. The only “difficulty” was figuring out which comm-port it was assigned to when I plugged in the various cables.
The cable DRIVER issue is only for those folks who take the route that leads them to the cloned chipset troubles. And it is up to them to “do their homework”. Each can decide if their time is worth the frustration and the few $$$$ saved with the cheaper cables. I don’t need to program my radios often. When I do, I just want it to work. I don’t want to find out something broke and now I have to spend time figuring out what broke. I don’t want to waste time “rolling back” until it works again. I want to program the radio and get on with my project. That is worth the extra cost of the cables to me. That value may not apply to all, and that is fine. It’s a personal choice after all.
For anyone interested in investigating RT-Systems cables after reading this, sign up for their newsletter. Periodically they have sales, and you can save a few $$$ buying during the sale.
NOTE: I have no connection with RT-Systems in any way. I will not make a penny if you buy 100 cables. I am just a satisfied customer. Very satisfied since the Win-10 upgrade went so perfectly with that part of the changeover. I just want it to work. And it does. Every time I plug in a cable - it works. Looking forward to several years of painless use on Win-10 now.
Vy73 – Mike – KD5KC
El Paso, Texas – DM61rt
*From:* chirp_users-bounces@intrepid.danplanet.com < chirp_users-bounces@intrepid.danplanet.com> *On Behalf Of *Dennis Wage *Sent:* Thursday, July 26, 2018 7:25 AM *To:* Discussion of CHIRP chirp_users@intrepid.danplanet.com *Subject:* Re: [chirp_users] I had a driver, then I lost it. (Mac OS issue)
I have 3 cables. One I bought. The other two came in a box of stuff I bought.
On Windows 10 in Device Manager
*#1 is recognized as:*
With this driver:
These driver files:
#2 is recognized as:
With this driver:
These driver files:
#3 is recognized as:
With this driver:
These driver files:
They all work, you just have to do YOUR homework and install the right drivers.
Dennis M. Wage (W9BOQ)
245 Corum Hill Road
Castalian Springs, TN 37031
(615) 310-4242 Cell
(615) 562-5128 Home http://hammondb3organ.net
On Thu, Jul 26, 2018 at 7:38 AM, mike-2007@elp.rr.com wrote:
My only suggestion, get a known good OEM cable, and never worry about the driver or an update again. But that's just me. Others seem to enjoy the challenge, I just want it to work when I need it.
Vy73 – Mike – KD5KC El Paso, Texas – DM61rt
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com < chirp_users-bounces@intrepid.danplanet.com> On Behalf Of T.E. Klamberg Klamberg via chirp_users Sent: Wednesday, July 25, 2018 8:51 PM To: chirp_users chirp_users@intrepid.danplanet.com Subject: [chirp_users] I had a driver, then I lost it. (Mac OS issue)
I had installed the driver for a USB cable from Valley Enterprise for my Yaesu FT-60. Three installs and it (Mac) finally recognized the driver and cable. That was six months back. I acquired another cable for my Yaesu FT-29 2m radio. I must have got an OS update (High Sierra OS, version 10.13.6) that I cannot call up the drivers for either one (it should be only one driver upgrade). I haven’t even got to the part of trying to get Chirp to frustrate me! I know there are folks out there that have more computer smarts than I, especially when it comes to Mac. Anyone have any ideas, short of becoming a programmer? Thanks.
Tip N9MVX Mascoutah, IL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to mike-2007@elp.rr.com at mike-2007@elp.rr.com 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 Dennis Wage at dwage@dwage.com 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 Dennis Wage at dwage@dwage.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
I have several cables with the fake Prolific chips in them. Once you roll back the driver for one cable, it rolls back for all of them. When you consider how often you need to reprogram your radios (about every other month or less), taking a minute to rollback your driver if you have to is such a minor thing to me. A lot easier and cheaper than replacing 10-15 cables. People make WAY to much of a big deal out of something so easy to deal with.
Jardy Dawson WA7JRD Ham Radio
Sent three weeks from now through a newly discovered worm hole in the space-time continuum.
On Jul 26, 2018, at 05:38, mike-2007@elp.rr.com mike-2007@elp.rr.com wrote:
My only suggestion, get a known good OEM cable, and never worry about the driver or an update again. But that's just me. Others seem to enjoy the challenge, I just want it to work when I need it.
Vy73 – Mike – KD5KC El Paso, Texas – DM61rt
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com On Behalf Of T.E. Klamberg Klamberg via chirp_users Sent: Wednesday, July 25, 2018 8:51 PM To: chirp_users chirp_users@intrepid.danplanet.com Subject: [chirp_users] I had a driver, then I lost it. (Mac OS issue)
I had installed the driver for a USB cable from Valley Enterprise for my Yaesu FT-60. Three installs and it (Mac) finally recognized the driver and cable. That was six months back. I acquired another cable for my Yaesu FT-29 2m radio. I must have got an OS update (High Sierra OS, version 10.13.6) that I cannot call up the drivers for either one (it should be only one driver upgrade). I haven’t even got to the part of trying to get Chirp to frustrate me! I know there are folks out there that have more computer smarts than I, especially when it comes to Mac. Anyone have any ideas, short of becoming a programmer? Thanks.
Tip N9MVX Mascoutah, IL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to mike-2007@elp.rr.com at mike-2007@elp.rr.com 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 Jardy at jardy72@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
There have been a lot of replies here about rolling back the driver, but they all miss the point. This is for macOS, and it appears to be an FTDI cable (Valley Enterprises uses FTDI in all of their cables as far as I know).
I haven't tried to use macOS for CHIRP in some time, but there appear to be some issues with the FTDI driver provided by Apple as compared to the official FTDI driver, at least in some of the Google searches I've done. The issue showed up on an Arduino programming discussion and they had difficulties getting the FTDI driver installed in place of the Apple driver (which appears to not implement certain features). Although it appears that it was mainly a permissions issue (you have to give permission, apparently).
Here's info on how to approve a driver: * https://developer.apple.com/library/archive/technotes/tn2459/_index.html
Here is the link to the FTDI driver page: * http://www.ftdichip.com/Drivers/VCP.htm
Here is the CHIRP page on working with macOS: * https://chirp.danplanet.com/projects/chirp/wiki/MacOS_Tips
Hopefully you can get it working from the above information.
On 7/26/2018 9:03 AM, Jardy Dawson via chirp_users wrote:
I have several cables with the fake Prolific chips in them. Once you roll back the driver for one cable, it rolls back for all of them. When you consider how often you need to reprogram your radios (about every other month or less), taking a minute to rollback your driver if you have to is such a minor thing to me. A lot easier and cheaper than replacing 10-15 cables. People make WAY to much of a big deal out of something so easy to deal with.
Jardy Dawson WA7JRD Ham Radio
Sent three weeks from now through a newly discovered worm hole in the space-time continuum.
On Jul 26, 2018, at 05:38, mike-2007@elp.rr.com mike-2007@elp.rr.com wrote:
My only suggestion, get a known good OEM cable, and never worry about the driver or an update again. But that's just me. Others seem to enjoy the challenge, I just want it to work when I need it.
Vy73 – Mike – KD5KC El Paso, Texas – DM61rt
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com On Behalf Of T.E. Klamberg Klamberg via chirp_users Sent: Wednesday, July 25, 2018 8:51 PM To: chirp_users chirp_users@intrepid.danplanet.com Subject: [chirp_users] I had a driver, then I lost it. (Mac OS issue)
I had installed the driver for a USB cable from Valley Enterprise for my Yaesu FT-60. Three installs and it (Mac) finally recognized the driver and cable. That was six months back. I acquired another cable for my Yaesu FT-29 2m radio. I must have got an OS update (High Sierra OS, version 10.13.6) that I cannot call up the drivers for either one (it should be only one driver upgrade). I haven’t even got to the part of trying to get Chirp to frustrate me! I know there are folks out there that have more computer smarts than I, especially when it comes to Mac. Anyone have any ideas, short of becoming a programmer? Thanks.
Tip N9MVX Mascoutah, IL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to mike-2007@elp.rr.com at mike-2007@elp.rr.com 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 Jardy at jardy72@yahoo.com 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 Aubrey Turner at aubrey.c.turner@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Rgr that Jardy. It works for you. Were I in this category, I guess I would learn how to do it, and it would become the first thing checked when a problem showed up. But from the number of messages from various individuals here, it seems to be more than a minor thing for many. When the first chip set got cloned, I had one adapter cable quit on me. Back then, the driver update wasn't a known problem. So I thought the cable was bad and replaced it. But when it happened again and the word got out what was happening, I made the decision to stick to OEM cables or cables of known good production. I discovered the RT-system cables, and over the years as I have gotten various different radios I just paid the price up front for the good cable from the start.
But you're right. People make way too much of an issue of it. Were I really interested, I'd take a look at what % of the messages in July were about CHIRP not working that ended up being a Windows update issue. Probably the #1 topic I'd wager. If CHIRP quits, reload your drivers and try again. Or replace the cable with a known good one and never worry about it again.
I'll bet Dan cringes every time a Windows update hits.
Vy73 – Mike – KD5KC El Paso, Texas – DM61rt
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com On Behalf Of Jardy Dawson via chirp_users Sent: Thursday, July 26, 2018 8:03 AM To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Subject: Re: [chirp_users] I had a driver, then I lost it. (Mac OS issue)
I have several cables with the fake Prolific chips in them. Once you roll back the driver for one cable, it rolls back for all of them. When you consider how often you need to reprogram your radios (about every other month or less), taking a minute to rollback your driver if you have to is such a minor thing to me. A lot easier and cheaper than replacing 10-15 cables. People make WAY to much of a big deal out of something so easy to deal with.
Jardy Dawson WA7JRD Ham Radio
Sent three weeks from now through a newly discovered worm hole in the space-time continuum.
On Jul 26, 2018, at 05:38, mike-2007@elp.rr.com mike-2007@elp.rr.com wrote:
My only suggestion, get a known good OEM cable, and never worry about the driver or an update again. But that's just me. Others seem to enjoy the challenge, I just want it to work when I need it.
Vy73 – Mike – KD5KC El Paso, Texas – DM61rt
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com On Behalf Of T.E. Klamberg Klamberg via chirp_users Sent: Wednesday, July 25, 2018 8:51 PM To: chirp_users chirp_users@intrepid.danplanet.com Subject: [chirp_users] I had a driver, then I lost it. (Mac OS issue)
I had installed the driver for a USB cable from Valley Enterprise for my Yaesu FT-60. Three installs and it (Mac) finally recognized the driver and cable. That was six months back. I acquired another cable for my Yaesu FT-29 2m radio. I must have got an OS update (High Sierra OS, version 10.13.6) that I cannot call up the drivers for either one (it should be only one driver upgrade). I haven’t even got to the part of trying to get Chirp to frustrate me! I know there are folks out there that have more computer smarts than I, especially when it comes to Mac. Anyone have any ideas, short of becoming a programmer? Thanks.
Tip N9MVX Mascoutah, IL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to mike-2007@elp.rr.com at mike-2007@elp.rr.com 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 Jardy at jardy72@yahoo.com 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 mike-2007@elp.rr.com at mike-2007@elp.rr.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Tip, I just upgraded to 10.13.6 and had an issue. Are you getting the message about /dev/cu.usb (or something like that, I'm not on that Mac right now to double check)?
What I found (after reinstalling drivers, etc.) was that I needed to open up System Preferences > Security & Privacy. When I did that there was a message (in the General tab) that some drivers had been blocked on boot. I can't remember the exact message, but I was able to click "Allow" or something like that and pick the drivers I wanted to allow - one of them was Prolific (for my cable) but there was like 5 or so drivers blocked and another was an FTDI driver (for Arduino stuff) - note, though, that FTDI was listed as "Future Technology Devices International" (which is what FTDI stands for).
So, it wasn't that the driver wasn't still installed, or that CHIRP wasn't working right, it was just that macOS 10.13.6 had blocked the driver (and others) and I had to explicitly allow them.
You might try rebooting if you don't see that in Security & Privacy right away. You might also try reinstalling the driver (instructions on CHIRP site) just to force macOS to show that option to allow the driver. *The magic (I think) is in watching System Preferences > Security & Privacy (General tab) for any messages that macOS is blocking you and explicitly choosing allow when it does.*
-Tycen K7TYC
On Wed, Jul 25, 2018 at 7:50 PM T.E. Klamberg Klamberg via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
I had installed the driver for a USB cable from Valley Enterprise for my Yaesu FT-60. Three installs and it (Mac) finally recognized the driver and cable. That was six months back. I acquired another cable for my Yaesu FT-29 2m radio. I must have got an OS update (High Sierra OS, version 10.13.6) that I cannot call up the drivers for either one (it should be only one driver upgrade). I haven’t even got to the part of trying to get Chirp to frustrate me! I know there are folks out there that have more computer smarts than I, especially when it comes to Mac. Anyone have any ideas, short of becoming a programmer? Thanks.
Tip N9MVX Mascoutah, IL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tycen at tycen@tycen.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
drivers here: http://www.ftdichip.com/Drivers/VCP.htm instructions here: http://www.ftdichip.com/Support/Documents/InstallGuides.htm
On 07/25/2018 09:50 PM, T.E. Klamberg Klamberg via chirp_users wrote:
I had installed the driver for a USB cable from Valley Enterprise for my Yaesu FT-60. Three installs and it (Mac) finally recognized the driver and cable. That was six months back. I acquired another cable for my Yaesu FT-29 2m radio. I must have got an OS update (High Sierra OS, version 10.13.6) that I cannot call up the drivers for either one (it should be only one driver upgrade). I haven’t even got to the part of trying to get Chirp to frustrate me! I know there are folks out there that have more computer smarts than I, especially when it comes to Mac. Anyone have any ideas, short of becoming a programmer? Thanks.
Tip N9MVX Mascoutah, IL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Paul AC0HY at ac0hy@wpmills.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
participants (7)
-
Aubrey Turner -
Dennis Wage -
Jardy Dawson -
mike-2007＠elp.rr.com -
T.E. Klamberg Klamberg -
Tycen Stafford -
W Paul Mills