hamlib-developer — hamlib developers forum

Re: [Hamlib-developer] Musings on backend behavior

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

On Sat, Nov 30, 2002, Nate Bargmann wrote:
 
> As I've worked on the backend library for the FT-920 a number of the
> warts and quirks of the radio are exposed through the frontend library
> to the application.  Really, I think this is incorrect as Hamlib should
> hide these things from the application.

Like what? Can you give some example?

> So, what I would like to see in the API documentation is a description
> of the expected behavior of the function at hand.  While this is often
> obvious, some things are more subtle and I would like a more defined
> target to work toward.

I'd love such documentation exists. Unfortunately, the only thing I can
do, is to reply the best I could to question when they are asked.
Writing specification, as valuable as it can be, is time consuming when
done alone. Any volunteer?

> Thus I think a firm definition of the virtual radio Hamlib presents to
> the application would be a big help to authors on each side of the
> frontend.
 
Sure a written definition is much needed! 

So far, it has not been done because:
- lack of time and lust
- developers tend to prefer to develop rather than write documentation,
  especially when they do this as a hobby
- the design of the API is not complete yet. It has to cover all the rig
  combinations over there. BTW I'm still not satisfied with the vfo_t.
  It may look silly to document something that's going to change in
  the near future, waste of energy.

So let's be pragmatic. Everyone is encouraged to submit comments on
existing flaws,limitations,.., and how they see the API should be designed,
point by point.

The resulting API documentation is to be put in the doxygen comments, and
also in the docbook manual.


Stephane

Re: [Hamlib-developer] rigctl options

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

Hi Nate!

> I noticed that in the latest update of rigctl several more options were
> added that use the characters 0x80 through 0x84.  These show only as a

yeah, we're running short of alphabetical characters. Maybe special characters
would be better than 8-bit chars.

> query (?) on my screen and I'm not sure how to access these functions.
> I was patching my local copy with the numeral 1 for the option to
> dumpcaps so I could access it.  These are extended characters that I can
> create in DOS, but they throw me in Bash.
> 
> What am I missing?

The man page? :)

Okay, this one was not very clear. Every command has short and long
name. For example, if you want to se the frequency, you can enter 'F' at
the rigctl prompt, but you can also do it the long way by entering
'\set_freq'. Note the backslash that prepend the long command name.
This way, you should be able to '\get_xit' or '\set_ant' even though
there's no short name.
Note: it is also possible to use rigctl in a non-interactive manner:

	rigctl -m xxx -r /dev/ttyS1 set_xit 0 set_mode CW 500

73
Stephane

Re: [Hamlib-developer] IC737 in hamlib-1.1.4-cvs-021128

[<al...@ph...>]

Hi Sid,

> GConfClient-WARNING **: Directory `/apps/gpredict' was not being
> monitored by GConfClient 0x80aa518

It looks like you even caught a silly bug in grig... Thanks.

Alex
OZ9AEC

[Hamlib-developer] IC737 in hamlib-1.1.4-cvs-021128

[Sid B. <sb...@bl...>]

	I get the usual "timed out messages". If I change ic775.c ID to "0x3c",
I can display/set mode and frequency - just as before. If you need any
further information, please shout.

	Error messages when I select IC737 as the rig.
-----------------------------------------------------------
barrabas:/usr1/HAMRADIO/hamlib-1.1.4-cvs-021128 # grig&
[4] 17283
barrabas:/usr1/HAMRADIO/hamlib-1.1.4-cvs-021128 # rig:rig_init called
rig: loading backend icom
icom: _init called
rig_register (309)
rig_register (310)
rig_register (311)
rig_register (313)
rig_register (319)
rig_register (321)
rig_register (330)
rig_register (326)
rig_register (327)
rig_register (347)
rig_register (334)
rig_register (344)
rig_register (335)
rig_register (340)
rig_register (342)
rig_register (304)
rig_register (307)
rig_register (352)
rig_register (353)
rig_register (351)
rig:rig_open called

** WARNING **: gnome_hamlib_rig.c: Could not get power status from RIG.


** WARNING **: gnome_hamlib_rig.c: Could not get mode and pbwidth from
RIG.

read_string: timedout without reading a character

** WARNING **: gnome-hamlib-rig.c: Could not get frequency.


GnomeUI-WARNING **: Could not open help topics file NULL
read_string: timedout without reading a character
read_string: timedout without reading a character
read_string: timedout without reading a character
read_string: timedout without reading a character
read_string: timedout without reading a character
read_string: timedout without reading a character

** WARNING **: gnome-hamlib-rig.c: Could not get mode and pbwidth.

read_string: timedout without reading a character

** WARNING **: gnome-hamlib-rig.c: Could not set mode. Trying to reset.

read_string: timedout without reading a character
read_string: timedout without reading a character

** WARNING **: gnome-hamlib-rig.c: Could not get mode and pbwidth.

read_string: timedout without reading a character

** WARNING **: gnome-hamlib-rig.c: Could not set mode. Trying to reset.

read_string: timedout without reading a character
rig:rig_close called
rig:rig_cleanup called

GConfClient-WARNING **: Directory `/apps/gpredict' was not being
monitored by GConfClient 0x80aa518
Regards
Sid.
-- 
Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot
Linux only shop

[Hamlib-developer] Musings on backend behavior

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

Hi all.

I'm in an email mood tonight.  :)

As I've worked on the backend library for the FT-920 a number of the
warts and quirks of the radio are exposed through the frontend library
to the application.  Really, I think this is incorrect as Hamlib should
hide these things from the application.

So, what I would like to see in the API documentation is a description
of the expected behavior of the function at hand.  While this is often
obvious, some things are more subtle and I would like a more defined
target to work toward.

Thus I think a firm definition of the virtual radio Hamlib presents to
the application would be a big help to authors on each side of the
frontend.

Comments?  Ideas?

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
  Amateur radio exams; ham radio; Linux info @  | a terrible resolve".
             http://www.qsl.net/n0nb/           | - Admiral Yamomoto

[Hamlib-developer] rigctl options

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

Hi Stephane.

I noticed that in the latest update of rigctl several more options were
added that use the characters 0x80 through 0x84.  These show only as a
query (?) on my screen and I'm not sure how to access these functions.
I was patching my local copy with the numeral 1 for the option to
dumpcaps so I could access it.  These are extended characters that I can
create in DOS, but they throw me in Bash.

What am I missing?

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
  Amateur radio exams; ham radio; Linux info @  | a terrible resolve".
             http://www.qsl.net/n0nb/           | - Admiral Yamomoto

Re: [Hamlib-developer] @LTLIBOBJS@

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

On Thu, Nov 28, 2002, Robert Steinhäußer wrote:
> Perhaps including the WANT_AUTOCONF_2_5 to autogen.sh is ok?

commited.
A new snapshot is to come in http://hamlib.org/bleeding-edge/


73's
Stephane

[Hamlib-developer] REQUESTED EDUCATION & STRATEGY PACKAGE

[<leb...@ya...>]

