[chirp_users] UV5R programming problems

[Neil Stone]

I bought a cheap one from ebay... windows keeps throwing it's toys out of
the pram with drivers, but I have worked out what I need to do with that
now. My cable has worked with ubuntu, Gentoo and debian happily with no
issues...

Btu

sent from my Galaxy S7 Edge - Powered by Percy the purple pig.

On 29 Oct 2016 23:29, "Richard" <richard.cs at gmail.com> wrote:

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 at 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 at gmail.com> wrote:
>
>> Geographically?
>>
>> Southampton, UK.
>>
>> On 29 October 2016 at 14:27, Nigel A. Gunn G8IFF/W8IFF <nigel at ngunn.net>
>> wrote:
>>
>>> Where are you?
>>>
>>>
>>> > On 29 October 2016 at 07:20 Richard <richard.cs at 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 at intrepid.danplanet.com
>>> > http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>> > This message was sent to Nigel Gunn, W8IFF at nigel at ngunn.net
>>> > To unsubscribe, send an email to chirp_users-unsubscribe at intrep
>>> id.danplanet.com
>>> _______________________________________________
>>> chirp_users mailing list
>>> chirp_users at intrepid.danplanet.com
>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>> This message was sent to Richard at richard.cs at gmail.com
>>> To unsubscribe, send an email to chirp_users-unsubscribe at intrep
>>> id.danplanet.com
>>>
>>
>>
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> This message was sent to Neil Stone at neil.stone at gmail.com
>> To unsubscribe, send an email to chirp_users-unsubscribe at intrep
>> id.danplanet.com
>>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Richard at richard.cs at gmail.com
> To unsubscribe, send an email to chirp_users-unsubscribe at intrep
> id.danplanet.com
>


_______________________________________________
chirp_users mailing list
chirp_users at intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to Neil Stone at neil.stone at gmail.com
To unsubscribe, send an email to chirp_users-unsubscribe@
intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161029/05c18216/attachment.html