hamlib-developer — hamlib developers forum

Re: [Hamlib-developer] what's up?

[Stephane F. <f4...@fr...>]

On Thu, Oct 11, 2001, Robert Steinhäußer wrote:
> > > Sorry, but I still haven't tested our IC275 and 475 at home. Have to find
> > > the old self-built interface first and then visit mom (DK3XJ) :)
> > >
> >   Great! She will be happy to see you, but first wait IC275 and 475
> >   are added..
> 
> Oops... isn't it a C-IV device as well? I really have to get that stuff
> out of the box on the shelf :-)
 
Yes it is. CI-V id $10 and $14. However, I still have to find the specs,
brochures, whatever, to fill in the caps..

> > 	Let me know if some functions are missing in Hamlib, or if you
> >   think the design is not appropriate. Accessing the caps/state directly is
> >   recommanded, instead set_conf/get_conf should be used, provided more
> >   parameters are declared (yet to be done). Maybe there should be some
> >   config data file support in Hamlib, regardless the application.
> >   What do you think?
> 
> I am trying to figure out why kdevelop wants to have -fno-exceptions in
> the CXXFLAGS. Any ideas? I removed it manually from configure, so now I
> can at least compile with <hamlib/rigclass.h> included.

no clue. I'm not an expert in C++. Anyone?

> Kontakt has an own static class RigCaps with member functions that do a
> get_rig_caps(rig_model_t) and return one specific value: A few
> things I need to show the user before selecting a device: mfg_name,
> model_name, rig_type, and a QString containing a textual representation of
> the status (alpha, ...). Or does hamlib(++) already supply this and I
> missed it?

I don't think so. But it would sure make others happy if such facilities
were present in hamlib(++). IMO, the textual representation
of status/mode/etc. should be in hamlib, no doubt. For the other functions,
let me have a look at your class RigCaps, and I'll see where it belongs.
Anyone is free to patch too.

> Config file in hamlib: I think the user would get too much "involved" with
> the lib, which should only be a background thing for the "real app". The
> user should be able to install a new rpm at any time without having to
> look for some config file somewhere. And, he has to do some settings in
> the application anyway, so put it all in there, even though he will have
> to enter the same data once(!) in each app.

Or at least, Hamlib should offer all the primitives to manage configuration
file?