PGh0bWw+DQoNCg0KPGJvZHk+DQoNCjxwIGFsaWduPSJsZWZ0Ij4NCjxiPg0K
PGZvbnQgZmFjZT0iVmVyZGFuYSwgQXJpYWwsIEhlbHZldGljYSwgc2Fucy1z
ZXJpZiIgY29sb3I9IiMwMDAwODAiPg0KUmVxdWVzdCBZb3VyIEZyZWUgSW52
ZXN0bWVudCBFZHVjYXRpb248L2ZvbnQ+PC9iPjwvcD4NCjxwIGFsaWduPSJs
ZWZ0Ij4NCjxiPg0KPGZvbnQgZmFjZT0iVmVyZGFuYSwgQXJpYWwsIEhlbHZl
dGljYSwgc2Fucy1zZXJpZiIgY29sb3I9IiMwMDAwODAiPkFuZCANClN0cmF0
ZWd5IFBhY2thZ2UgVG9kYXk8L2ZvbnQ+PC9iPjwvcD4NCjxwIGFsaWduPSJs
ZWZ0Ij48Yj4NCjxmb250IGZhY2U9IlZlcmRhbmEsIEFyaWFsLCBIZWx2ZXRp
Y2EsIHNhbnMtc2VyaWYiIGNvbG9yPSIjMDAwMDgwIj4NCllvdSBIYXZlIE5v
dGhpbmcgVG8gTG9vc2UgQW5kIEEgV29ybGQgT2YgRWR1Y2F0aW9uIFRvIEdh
aW4gPC9mb250PjwvYj48L3A+DQo8cCBhbGlnbj0ibGVmdCI+PGI+DQo8Zm9u
dCBmYWNlPSJWZXJkYW5hLCBBcmlhbCwgSGVsdmV0aWNhLCBzYW5zLXNlcmlm
IiBjb2xvcj0iIzAwMDA4MCI+DQpPdmVyIDQwIG1hcmtldHMgZHJpdmVuIGJ5
IHdvcmxkIGNvbnN1bWVyIGRlbWFuZDwvZm9udD48L2I+PC9wPg0KPHAgYWxp
Z249ImxlZnQiPjxmb250IGZhY2U9IlZlcmRhbmEsIEFyaWFsLCBIZWx2ZXRp
Y2EsIHNhbnMtc2VyaWYiIHNpemU9IjQiPg0KPGEgaHJlZj0iaHR0cDovL211
c3Rnby5uZXQvZC9jb21taWQvIj48Zm9udCBjb2xvcj0iI0ZGMDAwMCI+RlJF
RSBTVFJBVEVHWSBQQUNLQUdFPC9mb250PjwvYT48L2ZvbnQ+PC9wPg0KPHAg
YWxpZ249ImNlbnRlciI+Jm5ic3A7PC9wPg0KPHAgYWxpZ249InJpZ2h0Ij4m
bmJzcDs8L3A+DQoNCjxwIGFsaWduPSJyaWdodCI+Jm5ic3A7PC9wPg0KDQo8
cCBhbGlnbj0icmlnaHQiPjxmb250IGZhY2U9IlZlcmRhbmEsIEFyaWFsLCBI
ZWx2ZXRpY2EsIHNhbnMtc2VyaWYiPg0KPGEgaHJlZj0ibWFpbHRvOnJpbmEw
NjZAeWFob28uY29tIj5yZW1vdmUgbWU8L2E+PC9mb250PjwvcD4NCg0KPC9i
b2R5Pg0KDQo8L2h0bWw+DQoNCjwhLS1TVEFUUzRBTExfU1RBUlQtLT4NCjxz
Y3JpcHQgbGFuZ3VhZ2U9ImphdmFzY3JpcHQiPjwhLS0NCnN2ZXIgPSAxMDtz
Y3JlZW5zaXplPSIiO2NvbG9ycz0iIjtuYXZsYW49IiI7cGx1Zz0iIjsNCnJl
ZiA9IGVzY2FwZShkb2N1bWVudC5yZWZlcnJlcikrIiI7DQpzVXJsID0gZXNj
YXBlKGRvY3VtZW50LlVSTCkrIiI7DQppZigocmVmPT0iIikgfHwgKHJlZj09
InVuZGVmaW5lZCIpKXtyZWY9ImJvb2ttYXJrIjt9Ow0KbmF2PW5hdmlnYXRv
ci5hcHBOYW1lOw0KaWYobmF2LnN1YnN0cmluZygwLDkpPT0iTWljcm9zb2Z0
Iil7bmF2PSJNU0lFIjt9Ow0KdmVyc2lvbj1NYXRoLnJvdW5kKHBhcnNlRmxv
YXQobmF2aWdhdG9yLmFwcFZlcnNpb24pKjEwMCk7DQppZigobmF2PT0iTVNJ
RSIpICYmIChwYXJzZUludCh2ZXJzaW9uKT09Mikpe3ZlcnNpb249MzAxO307
amF2YT0iIjsNCmlmKG5hdmlnYXRvci5hcHBOYW1lPT0iTmV0c2NhcGUiKXsg
aWYodmVyc2lvbj40MDApIG5hdmxhbj1uYXZpZ2F0b3IubGFuZ3VhZ2U7DQpp
Zih2ZXJzaW9uPjMwMClmb3IodmFyIGk9MDtpPG5hdmlnYXRvci5wbHVnaW5z
Lmxlbmd0aDtpKyspcGx1ZyArPW5hdmlnYXRvci5wbHVnaW5zW2ldLm5hbWUr
IjoifTsNCi8vLS0+PC9zY3JpcHQ+DQo8c2NyaXB0IGxhbmd1YWdlPSJqYXZh
c2NyaXB0MS4xIj48IS0tDQpzdmVyPTExO2phdmE9KG5hdmlnYXRvci5qYXZh
RW5hYmxlZCgpPT10cnVlKT8ieSI6Im4iOw0KLy8tLT48L3NjcmlwdD4NCjxz
Y3JpcHQgbGFuZ3VhZ2U9ImphdmFzY3JpcHQxLjIiPjwhLS0NCnN2ZXI9MTI7
c2NyZWVuc2l6ZT1zY3JlZW4ud2lkdGgrIioiK3NjcmVlbi5oZWlnaHQ7DQpj
b2xvcnM9KG5hdj09Ik1TSUUiKT9zY3JlZW4uY29sb3JEZXB0aDpzY3JlZW4u
cGl4ZWxEZXB0aDsNCmlmKGNvbG9ycz09InVuZGVmaW5lZCIpe2NvbG9ycz0i
Ijt9Ow0KLy8tLT48L3NjcmlwdD4NCjxzY3JpcHQgbGFuZ3VhZ2U9ImphdmFz
Y3JpcHQxLjMiPjwhLS0NCnN2ZXI9MTM7DQovLy0tPjwvc2NyaXB0Pg0KPHNj
cmlwdCBsYW5ndWFnZT0iamF2YXNjcmlwdCI+PCEtLQ0KYXJndW1lbnRzPSIm
bmF2PSIrbmF2KyImdmVyc2lvbj0iK3ZlcnNpb24rIiZzY3JlZW5zaXplPSIr
c2NyZWVuc2l6ZSsiJmNvbG9ycz0iK2NvbG9ycysiJnN2ZXI9IitzdmVyOw0K
YXJndW1lbnRzKz0iJmphdmE9IitqYXZhKyImcmY9IityZWYrIiZuYXZsYW49
IituYXZsYW4rIiZwbHVnPSIrZXNjYXBlKHBsdWcpKyImc1VybD0iK3NVcmw7
DQpkb2N1bWVudC53cml0ZSAoIjxBIEhSRUY9J2h0dHA6Ly93d3cuc3RhdHM0
YWxsLmNvbS9hc3AvbG9naW4uYXNwP3NTaXRlTmFtZT1hYmJhNTAxMicgdGFy
Z2V0PV9ibGFuaz48SU1HIEJPUkRFUj0wIGhlaWdodD0xNiB3aWR0aD0xNiBT
UkM9J2h0dHA6Ly93d3cuaGl0LnN0YXRzNGFsbC5jb20vYXNwL2hpdC5hc3A/
c1NpdGVOYW1lPWFiYmE1MDEyIiArIGFyZ3VtZW50cyArICImc0V4dHJhPU5v
bmUnPjwvQT4iKQ0KLy8tLT48L3NjcmlwdD4NCjxzY3JpcHQgbGFuZ3VhZ2U9
ImphdmFzY3JpcHQxLjIiPjwhLS0NCmRvY3VtZW50LndyaXRlKCI8Iik7ZG9j
dW1lbnQud3JpdGUoIiEtLSIpOw0KLy8tLT48L3NjcmlwdD4NCjxub3Njcmlw
dD4NCjxhIGhyZWY9J2h0dHA6Ly93d3cuc3RhdHM0YWxsLmNvbS9hc3AvbG9n
aW4uYXNwP3NTaXRlTmFtZT1hYmJhNTAxMicgdGFyZ2V0PV9ibGFuaz4NCjxp
bWcgQk9SREVSPTAgaGVpZ2h0PTE2IHdpZHRoPTE2IHNyYz0naHR0cDovL3d3
dy5oaXQuc3RhdHM0YWxsLmNvbS9hc3AvaGl0LmFzcD9zU2l0ZU5hbWU9YWJi
YTUwMTInPjwvYT48L25vc2NyaXB0Pg0KPHNjcmlwdCBsYW5ndWFnZT0iamF2
YXNjcmlwdDEuMiI+PCEtLQ0KZG9jdW1lbnQud3JpdGUoIi0tIik7ZG9jdW1l
bnQud3JpdGUoIj4iKTsNCi8vLS0+PC9zY3JpcHQ+DQo8IS0tU1RBVFM0QUxM
X0VORC0tPg0KNjQ3Nmw0

