[chirp_users] HELP
I bought two baofeng radios, one is UV-82C an the other is BF-F8H and I can get neither one to up load to the computer it says in the paper i got with the radios that the small CD disc has all the software on it but when i click on it open it there is just a bunch of files, it says in the instructions that to click on the radio on the menu bar but so far I have found no menu bar with a radio to click on. It says I have to upload to the computer before I can program the radio OKAY what do I have to do get past this point. I'm lost I can't even get started till this happens. thank you Jim KM6WC CM97iw
On Sat, Dec 6, 2014 at 2:17 AM, Jim Russell km6wc6@yahoo.com wrote:
I bought two baofeng radios, one is UV-82C an the other is BF-F8H and I can get neither one to up load to the computer it says in the paper i got with the radios that the small CD disc has all the software on it but when i click on it open it there is just a bunch of files, it says in the instructions that to click on the radio on the menu bar but so far I have found no menu bar with a radio to click on. It says I have to upload to the computer before I can program the radio OKAY what do I have to do get past this point. I'm lost I can't even get started till this happens.
thank you
Jim KM6WC CM97iw
Hi Jim,
The best advice for the small CD that come with the low cost programming cables is to never put it in your optical drive.
The first think you must do is to get the programming cable working properly. Most low cost programming cables have an unauthorized copy of the Prolific USB-to-serial chip in them. The driver that is automatically installed by Windows is incompatible with these chips. You will have to downgrade your driver to a previous version (v3.2.0.0 for Windows Vista, 7, 8 and 8.1) which is compatible. Visit the miklor.com website to get the needed device driver and instructions to get it installed and selected.
http://www.miklor.com/COM/UV_Drivers.php
There are sections in the miklor.com website for the UV-82 and the BF-F8P. Each one will have the OEM software for each radio model. However, you won't need either since CHIRP will program both models.
It is not currently recommended that the CHIRP v0.4.x stable build be used with Balfeng/Pofung radios. So download and install the latest daily build of CHIRP.
The first thing that you must do with CHIRP is to _download_ from each radio into CHIRP. Once this first download is successful and before making any changes, save these channels and setting to a *.img file. Keep this first file in a safe place and don't ever edit it. It is you "factory reset" if you should ever need one in the future.
Notice how the CHIRP tab for each radio will be prefixed with "Baofeng UV-82:" and "Baofeng BF-F8HP:". You will only be able to upload the tab having the prefix that matches the target radio model. That being said, if you do all of you channel programming in the tab for the BF-F8HP and save it to the CHIRP .img data file format, you can import the BF-F8HP .img file into the "Baofeng UV82:" tab. Going this direction, all of the MID and HIGH power level settings of the BF-F8HP will automatically be converted to HIGH in the UV-82. If you go the other direction, the UV-82C HIGH power settings will be changed to MID (the closest match) in the BF-F8HP and you will have to manually edit any channels that you want to be set to HIGH power.
Jim KC9HI
Jim KC9HI
This is a very good explanation and should work fine. I usually just use the "official" cables myself and have no problem, so this is another option in case things don't pan out. I just bought one for my BAofeng radios and another for my Wouxun ones, no problems. Once I plugged the cable into the USB port of the computer, it had to install some drivers, but after that, programming happened without a hitch. Good luck with your programming! Shon, K6QT
Shon R. Edwards, MA, AG (Czech Republic) Amateur call: K6QT 1039 N 2575 W Layton, UT, 84041-7709 USA E-mail: sre.1966@gmail.com Home phone: (801) 444-3445 Cell: (605) 209-6064
On Sat, Dec 6, 2014 at 5:05 AM, Jim Unroe rock.unroe@gmail.com wrote:
On Sat, Dec 6, 2014 at 2:17 AM, Jim Russell km6wc6@yahoo.com wrote:
I bought two baofeng radios, one is UV-82C an the other is BF-F8H and I
can
get neither one to up load to the computer it says in the paper i got
with
the radios that the small CD disc has all the software on it but when i click on it open it there is just a bunch of files, it says in the instructions that to click on the radio on the menu bar but so far I have found no menu bar with a radio to click on. It says I have to upload to the computer before I can program the
radio
OKAY what do I have to do get past this point. I'm lost I can't even get started till this happens.
thank you
Jim KM6WC CM97iw
Hi Jim,
The best advice for the small CD that come with the low cost programming cables is to never put it in your optical drive.
The first think you must do is to get the programming cable working properly. Most low cost programming cables have an unauthorized copy of the Prolific USB-to-serial chip in them. The driver that is automatically installed by Windows is incompatible with these chips. You will have to downgrade your driver to a previous version (v3.2.0.0 for Windows Vista, 7, 8 and 8.1) which is compatible. Visit the miklor.com website to get the needed device driver and instructions to get it installed and selected.
http://www.miklor.com/COM/UV_Drivers.php
There are sections in the miklor.com website for the UV-82 and the BF-F8P. Each one will have the OEM software for each radio model. However, you won't need either since CHIRP will program both models.
It is not currently recommended that the CHIRP v0.4.x stable build be used with Balfeng/Pofung radios. So download and install the latest daily build of CHIRP.
The first thing that you must do with CHIRP is to _download_ from each radio into CHIRP. Once this first download is successful and before making any changes, save these channels and setting to a *.img file. Keep this first file in a safe place and don't ever edit it. It is you "factory reset" if you should ever need one in the future.
Notice how the CHIRP tab for each radio will be prefixed with "Baofeng UV-82:" and "Baofeng BF-F8HP:". You will only be able to upload the tab having the prefix that matches the target radio model. That being said, if you do all of you channel programming in the tab for the BF-F8HP and save it to the CHIRP .img data file format, you can import the BF-F8HP .img file into the "Baofeng UV82:" tab. Going this direction, all of the MID and HIGH power level settings of the BF-F8HP will automatically be converted to HIGH in the UV-82. If you go the other direction, the UV-82C HIGH power settings will be changed to MID (the closest match) in the BF-F8HP and you will have to manually edit any channels that you want to be set to HIGH power.
Jim KC9HI
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
On 06-Dec-14 09:15, Shon Edwards wrote:
This is a very good explanation and should work fine. I usually just use the "official" cables myself and have no problem, so this is another option in case things don't pan out.
I just went through this process for the first time myself, just last night. Both my radio and my programming cable came from Banggood (China).
After a bit of struggling I got my systems communication smoothly. My configuration:
* Laptop: Windows 8.1 * Radio Baofeng UV-82
I did try using the USB cable driver that came with Windows and it did not work. I downloaded the drivers from the Miklor site and they also did not work. As a last resort I used the drivers from the mini-disc supplied with my cable. Again: No luck at all.
Then I realized that Windows was automatically updating the USB cable driver the instant I plugged in the cable.
I discovered this by drilling down deep within Device Manager and looking at the Date/Version of the installed driver. As soon as the cable was inserted (with or without radio connected), Windows upgraded the driver instantly (Fail).
The solution for me — and YMMV, of course — was to re-enter Device Manager and to click on the “Roll Back Driver” button, after assuring the O/S that this was in fact my intention the driver reverted to the one that /I/ had installed. Immediately thereafter everything was golden and CHIRP worked perfectly.
I confess that it took me close to an hour to realize, diagnose, and correct the problem but I got mine working.
Thereafter I went back to the CHIRP Wiki page with the hope of being able to edit in my Windows 8 approach (since Win8 isn’t specifically mentioned there). Alas, although it is a Wiki page, I found no way to edit it — despite having registered/authenticated.
Instead, I post this here, hoping it will help someone. I can provide more detailed info, even a step-by-step procedure, if someone with Write authority on the Wiki would publish it there.
Tom Maynard WZ9U
P.S. I am actually using the driver that came with my cable on the mini-disc. I'm sure the download from Miklor would also work, but once I had a working solution I opted not to experiment further. (If it ain't broke, right?)
Yes, It sounds like what you experienced is described in FAQ #2 at http://www.miklor.com/COM/UV_Drivers.php This is a very common issue.
The driver does not follow the cable. If the cable is moved to a different COM port, Windows will now load the newest driver it finds. Windows will now load the newest driver it finds, not 3.2.0.0 When this occurs, you will need to load Prolific driver 3.2.0.0 to the new USB slot or plug the cable back into its original USB slot.
Anyway, glad to hear you got it working John
From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Tom Maynard Sent: Saturday, December 06, 2014 1:37 PM To: Discussion of CHIRP Subject: Re: [chirp_users] HELP
On 06-Dec-14 09:15, Shon Edwards wrote:
This is a very good explanation and should work fine. I usually just use the "official" cables myself and have no problem, so this is another option in case things don't pan out.
I just went through this process for the first time myself, just last night. Both my radio and my programming cable came from Banggood (China).
After a bit of struggling I got my systems communication smoothly. My configuration:
* Laptop: Windows 8.1
* Radio Baofeng UV-82
I did try using the USB cable driver that came with Windows and it did not work. I downloaded the drivers from the Miklor site and they also did not work. As a last resort I used the drivers from the mini-disc supplied with my cable. Again: No luck at all.
Then I realized that Windows was automatically updating the USB cable driver the instant I plugged in the cable.
I discovered this by drilling down deep within Device Manager and looking at the Date/Version of the installed driver. As soon as the cable was inserted (with or without radio connected), Windows upgraded the driver instantly (Fail).
The solution for me - and YMMV, of course - was to re-enter Device Manager and to click on the "Roll Back Driver" button, after assuring the O/S that this was in fact my intention the driver reverted to the one that I had installed. Immediately thereafter everything was golden and CHIRP worked perfectly.
I confess that it took me close to an hour to realize, diagnose, and correct the problem but I got mine working.
Thereafter I went back to the CHIRP Wiki page with the hope of being able to edit in my Windows 8 approach (since Win8 isn't specifically mentioned there). Alas, although it is a Wiki page, I found no way to edit it - despite having registered/authenticated.
Instead, I post this here, hoping it will help someone. I can provide more detailed info, even a step-by-step procedure, if someone with Write authority on the Wiki would publish it there.
Tom Maynard WZ9U
P.S. I am actually using the driver that came with my cable on the mini-disc. I'm sure the download from Miklor would also work, but once I had a working solution I opted not to experiment further. (If it ain't broke, right?)
On 06-Dec-14 13:14, John LaMartina wrote:
Yes, It sounds like what you experienced is described in FAQ #2 at */_http://www.miklor.com/COM/UV_Drivers.php_/* This is a very common issue.
The driver does not follow the cable. If the cable is moved to a different COM port, Windows will now load the newest driver it finds.
Well, yes of course I had studied the linked page(s) quite closely, and followed them precisely.
But I never said anything about ‘drivers following cables.’ In fact I only ever used a single USB port in all my attempts.
What I actually said was that ‘Windows updates the driver the instant the cable is plugged in.’ Regardless of port, the user needs to roll back the driver (backlevel it), overriding Windows auto-update, in order to make the process work.
When this occurs, you will need to load Prolific driver 3.2.0.0 to the new USB slot
I disagree with you here, John. Plugging the cable into any slot /where you have not specifically rolled back the driver level/ will recreate the problem again. I know this for fact since it happened to me at least thrice last evening. (I tried the Miklor download drivers and failed, and the supplied 'factory' drivers twice -- one failure at the instant of diagnosis, and one success.)
Anyway, glad to hear you got it working
The Miklor information was ‘guidance’ but certainly not ‘directions’. With persistence, and a lifetime as a computer professional, I managed to figure it out in about an hour. A normal “computer layperson” might never arrive at that solution. I still firmly believe that the Wiki page should be updated — if only to include more current Windows 8/8.1 methods.
But, I’ll leave that to the admin. This particular “Wiki” isn’t “wik-able.”
73 de WZ9U
Hi Tom,
I don't have Windows 8.1 here so I can test it out myself. Are you not able to choose the older compatible driver in the 8.1 Device Manager like is shows in step 11?
Jim KC9HI
On Sat, Dec 6, 2014 at 1:36 PM, Tom Maynard tom.wz9u@gmail.com wrote:
On 06-Dec-14 09:15, Shon Edwards wrote:
This is a very good explanation and should work fine. I usually just use the "official" cables myself and have no problem, so this is another option in case things don't pan out.
I just went through this process for the first time myself, just last night. Both my radio and my programming cable came from Banggood (China).
After a bit of struggling I got my systems communication smoothly. My configuration:
Laptop: Windows 8.1 Radio Baofeng UV-82
I did try using the USB cable driver that came with Windows and it did not work. I downloaded the drivers from the Miklor site and they also did not work. As a last resort I used the drivers from the mini-disc supplied with my cable. Again: No luck at all.
Then I realized that Windows was automatically updating the USB cable driver the instant I plugged in the cable.
I discovered this by drilling down deep within Device Manager and looking at the Date/Version of the installed driver. As soon as the cable was inserted (with or without radio connected), Windows upgraded the driver instantly (Fail).
The solution for me — and YMMV, of course — was to re-enter Device Manager and to click on the “Roll Back Driver” button, after assuring the O/S that this was in fact my intention the driver reverted to the one that I had installed. Immediately thereafter everything was golden and CHIRP worked perfectly.
I confess that it took me close to an hour to realize, diagnose, and correct the problem but I got mine working.
Thereafter I went back to the CHIRP Wiki page with the hope of being able to edit in my Windows 8 approach (since Win8 isn’t specifically mentioned there). Alas, although it is a Wiki page, I found no way to edit it — despite having registered/authenticated.
Instead, I post this here, hoping it will help someone. I can provide more detailed info, even a step-by-step procedure, if someone with Write authority on the Wiki would publish it there.
Tom Maynard WZ9U
P.S. I am actually using the driver that came with my cable on the mini-disc. I'm sure the download from Miklor would also work, but once I had a working solution I opted not to experiment further. (If it ain't broke, right?)
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
1. Open Device Manager 2. Remove Old Com ports and USB devices: Proceed to step 2 of this tutorial http://www.digi.com/support/kbase/kbaseresultdetl?id=3308. 3. When that is done, still in Device manager, navigate to your problem USB cable (it should have a yellow exclamation mark on it) 4. Remove it, and then reinstall the driver 5. If that driver will still not work then: 6. Right click on it, and choose *update driver*. 7. Click *Browse my Computer...* 8. Click *Let me pick from a list...* 9. A list of all of the drivers should show. Choose the oldest Prolific driver on the list. I chose version 3.2.0 from 2007 10. Install it, and you're done!
If you are using PuTTy, note that when you connect, the COM port may not work as expected. What you should do, if you need to, is go into the Serial options in the main PuTTy window, and turn off flow control.
Everything should work right now[?].
Regards, John Kellas 403-762-2333
On Sat, Dec 6, 2014 at 12:55 PM, Jim Unroe rock.unroe@gmail.com wrote:
Hi Tom,
I don't have Windows 8.1 here so I can test it out myself. Are you not able to choose the older compatible driver in the 8.1 Device Manager like is shows in step 11?
Jim KC9HI
On Sat, Dec 6, 2014 at 1:36 PM, Tom Maynard tom.wz9u@gmail.com wrote:
On 06-Dec-14 09:15, Shon Edwards wrote:
This is a very good explanation and should work fine. I usually just use the "official" cables myself and have no problem, so this is another
option
in case things don't pan out.
I just went through this process for the first time myself, just last
night.
Both my radio and my programming cable came from Banggood (China).
After a bit of struggling I got my systems communication smoothly. My configuration:
Laptop: Windows 8.1 Radio Baofeng UV-82
I did try using the USB cable driver that came with Windows and it did
not
work. I downloaded the drivers from the Miklor site and they also did not work. As a last resort I used the drivers from the mini-disc supplied
with
my cable. Again: No luck at all.
Then I realized that Windows was automatically updating the USB cable
driver
the instant I plugged in the cable.
I discovered this by drilling down deep within Device Manager and
looking at
the Date/Version of the installed driver. As soon as the cable was
inserted
(with or without radio connected), Windows upgraded the driver instantly (Fail).
The solution for me — and YMMV, of course — was to re-enter Device
Manager
and to click on the “Roll Back Driver” button, after assuring the O/S
that
this was in fact my intention the driver reverted to the one that I had installed. Immediately thereafter everything was golden and CHIRP worked perfectly.
I confess that it took me close to an hour to realize, diagnose, and
correct
the problem but I got mine working.
Thereafter I went back to the CHIRP Wiki page with the hope of being
able to
edit in my Windows 8 approach (since Win8 isn’t specifically mentioned there). Alas, although it is a Wiki page, I found no way to edit it — despite having registered/authenticated.
Instead, I post this here, hoping it will help someone. I can provide
more
detailed info, even a step-by-step procedure, if someone with Write authority on the Wiki would publish it there.
Tom Maynard WZ9U
P.S. I am actually using the driver that came with my cable on the mini-disc. I'm sure the download from Miklor would also work, but once I had a working solution I opted not to experiment further. (If it ain't broke, right?)
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Hi I just upgraded my MAC from Lion 10.7 to OS XYosemite 10.10.4, everything with Chirp has been working great till I did the upgrade, does anyone have the “magic” solution? What needs to be added? New Drivers ? or ??
Thankful for help
Mats
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
I too went from Lion to Yosemite on my 2011 Macbook Pro. Biggest mistake I have made with any computer ever. I do not have an answer for you. When anybody finds an answer, it deserves a page of its own on Miklor.com. I have tried everything, I though I had it with this technique, it seemed to work for a while and then it just stopped working as well. But you can try it, good luck and let us know how it works for you:
Here is what I found. The driver is the issue with Yosemite. The built-in FTDI driver prevents the osx-pl2303 driver from loading. The fix (not for the faint of heart) is to do some black magic at the command line.
In Terminal, enter:
sudo nvram boot-args="kext-dev-mode=1"
This allows other (unsigned) drivers to load. The driver that works for me is the Lion driver from miklor.com.
Then manually load the driver (first time only, it will load automatically after that) with this command in Terminal:
sudo kextload /System/Library/Extensions/osx-pl2303.kext
This creates the device cu.PL2303-000012FD, be sure that is what you select in the CHIRP Radio dialog in the Port drop-down. Again in the Terminal, do "cd /dev", and then "ls" (without the quotes) to see that the cu.PL2303-000012FD driver is actually loaded.
On Sun, Jul 19, 2015 at 2:46 PM, Roos G Mats mats.g.roos@gmail.com wrote:
Hi I just upgraded my MAC from Lion 10.7 to OS XYosemite 10.10.4,
everything with Chirp has been working great till I did the upgrade, does anyone have the “magic” solution? What needs to be added? New Drivers ? or ??
Thankful for help
Mats
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Thanks PAT,
the problem is that I am a normal “deadly guy”, just a simple MAC user, not sure I understand what you teaching me :-)
Can you please, line by line explain ? Also, will it may work as the upgrade Yosemite ? is it of temporary nature or for ever ?
Mats
On Jul 19, 2015, at 5:04 PM, Pat Anderson anderson5420@gmail.com wrote:
I too went from Lion to Yosemite on my 2011 Macbook Pro. Biggest mistake I have made with any computer ever. I do not have an answer for you. When anybody finds an answer, it deserves a page of its own on Miklor.com. I have tried everything, I though I had it with this technique, it seemed to work for a while and then it just stopped working as well. But you can try it, good luck and let us know how it works for you:
Here is what I found. The driver is the issue with Yosemite. The built-in FTDI driver prevents the osx-pl2303 driver from loading. The fix (not for the faint of heart) is to do some black magic at the command line.
In Terminal, enter:
sudo nvram boot-args="kext-dev-mode=1" This allows other (unsigned) drivers to load. The driver that works for me is the Lion driver from miklor.com http://miklor.com/.
Then manually load the driver (first time only, it will load automatically after that) with this command in Terminal:
sudo kextload /System/Library/Extensions/osx-pl2303.kext This creates the device cu.PL2303-000012FD, be sure that is what you select in the CHIRP Radio dialog in the Port drop-down. Again in the Terminal, do "cd /dev", and then "ls" (without the quotes) to see that the cu.PL2303-000012FD driver is actually loaded.
On Sun, Jul 19, 2015 at 2:46 PM, Roos G Mats <mats.g.roos@gmail.com mailto:mats.g.roos@gmail.com> wrote:
Hi I just upgraded my MAC from Lion 10.7 to OS XYosemite 10.10.4, everything with Chirp has been working great till I did the upgrade, does anyone have the “magic” solution? What needs to be added? New Drivers ? or ??
Thankful for help
Mats
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
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 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 http://intrepid.danplanet.com/mailman/listinfo/chirp_users To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
If you have the ability to go back to Lion, I would do that ASAP! I had a Lion backup (SuperDuper) on an external USB drive, and foolishly did not retain it, instead I backed up my Yosemite installation. HUGE mistake. So I am cut off from going back.
I could explain if we were sitting down together at a table with the computer in front of us, but probably not via email. Basically, you need to be comfortable using the Terminal (In Finder: Applications | Utilities | Terminal.app). It is a command line interface, no graphical interface. You type (or better yet, copy and paste) commands, enter your password, say a magic incantation (just kidding but it doesn't hurt) and press return. If all goes well, the command will execute; if not, you risk causing all kinds of problems with your computer, which is why I say it is not for the faint at heart! You have been warned!
Assuming you have the Terminal open, copy this and paste it to the command prompt:
sudo nvram boot-args="kext-dev-mode=1"
The "sudo" makes you the superuser (administrator) and the command that follows allows unsigned drivers to be loaded.
Now you would install your driver. I used the Lion driver from Miklor.com and it worked at the beginning.
It was necessary to manually load the driver the first time with another command in Terminal (again, copy and paste):
sudo kextload /System/Library/Extensions/osx-pl2303.kext
It worked for a while, then although the driver continued to show up in CHIRP, it always returned the error message "The radio did not respond." Same radio, same cable, work fine on my 2006 white Macbook.
Like I say, if anybody gets CHIRP working reliably in Yosemite, they need to detail how on a Miklor page!
On Sun, Jul 19, 2015 at 3:10 PM, Roos G Mats mats.g.roos@gmail.com wrote:
Thanks PAT,
the problem is that I am a normal “deadly guy”, just a simple MAC user, not sure I understand what you teaching me :-)
Can you please, line by line explain ? Also, will it may work as the upgrade Yosemite ? is it of temporary nature or for ever ?
Mats
On Jul 19, 2015, at 5:04 PM, Pat Anderson anderson5420@gmail.com wrote:
I too went from Lion to Yosemite on my 2011 Macbook Pro. Biggest mistake I have made with any computer ever. I do not have an answer for you. When anybody finds an answer, it deserves a page of its own on Miklor.com. I have tried everything, I though I had it with this technique, it seemed to work for a while and then it just stopped working as well. But you can try it, good luck and let us know how it works for you:
Here is what I found. The driver is the issue with Yosemite. The built-in FTDI driver prevents the osx-pl2303 driver from loading. The fix (not for the faint of heart) is to do some black magic at the command line.
In Terminal, enter:
sudo nvram boot-args="kext-dev-mode=1"
This allows other (unsigned) drivers to load. The driver that works for me is the Lion driver from miklor.com.
Then manually load the driver (first time only, it will load automatically after that) with this command in Terminal:
sudo kextload /System/Library/Extensions/osx-pl2303.kext
This creates the device cu.PL2303-000012FD, be sure that is what you select in the CHIRP Radio dialog in the Port drop-down. Again in the Terminal, do "cd /dev", and then "ls" (without the quotes) to see that the cu.PL2303-000012FD driver is actually loaded.
On Sun, Jul 19, 2015 at 2:46 PM, Roos G Mats mats.g.roos@gmail.com wrote:
Hi I just upgraded my MAC from Lion 10.7 to OS XYosemite 10.10.4,
everything with Chirp has been working great till I did the upgrade, does anyone have the “magic” solution? What needs to be added? New Drivers ? or ??
Thankful for help
Mats
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users 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 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 To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
well, I am still on 10.7 here (my machine won't support any further upgrades). However, my issue is a bit different than yours. I am totally blind and use the voiceover screen reader. Guess what? chirp doesn't have a visible interface. I can see the app, but nothing in the app pane is visible to voiceover.
Now, I had previously requested that some small changes be made that would have made chirp accessible. However, it appears that one or more of the devs either couldn't, or wouldn't, make the attempt. I had previously posted links to tools and libraries that would have made this program accessible in both windows and OS X. unfortunately, I never did get a clear response on that (other than the lament about having to maintain separate code bases). SInce python is multi-platform, it stands to reason that the accessibility libraries and tools are also.
Now, this is not to disparage chirp or its developers. The program is important in that it does support a large number of radios (mostly). It is definitely a much needed software package, but it still needs changes.
For any of you who don't think there are that many visually impaired hams out there, you would be wrong. our numbers are growing. As the population ages, more and more end up with age related visual impairments and some of them are hams. so please do not dismiss us as a niche population (apple didn't and as a result, our population represents one of the largest user bases for iDevices).
Anyway, thats my say and I am standing by it.
-eric
On Jul 19, 2015, at 3:04 PM, Pat Anderson wrote:
I too went from Lion to Yosemite on my 2011 Macbook Pro. Biggest mistake I have made with any computer ever. I do not have an answer for you. When anybody finds an answer, it deserves a page of its own on Miklor.com. I have tried everything, I though I had it with this technique, it seemed to work for a while and then it just stopped working as well. But you can try it, good luck and let us know how it works for you:
Here is what I found. The driver is the issue with Yosemite. The built-in FTDI driver prevents the osx-pl2303 driver from loading. The fix (not for the faint of heart) is to do some black magic at the command line.
In Terminal, enter:
sudo nvram boot-args="kext-dev-mode=1" This allows other (unsigned) drivers to load. The driver that works for me is the Lion driver from miklor.com.
Then manually load the driver (first time only, it will load automatically after that) with this command in Terminal:
sudo kextload /System/Library/Extensions/osx-pl2303.kext This creates the device cu.PL2303-000012FD, be sure that is what you select in the CHIRP Radio dialog in the Port drop-down. Again in the Terminal, do "cd /dev", and then "ls" (without the quotes) to see that the cu.PL2303-000012FD driver is actually loaded.
On Sun, Jul 19, 2015 at 2:46 PM, Roos G Mats mats.g.roos@gmail.com wrote:
Hi I just upgraded my MAC from Lion 10.7 to OS XYosemite 10.10.4, everything with Chirp has been working great till I did the upgrade, does anyone have the “magic” solution? What needs to be added? New Drivers ? or ??
Thankful for help
Mats
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users 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 To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
participants (9)
-
Eric Oyen -
Jim Russell -
Jim Unroe -
John Kellas -
John LaMartina -
Pat Anderson -
Roos G Mats -
Shon Edwards -
Tom Maynard