> How do I find out which device need which specific settings? Like
> baudrate, target IP address, etc. What is the struct confparams in rig.h?
> I am focussing completely on the <hamlib/*.h> includes and not really
> reading the hamlib source much (stupid app writers shouldn't have to
> anyway :))

I agree with you, and that's the point of having documentation. 
On this regard, the in-source documenting should be more verbose
in the set_conf/get_conf section. In the meantime, have a look
at src/conf.c. Right now, only "rig_pathname", "write_delay" and alike
are available. Baud rate and such should be added in there...
 
> >   Yep, as soon as I have downloaded the 8MB+ for the qt upgrade...
> 
> Which upgrade? This is Qt2-stuff, I'm not using Qt3 here.

The libqt-dev package depends on a newer libqt2, and a zillon of other
libraries. This will be done this week-end.

BTW, I'm going right now /P out-door (friday off, thanks to french "35 hours").
From time to time, I'll be calling CQ Hamlib on 21.250MHz..

73, Stephane - F8CFE

Re: [Hamlib-developer] what's up?

[<rs...@su...>]

On Thu, 11 Oct 2001, Stephane Fillod wrote:

> 	You'll need automake 1.5. Otherwise, you may have a chance
>  in regenerating all the .in files.

automake && ./configure && make install
works. Strange.

> > Sorry, but I still haven't tested our IC275 and 475 at home. Have to find
> > the old self-built interface first and then visit mom (DK3XJ) :)
> >
>   Great! She will be happy to see you, but first wait IC275 and 475
>   are added..

Oops... isn't it a C-IV device as well? I really have to get that stuff
out of the box on the shelf :-)

> 	Let me know if some functions are missing in Hamlib, or if you
>   think the design is not appropriate. Accessing the caps/state directly is
>   recommanded, instead set_conf/get_conf should be used, provided more
>   parameters are declared (yet to be done). Maybe there should be some
>   config data file support in Hamlib, regardless the application.
>   What do you think?

I am trying to figure out why kdevelop wants to have -fno-exceptions in
the CXXFLAGS. Any ideas? I removed it manually from configure, so now I
can at least compile with <hamlib/rigclass.h> included.

Kontakt has an own static class RigCaps with member functions that do a
get_rig_caps(rig_model_t) and return one specific value: A few
things I need to show the user before selecting a device: mfg_name,
model_name, rig_type, and a QString containing a textual representation of
the status (alpha, ...). Or does hamlib(++) already supply this and I
missed it?

Config file in hamlib: I think the user would get too much "involved" with
the lib, which should only be a background thing for the "real app". The
user should be able to install a new rpm at any time without having to
look for some config file somewhere. And, he has to do some settings in
the application anyway, so put it all in there, even though he will have
to enter the same data once(!) in each app.

How do I find out which device need which specific settings? Like
baudrate, target IP address, etc. What is the struct confparams in rig.h?
I am focussing completely on the <hamlib/*.h> includes and not really
reading the hamlib source much (stupid app writers shouldn't have to
anyway :))

>   Yep, as soon as I have downloaded the 8MB+ for the qt upgrade...

Which upgrade? This is Qt2-stuff, I'm not using Qt3 here.

Enough for today, more tmrw.

73, Robert
-- 
Robert Steinhaeusser, DL1NC / N9KBK                         rs...@su...
http://1409.org                                   ro...@st...

Re: [Hamlib-developer] what's up?

[Stephane F. <f4...@fr...>]

On Wed, Oct 10, 2001, Robert Steinhäußer wrote:
> My today's copy from the CVS doesn't, though. After some disk scratching,
> it says:
> 
> Making all in lib
> make[1]: Entering directory `/usr/src/hamlib/lib'
> Makefile:166: *** missing separator.  Stop.
> make[1]: Leaving directory `/usr/src/hamlib/lib'
> make: *** [all-recursive] Error 1
> 
> I'm using autoconf 2.52, automake 1.4-p5 and libtool 1.4.1.
> 
	You'll need automake 1.5. Otherwise, you may have a chance
 in regenerating all the .in files.

> Sorry, but I still haven't tested our IC275 and 475 at home. Have to find
> the old self-built interface first and then visit mom (DK3XJ) :)
> 
  Great! She will be happy to see you, but first wait IC275 and 475 
  are added..

> I'm working on my 'Kontakt' project (a GUI frontend for hamlib). Well, now
> I know a lot more about C++ (and differences to C, like using member
> functions for callback purposes... brrr!) and can actually give you a tree
> view of all devices supported by hamlib. A rig can be selected in the list
> (a subclass of QListViewItem now stores the rig_model_t entry), but that's
> about it right now. No actual controls yet, first I want to have the
> config data saved to/retrieved from the config file (hopefully this week).
 
	Let me know if some functions are missing in Hamlib, or if you
  think the design is not appropriate. Accessing the caps/state directly is
  recommanded, instead set_conf/get_conf should be used, provided more
  parameters are declared (yet to be done). Maybe there should be some
  config data file support in Hamlib, regardless the application.
  What do you think?

> If you *really* want to try it: http://sf.net/projects/kontakt -> cvs
> instructions. But please give me some feedback.

  Yep, as soon as I have downloaded the 8MB+ for the qt upgrade...

Cheers,
Stephane - F8CFE

Re: [Hamlib-developer] new to project--want to help

[<rs...@su...>]

On Wed, 10 Oct 2001, Stephane Fillod wrote:

> I've made a quick search about the ICOM T81A, and it turns out that
> this rig has only the ability to be cloned, in other words, it can
> only be memory programmed. It's not possible to control the rig,
> like changing VFOs, setting functions, get signal strength.
> But I might me wrong. Do you have some kind of documentation available
> in the manual?

I have a Yaesu FT51R. I also can only be cloned, via the 3.5mm jack on
top. I just checked the BBS, OM8ACE had some info on the technique
(9600Bd 3V/0V, ca. 3000 bytes of data). I asked him to mail me any other
info he's got :-)

73, Robert
-- 
Robert Steinhaeusser, DL1NC / N9KBK                         rs...@su...
http://1409.org                                   ro...@st...

Re: [Hamlib-developer] what's up?

[<rs...@su...>]

Hello out there,

On Mon, 8 Oct 2001, Stephane Fillod wrote:

> I haven't heard about you since the release of hamlib-1.1.2. I hope
> everything's fine on your side. I hardly believe 1.1.2 is so stable
> that you haven't had to report bugs :)

Well, it compiles without problems :-)

My today's copy from the CVS doesn't, though. After some disk scratching,
it says:

Making all in lib
make[1]: Entering directory `/usr/src/hamlib/lib'
Makefile:166: *** missing separator.  Stop.
make[1]: Leaving directory `/usr/src/hamlib/lib'
make: *** [all-recursive] Error 1

I'm using autoconf 2.52, automake 1.4-p5 and libtool 1.4.1.

> Also, I'd love to hear from people succeeding in (or not) to run Hamlib
> with any rig except the IC706 and FT847 (the only truly tested),
> like the Kenwoods, the various receives, etc.

Sorry, but I still haven't tested our IC275 and 475 at home. Have to find
the old self-built interface first and then visit mom (DK3XJ) :)

> Any wishes? Comments? Feedback welcome!

I'm working on my 'Kontakt' project (a GUI frontend for hamlib). Well, now
I know a lot more about C++ (and differences to C, like using member
functions for callback purposes... brrr!) and can actually give you a tree
view of all devices supported by hamlib. A rig can be selected in the list
(a subclass of QListViewItem now stores the rig_model_t entry), but that's
about it right now. No actual controls yet, first I want to have the
config data saved to/retrieved from the config file (hopefully this week).

If you *really* want to try it: http://sf.net/projects/kontakt -> cvs
instructions. But please give me some feedback.

73, Robert
-- 
Robert Steinhaeusser, DL1NC / N9KBK                         rs...@su...
http://1409.org                                   ro...@st...

Re: [Hamlib-developer] new to project--want to help

[Stephane F. <f4...@fr...>]

Hi Larry,


Welcome in the Hamlib team!

> My motivation in subscribing to the list come from owning an ICOM T81A and 
> finding the software/hardware necessary for programming the radio a bit 

I've made a quick search about the ICOM T81A, and it turns out that
this rig has only the ability to be cloned, in other words, it can
only be memory programmed. It's not possible to control the rig,
like changing VFOs, setting functions, get signal strength.
But I might me wrong. Do you have some kind of documentation available
in the manual?

> the radio, imho which would more than outweigh offering necessary items as 
> accesories for additional payment.

If only they would make the protocol specifications available.. 
However, some manufacturers do.

> My background is in information technology.  My radio interests are 
> homebrewing, both with tubes and silicon,  and 6 meter band communications.

The magic band is fun, and quite exciting for the least!
 
> I am not sure, at this point, if the control codes for the ICOM T81A are 
> available or how they compare to the HF rigs this company makes.  I realize 

Well, it looks like the ICOM T81A is not using the CI-V protocol.
Do you have some protocol specifications coming along with your manual?
Hamlib is not supporting any "clonable" rig yet, but through 
the rig_set_channel() and rig_get_channel(), this would be quite easy.
Maybe some rig_mem_sync() to cope with whole memory only bank transfer
would help. To be designed..

> the control codes in a case by case fashion.  So this project is a 
> commendable example of putting the horse before the cart, in my opinion.

Well, thank you. The Hamlib team is pleased to hear that, even though
there's still lot of work to be done (esp. testing on different rigs). 
We hope to see plenty of user applications using Hamlib. Some of them
are already working on it: kontakt, groundstation, etc.

Cheers,
Stephane / F8CFE

Re: [Hamlib-developer] new to project--want to help

[Nate B. <n0...@ne...>]

On Tue, Oct 09, 2001 at 10:16:29AM -0400, Larry Braden wrote:
> Hello,
> 
> My name is Larry Braden.
> 
> I would like to help with this project, however I am not sure at this point 
> in what capacity.  I will be looking over the work that is done so far.

Hi Larry.

Welcome to Hamlib!  I'm sure Stephane has a number of things to be done,
not all of which require knowledge of C programming.  Just testing and
trying to get things going on your radio is often a big help.

> My motivation in subscribing to the list come from owning an ICOM T81A and 
> finding the software/hardware necessary for programming the radio a bit 
> expensive and, to say the least, I am a bit miffed that the software, at 
> least, is not offered free by the company.  When one buys a radio that is 
> capable of being controlled and/or programmed by a computer --almost a 
> necessity given the features in some cases-- then it should be included.  To 
> include the software and/or programming cables would help sell more units of 
> the radio, imho which would more than outweigh offering necessary items as 
> accesories for additional payment.
> 
> Additionally, I believe that linux--in particular--offers users of ham radios 
> and computer hardware a great deal of freedom to come up with new, more 
> convenient and powerful, means to do high performance radio.  What hams 
> actually do with radios is not always anticipated by radio manufacturers.

Ahhh, we of like minds.  Welcome to the world of Free Software--an
often loud and somewhat intimidating place (if judged by sites like
Slahsdot).  However, the noise is often passion expressed and in the end 
the code speaks for itself.

> My background is in information technology.  My radio interests are 
> homebrewing, both with tubes and silicon,  and 6 meter band communications.

I have a similar background although different ham interests, such as a
bit of contesting, public service, digital, and FM/repeaters to name a
few.

> I am not sure, at this point, if the control codes for the ICOM T81A are 
> available or how they compare to the HF rigs this company makes.  I realize 
> that this project is dealing primarily with creating a user interface library 
> for developing rig control applications, and that the rig control codes sent 
> to the radio are at another level of an application.   These control codes 
> are accessed as needed and appropriate by the application and the user 
> interface, and thus by switching the codes a generalized user interface 
> library can be used to control almost any radio device.  Very good idea for a 
> number of reasons, and I can see that this would make the development of 
> applications go much faster rather than trying to hang the user interface off 
> the control codes in a case by case fashion.  So this project is a 
> commendable example of putting the horse before the cart, in my opinion.

Actually, this project is focusing on communicating directly with the
radio (or other controllable hardware, rotors, etc.) and providing an 
abstracted rig API.  So, whatever command info you can provide on your 
radio (providing Stephane needs it!) is most welcome.  This isn't a 
flashy project.  Rather it is low level backend type stuff, but for 
folks who like tinkering with hardware too, it's an interesting
project.

I jumped in and volunteered to work on the Web pages and the Hamlib
reference docs.  The Web pages are reasonably up-to-date, but the manual
is a couple of versions behind.  Your feedback to me on these items
would be most helpful, especially the part about getting Hamlib from
CVS in Chapter 1.

Stephane has been doing most of the coding of late.  We haven't heard
from Frank in a while and understand he is quite busy.  Terry has done a
nice job with the Debian packages.  I'm quite busy right now, but the 
weather is supposed to be a bit rainy around here which may give me 
some extra time the next few days to work on the manual.  

73, de Nate >>

-- 
 Wireless | Amateur Radio Station N0NB          | "We have awakened a
 Internet | n0...@ne...               | sleeping giant and
 Location | Bremen, Kansas USA EM19ov           | have instilled in him
   Wichita area exams; ham radio; Linux info @  | a terrible resolve".
             http://www.qsl.net/n0nb/           | - Admiral Yamomoto

[Hamlib-developer] new to project--want to help

[Larry B. <lb...@ho...>]

Hello,

My name is Larry Braden.

I would like to help with this project, however I am not sure at this point 
in what capacity.  I will be looking over the work that is done so far.

My motivation in subscribing to the list come from owning an ICOM T81A and 
finding the software/hardware necessary for programming the radio a bit 
expensive and, to say the least, I am a bit miffed that the software, at 
least, is not offered free by the company.  When one buys a radio that is 
capable of being controlled and/or programmed by a computer --almost a 
necessity given the features in some cases-- then it should be included.  To 
include the software and/or programming cables would help sell more units of 
the radio, imho which would more than outweigh offering necessary items as 
accesories for additional payment.

Additionally, I believe that linux--in particular--offers users of ham radios 
and computer hardware a great deal of freedom to come up with new, more 
convenient and powerful, means to do high performance radio.  What hams 
actually do with radios is not always anticipated by radio manufacturers.

My background is in information technology.  My radio interests are 
homebrewing, both with tubes and silicon,  and 6 meter band communications.

I am not sure, at this point, if the control codes for the ICOM T81A are 
available or how they compare to the HF rigs this company makes.  I realize 
that this project is dealing primarily with creating a user interface library 
for developing rig control applications, and that the rig control codes sent 
to the radio are at another level of an application.   These control codes 
are accessed as needed and appropriate by the application and the user 
interface, and thus by switching the codes a generalized user interface 
library can be used to control almost any radio device.  Very good idea for a 
number of reasons, and I can see that this would make the development of 
applications go much faster rather than trying to hang the user interface off 
the control codes in a case by case fashion.  So this project is a 
commendable example of putting the horse before the cart, in my opinion.

Best wishes,

Larry Braden
KC5CWG
Catonsville, Maryland

[Hamlib-developer] what's up?

[Stephane F. <f4...@fr...>]

Hi fellows,

I haven't heard about you since the release of hamlib-1.1.2. I hope
everything's fine on your side. I hardly believe 1.1.2 is so stable
that you haven't had to report bugs :)
Also, I'd love to hear from people succeeding in (or not) to run Hamlib
with any rig except the IC706 and FT847 (the only truly tested),
like the Kenwoods, the various receives, etc.

New stuff's coming out. Actualy I've commited a first version of
the RPC backend, which is nothing else that what anyone would expect
to have running on a desktop to share a rig among applications.
Well, right now, only set_freq and get_freq work, but it's a start.
This was just a proof of concept, and it works!
Just run "rpc.rigd" with appropriate args (similar to rigctl, -vvvv helps) 
and use the model 1901 on the client side, regardless how many 
they could be, and you're in business!
Any wishes? Comments? Feedback welcome!

Cheers,
Stephane / F8CFE

PS: fine work Terry on the Debian packages! Do you want to commit the
    scripts in the debian/ subdirectory?

[Hamlib-developer] Re: New web pages

[Stephane F. <f4...@fr...>]

Hi Nate!

> The way I see it, the document source is GPL just like program source
> and the formatted result, HTML, PDF, whatever is analogous to a binary
> program.  We don't modify the binary, but the source and it's the same
> with Docbook.  So, I think I shall stick with the GPL for now.
> 
> That covers my thoughts on the manual.  As for the web pages, they're
> nothing spectacular so if folks want to use bits that's just fine and
> I'm sure the GPL is a reasonable choice there.

GPL is fine. I hardly remember there was some special case with editing books,
but that's not our aim.

> I downloaded the latest CVS and will add and commit the SGML tonight.  I
> plan to put it in the docs directory in a subdirectory of sgml (for lack
> of anything more imaginative).  Please tell me more about doxygen as
> I've not heard of it.
 
A subdirectory like "manual" would have been less confusing than sgml,
especially in regards of the html subdirectory. Anyhow, it's up to you.

About doxygen:
<<
Doxygen is a documentation system for C, C++ and IDL. It can generate an on-lineclass browser (in HTML) and/or an off-line reference manual (in LaTeX) from a
set of documented source files. There is also support for generating man pages
and for converting the generated output into Postscript, hyperlinked PDF or
compressed HTML. The documentation is extracted directly from the sources.
>>
In other words, it lets one document an API, program, etc. within the source
code. Have a look at src/rig.c, each "/**" statement will be interpreted
by doxygen, and generate some kind of output in the resulting manual.
The official doxygen web site is at http://www.doxygen.org
Provided doxygen is installed on you system, type "make doc" in the doc/
subdirectory, and doxygen will be executed with the file hamlib.cfg
as an argument. The Hamlib HTML manual and man pages are then generated 
in the html/ and man/ subdirectories.
Have a look at http://f4cfe.free.fr/ham/hamlib/doxygen/ for a glimpse of it.
I think these materials would fit perfectly (with some tune up, of course) 
with your SGML manual. Let me know what you think of it.

Cheers,
Stephane - F8CFE

[Hamlib-developer] Re: [ANN] Hamlib 1.1.2 released

[Terry D. <te...@an...>]

Stephane Fillod wrote:


> Hamlib-1.1.2 has been released. This version controls more radios,
> with an extended API to cover the capabilities commonly found on latest
> rigs. Also you'll be pleased to notice that Hamlib is now released
> under LGPL, see LICENSE for more info.

> Download pages are accessible at http://sourceforge.net/projects/hamlib
> i386 rpms available, .deb coming soon.


Debian packages are completed and available in the debian master incoming 
directory. They'll be in the standard Debian unstable distribution just as soon 
as the new hamlib-doc and hamlib-util packages are approved.

regards
Terry

RE: [Hamlib-developer] C-IV spec from Icom - it does exist!

[<dar...@bt...>]

Stephane,

Sadly I have a feeling the one I have is the same date. I'll check it anyway
and forward if newer.

Darren - G0WCW

-----Original Message-----
From: Stephane Fillod [mailto:f4...@fr...]
Sent: Tuesday, September 25, 2001 7:06 AM
To: Hamlib developers
Subject: Re: [Hamlib-developer] C-IV spec from Icom - it does exist!


On Mon, Sep 24, 2001, dar...@bt... wrote:
> I noted that Stephane said that we do not have the spec for the Icom C-IV
> interface from Icom. Well, I have a hard copy of what I think is missing.
It
> details what radio can do what (missing from ekki website in section 5).
 
Well, actually we have some kind of docs. Last year, Kai asked Icom
for some documentation. They refused to help us. But somehow, we managed
to get an old manual "Icom Communication Interface V, Reference Manual"
July 28, 1993. This manual is fine, except it covers only pretty old rigs.
Still helpful though.
In the case your hard copy is newer, and you are allowed to make copies
of it, I would be really interrested to have a glance over it!

Thanks,
Stephane - F8CFE

_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer

Re: [Hamlib-developer] C-IV spec from Icom - it does exist!

[Stephane F. <f4...@fr...>]

On Mon, Sep 24, 2001, dar...@bt... wrote:
> I noted that Stephane said that we do not have the spec for the Icom C-IV
> interface from Icom. Well, I have a hard copy of what I think is missing. It
> details what radio can do what (missing from ekki website in section 5).
 
Well, actually we have some kind of docs. Last year, Kai asked Icom
for some documentation. They refused to help us. But somehow, we managed
to get an old manual "Icom Communication Interface V, Reference Manual"
July 28, 1993. This manual is fine, except it covers only pretty old rigs.
Still helpful though.
In the case your hard copy is newer, and you are allowed to make copies
of it, I would be really interrested to have a glance over it!

Thanks,
Stephane - F8CFE

[Hamlib-developer] C-IV spec from Icom - it does exist!

[<dar...@bt...>]

All,

Thanks for the revision to the web-site - this is a great piece of work and
much appreciated!

I noted that Stephane said that we do not have the spec for the Icom C-IV
interface from Icom. Well, I have a hard copy of what I think is missing. It
details what radio can do what (missing from ekki website in section 5).

Although some of it looks like already in the public domain (and it is a few
years old now), I am able to scan in and convert for review (I trust this
won't cause copyright probs). Would this be of use to the team? Let me know
if it's needed and if so, I'll get it scanned at the weekend.

Regards,

Darren - G0WCW
-----Original Message-----
From: Stephane Fillod [mailto:f4...@fr...]
Sent: Monday, September 24, 2001 7:01 AM
To: Hamlib developers
Cc: Linux HAMs
Subject: [Hamlib-developer] [ANN] Hamlib 1.1.2 released



Good news everyone!

Hamlib-1.1.2 has been released. This version controls more radios,
with an extended API to cover the capabilities commonly found on latest
rigs. Also you'll be pleased to notice that Hamlib is now released
under LGPL, see LICENSE for more info.

There's a new web site at http://hamlib.sourceforge.net
Please take a break and stop by!

New in 1.1.2:
 * License converted to LGPL
 * new backends: Alinco (DX-77), Uniden (BC895),
		 Ten-Tec (RX320), Kachina (505DSP)
 * New port_t design, coming with easy rig auto-probe
 * mv_ctl replaced by vfo_op, set_vfo/get_vfo extended to RIG_VFO_MEM
 * set_conf/get_conf for opaque variable parameters setting
 * Better portability, esp. with libtool (DLL dlopen'ing works under Win32
!)
 * added C++ and tcl/tk bindings (not complete yet)
 * converted from hamlib-doc to doxygen in-source interface documenting

Download pages are accessible at http://sourceforge.net/projects/hamlib
i386 rpms available, .deb coming soon.

Plan for 1.1.3:
* Enter more models of supported backends
* rotor stuff
* support for network backends
* extend C++ bindings
* etc. (any wishes?)

Please, test it out and report to ham...@li...
Developers are also invited to join the Hamlib team by subscribing to this
mailing list.

Have fun and let us know!

73's de Stephane Fillod (f8cfe) 

_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer

[Hamlib-developer] [ANN] Hamlib 1.1.2 released

[Stephane F. <f4...@fr...>]

Good news everyone!

Hamlib-1.1.2 has been released. This version controls more radios,
with an extended API to cover the capabilities commonly found on latest
rigs. Also you'll be pleased to notice that Hamlib is now released
under LGPL, see LICENSE for more info.

There's a new web site at http://hamlib.sourceforge.net
Please take a break and stop by!

New in 1.1.2:
 * License converted to LGPL
 * new backends: Alinco (DX-77), Uniden (BC895),
		 Ten-Tec (RX320), Kachina (505DSP)
 * New port_t design, coming with easy rig auto-probe
 * mv_ctl replaced by vfo_op, set_vfo/get_vfo extended to RIG_VFO_MEM
 * set_conf/get_conf for opaque variable parameters setting
 * Better portability, esp. with libtool (DLL dlopen'ing works under Win32 !)
 * added C++ and tcl/tk bindings (not complete yet)
 * converted from hamlib-doc to doxygen in-source interface documenting

Download pages are accessible at http://sourceforge.net/projects/hamlib
i386 rpms available, .deb coming soon.

Plan for 1.1.3:
* Enter more models of supported backends
* rotor stuff
* support for network backends
* extend C++ bindings
* etc. (any wishes?)

Please, test it out and report to ham...@li...
Developers are also invited to join the Hamlib team by subscribing to this
mailing list.

Have fun and let us know!

73's de Stephane Fillod (f8cfe) 

[Hamlib-developer] Hamlib Web pages -- Version 2 online!

[Nate B. <n0...@ne...>]

Greetings Hamlib developers.

I have uploaded the initial group of what I'm calling Phase 2 of the
Hamlib Web pages.  They may be viewed at:

http://hamlib.sourceforge.net

Comments, critique, and improvements welcome.

A couple notes about the pages.

All the HTML is hand crafted, any errors are surely mine and I can't
(properly) blame some software.  I am srtiving to make the pages HTML
4.01 and CSS 1.0 compliant.  I've looked them over in Mozilla 0.9.4,
Netscape 4.77 and Lynx.  If something appears broken in your browser,
please let me know, but only if your browser is known to be CSS capable!

Things I am working on.

I have a bit of rework on the first Hamlib manual and hope to upload
versions in HTML, PS, and PDF formats.  After this is complete I plan to
update the manual for the upcoming 1.2.2 release.

73, de Nate >>

-- 
 Wireless | Amateur Radio Station N0NB          | "We have awakened a
 Internet | n0...@ne...               | sleeping giant and
 Location | Bremen, Kansas USA EM19ov           | have instilled in him
   Wichita area exams; ham radio; Linux info @  | a terrible resolve".
             http://www.qsl.net/n0nb/           | - Admiral Yamomoto

Re: [Hamlib-developer] last chance before next release

[Nate B. <n0...@ne...>]

On Thu, Sep 20, 2001 at 10:56:48PM +0200, Stephane Fillod wrote:
> Hi everyone,
> 
> Terry, could you check everything is ready to build the .deb package?
> Also the Hamlib web site would need one volunteer to update the page,
> anyone? 

I'll do what I can with the web pages as I'm on the verge of getting
some time to get back to that.

73, de Nate >>

-- 
 Wireless | Amateur Radio Station N0NB          | "We have awakened a
 Internet | n0...@ne...               | sleeping giant and
 Location | Bremen, Kansas USA EM19ov           | have instilled in him
   Wichita area exams; ham radio; Linux info @  | a terrible resolve".
             http://www.qsl.net/n0nb/           | - Admiral Yamomoto

[Hamlib-developer] last chance before next release

[Stephane F. <f4...@fr...>]

Hi everyone,

I finally managed to get libtool working on my system. It seems like
starting from libtool-1.4.?, lt_dlopen needs to open the .la file
instead of the .so file.
Anyway, it looks fine now. After some cleanup, Hamlib should be ready
to be released this week-end under version 1.1.2. 
Please test the CVS version as much as you can, and report on this list.

Terry, could you check everything is ready to build the .deb package?
Also the Hamlib web site would need one volunteer to update the page,
anyone? 

Cheers,
Stephane - F8CFE

Re: [Hamlib-developer] Get/set memories?

[Stephane F. <f4...@fr...>]

On Tue, Sep 18, 2001, John Roberts wrote:
> Can I get and set the contents of the memory channels with hamlib? I have an 
> Icom 756Pro.

yep, rig_get_channel amd rig_set_channel should meet your needs.
Have a look at tests/dumpmem.c for an idea on how to use them.
However, as far as I remember, I haven't coded already the support
for the channel name for the 756Pro. The emulation code should work
fine though.
Contribution welcome!

Cheers,
Stephane

Re: [Hamlib-developer] Resource temporarily unavailable?

[Stephane F. <f4...@fr...>]

On Tue, Sep 18, 2001, John Roberts wrote:
> I'm hacking up testrig to try and put together an app to talk to my Icom 
> 756Pro. Below is the code and the output that I get. Any idea why I see 
> "Resource temporarily unavailable"?
 
Your program is fine. The problem lies with the poor robustness
of the current Icom backend (yeah, that's on my TODO list). 
To make a long story short, CI-V protocol uses a CSMA/CD bus system,
with TXD and RXD tied together. That's why when the backend
send "ff fe fe 5c e0 07 00 fd", it has to read (ie. empty)
what it just sent, before expecting the reply from the rig.
However, it looks like the receive ibuffer should be drained beforehand.
Right now, I don't know what the best solution. Anyway, read on...

> TX 8 bytes
> 0000	 ff fe fe 5c e0 07 00 fd	...\....
> RX 8 bytes
> 0000	 e0 07 00 fd fe fe e0 5c	.......\
         ^^^^^^^^^^^  ^^^^^^^^^^
 end of previous cmd     begining of the reply

> rig timeout after 2 chars or select error - Resource temporarily 
> unavailable!
> rig timeout after 0 chars or select error - Resource temporarily 
> unavailable!

oh, wait, I'm not sure, but I think I fixed this in the CVS repository,
which is the forthcoming Hamlib-1.1.2 (hopefully by next week). 
Can you checkout the CVS version and give it a try?

The other explanation could be the so-called transceive mode, i.e. the rig
which is sending asynchronously "events" notification. But according to
the traces, it's not likely.

As you can see, Hamlib is still in ALPHA stage, and badly needs programers
(I'm doing this on my spare time). Anyway, testers are more than needed too!

Cheers,
Stephane

[Hamlib-developer] Non-reproducable results?

[John R. <js...@ho...>]

Why if I run my little test program twice in a row do I not get the same 
result each time? All I'm doing is asking for the signal strength.

jroberts@scif44ab(~/jroberts/src/ic756pro) 124$ make run
make: *** Warning: File `makefile' has modification time in the future 
(2001-09-18 13:44:15 > 2001-09-18 13:41:37)
export LD_LIBRARY_PATH=../hamlib-1.1.1/src/.libs:../hamlib-1.1.1/icom/.libs
./testrig
(testrig.c:26) rig_load_backend
rig: loading backend icom
icom: _init called
rig_register (43)
rig_register (44)
rig_register (45)
rig_register (76)
rig_register (34)
(testrig.c:34) rig_init
rig:rig_init called
(testrig.c:45) rig_open
rig:rig_open called
Unsupported PTT type 1
TX 8 bytes
0000     ff fe fe 5c e0 15 02 fd        ...\....
RX 8 bytes
0000     ff fe fe 5c e0 15 02 fd        ...\....
RX 6 bytes
0000     fe fe e0 5c 15 02      ...\..
RX 1 bytes
0000     01     .
RX 1 bytes
0000     62     b
RX 1 bytes
0000     fd     .
get_level: 2 162 162 0.000000
rig_get_strength: strength = 162
rig:rig_close called
Unsupported PTT type 1
rig:rig_cleanup called
make: warning:  Clock skew detected.  Your build may be incomplete.



jroberts@scif44ab(~/jroberts/src/ic756pro) 125$ make run
make: *** Warning: File `makefile' has modification time in the future 
(2001-09-18 13:44:15 > 2001-09-18 13:41:47)
export LD_LIBRARY_PATH=../hamlib-1.1.1/src/.libs:../hamlib-1.1.1/icom/.libs
./testrig
(testrig.c:26) rig_load_backend
rig: loading backend icom
icom: _init called
rig_register (43)
rig_register (44)
rig_register (45)
rig_register (76)
rig_register (34)
(testrig.c:34) rig_init
rig:rig_init called
(testrig.c:45) rig_open
rig:rig_open called
Unsupported PTT type 1
TX 8 bytes
0000     ff fe fe 5c e0 15 02 fd        ...\....
RX 8 bytes
0000     e0 15 02 fd fe fe e0 5c        .......\
rig timeout after 5 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
make: *** [run] Interrupt

jroberts@scif44ab(~/jroberts/src/ic756pro) 126$

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

[Hamlib-developer] Resource temporarily unavailable?

[John R. <js...@ho...>]

Hi,

I'm hacking up testrig to try and put together an app to talk to my Icom 
756Pro. Below is the code and the output that I get. Any idea why I see 
"Resource temporarily unavailable"?





int main(int argc, char *argv[])
{
  RIG *my_rig;                  /* handle to rig (nstance) */
  freq_t freq;                  /* frequency  */
  rmode_t rmode;                /* radio mode of operation */
  pbwidth_t width;
  vfo_t vfo;                    /* vfo selection */
  int strength;                 /* S-Meter level */
  int retcode;                  /* generic return code from functions */


  fprintf(stdout, "(%s:%d) rig_load_backend\n", __FILE__, __LINE__);
  retcode = rig_load_backend("icom");
  if (retcode != RIG_OK)
  {
    printf("rig_load_backend: error = %s \n", rigerror(retcode));
    return -1;
  }

  fprintf(stdout, "(%s:%d) rig_init\n", __FILE__, __LINE__);
  my_rig = rig_init( 34 );
  if (!my_rig)
  {
    fprintf(stderr, "Unknown rig num: %d\n", atoi(argv[1]));
    fprintf(stderr, "Please check riglist.h\n");
    return -1;
  }

  strncpy(my_rig->state.rig_path, SERIAL_PORT, FILPATHLEN);

  fprintf(stdout, "(%s:%d) rig_open\n", __FILE__, __LINE__);
  if (rig_open(my_rig))
  {
    return -1;
  }

  sleep(1);

  fprintf(stdout, "(%s:%d) rig_set_vfo\n", __FILE__, __LINE__);
  retcode = rig_set_vfo(my_rig, RIG_VFO_A);
  if (retcode != RIG_OK)
  {
    printf("rig_set_vfo: error = %s \n", rigerror(retcode));
  }

  retcode = rig_get_strength(my_rig, RIG_VFO_CURR, &strength);
  if (retcode == RIG_OK)
  {
    printf("rig_get_strength: strength = %i \n", strength);
  }
  else
  {
    printf("rig_get_strength: error =  %s \n", rigerror(retcode));
  }

  retcode = rig_get_vfo(my_rig, &vfo); /* try to get vfo info */
  if (retcode == RIG_OK)
  {
    printf("rig_get_vfo: vfo = %i \n", vfo);
  }
  else
  {
    printf("rig_get_vfo: error =  %s \n", rigerror(retcode));
  }

  rig_close(my_rig);            /* close port */
  rig_cleanup(my_rig);          /* if you care about memory */

  return 0;
}

