23 Jan
2014
23 Jan
'14
1:58 p.m.
On Thu, Jan 23, 2014 at 1:27 PM, Basil Copeland blcjr2@gmail.com wrote:
windows, with a final error message saying something about being unable to "read echo" and then "bad cable?"
This error means that Chirp tried to send something out over the serial port and didn't get a response. With Yaesu cables, everything sent should echo back to the serial port, because the tx and rx lines are connected together. The cause of this is usually, as reported, a faulty cable or driver. My only other idea is that another program may have been using the serial port when Chirp tried to access it. Was Commander still open?
Tom KD7LXL