Re: [Hamlib-developer] Re: Fun with Hamlib
Library to control radio transceivers and receivers
Brought to you by:
n0nb
|
From: Stephane F. <f4...@fr...> - 2002-02-27 23:12:57
|
Hi Chuck, First of all, Thanks for your interrest in Hamlib. We do appreciate feedback! On Wed, Feb 27, 2002, Francois Retief wrote: > > 2. In my testing of the ic-r7000, I noticed that the radios using the new icom > > routines didn't support setting the CI-V address. I was using this to play > > with the ic-r7000 with rigctl to talk to the ic-r7000 before I created the > > entry for it. Just wondering if anyone noticed. If I get a chance, I'll try > > to figure out what needs to be done and send in a patch. > > The set_conf()/get_conf() functions is what you need. Add the > following lines to the rig structure: > > cfgparams: icom_cfg_params, > set_conf: icom_set_conf, > get_conf: icom_get_conf, Dang, the icr8500 was the only one missing these lines. Thanks Francois for noticing it. This is commited with an initial ic-r7000 support. Some functions may not be there, I have yet to dig through the manual to see which one are available. > Now to set the CIV address to 0x42, issue: > rig_set_conf(rig, TOK_CIVADDR, 0x42); Chuck, could you confirm this is 0x08 for the R-7000? > Please note, that these two functions is not added to all the > Icom rigs. Still have to be done ;-) Besides icr8500, is there any other? > > 3. One of these days I was going to try testing my software over at a friend's > > house who has an Icom 910 and an AOR 5000 which are also not currently > > supported. If anyone wants me to try something, I'll be happy to. Otherwise > > I'll have to try to come up with descriptions of the radios myself. > > > I have partially completed support for the Icom 910. Our radio is > currently in use, so I cannot test the code. Will finish the IC-910 > code and commit it some time tonight or tomorrow. Alright Francois, good stuff. I've forked an AR5000, should be commited by the time your read this. Please note that the aor backend has never been fully tested, so your report is more than welcome. In order to ease Hamlib hacking, there are some guidelines to test the cvs version, available at the following URL: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/hamlib/hamlib/README.betatester?rev=1.1&content-type=text/vnd.viewcvs-markup Thanks, Stephane F8CFE |