export LD_LIBRARY_PATH=../hamlib-1.1.1/src/.libs:../hamlib-1.1.1/icom/.libs
./testrig
rig: loading backend icom
icom: _init called
rig_register (43)
rig_register (44)
rig_register (45)
rig_register (76)
rig_register (34)
rig:rig_init called
rig:rig_open called
Unsupported PTT type 1
TX 8 bytes
0000	 ff fe fe 5c e0 07 00 fd	...\....
RX 8 bytes
0000	 e0 07 00 fd fe fe e0 5c	.......\
rig timeout after 2 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
rig timeout after 0 chars or select error - Resource temporarily 
unavailable!
icom_set_vfo: ack NG (0xfe), len=373
make: *** [run] Segmentation fault (core dumped)

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

[Hamlib-developer] Get/set memories?

[John R. <js...@ho...>]

Hi,

Can I get and set the contents of the memory channels with hamlib? I have an 
Icom 756Pro.

Thanks,
John

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

[Hamlib-developer] Re: hamlib++

[Stephane F. <f4...@fr...>]

[this reply has been Cc: to hamlib-developer]

Hi Robert!

> Finally I am running the CVS version of the lib. In my opinion, there are
> many improvements to the lib. You should think of releasing 1.1.2 (or even

I would love to. Unfortunately, libtool seems borken (1.4b2, 1.4.1).
Symptoms are strange.
On my system, during test phase, I do not issue a make install. 
Actually, I'm just setting up LD_LIBRARY_PATH to the various .libs 
subdirectory of each backend and that used to do it. 
However, with recent version of libtool, libltdl does not find 
the .so modules. It looks like I need to provide 2 times the same path
in LD_LIBRARY_PATH to make it work. Well, after all, this must be
the *bleeding* edge of the unstable dist of Debian.

Let's say if libtool is not fixed by next week, I'll downgrade it to 1.4,
loosing temporarly the win32 portability, and make things going on.

> 1.2.0) soon. I am basing my work on hamlib++, which is much more like the
> things I have learned at university (we only do oop on Java there). The
> class-encapsulation should make things a lot easier for application
> programmers (like me :-)).

