On Wed, May 13, 2015 at 9:52 AM, Charles Boling junk07+chirp@boling.us wrote:
On 05/12/2015 07:20 PM, Ryan Tourge wrote:
if you are getting the same issue as a fella with a a cable issue I would bet that your cable doesn't have the right driver installed. Tell us more about the cable.
It's Linux, so it doesn't have the mess of driver issues that the Prolific chipsets (and clones) have on Windows.
The fact that, unlike Ben, I do get the expected text from the radio is encouraging. Of course, it doesn't tell me that anything sent *to* the radio is getting there, but at least we know something's [at least mostly] working in one direction.
Your loopback test proves it's not a driver issue.
It's possible there's another issue with the cable, but I'd bet there's something funky in the code. At the very least, Chirp's error handling is lacking because here we're seeing a low-level Python error, not a Chirp application error.
I don't have time to look into this now, but I'd start by viewing the history on ft7800.py in the repo.
Tom KD7LXL