Re: [Hamlib-developer] @LTLIBOBJS@

[Robert <ro...@st...>]

OK, now I tried once again. Compile went fine after twiddling a bit with =
the=20
settings.

automake seems to be (fairly) irrelevant, i.e. I'm using standard 1.4p5. =
But=20
1.6 is OK, too (at least no LIBOBJS-problem).

Now the autoconf version matters. Even the newest "stable" (in my Gentoo=20
Linux) 2.53a didn't work. I have to build 2.54, which Gentoo always wants=
 to=20
"upgrade" to 2.53a.

This procedure worked:

=09# unset WANT_AUTOMAKE_1_6=09# doesn't really matter
=09# export WANT_AUTOCONF_2_5 # 2.54, not 2.53a or 2.13
=09# ./autogen
=09# make

Perhaps including the WANT_AUTOCONF_2_5 to autogen.sh is ok?

73, Robert

[Hamlib-developer] Propel Your Job Future hamlib-developer

[Gale C. <Car...@cy...>]

WU9VUiBERUdSRUUgTUFZIEJFIENMT1NFUiBUSEFOIFlPVSBUSElOSw0KV2UgcmVtb3ZlIHRo
ZSBvYnN0YWNsZXMgdGhhdCBjYXVzZSBhZHVsdHMgdG8gYWJhbmRvbiBob3BlLg0KRElEIFlP
VSBLTk9XIHRoYXQgeW91IGNvdWxkIGVhcm4geW91ciBsZWdpdGltYXRlIEFzc29jaWF0ZSdz
LCBCYWNoZWxvcidzLCBNYXN0ZXIncyBvciBldmVuIERvY3RvcmF0ZSBkZWdyZWUsIHV0aWxp
emluZyB5b3VyIGFscmVhZHkgZXhpc3RpbmcgcHJvZmVzc2lvbmFsIG9yIGFjYWRlbWljIGV4
cGVydGlzZT8gDQoNClByZXBhcmUgZm9yIHRoZSBwcm9mZXNzaW9uYWwgYWR2YW5jZW1lbnQg
eW91IGRlc2VydmUNCklmIHlvdSBhcmUgYW4gYWR1bHQgd2l0aCBhIGhpZ2ggc2Nob29sIGRp
cGxvbWEgYW5kIGhhdmUgYSBtaW5pbXVtIG9mIHRocmVlIHllYXJzIG9mIGV4cGVyaWVuY2Ug
aW4gdGhlIGZpZWxkIHlvdSBhcmUgc2Vla2luZyBhIGRlZ3JlZSBpbiwgWU9VIFFVQUxJRlku
DQoNCkFzIHlvdSBrbm93LCBlbXBsb3llcnMgY29udGludWFsbHkgaGlyZSwgcHJvbW90ZSBh
bmQgZ2l2ZSByYWlzZXMgdG8gbmV3IGVtcGxveWVlcyB0aGF0IGhhdmUgWkVSTyBza2lsbHMg
b3IgZXhwZXJpZW5jZSwganVzdCBiZWNhdXNlIHRoZXkgaGF2ZSB0aGF0IHBpZWNlIG9mIHBh
cGVyLg0KVGFrZSBwYXJ0IGluIHRoZSB3ZWFsdGggbm93ISAgIFdpdGhpbiBkYXlzIHlvdSBj
YW4gYXBwbHkgZm9yIHRoYXQgdW5yZWFjaGFibGUgam9iLCBvciBzaG93IHlvdXIgZGVncmVl
IHRvIHlvdXIgZW1wbG95ZXIgYW5kIGRlbWFuZCB0aGUgcmFpc2UgYW5kIHByb21vdGlvbiB0
aGF0IHlvdXIga25vd2xlZGdlIGFuZCBza2lsbHMgZGVzZXJ2ZS4NCkhvdyBkb2VzIHRoaXMg
d29yaz8gIFlvdSBncmFkdWF0ZSB3aXRob3V0IGF0dGVuZGluZyBjbGFzc2VzLCBvciB0YWtp
bmcgYSBsZWF2ZSBvZiBhYnNlbmNlIGZyb20geW91ciBjdXJyZW50IGpvYi4gIFlvdSByZWNl
aXZlIHlvdSBkZWdyZWUgYmFzZWQgb24gbGlmZSBhbmQgd29yayBleHBlcmllbmNlIQ0KVGhl
IGRlZ3JlZSBlYXJuZWQgYnkgb3VyIHN0dWRlbnRzIGVuYWJsZXMgdGhlbSB0byBxdWFsaWZ5
IGZvciBjYXJlZXIgYWR2YW5jZW1lbnQgYW5kIHBlcnNvbmFsIGdyb3d0aCwgd2hpbGUgYnJl
YWtpbmcgZG93biB0aGUgd2FsbCB0aGF0IHByZXZlbnRzIHRoZW0gZnJvbSByZWNlaXZpbmcg
YmlnIG1vbmV5Lg0KDQpEZWdyZWUgdmVyaWZpY2F0aW9uIGFuZCBvZmZpY2lhbCB0cmFuc2Ny
aXB0cyB3aWxsIGJlIHByb3ZpZGVkIGluIHdyaXRpbmcgd2hlbiByZXF1ZXN0ZWQgYnkgZW1w
bG95ZXJzIGFuZCBvdGhlcnMgYXV0aG9yaXplZCBieSB0aGUgZ3JhZHVhdGUuIE91ciBjb2xs
ZWdlICYgVW5pdmVyc2l0eSB0cmFuc2NyaXB0cyBtZWV0IHRoZSBoaWdoZXN0IGFjYWRlbWlj
IHN0YW5kYXJkcy4gT3VyIFVuaXZlcnNpdHkgaXNzdWVzIGEgZGVncmVlIHByaW50ZWQgb24g
cHJlbWl1bSBkaXBsb21hIHBhcGVyLCBiZWFyaW5nIGFuIG9mZmljaWFsIGdvbGQgcmFpc2Vk
IGNvbGxlZ2Ugc2VhbC4NCiANCk5vIG9uZSBpcyB0dXJuZWQgZG93bi4NCg0KQ29uZmlkZW50
aWFsaXR5IGFzc3VyZWQuDQoNCkNBTEwgMS02MDItMjMwLTQyNTINCg0KQ2FsbCAyNCBob3Vy
cyBhIGRheSwgNyBkYXlzIGEgd2VlaywgaW5jbHVkaW5nDQpTdW5kYXlzIGFuZCBob2xpZGF5
cy4NCg0KDQpUbyBiZSB0YWtlbiBvZmYgb3VyIGxpc3QgcmVwbHkgd2l0aCBvZmYgYXMgdGhl
IHN1YmplY3Qu

[Hamlib-developer] Money for hamlib-developer

[Andrea B. <Ang...@ex...>]

