[chirp_users] UV5R programming problems
I know this is a common problem but I have tried all the "usual" things with no success. I am on my second programming cable after the first one just didn't get recognised as a USB device, and first attempt I was able to download the contents of my radio. Since then however it's not worked again.
The cable works OK and the drivers are loaded, as confirmed by opening a serial terminal, linking the TX and RX pins and observing loopback. The radio goes into TX when powered on with the cable attached and some vicious connector trimming doesn't help - I am sure it is going all the way in. Following the order in the Chirp pop-up instructions (cable is already connected to PC and correct serial port selected, radio off, connect cable, radio on with volume right up, check no activity, click OK) doesn't help. The radio goes into TX as soon as it's booted and after a few seconds I get "Radio did not respond".
The radio does *not* go into TX if I have that port open in a serial terminal when I turn the radio on, and presumably if Chirp opened the port when the instructional message is displayed (before the radio is turned on) but still waited for the user to click OK before trying to communicate all would work?
I think that the one time it did work it might have been TX-ing and I just got lucky that it didn't interfere with communications - I do remember some interference on my monitor which I now know happens when the radio transmits.
Anyone got any good ideas? Given that the radio doesn't go into transmit mode when the serial port is open I can't see how it can be bad cable / poor connections.
This is on Linux Mate 1.12.1, with the current daily Chirp build. My user is in the dialout group and has serial port access.
Thanks Richard
Where are you?
On 29 October 2016 at 07:20 Richard richard.cs@gmail.com wrote:
I know this is a common problem but I have tried all the "usual" things with no success. I am on my second programming cable after the first one just didn't get recognised as a USB device, and first attempt I was able to download the contents of my radio. Since then however it's not worked again.
The cable works OK and the drivers are loaded, as confirmed by opening a serial terminal, linking the TX and RX pins and observing loopback. The radio goes into TX when powered on with the cable attached and some vicious connector trimming doesn't help - I am sure it is going all the way in. Following the order in the Chirp pop-up instructions (cable is already connected to PC and correct serial port selected, radio off, connect cable, radio on with volume right up, check no activity, click OK) doesn't help. The radio goes into TX as soon as it's booted and after a few seconds I get "Radio did not respond".
The radio does *not* go into TX if I have that port open in a serial terminal when I turn the radio on, and presumably if Chirp opened the port when the instructional message is displayed (before the radio is turned on) but still waited for the user to click OK before trying to communicate all would work?
I think that the one time it did work it might have been TX-ing and I just got lucky that it didn't interfere with communications - I do remember some interference on my monitor which I now know happens when the radio transmits.
Anyone got any good ideas? Given that the radio doesn't go into transmit mode when the serial port is open I can't see how it can be bad cable / poor connections.
This is on Linux Mate 1.12.1, with the current daily Chirp build. My user is in the dialout group and has serial port access.
Thanks Richard _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Geographically?
Southampton, UK.
On 29 October 2016 at 14:27, Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote:
Where are you?
On 29 October 2016 at 07:20 Richard richard.cs@gmail.com wrote:
I know this is a common problem but I have tried all the "usual" things with no success. I am on my second programming cable after the first one just didn't get recognised as a USB device, and first attempt I was able
to
download the contents of my radio. Since then however it's not worked
again.
The cable works OK and the drivers are loaded, as confirmed by opening a serial terminal, linking the TX and RX pins and observing loopback. The radio goes into TX when powered on with the cable attached and some
vicious
connector trimming doesn't help - I am sure it is going all the way in. Following the order in the Chirp pop-up instructions (cable is already connected to PC and correct serial port selected, radio off, connect
cable,
radio on with volume right up, check no activity, click OK) doesn't help. The radio goes into TX as soon as it's booted and after a few seconds I
get
"Radio did not respond".
The radio does *not* go into TX if I have that port open in a serial terminal when I turn the radio on, and presumably if Chirp opened the
port
when the instructional message is displayed (before the radio is turned
on)
but still waited for the user to click OK before trying to communicate
all
would work?
I think that the one time it did work it might have been TX-ing and I
just
got lucky that it didn't interfere with communications - I do remember
some
interference on my monitor which I now know happens when the radio transmits.
Anyone got any good ideas? Given that the radio doesn't go into transmit mode when the serial port is open I can't see how it can be bad cable / poor connections.
This is on Linux Mate 1.12.1, with the current daily Chirp build. My user is in the dialout group and has serial port access.
Thanks Richard _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net 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 Richard at richard.cs@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
Is that... IFF as in SIF/IFF ?? Dave K1SIW
Sent from my iPhone DSP
On Oct 29, 2016, at 5:53 PM, Richard richard.cs@gmail.com wrote:
Geographically?
Southampton, UK.
On 29 October 2016 at 14:27, Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote: Where are you?
On 29 October 2016 at 07:20 Richard richard.cs@gmail.com wrote:
I know this is a common problem but I have tried all the "usual" things with no success. I am on my second programming cable after the first one just didn't get recognised as a USB device, and first attempt I was able to download the contents of my radio. Since then however it's not worked again.
The cable works OK and the drivers are loaded, as confirmed by opening a serial terminal, linking the TX and RX pins and observing loopback. The radio goes into TX when powered on with the cable attached and some vicious connector trimming doesn't help - I am sure it is going all the way in. Following the order in the Chirp pop-up instructions (cable is already connected to PC and correct serial port selected, radio off, connect cable, radio on with volume right up, check no activity, click OK) doesn't help. The radio goes into TX as soon as it's booted and after a few seconds I get "Radio did not respond".
The radio does *not* go into TX if I have that port open in a serial terminal when I turn the radio on, and presumably if Chirp opened the port when the instructional message is displayed (before the radio is turned on) but still waited for the user to click OK before trying to communicate all would work?
I think that the one time it did work it might have been TX-ing and I just got lucky that it didn't interfere with communications - I do remember some interference on my monitor which I now know happens when the radio transmits.
Anyone got any good ideas? Given that the radio doesn't go into transmit mode when the serial port is open I can't see how it can be bad cable / poor connections.
This is on Linux Mate 1.12.1, with the current daily Chirp build. My user is in the dialout group and has serial port access.
Thanks Richard _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net 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 Richard at richard.cs@gmail.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 Dr. Dave Palmer at dmdfacp@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
No SIF. I'm not at all selective.
On 29 October 2016 at 17:56 "dmdfacp@gmail.com" dmdfacp@gmail.com wrote:
Is that... IFF as in SIF/IFF ?? Dave K1SIW
Sent from my iPhone DSP
On Oct 29, 2016, at 5:53 PM, Richard richard.cs@gmail.com wrote:
Geographically?
Southampton, UK.
On 29 October 2016 at 14:27, Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote: Where are you?
On 29 October 2016 at 07:20 Richard richard.cs@gmail.com wrote:
I know this is a common problem but I have tried all the "usual" things with no success. I am on my second programming cable after the first one just didn't get recognised as a USB device, and first attempt I was able to download the contents of my radio. Since then however it's not worked again.
The cable works OK and the drivers are loaded, as confirmed by opening a serial terminal, linking the TX and RX pins and observing loopback. The radio goes into TX when powered on with the cable attached and some vicious connector trimming doesn't help - I am sure it is going all the way in. Following the order in the Chirp pop-up instructions (cable is already connected to PC and correct serial port selected, radio off, connect cable, radio on with volume right up, check no activity, click OK) doesn't help. The radio goes into TX as soon as it's booted and after a few seconds I get "Radio did not respond".
The radio does *not* go into TX if I have that port open in a serial terminal when I turn the radio on, and presumably if Chirp opened the port when the instructional message is displayed (before the radio is turned on) but still waited for the user to click OK before trying to communicate all would work?
I think that the one time it did work it might have been TX-ing and I just got lucky that it didn't interfere with communications - I do remember some interference on my monitor which I now know happens when the radio transmits.
Anyone got any good ideas? Given that the radio doesn't go into transmit mode when the serial port is open I can't see how it can be bad cable / poor connections.
This is on Linux Mate 1.12.1, with the current daily Chirp build. My user is in the dialout group and has serial port access.
Thanks Richard _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net 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 Richard at richard.cs@gmail.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 Dr. Dave Palmer at dmdfacp@gmail.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 Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Hi Richard,
Do you want to try another radio and/or cable? I work overlooking Segensworth roundabout and am more than happy to help if I can.
73
Neil M6LPI
sent from my Galaxy S7 Edge - Powered by Percy the purple pig.
On 29 Oct 2016 22:54, "Richard" richard.cs@gmail.com wrote:
Geographically?
Southampton, UK.
On 29 October 2016 at 14:27, Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote:
Where are you?
On 29 October 2016 at 07:20 Richard richard.cs@gmail.com wrote:
I know this is a common problem but I have tried all the "usual" things with no success. I am on my second programming cable after the first one just didn't get recognised as a USB device, and first attempt I was
able to
download the contents of my radio. Since then however it's not worked
again.
The cable works OK and the drivers are loaded, as confirmed by opening a serial terminal, linking the TX and RX pins and observing loopback. The radio goes into TX when powered on with the cable attached and some
vicious
connector trimming doesn't help - I am sure it is going all the way in. Following the order in the Chirp pop-up instructions (cable is already connected to PC and correct serial port selected, radio off, connect
cable,
radio on with volume right up, check no activity, click OK) doesn't
help.
The radio goes into TX as soon as it's booted and after a few seconds I
get
"Radio did not respond".
The radio does *not* go into TX if I have that port open in a serial terminal when I turn the radio on, and presumably if Chirp opened the
port
when the instructional message is displayed (before the radio is turned
on)
but still waited for the user to click OK before trying to communicate
all
would work?
I think that the one time it did work it might have been TX-ing and I
just
got lucky that it didn't interfere with communications - I do remember
some
interference on my monitor which I now know happens when the radio transmits.
Anyone got any good ideas? Given that the radio doesn't go into transmit mode when the serial port is open I can't see how it can be bad cable / poor connections.
This is on Linux Mate 1.12.1, with the current daily Chirp build. My
user
is in the dialout group and has serial port access.
Thanks Richard _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrep
id.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Richard at richard.cs@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrep id.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Neil Stone at neil.stone@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
Hi Neil,
Thanks for the offer. You're some distance from me but I may take you up if I get really stuck. Could I ask where you bought yours from? When I look I only see cheap cables, even the higher-priced ones are the same cheap cables.
At the moment I think the symptoms probably point elsewhere - given that if I open GtkTerm the radio doesn't go into TX like it does with Chirp, and that I can show characters being looped-back.
Richard
On 29 October 2016 at 23:01, Neil Stone neil.stone@gmail.com wrote:
Hi Richard,
Do you want to try another radio and/or cable? I work overlooking Segensworth roundabout and am more than happy to help if I can.
73
Neil M6LPI
sent from my Galaxy S7 Edge - Powered by Percy the purple pig.
On 29 Oct 2016 22:54, "Richard" richard.cs@gmail.com wrote:
Geographically?
Southampton, UK.
On 29 October 2016 at 14:27, Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote:
Where are you?
On 29 October 2016 at 07:20 Richard richard.cs@gmail.com wrote:
I know this is a common problem but I have tried all the "usual" things with no success. I am on my second programming cable after the first
one
just didn't get recognised as a USB device, and first attempt I was
able to
download the contents of my radio. Since then however it's not worked
again.
The cable works OK and the drivers are loaded, as confirmed by opening
a
serial terminal, linking the TX and RX pins and observing loopback. The radio goes into TX when powered on with the cable attached and some
vicious
connector trimming doesn't help - I am sure it is going all the way in. Following the order in the Chirp pop-up instructions (cable is already connected to PC and correct serial port selected, radio off, connect
cable,
radio on with volume right up, check no activity, click OK) doesn't
help.
The radio goes into TX as soon as it's booted and after a few seconds
I get
"Radio did not respond".
The radio does *not* go into TX if I have that port open in a serial terminal when I turn the radio on, and presumably if Chirp opened the
port
when the instructional message is displayed (before the radio is
turned on)
but still waited for the user to click OK before trying to communicate
all
would work?
I think that the one time it did work it might have been TX-ing and I
just
got lucky that it didn't interfere with communications - I do remember
some
interference on my monitor which I now know happens when the radio transmits.
Anyone got any good ideas? Given that the radio doesn't go into
transmit
mode when the serial port is open I can't see how it can be bad cable / poor connections.
This is on Linux Mate 1.12.1, with the current daily Chirp build. My
user
is in the dialout group and has serial port access.
Thanks Richard _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrep
id.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Richard at richard.cs@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrep id.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Neil Stone at neil.stone@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrep id.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Richard at richard.cs@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
OK. Reason I ask, is that it is often easier for someone else to pay a visit with their equipment andhelp to sort a problem. Your post appeared to have nothing to give away even your country.
On 29 October 2016 at 17:53 Richard richard.cs@gmail.com wrote:
Geographically?
Southampton, UK.
On 29 October 2016 at 14:27, Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote:
Where are you?
I am just starting out with my radio, I had this problem and I did not have my radio in frequency mode. Thank You Robert
On Saturday, October 29, 2016 4:54 PM, Richard richard.cs@gmail.com wrote:
Geographically?
Southampton, UK.
On 29 October 2016 at 14:27, Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote:
Where are you?
On 29 October 2016 at 07:20 Richard richard.cs@gmail.com wrote:
I know this is a common problem but I have tried all the "usual" things with no success. I am on my second programming cable after the first one just didn't get recognised as a USB device, and first attempt I was able to download the contents of my radio. Since then however it's not worked again.
The cable works OK and the drivers are loaded, as confirmed by opening a serial terminal, linking the TX and RX pins and observing loopback. The radio goes into TX when powered on with the cable attached and some vicious connector trimming doesn't help - I am sure it is going all the way in. Following the order in the Chirp pop-up instructions (cable is already connected to PC and correct serial port selected, radio off, connect cable, radio on with volume right up, check no activity, click OK) doesn't help. The radio goes into TX as soon as it's booted and after a few seconds I get "Radio did not respond".
The radio does *not* go into TX if I have that port open in a serial terminal when I turn the radio on, and presumably if Chirp opened the port when the instructional message is displayed (before the radio is turned on) but still waited for the user to click OK before trying to communicate all would work?
I think that the one time it did work it might have been TX-ing and I just got lucky that it didn't interfere with communications - I do remember some interference on my monitor which I now know happens when the radio transmits.
Anyone got any good ideas? Given that the radio doesn't go into transmit mode when the serial port is open I can't see how it can be bad cable / poor connections.
This is on Linux Mate 1.12.1, with the current daily Chirp build. My user is in the dialout group and has serial port access.
Thanks Richard ______________________________ _________________ chirp_users mailing list chirp_users@intrepid. danplanet.com http://intrepid.danplanet.com/ mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net 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 Richard at richard.cs@gmail.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 rbairdjr59@yahoo.com at rbairdjr59@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Sat, Oct 29, 2016 at 10:32 PM, Robert Baird via chirp_users chirp_users@intrepid.danplanet.com wrote:
I am just starting out with my radio, I had this problem and I did not have my radio in frequency mode. Thank You Robert
When programming a UV-5R manually using the keypad, the radio must be in VFO (frequency) mode with the top (A) display line selected. It doesn't matter which mode the radio is in or which display line is selected when programming with a computer.
Jim KC9HI
I used the instructions at miklor.com and made my own cable. Much cheaper than store bought and it works every single time.
Chris KM4PUR
On Oct 29, 2016 10:46 PM, "Jim Unroe" rock.unroe@gmail.com wrote:
On Sat, Oct 29, 2016 at 10:32 PM, Robert Baird via chirp_users chirp_users@intrepid.danplanet.com wrote:
I am just starting out with my radio, I had this problem and I did not
have
my radio in frequency mode. Thank You Robert
When programming a UV-5R manually using the keypad, the radio must be in VFO (frequency) mode with the top (A) display line selected. It doesn't matter which mode the radio is in or which display line is selected when programming with a computer.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chris at chrispetry1971@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
Thanks all,
Bug 4165 ( http://chirp.danplanet.com/issues/4165 ) sounds a lot like my problem and explains all the behaviour I have observed. At some point I will try prodding the DTR line and see if that is what puts the radio into transmit which would pretty much confirm it. Only thing is that I didn't think the DTR line was connected in my cable, though it could still be an issue of default states of an uninitialised port (with this USB-serial device and driver anyway). What is interesting is that the PTT /RXD line is grounded for PTT so sending a logic-zero is inherently equivalent to pressing PTT, I guess it's just normally of too short duration for the radio to respond to it. That would mean that if the PC-TXD-->Radio-RXD line defaults to low when the port isn't open (as opposed to high OR tristate) then it is exactly equivalent to holding PTT. Or have I missed something here?
It's useful to know that RTSYSTEMS and Wouxon cables behave. I have the guts of the first one I bought, I could use that to make a new cable up. Has anyone used the version which level-shifts RS232 levels with two transistors rather than using a TTL-level USB-serial board? This kind of thing: http://www.hamradio.in/circuits/images/baofeng/programmer.jpg
Cheers Richard
On 30 October 2016 at 12:44, Chris Petry chrispetry1971@gmail.com wrote:
I used the instructions at miklor.com and made my own cable. Much cheaper than store bought and it works every single time.
Chris KM4PUR
On Oct 29, 2016 10:46 PM, "Jim Unroe" rock.unroe@gmail.com wrote:
On Sat, Oct 29, 2016 at 10:32 PM, Robert Baird via chirp_users chirp_users@intrepid.danplanet.com wrote:
I am just starting out with my radio, I had this problem and I did not
have
my radio in frequency mode. Thank You Robert
When programming a UV-5R manually using the keypad, the radio must be in VFO (frequency) mode with the top (A) display line selected. It doesn't matter which mode the radio is in or which display line is selected when programming with a computer.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chris at chrispetry1971@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrep id.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Richard at richard.cs@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
Anyone got any good ideas? Given that the radio doesn't go into transmit mode when the serial port is open I can't see how it can be bad cable / poor connections.
Richard,
I have never had this issue (yet) with any of my Linux distros. However it seems that you are not alone. A patch was recently submitted for what seems to be a similar issue. You can review it here.
http://chirp.danplanet.com/issues/4165
Jim KC9HI
What cable is being used?
I had issues with the Baofeng Tech cable on a UV82-HP within the last 6 months. I trimmed the cable to insure a good fit etc. Finally I tried my Wouxon cable that I also had and it worked like a charm. Since the HT I was trying to program was a gift for my granddaughter I immediately ordered another Wouxon cable to give to her. It works on the Kenwood's and other like radios with the same type connections.
So I threw away both Baofeng cables and stick with something I know works.
Ken KC9QV
ARRL Accredited Volunteer Examiner MRAC Accredited Volunteer Examiner Alger County Michigan ARES AEC Munising, MI (Spring, Summer & Fall) Grid Square EN66og South Milwaukee, WI (Winter) Grid Square EN62bv Member of AARC, HARA, LARS, MAARS, SMARC & ARRL
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Jim Unroe Sent: Saturday, October 29, 2016 5:49 PM To: Discussion of CHIRP Subject: Re: [chirp_users] UV5R programming problems
Anyone got any good ideas? Given that the radio doesn't go into transmit mode when the serial port is open I can't see how it can be bad cable / poor connections.
Richard,
I have never had this issue (yet) with any of my Linux distros. However it seems that you are not alone. A patch was recently submitted for what seems to be a similar issue. You can review it here.
http://chirp.danplanet.com/issues/4165
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to krugaber@gmail.com at krugaber@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
If you want a cable that will always work get them from RTSYSTEMS. I have no interests in their company.
Jock Soutar KC6IIH Sent via Samsung Galaxy S7 on AT&T 4G LTE Smartphone
On Saturday, October 29, 2016 Ken Rugaber (KC9QV) krugaber@gmail.com wrote: What cable is being used?
I had issues with the Baofeng Tech cable on a UV82-HP within the last 6 months. I trimmed the cable to insure a good fit etc. Finally I tried my Wouxon cable that I also had and it worked like a charm. Since the HT I was trying to program was a gift for my granddaughter I immediately ordered another Wouxon cable to give to her. It works on the Kenwood's and other like radios with the same type connections.
So I threw away both Baofeng cables and stick with something I know works.
Ken KC9QV
ARRL Accredited Volunteer Examiner MRAC Accredited Volunteer Examiner Alger County Michigan ARES AEC Munising, MI (Spring, Summer & Fall) Grid Square EN66og South Milwaukee, WI (Winter) Grid Square EN62bv Member of AARC, HARA, LARS, MAARS, SMARC & ARRL
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Jim Unroe Sent: Saturday, October 29, 2016 5:49 PM To: Discussion of CHIRP Subject: Re: [chirp_users] UV5R programming problems
Anyone got any good ideas? Given that the radio doesn't go into transmit mode when the serial port is open I can't see how it can be bad cable / poor connections.
Richard,
I have never had this issue (yet) with any of my Linux distros. However it seems that you are not alone. A patch was recently submitted for what seems to be a similar issue. You can review it here.
http://chirp.danplanet.com/issues/4165
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to krugaber@gmail.com at krugaber@gmail.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 Jock at kc6iih@aol.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Jock Soutar KC6IIH Sent via Samsung Galaxy S7 on AT&T 4G LTE Smartphone
On Saturday, October 29, 2016 Jock via chirp_users chirp_users@intrepid.danplanet.com wrote:
If you want a cable that will always work get them from RTSYSTEMS. I have no interests in their company.
Jock Soutar KC6IIH Sent via Samsung Galaxy S7 on AT&T 4G LTE Smartphone
On Saturday, October 29, 2016 Ken Rugaber (KC9QV) krugaber@gmail.com wrote: What cable is being used?
I had issues with the Baofeng Tech cable on a UV82-HP within the last 6 months. I trimmed the cable to insure a good fit etc. Finally I tried my Wouxon cable that I also had and it worked like a charm. Since the HT I was trying to program was a gift for my granddaughter I immediately ordered another Wouxon cable to give to her. It works on the Kenwood's and other like radios with the same type connections.
So I threw away both Baofeng cables and stick with something I know works.
Ken KC9QV
ARRL Accredited Volunteer Examiner MRAC Accredited Volunteer Examiner Alger County Michigan ARES AEC Munising, MI (Spring, Summer & Fall) Grid Square EN66og South Milwaukee, WI (Winter) Grid Square EN62bv Member of AARC, HARA, LARS, MAARS, SMARC & ARRL
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Jim Unroe Sent: Saturday, October 29, 2016 5:49 PM To: Discussion of CHIRP Subject: Re: [chirp_users] UV5R programming problems
Anyone got any good ideas? Given that the radio doesn't go into transmit mode when the serial port is open I can't see how it can be bad cable / poor connections.
Richard,
I have never had this issue (yet) with any of my Linux distros. However it seems that you are not alone. A patch was recently submitted for what seems to be a similar issue. You can review it here.
http://chirp.danplanet.com/issues/4165
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to krugaber@gmail.com at krugaber@gmail.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 Jock at kc6iih@aol.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 Jock at kc6iih@aol.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Sat, Oct 29, 2016 at 8:27 PM, Ken Rugaber (KC9QV) krugaber@gmail.com wrote:
What cable is being used?
I had issues with the Baofeng Tech cable on a UV82-HP within the last 6 months. I trimmed the cable to insure a good fit etc. Finally I tried my Wouxon cable that I also had and it worked like a charm. Since the HT I was trying to program was a gift for my granddaughter I immediately ordered another Wouxon cable to give to her. It works on the Kenwood's and other like radios with the same type connections.
So I threw away both Baofeng cables and stick with something I know works.
Ken KC9QV
Baofeng Tech cables are not Baofeng branded cables so it is not clear what you threw away.
Jim KC9HI
participants (9)
-
Chris Petry -
dmdfacp＠gmail.com -
Jim Unroe -
kc6iih＠aol.com -
Ken Rugaber (KC9QV) -
Neil Stone -
Nigel A. Gunn G8IFF/W8IFF -
Richard -
Robert Baird