Re: [Hamlib-developer] problem adding modules (rigs)
Library to control radio transceivers and receivers
Brought to you by:
n0nb
|
From: Stephane F. <f4...@fr...> - 2001-02-05 07:48:05
|
Hi David!
David HM Spector wrote:
> I'm working on adding support for the Icom R-8500 and the 750PRO to
> hamlib (and a set of nice GUIs to make'em useful), but I'm running in
Good to see people interested in CI-V! Have you noticed there's
already some basic IC-R8500 support in the current CVS repository?
REM: Always use CVS for now, as we're still in alpha stage.
It would be great if you own, or at least are able to test Hamlib
on the Icom R-8500 and the 750PRO. I wrote part of the CI-V support
that is used by most Icoms (~75% opcodes done), but we still have
to find a nice way to handle the CSMA/CD nature of the CI-V bus,
and the sharing of serial ports, including the transceive mode.
> to a prtty basic problem: After adding the modules (i.e., "r8500.c")
> to the Makefile.am file in the icom directory, and rebuilding the
> entire package, I never see the new rig(s) listed when I invoke
> listrigs in the tests directory.
This should really be explained in a new-backend-mini-HOWTO..
Very simple. New backends need to be registered to be known by Hamlib.
For instance, at the very bottom of icom.c, there's a init_icom() function
(the initialization function called right after the backend is loaded)
that should register the R-8500 with "rig_register(&icr8500_caps);"
(as done currently in the CVS rep, see cvsweb or cvs snapshot).
Then, as long as rig_load_backend("icom") is called in listrig,
it should show up:
(fillods@charybde:hamlib)$ tests/listrigs
Rig# Mfg Model Vers. Status Type
0 Yaesu FT-847 0.1 Alpha Transceiver
4 Yaesu FT-747GX 0.1 Alpha Mobile
40 Icom IC-706 0.2 Untested Mobile
73 Icom ICR-8500 0.2 Untested Receiver
41 Icom IC-706MKII 0.2 Untested Mobile
42 Icom IC-706MKIIG 0.2 Alpha Mobile
27 Kenwood TS-870S 0.1 Untested Transceiver
79 AOR AR8200 0.1 Untested Scanner
Anyway, feel free to ask any question if my code looks odd or whatever.
Also you are more than welcome to join the Hamlib development team, and
gain CVS access. I'd be pleased also to hear your comments about
the CI-V layer design in Hamlib, which is far from perfect and complete.
Cheers,
--
Stephane / F4CFE
|