PEhUTUw+PFAgQUxJR049Q0VOVEVSPjxGT05UICBTSVpFPTYgUFRTSVpFPTI0PjxCPmhhbWxp
Yi1kZXZlbG9wZXIsPEJSPg0KPC9GT05UPjxGT05UICBDT0xPUj0iI2ZmMDAwMCIgQkFDSz0i
I2ZmZmZmZiIgc3R5bGU9IkJBQ0tHUk9VTkQtQ09MT1I6ICNmZmZmZmYiIFNJWkU9NiBQVFNJ
WkU9MjQgRkFNSUxZPSJTQU5TU0VSSUYiIEZBQ0U9IkFyaWFsIiBMQU5HPSIwIj48VT5Zb3Ug
aGF2ZSBiZWVuIGFwcHJvdmVkLjxCUj4NCjwvRk9OVD48Rk9OVCAgQ09MT1I9IiNmZjAwMDAi
IEJBQ0s9IiNmZmZmZmYiIHN0eWxlPSJCQUNLR1JPVU5ELUNPTE9SOiAjZmZmZmZmIiBTSVpF
PTUgUFRTSVpFPTE4IEZBTUlMWT0iU0FOU1NFUklGIiBGQUNFPSJBcmlhbCIgTEFORz0iMCI+
PC9VPkNhc2ggR3JhbnQgQW1vdW50OjxCUj4NCjwvRk9OVD48Rk9OVCAgQ09MT1I9IiMwMDAw
ZmYiIEJBQ0s9IiNmZmZmZmYiIHN0eWxlPSJCQUNLR1JPVU5ELUNPTE9SOiAjZmZmZmZmIiBT
SVpFPTcgUFRTSVpFPTM2IEZBTUlMWT0iU0FOU1NFUklGIiBGQUNFPSJBcmlhbCIgTEFORz0i
MCI+JDEwLDAwMC0kNSwwMDAsMDAwPEJSPg0KPC9GT05UPjxGT05UICBDT0xPUj0iIzAwMDAw
MCIgQkFDSz0iI2ZmZmZmZiIgc3R5bGU9IkJBQ0tHUk9VTkQtQ09MT1I6ICNmZmZmZmYiIFNJ
WkU9NiBQVFNJWkU9MjQgRkFNSUxZPSJTQU5TU0VSSUYiIEZBQ0U9IkFyaWFsIiBMQU5HPSIw
Ij48ST48VT5EaWQgWW91IEtub3c/PEJSPg0KPC9GT05UPjxGT05UICBDT0xPUj0iIzAwMDAw
MCIgQkFDSz0iI2ZmZmZmZiIgc3R5bGU9IkJBQ0tHUk9VTkQtQ09MT1I6ICNmZmZmZmYiIFNJ
WkU9NSBQVFNJWkU9MTggRkFNSUxZPSJTQU5TU0VSSUYiIEZBQ0U9IkFyaWFsIiBMQU5HPSIw
Ij48L0I+PC9JPjwvVT4tRWFjaCBZZWFyIHRoZSBVLlMuIEdvdmVybWVudCBHaXZlcyBhd2F5
IEJJTExJT05TIGluIGNhc2ggZ3JhbnRzPzxCUj4NCi1UaGVyZSZuYnNwOyBhcmUgTm8gc3Bl
Y2lhbCByZXF1aXJlbWVudHMgdG8gb2J0YWluIHRoZXNlIGdyYW50cy48QlI+DQotVGhlc2Ug
YXJlIEZyZWUgQ2FzaCBHcmFudHMgVGhhdCB5b3UgTkVWRVIgaGF2ZSB0byByZXBheSE8QlI+
DQo8QlI+DQo8L0ZPTlQ+PEZPTlQgIENPTE9SPSIjMDAwMDAwIiBCQUNLPSIjZmZmZmZmIiBz
dHlsZT0iQkFDS0dST1VORC1DT0xPUjogI2ZmZmZmZiIgU0laRT02IFBUU0laRT0yNCBGQU1J
TFk9IlNBTlNTRVJJRiIgRkFDRT0iQXJpYWwiIExBTkc9IjAiPmhhbWxpYi1kZXZlbG9wZXIs
WW91IFF1YWxpZnkhPEJSPg0KPC9GT05UPjxGT05UICBDT0xPUj0iIzAwMDBmZiIgQkFDSz0i
I2ZmZmZmZiIgc3R5bGU9IkJBQ0tHUk9VTkQtQ09MT1I6ICNmZmZmZmYiIFNJWkU9NyBQVFNJ
WkU9MzYgRkFNSUxZPSJTQU5TU0VSSUYiIEZBQ0U9IkFyaWFsIiBMQU5HPSIwIj48QSBIUkVG
PSJodHRwOi8vcmQueWFob28uY29tLzY0NTExMS8qaHR0cDovL3d3dy5mcmVlaG9zdG5ldHdv
cmsuY29tL2dyYW50MmsvaW5kZXguYXNwP2R2bj0pOExmNSh9QzFJMWY2NzEyeGY1OTM5dzk2
XzJKMUI2MmExd20xMyI+Q2xpY2sgSGVyZTwvQT48L0ZPTlQ+PEZPTlQgIENPTE9SPSIjMDAw
MDAwIiBCQUNLPSIjZmZmZmZmIiBzdHlsZT0iQkFDS0dST1VORC1DT0xPUjogI2ZmZmZmZiIg
U0laRT01IFBUU0laRT0xOCBGQU1JTFk9IlNBTlNTRVJJRiIgRkFDRT0iQXJpYWwiIExBTkc9
IjAiPjxCUj4NCjwvRk9OVD48Rk9OVCAgQ09MT1I9IiNmZjAwMDAiIEJBQ0s9IiNmZmZmZmYi
IHN0eWxlPSJCQUNLR1JPVU5ELUNPTE9SOiAjZmZmZmZmIiBTSVpFPTcgUFRTSVpFPTM2IEZB
TUlMWT0iU0FOU1NFUklGIiBGQUNFPSJBcmlhbCIgTEFORz0iMCI+PEI+TGltaXRlZCBUaW1l
IE9mZmVyPC9GT05UPjxGT05UICBDT0xPUj0iIzAwMDBmZiIgQkFDSz0iI2ZmZmZmZiIgc3R5
bGU9IkJBQ0tHUk9VTkQtQ09MT1I6ICNmZmZmZmYiIFNJWkU9NyBQVFNJWkU9MzYgRkFNSUxZ
PSJTQU5TU0VSSUYiIEZBQ0U9IkFyaWFsIiBMQU5HPSIwIj48QlI+DQo8L0ZPTlQ+PEZPTlQg
IENPTE9SPSIjZmYwMDAwIiBCQUNLPSIjZmZmZmZmIiBzdHlsZT0iQkFDS0dST1VORC1DT0xP
UjogI2ZmZmZmZiIgU0laRT02IFBUU0laRT0yNCBGQU1JTFk9IlNBTlNTRVJJRiIgRkFDRT0i
QXJpYWwiIExBTkc9IjAiPjwvQj48QlI+DQo8QlI+DQo8L1A+PC9GT05UPjwvSFRNTD4=

[Hamlib-developer] Direct Mail is the way to go

[<mar...@ho...>]

<html>

<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>New Page 1</title>
</head>

<body bgproperties="fixed">

<p align="center"><font size="5" color="#000080"><b>Christmas Is Coming</b></font></p>

<p align="center"><b><font face="Times New Roman" size="5" color="#000080">Email
Your Site For Less Than A Penny A Name</font></b></p>

<p align="center"><b><font size="5" color="#000080">Explosive email campaigns 
for less</font></b></p>

<p align="center"><b><font size="5" color="#000080">1 million emails sent for 
$500.00</font></b></p>

<p align="center"><b><i><a href="http://mustgo.net/d/baymed">
<font size="7" color="#FF0000">Website</font></a></i></b></p>

<p align="center">&nbsp;</p>
<p align="center">&nbsp;</p>
<p align="center">&nbsp;</p>
<p align="center"><a href="mailto:po...@ho...">Remove</a></p>
<p align="center">&nbsp;</p>

</body>

</html>

<!-- Gostats.com web hit code. Please do not change this-->
<script>var go_mem="tarastevens";</script>
<script src="http://gostats.com/go.js"></script>
<noscript>
<a href="http://gostats.com/gogi/viewstats.pl?mn=tarastevens" target="_top">
<img src="http://gostats.com/gogi/count.pl?mn=tarastevens" border=0></a></noscript><br>
<a href="http://gostats.com">Get a GoStats hit counter</a><!-- End of Gostats.com web hit code -->
4393WEtC6-975qTii7216Zl21

Re: [Hamlib-developer] IC737 ?

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

On Sun, Nov 24, 2002 at 08:23:14PM +0000, Sid Boyce wrote:
> 	Some success to report."rigctl -Ccivaddr=0x3c -m 319 -vvvvvv" gave me
> the following results:-
> -------------------------------------------------------
> rig:rig_open called
> Opened rig model 319, 'IC-735'
> Backend version: 0.2, Status: Alpha
> 
> Rig command: f
> TX 6 bytes
> 0000     fe fe 3c e0 03 fd      ..<...
> RX 6 characters
> 0000     fe fe 3c e0 03 fd      ..<...
> RX 11 characters
> 0000     fe fe e0 3c 03 70 10 20 14 00 fd       ...<.p. ...
> icom_get_freq: wrong frame len=5
> get_freq: error = Command rejected by the rig
[..]
> ---------------------------------------------
> I've tried most commands, but those are the ones that gave me other than
> "Feature Not Available". Specifying an IC756 did not work.
> 73....Sid.

This is because the 735 uses different freq len. The best for you is
to grab the latest from http://hamlib.org/bleeding-edge/ , it has 
support the IC-737. The "-m 321" is your friend.

73 de Stephane

[Hamlib-developer] Re: IC737 - more testing

[Sid B. <sb...@bl...>]

	I tried "-m 319" and am able to get/set frequency, also with grig I am