Like everyone!  hamlib++ is far from complete though..

> Actually, it got on my nerves having to hard-code all backends (1.1.1) and
> calling them in a for loop, then rig_init() the device.
> rig_load_all_backends() was a first step, but I still prefer just creating
> an instance of the desired Rig. Let the lib to the dirty job :-)

yeah, Hamlib 1.1.2 is supposed to take care of that, with automagical
loading (at the cost of riglist.h maintainance).

> There is one thing I have not found out yet: How can I get a list of
> _currently_ supported rigs? I would like to let the user choose his rig
> from a runtime-generated list of available rigs. A list of int values
> should be enough, then I could run through the list and retrieve the
> description strings (but if would be nice to get both at once :-)

Just imagine you dream comes true! Have a look at tests/listrigs.c
This is quite simple. You need to load all the backends, then
rig_list_foreach() will call one of your function for each registered
cap. Simple, effective. (at the cost of loading every backend).

> As far as I could see, the ft847 backend only supports writing to
> the trx. I cannot retrieve data from it. The handbook says how it works,
> but I have not looked at the code that much.

Frank hasn't had enough time to complete the ft847 backend.
He was in the middle of the process of making the backend more generic.
You're more than welcome to get it further. I can help you if you'd like to.

> Last weekend I have spoken with some hams who work with the
> "Funkmessdienst" (those guys who drive around and scan for
> RF troublemakers). He heard of the hamlib and maybe can get me
> access to some Rohde&Schwarz equipment (it has a TCP/IP interface).

