<div dir="ltr"><div>Geographically?<br><br></div>Southampton, UK.<br><div class="gmail_extra"><br><div class="gmail_quote">On 29 October 2016 at 14:27, Nigel A. Gunn G8IFF/W8IFF <span dir="ltr"><<a href="mailto:nigel@ngunn.net" target="_blank">nigel@ngunn.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Where are you?<br>
<div><div class="h5"><br>
<br>
> On 29 October 2016 at 07:20 Richard <<a href="mailto:richard.cs@gmail.com">richard.cs@gmail.com</a>> wrote:<br>
><br>
><br>
> I know this is a common problem but I have tried all the "usual" things<br>
> with no success. I am on my second programming cable after the first one<br>
> just didn't get recognised as a USB device, and first attempt I was able to<br>
> download the contents of my radio. Since then however it's not worked again.<br>
><br>
> The cable works OK and the drivers are loaded, as confirmed by opening a<br>
> serial terminal, linking the TX and RX pins and observing loopback. The<br>
> radio goes into TX when powered on with the cable attached and some vicious<br>
> connector trimming doesn't help - I am sure it is going all the way in.<br>
> Following the order in the Chirp pop-up instructions (cable is already<br>
> connected to PC and correct serial port selected, radio off, connect cable,<br>
> radio on with volume right up, check no activity, click OK) doesn't help.<br>
> The radio goes into TX as soon as it's booted and after a few seconds I get<br>
> "Radio did not respond".<br>
><br>
> The radio does *not* go into TX if I have that port open in a serial<br>
> terminal when I turn the radio on, and presumably if Chirp opened the port<br>
> when the instructional message is displayed (before the radio is turned on)<br>
> but still waited for the user to click OK before trying to communicate all<br>
> would work?<br>
><br>
> I think that the one time it did work it might have been TX-ing and I just<br>
> got lucky that it didn't interfere with communications - I do remember some<br>
> interference on my monitor which I now know happens when the radio<br>
> transmits.<br>
><br>
> Anyone got any good ideas? Given that the radio doesn't go into transmit<br>
> mode when the serial port is open I can't see how it can be bad cable /<br>
> poor connections.<br>
><br>
> This is on Linux Mate 1.12.1, with the current daily Chirp build. My user<br>
> is in the dialout group and has serial port access.<br>
><br>
> Thanks<br>
> Richard<br>
</div></div>> ______________________________<wbr>_________________<br>
> chirp_users mailing list<br>
> <a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.<wbr>danplanet.com</a><br>
> <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/<wbr>mailman/listinfo/chirp_users</a><br>
> This message was sent to Nigel Gunn, W8IFF at <a href="mailto:nigel@ngunn.net">nigel@ngunn.net</a><br>
> To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@<wbr>intrepid.danplanet.com</a><br>
______________________________<wbr>_________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.<wbr>danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/<wbr>mailman/listinfo/chirp_users</a><br>
This message was sent to Richard at <a href="mailto:richard.cs@gmail.com">richard.cs@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@<wbr>intrepid.danplanet.com</a><br>
</blockquote></div><br></div></div>