[chirp_devel] VX-7R w/USB-Serial Adapter - Locking Up MacOSX
First off, thanks for Chirp! Love it! Working great with my Wouxun KG-UV3D once I found the driver for the WXUSB cable.
However, for my Yaesu VX-7R, I'm not able to Upload. I was able to Download what I had in their before though. Whenever I try and upload anything to the VX-7R, the progress bar makes it to about between the "i" and "n" in the word "Cloning" above the progress bar every time... and then. KABOOM! Keyboard and Mouse input stops working on the Mac. Cannot even do a Force Kill keystroke (CMD-OPT-ESC). The power button does still work and brings up the Reboot/Shutdown/Cancel dialog box... but with no keyboard/mouse, can't really click on it. I have to hold down the power down till the machine forces turn off.
A couple of seconds after the progress bar stops, the VX-7R goes into non-Clone mode, but has completely lost all programming.
UV-3D still works like a champ, BTW.
I have Best Buy brand (Dynex I think?) USB-Serial convertor for my 9-pin serial Yaesu cable. I've ordered a USB Yaesu cable from WAMA (or whatever that eBay site is), but won't be here for a few days. Here are the pertinent data, I think.
MacOSX 10.6.8 CHIRP daily-08202011 GTK 2.16.6 (from CHIRP about) PyGTK 2.14.1 (from CHIRP about)
MacBook Pro 15" (2.8Ghz Core i7, 8GB RAM, 240GB SSD) Dynex USB-Serial Adapter Yaesu Serial programming cable Yaesu VX-7R
However, for my Yaesu VX-7R, I'm not able to Upload. I was able to Download what I had in their before though. Whenever I try and upload anything to the VX-7R, the progress bar makes it to about between the "i" and "n" in the word "Cloning" above the progress bar every time... and then. KABOOM! Keyboard and Mouse input stops working on the Mac. Cannot even do a Force Kill keystroke (CMD-OPT-ESC). The power button does still work and brings up the Reboot/Shutdown/Cancel dialog box... but with no keyboard/mouse, can't really click on it. I have to hold down the power down till the machine forces turn off.
Yikes! That'd be a driver issue for the serial adapter. Nothing in userspace should be able to do that to your machine. Prolific had lots of trouble with their ported-from-XP driver on Vista for about a year after its release. Similar behavior would occur, requiring a total reboot to unstick the system. It was so bad that they posted something on their driver page that stated they didn't support vista at all. They seem to have resolved their issues now, however. Maybe there's an updated driver out there?
I have Best Buy brand (Dynex I think?) USB-Serial convertor for my 9-pin serial Yaesu cable. I've ordered a USB Yaesu cable from WAMA (or whatever that eBay site is), but won't be here for a few days. Here are the pertinent data, I think.
It will use a prolific chip, which appears to be what's in your Dynex. That means you'll likely have similar issues unless you find and install an updated driver.
FWIW, KeySpan seems to be best choice for MacOS users, but they're spendy.
Thanks for the reply Dan. I might see if I can find an updated MacOSX driver just to make sure that that fixes it. Will reply back if I do. Looking forward to the USB adapter from KAWAMALL and see how that works, think that will be the real answer.
Jay
On Sun, Aug 21, 2011 at 7:02 PM, Dan Smith dsmith@danplanet.com wrote:
However, for my Yaesu VX-7R, I'm not able to Upload. I was able to Download what I had in their before though. Whenever I try and upload anything to the VX-7R, the progress bar makes it to about between the "i" and "n" in the word "Cloning" above the progress bar every time... and then. KABOOM! Keyboard and Mouse input stops working on the Mac. Cannot even do a Force Kill keystroke (CMD-OPT-ESC). The power button does still work and brings up the Reboot/Shutdown/Cancel dialog box... but with no keyboard/mouse, can't really click on it. I have to hold down the power down till the machine forces turn off.
Yikes! That'd be a driver issue for the serial adapter. Nothing in userspace should be able to do that to your machine. Prolific had lots of trouble with their ported-from-XP driver on Vista for about a year after its release. Similar behavior would occur, requiring a total reboot to unstick the system. It was so bad that they posted something on their driver page that stated they didn't support vista at all. They seem to have resolved their issues now, however. Maybe there's an updated driver out there?
I have Best Buy brand (Dynex I think?) USB-Serial convertor for my 9-pin serial Yaesu cable. I've ordered a USB Yaesu cable from WAMA (or whatever that eBay site is), but won't be here for a few days. Here are the pertinent data, I think.
It will use a prolific chip, which appears to be what's in your Dynex. That means you'll likely have similar issues unless you find and install an updated driver.
FWIW, KeySpan seems to be best choice for MacOS users, but they're spendy.
-- Dan Smith www.danplanet.com KK7DS _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
On Mon, Aug 22, 2011 at 4:04 PM, Jay Moran jay+CHIRP@tp.org wrote:
Thanks for the reply Dan. I might see if I can find an updated MacOSX driver just to make sure that that fixes it. Will reply back if I do. Looking forward to the USB adapter from KAWAMALL and see how that works, think that will be the real answer.
Well, already had a newer PL2303 driver installed from the Wouxun WXUSB cable (which works with the UV3D). Hrmph. Wouldn't let me install the older driver from the Dynex site since the newer driver was installed. I'll just wait for KAWAMAL and try that. Thanks again!
Jay
On Mon, Aug 22, 2011 at 4:33 PM, Jay Moran jay+CHIRP@tp.org wrote:
Well, already had a newer PL2303 driver installed from the Wouxun WXUSB cable (which works with the UV3D). Hrmph. Wouldn't let me install the older driver from the Dynex site since the newer driver was installed. I'll just wait for KAWAMAL and try that. Thanks again!
KAWAMALL cable did the same thing. Guess MacOSX (or at least mine) and Prolific and Yaesu Uploading of programming just does NOT work. Bummer. That said, picked up a Tripp Keyspan USB-Seria. Worked awesomely well, so now have my VX-7R (that my wife has taken over after getting her ticket a couple of weeks ago) working just fine.
Thanks for the help Dan. Hopefully others can avoid the issue.
Jay
KAWAMALL cable did the same thing. Guess MacOSX (or at least mine) and Prolific and Yaesu Uploading of programming just does NOT work. Bummer.
Well, the (prolific adapters) will work, there are many people on the list that use then (and it shouldn't be related to the VX-7). However, it sounds like there's a potential driver issue that needs to get worked out. If you're interested, Debbie Filgor on the users list is a very competent Mac power user which I'm sure could help you.
That said, picked up a Tripp Keyspan USB-Seria. Worked awesomely well, so now have my VX-7R (that my wife has taken over after getting her ticket a couple of weeks ago) working just fine.
Excellent. Keyspan devices are, without a doubt, the highest quality USB adapters I've found.
On Sat, Aug 27, 2011 at 12:25 PM, Dan Smith dsmith@danplanet.com wrote:
Well, the (prolific adapters) will work, there are many people on the list that use then (and it shouldn't be related to the VX-7). However, it sounds like there's a potential driver issue that needs to get worked out. If you're interested, Debbie Filgor on the users list is a very competent Mac power user which I'm sure could help you.
I'll try out the users list sometime and see if I can work through those issues. Just strange that the Prolific chip in the WXUSB cable works perfectly... and even the KAWAMALL cable (and the Best Buy Dynex USB-Serial adpater) work fine with DOWNLOADING from the radio. Is only an UPLOAD problem for the Yaesu. Again, UPLOAD/DOWNLOAD works fine with the Wouxun WXUSB Prolific-based cable.
Saw the daily change log talking about throttling the conversation for the FT2800 and thought that might help. Unfortunately, I can't get any daily build beyond 8/25/11 to work. I'll try a new build in a few days and if still broken will file a bug report then.
I'll try out the users list sometime and see if I can work through those issues. Just strange that the Prolific chip in the WXUSB cable works perfectly... and even the KAWAMALL cable (and the Best Buy Dynex USB-Serial adpater) work fine with DOWNLOADING from the radio. Is only an UPLOAD problem for the Yaesu. Again, UPLOAD/DOWNLOAD works fine with the Wouxun WXUSB Prolific-based cable.
Yeah, but the wouxun cable behaves a little differently. The VX7 cable has the TX and RX lines tied together so that it "echos" everything either side sends. If there is a race condition in an interrupt handler in the prolific driver (or something similar), the immediate echo could be poking it where the relatively slow exchange back and forth of the wouxun does not.
Saw the daily change log talking about throttling the conversation for the FT2800 and thought that might help.
Well, (a) that's only in the FT2800 driver, so it won't affect the VX7 and (b) that is because the radio doesn't implement flow control and shoving data to it too fast makes it silently fail. It's definitely a different problem than the kernel USB driver crashing.
Unfortunately, I can't get any daily build beyond 8/25/11 to work. I'll try a new build in a few days and if still broken will file a bug report then.
Oh, yeah? Someone contributed a script change for the MacOS package and he said it worked. I'll cc you on an email to him so we can get that worked out as I was hoping to do another release before too long :)
Thanks!
On Sat, Aug 27, 2011 at 2:12 PM, Dan Smith dsmith@danplanet.com wrote:
Yeah, but the wouxun cable behaves a little differently. The VX7 cable has the TX and RX lines tied together so that it "echos" everything either side sends. If there is a race condition in an interrupt handler in the prolific driver (or something similar), the immediate echo could be poking it where the relatively slow exchange back and forth of the wouxun does not.
Makes sense. New cable from KAWAMALL doesn't kill the keyboard/mouse (X-Windows and the script itself do lock up though). Keyboard/mouse are still active though so I can at least kill -9 the process and the like. But still requires a reboot to get the cable working again, so certainly something bad that the Yaesu is causing to happen with the PL2303 drivers that the Wouxun doesn't.
Well, (a) that's only in the FT2800 driver, so it won't affect the VX7 and (b) that is because the radio doesn't implement flow control and shoving data to it too fast makes it silently fail. It's definitely a different problem than the kernel USB driver crashing.
Well, I figured it was a script, and I'd just do a diff and see what you changed and change the VX7 as well. :) Keyspan cable eliminated that need though.
Oh, yeah? Someone contributed a script change for the MacOS package and he said it worked. I'll cc you on an email to him so we can get that worked out as I was hoping to do another release before too long :)
Saw the other emails, will check and see if you have a new daily build up with the change. If not, I'll manually make the change and see if it works. Looks like it should from what submitter said in the other email thread.
Thanks again Dan!
Saw the other emails, will check and see if you have a new daily build up with the change. If not, I'll manually make the change and see if it works. Looks like it should from what submitter said in the other email thread.
Yeah, I didn't push anything into the tree yesterday so it didn't squeeze out another build. I have already today though, so there will be one tomorrow. Even if you make the change today, I'd appreciate confirmation tomorrow that the official build is being created properly :)
Thanks!
On Sun, Aug 28, 2011 at 1:09 PM, Dan Smith dsmith@danplanet.com wrote:
Yeah, I didn't push anything into the tree yesterday so it didn't squeeze out another build. I have already today though, so there will be one tomorrow. Even if you make the change today, I'd appreciate confirmation tomorrow that the official build is being created properly :)
Might be a problem due to the fact that I'm not using MacPorts py27 instead of the static build. I can hack it and force it to use the static stuff for testing though. Personally, I'm glad to see it working without that static stuff though, but that might be a challenge for most folks to get working and the downloadable static setup is relatively easy for them.
participants (2)
-
Dan Smith -
Jay Moran