able to use mouse clicks to tune up/down, steps depending on what figure
I click on, e.g if I am on 7075.000 and I click on the "5", it changes
up to "7076.000"  or down to "7074.000". I've now altered ic775.c to
default address 0x3c, so I can access using grig.
73...Sid.

On Mon, 2002-11-18 at 22:35, Stephane Fillod wrote:
> On Sat, Nov 16, 2002 at 02:59:03PM +0000, Sid Boyce wrote:
> > 	I had been trying via grig, using IC735 and IC756, also under rigctl -m
> > 300 (IC-DoItAll) and also rigctl -m 321 (IC737). It appears that if the
> > rig isn't in the list (rigctl --list), it won't work. 
> > ------------------------------------------
> > # rigctl -Ccivaddr=0x3c
> > Config parameter error: Feature not available
> 
> try "rigctl -Ccivaddr=0x3c -m 326 -vvvvvv"
> You should be able at least to exercise basic support.
> 
> Let me know if you have trouble checking out the CVS version
> (the autoconf/automake versions can be troublesome).
> I can put a snapshot on the web site.
> 
> 73's
> Stephane
-- 
Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot
Linux only shop

[Hamlib-developer] TS450S connections ?

[Sid B. <sb...@bl...>]

	All the interfaces I've seen on the web don't seem to cater for the rig
I have here and I have somehow mislaid the manual during QSY to the
present shack.
On the left side I have 7-pin DIN socket.
At the rear, there are ....
ACC3 - power socket to the left of the main DC input.
left to right ... DSP3 (Multi), DSP2(Phono), DSP1(phono), REMOTE
(Multi), EXT. SP 8ohm (3.5mm socket), CW KEY and ACC2 (Multi).
	Can anyone please tell me if any of these provide for a connection to a
PC for rigctl operation ?
73....Sid.

-- 
Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot
Linux only shop

Re: [Hamlib-developer] IC737 ?

[Sid B. <sb...@bl...>]

	Some success to report."rigctl -Ccivaddr=0x3c -m 319 -vvvvvv" gave me
the following results:-
-------------------------------------------------------
rig:rig_open called
Opened rig model 319, 'IC-735'
Backend version: 0.2, Status: Alpha

Rig command: f
TX 6 bytes
0000     fe fe 3c e0 03 fd      ..<...
RX 6 characters
0000     fe fe 3c e0 03 fd      ..<...
RX 11 characters
0000     fe fe e0 3c 03 70 10 20 14 00 fd       ...<.p. ...
icom_get_freq: wrong frame len=5
get_freq: error = Command rejected by the rig

Rig command: m
TX 6 bytes
0000     fe fe 3c e0 04 fd      ..<...
RX 6 characters
0000     fe fe 3c e0 04 fd      ..<...
RX 8 characters
0000     fe fe e0 3c 04 01 01 fd        ...<....
Mode: USB
Passband: 2400
Rig command: E
Memory#: 1
TX 7 bytes
0000     fe fe 3c e0 08 01 fd   ..<....
RX 7 characters
0000     fe fe 3c e0 08 01 fd   ..<....
RX 6 characters
0000     fe fe e0 3c fb fd      ...<..
---------------------------------------------
I've tried most commands, but those are the ones that gave me other than
"Feature Not Available". Specifying an IC756 did not work.
73....Sid.



On Mon, 2002-11-18 at 22:35, Stephane Fillod wrote:
> On Sat, Nov 16, 2002 at 02:59:03PM +0000, Sid Boyce wrote:
> > 	I had been trying via grig, using IC735 and IC756, also under rigctl -m
> > 300 (IC-DoItAll) and also rigctl -m 321 (IC737). It appears that if the
> > rig isn't in the list (rigctl --list), it won't work. 
> > ------------------------------------------
> > # rigctl -Ccivaddr=0x3c
> > Config parameter error: Feature not available
> 
> try "rigctl -Ccivaddr=0x3c -m 326 -vvvvvv"
> You should be able at least to exercise basic support.
> 
> Let me know if you have trouble checking out the CVS version
> (the autoconf/automake versions can be troublesome).
> I can put a snapshot on the web site.
> 
> 73's
> Stephane
-- 
Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot
Linux only shop

[Hamlib-developer] New concept of giving for hamlib-developer

[Florida C. <Bla...@to...>]

PGh0bWw+DQo8Qk9EWSA+PFAgYWxpZ249Y2VudGVyPjxGT05UIHNpemU9NiBQVFNJWkU9IjI0
Ij48Qj5oYW1saWItZGV2ZWxvcGVyLDxCUj48L0ZPTlQ+PEZPTlQgbGFuZz0wIHN0eWxlPSJC
QUNLR1JPVU5ELUNPTE9SOiAjZmZmZmZmIiBmYWNlPUFyaWFsIGNvbG9yPSNmZjAwMDAgc2l6
ZT02IFBUU0laRT0iMjQiIEZBTUlMWT0iU0FOU1NFUklGIiBCQUNLPSIjZmZmZmZmIj48VT5Z
b3UgaGF2ZSBiZWVuIGFwcHJvdmVkLjxCUj48L0ZPTlQ+PEZPTlQgbGFuZz0wIHN0eWxlPSJC
QUNLR1JPVU5ELUNPTE9SOiAjZmZmZmZmIiBmYWNlPUFyaWFsIGNvbG9yPSNmZjAwMDAgc2l6
ZT01IFBUU0laRT0iMTgiIEZBTUlMWT0iU0FOU1NFUklGIiBCQUNLPSIjZmZmZmZmIj48L1U+
Q2FzaCBHcmFudCBBbW91bnQ6PEJSPjwvRk9OVD48Rk9OVCBsYW5nPTAgc3R5bGU9IkJBQ0tH
Uk9VTkQtQ09MT1I6ICNmZmZmZmYiIGZhY2U9QXJpYWwgY29sb3I9IzAwMDBmZiBzaXplPTcg
UFRTSVpFPSIzNiIgRkFNSUxZPSJTQU5TU0VSSUYiIEJBQ0s9IiNmZmZmZmYiPiQxMCwwMDAt
JDUsMDAwLDAwMDxCUj48L0ZPTlQ+PEZPTlQgbGFuZz0wIHN0eWxlPSJCQUNLR1JPVU5ELUNP
TE9SOiAjZmZmZmZmIiBmYWNlPUFyaWFsIGNvbG9yPSMwMDAwMDAgc2l6ZT02IFBUU0laRT0i
MjQiIEZBTUlMWT0iU0FOU1NFUklGIiBCQUNLPSIjZmZmZmZmIj48ST48VT5EaWQgWW91IEtu
b3c/PEJSPjwvRk9OVD48Rk9OVCBsYW5nPTAgc3R5bGU9IkJBQ0tHUk9VTkQtQ09MT1I6ICNm
ZmZmZmYiIGZhY2U9QXJpYWwgY29sb3I9IzAwMDAwMCBzaXplPTUgUFRTSVpFPSIxOCIgRkFN
SUxZPSJTQU5TU0VSSUYiIEJBQ0s9IiNmZmZmZmYiPjwvQj48L0k+PC9VPi1FYWNoIFllYXIg
dGhlIFUuUy4gR292ZXJtZW50IEdpdmVzIGF3YXkgQklMTElPTlMgaW4gY2FzaCBncmFudHM/
PEJSPi1UaGVyZSZuYnNwOyBhcmUgTm8gc3BlY2lhbCByZXF1aXJlbWVudHMgdG8gb2J0YWlu
IHRoZXNlIGdyYW50cy48QlI+LVRoZXNlIGFyZSBGcmVlIENhc2ggR3JhbnRzIFRoYXQgeW91
IE5FVkVSIGhhdmUgdG8gcmVwYXkhPEJSPjxCUj48L0ZPTlQ+PEZPTlQgbGFuZz0wIHN0eWxl
PSJCQUNLR1JPVU5ELUNPTE9SOiAjZmZmZmZmIiBmYWNlPUFyaWFsIGNvbG9yPSMwMDAwMDAg
c2l6ZT02IFBUU0laRT0iMjQiIEZBTUlMWT0iU0FOU1NFUklGIiBCQUNLPSIjZmZmZmZmIj5o
YW1saWItZGV2ZWxvcGVyLFlvdSBRdWFsaWZ5ITxCUj48L0ZPTlQ+PEZPTlQgbGFuZz0wIHN0
eWxlPSJCQUNLR1JPVU5ELUNPTE9SOiAjZmZmZmZmIiBmYWNlPUFyaWFsIGNvbG9yPSMwMDAw
ZmYgc2l6ZT03IFBUU0laRT0iMzYiIEZBTUlMWT0iU0FOU1NFUklGIiBCQUNLPSIjZmZmZmZm
Ij48QSBocmVmPSJodHRwOi8vcmQueWFob28uY29tLzU0MzM0LypodHRwOi8vd3d3LmFsd2F5
czRsZXNzLm5ldC9ncmFudDJrL2luZGV4LmFzcD9jdm49IyNlbmNvZGVkIyMiPkNsaWNrIEhl
cmU8L0E+PC9GT05UPjxGT05UIGxhbmc9MCBzdHlsZT0iQkFDS0dST1VORC1DT0xPUjogI2Zm
ZmZmZiIgZmFjZT1BcmlhbCBjb2xvcj0jMDAwMDAwIHNpemU9NSBQVFNJWkU9IjE4IiBGQU1J
TFk9IlNBTlNTRVJJRiIgQkFDSz0iI2ZmZmZmZiI+PEJSPjwvRk9OVD48Rk9OVCBsYW5nPTAg
c3R5bGU9IkJBQ0tHUk9VTkQtQ09MT1I6ICNmZmZmZmYiIGZhY2U9QXJpYWwgY29sb3I9I2Zm
MDAwMCBzaXplPTcgUFRTSVpFPSIzNiIgRkFNSUxZPSJTQU5TU0VSSUYiIEJBQ0s9IiNmZmZm
ZmYiPjxCPkxpbWl0ZWQgVGltZSBPZmZlcjwvRk9OVD48Rk9OVCBsYW5nPTAgc3R5bGU9IkJB
Q0tHUk9VTkQtQ09MT1I6ICNmZmZmZmYiIGZhY2U9QXJpYWwgY29sb3I9IzAwMDBmZiBzaXpl
PTcgUFRTSVpFPSIzNiIgRkFNSUxZPSJTQU5TU0VSSUYiIEJBQ0s9IiNmZmZmZmYiPjxCUj48
L0ZPTlQ+PEZPTlQgbGFuZz0wIHN0eWxlPSJCQUNLR1JPVU5ELUNPTE9SOiAjZmZmZmZmIiBm
YWNlPUFyaWFsIGNvbG9yPSNmZjAwMDAgc2l6ZT02IFBUU0laRT0iMjQiIEZBTUlMWT0iU0FO
U1NFUklGIiBCQUNLPSIjZmZmZmZmIj48L0I+PEJSPjxCUj48L1A+PC9GT05UPjwvQk9EWT4N
CjwvaHRtbD4NCiAgICAgICAgICAgICAgICAgICAgDQogICAgICAgICAgICAgICAgICAgIA==

