Re: patches for icom

Welcome!

On Friday 07 July 2006 23:06, KHill wrote:
> I have patched and revised the Icom CIV backend, tested against the an ICOM
> 746 pro, and compared against as many protocols as I could find on the
> internet. 746, 756, 756 pro II & III 780 icr 75 9000 and many of the old
> ones I found together in a single table.

Is the patch against current CVS or a release?

> Some general observations:
> Many of the "get_**** " are not available on the rigs.  The general rule is
> that if it doesn't say read/send then using the command without a
> subcommand or data won't work.  Most of  the level and functions are not
> channel specific and are not saved with a channel memory.  Unfortunately,
> most of the protocols do not give the format of the memory structure.  And
> it appears to differ between rigs.   The filter/passband structure for most
> Icom rigs is different than originally coded.  It appears to apply only to
> the 706.  I replaced it with what appears to be the most common usage, but
> I did not complete it especially the rtty mode.  Unfortunately it changes
> from rig to rig although there are commonalities.

Good sleuth work, it looks like it could be very useful.  Sadly, there is 
little consistency between rigs and almost zero between manufacturers.

> Make dist-clean fails with errors of file not found in the bindings dir.

Is this from CVS or release code?

> Rigctl needs much in the way of documentation.

As does much else.  :(  Rigctl is primarily a testing program and not really 
something to be used for everyday operation.

> It's been fun to hack.  I've been trying to use Kdevelop but it is only
> partially successfull, debug mode fails during Make install of the Docs,
> but it goes far enough to use the debugger.  Straight make works.  Has any
> one figured out how to make it completely compatible with the Kdevelop
> debug mode?  Alternatively, how do you get Kdebug to work with dl system?

It's all about fun and the fact that we get something useful along the way is 
a bonus!

I think this since this is a project that has its emphasis in creating a 
library, the focus has been on the use of make and GNU Autotools as the 
development tools of choice.  Myself, I use a nice text editor (FTE) and 
make.  Since I lurk deep in the Yaesu backend area, it works fine for me.

Debugging for me has taken the form of plenty of wrapped print functions that 
are active when a debug level of TRACE is set.  These spit out plenty of 
lines to stderr so I can determine what is happening in my backend code.  So 
far I don't know if anyone is using a debugger with Hamlib.

I'd be happy to apply your patches, but I'd like to hear from anyone else that 
is able to test them with various Icom radios first.  Stephane F8FCE is the 
leading developer on this project so it would be nice to have him be able to 
look at them as well before they go in.

73, de Nate >>

--

-- 
 Wireless | Amateur Radio Station N0NB          |  Successfully Microsoft
  Amateur radio exams; ham radio; Linux info  <at>   | free since January 1998.
             http://www.qsl.net/n0nb/           |  "Debian, the choice of
             My Kawasaki KZ-650 SR  <at>             |     a GNU generation!"
        http://www.networksplus.net/n0nb/       |   http://www.debian.org

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642