On Sat, Sep 22, 2012 at 4:15 PM, <span dir="ltr"><<a href="mailto:chirp.cordless@xoxy.net" target="_blank">chirp.cordless@xoxy.net</a>></span> wrote:<br><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
My sincere thanks for the effort.<br></blockquote><div><br>You're welcome!<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
for you in a very similar configuration. My MacBook is 2.9 GHz vice your<br>
Air looks to be 1.7 GHz - there wouldn't be any clock-counting timeouts in this<br>
software, would there?.<br></blockquote><div><br>2.0Ghz i7 here; but no clock speed should have zero impact on performance of the USB cable. There are separate clocking for each sub-system these days as well.<br> <br></div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is there anything reasonable I can do to troubleshoot this?<br></blockquote><div><br>Reading the later emails, I think your best bet is to do what you've done and order a new cable... I'd recommend sticking with that driver first and see how it works. I have 4 different USB cables (and radios) all told and that driver worked for all of them. Hopefully you just had a bad cable. <br>
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
When Chirp decides it's done after half a second, are there any logs<br>
to look at, or any way to get visibility into what it thinks it's doing?<br></blockquote><div><br>There is a debug.log... it is at: ~/.chirp/debug.log ... that said, I don't think it'll help, but might want to check the end of it and see what you see. <br>
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'd suspect the cable, but it works for read, and I'm reluctant to<br>
spend the money and wait time to get another without some confidence<br>
that that's the problem, and it isn't feeling that way to me so far.<br></blockquote><div> <br>I think trying a new cable is definitely the right next step. I hope it works for you!<br><br>Jay<br></div></div>