[chirp_users] Thoughts on TH-F6A support and looking for D710 support

David Ranch chirp at trinnet.net
Sat Feb 5 12:00:15 PST 2011


Hello Dan,

> Do you mean the column is missing or the values are blank?  If the 
> column is missing, add it in the View menu.  However, you should be 
> seeing them in the stderr output, as you mentioned.
>   
the column is blank as is the output of STDERR.  Please see my original 
post for an example of what's seen in the STDERR output.


>> Any thoughts on why the cancel doesn't work on the Yaesu radios? Is my
>> Python environment missing something?
>>     
>
> Oh, right, I meant to mention that.  Apparently you're missing the 
> 'ctypes' module.  What Python and OS version are you running?
>   
Also mentioned in the first email: Centos 5.5.  I have two versions of 
Python installed but, by default, it will run the 2.4.3 version which is 
the Centos stock version.
python-2.4.3-27.el5_5.3
python25-2.5.1-bashton1

If I try to use the 2.5 version, it seems like many of my other modules 
are no longer found.  I've seen this before but I don't know how to 
populate one version of Python's modules into a different version of Python:
--
$ /usr/bin/python2.5 chirpw
Traceback (most recent call last):
  File "chirpw", line 24, in <module>
    import gtk
ImportError: No module named gtk
--


> The Kenwood radios are really a lot easier to do than the other types, 
> so I wouldn't be opposed to starting down that road on some of those. 
> The only problem is that I have a D700 in my car, but that's my only 
> one, so it's not very convenient for development.
>   
Yeah.. I can understand that and they aren't all that cheap either.  I 
would assume they are fairly similar but maybe that's a bad assumption.


>> Have you chatted with the author of the VX commander software? It seems
>> like he's been busy for a long time and he might be willing to send you
>> his source code for that alpha version of the tool.
>>     
>
> I haven't, but other people have reportedly solicited some input from 
> him and have not been very pleased with the results.
>   
Hmmmm... maybe that's when he still had time for things.. maybe things 
have changed?  I can try if you'd like.


> Your call.  I'd be glad to do the work and get it back to you if you 
> want to send it.  I'm able to reverse engineer most radios in about 48 
> hours (wall clock time) depending on what else I have going on.
>   
Well, like I mentioned, the VX5 is the bottom of my list so I rather you 
spend your time on the D710 first and then, if you're willing, I can 
ship it up.


> Well, I could.  It used to be that the live radios were treated a little 
> differently in the UI than the clone types, and it generated confusion 
> for a lot of people.  Moving to a more unified approach has made it a 
> lot easier to use.  Maybe a "FYI this is live" pop-up with a "don't show 
> me this again" checkbox would be appropriate.
>   
That would help though I think most people won't understand what a 
"live" radio means.  Most programs that people have used like Kenwood's 
radios, VX commander, etc. are batch download/upload tools.  I prefer 
this live approach though!


> Feel free to document the above in a tracker item to (a) remind me and 
> (b) preserve it for when we get there.  You can do that here:
>
>    http://trac.chirp.danplanet.com
>   
Will do!

>On second thought, let me use the software to emulate the radio, and 
>then I'll let you test it with the real radio to make sure it works. 
>The yaesus are extremely sensitive to timing (compared to the Icom and 
>Kenwood radios), so it's not uncommon for me to need to do some tweaking 
>after the protocol is in place.
>
>So, stay tuned for some beta code for the VX5 and lets see how it goes, 
>okay?

Did you notice in my original email that there was some data output when 
I selected the VX3 mode?  Does that help at all?

--David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20110205/be24cf9c/attachment-0002.html 


More information about the chirp_users mailing list