Re: [Rigserve-devel] Icom Receiver Development

[Martin A. <aa...@ew...>]

Jim,

   I have been looking at the problem of multiple Icom rigs & classes a 
little bit.  There is useful CI-V command documentation at 
http://www.plicht.de/ekki/civ/index.html - if that helps.  The 
conclusion is (in part) that Icom CI-V capable rigs are all quite 
similar, but they are all different.  How to express all that 
information in a natural and compact way is an interesting question.  It 
would be nice to have a CIV base class with subclasses for each distinct 
model.

On the other hand, in the short run it's way easier to do what you've 
done and just copy the hardware interface subroutines and adapt to the 
one particular model you're interested in.

There is also the problem we have talked about in Hamlib for some time. 
  Are we trying to invent a system that expresses the full capability of 
each type of rig, or are we looking to implement some lowest common 
denominator?  For example, I'm inclined to ignore the scanning and 
memory capabilities that vary a lot from rig to rig - at least until 
someone comes along who really wants to implement it.

Hopefully, I'll have more to say after a while.

73 Martin AA6E

James Watson wrote:
> Hi Martin,
> 
> Sorry for the delay in getting back to you but I've been stupidly busy
> at work.
> 
> I've attached the files that so far seem to work on my R75. I've tested
> most routines fairly thoroughly. I've also added a simple routine ant to
> select the antenna input (my first Python script).
> 
> I'm not sure of the best way to organise the code to reduce re-coding
> for similar receivers but was wondering about a CIV class that
> initialised with rig specific class that consisted essentially of
> definitions, i.e. dictionaries of valid modes (the modes/filter
> bandwidths are called up with the same syntax but not all modes appear
> to be supported on all receivers).
> 
> Anyway,  I hope the attached is of interest.  If there's anything I can
> do to help, please let me know.
> 
> 
> 
> 
> o readOn Sun, 2007-07-15 at 16:00 -0400, Martin AA6E wrote:
>> Jim -
>>
>> I would only point out that the Python 'serial' package already provides 
>> the basic serial class.  Is there something that it lacks for our work?
>>
>> Maybe there is room for a CI-V class that is effectively based on 'serial'.
>>
>> -Martin
>>