Re: [chirp_users] Mac user - inconsistent ability to contact radio
OK, after some more playing around, I think in my case the problem is indeed mechanical.
I have 2 cables. The one that came with the radio and a Baofeng branded one I bought when I couldn't get the first one to work with the Mac.
I now think the original issue was not having the right Prolific chip drivers, but as I then changed the cable as well, *that* became the problem.
Going back to my original cable, and it works every time. (Except after first plugging in - seems that until Chirp has tried to communicate the ports are in the wrong configuration, and it opens up the mic.)
So my - so far - way of working is:
Plug cable into USB Launch Chirp Try to download - this will fail Plug cable into radio (while it is off) and then turn radio on Now download (or upload, I guess - not tried yet) seems to work fine.
I can turn the radio off/on and it will still load.
I had attached pics of the 2 cables to show the difference but the list rejected the email :( Basically, one of them has better clearance on the casing around the sockets - and that's the one that works.
On 24 October 2015 at 16:33, Paul Slootweg paul.slootweg@gmail.com wrote:
OK, after some more playing around, I think in my case the problem is indeed mechanical.
I have 2 cables. The one that came with the radio and a Baofeng branded one I bought when I couldn't get the first one to work with the Mac.
I now think the original issue was not having the right Prolific chip drivers, but as I then changed the cable as well, *that* became the problem.
Going back to my original cable, and it works every time. (Except after first plugging in - seems that until Chirp has tried to communicate the ports are in the wrong configuration, and it opens up the mic.)
So my - so far - way of working is:
Plug cable into USB Launch Chirp Try to download - this will fail Plug cable into radio (while it is off) and then turn radio on Now download (or upload, I guess - not tried yet) seems to work fine.
I can turn the radio off/on and it will still load.
I have attached a couple of pics that hopefully show the problem. (The working one is the Front/Left in these pics.)
Paul
On 24 October 2015 at 15:07, Kearney mbk7@comcast.net wrote:
I've had a similar issue with "Error: can't find or read the radio". Sorry, I have no other suggestions. I am working on a 'cheat sheet' to help avoid some mis-steps with CHIRP for first time users in our club so I am curios to find out what causes your problems.
Mike KG7KIQ
----- Original Message ----- From: paul.slootweg@gmail.com To: "Discussion of CHIRP" chirp_users@intrepid.danplanet.com Sent: Saturday, October 24, 2015 6:46 AM Subject: Re: [chirp_users] Mac user - inconsistent ability to contact radio
Done that too - if it worked.
The issue is connectivity to the radio.
On 24 Oct 2015, at 14:35, Kearney mbk7@comcast.net wrote:
Have you tried to download to a new file? ----- Original Message ----- From: paul.slootweg@gmail.com To: "Discussion of CHIRP" chirp_users@intrepid.danplanet.com Sent: Saturday, October 24, 2015 6:21 AM Subject: Re: [chirp_users] Mac user - inconsistent ability to contact radio
Nope. Same radio. (One of the times that download did work!)
Paul
On 24 Oct 2015, at 14:12, Kearney mbk7@comcast.net wrote:
Paul, was your original img. file created on a different radio?
Mike KG7KIQ
----- Original Message ----- From: "Paul Slootweg" paul.slootweg@gmail.com To: "Discussion of CHIRP" chirp_users@intrepid.danplanet.com Sent: Friday, October 23, 2015 1:15 AM Subject: Re: [chirp_users] Mac user - inconsistent ability to contact radio
> I would have assumed that if the was a compatibility problem, then the > cable/drivers would work 'never', not 'sometimes'. > > As for FTDI cables - unobtanium in the UK. > > Paul > >> On 21 October 2015 at 17:00, Jim Unroe rock.unroe@gmail.com wrote: >> On Wed, Oct 21, 2015 at 9:43 AM, Paul Slootweg >> paul.slootweg@gmail.com >> wrote: >>> I have the latest of everything installed, the Prolific drivers show >>> up as started in the Console, and the USB serial device shows up, >>> but >>> I can rarely download (never mind upload.) >>> Radio is UV-5RA >>> >>> Am I missing something? >>> >>> Paul >> >> Paul, >> >> When it comes to Prolific drivers, you don't want the latest. They >> are >> incompatible with the unauthorized Prolific chip copies that are in >> most programming cables (including the "genuine" Baofeng programming >> cable). Try the generic drivers on the MacOS_Tips page or purchase >> the >> 3rd party driver. >> >> http://chirp.danplanet.com/projects/chirp/wiki/MacOS_Tips >> >> https://www.mac-usb-serial.com/ >> >> Or to avoid the hassle of finding and installing a compatible driver, >> get a programming cable with the FTDI chip. >> >> http://www.amazon.com/gp/product/B00HUB0ONK >> >> Jim KC9HI >> _______________________________________________ >> 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
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
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
I have three sub-generic USB programming cables for my Baofeng. Two of three operate in this way, where I have to try to program the (turned off) radio first, and then turn on the radio. I believe this is due to the ultra-crappiness of the cables.
The one cable that doesn't do this, I can program normally, and it operates like it should (does not open TX when plugging in the cable).
Luckily, we don't need to program our radios constantly. This is just a minor annoyance.
(chirp + osx + baofeng)
On 10/29/15 8:25 AM, Paul Slootweg wrote:
OK, after some more playing around, I think in my case the problem is indeed mechanical.
I have 2 cables. The one that came with the radio and a Baofeng branded one I bought when I couldn't get the first one to work with the Mac.
I now think the original issue was not having the right Prolific chip drivers, but as I then changed the cable as well, *that* became the problem.
Going back to my original cable, and it works every time. (Except after first plugging in - seems that until Chirp has tried to communicate the ports are in the wrong configuration, and it opens up the mic.)
So my - so far - way of working is:
Plug cable into USB Launch Chirp Try to download - this will fail Plug cable into radio (while it is off) and then turn radio on Now download (or upload, I guess - not tried yet) seems to work fine.
More often than not, if the radio transmits when the programming cable is plugged in, the programming has a conterfeit Prolific type USB-to-TTL chip and an incompatible driver is installed. Many think they can avoid this by purchasing the "genuine" Baofeng labeled programming cable. Not so. It is made with same counterfeit chip as the generic cables are. From what I have seen in the last 3.5 years, this is the #1 cause of problems for Baofeng radios users. One of the most common indicators of an incompatible driver is that the radio will transmit when the programming cable is plugged in.
This issue can usually be corrected by one or more of the following...
- Windows users can download, install and select the older v3.2.0.0 Prolific driver. - Mac OS X users can install a generic driver or purchase a 3rd party driver - Use Linux or the CHIRP Live CD - Replace the programming cable with one having the FTDI chip - Modify the programming cable so it has a CP2102 chip or FTDI chip
If you can't solve the transmitting problem with one of the above solutions, Baofeng users (and most likely others) can at least program a channel that has TX disabled and then select it when the radio is being programmed.
The #2 most common problem that I have seen is not getting the programming cable fully plugged into the radio's socket. Interference between the plugs plastic shell and the case if the most common cause. Trimming the plug's shell can reduce this interference. There are other causes of this as well. Variations in length of the pins on the cheaper cables. Variations of the location of the socket inside the case of the cheaper radios. And sometimes it is the user just failed to push the plug in all the way.
Jim KC9HI
On Thu, Oct 29, 2015 at 9:57 AM, Drew from Zhrodague drewzhrodague@zhrodague.net wrote:
I have three sub-generic USB programming cables for my Baofeng. Two ofthree operate in this way, where I have to try to program the (turned off) radio first, and then turn on the radio. I believe this is due to the ultra-crappiness of the cables.
The one cable that doesn't do this, I can program normally, and itoperates like it should (does not open TX when plugging in the cable).
Luckily, we don't need to program our radios constantly. This is just aminor annoyance.
(chirp + osx + baofeng)On 10/29/15 8:25 AM, Paul Slootweg wrote:
OK, after some more playing around, I think in my case the problem is indeed mechanical.
I have 2 cables. The one that came with the radio and a Baofeng branded one I bought when I couldn't get the first one to work with the Mac.
I now think the original issue was not having the right Prolific chip drivers, but as I then changed the cable as well, *that* became the problem.
Going back to my original cable, and it works every time. (Except after first plugging in - seems that until Chirp has tried to communicate the ports are in the wrong configuration, and it opens up the mic.)
So my - so far - way of working is:
Plug cable into USB Launch Chirp Try to download - this will fail Plug cable into radio (while it is off) and then turn radio on Now download (or upload, I guess - not tried yet) seems to work fine.
--
Drew from Zhrodague post-apocalyptic ad-hoc industrialist drew@zhrodague.net _______________________________________________ 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
While this is true, I do have the correct driver installed for OSX, and still have two cables that work the same (TX on plug-in), and one cable that does not have this behavior. Again, luckily, I haven't had to re-program my baofengs in a while. This is more of an annoyance than an actual problem for me. All three cables look exactly the same, except the 'working' cable has a sticker on it.
Same deal with these two cables when using Linux - I suspect that these cables are just poorly made, improperly wired, or even cast-offs from the factory that still somehow made it onto Amazon (or EBay).
(I am a very happy CHIRP user, and hope to help work out TS-480 and IC-7100 issues)
On 10/29/15 12:32 PM, Jim Unroe wrote:
More often than not, if the radio transmits when the programming cable is plugged in, the programming has a conterfeit Prolific type USB-to-TTL chip and an incompatible driver is installed. Many think they can avoid this by purchasing the "genuine" Baofeng labeled programming cable. Not so. It is made with same counterfeit chip as the generic cables are. From what I have seen in the last 3.5 years, this is the #1 cause of problems for Baofeng radios users. One of the most common indicators of an incompatible driver is that the radio will transmit when the programming cable is plugged in.
This issue can usually be corrected by one or more of the following...
- Windows users can download, install and select the older v3.2.0.0
Prolific driver.
- Mac OS X users can install a generic driver or purchase a 3rd party driver
- Use Linux or the CHIRP Live CD
- Replace the programming cable with one having the FTDI chip
- Modify the programming cable so it has a CP2102 chip or FTDI chip
If you can't solve the transmitting problem with one of the above solutions, Baofeng users (and most likely others) can at least program a channel that has TX disabled and then select it when the radio is being programmed.
The #2 most common problem that I have seen is not getting the programming cable fully plugged into the radio's socket. Interference between the plugs plastic shell and the case if the most common cause. Trimming the plug's shell can reduce this interference. There are other causes of this as well. Variations in length of the pins on the cheaper cables. Variations of the location of the socket inside the case of the cheaper radios. And sometimes it is the user just failed to push the plug in all the way.
Jim KC9HI
On Thu, Oct 29, 2015 at 9:57 AM, Drew from Zhrodague drewzhrodague@zhrodague.net wrote:
I have three sub-generic USB programming cables for my Baofeng. Two ofthree operate in this way, where I have to try to program the (turned off) radio first, and then turn on the radio. I believe this is due to the ultra-crappiness of the cables.
The one cable that doesn't do this, I can program normally, and itoperates like it should (does not open TX when plugging in the cable).
Luckily, we don't need to program our radios constantly. This is just aminor annoyance.
(chirp + osx + baofeng)On 10/29/15 8:25 AM, Paul Slootweg wrote:
OK, after some more playing around, I think in my case the problem is indeed mechanical.
I have 2 cables. The one that came with the radio and a Baofeng branded one I bought when I couldn't get the first one to work with the Mac.
I now think the original issue was not having the right Prolific chip drivers, but as I then changed the cable as well, *that* became the problem.
Going back to my original cable, and it works every time. (Except after first plugging in - seems that until Chirp has tried to communicate the ports are in the wrong configuration, and it opens up the mic.)
So my - so far - way of working is:
Plug cable into USB Launch Chirp Try to download - this will fail Plug cable into radio (while it is off) and then turn radio on Now download (or upload, I guess - not tried yet) seems to work fine.
--
Drew from Zhrodague post-apocalyptic ad-hoc industrialist drew@zhrodague.net _______________________________________________ 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 (3)
-
Drew from Zhrodague -
Jim Unroe -
Paul Slootweg