<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>The best and most reliable cables come from www.rtsystems.com</div><div>Yes they are not cheap but they work every time.</div><div><br></div><div><br></div><div style="font-size:10px">Jock A. Soutar </div><div style="font-size:10px">KC6IIH</div><div style="font-size:10px">Sent via the Samsung Galaxy S™ III, an AT&T 4G LTE smartphone</div><br><br><div>-------- Original message --------</div><div>From: John Randle <john.randle@tds.net> </div><div>Date:03/16/2016 7:03 PM (GMT-08:00) </div><div>To: chirp_users@intrepid.danplanet.com </div><div>Subject: Re: [chirp_users] BAOFENG UV-5Rs acting strange when programming
with Chirp </div><div><br></div>For what it is worth, I think I have isolated the second problem to a <br>"defective" USB cable. While the "defective"cable requires the older <br>driver (as do my other two "non-defective" cables) and does a download <br>and upload without issues, this is the only cable that then causes the <br>radio to go into transmit after uploading a configuration file ... <br>followed by the normal power off/power on of the radio. Disconnecting <br>the cable immediately after the power off seems to preclude the <br>erroneous transmit indication.<br>The first problem is still a puzzler. While the workaround of resetting <br>the fields is acceptable, I am still curious as to why/how this was <br>suddenly manifested as my UV5Rs are several years old.<br>--<br>John<br>73's de K9RSQ<br><br>On 3/14/2016 11:50 PM, John Randle wrote:<br>> I have been maintaining several UV5R's with Chirp for a couple of <br>> years without any issues.<br>> I am currently running Chirp Daily Build 20151126 on W10 to program <br>> several UV5R's. I have recently experienced two strange programming <br>> operation issues, with all the UV5R's, that I have not previously <br>> encountered.<br>> First problem: After downloading the current configuration of the <br>> UV5R's, I then proceeded to add some new memory channels that use <br>> Digital Coded Squelch settings.<br>> When programming the DCS settings, I first set "DTCS", then I set the <br>> individual T-DCS and R-DCS codes and then I set Cross to "Tone -> <br>> Tone" (as this is what the existing DCS memory channels reflect), but <br>> as soon as I set the offset direction, Chirp changes "DTCS" to "Cross" <br>> and changes "Tone -> Tone" to "DTCS->". As these settings are not what <br>> is required (or at least what is currently reflected in the older DCS <br>> memory channels), I then have to go back and reset "DTCS->" to "Tone <br>> -> Tone" and "Cross" to "DTCS". Is there any reason why my initial <br>> inputs are being over-ridden?<br>> Second problem: After successfully uploading a new configuration to <br>> the UV5-R's, the UV5R's automatically go into transmit mode about 5 <br>> seconds after they restart if the programming cable is left connected <br>> to the radio. This seems to be a new issue that I had not previously <br>> experienced.<br>> Any suggestions on either problem will be greatly appreciated.<br>> -- <br>> John<br>> 73's de K9RSQ<br>><br><br>_______________________________________________<br>chirp_users mailing list<br>chirp_users@intrepid.danplanet.com<br>http://intrepid.danplanet.com/mailman/listinfo/chirp_users<br>This message was sent to Jock at kc6iih@aol.com<br>To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br></body>