Re: [Hamlib-developer] Licensing

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

* Stephane Fillod <f8...@fr...> [2002 Nov 17 21:42 -0600]:
> 	(fillods@charybde:hamlib)$ grep '"GPL"' */*.c
> 	gnuradio/gr.c:  .copyright =     "GPL",
> 	yaesu/ft100.c:  .copyright =            "GPL",
> 	yaesu/ft817.c:  .copyright =            "GPL",
> 	yaesu/ft920.c:  .copyright =          "GPL",
> 
> - gnuradio is GPL, on library constraint.
> - IIRC, ft100 and ft817 were written by Chris AA1VL, cloning Frank's work
> before the licensing change.  I hope he'll be okay to relicense
> accordingly.
> - ft920: Nate, you decide :)

Okay we can safely convert the remaining files in the yaesu directory as
I received the following message from Frank today (I was able to reach him
through sourceforge address):

>Subject:
>Request to relicense source cod in Hamlib
>From:
>Nate Bargmann <n0...@ne...>
>Date:
>Wed, 20 Nov 2002 16:35:37 -0600
>To:
>vk...@ix...
>
>
>Hi Frank.
>
>Long time no hear on the Hamlib list.   
>
>I have been using your ft747.c and ft747.h files as the base for
>support   
>for the FT-920 in Hamlib.  About a year ago a licensing change for the
>main front-end library to the Lesser GPL was announced.  Consistent
>with
>that action Stephane has requested that new code contributed to Hamlib
>be licensed under the LGPL.
>
>Your files still carry the GPL boilerplate and as such I am carrying
>the
>GPL boilerplate in the files I am working with.  So, for consistency
>with the rest of the project, I would like to ask your permission to
>re-license the files which carry your copyright to the LGPL.
>
>73, de Nate >>
>

Hi Nate,

Nice to hear from you.
I have no problem with LGPL being used instead of GPL, and you
have my permission to make the changes. It should promote more
usage of our libs.   


My old address gets spammed so much I rarely visit it, but I am glad
you found me :-)

Since we last spoke we are enjoying our new child, and I am training to
be a GA Pilot here in Dallas, so there has been little time
for other things..


So how has hamlib been going latelty ??

I am still a developer for http://www.ethereal.com/
mainly the CORBA part of it.

73's de Frank

-- 

So I will change the ft920.* files to the LGPL boiler plate.  Chris,
would you like to change your files or shall I do it?

BTW, we need to carefully examine the boilerplate of each file as
Stephane's grep output above missed ft747.c which still carries the GPL
boilerplate but has the LGPL string in the rig_caps structure!

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
  Amateur radio exams; ham radio; Linux info @  | a terrible resolve".
             http://www.qsl.net/n0nb/           | - Admiral Yamomoto

[Hamlib-developer] Re: ft920.c compile and new snapshot

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

* Stephane Fillod <f8...@fr...> [2002 Nov 21 19:31 -0600]:
> On Thu, Nov 21, 2002, Robert Steinhäußer wrote:
> > ft920.c: In function `ft920_set_vfo':
> > ft920.c:814: warning: `cmd_index' might be used uninitialized in this function

I'm not too worried about this warning as it is quite minor.  I simply
have an integer declared that may not get used in that function.

> > ft920.c: In function `ft920_get_vfo':
> > ft920.c:924: pointers are not permitted as case values

Hmmmm, this one seems strange as NULL should be a defined constant, not?
Or is NULL defined as a pointer in GNU C?

I shall investigate this a bit further, and yes it could be coded a bit
better...

> okay, I've commited a quick fix. Nate will certainly bring a better fix.
> 
> This is because I wanted to roll out a new bleeding-edge version tonight,
> with FT-1000MP support!

Fortunately, we keep getting better!

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
  Amateur radio exams; ham radio; Linux info @  | a terrible resolve".
             http://www.qsl.net/n0nb/           | - Admiral Yamomoto

ft920.c compile and new snapshot, was Re: [Hamlib-developer] @LTLIBOBJS@

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

On Thu, Nov 21, 2002, Robert Steinhäußer wrote:
> now my PCs are running Gentoo Linux 1.4RC1... it defaults to automake 1.4-p5 
> and autoconf 2.13, but setting WANT_AUTOMAKE_1_6=1 calls automake 1.6.3 and 
> WANT_AUTOCONF_2_5 calls autoconf 2.54... this finally got rid of the 
> LTLIBOBJS message... now I get
> 
> gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../src -I../lib -g -O2 
> -Wall -c ft920.c -MT ft920.lo -MD -MP -MF .deps/ft920.TPlo  -fPIC -DPIC -o 
> .libs/ft920.lo
> ft920.c: In function `ft920_set_vfo':
> ft920.c:814: warning: `cmd_index' might be used uninitialized in this function
> ft920.c: In function `ft920_get_vfo':
> ft920.c:924: pointers are not permitted as case values
> make[1]: *** [ft920.lo] Error 1
> make[1]: Leaving directory `/usr/src/hamlib/yaesu'
> make: *** [all-recursive] Error 1
> 
> but that'll go away soon surely ;-)

okay, I've commited a quick fix. Nate will certainly bring a better fix.

This is because I wanted to roll out a new bleeding-edge version tonight,
with FT-1000MP support!

73
Stephane

Re: [Hamlib-developer] @LTLIBOBJS@

[Robert <ro...@st...>]

Hi again,

> I remember having problems with LTLIBOBJS on some automake 1.5 versions=
,
> which was known btw to be, hmm, development work. Even 1.6 is considere=
d
> so. It looks like the 1.7 is a lot more stable, with features working a=
s
> expected.
> Okay, on some system this might be a pain to upgrade to a more recent
> automake, but this what I would suggest you. I've just tested to compil=
e
> a fresh checkout, and got no problem at all (autoconf-2.54-1 and
> automake1.7.1-1).
>
> Note, --config-cache was needed with some unstable automake versions.
> Since I'm not using it any more, some I'm going to update the README fi=
le.

now my PCs are running Gentoo Linux 1.4RC1... it defaults to automake 1.4=
-p5=20
and autoconf 2.13, but setting WANT_AUTOMAKE_1_6=3D1 calls automake 1.6.3=
 and=20
WANT_AUTOCONF_2_5 calls autoconf 2.54... this finally got rid of the=20
LTLIBOBJS message... now I get

gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../src -I../lib -=
g -O2=20
-Wall -c ft920.c -MT ft920.lo -MD -MP -MF .deps/ft920.TPlo  -fPIC -DPIC -=
o=20
=2Elibs/ft920.lo
ft920.c: In function `ft920_set_vfo':
ft920.c:814: warning: `cmd_index' might be used uninitialized in this fun=
ction
ft920.c: In function `ft920_get_vfo':
ft920.c:924: pointers are not permitted as case values
make[1]: *** [ft920.lo] Error 1
make[1]: Leaving directory `/usr/src/hamlib/yaesu'
make: *** [all-recursive] Error 1

but that'll go away soon surely ;-)

73, Robert

Re: [Hamlib-developer] Newbie Questions

[Aaron M. <tu...@am...>]

> Aaron May  [2002 Nov 18 06:09 -0600]
> Hi,
> I've just taken delivery of a nice Yaesu FT-8900R (quad band) and...<sn=
ip>

On Tue, 19 Nov 2002 01:35, Nate Bargmann wrote:
<snip>
>
> Some of the earlier FM mobiles did support CAT and the commands were
> documented in the owners manual.  Exactly what the AMDS software uses
> for commands is unknown by me, but my suspicion is that it acts in the
> same manner as the cloning function and is probably a memory dump from
> the radio to the PC and then a dump back in.  This is only a guess as I
> have no documentation supporting my opinion.
>
> If this is how it is done, then we're facing an issue of documentation.
> If Yaesu hasn't provided documentation on the data format to/from the
> radio in the owners/service literature then it must be reversed
> engineered to see how it works.  Only then will we have a clear idea of
> what level of support for the '8900 we can code into Hamlib.
>
> "It's only bits."*
>
> 73, de Nate >>
>
> * Probably already a famous quote from somewhere...

I have made some progress... there is a freeware Windows Program called E=
VE=20
which captures the clone data. I have found that you are correct in=20
suspecting that the (comercial) AMDS software does exactly as you suggest=
=2E

I have borrowed a cable from my father (also a ham) and I am about to sta=
rt=20
the laborious (but fun) task of comparing various dumps from my radio to=20
identify the "bits".  I suspect that the memory dump/clone idea falls out=
side=20
the scope of the hamlib project (?) but I thank you for your helpful=20
response.

Cheers,
Aaron, ZL3UAR

[Hamlib-developer] TODO be forever young

[Magdalena C. <Kar...@ek...>]

PGh0bWw+DQo8Ym9keQ0KPGJyPg0KQXMgc2VlbiBvbiBOPCEtLVRPRE8tLT5CPCEtLVRPRE8t
LT5DLCBDPCEtLVRPRE8tLT5CPCEtLVRPRE8tLT5TLCBDPCEtLVRPRE8tLT5OPCEtLVRPRE8t
LT5OLCBhbmQgZXZlbiBPPCEtLVRPRE8tLT5wPCEtLVRPRE8tLT5yYWguPGJyPg0KQXMgcmVw
b3J0ZWQgb24gaW4gdGhlIE5ldyBFbjwhLS1UT0RPLS0+Z2xhbmQgSm91PCEtLVRPRE8tLT5y
bmFsIG9mIE1lZGk8IS0tVE9ETy0tPmNpbmUuPGJyPg0KUmV2ZXJzZXMgYWc8IS0tVE9ETy0t
PmluZyB3aGlsZSBidXI8IS0tVE9ETy0tPm5pbmcgZjwhLS1UT0RPLS0+YXQsIHdpdGhvdXQg
ZGlldGluZyBvciBleGVyY2lzZS48YnI+DQpGb3JnZXQgIGFnaW5nIGFuZCBkaWU8IS0tVE9E
Ty0tPnRpbmcgZm9yZXZlciBBbmQgaXQncyBHdTwhLS1UT0RPLS0+YXJhbnQ8IS0tVE9ETy0t
PmVlZCE8YnI+IA0KPGJyPg0KMS5Cb2R5IEY8IS0tVE9ETy0tPmF0IExvPCEtLVRPRE8tLT5z
czxicj4NCjIuV3I8IS0tVE9ETy0tPmlua2xlIFJlZHVjPCEtLVRPRE8tLT50aW9uPGJyPg0K
My5JbmNyZWFzZWQgRW5lPCEtLVRPRE8tLT5yZ3kgTGV2ZWxzPGJyPg0KNC5NdXM8IS0tVE9E
Ty0tPmNsZSBTdHJlPCEtLVRPRE8tLT5uZ3RoIGltcHJvPCEtLVRPRE8tLT52ZW1lbnQ8YnI+
DQo1LkluY3I8IS0tVE9ETy0tPmVhc2VkIFNlPCEtLVRPRE8tLT54dWFsIFBvdDwhLS1UT0RP
LS0+ZW5jeTxicj4NCjYuSW1wPCEtLVRPRE8tLT5yb3ZlZCBFbW90aTwhLS1UT0RPLS0+b25h
bCBTdGFiPCEtLVRPRE8tLT5pbGl0eTxicj4NCjcuQjwhLS1UT0RPLS0+ZXQ8IS0tVE9ETy0t
PnRlciBNZTwhLS1UT0RPLS0+bW9yeTxicj4NCjxicj4gDQpMbzwhLS1UT0RPLS0+c2Ugd2Vp
PCEtLVRPRE8tLT5naHQgd2hpbGUgYnVpPCEtLVRPRE8tLT5sZGluZyBsZTwhLS1UT0RPLS0+
YW4gbXVzPCEtLVRPRE8tLT5jbGUgbWE8IS0tVE9ETy0tPnNzPGJyPg0KYW5kIHJldmU8IS0t
VE9ETy0tPnJzaW5nIHRoZSByYXY8IS0tVE9ETy0tPmFnZXMgb2YgYWdpbmcgYWxsIGF0IG9u
Y2UuPGJyPg0KPGJyPg0KPGEgaHJlZj0iaHR0cDovL3d3dy5jb29sZnJlZWNhcmQuY29tIj5Q
bGVhc2UgdmlzPCEtLVRPRE8tLT5pdCBvdXIgd2ViPCEtLVRPRE8tLT5zaTwhLS1UT0RPLS0+
dGUgdG8gbGU8IS0tVE9ETy0tPmFybiB0aGUgZmE8IS0tVE9ETy0tPmN0cyBhYm91dCB0aGlz
IHF1YTwhLS1UT0RPLS0+bGl0eSAgaGVhPCEtLVRPRE8tLT5sdGggIHBybzwhLS1UT0RPLS0+
ZHVjdCBhbmQgdmk8IS0tVE9ETy0tPmV3IG91ciBhYnM8IS0tVE9ETy0tPm9sdXRlIHNhdGlz
PCEtLVRPRE8tLT5mYWN0aW9uIGd1YTwhLS1UT0RPLS0+cmFudGVlPCEtLS0tPiBjbGljayBo
ZXJlPC9hPjxicj48QlI+DQo8YnI+DQpUbyB1bjwhLS1UT0RPLS0+c3ViPCEtLVRPRE8tLT5z
YzwhLS1UT0RPLS0+cmliZSBmcm9tIGZ1dDwhLS1UT0RPLS0+dXJlIG9mPCEtLVRPRE8tLT5m
ZXJzLA0KcmU8IS0tVE9ETy0tPnBseSB3aXRoIG9mPCEtLVRPRE8tLT5mDQo8L2E+PC9kaXY+
PC9ib2R5PjwvaHRtbD4NCjwvYm9keT4NCjwvaHRtbD4=

Re: [Hamlib-developer] Newbie Questions

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

* Aaron May <tu...@am...> [2002 Nov 18 06:09 -0600]:
> Hi,
> 
> I've just taken delivery of a nice Yaesu FT-8900R (quad band) and was looking 
> for bits on the net when I stumbled upon your site. 

Cool!

That sounds like a neat rig, I had completely missed it at Dayton this
spring only to read about it during the next week or so.  I hope this
radio has a better reputation than the FT-7100R which seemed plagued by
a host of manufacturing issues.

> I downloaded and (successfully!) installed the 1.1.3 version, but am missing a 
> cable to try anything with.  I will have to make one up soon.
> 
> While I have limited Linux experience, I have done some programming / web 
> stuff and am keen to help where I can.
> 
> * My radio does not support the "CAT" software that Yaesu has with some of 
> their radios, and the Yaesu AMDS system does not yet support the FT8900 (I 
> suspect it will eventually.)  So, am I wasting my time without the CAT stuff, 
> or can the ham-libs talk to my radio? 

Short answer is no.

Long answer is that nothing is impossible.  :-)

Some of the earlier FM mobiles did support CAT and the commands were
documented in the owners manual.  Exactly what the AMDS software uses
for commands is unknown by me, but my suspicion is that it acts in the
same manner as the cloning function and is probably a memory dump from
the radio to the PC and then a dump back in.  This is only a guess as I
have no documentation supporting my opinion.

If this is how it is done, then we're facing an issue of documentation.
If Yaesu hasn't provided documentation on the data format to/from the 
radio in the owners/service literature then it must be reversed
engineered to see how it works.  Only then will we have a clear idea of
what level of support for the '8900 we can code into Hamlib.

"It's only bits."*

73, de Nate >>

* Probably already a famous quote from somewhere...

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

[Hamlib-developer] Feel better hamlib-developer

[Tiara A. <Des...@qu...>]

PGh0bWw+DQo8Ym9keSBxd2VydHk9ImdkZXNtZG1yaW11Z3Zxd2FxeWF4bnVtbHN5YXhsaG50
bnRtYXdhcmZtcG5rZ2ttd21td2Npam5kaSIgYmdDb2xvcj0iI0NDQ0NDQyIgdG9wbWFyZ2lu
PTEgb25Nb3VzZU92ZXI9IndpbmRvdy5zdGF0dXM9Jyc7IHJldHVybiB0cnVlIiBvbmNvbnRl
eHRtZW51PSJyZXR1cm4gZmFsc2UiIG9uZHJhZ3N0YXJ0PSJyZXR1cm4gZmFsc2UiIG9uc2Vs
ZWN0c3RhcnQ9InJldHVybiBmYWxzZSI+DQpIZWxsbywgaGFtbGliLWRldmVsb3BlckBsaXN0
cy5zb3VyY2Vmb3JnZS5uZXQ8QlI+DQo8QlI+DQpBcyBzZTwhLS01LS0+ZW4gb24gTkI8IS0t
RC0tPkMsIENCUywgYW5kIENOPCEtLUgtLT5OLCBhbmQgZXZlbiBPcHI8IS0tRC0tPmFoISAg
VGhlIGhlYWx0aDxicj4NCmRpc2NvdmU8IS0tRi0tPnJ5IHRoYXQgYWN0dWFsbHkgcmV2ZXJz
PCEtLUQtLT5lcyBhZ2luZyB3aGlsZSBidXJuaW5nIGZhdCw8YnI+DQp3aXRoPCEtLWJveS0t
Pm91dCBkaWV0aTwhLS1ELS0+bmcgb3IgZXhlcmM8IS0tRi0tPmlzZSEgIFRoaXMgcHJvPCEt
LUEtLT52ZW4gZGlzY292ZXJ5IGhhcyBldmVuPGJyPg0KYmVlbiByZXBvcnQ8IS0taGFtbGli
LWRldmVsb3Blci0tPmVkIG9uIGJ5IHRoZSBOZTwhLS10ZXN0LS0+dyBFbmdsPCEtLS0tPmFu
ZCBKb3VyPCEtLUYtLT5uYWwgb2YgTWVkaTwhLS1GLS0+Y2luZS48YnI+DQpGb3I8IS0taGFt
bGliLWRldmVsb3Blci0tPmdldCBhZ2luZyBhbmQgZDwhLS0tLT5pZXRpbmcgZm9yZXZlciEg
IEFuZCBpdCdzIEd1YTwhLS1TLS0+cmFudGVlZCE8YnI+DQo8YnI+DQoqIFJlZDwhLS1sby0t
PnVjZSBib2R5IGZhdCBhbmQgYnVpbGQgbGVhbiBtdXNjbGUgV0lUPCEtLWhhbWxpYi1kZXZl
bG9wZXItLT5IT1VUIEVYRVJDSVNFITxicj4NCiogRW5oYTwhLS1oYW1saWItZGV2ZWxvcGVy
LS0+bmNlIHNlPCEtLWxhLS0+eHVhbCBwZXJmPCEtLWhlaGUtLT5vcm1hbmNlPGJyPg0KKiBS
ZW08IS0taGFtbGliLWRldmVsb3Blci0tPm92ZSB3cmlua2xlcyBhbmQgY2VsbHVsaXRlPGJy
Pg0KKiBMb3dlciBibG9vZCBwcmVzPCEtLWhhbWxpYi1kZXZlbG9wZXItLT5zdXJlIGFuZCBp
bXByb3ZlIGNob2xlczwhLS0tLT50ZXJvbCBwcm9maWxlPGJyPg0KKiBJbXA8IS0taGFtbGli
LWRldmVsb3Blci0tPnJvdmUgc2xlZXAsIHZpc2lvbiBhbmQgbWU8IS0tLS0+bW9yeTxicj4N
CiogUmVzdG88IS0taGFtbGliLWRldmVsb3Blci0tPnJlIGhhaXIgY29sb3IgYW5kIGdybzwh
LS0tLT53dGg8YnI+DQoqIFN0cmVuPCEtLWhhbWxpYi1kZXZlbG9wZXItLT5ndGhlbiB0aGUg
aW1tdW5lIHN5czwhLS0tLT50ZW08YnI+DQoqIEluY3JlPCEtLWhhbWxpYi1kZXZlbG9wZXIt
LT5hc2UgZW5lcjwhLS0tLT5neSBhbmQgY2FyZDwhLS0tLT5pYWMgb3V0cHV0PGJyPg0KKiBU
dXJuIGJhYzwhLS1oYW1saWItZGV2ZWxvcGVyLS0+ayB5b3VyIGJvZHkncyBiaW9sPCEtLS0t
Pm9naWNhbCB0aW1lIGNsPCEtLS0tPm9jayAxMC0yMCB5ZWFyczxicj4NCmluIDYgbW9udGhz
IG9mIHVzYWdlICEhITxicj48YnI+DQo8YSBocmVmPSJodHRwOi8vd3d3LmdyZWV0aW5ncGVy
ZmVjdC5jb20vaGVhbHRoL2luZGV4Lmh0bWwiPkZPUiBGUkU8IS0tby0tPkUgSU5GTzwhLS15
b3UtLT5STUFUSU9OIEFORCBHPCEtLWxvdmUtLT5FVCBGUkVFIA0KMSBNT048IS0taGFtbGli
LWRldmVsb3Blci0tPlRIIFNVUFBMWSBPRiBIRzwhLS0tLT5IIENMSUNLIEhFUkU8L2E+PGJy
PjxCUj4NCjxicj4NCjxkaXYgYWxpZ249ImNlbnRlciI+PGJyPg0KWW91IGFyZSByZWNlaXZp
bmcgdGhpcyBlbWFpbCBhcyBhIHN1YnNjcjwhLS1jYXRsb3Zlci0tPmliZXI8YnI+DQogIHRv
IHRoZSBPcHQ8IS0tY2F0bG92ZXItLT4tSW4gQW1lcmk8IS0tLS0+Y2EgTWFpbGluPCEtLS0t
PmcgTGlzPCEtLS0tPnQuIDxicj4NClRvIHJlbW88IS0tZG9nc2JhcmstLT52ZSB5b3VyPCEt
LS0tPnNlbGYgZnJvbSBhbGwgcmVsYXRlZCBtYWlsbGk8IS0tbWUtLT5zdHMsPGJyPmp1c3Qg
cmVwbHkNCndpdGggb2ZmLg0KPC9hPjwvZGl2PjwvYm9keT48L2h0bWw+DQo8L2JvZHk+DQo8
L2h0bWw+