Probably I am not ready for them just yet.  I gave OWX a shot, and 
nothing I could do would get it to work for me on a Mac.  I think you 
said there was a Windows build somewhere, but I could not find it.  
If it is out there, it would require the whole Cygwin environment 
because the code pretty much assumes Linux and does not bother to 
check for anything else.

I did get CHIRP to work, but it runs under X11 on the Mac.  On the 
plus side, that means I could configure it to talk by installing the 
appropriate accessibility components.  Might as well, the runtime 
includes Perl, two versions of Python, TCL/TK, GTK+, Pango, and 
basically the greater part of a full Linux desktop.  Yeesh.

What these two projects have going for them is that CHIRP works and 
is written in pretty basic and understandable Python, and OWX is far 
more complete and written in pretty basic C++.

This afternoon, I’ve already got a fairly robust bit of code to 
detect a Wouxun radio connected to any serial port in an enumerated 
list of acceptable ports.  At the moment, I’m borrowing that list of 
ports wholesale from CHIRP, so it’s basically variations on 
/dev/cu.usbserial for the Mac and a whole bunch of device names for 
Linux.  I haven’t forgotten about Windows, but I’m not there yet.

I’ve dumped the Wouxun memory to my screen, but not actually parsed 
it yet.  I found (yet another) IOKit bug to do with USB devices in 
the process.  In fact, I think this is the same bug Florent Pillet 
and I reported to Apple seven years ago.  *sigh*  In fact, I think 
Florent actually sent them a PATCH!  Winning the future, Apple!

Right now the code is Python because I am prototyping.  Were it just 
for me, the code would remain in Python.  It is actually pretty easy 
to make Python "binaries" for Windows, but the GUI is usually not 
going to be accessible that way.  Nope, I am going to have to port 
this to C at some point, once I am satisfied that I have a robust 
means of talking to the HT.

I may not have time to work on it for a week or so.

Joseph - KF7QZC


On Fri, Aug 26, 2011 at 10:06:11AM -0400, Buddy Brannan wrote:
>Bear in mind it doesn't grok .tw files, however.
>
>I do have some .xls spreadsheets with macros that Dave, K7DB, put =
>together that are supposed to map the .tw files and that have some other =
>magic which supposedly reads and writes .tw files using Excel, but I'm =
>too stupid to figure out how to use them. If you think they'd be =
>helpful, I'm happy to pass those on as well.
>--
>Buddy Brannan, KB5ELV - Erie, PA
>Phone: (814) 860-3194 or 888-75-BUDDY
>
>
>
>On Aug 26, 2011, at 5:22 AM, T. Joseph Carter wrote:
>
>> Jackpot, this is what I wanted!  It=3DE2=3D80=3D99s written in C++, =
>but I can r=3D
>> ead=3D20
>> that, and it has a far more complete definition of the protocol=3D20
>> involved.
>>=20
>> Joseph - KF7QZC
>>=20
>>=20
>> On Thu, Aug 25, 2011 at 03:54:52PM -0400, Buddy Brannan wrote:
>>> Hey Joseph,
>>>=20
>>> Actually, no, not chirp. Hang on, I've got a URL around here=3D20
>>> somewhere to the original GNU/Linux source. I just compiled under=3D20
>>> cygwin as well and included the cygwin bits for Windows use.=3D20
>>> However, what these guys have done might be useful to you.
>>>=20
>>> Ah. Here we are. Haven't looked at this in a long time.
>>>=20
>>> http://owx.chmurka.net/
>>> --
>>> Buddy Brannan, KB5ELV - Erie, PA
>>> Phone: (814) 860-3194 or 888-75-BUDDY