There is a driver, actually! It comes from the Prolific website, and
it creates /dev/cu.usbserial which I have had no trouble reading to
or writing from using either CHIRP or my own very early Wouxun code.
Thanks for a link to the OWX windows binary, I’ll pass it on to a
friend who is looking for it!
Joseph - KF7QZC
On Sat, Aug 27, 2011 at 08:26:15PM -0400, Buddy Brannan wrote:
>Hi Joseph,
>
>Sorry. I'm not smart enough to get this to work with the Mac, mostly =
>because I don't know if there's a driver for the USB to serial adapter =
>in the cable.=20
>
>The owx I have for Windows, I just ran cygwin and it did the whole build =
>right in cygwin. This is probably a couple versions ago, but here it is:
>http://dl.dropbox.com/u/1053407/owx-win32.zip
>
>--
>Buddy Brannan, KB5ELV - Erie, PA
>Phone: (814) 860-3194 or 888-75-BUDDY
>
>
>
>On Aug 27, 2011, at 8:20 PM, T. Joseph Carter wrote:
>
>> Probably I am not ready for them just yet. I gave OWX a shot, and=3D20
>> nothing I could do would get it to work for me on a Mac. I think =
>you=3D20
>> said there was a Windows build somewhere, but I could not find it. =3D20=
>
>> If it is out there, it would require the whole Cygwin environment=3D20
>> because the code pretty much assumes Linux and does not bother to=3D20
>> check for anything else.
>>=20
>> I did get CHIRP to work, but it runs under X11 on the Mac. On the=3D20
>> plus side, that means I could configure it to talk by installing =
>the=3D20
>> appropriate accessibility components. Might as well, the runtime=3D20
>> includes Perl, two versions of Python, TCL/TK, GTK+, Pango, and=3D20
>> basically the greater part of a full Linux desktop. Yeesh.
>>=20
>> What these two projects have going for them is that CHIRP works and=3D20=
>
>> is written in pretty basic and understandable Python, and OWX is =
>far=3D20
>> more complete and written in pretty basic C++.
>>=20
>> This afternoon, I=3DE2=3D80=3D99ve already got a fairly robust bit of =
>code to=3D20
>> detect a Wouxun radio connected to any serial port in an enumerated=3D20=
>
>> list of acceptable ports. At the moment, I=3DE2=3D80=3D99m borrowing =
>that list=3D
>> of=3D20
>> ports wholesale from CHIRP, so it=3DE2=3D80=3D99s basically variations =
>on=3D20
>> /dev/cu.usbserial for the Mac and a whole bunch of device names for=3D20=
>
>> Linux. I haven=3DE2=3D80=3D99t forgotten about Windows, but =
>I=3DE2=3D80=3D99m not th=3D
>> ere yet.
>>=20
>> I=3DE2=3D80=3D99ve dumped the Wouxun memory to my screen, but not =
>actually pars=3D
>> ed=3D20
>> it yet. I found (yet another) IOKit bug to do with USB devices in=3D20
>> the process. In fact, I think this is the same bug Florent Pillet=3D20
>> and I reported to Apple seven years ago. *sigh* In fact, I think=3D20
>> Florent actually sent them a PATCH! Winning the future, Apple!
>>=20
>> Right now the code is Python because I am prototyping. Were it =
>just=3D20
>> for me, the code would remain in Python. It is actually pretty =
>easy=3D20
>> to make Python "binaries" for Windows, but the GUI is usually not=3D20
>> going to be accessible that way. Nope, I am going to have to port=3D20
>> this to C at some point, once I am satisfied that I have a robust=3D20
>> means of talking to the HT.
>>=20
>> I may not have time to work on it for a week or so.
>>=20
>> Joseph - KF7QZC
>>=20
>>=20
>> On Fri, Aug 26, 2011 at 10:06:11AM -0400, Buddy Brannan wrote:
>>> Bear in mind it doesn't grok .tw files, however.
>>>=20
>>> I do have some .xls spreadsheets with macros that Dave, K7DB, put =3D3D=
>
>>> together that are supposed to map the .tw files and that have some =
>other=3D
>> =3D3D
>>> magic which supposedly reads and writes .tw files using Excel, but =
>I'm =3D3D
>>> too stupid to figure out how to use them. If you think they'd be =3D3D
>>> helpful, I'm happy to pass those on as well.
>>> --
>>> Buddy Brannan, KB5ELV - Erie, PA
>>> Phone: (814) 860-3194 or 888-75-BUDDY
>>>=20
>>>=20
>>>=20
>>> On Aug 26, 2011, at 5:22 AM, T. Joseph Carter wrote:
>>>=20
>>>> Jackpot, this is what I wanted! It=3D3D3DE2=3D3D3D80=3D3D3D99s =
>written in C=3D
>> ++, =3D3D
>>> but I can r=3D3D3D
>>>> ead=3D3D3D20
>>>> that, and it has a far more complete definition of the =
>protocol=3D3D3D20
>>>> involved.
>>>> =3D3D20
>>>> Joseph - KF7QZC
>>>> =3D3D20
>>>> =3D3D20
>>>> On Thu, Aug 25, 2011 at 03:54:52PM -0400, Buddy Brannan wrote:
>>>>> Hey Joseph,
>>>>> =3D3D20
>>>>> Actually, no, not chirp. Hang on, I've got a URL around here=3D3D3D20=
>
>>>>> somewhere to the original GNU/Linux source. I just compiled =
>under=3D3D3=3D
>> D20
>>>>> cygwin as well and included the cygwin bits for Windows use.=3D3D3D20=
>
>>>>> However, what these guys have done might be useful to you.
>>>>> =3D3D20
>>>>> Ah. Here we are. Haven't looked at this in a long time.
>>>>> =3D3D20
>>>>> http://owx.chmurka.net/
>>>>> --
>>>>> Buddy Brannan, KB5ELV - Erie, PA
>>>>> Phone: (814) 860-3194 or 888-75-BUDDY
|
