For what it is worth, I think I have isolated the second problem to a "defective" USB cable. While the "defective"cable requires the older driver (as do my other two "non-defective" cables) and does a download and upload without issues, this is the only cable that then causes the radio to go into transmit after uploading a configuration file ... followed by the normal power off/power on of the radio. Disconnecting the cable immediately after the power off seems to preclude the erroneous transmit indication. The first problem is still a puzzler. While the workaround of resetting the fields is acceptable, I am still curious as to why/how this was suddenly manifested as my UV5Rs are several years old. -- John 73's de K9RSQ
On 3/14/2016 11:50 PM, John Randle wrote:
I have been maintaining several UV5R's with Chirp for a couple of years without any issues. I am currently running Chirp Daily Build 20151126 on W10 to program several UV5R's. I have recently experienced two strange programming operation issues, with all the UV5R's, that I have not previously encountered. First problem: After downloading the current configuration of the UV5R's, I then proceeded to add some new memory channels that use Digital Coded Squelch settings. When programming the DCS settings, I first set "DTCS", then I set the individual T-DCS and R-DCS codes and then I set Cross to "Tone -> Tone" (as this is what the existing DCS memory channels reflect), but as soon as I set the offset direction, Chirp changes "DTCS" to "Cross" and changes "Tone -> Tone" to "DTCS->". As these settings are not what is required (or at least what is currently reflected in the older DCS memory channels), I then have to go back and reset "DTCS->" to "Tone -> Tone" and "Cross" to "DTCS". Is there any reason why my initial inputs are being over-ridden? Second problem: After successfully uploading a new configuration to the UV5-R's, the UV5R's automatically go into transmit mode about 5 seconds after they restart if the programming cable is left connected to the radio. This seems to be a new issue that I had not previously experienced. Any suggestions on either problem will be greatly appreciated. -- John 73's de K9RSQ