That's great! Before having access to the equipment itself, is there
any kind of documentation or a manual about the protocol used 
by these beasts?
 
> How generic do you want the hamlib to become? Rigs, antenna rotors
> planned. I remembered a multimeter of a friend of mine. It has an RS232
> interface. Not sure what it is capable of, though. Perhaps a digi sysop
> wants to read some pins of his serial port. Is that possible? Is it
> desired? Just thinking...

Well, that's for sure I'd like to see Hamlib generic. However, there's no
point in supporting coffee machines in this lib (even though this would
be fun if not useful). So, to my mind, rigs, antenna, frequency counters
like the ones from Optoelectronics, are fine. There's already a freegps
project, so that's all I can see for now. If you have any other idea,
please let us know. But rigs are already dense enough...
 
> 73, Robert
> -- 
> Robert Steinhaeusser, DL1NC / N9KBK                         rs...@su...
> http://1409.org                                   ro...@st...


73, Stephane

[Hamlib-developer] Re: Ham lib errors

[Stephane F. <f4...@fr...>]

Hi John,

On Mon, Sep 17, 2001, ROBERTS,JOHN (A-USA,ex1) wrote:
> I have an Icom 756 Pro connected via IcomCT-17 to a laptop running RedHat
> 7.1.
> 
> Is there a mailing list for hamlib?

yep, this is <ham...@li...>
This reply has been Cc'd to it. I hope you won't mind.

> When I run testrig I get these errors. Any idea where I should look to fix
> them?

The problem lies with the wrong CI-V address Hamlib is using with your 756PRO.
It looks like you selected "icall" backend, which is a good choice,
however, the icall backend is using the 706MkIIg as a default CI-V address.
The easiest fix (read ugly hack), is to edit line 58 of icom/icall.c
and change 0x58 to 0x5c.
Recompile, and give it another try. That should do it.

> jroberts@scif44ab(/mnt/geiswd/home/jroberts/src/hamlib-1.1.1/tests) 94$
> ./testrig 34
> testrig:hello, I am your main() !
> rig: loading backend icom
> icom: _init called
> rig_register (43)
> rig_register (44)
> rig_register (45)
> rig_register (76)
> rig_register (34)
> Calling init
> rig:rig_init called 
> After init
> Calling rig_open
> rig:rig_open called 
> Unsupported PTT type 1
> Port /dev/usb/ttyUSB0 opened ok
> TX 8 bytes
> 0000     ff fe fe 58 e0 07 01 fd        ...X....
                    ^^
  This is the rig address. The 756PRO has default set to 5c. That's why
it's not responding to simple command transmitted. With the change in icall.c,
this field should change, and also you should expect some reply...

> rig timeout after 7 chars or select error - Resource temporarily
> unavailable!
> rig timeout after 0 chars or select error - Resource temporarily
> unavailable!
> rig timeout after 0 chars or select error - Resource temporarily
> unavailable!
> icom_set_vfo: ack NG (0x07), len=2
> rig_set_vfo: error = Command rejected by the rig 
[snip]

Hamlib-1.1.2, which is expected to be release soon (as soon as I get
this #$%@$ libltl fixed properly), has a much cleaner approach
to cope with CI-V addresses (which are specific to the Icom backend).
This will be rendered possible through the following setup
between the rig_init() and rig_open() calls:

	token_t tok = rig_token_lookup(my_rig, "civaddr");
	rig_set_conf(my_rig, tok, "92");	/* 92 is decimal for 0x5c */

BTW, I noticed you're using a USB serial port. Since I've never tested
Hamlib with such a serial port, please let me know how it works.
Also, any feedback on the Icom backend and your IC-756PRO is welcome.
Commits to the CVS rep are pending, this rig will be supported in Hamlib-1.1.2.
This version has also a far better "rigctl" tool.

Cheers,

Stephane - F8CFE